This may just be me misunderstanding how rules work, but I’m several of my condition-based rules aren’t firing. I have several time-of-day based rules: “It’s morning”, “It’s day”, etc. These are rules with time conditions and no actions, they just indicate a state. (Basically like modes.) I have r…

@jason0x43 yeah i understand, as mentioned more than one way to do things so I’m sure someone else might have the magic. I have a pretty simple setup so going into it just configued as my ST was as it worked. Hopefully it’s something simple.

I’ve been using CoRE and webCoRE for a while now on ST, and thought it’d be fun to re-implement things in RM when I was setting up my Hubitat. I was using some webCoRE features that RM doesn’t directly support, like “global” variables, so my setup there doesn’t port directly over. It’s been interes…

[image] jason0x43: I clicked the “Done” button in “Good evening”, at which point the rule immediately fired and lights came on. I’ve noted this multiple other times over the last couple of days (where a rule doesn’t fire, but if I open it and click the “Done” button it does). OK, a couple of …

[image] bravenel: Remember this key point, rule truth must change for a rule to do anything. That's what I was thinking. When "It's evening" becomes true, the state change should cause any rules that depend on it to be evaluated. [image] bravenel: Assuming second rule was false prior to …

I can confirm that there is a bug somewhere. Now to dig it out. It appears that the second rule is firing it’s true action when the first rule goes false, which is obviously wrong.

This bug has been identified and fixed, should be in the next release. This one was very interesting. Turns out that the code worked fine in ST, but not in Hubitat. In Hubitat there was a race condition caused due to our multi-threaded architecture. Solution was quite simple.

[image] bravenel: This bug has been identified and fixed, should be in the next release. Excellent! [image] bravenel: In Hubitat there was a race condition caused due to our multi-threaded architecture. Always the most fun things to debug. At least the failure case was the common case…

A case of the left hand not knowing quickly enough what the right hand was doing. Fix is to only use one hand. :sunglasses:

This bug has been fixed in the latest release. [image] Hub Update 1.0.4.706 Announcements Hubitat Elevation Software Update 1.0.4.706 is now available. Please note, the process takes about a minute to download (depending on your Internet connection) and extract the hub u…

Rules seem to be firing now for rule truth changes, but I'm seeing at least one case where a rule that's using another rule's truth as a condition isn't seeing the rule's current state (or I'm not fully understanding how that should work). Here I have an "It's day" rule that doesn't do anything it…

RM rules not firing when rule-truth conditions change

Get Help

bravenel March 25, 2018, 10:20pm 23

This bug has been fixed in the latest release.