I think deleted rule is still running

alex2 · July 9, 2021, 5:55am

I have a light that keeps turning off when a motion sensor is triggered even though there are currently no rules for this action.

I think one my test rules that I previously deleted may be triggering this action, but I'm not sure how to debug this issue. It may either be a Rule Machine rule or a Simple Automation rule.

Logs simply show that motion is detected and light turns off.

Could you point me in the direction to try to identify what is triggering this action?

Logs below just in case:

dev:652021-07-08 22:41:31.277 debugAfter zwaveEvent(cmd) >> Parsed 'zw device: 09, command: 3003, payload: 00 0C , isMulticast: false' to ['name':'motion', 'value':'inactive', 'descriptionText':Front sensor no motion, 'isStateChange':true]
dev:652021-07-08 22:41:31.271 debugPST02 No Motion
dev:652021-07-08 22:41:31.268 debugPST02 cmd.sensorValue: 0
dev:652021-07-08 22:41:31.264 debugPST02: SensorBinaryReport SensorBinaryReport(sensorValue:0, sensorType:12)}
dev:652021-07-08 22:41:31.258 debugparse() >> zwave.parse(description)
dev:652021-07-08 22:41:31.252 debugparse() >> description: zw device: 09, command: 3003, payload: 00 0C , isMulticast: false
dev:352021-07-08 22:41:16.961 debugUpstairs single light: MeterReport(meterType: 1, precision: 1, scale: 2, size: 4, meterValue: [0, 0, 0, 0], rateType: 1, deltaTime: 0, previousMeterValue: [])
dev:352021-07-08 22:41:14.680 debugUpstairs single light: BasicReport(value:0)
dev:652021-07-08 22:41:12.949 debugAfter zwaveEvent(cmd) >> Parsed 'zw device: 09, command: 3105, payload: 01 0A 00 4B , isMulticast: false' to ['value':'24', 'unit':'C', 'name':'temperature']
dev:652021-07-08 22:41:12.931 debugAdjusted temp value 24
dev:652021-07-08 22:41:12.921 debugAfter zwaveEvent(cmd) >> Parsed 'zw device: 09, command: 3105, payload: 03 01 01 , isMulticast: false' to ['value':'1', 'unit':'lux', 'name':'illuminance']
dev:652021-07-08 22:41:12.916 debugPST02: SensorMultilevel SensorMultilevelReport(precision:0, scale:1, sensorType:1, sensorValue:[0, 75], size:2, scaledSensorValue:75)
dev:652021-07-08 22:41:12.905 debugPST02: SensorMultilevel SensorMultilevelReport(precision:0, scale:0, sensorType:3, sensorValue:[1], size:1, scaledSensorValue:1)
dev:652021-07-08 22:41:12.900 debugparse() >> zwave.parse(description)
dev:652021-07-08 22:41:12.896 debugparse() >> description: zw device: 09, command: 3105, payload: 01 0A 00 4B , isMulticast: false
dev:652021-07-08 22:41:12.878 debugAfter zwaveEvent(cmd) >> Parsed 'zw device: 09, command: 3003, payload: FF 0C , isMulticast: false' to ['name':'motion', 'value':'active', 'descriptionText':Front sensor is active, 'isStateChange':true]
dev:652021-07-08 22:41:12.872 debugPST02 Motion Detected
dev:652021-07-08 22:41:12.868 debugPST02 cmd.sensorValue: 255
dev:652021-07-08 22:41:12.864 debugPST02: SensorBinaryReport SensorBinaryReport(sensorValue:255, sensorType:12)}
dev:652021-07-08 22:41:12.836 debugparse() >> zwave.parse(description)
dev:652021-07-08 22:41:12.833 debugparse() >> zwave.parse(description)
dev:652021-07-08 22:41:12.828 debugparse() >> description: zw device: 09, command: 3105, payload: 03 01 01 , isMulticast: false
dev:652021-07-08 22:41:12.823 debugparse() >> description: zw device: 09, command: 3003, payload: FF 0C , isMulticast: false
dev:352021-07-08 22:40:05.338 debugUpstairs single light: MeterReport(meterType: 1, precision: 1, scale: 2, size: 4, meterValue: [0, 0, 0, 149], rateType: 1, deltaTime: 0, previousMeterValue: [])
dev:352021-07-08 22:40:00.597 debugUpstairs single light: BasicReport(value:90)

thebearmay · July 9, 2021, 10:29am

At the bottom of the device page there should be section that is labeled In Use By, any apps/rules in that section would be your first suspects - look for one that appears under both the motion sensor and the light(s) in question. If nothing is showing there you may want to reboot your hub to clear out anything that could still be cached in memory.

alex2 · July 10, 2021, 7:10am

I did check there. There's only one Rule Machine rule that uses both and it's action is different.

I also did reboot hub multiple times. Even tried shutting it down and starting it back up just in case. Also updated firmware recently.

Sebastien · July 10, 2021, 10:09am

Can this light be controlled by Alexa or Google Home? Alexa has a new feature that automatically adds automations based on user habits… I wonder if this could be the cause…?

bravenel · July 10, 2021, 2:28pm

Try removing the device from Alexa, and see if that fixes the problem, at least as an experiment. You can change a setting in the Alexa app to stop “hunches”.

alex2 · July 10, 2021, 11:43pm

I did confirm that there are no routines that use both of these devices, but just to be absolutely sure I excluded the light from devices exposed to Alexa and the problem persists.

Edit:
I also removed IFTTT integration just to be 100% certain even though I don't really use it anyway.

bravenel · July 11, 2021, 12:14am

So there is nothing showing on the device page for In Use By?

bravenel · July 11, 2021, 12:27am

Could you have a Z-Wave association between these two devices? You might remove one, exclude it, reset it, then rejoin it.

aaiyar · July 11, 2021, 12:49am

Could you post a screen shot of this rule and also it’s event subscriptions?

alex2 · July 11, 2021, 4:58am

I lied a bit. There are 2 rules, but they are related to each other so I forgot they are separate rules. Screenshot for both attached. I didn't have any logging enabled for either so I don't have any event subscriptions. Not sure if I understood your request correctly though.

alex2 · July 11, 2021, 5:01am

I am using this light in a bunch of rules, but only the two I posted screenshots above ALSO use the sensor that's triggering the light to turn off. The rest are just button triggers.
This is what light is used by:

This is the sensor:

I do not. I avoid direct z-wave associations specifically because they are difficult to track.

bravenel · July 11, 2021, 2:59pm

So, disable or pause those two rules for a test... And turn on logging for both, all logging.

alex2 · July 11, 2021, 8:14pm

That was it. I did not completely understand how Rule Machine operates. First rule was constantly triggering on motion regardless of mode and second rule was immediately passing the wait for mode condition.

I'll rewrite the rule or find something else if I can't work around the limitations of Rule Machine.
Thanks everyone for your help!

bravenel · July 11, 2021, 9:03pm

Hardly a "limitation", that it does what you told it to do! Suggest you lose the Other Triggers trigger, and use Run Action instead from the first rule, at the point where you actually want it to happen.

bertabcd1234 · July 11, 2021, 9:51pm

I assume you might end up rewriting this anyway, but it should also be noted that the "Stop Repeating Actions" in your second rule will not affect the repeat in the first, which I assume was your intent. This action applies only to repeats within the same rule. You could use the "Cancel Timed Actions" action from the second rule and invoke it on the first rule (this is one of few actions that lets you pick another rule to invoke the action on, and it technically affects more than repeats, as indicated in the UI, but shouldn't matter in this case).

If you explan what you're going for (in plain language, not RM), you might also get some ideas from the community. For example, it looks to me like you might be able to just put this all in one rule and eliminate any of the above complications (the action after END-REP will only be executed after the repeat is done, so no need to put them in a separate rule just to get that outcome), but it depends on what you really want. Good luck, and glad you got this much figured out!

alex2 · July 11, 2021, 9:54pm

Very simple:
I want a light to flash when I get home and mode is set to away to remind me to turn off the alarm.
I then want it to stop flashing once I set mode to home.

Thanks.

bertabcd1234 · July 11, 2021, 10:25pm

Maybe something like...

neonturbo · July 11, 2021, 10:38pm

BPTWorld's The Flasher app might do most of what you want, either by itself, or with just a basic rule to toggle a switch.

alex2 · July 12, 2021, 5:51am

RM doesn't support logic on triggers or having multiple required triggers. These are the limitations I was talking about.

I think I can work around them knowing more about RM though, but it looks like The Flasher does exactly what I want with no effort. Thank you

Testing for presence (I assume it uses Geo fencing) sort of makes sense, but

I want intruders to also immediately know alarm is active.
I don't want to forget to disarm just because I forgot my phone somewhere.
If I do have my phone it'll disarm the alarm automatically so I don't need a reminder anyway.

Thanks again for your help everyone. I'll stick with Flasher for now unless I need more advanced functionality.

bertabcd1234 · July 12, 2021, 6:13am

To be clear, my device was named "TEST Presence" (a virtual sensor I used to write this rule)--there is no "testing" going on, just a regular trigger: when the event happens, the trigger fires, and your rule actions run. You said you wanted this to happen "when you come home" and this was my best guess, so if you're not using a presence device to do that, just trigger on whatever event corresponds to that for you (maybe a specific motion sensor becoming active or a door/contact sensor opening?). Other than this, I believe the rule should do exactly what you asked.