The device is Kasa KP115 with set poll interval at 1 minute with latest driver from HPM.
The rule says if power has become <10.0 for one minute turn the switch off. This rule does not fire when the conditions are met.
I have a rule in basic rule to notify if switch is turned off. This rule works.
I also have a rule in Rule 4.1 that says if the power reports <10.0 to turn the switch off. This rule works.
Any ideas on why one would work and not the other?
I don't know if I can help you, but someone else can probably do it if you post a screen shot of the rule that doesn't work.
Turn on logging for the one that doesn't work, and post a screenshot of the logs here. Also, look at the App Status page (gear icon, upper right of the app page), and take a screenshot of the Event Subscriptions section, post it here.
The switch did not turn off.
That's probably an issue with the switch. Can you turn it off from its device page?
Yes I can and the device page updates immediately. I also have the simple rule to notify me when the switch is off and that fires every time as does the rule in Rule 4.1 that says if the power reports <10.0 to turn the switch off
OK, so the Basic Rule logs that it turned the switch off. Please look at the device events for that time (Events button on top of the device page), and see if there was an event at that time or not.
I just tested this and it works for me as expected:
Below, you can see where I turned on "a color bulb', then ran the rule. It turned off at 5:33:49,313 and the app's logs shows turning it off at 5:33:49.280.
I'll try the same rule with a different plug and report back the findings. This seems to be the only variable in the mix.
I tried the same rule except using an Iris V2 ZigBee plug and the rule fired as expected. So the question becomes why is the Kasa plug failing this rule while being controllable from the device page and works in another simple rule and in Rule 4.1?
You've pretty well established that it isn't the Basic Rule that is the source of your problem.
I would suggest that you examine the device events for clues. You mention the device has to be polled. Could that have something to do with it? I suggest you take this up with whoever wrote the driver for it. Turn on debug logging in the driver, etc.
Since problems usually show up when an app doesn't do what we expect, there is a tendency to identify the app as the source of the problem. Sometimes this is true, and often it is not true, as it is a device issue we see as an app failure. That's the case here, so I changed the title of the post accordingly,.
Thank you for looking at this. I did post this in the thread of the driver announcement but didn't here anything.