Z-wave warning after upgrade to OH2.2 - Device discovery could not resolve to a thingType! 010F:0302:1000::25.25

Add-ons Bindings
1

After upgrde to OH2.2 and z-wave snapshot 2.3 I get a lot of these warnings. Can I ignore this?

2017-12-29 12:40:38.604 [WARN ] [wave.discovery.ZWaveDiscoveryService] - NODE 33: Device discovery could not resolve to a thingType! 010F:0302:1000::25.25
2017-12-29 12:40:38.616 [WARN ] [wave.discovery.ZWaveDiscoveryService] - NODE 13: Device discovery could not resolve to a thingType! 0154:0004:0011::1.2
2017-12-29 12:40:38.630 [WARN ] [wave.discovery.ZWaveDiscoveryService] - NODE 58: Device discovery could not resolve to a thingType! 010F:0700:1000::2.5
2017-12-29 12:40:38.624 [WARN ] [wave.discovery.ZWaveDiscoveryService] - NODE 28: Device discovery could not resolve to a thingType! 010F:0701:1001::3.2
2017-12-29 12:40:38.638 [WARN ] [wave.discovery.ZWaveDiscoveryService] - NODE 9: Device discovery could not resolve to a thingType! 013C:0002:000C::1.24
2017-12-29 12:40:38.641 [WARN ] [wave.discovery.ZWaveDiscoveryService] - NODE 50: Device discovery could not resolve to a thingType! 010F:0701:1001::3.2
2017-12-29 12:40:38.647 [WARN ] [wave.discovery.ZWaveDiscoveryService] - NODE 42: Device discovery could not resolve to a thingType! 010F:0700:1000::2.5
2017-12-29 12:40:38.658 [WARN ] [wave.discovery.ZWaveDiscoveryService] - NODE 60: Device discovery could not resolve to a thingType! 010F:0900:1000::25.25
2

It means the device is not known. Probably your device is already detected and working, so it can be ignored so long as you don’t delete it!

I did a database resync a couple of days back and it looks like the version you have got missed - I’ve just re-approved it so it should be sorted in a day or two (when I do another database update).

3

Hi chris,

thanks for the reply. I got a lot of this messages, looks like all devices I use.

Before the update I use a very old snapshot binding 2.1.0. With the update I migrated to the newest snapshot binding 2.3 from yesterday.

I see in the past, that the files created unter \openhab2\userdata\zwave are named “node15.xml” (I have this before and after the update) and sometimes “network_c2e5fc3d__node_8.xml” depending on the used snapshot ot developing binding.

Do I mixed snapshot and developing binding usage now?
Is file naming “node15.xml” an indicator for developing binding?

4

So you mean not just the FGR222 but other devices as well? (really ALL devices?).

These are the old names - the development binding uses the names which start with network - this allows multiple controllers.

5

Sorry for confusing:

full log:

2017-12-29 12:40:38.604 [WARN ] [wave.discovery.ZWaveDiscoveryService] - NODE 33: Device discovery could not resolve to a thingType! 010F:0302:1000::25.25
2017-12-29 12:40:38.616 [WARN ] [wave.discovery.ZWaveDiscoveryService] - NODE 13: Device discovery could not resolve to a thingType! 0154:0004:0011::1.2
2017-12-29 12:40:38.630 [WARN ] [wave.discovery.ZWaveDiscoveryService] - NODE 58: Device discovery could not resolve to a thingType! 010F:0700:1000::2.5
2017-12-29 12:40:38.624 [WARN ] [wave.discovery.ZWaveDiscoveryService] - NODE 28: Device discovery could not resolve to a thingType! 010F:0701:1001::3.2
2017-12-29 12:40:38.638 [WARN ] [wave.discovery.ZWaveDiscoveryService] - NODE 9: Device discovery could not resolve to a thingType! 013C:0002:000C::1.24
2017-12-29 12:40:38.641 [WARN ] [wave.discovery.ZWaveDiscoveryService] - NODE 50: Device discovery could not resolve to a thingType! 010F:0701:1001::3.2
2017-12-29 12:40:38.647 [WARN ] [wave.discovery.ZWaveDiscoveryService] - NODE 42: Device discovery could not resolve to a thingType! 010F:0700:1000::2.5
2017-12-29 12:40:38.658 [WARN ] [wave.discovery.ZWaveDiscoveryService] - NODE 60: Device discovery could not resolve to a thingType! 010F:0900:1000::25.25
2017-12-29 12:40:38.672 [WARN ] [wave.discovery.ZWaveDiscoveryService] - NODE 16: Device discovery could not resolve to a thingType! 010F:0701:1001::3.2
2017-12-29 12:40:38.676 [WARN ] [wave.discovery.ZWaveDiscoveryService] - NODE 43: Device discovery could not resolve to a thingType! 010F:0700:1000::2.5
2017-12-29 12:40:38.680 [WARN ] [wave.discovery.ZWaveDiscoveryService] - NODE 31: Device discovery could not resolve to a thingType! 010F:0701:1001::3.2
2017-12-29 12:40:38.699 [WARN ] [wave.discovery.ZWaveDiscoveryService] - NODE 37: Device discovery could not resolve to a thingType! 010F:0701:1001::3.2
2017-12-29 12:40:38.702 [WARN ] [wave.discovery.ZWaveDiscoveryService] - NODE 6: Device discovery could not resolve to a thingType! 0109:2001:0106::5.1
2017-12-29 12:40:38.707 [WARN ] [wave.discovery.ZWaveDiscoveryService] - NODE 26: Device discovery could not resolve to a thingType! 0115:0100:0101::1.1
2017-12-29 12:40:38.706 [WARN ] [wave.discovery.ZWaveDiscoveryService] - NODE 4: Device discovery could not resolve to a thingType! 010F:0302:1000::25.25
2017-12-29 12:40:38.707 [WARN ] [wave.discovery.ZWaveDiscoveryService] - NODE 7: Device discovery could not resolve to a thingType! 010F:0701:1001::3.2
2017-12-29 12:40:38.709 [WARN ] [wave.discovery.ZWaveDiscoveryService] - NODE 36: Device discovery could not resolve to a thingType! 010F:0701:1001::3.2
2017-12-29 12:40:38.710 [WARN ] [wave.discovery.ZWaveDiscoveryService] - NODE 22: Device discovery could not resolve to a thingType! 010F:0701:1001::3.2
2017-12-29 12:40:38.713 [WARN ] [wave.discovery.ZWaveDiscoveryService] - NODE 53: Device discovery could not resolve to a thingType! 010F:0700:1000::2.5
2017-12-29 12:40:38.716 [WARN ] [wave.discovery.ZWaveDiscoveryService] - NODE 18: Device discovery could not resolve to a thingType! 010F:0701:1001::3.2
2017-12-29 12:40:38.719 [WARN ] [wave.discovery.ZWaveDiscoveryService] - NODE 15: Device discovery could not resolve to a thingType! 0109:2001:0106::5.1
2017-12-29 12:40:38.722 [WARN ] [wave.discovery.ZWaveDiscoveryService] - NODE 57: Device discovery could not resolve to a thingType! 010F:0700:1000::2.5
2017-12-29 12:40:38.730 [WARN ] [wave.discovery.ZWaveDiscoveryService] - NODE 35: Device discovery could not resolve to a thingType! 010F:0701:1001::3.2
2017-12-29 12:40:38.730 [WARN ] [wave.discovery.ZWaveDiscoveryService] - NODE 39: Device discovery could not resolve to a thingType! 010F:0700:1000::2.5
2017-12-29 12:40:38.754 [WARN ] [wave.discovery.ZWaveDiscoveryService] - NODE 14: Device discovery could not resolve to a thingType! 0109:2001:0106::5.1
2017-12-29 12:40:38.750 [WARN ] [wave.discovery.ZWaveDiscoveryService] - NODE 24: Device discovery could not resolve to a thingType! 010F:0700:1000::2.1
2017-12-29 12:40:38.772 [WARN ] [wave.discovery.ZWaveDiscoveryService] - NODE 44: Device discovery could not resolve to a thingType! 010F:0701:1001::3.2
2017-12-29 12:40:38.773 [WARN ] [wave.discovery.ZWaveDiscoveryService] - NODE 23: Device discovery could not resolve to a thingType! 0060:000B:0001::1.3
2017-12-29 12:40:38.748 [WARN ] [wave.discovery.ZWaveDiscoveryService] - NODE 48: Device discovery could not resolve to a thingType! 010F:0701:1001::3.2
2017-12-29 12:40:38.778 [WARN ] [wave.discovery.ZWaveDiscoveryService] - NODE 10: Device discovery could not resolve to a thingType! 010F:0701:1001::3.2
2017-12-29 12:40:38.748 [WARN ] [wave.discovery.ZWaveDiscoveryService] - NODE 30: Device discovery could not resolve to a thingType! 010F:0701:1001::3.2
2017-12-29 12:40:38.780 [WARN ] [wave.discovery.ZWaveDiscoveryService] - NODE 38: Device discovery could not resolve to a thingType! 010F:0700:1000::2.5
2017-12-29 12:40:38.784 [WARN ] [wave.discovery.ZWaveDiscoveryService] - NODE 56: Device discovery could not resolve to a thingType! 010F:0302:1000::25.25
2017-12-29 12:40:38.817 [WARN ] [wave.discovery.ZWaveDiscoveryService] - NODE 21: Device discovery could not resolve to a thingType! 010F:0302:1000::25.25
2017-12-29 12:40:38.747 [WARN ] [wave.discovery.ZWaveDiscoveryService] - NODE 2: Device discovery could not resolve to a thingType! 0108:0004:000A::1.8
2017-12-29 12:40:38.816 [WARN ] [wave.discovery.ZWaveDiscoveryService] - NODE 27: Device discovery could not resolve to a thingType! 010F:0701:1001::3.2
2017-12-29 12:40:38.821 [WARN ] [wave.discovery.ZWaveDiscoveryService] - NODE 17: Device discovery could not resolve to a thingType! 010F:0701:1001::3.2
2017-12-29 12:40:38.823 [WARN ] [wave.discovery.ZWaveDiscoveryService] - NODE 12: Device discovery could not resolve to a thingType! 010F:0701:1001::3.2
2017-12-29 12:40:38.810 [WARN ] [wave.discovery.ZWaveDiscoveryService] - NODE 3: Device discovery could not resolve to a thingType! 0086:0002:0070::1.2
2017-12-29 12:40:38.769 [WARN ] [wave.discovery.ZWaveDiscoveryService] - NODE 29: Device discovery could not resolve to a thingType! 010F:0701:1001::3.2
2017-12-29 12:40:38.831 [WARN ] [wave.discovery.ZWaveDiscoveryService] - NODE 45: Device discovery could not resolve to a thingType! 010F:0302:1000::25.25
2017-12-29 12:40:38.842 [WARN ] [wave.discovery.ZWaveDiscoveryService] - NODE 52: Device discovery could not resolve to a thingType! 010F:0700:1000::2.5
2017-12-29 12:40:38.845 [WARN ] [wave.discovery.ZWaveDiscoveryService] - NODE 59: Device discovery could not resolve to a thingType! 0086:0002:0070::1.1
2017-12-29 12:40:38.853 [WARN ] [wave.discovery.ZWaveDiscoveryService] - NODE 34: Device discovery could not resolve to a thingType! 010F:0302:1000::25.25
2017-12-29 12:40:38.853 [WARN ] [wave.discovery.ZWaveDiscoveryService] - NODE 51: Device discovery could not resolve to a thingType! 010F:0302:1000::25.25
2017-12-29 12:40:38.857 [WARN ] [wave.discovery.ZWaveDiscoveryService] - NODE 47: Device discovery could not resolve to a thingType! 010F:0302:1000::25.25
2017-12-29 12:40:39.030 [WARN ] [wave.discovery.ZWaveDiscoveryService] - NODE 55: Device discovery could not resolve to a thingType! 010F:0302:1000::25.25
2017-12-29 12:40:39.033 [WARN ] [wave.discovery.ZWaveDiscoveryService] - NODE 32: Device discovery could not resolve to a thingType! 010F:0302:1000::25.25

I have only this file type in \openhab2\userdata\zwave “node15.xml”. So I used the snapshot binding in the past and now too?

Only a problem in your database which is solved with the next snapshot?

6

Hmmm - I’m not sure. It seems VERY unlikely all these devices are missing in the database now (I’m pretty sure that’s not the case and I’ve just checked a few are correct).

Maybe there’s another error on startup and the database isn’t being read correctly. We had a problem like this in the past - can you check there are no errors thrown during startup? I’ll try and do a check here as well, but it will be later today.

7

Hi,

I have a similar problem with my device PAT02-1b a Temp/hum sensor.
Running the discovery from inbox tapping the sensor at the same time for it to “be alive”, still it wont identify it, only seeing it as Node 4.

This is the log:

2017-12-29 16:16:41.289 [WARN ] [wave.discovery.ZWaveDiscoveryService] - NODE 4: Device discovery could not resolve to a thingType! 7FFFFFFF:7FFFFFFF:7FFFFFFF::0.0

==> /var/log/openhab2/events.log <==

2017-12-29 16:16:41.331 [arthome.event.BindingEvent] - org.openhab.binding.zwave.event.BindingEvent@11cb0f9

Removed it so many times now and re-discovered with the same result.
-Running snapshot 2.3
-Less then a meter from the the z-wave controller.
-Taping as hell on the sensor for it to be alive.
-it should be this device in the database: http://www.cd-jackson.com/index.php/zwave/zwave-device-database/zwave-device-list/devicesummary/533
Even though it says PAT02-1b on the backside of the sensor.

Any ideas?

Thanks

8

Only what I said earlier - are there any errors in the log during binding initialisation? I will take a look later, but if someone can check then I can try and resolve it earlier.

9

Hi chris,

the errors are gone. I’ve rebotted the pc and then no errors anymore.

I think, nothing to worry.

10

This is a typical error on a batterie powered device which is not fully recogniced by the binding.

Try to wake the device up manually as often as needed. It will recogniced at the end.

11

I let it be for now and these are the last log entrys:

2017-12-29 16:16:41.331 [arthome.event.BindingEvent] - org.openhab.binding.zwave.event.BindingEvent@11cb0f9

2017-12-29 16:17:11.381 [arthome.event.BindingEvent] - org.openhab.binding.zwave.event.BindingEvent@1db5c2a

2017-12-29 16:32:10.877 [hingStatusInfoChangedEvent] - 'zwave:device:2d6b9974:node4' changed from OFFLINE (COMMUNICATION_ERROR): Node is not communicating with controller to ONLINE

2017-12-29 16:32:26.538 [hingStatusInfoChangedEvent] - 'zwave:device:2d6b9974:node4' changed from ONLINE to OFFLINE (COMMUNICATION_ERROR): Node is not communicating with controller

2017-12-29 16:45:50.608 [hingStatusInfoChangedEvent] - 'zwave:device:2d6b9974:node4' changed from OFFLINE (COMMUNICATION_ERROR): Node is not communicating with controller to ONLINE

2017-12-29 16:46:06.276 [hingStatusInfoChangedEvent] - 'zwave:device:2d6b9974:node4' changed from ONLINE to OFFLINE (COMMUNICATION_ERROR): Node is not communicating with controller

2017-12-29 17:00:33.630 [hingStatusInfoChangedEvent] - 'zwave:device:2d6b9974:node4' changed from OFFLINE (COMMUNICATION_ERROR): Node is not communicating with controller to ONLINE

2017-12-29 17:00:49.225 [hingStatusInfoChangedEvent] - 'zwave:device:2d6b9974:node4' changed from ONLINE to OFFLINE (COMMUNICATION_ERROR): Node is not communicating with controller

Is there a certain time that i should try to have it alive, can i manually activate OH and the z-wave controller to look for it. This device has a tamper switch which i have to triple tap for it to blink for a moment, i dont know if that it is the short window the device is acctually alive…

12

That’s a little strange, although I’m happy it’s working…