I may have found a bug in RM regarding Acceleration and "stays that way"

I have a sensor that detects acceleration and have it attached to my backup sump pump. If it runs (goes active) for X span of time I want to be notified. No matter if I use seconds or minutes, it never fires the actions to run. Here is the rule and logs. The first log at 08:08:01 had the "stays that way" set at 20 seconds. The other was when I tested to see if seconds did not work and use minutes. No change. No notification and with RM logging set to all three this is all I get in the logs

I know the action works. I can press the "Run Actions" button and get the notification.

I have tried using both the custom attribute for acceleration as seen in the screenshot and the normal acceleration capability with no difference.

Running current version 2.4.0.151 on a C-8 Pro.

1 Like

I am not using any vibration/acceleration sensors but acceleration seems to be a wrong attribute. Physically acceleration means constant speed increase. However your pump is not moving. It is vibrating. You should use a vibration attribute if there is one.

1 Like

From the logged events, you can see that this is the correct attribute for the device (you can pick on the name, but that's just what it's called per the capability; "vibration" does not exist as a standard capability or attribute, but that is typically what this one means).

As for the OP and the rule, not sure what's going on. Have you tried re-creating the rule to see if it still happens there? I'll try a test myself... EDIT: Tried the test and it worked as expected. I am running a 2.4.1 beta, which has some fixes/changes for "and stays" (sticky) triggers, though I don't think simple cases like this were one of them...

4 Likes

I created a new rule and got the same results. The Triggers is not firing when using "and stays".

Just to rule out a problem with your physical device or driver, can you replicate with a Virtual Acceleration Sensor (or similar device, e.g., Virtual Omni Sensor)? Along those lines, while event logging in your rule should show the same, I'd also be curious what the "Events" tab on the device detail page for the device in question looks like.

I replicated your exact trigger, down to the timing of the "and stays?" option, and did not have any problems. I suppose it's possible a fix for something related in 2.4.1 might be doing this (you can join the beta if you want to test), but I don't think there was anything specifically for this.., :thinking:

There are known bugs in Stays triggers. These are addressed in 2.4.1, now in beta testing.

8 Likes

Of course, this is out of topic and I don't want to start a discussion but attributes should be named appropriately.
"acceleration" means something is moving with a constantly increased speed.
This is not a case a better to be fixed.

YES: :point_up_2: :point_up_2: :point_up_2:

1 Like

Yet still my favorite post in the topic. :wink:

3 Likes

:point_up: Exactly 100% !

Agreed! :slight_smile:

2 Likes

This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.