Cancelled Frames after adding new Z-wave devices

[5iver (Scott Rushworth)]

@Bruce_Osborne

That would also be recommended if you were using manual Things files, but I am not sure the developer supports that any more for Z-Wave.

Manual Thing files are absolutely supported… basically a requirement for an official binding. The trouble with them is that OH dies not support updating Thing definitions, so Things need to be deleted and rediscovered to pull in an updated definition. I tried to explain here…

Rule for deleting and rediscovering Things

OH2 does not currently have a mechanism for updating Thing types. When a binding update includes new or modified Channel definitions, the Thing needs to be manually deleted and recreated in order to use the new/modified Channel. For most bindings, it is not too cumbersome to do this manually. But when you are using the Zwave binding with ~120 devices, this can be a real headache. Here is an example of how I have automated the deletion, rediscovery, and reconfiguration of my Zwave Things. I run t…

@brianmichalk

At first I thought, cool, but this means I’ll have to re-enter the specific device configuration.

Labels and locations… yes, but this can be easily added into the script that I wrote, so that they will be restored. Configuration parameters… no, these will be read in from the device and updated in OH.

@Ryan_Illman

My 3 new devices are still off at the breaker, but two are showing online in openhab, and something appears to respond to commands just enough that they get kept online.

If they are still included in the network, the controller is reporting to the binding that the devices exist. The online/offline logic is tricky to get right and is not perfect. BUT, you should not keep device powered off, especially mains powered devices. These are routing devices and the mesh needs them. If you are not using them, then exclude the devices from the network.

@Ryan_Illman

When I originally switched from SmartThings

… oops, sorry! 5 years ST free!

@Ryan_Illman

Does this hold true during the discovery process? I believe I tried that and it didn’t work (device shows up as unknown and doesn’t resolve within a few minutes, delete from inbox and rerun discovery, device still shows as unknown).

If your device is battery powered, wake it up several times to complete the discovery and initialization. Then add it in from the inbox. If it is a mains powered device, make sure it is in the device database and that the binding you are using is up to date, and also make sure that your zwave mesh is healthy… maybe take a look at a sniffer trace.

@Ryan_Illman

Looks like I picked the wrong week to quit sniffing glue.

It’s actually a very good week for it!!!