It’s actually very relevant. Rule Machine, CoRE, or any other SmartApp references certain capabilities for devices, and in your use case they must be coded to look for “capability.thermostatFanMode”. If that is not in Rule Machine or CoRE, you won’t be able to trigger any action.
You’re in luck because CoRE does allow you to select that capability. You’ll see it as “Thermostat Fan Mode”. Now you just have to make sure that the device handler you’re using for your thermostat specifies that capability and sends the right event to trigger your actions.
I tested that with CoRE, and it does work; but I found a bug in my DH while testing that I’m in process of fixing.
I think I may have found an issue with CoRE that I thought was a problem with my DH (and ST’s default DH). I’ve PM’d the developer asking him to check on what I’ve found and got it to work. Once I made that change, CoRE worked perfectly to turn on a light when I set my thermostat to circulate (my trigger and action).
If you decide to try CoRE, there’s just a simple change that needs done that you can easily do if the developer can’t get to it right away. Just let me know.
Some week ago I tried to trigger the HVAC status using CoRE. But it didn’t work. I can control the HVAC and the setpoint. That’s all working fine but I couldn’t trigger the HVAC mode (if cooling, heating or off). Have to say I didn’t try to set it up again since then.
