Attempting to use ThermostatMode with a thermostat device in a required expression causes RM to hang. Neither the Thermostat Mode nor the Cancel this Condition buttons are responsive, The only way out is abort the rule by selecting a command from the left menu.
Using CustomAttribute as a work-around has no problem:
Brand new rule. No triggers or actions established. I can do it every time. Doesn't really matter to me since the work-around produces the result I wanted. Maybe a thermostat issue? Honeywell T6 Pro using the "Generic Z-Wave Plus Thermostat" driver. Not sure how the device would interact with RM however.
I have a second C-7. Radios are all off since it just runs cloud stuff, but it's up-to-date. I'll try a virtual thermostat there and see if it works. If it does, I'll try an update here.
Good call. I worked fine on the up-to-date C7. I'll update this one when it's gets quiet around here. If it works (guessing it will) I'll RESOLVE this issue.
I am now running 2.3.0.124 on this hub and the problem persists. With either of my Honeywell T6 Pros, I cannot use ThermostatMode == heat as a required expression. I have to use a Custom Attribute to get to it.
For sh?ts and gr?ns, I created a Virtual Thermostat on this hub and it worked! That seems to point towards the driver or some sort of interaction. As I indicated above, I have a perfectly acceptable work-around so this is a non-issue for me.
Interesting. I changed the driver as you suggested to "Honeywell T6 Pro Z-Wave Thermostat", Saved, Configured, and I was able to create the required expression. Any idea why?
Oh, are they both built-in? I was just curious to take a look at the driver you were using initially, so was after a link, but if it is also built-in, then that's ok.