OH 3.0 unknown Z-Wave devices

After installing openhabian with OH 3.0 all z-wave devices appear as unknown.
Uninstalled z-wave binding and installed it again - no luck.
All devices worked fine with OH 2.5.

Anyone same issue?

Welcome

Did you manually discover your controller?
Did you follow the binding documentation for when things so not do as planned and post DEBUG logs?

The binding database for the last OH2 version & the OH3 version are from the same source.

Hi Bruce,
Thank you for your support.

Yesterday after about 1h one out of 10 devices appeared correctly within OH3. All other remain unknown. Correct i manually discovered the controller and ran multiple scans of the zwave network to get the other devices in. But they are only listed as “Z-Wave Node 00…” without manufacturer or device type. Enabled debug log of zwave and saw the following:

2020-12-22 07:56:27.990 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Received msg: ACK
2020-12-22 07:56:27.992 [DEBUG] [nal.protocol.ZWaveTransactionManager] - ZWaveReceiveThread queue empty
2020-12-22 07:56:27.993 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction SendNextMessage 1 out at start. Holdoff false.
2020-12-22 07:56:29.014 [DEBUG] [wave.discovery.ZWaveDiscoveryService] - NODE 2: Device discovery completed
2020-12-22 07:56:29.019 [WARN ] [mmon.WrappedScheduledExecutorService] - Scheduled runnable ended with an exception:
java.lang.NullPointerException: null
at org.openhab.binding.zwave.discovery.ZWaveDiscoveryService$1.run(ZWaveDiscoveryService.java:87) ~[?:?]
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515) ~[?:?]
at java.util.concurrent.FutureTask.run(FutureTask.java:264) ~[?:?]
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:304) ~[?:?]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128) [?:?]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628) [?:?]
at java.lang.Thread.run(Thread.java:834) [?:?]
2020-12-22 07:56:29.037 [WARN ] [wave.discovery.ZWaveDiscoveryService] - NODE 2: Device discovery could not resolve to a thingType! Manufacturer data not known.
2020-12-22 07:56:29.043 [DEBUG] [wave.discovery.ZWaveDiscoveryService] - NODE 3: Device discovery completed
2020-12-22 07:56:29.062 [WARN ] [wave.discovery.ZWaveDiscoveryService] - NODE 3: Device discovery could not resolve to a thingType! Manufacturer data not known.
2020-12-22 07:56:29.067 [DEBUG] [wave.discovery.ZWaveDiscoveryService] - NODE 4: Device discovery completed
2020-12-22 07:56:29.153 [WARN ] [wave.discovery.ZWaveDiscoveryService] - NODE 4: Device discovery could not resolve to a thingType! Manufacturer data not known.
2020-12-22 07:56:29.164 [DEBUG] [wave.discovery.ZWaveDiscoveryService] - NODE 5: Device discovery completed
2020-12-22 07:56:29.172 [WARN ] [wave.discovery.ZWaveDiscoveryService] - NODE 5: Device discovery could not resolve to a thingType! Manufacturer data not known.
2020-12-22 07:56:29.179 [DEBUG] [wave.discovery.ZWaveDiscoveryService] - NODE 6: Device discovery completed
2020-12-22 07:56:29.188 [WARN ] [wave.discovery.ZWaveDiscoveryService] - NODE 6: Device discovery could not resolve to a thingType! Manufacturer data not known.
2020-12-22 07:56:29.192 [DEBUG] [wave.discovery.ZWaveDiscoveryService] - NODE 7: Device discovery completed
2020-12-22 07:56:29.201 [WARN ] [wave.discovery.ZWaveDiscoveryService] - NODE 7: Device discovery could not resolve to a thingType! Manufacturer data not known.
2020-12-22 07:56:29.205 [DEBUG] [wave.discovery.ZWaveDiscoveryService] - NODE 9: Device discovery completed
2020-12-22 07:56:29.213 [WARN ] [wave.discovery.ZWaveDiscoveryService] - NODE 9: Device discovery could not resolve to a thingType! Manufacturer data not known.
2020-12-22 07:56:29.218 [DEBUG] [wave.discovery.ZWaveDiscoveryService] - NODE 10: Device discovery completed
2020-12-22 07:56:29.225 [DEBUG] [wave.discovery.ZWaveDiscoveryService] - NODE 10: Device discovery resolved to thingType zwave:shenzhen_powerplug_00_000
2020-12-22 07:56:29.305 [DEBUG] [wave.discovery.ZWaveDiscoveryService] - ZWave discovery: Stop zwave:serial_zstick:51d9658653
2020-12-22 07:56:29.308 [DEBUG] [al.protocol.ZWaveInclusionController] - ZWave controller stopping inclusion at IncludeStart
2020-12-22 07:56:29.310 [DEBUG] [ol.serialmessage.AddNodeMessageClass] - Ending INCLUSION mode.

The identity of the devices is not known -:

Probably these are battery devices, or maybe some other communication issue is preventing the binding finding this information. If it’s a battery device, you should wake the device up so it can be discovered.

1 Like

After waiting almost 30 hours all devices are now appearing as known devices incl. manufacturer id etc.
Seems the issue has been solved by just waiting.

Thanks for your help!

1 Like

Yep - that’s the other alternative to waking the devices or copying the cache files :slight_smile: . If you wait long enough, the devices will wake up by themselves so the binding will be able to reinitialise them.

1 Like

This topic was automatically closed 41 days after the last reply. New replies are no longer allowed.