Hey @sihui,
can you tell me how I shall compare the XML and https://www.cd-jackson.com/index.php/zwave/zwave-device-database/zwave-device-list/devicesummary/367 ?
Got a v1.4 device, too, which worked well in 2.3, but after upgrade settings have been dropped and it is undiscovered now.
Thanks!
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.
Same here: Upgrading to OH2.5-snapshot -> formerly known Popp outdoor siren is marked as “unknown device”.
OH Log:
2019-03-15 10:02:38.264 [WARN ] [nal.protocol.ZWaveTransactionManager] - NODE 2: Not initialized (ie node unknown), ignoring message.
2019-03-15 10:02:40.089 [WARN ] [core.thing.internal.ThingManagerImpl] - Initializing handler for thing ‘zwave:device:22bfd1f4:node2’ takes more than 5000ms.
2019-03-15 10:02:41.096 [WARN ] [wave.discovery.ZWaveDiscoveryService] - NODE 2: Device discovery could not resolve to a thingType! 0154:0004:0002::1.4
What can I do?
Thanks.
The change I made has not made it into the binding yet:
https://github.com/openhab/org.openhab.binding.zwave/tree/master/ESH-INF/thing/popp
Wait a couple of days and upgrade to the latest snapshot binding.
Hi guys,
i’m on newest Openhab version but its still not recognizing the siren…
Any news or workarounds available?
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.
Oh Hi chris,
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.
Status: ONLINE
HIDE PROPERTIES
zwave_beaming true zwave_class_basic BASIC_TYPE_ROUTING_SLAVE zwave_class_generic GENERIC_TYPE_SWITCH_BINARY zwave_class_specific SPECIFIC_TYPE_SIREN zwave_deviceid 2 zwave_devicetype 4 zwave_frequent true zwave_listening false zwave_manufacturer 340 zwave_neighbours zwave_nodeid 23 zwave_plus_devicetype NODE_TYPE_ZWAVEPLUS_NODE zwave_plus_roletype ROLE_TYPE_SLAVE_SLEEPING_LISTENING zwave_routing true zwave_secure false zwave_version 2.6
Binding Version is
20 │ Active │ 80 │ 2.5.1.201912300340 │ openHAB Add-ons :: Bundles :: ZWave Binding
You don’t need to, your device is here, we had to adjust the firmware versions in the database entry:
https://www.cd-jackson.com/index.php/zwave/zwave-device-database/zwave-device-list/devicesummary/960
After the changes got merged please upgrade to the latest zwave snapshot binding.
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 will likely be after the weekend before a snapshot binding is available with those changes. The easiest is usually using the update script.
Zigbee and Z-Wave manual install script - Tutorials & Examples - openHAB Community
When were the changes made? I did do an update last night (merged this morning) - next will be at the weekend.
The database says the change was 11 hours ago.
Ok, then it will be the weekend unfortunately - sorry.
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 -:
Status: ONLINE
HIDE PROPERTIES
| zwave_beaming | true |
|---|---|
| zwave_class_basic | BASIC_TYPE_ROUTING_SLAVE |
| zwave_class_generic | GENERIC_TYPE_SWITCH_BINARY |
| zwave_class_specific | SPECIFIC_TYPE_SIREN |
| zwave_deviceid | 2 |
| zwave_devicetype | 4 |
| zwave_frequent | true |
| zwave_listening | false |
| zwave_manufacturer | 340 |
| zwave_neighbours | |
| zwave_nodeid | 25 |
| zwave_plus_devicetype | NODE_TYPE_ZWAVEPLUS_NODE |
| zwave_plus_roletype | ROLE_TYPE_SLAVE_SLEEPING_LISTENING |
| zwave_routing | true |
| zwave_secure | false |
| zwave_version | 2.6 |
<node>
<homeId>0xdc60617a</homeId>
<nodeId>25</nodeId>
<version>4</version>
<manufacturer>0x154</manufacturer>
<deviceId>0x2</deviceId>
<deviceType>0x4</deviceType>
<listening>false</listening>
<frequentlyListening>true</frequentlyListening>
<routing>true</routing>
<security>false</security>
<beaming>true</beaming>
<maxBaudRate>40000</maxBaudRate>
<sleepDelay>1000</sleepDelay>
<nodeInformationFrame>
<commandClass>COMMAND_CLASS_ZWAVEPLUS_INFO</commandClass>
<commandClass>COMMAND_CLASS_ASSOCIATION</commandClass>
<commandClass>COMMAND_CLASS_MULTI_CHANNEL_ASSOCIATION</commandClass>
<commandClass>COMMAND_CLASS_ASSOCIATION_GRP_INFO</commandClass>
<commandClass>COMMAND_CLASS_TRANSPORT_SERVICE</commandClass>
<commandClass>COMMAND_CLASS_VERSION</commandClass>
<commandClass>COMMAND_CLASS_MANUFACTURER_SPECIFIC</commandClass>
<commandClass>COMMAND_CLASS_DEVICE_RESET_LOCALLY</commandClass>
<commandClass>COMMAND_CLASS_POWERLEVEL</commandClass>
<commandClass>COMMAND_CLASS_SECURITY</commandClass>
<commandClass>COMMAND_CLASS_SWITCH_BINARY</commandClass>
<commandClass>COMMAND_CLASS_CONFIGURATION</commandClass>
<commandClass>COMMAND_CLASS_BATTERY</commandClass>
<commandClass>COMMAND_CLASS_SENSOR_BINARY</commandClass>
<commandClass>COMMAND_CLASS_ALARM</commandClass>
<commandClass>COMMAND_CLASS_SUPERVISION</commandClass>
<commandClass>COMMAND_CLASS_FIRMWARE_UPDATE_MD</commandClass>
</nodeInformationFrame>
<associationGroups class="concurrent-hash-map">
<entry>
<int>1</int>
<associationGroup>
<index>1</index>
<maxNodes>0</maxNodes>
<associations/>
</associationGroup>
</entry>
</associationGroups>
<endpoints class="concurrent-hash-map">
<entry>
<int>0</int>
<endPoint>
<deviceClass>
<basicDeviceClass>BASIC_TYPE_ROUTING_SLAVE</basicDeviceClass>
<genericDeviceClass>GENERIC_TYPE_SWITCH_BINARY</genericDeviceClass>
<specificDeviceClass>SPECIFIC_TYPE_SIREN</specificDeviceClass>
</deviceClass>
<endpointId>0</endpointId>
<secureCommandClasses/>
<supportedCommandClasses class="concurrent-hash-map">
<entry>
<commandClass>COMMAND_CLASS_POWERLEVEL</commandClass>
<COMMAND__CLASS__POWERLEVEL>
<version>1</version>
<instances>1</instances>
<control>false</control>
<versionSupported>1</versionSupported>
<powerLevel>0</powerLevel>
<powerTimeout>0</powerTimeout>
</COMMAND__CLASS__POWERLEVEL>
</entry>
<entry>
<commandClass>COMMAND_CLASS_MULTI_CHANNEL_ASSOCIATION</commandClass>
<COMMAND__CLASS__MULTI__CHANNEL__ASSOCIATION>
<version>3</version>
<instances>1</instances>
<control>false</control>
<versionSupported>3</versionSupported>
<maxGroups>1</maxGroups>
</COMMAND__CLASS__MULTI__CHANNEL__ASSOCIATION>
</entry>
<entry>
<commandClass>COMMAND_CLASS_DEVICE_RESET_LOCALLY</commandClass>
<COMMAND__CLASS__DEVICE__RESET__LOCALLY>
<version>1</version>
<instances>1</instances>
<control>false</control>
<versionSupported>1</versionSupported>
</COMMAND__CLASS__DEVICE__RESET__LOCALLY>
</entry>
<entry>
<commandClass>COMMAND_CLASS_BATTERY</commandClass>
<COMMAND__CLASS__BATTERY>
<version>1</version>
<instances>1</instances>
<control>false</control>
<versionSupported>1</versionSupported>
<batteryLevel>0</batteryLevel>
<batteryLow>true</batteryLow>
<isGetSupported>true</isGetSupported>
</COMMAND__CLASS__BATTERY>
</entry>
<entry>
<commandClass>COMMAND_CLASS_VERSION</commandClass>
<COMMAND__CLASS__VERSION>
<version>2</version>
<instances>1</instances>
<control>false</control>
<versionSupported>3</versionSupported>
<libraryType>LIB_SLAVE_ENHANCED</libraryType>
<protocolVersion>6.2</protocolVersion>
<applicationVersion>2.6</applicationVersion>
<hardwareVersion>1</hardwareVersion>
</COMMAND__CLASS__VERSION>
</entry>
<entry>
<commandClass>COMMAND_CLASS_CONFIGURATION</commandClass>
<COMMAND__CLASS__CONFIGURATION>
<version>1</version>
<instances>1</instances>
<control>false</control>
<versionSupported>1</versionSupported>
<configParameters/>
</COMMAND__CLASS__CONFIGURATION>
</entry>
<entry>
<commandClass>COMMAND_CLASS_ZWAVEPLUS_INFO</commandClass>
<COMMAND__CLASS__ZWAVEPLUS__INFO>
<version>1</version>
<instances>1</instances>
<control>false</control>
<versionSupported>2</versionSupported>
<zwPlusVersion>1</zwPlusVersion>
<zwPlusRole>ROLE_TYPE_SLAVE_SLEEPING_LISTENING</zwPlusRole>
<zwPlusNodeType>NODE_TYPE_ZWAVEPLUS_NODE</zwPlusNodeType>
<isGetSupported>true</isGetSupported>
</COMMAND__CLASS__ZWAVEPLUS__INFO>
</entry>
<entry>
<commandClass>COMMAND_CLASS_MANUFACTURER_SPECIFIC</commandClass>
<COMMAND__CLASS__MANUFACTURER__SPECIFIC>
<version>1</version>
<instances>1</instances>
<control>false</control>
<versionSupported>2</versionSupported>
<initSerialNumber>false</initSerialNumber>
<deviceManufacturer>340</deviceManufacturer>
<deviceType>4</deviceType>
<deviceId>2</deviceId>
</COMMAND__CLASS__MANUFACTURER__SPECIFIC>
</entry>
<entry>
<commandClass>COMMAND_CLASS_SENSOR_BINARY</commandClass>
<COMMAND__CLASS__SENSOR__BINARY>
<version>2</version>
<instances>1</instances>
<control>false</control>
<versionSupported>2</versionSupported>
<isGetSupported>true</isGetSupported>
<types>
<binarySensorType>TAMPER</binarySensorType>
</types>
</COMMAND__CLASS__SENSOR__BINARY>
</entry>
<entry>
<commandClass>COMMAND_CLASS_FIRMWARE_UPDATE_MD</commandClass>
<COMMAND__CLASS__FIRMWARE__UPDATE__MD>
<version>1</version>
<instances>1</instances>
<control>false</control>
<versionSupported>4</versionSupported>
</COMMAND__CLASS__FIRMWARE__UPDATE__MD>
</entry>
<entry>
<commandClass>COMMAND_CLASS_ASSOCIATION_GRP_INFO</commandClass>
<COMMAND__CLASS__ASSOCIATION__GRP__INFO>
<version>1</version>
<instances>1</instances>
<control>false</control>
<versionSupported>1</versionSupported>
<autoSubscribeGroups/>
</COMMAND__CLASS__ASSOCIATION__GRP__INFO>
</entry>
<entry>
<commandClass>COMMAND_CLASS_ALARM</commandClass>
<COMMAND__CLASS__ALARM>
<version>8</version>
<instances>1</instances>
<control>false</control>
<versionSupported>8</versionSupported>
<alarms>
<entry>
<alarmType>BURGLAR</alarmType>
<alarmState>
<alarmType>BURGLAR</alarmType>
<reportedEvents/>
<outer-class reference="../../../.."/>
</alarmState>
</entry>
</alarms>
<v1Supported>true</v1Supported>
<isGetSupported>true</isGetSupported>
</COMMAND__CLASS__ALARM>
</entry>
<entry>
<commandClass>COMMAND_CLASS_NO_OPERATION</commandClass>
<COMMAND__CLASS__NO__OPERATION>
<version>1</version>
<instances>1</instances>
<control>false</control>
<versionSupported>1</versionSupported>
</COMMAND__CLASS__NO__OPERATION>
</entry>
<entry>
<commandClass>COMMAND_CLASS_SWITCH_BINARY</commandClass>
<COMMAND__CLASS__SWITCH__BINARY>
<version>1</version>
<instances>1</instances>
<control>false</control>
<versionSupported>1</versionSupported>
<isGetSupported>true</isGetSupported>
</COMMAND__CLASS__SWITCH__BINARY>
</entry>
<entry>
<commandClass>COMMAND_CLASS_BASIC</commandClass>
<COMMAND__CLASS__BASIC>
<version>1</version>
<instances>1</instances>
<control>false</control>
<versionSupported>1</versionSupported>
<isGetSupported>true</isGetSupported>
</COMMAND__CLASS__BASIC>
</entry>
<entry>
<commandClass>COMMAND_CLASS_SECURITY</commandClass>
<COMMAND__CLASS__SECURITY>
<version>1</version>
<instances>1</instances>
<control>false</control>
<versionSupported>1</versionSupported>
</COMMAND__CLASS__SECURITY>
</entry>
<entry>
<commandClass>COMMAND_CLASS_ASSOCIATION</commandClass>
<COMMAND__CLASS__ASSOCIATION>
<version>2</version>
<instances>1</instances>
<control>false</control>
<versionSupported>2</versionSupported>
<maxGroups>1</maxGroups>
</COMMAND__CLASS__ASSOCIATION>
</entry>
</supportedCommandClasses>
</endPoint>
</entry>
</endpoints>
<nodeNeighbors/>
<lastReceived>2020-02-08 13:07:23.214 UTC</lastReceived>
</node>
The binding has not been updated since the changes have been made. As I said a couple of days back, I will do another update this weekend.
It’s not enough to be “SaperAude” you also need to be “alqm patienter ferre” 
He he, Sorry and thanks a lot!
It’s solved! Thanks a lot!