Is there a significant delay in reading data from Zwave thermostats when using the generic Zwave thermostat as the driver? I have a Go Control TBZ48 which is following the rules I have set for it in Rule Manager, the information on the actual thermostat is correct, however, when I look at the device in Hubitat the data is quite old. It's on a new rule and not representing this under the device, it's showing the previous rule data which has been FALSE for over 2 hours at this point.
The current rule is HeatSetPoint: 67 and CoolSetPoint: 75 (again, reflected on the actual thermostat so I know Hubitat is sending the rule to the thermostat) yet not reading the thermostats actual status,
Since my thermostat is connected via C-Wire and not a battery I would much prefer it's updated in near real time as there is no concern of battery life.
I have a Honeywell thermostat using the Generic ZWave thermostat driver.
I have both "Debug" and "Enable description Text" logging set to enabled.
Looking at my events, I only see the temperature when there is a change in temperature. This only happens when I make a change in in temperature and the room catches up.
Below is the events for an increase from 68 Deg.
It seems to be:
Heating setpoint change to 69 Deg
Thermostat reflecting the change was indeed set.
The thermostat reporting a change in temperature (reaching the new setpoiiint)
If I change from say 64 to 68 I would expect to see the change from 64 -> 65 then 65 -> 66 etc. However I have not tried this.
Something even stranger, SharpTools has the correct data from this thermostat but Hubitat device is still incorrect. How is this possible? It's a local Zwave thermostat??
I'll assume the current mode is "heating" and the number below is the current temperature, with the number below the Cool being its setpoint.
If it were in the cooling mode, I would then expect the number below COOL to be the current temperature and the number below HEAT is the heat setpoint.
I only suggest this possibility because it fits the two screens.
Thinking more, because you are in AUTO and the operating state is IDLE the tstat cannot know the next operation (i.e. either heat or cool). Perhaps it responds to the last mode.
I don't use Sharptools, can you tell what variables the "70" and "75" are linked to?
The 70 and 75 from SharpTools were the correct Heating and Cooling setpoints on the actual thermostat. I don't know how SharpTools had correct information when Hubitat did not, at least not in the device status page.
I tried several rules, polling and refreshing and it seems to be the Hubitat driver only updated every 4 hours from digging through the logs.
To be fair, I did not open a direct support ticket via email with Hubitat, but I assumed someone would have chimed in here. With that said, I have removed the ZWave thermostat. Was just not a reliable device when connected to Hubitat in my opinion. I don't want data that is 4 hours old.
I looked at my events page for my Z-Wave thermostat. It seems like there is only a report on temperature change. Sometimes the reports are minutes apart, sometimes longer. Could this be your situation?
