ZWave.js and Climate Entities

Configuration Z-Wave
,
1

So I just setup ZWave.js. All was working well until I started to recreate my climate automations.
I am using an AEON Labs Z‐Stick Gen5 USB Controller and have a Radio Thermostat Company CT100.
Previously, I was using a Vera Edge for zwave.

My issue is when I change the climate.thermostat state to off, set temp and target temp high and low entities change to null. However, when I check in the zwave.js UI, those values are still set.
The current_temperature and current_humidity work regardless of state.

These null values break my automations. I am using template values for triggers.
an example:
{{ states.climate.thermostat.attributes.current_temperature > ( states.climate.thermostat.attributes.target_temp_high + 10 ) }}

When the state is off, the states.climate.thermostat.attributes.target_temp_high is now null. The reason I do this as I want the current_temperature to be dynamic as needed and not hardcoded in the scripts.

This used to work with Vera.

Is this a bug with the zwave.js integration

Thoughts? Ideas?

2

I have 2 of those thermostats that are working well. I’ve noticed that there are 2 climate entities created per thermostat. One works and the other does not. This issue is known to the developers.

You might try to reset it and try again.

3

I do see 2 thermostat entites for this device, but that is not the issue I have.
While the thermostat state is cool, heat or heat_cool, I have values and my automations are valid.

image
image872×301 18.5 KB

However, when the thermostat state is off, these values go null and it breaks my automations because templates do not work with null values.

image
image869×297 18 KB

4

That makes sense to me. When I physically go to the thermostat and put it in off mode, there are no set points because the thermostat is turned off.

In any other mode, the appropriate set points are available.

1 Like
5

I’m having a strange problem similar to this since moving from the old zwave integration, which was working perfectly, to zwave.js (had to completely rebuild the network as the migration wizard failed spectacularly)

There is only ONE thermostat entity for me.

Zwave.js info:
Driver Version: 8.7.7
Server Version: 1.12.0

Z-stick GEN5 ZW090
by AEON Labs
Firmware: 1.1

Version
core-2021.11.5

I’m no longer able to get the status of my thermostat, which is temperature set point and modes (heat, cool, etc) and the fan settings. They just don’t update, or land on something completely arbitrary.

What does work is probably telling. The sensors work. I can read current room temperature and humidity. I can also SET the temperature, and I can set the mode, and I can turn the fan on and off as usual, but none of these changes are propagating back to home assistant. I set the heat to 68°F and the thermostat takes the command, but then home assistant shows the set point going back to whatever the original value was.

However (BIG however) when I change the temperature setpoint via the buttons on then physical thermostat, it propagates back to Home assistant.

I use the nabucasa integration to link to Google assistant, and it’s messed up there too.

They all worked great under the old z-wave.

The thermostat is the CT32 by Radio Thermostat Company of America (RTC), Firmware: 10.0 which is in the database.

I hope this gets cleared up. I can’t be the only person this is happening to.

6

This is happening to me as well. All the coaxing to upgrade to ZWave JS because other is deprecated. I have even disconnected and reconnected to my Zigbee/ZWave stick, still NO JOY. Does anyone know the fix?

Thanks for any and all help!