2019-01-29 22:07:43.699 [INFO ] [arthome.ui.paper.internal.PaperUIApp] - Started Paper UI at /paperui
2019-01-29 22:07:54.149 [WARN ] [wave.discovery.ZWaveDiscoveryService] - NODE 2: Device discovery could not resolve to a thingType! 0154:0004:0002::1.4
2019-01-29 22:07:54.196 [INFO ] [g.discovery.internal.PersistentInbox] - Added new thing 'zwave:device:79c57bc7:node2' to inbox.
Thanks for the answer. The device is being discovered properly according to the log entry but not recognised properly by OpenHab2.
2019-01-29 22:07:54.149 [WARN ] [wave.discovery.ZWaveDiscoveryService] - NODE 2: Device discovery could not resolve to a thingType! 0154:0004:0002::1.4
2019-01-29 22:07:54.196 [INFO ] [g.discovery.internal.PersistentInbox] - Added new thing 'zwave:device:79c57bc7:node2' to inbox.
Yes, good catch.
Please check the command classes, association groups and config parameters. If they are the same as the existing device we need to change the max version, if those are different we need to add a new device (then please provide the xml file from your userdata/zwave folder).
To be honest, I have no idea why the change to max firmware=1.2 was made in the database.
As your device was working okay in 2.3 I changed the max version to 1.4 now, it is very unlikely that we need a separate database entry for that firmware version.
You need to upgrade to the latest 2.5 zwave snapshot once the database changes got merged into the binding.
What version of the binding are you using? What device type/id and version are shown in the properties in PaperUI? If it’s not showing this, then please wake up the device so it can complete discovery.
thanks for the fast reply.
I just created an ticket due it’s seems I’m not allow to add new devices.
Here’s the paperUI Output:
Z-Wave Node 023
Unknown Device
This device has not been fully discovered by the binding. There are a few possible reasons for this -:
The device is not in the database. If the device attributes show that this device has a valid manufacturer ID, device ID and type, then this is likely the case (eg. you see a label like " Z-Wave node 1 (0082:6015:020D::2.0) "). Even if the device appears to be in the database, some manufacturers use multiple sets of references for different regions or versions, and your device references may not be in the database. In either case, the database must be updated and you should raise an issue to get this addressed.
The device initialisation is not complete. Once the device is included into the network, the binding must interrogate it to find out what type of device it is. One part of this process is to get the manufacturer information required to identify the device, and until this is done, the device will remain unknown. For mains powered devices, this will occur quickly, however for battery devices the device must be woken up a number of times to allow the discovery phase to complete. This must be performed with the device close to the controller.
Sounds perfect but where can i get that latest binding? Is there a general approach to get those from an standardized url? I only find older or dead links here in the forum.
It would be great if you can publish the link to the snapshot here… (those update script do not match to my raspbian + zwave installation and the execution of backup and update with the openhab account does run into restriction errors)
Hi, I tested the org.openhab.binding.zwave-2.5.2-SNAPSHOT build #16 today but the popp siren is still not included successfully.
NODE 24: Device discovery could not resolve to a thingType! 0154:0004:0002::2.6
This text will be hidden
Z-Wave Node 025 (0154:0004:0002:2.6)
Unknown Device
This device has not been fully discovered by the binding. There are a few possible reasons for this -:
The device is not in the database. If the device attributes show that this device has a valid manufacturer ID, device ID and type, then this is likely the case (eg. you see a label like " Z-Wave node 1 (0082:6015:020D::2.0) "). Even if the device appears to be in the database, some manufacturers use multiple sets of references for different regions or versions, and your device references may not be in the database. In either case, the database must be updated and you should raise an issue to get this addressed.
The device initialisation is not complete. Once the device is included into the network, the binding must interrogate it to find out what type of device it is. One part of this process is to get the manufacturer information required to identify the device, and until this is done, the device will remain unknown. For mains powered devices, this will occur quickly, however for battery devices the device must be woken up a number of times to allow the discovery phase to complete. This must be performed with the device close to the controller.