I'm in the process of migrating from SmartThings to Hubitat and am very far along. The last thing I am doing is converting my WebCore automatons into Rule Machines. I'm aware I could install WebCore for Hubitat, but want to manage everything in one place.
This is what my WebCore looks like that I've decided to break up into two different Rule Machines ("on" and "off"):
As you can see, the Required Expression is true and the Trigger is true. However, the Action just does not automatically run. I can click "Run Actions" and it will run as expected, but the Trigger does not appear to be setting itself off. It's like it is not "listening".
Triggers aren't true (or false). Hubitat is entirely an event driven system. That rule will trigger when there is a temperature event reporting less than 76, not from the state of the temperature.
Turn on Event, Trigger and Action logging for the rule. The Logs page is your friend. Most apps will report exactly what they are doing and why. When you see a temperature event, the rule will run (or not) depending on the reported value.
A good way to test things out is to add a virtual device. You can create a Virtual Temperature sensor, add it to the rule, and force a temperature event. Once you're satisfied it works, you could remove the virtual sensor. If you add a Virtual Omni Sensor, you get pretty much every kind of sensor there is; those are handy for testing things.
Ah, now I get it. WebCore is "state" driven, Hubitat is "change in state" driven. I was reading through a lot of threads and docs before and did not get that, but once you laid it out this way I knew what to look for and read some other situations.
Yes, I had already done this, but there was nothing in the Events or Logs pages that was telling me anything about why it was not running. As it turns out, Ecobee was not reporting back the temperature and did not do so until many hours later.
