There’s no point in performing a secure inclusion with a device that doesn’t support the specified CC. OpenZWave will handle non-secure and secure devices mixed just fine. Just make sure you actually set a new key before performing a secure inclusion. You only need to exclude the Z-Wave deadbolt from HASS and reinclude it, after setting the network key.
Aeon labs z stick add device plus#
Z-Wave Plus devices from Fibaro are capable of range tests after inclusion, with a green LED signal if it’s able to communicate directly with the controller (which it should be directly after inclusion if performed close to the controller). Some devices such as the most recent Z-Wave Plus product range from Aeotec signals inclusion and successful inclusion though its LED. This allows for copying the configuration entry for a previously added node, then paste and change the node ID to match the new device. I use a lot of Qubino devices, Aeotec Multisensor 6 and Fibaro wall plugs. I try to build and expand my Z-Wave network using a selected set of devices. Sometimes the procedure requires a HASS restart if the new node and slave devices are there, but are listed as “unknown”. If you’re not using a default view (‘default_view: yes’ in configuration.yaml) the new device(s) is visible in the frontend.CTRL+F and search for the assumed new node ID, eg “node_id: 40”.I make small notes of the node ID and personal device identifier in my Z-Wave device configuration file to make life easier. Kepp track of (or verify) the most recent node ID that was added.My usual routine when adding Z-Wave devices through the HASS interface is: I like pairing with the Z stick removed from the Pi since you get that immediate flash to let you know that something happened. At this point, I’ll usually also go over to the states dev tool tab to see the generated entity_id’s for my devices to add them to groups/automations/etc.
![aeon labs z-stick add device aeon labs z-stick add device](https://m.media-amazon.com/images/S/aplus-media/vc/55153f6c-8a0e-4c2b-ae2d-187b6a0ee424._CR0,0,300,300_PT0_SX300__.jpg)
open HA and confirm that everything’s behaving.For me, this command is:Ĭp /srv/hass/src/open-zwave-control-panel/zwcfg_0xc28fd2ed.xml /home/hass/.homeassistant/zwcfg_0xc28fd2ed.xml1 I think I broke that and I’m not Linuxy enough to switch back. I manually copy my zwcfg_xxx.xml file to my homeassistant folder.hit “close” button in OZWCP and drop back to shell on my Pi.tap action button to take stick out of include mode.turn on/off the switch and watch for the fast-blink of the blue LED on the stick.put the stick in pair/include mode (tap the big action button and see the blue flash).
![aeon labs z-stick add device aeon labs z-stick add device](https://i.ytimg.com/vi/y52IAcghQ4M/maxresdefault.jpg)
remove Z-stick and bring it to the switch (or switches - I’ve done several at a time).The way I’ve always added mine (which, admittedly is a bit of a pain) is: Is this ok? Or should I be using the add from Hass, or from OZWCP, or does it matter? Does it make any difference for the secure device (schalage lock)?īTW, I do have a network key set in my options.xml, there are a number of options.xml files, but I am seeing the msg: " Info, Setting Up Provided Network Key for Secure Communications" in the OZW log, so I presume that is ok? When I added each device, I removed the Z-Stick from the rasppi and took it to each zwave device to perform the add. Read someone restarted Hass and it fixed, so I tried that, but when Hass restarted, all z-wave devices except the controller are showing dead. Woke up this morning and noticed the intermatic was showing incorrect status (showing on, but was off) and zwave status: dead. Yesterday had an intermatic light switch, a lamp module, and a Schlage lock all paired. Just set up Hass a couple days ago, have a Aeon Labs Z-Stick V5.