My ancient Vera controller died and after some research I replaced it with hubitat c8-pro running 2.4.2.129.
I can view and control all my zwave devices individually using the Hubitat browser GUI, but I can’t seem to get any automations to work. For example, I have 8 Trane Z-wave Thermostats that control heat in my home. I want to set them all to the same temperature. I have tried setting them all manually using the thermostat scheduler app. I tried to set them all based on a hub mode change with a simple rule. Neither has any effect on the heating set point of the thermostats. What am I missing?
Leave all the apps out of the picture for a moment and just try commands from the device detail page page. At this point, you need to figure out whether there's a problem with the device or just the configuration of those particular apps (automations).
In general, you'll want to follow the steps for troubleshooting apps and devices here, likely focusing mostly on the device unless you rule that out with the simple command tests as described above (and also here):
Once you've narrowed down where the breakdown is, you (and anyone here) will have a better idea of what to look at next.
As I said all my thermostats work fine from the Devices tab. They instantly and correctly respond when for example I change the heating setpoint. The apps are the problem. Here is an example simple rule:
When mode becomes Away ...
Set mode to heat, heating to 70.0 for Master BR Thermostat
I turned on logging and when the rule is triggered, the app erroneously tries to set heating point to 2 degrees rather than 70 degrees. 2 degrees is not valid and the thermostat just ignores the command from the app and the heating setpoint is unchanged.
Can you provide a screenshot of the rules / apps involved, e.g. the main RM rule showing how it is constructed. Having some context about other aspects of the automation setup may trigger an idea for someone as to why it my be choosing 2 degress instead of something more realistic.
Also, providing some screenshots of any log outputs from the rules / apps to show the errors would also likely help. I know you have provided some details on the error, but again, sometimes seeing this in context of other logs or even just seeing the actual log output can suddenly make sense compared to a natural explanation of the error.
And welcome to the Community.... Shame it was not a more seamless experience. I'm sure there will be something simple at play that can be easily fixed. I'm sure you will enjoy the level of support the Community can provide.
Could you provide the details that @bertabcd1234 requested (it is in the link he provided)? Including the app used, screen shot of the app, screen shot of the logs when the app runs, and a screen shot of the events page from your thermostat device when the app runs.
If you are doing automations using Rule Machine, please turn on logging for Events, Triggers, Actions.
Can you provide the same logs for when you manually send a command from the device detail page? If that works, there is no reason the rule shouldn't, either. Keep in mind that this app appears to be sending 70.0, not 70, and I'm wondering if that is related.
Setting temp to 70.0F from device page works fine.
Changing the driver to Generic Zwave Thermostat and configuring works! I had been using the driver Hubitat chose for me when I added my thermostat devices. I didn't realize there were multiple "Generic" drivers. Thank you for the suggestion.
Thanks for the information! This is interesting, because as far as I can see, both drivers set the setpoint in the same way. But since it works from the device detail page, it seems like it has something to do with that decimal value getting sent from the app.
If you want to switch to the "Device" driver, run the "Get Info" command, and provide the "fingerprint" entry that should be output to "Logs" when you run that, this could at least be added to the Generic Z-Wave Thermostat driver or the Generic Z-Wave Plus Thermostat driver (sounds like you may have only tried the former; sharing the manufacturer and model of your device may be helpful, as it's unlikely the "DT" drivers will work with anything that isn't actually Z-Wave Plus, in which case the Plus driver may be a better choice). That would help avoid the problem the next time you -- or someone else -- adds this particular device in the future. If you're happy with the way things are working and don't want to bother with this, no big deal! But it may be good to know to see if anything can be done in any of these drivers.
For the record, my z-wave thermostats were made by Trane, Model TZEMT400BB32. Purchased in 2013. I'm working through adding rules for my other z-wave devices right now and will return to this issue when I get time.
Yeah, anything from 2013 is unlikely to be Z-Wave Plus, so the driver you changed to is probably best. Could still get the fingerprint added to match it up better in the future if you didn't choose the other driver yourself!
