Hello all,
I recently swapped out my Nest Thermostat for the GoControl Z-Wave Thermostat GC-TBZ48 (for obvious reasons) and after quickly find -> replace all with the new entity in my automations, etc, was back up and running in no time. I’m connecting my Z-Wave devices through Vera.
Only problem is that after switching the thermostat to celsius, it doesn’t seem to accept 0.5 degree increments. My automation is setting it to 21.5 and it automatically resets to 22, even though the thermostat spec sheet shows it can do 0.5 C increments.
So, what does this mean in terms of setting the thermostat to 0.5 C increments? Seems like HASS sends the half degree value, and then the device sends back that it was set to the nearest integer.
Might also try posting the contents of OZW_Log.txt when you are setting the temperature. It should show you exactly what commands are being sent to the thermostat and their contents.
I’ve connected these through Vera, so likely don’t have the same type of logging available. I’ll have to see what logs are available tonight or on the weekend when I’m able to dig into it.
Let’s take Home Assistant out of the equation for a moment: Can you manually set the thermostat to 21.5? If you cannot then this becomes a different conversation.
Let’s assume you can set it manually. The question becomes: What is the value sent by Home Assistant?
Do you have a means of confirming it sends a zwave command containing 21.5?
Sets the desired setpoint. User serviceId urn:upnp-org:serviceId:TemperatureSetpoint1_Heat for heat and urn:upnp-org:serviceId:TemperatureSetpoint1_Cool for cooling
Arguments: NewCurrentSetpoint(Integer)
NewCurrentSetpoint: An integer value between 0 and 100 specifying the desired heat or cooling setpoint.
If the API truly only accepts “an integer value”, then you are out of luck.
Honestly, I somehow fried mine and ended up replacing it with a Radio Thermostat CT50. Good luck though, if you’re using Vera and this thermostat, you’ll need to talk to the vera/pyvera folks.