No actions run when a Rule 5.1 /2.3.3 triggered

[jkister]

Im trying to debug a rule 5.1 that used to work <2.3.3.138 (I did several updates lately and am not sure what/which broke it).

No actions run even though the rule is triggered.

I disabled /all/ the actions and inserted a log command as the only action. even that doesn't run.

It's triggered by a lzw31-sn with the inovelli driver

Both the physical button and the on/off button the device page show the same behavior:

clue? @bravenel ?

[FriedCheese2006]

Known issue. Try disabling the "Trigger" logging.

Known Issues in 2.3.3.140

Please see Release 2.3.3 Available - #16 by bravenel The following issues are known to exist in Release 2.3.3.140; these will be fixed in the next release: Rule 5.1: Creates an extraneous Event Subscription when Mode is used both in Required Expression and Trigger, possibly leading to double triggering. Deleting a Disabled Action does not clear the disabled actions indication. Triggers with annual dates throwing an error when initialized. Throws an error when DateTime variable deleted that i…

[jkister]

@FriedCheese2006

Known issue. Try disabling the "Trigger" logging.

SOB. Thanks.

I spent forever debugging. Lesson learned.

[smartishhome]

I just had this same issue that the OP describes here. And similarly, the logs did not show the error for certain triggers on line 8928 when I opened up the live logs to see what was going on. I only saw this error.

I read through the known issues and didn't think any applied to my situation.
This is probably obvious to everyone else but I just decided to check the Past Logs and I found the first three errors thrown did have the reference to triggers on line 8928.

So I guess what I'm trying to say is if, like me, you see this shorter error it's worth it to look through the past logs to see if the past logs have any additional information. I never thought that I would see error messages change over time but I guess that is a thing I need to remember for next time!

[pseudonym]

@jkister it looks like you have holes in your IF-THEN logic. For example, you have between 10:00 PM and 10:59 PM and between 11:00PM and Sunrise. At 10:59:30, you won't meet any IF-THEN condition and the ELSE will execute. I think you want between 10:00 and 11:00 which will evaluate as true between 10:00:00.000 and 10:59:59.999

[jkister]

@pseudonym

it looks like you have holes in your IF-THEN logic.

hah, quite right. thx!