I bought a temperature and humidity sensor LS Control ES 861.
I included the device into an existing zwave network via opehab but the problem is that the z-wave binding in openhab does not cover any channels. The thing type is unknown.
As far as I understood the following information say that the device is not covered by the binding, isn’t it?
Following the details from “thing type” and “thing properties”
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.
What can one (me?) do so that the device is working?
Do you have a Node17 XML in the userdata/zwave folder? What does that look like
As all the links appear broken, what I think; LS Control made these devices for awhile and then stopped and sold all the stock to resellers with no manual and no support. IMO these look clunky and there are better humidity and temperature devices out there.
Sorry to say that my solution was to use something other than openHAB.
I now have eight of these sensors running in our house. No disconnections or other issues. At £10 each I reckon they’re just a loss leader as I got a Aeotec Z-Stick Gen5+ USB Controller at the same time. Note that they don’t transmit any humidity values, only temperature.
Unfortunately the database entry wasn’t deleted. I did ask for that in my last post. That was the blocker for me, so perhaps making more noise than I did might get it removed and give you the chance to make progress.
Could be some miscommunication on my part. The plan was to undelete and then modify the existing entry. It was basically aligned with the XML you posted, so only a couple of references needed to be added.
Anyway to resolve I added some references and marked for review. Should be in next ZW update.
@Bitty If you found your XML, please post for double check.
Thank you for your e-mail. I have talked with our technical support regarding your inquiry.
Unfortunately the product is very old and never really penetrated the market. Hence it is not fully supported for newer protocols. Some newer protocols are even known to drain the batteries in 48hours on these, because the ES 861 answers every ping.
Please see this Danish short document for the Temperature sensor and a long one for a different version with a potentiometer, but should be the same communication.
That’s all the documentation we can provide for this sensor.
The product went out of production in February 2017.
Your XML is the same as the one already in the ZW DB. I was just curious if the humidity might be displayed under SENSOR__MULTILEVEL, but it is not.
Actually, to resolve this issue I went ahead and copied some information from the ZWA site and finished the DB entry and marked for review. If it passes review it should be in the next ZW binding snapshot without any additional effort. However you can follow the blog, register, open ticket for write access & once granted, add the documents to the reference tab. Hopefully they are in english?
Weirdly, I just bought one from Vesternet and have come looking on the forum so see why it’s not working. They really should slap a warning on the product page if the device is unlikely to work with most systems.
Let me know if the new binding goes live and I’ll test an update also.
I may have misinterpreted your suggestion but I tried changing Number:Temperature to Number:temperature and received this message:
09:42:15.855 [INFO ] [del.core.internal.ModelRepositoryImpl] - Loading model 'zwave.items'
09:42:15.918 [INFO ] [del.core.internal.ModelRepositoryImpl] - Validation issues found in configuration model 'zwave.items', using it anyway:
'temperature' is not a valid dimension.
According to the item documentation it should include the capitalisation, but again I may have misunderstood.
I define my items textually, but as a test I created the channel through openHAB UI. By default the item is added as Number.Temperature•Point. However, the result is the same.