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!
This comes from the controller - so it depends on the UID that you gave the controller. In this case, it seems you set it to 512?
No - this should be fine so long as you transfer the network key correctly. Otherwise secure devices won’t work securely.
What is node 23?
Cool - may the force be with me.
it’s an Aeon Labs ZW096 Smart Switch 6 - wired, of course. Seems to be behaving…
Is there an association configured between these devices? The binding is trying to set a route between them…
how weird - that’s the coffee grinder and the entryphone, so would make a pretty peculiar bit of automation.
I’ve used habmin to set the associations to the zwave controller only - I’ll see if that makes a difference
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?
My log shows some warnings:
2018-07-14 21:33:08.622 [WARN ] [ve.internal.protocol.ZWaveController] - NODE 4: Restore from config: Error. Data invalid, ignoring config. 2018-07-14 21:33:08.639 [WARN ] [ve.internal.protocol.ZWaveController] - NODE 24: Restore from config: Error. Data invalid, ignoring config. 2018-07-14 21:33:08.642 [WARN ] [ve.internal.protocol.ZWaveController] - NODE 35: Restore from config: Error. Data invalid, ignoring config. 2018-07-14 21:33:14.168 [WARN ] [ding.zwave.handler.ZWaveThingHandler] - NODE 33: Invalid item type defined (DecimalType). Assuming DecimalType 2018-07-14 21:33:14.368 [WARN ] [ding.zwave.handler.ZWaveThingHandler] - NODE 43: Invalid item type defined (DecimalType). Assuming DecimalType 2018-07-14 21:33:14.704 [WARN ] [ding.zwave.handler.ZWaveThingHandler] - NODE 34: Invalid item type defined (DecimalType). Assuming DecimalType
For the first three messages it’s unclear for me what config the binding is talking about. Is it node.xml or something else? Maybe good point to add to the message what config it is related to.
About the last three warnings i suppose a DecimalType was expected and a DecimalType is supplied ? So this is wrong? I really don’t know how to read this.
node 33 and 34 are Coolcam PIR motion sensors (with lux sensor) and the channel is bound to a number item. The value does show up right on basicUI.
MySQL specific sensors don't persist their value's
What you’re seeing looks to be related to this…
It means that the initialisation is incomplete. I will remove this as it’s not something the user needs to worry about.
There will be an update tomorrow to fix this.
Cool, will update and provide feedback if needed.
About the initialisation. The nodes are battery devices and are connected for several days, shouldn’t the initialisation be done allready? Or is this done every time after a openhab restart?
Edit: Another question, if persistence is setup should the channel value be persisted after polling?
Would there be any benefit for me to also include a Vera Plus as a secondary controller now that I’m re-including my network - or would it only mess things up?
Normally, yes - so long as the wakeup interval is set. The binding should set this when the device is first initialised, and after this the device should wake at the wakeup interval you have set in the controller (I think it defaults to once per hour).
There is an “initialisation” every time the binding starts, but assuming the initialisation was previously completed, then it should be short. When the binding first initialises a device, it reads all the service information, and configures a load of stuff. After that, it stores it in the XML files, and reloads this on startup. Then it just reads data it considers is dynamic on startup (this is stuff like temperature, switch state etc) so that it can update the GUI.
Up to you really - I’m not sure there is a lot of benefit unless you are using your Vera for some reason still? It shouldn’t mess things up (too much!), but it is worth noting that some features in ZWave will only work with one controller, so the Vera may reconfigure some settings when may stop OH being able to make configuration changes.
I’ll skip extra controller
Use Z-Way (I’m running Z-Wave.me RaZberry board on rpi) to include all devices.
Copy the security key to OpenHAB.
and add all things, wait like 24h for initialisation and hope for a working system again!
Is there any way with OpenHAB Z-Wave Binding to do a network backup to avoid this happening again?
Thanks for all your support!