If you have hard reset, then yes - it’s game over and you need to start a new game . The controller will be reset to factory default - you will have to re-include all devices again - I don’t think there’s any way around it other than to go through each device one by one.
Deleted all things using “smarthome:things remove zwave:device:RaZberry:node*” in Karaf
Deleted all network_XXX_node*.xml
Restarted ZWave 20180707 bundle
Started adding a device, why is it not starting at 0?
First device I added got this ID: Z-Wave Node 103
Did it not reset completely?
Edit:
It’s not only the “Thing naming”, even the logs states NODE 103 as well…
Getting dangerously close to 255 if I am to re-include them all again
I empathized with you! At least your network will be nice and clean! I suggest looking into your item files (if you use them), or the /userdata/jsondb/org.eclipse.smarthome.core.thing.Thing.json file to get your node numbers for your devices, and include them in the same order… or you will be editing all of the items with the new nodes. You should be able to use the same network name when creating the controller Thing, so you might get through it without having to modify any files.
If you’re using an Aeon Labs gen 5 zstick, there is a backup tool that could restore your network, if you had a backup. I use it with my HUSBZB-1, so it might work with other types of controllers too.
A new feature was added to ESH, and then the binding to detect devices on USB. Since you added the controller manually, it is detected again. Just ignore it and use the correct controller - or delete the old controller and use the new one.
It seems alot has changed as all my devices have lost their linkages…There used to be a very long number and then the node number, now its just - zwave:device:512:node5
Chris, do you see any drawback to me using Z-Way server to include all devices instead of Habmin? I will just have to make sure to use the same Network Key.
sorry, not sure what you mean by attaching to the log ticket. The full zwave log is here - the troublesome node is node 29. It’s a wired FGS222 double relay, close to multiple nodes and so it really shouldn’t be offline… but it is!
doesn’t seem to help. here’s another log. This time I have offline nodes 17 and 39 (smart switches), 29 (double relay), 4, 30, 31 and 36 (heatit thermostats) and 55 (binary sensor).
I don’t suppose you could post a link to a version of the binding from before you changed the offline logic?