POPP Solar Siren not recognized after upgrading from OH 2.3

zwave
Tags: #<Tag:0x00007f51efc765f8>

(Ricardo) #1

Details

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.

Thank you.


(SiHui) #2

You need to wake the device, push the wake up button.

Good idea, stick with that because it includes the latest database changes.


(Ricardo) #3

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.

cd-jakson database entry matches the discovered device.

<properties>
      <property name="vendor">Popp &amp; Co</property>
      <property name="modelId">005107</property>
      <property name="manufacturerId">0154</property>
      <property name="manufacturerRef">0004:0002</property>
      <property name="versionMin">1.1</property>
      <property name="versionMax">1.2</property>

Could this be related to the version min/max? Device version seems to be 1.4.


(SiHui) #4

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).


(Thomas Pietrowski) #5

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!


(SiHui) #6

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.


(Dr. D.) #7

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.


(SiHui) #8

The change I made has not made it into the binding yet:

Wait a couple of days and upgrade to the latest snapshot binding.