Core: Can't read/set setpoint temperature on the Danfoss Living Connect zwave device

[paweljankowski]

Make sure you are running the latest version of Home Assistant before reporting an issue.

You should only file an issue if you found a bug. Feature and enhancement requests should go in the Feature Requests section of our community forum:

Home Assistant release (hass --version):
0.53.1

Python release (python3 --version):
Python 3.6.2

Component/platform:
macOS/Zwave usb stick

Description of problem:
Can't set and read target temperature from the Danfoss Living Connect thermostat. HA shows empty value on the dashboard screen and I can't set target temperature for the thremostat. I've tried to use OZWCP and I was able to read/set target temperature from this device.

[balloobbot]

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates.

Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment :+1:

[ardeus-ua]

Unfortunately, LC13 is not reporting the current temperature. It's only using it for internal calculations. It would be useful to add the reading of the external temperature sensor in case the device description is:

<Manufacturer id="2" name="Danfoss">
<Product type="5" id="4" name="Z Thermostat 014G0013" />

Just like there's a workaround for REMOTEC_ZXT_120

[bieniu]

Yes, adding a reading current temperature from the external sensor would be great. Now in HA we have for this thermostat state "unknown" and the current temperature is missing. Really confusing for users.

Some time ago I started a thread in feature requests for this functionality and I tried to get current temperature from external sensor with scripts and a lot of people are interested in it.
It would be best to solve the this at the component level.

[mlesn]

I have the exactly the same issue ;-(

It would be really nice if this bug was corrected.

[sensei73]

Same here with Z-wave danfoss thermostats! I'm using bieniu's solution (thanks mate)! Would be great if possible!

[ronvl]

All for it to make this a real feature!!

[ardeus-ua]

+1

[kabturek]

But this issue is about not beeing able to set/read target temperature setpoint - this does work - ie setting the temperature (and was working for me for some time). The other thing is the current temperature/mode is unavailable (using @bieniu script too - thx!) but that belongs to the feature requests (as it is now).
Do you have the problem still @paweljankowski ?

[paweljankowski]

Yes, the problem still exist. Danfoss thermostat doesn't have current temperature but it has target temperature characteristic. I believe this should be use for reporting current temperature. I've made some changes in the homebridge-homeassistant plugin for having this working, but this is only a workaround.

[kabturek]

i'm confused - the original report was about setpoint/target temperature (this always worked for me) not current temperature (this doesn't work as stated before cause the device doesn't report it back - there is a feature request for it with an automation/appdeamon app developed already).

IMO this should be closed as this is not a bug - the device does not return the temperature - and a feature request (already created) is the appropriate option.

If there is a bug - then its in the frontend - it displays an empty 'currently:" value even tho there is no temperature. https://github.com/home-assistant/home-assistant-polymer/issues/654

(btw i do own the device and have it running with the appdeamon app)

[mike9011]

Would be great when this will be implemented! +1

[balloobbot]

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates.

Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment :+1:

[balloobbot]

This issue will be auto-closed because there hasn't been any activity for a few months. Feel free to open a new one if you still experience this problem 👍