Core: Z-Wave climate device problem in version 0.103.x

[jacekpaszkowski]

Home Assistant release with the issue:
0.103.x

*Last working Home Assistant release (if known): *
0.102.3

Operating environment (Hass.io/Docker/Windows/etc.):
Hass.io

Integration:
Z-Wave / Climate

Description of problem:
I have couple of z-wave thermostats (Eurotronic and Thermofloor). Up to the version 0.102.3 each device had two separate climate entities, one for "normal" mode and one for "eco" mode. Now in version 0.103.0 there is only one entity for each device (with different name) than previous "normal" mode entity. Now i'm not able to set "eco" mode temperature and get "eco" mode setpoint temperature.

I also noticed that now when hvac_mode is of temperature attribute is null.

Will this behavior be changed in new versions?

Thanks

[probot-home-assistant[bot]]

Hey there @home-assistant/z-wave, mind taking a look at this issue as its been labeled with a integration (zwave) you are listed as a codeowner for? Thanks!

[dshokouhi]

@jacekpaszkowski you should be able to use the service call climate.set_preset_mode now

https://www.home-assistant.io/integrations/climate/#service-climateset_preset_mode

If that does not work make sure to list the make and model of your thermostats.

[jacekpaszkowski]

@dshokouhi i know there is service climate.set_preset_mode and i use it to activate "eco" or "normal modes. But now i'm not able to set (and retrive) "eco" mode temperature setpoint - i used to do this by calling climate.set_temperature on secondary "eco" entity of my z-wave device.

Second, now if the clime mode is off the vale of temperature attribute (setpoint temperature value) is always null. So when device is off i cannot retrive the target temperature set to this device.

Ealier it was possible to call climate.set_temperature and set target (setpoint) temperature even if hvac_mode (state) was 'off'.

I use:

1. manufacturer_name: EUROtronic, product_name: EUR_SPIRITZ Wall Radiator Thermostat

2. manufacturer_name: ThermoFloor AS, product_name: Heatit Thermostat TF 021

I have same issues in both cases.

[elad-bar]

Duplicate of #29944

[jacekpaszkowski]

@elad-bar it seem to be very similar issue. In #29944 there is a problem when device has heating and cooling features. In my case i have heating in two modes "normal" and "eco/away".

All issues describes in #29944 are same in my case.

[elad-bar]

@jacekpaszkowski seems that the way the componet is extracting the temprature when working in MODE (aggregated) instead of SETPOINT is not fully covered, the problem is that there are not enough debug logs.

When enabling HA debug logs or in ZWave logs, you can see that the command is being sent correctly, and ZWave logs contains the right values while reading it,
It's just the way it's being stored in the class members.

[jacekpaszkowski]

Yes, maybe it's caused by new aggregation of values. But now we've lost some functionalities.

[Kurisutian]

I have a similar problem with my Eurotronic Spirit Zwave Thermostats. I have 2 automations in NodeRED, one time based which turns the thermostat on or off and sets certain temperatures. The other checks the outside temperature and based on the result either turns the thermostats on or off and sets another temperature.
While the timer based triggers all work I have a problem with setting the temperature in my other automation. When I have set a timer based temperature of eg. 24°C and turn off the thermostat at a specific time, I check the outside temperature and when it's cold (<10°C) it should turn on the thermostat and set the temperature to 21°C. After the last update to 0.103.x this is no longer working correct. While the timer still does it's job the check for the outside temperature does no longer set the temperature. It turns on the thermostat but instead of setting the temperature (to 21°C in this case) it uses the last set temperature from the time based trigger before this one turns off the thermostat (24°C). I checked it several times but despite the different temperature the triggers are identical and I cannot find a cause why one ignores all temperatures set while the other sets them correctly.

[stale[bot]]

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 👍
This issue now has been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

[jacekpaszkowski]

Any chance to any kind of solution?

[stale[bot]]

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 👍
This issue now has been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.