Hey all, last weekend up upgraded to 2.4 Release version from 2.3.
a week later i still have 3 devices showing as ‘unknown’ in Habmin, and 1 showing as ‘node not communicating with controller’
Unknown devices are node numbers 23, 25, 26, with the not communicating node 24. coincidence that the 4 nodes are sequential?
my openhab.log is here https://www.dropbox.com/s/silsopp8epvxt1v/openhab.log?dl=0
if anyone could take a look please
The upgrade path i took was to install a fresh version of 2.4, not an actual upgrade of code - apologies for not making that clear. this evening i have removed and readded all z-wave things - now i have another couple of additional unknown nodes.
What I am seeing is:
2019-01-26 10:25:24.129 [WARN ] [ve.internal.protocol.ZWaveController] - NODE 23: Restore from config: Error. Data invalid, ignoring config.
Means openHAB cannot read your zwave xml files anymore.
This could be a bad storage medium. It’s only a warning but I would try to find out why. It could also be a permission issue.
Next thing i see: while setting a parameter you get huge timeouts for node 24. Node too far away from the controller?
Node 25 and node 26 do not exist at all in your log, maybe some ghost nodes from failed inclusion attempts?
Does the zwave binding not recreate the XML files if there is a problem with them? Maybe I should remove the node 23 and delete the XML file? Nodes 23 & 24 are next to each other in the shed at the bottom of the garden and have been for a coupe of years now
The xml files are recreated is something changes. For example during a nightly heal.
If you are talking about excluding and reincluding: no, this is normally not necessary and should be the very last step.
I first would do a soft reset of the controller: shutdown your openHAB server, disconnect power (or remove the controller physically), reconnect power, start openHAB.
Next step would be to reiniaialize the device in question (you need to switch to advanced settings in HABmin). This also recreates the xml files.
If those are battery devices, wake them up manually, this may have to be done several times.