this rule does not work and never triggers..
this one works but it is using custom attribute not the co2 standard capability
I will look into it...
1 Like
let me know if you want me to beta something with more debugging etc. thanks
Please show me the Event Subscriptions portion of App Status page.
i have redone the rule to use the custom attribute .. i will recreate a shorter rule with same triggers .. confirm it is still not working and then post the event subscription for you..
thanks
here is new rule,, see all logging is on. event subscription looks ok to me but you are the expert.
Also logs showing it is not firing.. the new rule is called "co2 handler test" the old one rewritten with custom attributes is "co2 handler" You can see the old one fire in the logs using custom attributes but the new test rule is still not firing.
logs
Yeah, the event subscription shouldn't have the value in it like it does. Easy fix.... next release.
1 Like
@bravenel, I'm seeing this behavior again today. Created a super trivial rule with a virtual omnisensor triggering on CO2 > 1000. The rule appears to trigger with any change in CO2 levels, regardless of the 1000 ppm threshold. Detail below.
I keep looking over my shoulder for the bone-headed mistake I made.....so it'll make me feel way better to know this is an actual bug lol.
The Log
First I used a value above threshold (trigged correctly), then one below the threshold (still triggered):
app:58172022-07-17 03:19:06.191 pm infoAction: Notify Mark (SMS): 'CO2 Level Too Light Triggered'
app:58172022-07-17 03:19:05.340 pm infoTriggered
app:58172022-07-17 03:19:05.334 pm infoEvent: AAA Omni Tester carbonDioxide 444
app:58172022-07-17 03:18:52.327 pm infoInitialized
app:58172022-07-17 03:18:22.302 pm infoAction: Notify Mark (SMS): 'CO2 Level Too Light Triggered'
app:58172022-07-17 03:18:21.492 pm infoTriggered
app:58172022-07-17 03:18:21.485 pm infoEvent: AAA Omni Tester carbonDioxide 1100
Are you on the latest build? If not, please try this again after updating.
I did a simple test rule, and it works fine:
Only triggered on the value over 1000, not other reported values.
I'm on 2.3.2.139, which appears to be the latest. I can reproduce this at will. Stumped. Wonder if our trigger logic is the same?
Show the Event Subscriptions from the App Status page.
So weird, I created a new omni sensor and same result
app:58172022-07-18 06:23:59.586 pm infoAction: Notify Mark (SMS): 'CO2 Level Too High Triggered'
app:58172022-07-18 06:23:57.884 pm infoTriggered
app:58172022-07-18 06:23:57.876 pm infoEvent: AAA CO2 Tester v2 carbonDioxide 222
app:58172022-07-18 06:23:29.657 pm infoAction: Notify Mark (SMS): 'CO2 Level Too High Triggered'
app:58172022-07-18 06:23:28.098 pm infoTriggered
app:58172022-07-18 06:23:27.953 pm infoEvent: AAA CO2 Tester v2 carbonDioxide 1111
Edit: Rebuilt RM5.1 rule and same result. Stymied.
@bravenel, one troubleshooting tidbit that I can recreate -- hope it's helpful -- if I switch the trigger to sticky (for 1 second or any length of time), it behaves as expected. If I then put the trigger back to instant, it reverts to the odd behavior.
@bobbyD, what do you suggest I do at this point? I genuinely appreciate @bravenel taking time out to look at this issue--just the fact you guys are so active/responsive on the community at all is amazing.
But here's a situation now where @bravenel can't reproduce the error (which I imagine may be why he exited the conversation).
Still, I can easily reproduce the behavior no matter what test device or rule I use. Is there any other help you or anyone can offer? I'm stumped.
Try using a Custom Attribute for the trigger instead. See if that changes anything.
No change. Same behavior. So weird.
You'll be happy to hear that I am now able to reproduce this problem. Investigating ...
1 Like
