Upgrade to 2.4 all Z-Wave Node status: UNINITIALIZED - HANDLER_CONFIGURATION_PENDING

[micware (Michiel)]

Hi

• Platform information:

  • Hardware: Intel NUC / Aeon Gen 5 Zwave USB stick
  • OS: Ubuntu 18.04
  • Java Runtime Environment: openjdk version “1.8.0_191”
  • openHAB version: 2.4

• Issue of the topic:
  I Upgraded to 2.4 via apt and now all Z-Wave Node have status: UNINITIALIZED - HANDLER_CONFIGURATION_PENDING

• Cleared cache,

• restarted OpenHAB a few times, no luck

• I see my “Z-Wave Serial Controller” is still online

• If logs where generated please post these here using code fences:

openhab.log

2018-12-23 20:18:57.845 [WARN ] [nal.protocol.ZWaveTransactionManager] - NODE 14: Not initialized (ie node unknown), ignoring message.
2018-12-23 20:18:57.845 [WARN ] [nal.protocol.ZWaveTransactionManager] - NODE 14: Not initialized (ie node unknown), ignoring message.
2018-12-23 20:18:57.846 [WARN ] [nal.protocol.ZWaveTransactionManager] - NODE 14: Not initialized (ie node unknown), ignoring message.
2018-12-23 20:18:57.846 [WARN ] [nal.protocol.ZWaveTransactionManager] - NODE 14: Not initialized (ie node unknown), ignoring message.
2018-12-23 20:18:57.847 [WARN ] [nal.protocol.ZWaveTransactionManager] - NODE 14: Not initialized (ie node unknown), ignoring message.
2018-12-23 20:18:57.847 [WARN ] [nal.protocol.ZWaveTransactionManager] - NODE 14: Not initialized (ie node unknown), ignoring message.
2018-12-23 20:19:01.447 [WARN ] [ve.internal.protocol.ZWaveController] - NODE 2: Restore from config: Error. Data invalid, ignoring config.
2018-12-23 20:35:48.418 [WARN ] [wave.discovery.ZWaveDiscoveryService] - NODE 2: Device discovery could not resolve to a thingType! Manufacturer data not known.

events.log

2018-12-23 20:18:57.167 [hingStatusInfoChangedEvent] - 'zwave:device:9a9b7927:node9' changed from UNINITIALIZED to UNINITIALIZED (BRIDGE_UNINITIALIZED)
2018-12-23 20:18:57.174 [hingStatusInfoChangedEvent] - 'zwave:device:9a9b7927:node8' changed from UNINITIALIZED to UNINITIALIZED (BRIDGE_UNINITIALIZED)
2018-12-23 20:18:57.175 [hingStatusInfoChangedEvent] - 'astro:moon:home' changed from UNINITIALIZED to INITIALIZING
2018-12-23 20:18:57.186 [hingStatusInfoChangedEvent] - 'astro:moon:home' changed from INITIALIZING to ONLINE
2018-12-23 20:18:57.302 [hingStatusInfoChangedEvent] - 'zwave:serial_zstick:9a9b7927' changed from UNINITIALIZED to INITIALIZING
2018-12-23 20:18:57.698 [hingStatusInfoChangedEvent] - 'zwave:serial_zstick:9a9b7927' changed from INITIALIZING to OFFLINE (BRIDGE_OFFLINE): Controller is offline
2018-12-23 20:18:57.699 [hingStatusInfoChangedEvent] - 'zwave:device:9a9b7927:node7' changed from UNINITIALIZED to UNINITIALIZED (HANDLER_CONFIGURATION_PENDING)
2018-12-23 20:18:57.700 [hingStatusInfoChangedEvent] - 'zwave:device:9a9b7927:node4' changed from UNINITIALIZED to UNINITIALIZED (HANDLER_CONFIGURATION_PENDING)
2018-12-23 20:18:57.701 [hingStatusInfoChangedEvent] - 'zwave:device:9a9b7927:node5' changed from UNINITIALIZED to UNINITIALIZED (HANDLER_CONFIGURATION_PENDING)
2018-12-23 20:18:57.701 [hingStatusInfoChangedEvent] - 'zwave:device:9a9b7927:node3' changed from UNINITIALIZED to UNINITIALIZED (HANDLER_CONFIGURATION_PENDING)
2018-12-23 20:18:57.702 [hingStatusInfoChangedEvent] - 'zwave:device:9a9b7927:node6' changed from UNINITIALIZED to UNINITIALIZED (HANDLER_CONFIGURATION_PENDING)
2018-12-23 20:18:57.703 [hingStatusInfoChangedEvent] - 'zwave:device:9a9b7927:node9' changed from UNINITIALIZED (BRIDGE_UNINITIALIZED) to UNINITIALIZED (HANDLER_CONFIGURATION_PENDING)
2018-12-23 20:18:57.704 [hingStatusInfoChangedEvent] - 'zwave:device:9a9b7927:node13' changed from UNINITIALIZED to UNINITIALIZED (HANDLER_CONFIGURATION_PENDING)
2018-12-23 20:18:57.704 [hingStatusInfoChangedEvent] - 'zwave:device:9a9b7927:node11' changed from UNINITIALIZED to UNINITIALIZED (HANDLER_CONFIGURATION_PENDING)
2018-12-23 20:18:57.761 [hingStatusInfoChangedEvent] - 'zwave:device:9a9b7927:node14' changed from UNINITIALIZED to UNINITIALIZED (HANDLER_CONFIGURATION_PENDING)
2018-12-23 20:18:57.762 [hingStatusInfoChangedEvent] - 'zwave:device:9a9b7927:node10' changed from UNINITIALIZED to UNINITIALIZED (HANDLER_CONFIGURATION_PENDING)
2018-12-23 20:18:57.762 [hingStatusInfoChangedEvent] - 'zwave:device:9a9b7927:node12' changed from UNINITIALIZED to UNINITIALIZED (HANDLER_CONFIGURATION_PENDING)
2018-12-23 20:18:57.763 [hingStatusInfoChangedEvent] - 'zwave:device:9a9b7927:node8' changed from UNINITIALIZED (BRIDGE_UNINITIALIZED) to UNINITIALIZED (HANDLER_CONFIGURATION_PENDING)

someone wrote: For some reason the Zwave controller device ID changed, or got replaced. Meant that existing items no longer worked until I modified the .items file(s) to reflect the new ID.

Maybe this has something to do with it!!???

[vzorglub (Vincent Regaud)]

ZWave binding updates

I have now merged the development version of the ZWave binding into master, so it will be available in the 2.4 snapshot version. If you are using the ZWave binding, please read this post as the binding contains some breaking changes so you will need to manually update your configuration. Firstly though - the major enhancements (there are tons more smaller updates) -: Security has been added using the S0 security class. This should allow all devices supporting security to be included into the…

[micware (Michiel)]

Thanks for your answer. If i understand it correctly i have to remove and then add the z-wave thing again to openhab.
I willen try That