Danfoss LC-13 Thermostate discovered as unknown device

Hello, here is the problem:
I’m running OH 2.5.1 with some Z-Wave devices. After the update to 2.5.1 the LC-13 is shown in HABmin with a button “delete” an no informations about the device are shown. At first i deleted the thing an readded it. (like after the other updates when z-wave is affected).
Now it is dicovered as an unknown device.
I excluded it, reseted it to factory defaults an reincluded it -> also unknown.
I tried readding with about 20 wakeups -> still unknown.
I checked the jackson DB: Device 0002.0005.0004 is there with an actual entry: https://www.cd-jackson.com/index.php/zwave/zwave-device-database/zwave-device-list/devicesummary/165
Log entry at discovery:
2020-01-25 20:04:02.594 [WARN ] [wave.discovery.ZWaveDiscoveryService] - NODE 24: Device discovery could not resolve to a thingType! 0002:0005:0004::1.1

Has anybody another idea?

???

read-write error. I corrected it. Thank you.

I have a very similar problem; but I haven’t pressed that button so they still work for me :slight_smile:

However, there is something wrong, because when I was in the process of adding a new switch, I saw several error messages about not being able to add the thermostats, which are already added (and working).

Your device is in the database:

https://www.cd-jackson.com/index.php/zwave/zwave-device-database/zwave-device-list/devicesummary/165

You need to wake the device several times to get fully initialized.
If that does not work change batteries, try again, factory reset, try again.

If it still does not work post a debug log and then perform the inclusion.

Please post a debug log showing the error.

When I start a discovery, I get this in my debug log (node 55 and 56 are two thermostat):

2020-01-28 20:05:17.292 [DEBUG] [nhab.binding.zwave.discovery.ZWaveDiscoveryService] - NODE 54: Device discovery resolved to thingType zwave:fibaro_fgdw002_00_000
2020-01-28 20:05:17.296 [DEBUG] [nhab.binding.zwave.discovery.ZWaveDiscoveryService] - NODE 55: Device discovery completed
2020-01-28 20:05:17.298 [WARN ] [nhab.binding.zwave.discovery.ZWaveDiscoveryService] - NODE 55: Device discovery could not resolve to a thingType! 0002:0005:0004::1
.1
2020-01-28 20:05:17.301 [DEBUG] [nhab.binding.zwave.discovery.ZWaveDiscoveryService] - NODE 56: Device discovery completed
2020-01-28 20:05:17.303 [WARN ] [nhab.binding.zwave.discovery.ZWaveDiscoveryService] - NODE 56: Device discovery could not resolve to a thingType! 0002:0005:0004::1
.1
2020-01-28 20:05:17.306 [DEBUG] [nhab.binding.zwave.discovery.ZWaveDiscoveryService] - NODE 57: Device discovery completed
2020-01-28 20:05:17.307 [DEBUG] [nhab.binding.zwave.discovery.ZWaveDiscoveryService] - NODE 57: Device discovery resolved to thingType zwave:shenzhen_coolcampwrplug
_00_000

Again, note that I do have both nodes correctly configured in my system; but it was done long ago.

Hi,

I have a similar problem with the LC-13 on a newly installed system (openHABian). I can find the device in the database on the internet:
https://www.cd-jackson.com/index.php/zwave/zwave-device-database/zwave-device-list/devicesummary/165

But it is missing in the supported things list in the binding in PaperUI of my system.

Also the proper xml file is not part of the jar file
org.openhab.binding.zwave-2.5.1.jar

Seems like it is not part of the stable release (anymore?).

Markus

It looks like we have a problem here, Chris will take a look.

It looks like the device was removed from the database a few months back during the full export, and only added back last week. So if you are using a version of the binding between 25 Dec and 17 Jan, then it will not work.

If you use the latest binding it should work.

1 Like

Hi,
yesterday I have installed openHAB for the first time (I migrated from Home Assistant) with openHABian and I have exactly the same problem with LC-13.

Can you provide steps for solution?

Welcome to openHAB.
Please upgrade to the latest zwave snapshot binding.

Thank you at all. Now I’ve installed the latest Z-Wave Snapshot with the script above. Everything works fine now.

1 Like