I have three Danfoss (sometimes branded Devolo) Z-Wave Wall Thermostats that have been relegated to only temperature sensors with the stock Z-Wave Sensor EDGE driver. They are not detected as Z-Wave Thermostats, as I am assuming the device fingerprints are not matching. Any help would be great (@Mariano_Colmenarejo I’m using a number of your edge drivers, but these still do not match up as Z-Wave Thermostats, only Z-Wave “sensors”) - Thanks!
These are fairly simple devices, and all I want is to set a “heat set point” as expected and use the temperature sensor value for automations.
Here is all the device info I can get:
Z-Wave Device:
Id: 8b772b28-65e8-40cf-b0d8-dc26b336f469
DNI: 0x2A
Firmware Ver: 1.0
Library Ver: 6
Zw Protocol Ver: 3.67
I was able to select the driver, and it’s reporting temperature and battery, however I still can’t set the heating set point. Here is what I captured with logcat when I change the set point:
I have been using the Vision Keyfob 1101 for years on several Z-Wave platforms. It is cheap, reliable, great battery life and 4 buttons. Each button can trigger multiple events so very powerful. While I can add it to Smartthings hub, it is recognised as a repeater. I can change the driver to a switch but the functionality is useless. Also tried an Edge driver but can’t assign it to the device.
Would love to see a driver for this device as they are such a useful and practical device, and don’t want to have to buy another device if this is easy to add.
The devices are still selling globally so very accessable.
Any advice appreciated on how this could be added.
Can’t seem to find this device, so if I am missing it, this post can be removed/deleted. Trying to see if anyone has an Edge Driver for the Ring Outdoor Contact Sensor Gen 2 (the one that uses Z-wave Gen 8/Z-wave LR)
Model Number:
0C01-0301
Manufacturer Code:
0346-0C01-0301
Thanks a bunch! Also Thanks to JDRoberts for showing me where these threads are!
The Z-Wave Sensor CS driver supports the indoor version of the Ring Z-Wave Gen 2 contact sensor. @csstup can probably add this fingerprint, but I don’t know if it will provide the functionality you need. For the indoor version, the driver supports contact sensor status, button status, tamper alert, battery level, and Z-Wave network ID.
I presume that the outdoor version of this sensor is backwards compatible with older Z-Wave versions since there is no ST hub that supports Gen8/Z-Wave LR.
The device is viewable in SmartThings, however since its a newer device SmartThings reads it as a “z-wave sensor”. This results in it being considered as every single sensor possible, such as a smoke alarm and a light sensor. Whenever the contact sensor is opened, it also states that motion is being detected, despite it not having a motion sensor on it. Using the Z-wave Sensor CS driver, it loses most of these issues, but still shows light and motion, along with stating it hasn’t updated yet, and to check again later. I originally thought this was a connection issue, but since there is a repeater nearby, I have ruled this out as an issue
That message typically indicates that the device is matching a profile with capabilities the device doesn’t support, so the driver can’t update the app for those capabilities. What profile does it say it is using in the ST Advanced Web App when using the Z-Wave Sensor CS driver?
Also, what capabilities are you expecting it to have? I could whip up a test version of the Z-Wave Sensor CS driver with your device fingerprint that matches the Ring profile that I mentioned previously.
As @h0ckeysk8er mentioned, this is because the device can’t send values for those attributes, so ST says the device hasn’t updated everything yet.
According to the manual, it looks like its the same basic device as the indoor version, with contact and tamper being supported. The parameters P1 and P4 are the same and already supported. The other parameters either wouldn’t be supported (supervision) or don’t matter anyway.
I can add the fingerprint 0346-0C01-0301 to Z-wave Sensor CS shortly and send the update out.
I answer the same thing as in January, I have developed a driver for the zigbee version of this thermostat that works well.
Extending the explanation a little more, this thermostat, both in the zigbee and zwave versions, uses non-standard mode functions that the default zwave handlers (dry, away modes, with their respective differentiated setpoints) that require writing a specific subdriver and performing tests, to debug correct operation.
This requires several hours of dedication to see the manual and adapt the code to the lua libraries and without having a device to do so it is even more complicated.
I’m sorry, but I think this zigbee thermostat costs about €85. Change 3 or 5 electrical connections from one thermostat to another and everything could be solved.
I’ve had this Ring ZWave device for a while, it’s a smoke/co listener. When I install in ST’s, it it falls under ZWave Sensor Ring, but the functions are not correct. I also have an Ecolink Firefighter and that is using the Z-Wave Siren MC edge driver and works perfectly.
I’ve made a screen shot from the Advanced tag, I’m hoping this is the information that is need to add the fingerprints to the Z-Wave Siren MC driver to make the Ring sensor work correctly