Wait event basic rule and RM

Hi,

So all my apps in RM and also a basic rule utilizing a wait event stopped working today.
Everything worked fine yesterday and today it stopped. One thing has happened since yesyerday, i've added a sunricher exacct oulet as a zigbee generic outlet. Worked like a sharm. It connected as a repeater and neigbourgh. But since then even the basic motion rule with wait for event inactive for 1 minute is not getting through. My motion sensors reports inavtive but no rules work.
The light goes on but never turns off...

I am out of things to try and really need your help here. Have read a bunch of similar threads but when a basic rule starts to fail, my limited knowledge isnt helping me solving this issue.

The hub i rebooted, ive change the RM to wait for expression but nothing helps. Not getting my apps to turn of my lights..

Br Nicklas

You will need to show a screenshot of a rule that failed along with screenshots of logs filtered to show the rule and devices involved. Without that there’s no evidence anything failed and nothing to diagnose the cause of it did.

2 Likes

@johnwill1 Here is one rule and the log of the same rule not switching off the light. As you can see between 23.09 and 23.22 nothung happens. Same with 3 more rules ( same set up).


It doesn’t show that motion stayed inactive for 1 min 30. You might want to set logging for the motion sensor as well and show the logs showing that device as well as the app. Why the 1 min 35 timeout? It shouldn’t be needed

@johnwill1 read in a thread it could force it work again... worth a try but did nothing :sweat_smile:

This is my motion sensor during the same time frame

Two things apparent to me:

  • The timeout should be removed. In this case it will have no function. Every time the motion sensor goes active, the one minute 30 wait for motion inactive event starts again. The only way that timeout would ever do anything is if the motion sensor went active and stayed active solidly for 1 min 35. You’re moving around and the sensor will trigger repeatedly, active, inactive, active and so on, retriggering the rule and restarting the wait.

  • Remove the ‘only turn off if on’. We’ve not seen logs for the light; only the rule and motion sensor (see below). We know the light turns on but without logs we’re assuming that the hub is aware the light is switched on. It’s better to send the off command without regard to whether the light is on in this case.

The logs are difficult to read when posted separately. Turn on logging for the light as well. Use the filter in the logs and select the rule, the motion sensor and the light, so that the entire sequence is shown in a single view.

1 Like

Made those changes but nothing happens. I can turnnoff the light via button and also other rules but as soon as i put in a waitevent nothing happens after that wait event

It's very difficult to read unfortunately. Only info/descriptionText logging is needed rather than debug logs (easier to add multiple screenshots as you can only zoom so far to read the log text)

I'll have to give up on this one unfortunately as the logs etc displayed from a mobile are making it virtually impossible to interpret.

2 Likes

The timeout will in fact make the Wait action work pretty much like a simple 1:35 delay, as the timeout applies to the Wait action as a whole. Therefore the Wait will only ever successfully complete if the motion sensor goes inactive within 5 seconds of the start of the wait.

As @johnwill1 explained it's hard to see what's going on with those mobile screenshots, but be aware that if another motion active event comes in it will retrigger the rule and cancel the ongoing Wait.

Suggest you split the logic into two rules : one triggering on motion active (set your dimmer) and another triggering on motion inactive and stays for 1:30 (turn off switches). You could also have a look at Room Lights.

2 Likes

Im starting to think so.ething else has happened.

Trying to do my best, this is the first time in 3 years someyhing like this has happened. I can't turn off the lights with a physical button either...

Did you guys mean logs like this? @hubitrep @johnwill1

This is with two different events, one off and one on

Tried the room lightning app and there is something fishy here, it says after 20 sec not turning off motion still avtive @hubitrep
And the motion sensor is reporting lux but motionsensor is inactive

No expert here but I would try switching your “wait for event” to “wait for expression”

Tried it and nothing changes..

Can you post the rule with that change? I'll take another look

Gotta be something amiss with the motion sensor not reporting inactive back to the hub. The rule is way too simple to be having issues with. Check the preferences of the motion detector device you're using to trigger the rule for clues (motion retrigger setting or something like that?). You can also view the events in that motion detector page and check that there's a corresponding motion inactive for every motion active.

1 Like

That was my first thought aswell but now i realized that no physical buttons work. All digital switches works but thats is.
This is the room lightning running atm.

That changed? Havent been able to get anyting working since i connected a sunricher exacct as a generic zigbee outlet.

And now all my switches are also malfunctioning. My digital switches work but the pyshical ones just turns off and then on with miliseconds delay, not changes made what so ever.

Ita wierd that 3 of the same sort (Hue) stops at the same time. Also all of my Fibaro dimmer 2 stops working with the physical button (6 dimmers).

And the inly thing i can think of is adding a new zigbee outlet. Haven't cha ged anything for months before that...

Sorry, I'm only somewhat familiar with what you originally posted = a Rule Machine rule. Maybe someone else can comment on this.