Sensative Z-wave comfort strip - cannot set reporting period for moisture

Hi,
I purchased one Sensative Z-wave comfort strip and beside it not reporting anything to openhab (i will still be patient and try to make it work) I cannot set its Moisture reporting period to any value, select box contains label instead of values:
18

Instead of the text inside dropdown, choice from 0-120 should be presented.

There were several errors in the database. I think I fixed them so after the changes are merged into the binding you need to upgrade to the latest snapshot or development version.

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

Thanks! I was avoiding long enough upgrading to latest snapshot, but I think I will have to do it (do I have to update openhab as well or only the binding?)

And will that also make the stick report values?

Right now I see it in the logs just saying that it is being updated

2018-09-05 22:36:46.799 [me.event.ThingUpdatedEvent] - Thing ‘zwave:device:0aa4dfe7:node13’ has been updated.

2018-09-05 22:36:46.908 [me.event.ThingUpdatedEvent] - Thing ‘zwave:device:0aa4dfe7:node13’ has been updated.

2018-09-05 22:40:03.659 [me.event.ThingUpdatedEvent] - Thing ‘zwave:device:0aa4dfe7:node13’ has been updated.

2018-09-05 22:59:04.502 [me.event.ThingUpdatedEvent] - Thing ‘zwave:device:0aa4dfe7:node13’ has been updated.

2018-09-05 23:28:09.613 [me.event.ThingUpdatedEvent] - Thing ‘zwave:device:0aa4dfe7:node13’ has been updated.

2018-09-05 23:57:14.226 [me.event.ThingUpdatedEvent] - Thing ‘zwave:device:0aa4dfe7:node13’ has been updated.

But no values change in items associated with it, it is just stuck at
Temperature 31.7 Luminance 6910.0

If you are at 2.3 stable you should be fine with a 2.4 zwave binding.

It should :grinning:

Hi @sihui I upgraded now to 2.4 stable version, I had to remove all my devices and add them again, and (so far) all works as expected. However, this strip doesn’t get recognized at all now.

All I get in log is this:

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

2018-12-28 00:16:53.345 [arthome.event.BindingEvent] - org.openhab.binding.zwave.event.BindingEvent@161c7a33

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

2018-12-28 00:16:55.348 [WARN ] [wave.discovery.ZWaveDiscoveryService] - NODE 5: Device discovery could not resolve to a thingType! Manufacturer data not known.

2018-12-28 00:16:55.358 [WARN ] [wave.discovery.ZWaveDiscoveryService] - NODE 9: Device discovery could not resolve to a thingType! Manufacturer data not known.

2018-12-28 00:16:55.373 [WARN ] [wave.discovery.ZWaveDiscoveryService] - NODE 13: Device discovery could not resolve to a thingType! Manufacturer data not known.

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

2018-12-28 00:17:30.975 [arthome.event.BindingEvent] - org.openhab.binding.zwave.event.BindingEvent@1223fc28

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

2018-12-28 00:17:32.981 [WARN ] [wave.discovery.ZWaveDiscoveryService] - NODE 5: Device discovery could not resolve to a thingType! Manufacturer data not known.

2018-12-28 00:17:32.990 [WARN ] [wave.discovery.ZWaveDiscoveryService] - NODE 9: Device discovery could not resolve to a thingType! Manufacturer data not known.

2018-12-28 00:17:33.003 [WARN ] [wave.discovery.ZWaveDiscoveryService] - NODE 13: Device discovery could not resolve to a thingType! Manufacturer data not known.

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

2018-12-28 00:17:55.016 [arthome.event.BindingEvent] - org.openhab.binding.zwave.event.BindingEvent@57217008

2018-12-28 00:18:02.372 [arthome.event.BindingEvent] - org.openhab.binding.zwave.event.BindingEvent@50b137eb

2018-12-28 00:18:03.598 [arthome.event.BindingEvent] - org.openhab.binding.zwave.event.BindingEvent@5df8c2c4

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

2018-12-28 00:18:04.376 [WARN ] [wave.discovery.ZWaveDiscoveryService] - NODE 5: Device discovery could not resolve to a thingType! Manufacturer data not known.

2018-12-28 00:18:04.386 [WARN ] [wave.discovery.ZWaveDiscoveryService] - NODE 9: Device discovery could not resolve to a thingType! Manufacturer data not known.

2018-12-28 00:18:04.403 [WARN ] [wave.discovery.ZWaveDiscoveryService] - NODE 13: Device discovery could not resolve to a thingType! Manufacturer data not known.

2018-12-28 00:18:05.569 [WARN ] [wave.discovery.ZWaveDiscoveryService] - NODE 5: Device discovery could not resolve to a thingType! Manufacturer data not known.

2018-12-28 00:18:05.587 [WARN ] [wave.discovery.ZWaveDiscoveryService] - NODE 9: Device discovery could not resolve to a thingType! Manufacturer data not known.

2018-12-28 00:18:05.624 [WARN ] [wave.discovery.ZWaveDiscoveryService] - NODE 13: Device discovery could not resolve to a thingType! Manufacturer data not known.

2018-12-28 00:18:06.525 [WARN ] [wave.discovery.ZWaveDiscoveryService] - NODE 5: Device discovery could not resolve to a thingType! Manufacturer data not known.

2018-12-28 00:18:06.535 [WARN ] [wave.discovery.ZWaveDiscoveryService] - NODE 9: Device discovery could not resolve to a thingType! Manufacturer data not known.

2018-12-28 00:18:06.548 [WARN ] [wave.discovery.ZWaveDiscoveryService] - NODE 13: Device discovery could not resolve to a thingType! Manufacturer data not known.

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

2018-12-28 00:18:08.616 [arthome.event.BindingEvent] - org.openhab.binding.zwave.event.BindingEvent@1281c5a4

2018-12-28 00:18:34.566 [arthome.event.BindingEvent] - org.openhab.binding.zwave.event.BindingEvent@2af5c4b2

2018-12-28 00:18:40.350 [arthome.event.BindingEvent] - org.openhab.binding.zwave.event.BindingEvent@14c4424d

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

2018-12-28 00:18:42.349 [WARN ] [wave.discovery.ZWaveDiscoveryService] - NODE 5: Device discovery could not resolve to a thingType! Manufacturer data not known.

2018-12-28 00:18:42.362 [WARN ] [wave.discovery.ZWaveDiscoveryService] - NODE 9: Device discovery could not resolve to a thingType! Manufacturer data not known.

2018-12-28 00:18:42.373 [WARN ] [wave.discovery.ZWaveDiscoveryService] - NODE 13: Device discovery could not resolve to a thingType! Manufacturer data not known.

It was recognized before (but it was not reporting any values). I cleared openhab cache as I was having some common known log entries.

I tried waking the strip about 20 times, and I can wait more if needed, but do you have some other tips? (it is the node 13 in this particular case I am waking up)

Thanks!

small update, it did identify itself overnight as " Z-Wave Node 013: 11 02 011 Strips Comfort/Drips Multisensor", but it still says:

Status: ONLINE
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.

I tried waking it up several times now, in logs I get

2018-12-28 08:29:59.422 [arthome.event.BindingEvent] - org.openhab.binding.zwave.event.BindingEvent@5474616d

==&gt; /var/log/openhab2/openhab.log &lt;==

2018-12-28 08:30:01.429 [WARN ] [wave.discovery.ZWaveDiscoveryService] - NODE 9: Device discovery could not resolve to a thingType! Manufacturer data not known.

==&gt; /var/log/openhab2/events.log &lt;==

2018-12-28 08:30:39.174 [arthome.event.BindingEvent] - org.openhab.binding.zwave.event.BindingEvent@6cb12dfa

Regarding wake ups it seems to be a horrible device (search the forum).
Try to wake it up a couple of more times, I have seen peeple having to do that 10 or even more times.

Thanks, I was just writing that it did identify itself fine. Still not sending any data thought, temperature just sits there as in the beginning of the thread, but I will give it a few days to start sending some data.
Thanks again!

My Comfort started sending data as soon as I included it (Strips bought 2 weeks ago, OH installed 3 weeks ago so both fresh). I wonder if you got yours to work?

However, it looks like the current device on the database has older firmware than what is currently being sold:

  • The linked manual calls the device “Strips Multisensor” (vs Comfort/Drips) which cannot be found from the manufacturers site
  • Some configuration parameters are missing
  • Most configuration parameters are marked as “read only” and cannot be changed on HABmin

There are three “Strips Multisensor” devices on Z-Wave product catalog. I guestimate that the current device on cd-jackson database is FW: 0.01:00.01 and what is currently sold are FW: 0.03:00.03 or FW: 0.04:00.04. On HABmin it says my Comfort has firmware 0.3.

Database guide tells to flag @chris in this case which is all that my know-how allows me to do anyway.

1 Like

I purchased another strip and it got included fine, and started reporting temp and luminosity fine immediately, so I will be returning the old one. It didn’t report the humidity thought, but it is fine as I do not really need that. what is “funny” is that it got included as node 36, and previous node was 15. I guess that all my tries to include previous node did not go unnoticed by controller, and it was just reserving some places for it and skipping count/ids.

However, second worked fine for 3-4 days and then it stopped reporting anything at all, I suspect because I did sent it some config from paperUi (from Habmin all the fields are grayed out so I cannot change anything for both old and new device, not sure why :frowning: )

I also noticed that memory usage of openhab almost doubled, I was never getting server over 65% usage (2gb ram) but now it is 90% all the time after upgrade. So all this combined “forced” me to reconfigure and reinstall entire openhab server and probably rebuild z-wave network as well. I will be moving to docker version of openhab as I think configuration and upgrade might be a bit easier (if nothing at all, easier to test upgrade I hope).
So this is my full focus for now, so I will have to put dealing with the strips on hold.
I do have two contact strip sensors, they work fine without any complaints (one included very recently, after the problematic sensor).

You could post your xml file from your zwave folder. Also please post the updated manual or a link to it.

We need to add a new device to the database.

Very strange, I have edited the database and removed the read only marks.

1 Like

Here is the xml-file. I censored the home id-value since it seemed like per installation kind of information, I hope that’s okay.

network_xxxxxxxx__node_11.xml (14.6 KB)

Product manual (EU version) from Z-Wave Alliance catalog. This has both Comfort and Drip, whereas manufacturers site has these separate with very minor changes (wording, images).

Done:

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

1 Like

Great, thanks!

I don’t know if it’s relevant or not but the new device has a wrench symbol and “More information required” on the device list and the old device page has a bunch of errors now (“Device definition contains errors”).

Fixed.