I can’t set the temperature in the device by manually setting the temperature. Very occasionally I might get it to accept the temperature but then it starts reducing the temperature.
I have a video of the screen showing the problem with the temperature looking like it is set but it reverts back to the original temperature.
@Mariano_Colmenarejo would you mind taking a look at this issue? I am using your driver for the device because it was more stable than the SmartThings driver. I don’t understand why the temperature is showing set to 57.2 when the settings can only be while numbers.
I suspect SmartThings has changed or broke some similar to the check your network issue you helped with several months ago (see the screenshot for the error which is still not fixed by SmartThings development)
I’ll look at it tomorrow, it’s very late here and I was going to sleep.
Have you tried the stock Zwave Thermostat driver? I think the problem with decimals in the setpoint has been solved, they changed the profile.
But now they have changed things in the app, so if the change in the set point value does not coincide with the 1º adjustment interval, the app does not accept it and resends the corresponding value in 1ºC intervals. The problem is that the default interval is 1ºC and when converting it to ºF it is approximately 1.8ºF and this may be the error you are seeing.
I don’t know what solution should be given, I can’t test it because in my location app uses ºC, but this problem will be occurring in all the thermostats that use ºF due to their location.
In your device, now the app will only accept values from 39.2 °F to 82.2°F interval 1° (40.2, 41.2, …, 57.2, 58.2, …, 82.2)
I will try to change the profile interval to 0.1° tomorrow
I have tried both default and custom drivers. Neither is working to set the temperature consistently. The default driver generates the network error almost all the time so it has 2 problems to fight with when I try to use it.
Try with this driver version
This version supports setpoint change intervals of 0.1º, but the thermostat could not support values with a precision of 0.1º.
If thermostat only supports a precision of 0.5º or 1º, the driver, when reading the setpoint value after sending it, will update it to the adjustment value that the thermostat sends as valid and they should be synchronized.
───────────────────────────────────────────────────
Name Z-Wave Thermostat Mc
Version 2024-12-28T10:20:09.894628372
───────────────────────────────────────────────────
I have uninstalled the previous driver and installed the new one. I did a quick test with it and it was still not acting correctly but I didn’t have time to document the issues I was seeing. I do see .1 degree temperature increments in the new driver.
I’ll let you know more when I get back home and can test it more.
I installed the new driver. It did correct the constant lowering of temperature, it still acted strange. It shows the x.9 temperatures, and it did lower the temp 2 degrees after I set the temperature by choosing the heating temp and selecting a number from the vertical menu by choosing temperature like 68, 69, 70, etc… If I slid the horizontal slider, it gave me the options with x.9 (66.9, 67.9, 68.9, 69.9, etc) however when I selected the temperature, it stayed where I set it.
After I closed out of the thermostat and selected it again, as it opened, it slowly reduced temperature around 4 degrees.
Another point I wanted to make. I was NOT running your driver prior and it was behaving the same way since the update.
Once the driver sends the value to the thermostat, the driver sends a “Get” command to check the value set in the thermostat and update the capability state.
With the value returned by the thermostat, the driver emits the response value to the app and the platform.
If the value is not received or the value received in the App is not the one the App expects, (the same one sent by the app), then the App gives a network error and shows the previous value again. When app must show any value received from the driver.
You can check if the value shown in the physical thermostat matches the value in the App, it may be out of sync or not.
This behavior is producing some desynchronizations between real device states and the App in multiple capabilities of different devices, which are sometimes solved by doing a refresh and sometimes not, because the platform blocks states already emitted by the driver and only allows state changes to be propagated.
I say this because I’m tired of seeing in CLI logs, drivers emit state values that get blocked somewhere and don’t reach all the endpoints of the platform, producing strange behaviors and state desynchronization, even failures in routine execution.
You can post CLI logs of these behaviors and I could analyze them.
@Mariano_Colmenarejo the new driver is working better than the previous and the SmartThings driver. I can get the temperature set and it stays.
I have been using a routine to set the value since it seems to be the most reliable and is how I primarily change the temperature. The manual method in the device is still quirky but I suspect it is due to the information in your last note. Thanks for the quick response and update.
I wish SmartThings support was that quick. I am still fighting with the network connection issues you had looked at months ago and still haven’t received any real updates for the problem. It is another reason why I am using routines. I can’t always access the devices without the error an getting bounced out of the device.
Yes, Using routines is a way to get around the App’s filters and obstacles, even when the states of a device become unsynchronized, one way to resynchronize them is with a manual or automatic routine and thus the App does not block the change of state.
Thank you. I noticed today that it is working much better than yesterday. It looks like choosing the temperature and typing a value in is more reliable.
Also, not that I use this but I would mention it in case it is important. The web interface for my.smartthings.com thermostat option shows temperature range of -460 to 10000F when I select it. Again, I don’t regularly use this at all, I only was looking at it because I was trying to figure out what was happening with the driver.
