My usual routine when adding Z-Wave devices through the HASS interface is:
- Kepp track of (or verify) the most recent node ID that was added. I make small notes of the node ID and personal device identifier in my Z-Wave device configuration file to make life easier.
- Add the node.
- Go to Developer Tools -> States.
- CTRL+F and search for the assumed new node ID, eg “node_id: 40”. Verify it’s listed.
- If you’re not using a default view (‘default_view: yes’ in configuration.yaml) the new device(s) is visible in the frontend.
Sometimes the procedure requires a HASS restart if the new node and slave devices are there, but are listed as “unknown”.
I try to build and expand my Z-Wave network using a selected set of devices. I use a lot of Qubino devices, Aeotec Multisensor 6 and Fibaro wall plugs. This allows for copying the configuration entry for a previously added node, then paste and change the node ID to match the new device.
Some devices such as the most recent Z-Wave Plus product range from Aeotec signals inclusion and successful inclusion though its LED. 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).
You only need to exclude the Z-Wave deadbolt from HASS and reinclude it, after setting the network key. Just make sure you actually set a new key before performing a secure inclusion. The defauly key will not work.
OpenZWave will handle non-secure and secure devices mixed just fine. There’s no point in performing a secure inclusion with a device that doesn’t support the specified CC.
Out of curiosity, do you have any information that verifies the inability of non-secure devices to route secure traffic? I’ve never had an opportunity to perform any tests myself, but I was under the impression that a non-secure node would be able to route the signal, but only the recipient node would be able to decrypt it.