Hey all, I have recently come to recognize a situation that should never be happening.
I have a KP400 outside controlling a couple of things, one of which is the pump in my pond, this should never be turned off, as if this happens, water will flow backwards through my filter/pump and will cause an overflow due to low ground.
If you look at the logs of this plug, I see it's turning off every morning precisely at 7:30am.
when I look at the device there are only dashboards and a PING application using it (Ping is to warn me if it goes offline, oddly enough, it's only warning me when it goes back online, but that's another matter)
I'm at a real loss here and would appreciate any assistance.
I don't know anything about Kasa, but I would look at the following: the unfiltered logs around the time the device is turned off, and the device events page to see if you can tell what is triggering it.
These are WiFi and/or other app driven, correct? Is it possible there's an old schedule on another system lingering about?
I can honestly say I've never looked at the logs unfiltered, definitely some interesting things there. You are correct, it is WIFI controlled and integrates into HE via an app. I confirmed my phone has no mysterious schedules either.
I might be worth nothing last weekend there was a fairly major power outage, and I wonder if this isn't a result of that.
On the device page, click the events tab.
If something from within HE called the "off" command on the device you will see it listed in there.
For example this is showing my rule named "Holiday Lights Automation" turned this Kasa device off at 7:04 am. Ignore the second command-off (above), that is just a secondary delayed command in the rule in case something did not turn off the first time.
Hmm oddly enough to me, it appears the "check" I have running might be the cause, it says as digital, but this appears to be it, assuming I'm reading it right.
You can actually check the power state by doing a simple REFRESH or ON command of the Kasa Device from within Hubitat. At the same time, also check the state.errorCount and the attribute "commsError" on the device. They should be 0 and false (respectively).
If something called the off command on the device it should show "command-off" in the name column.
Think through any other apps you may have logged into your Kasa account with. Alexa, IFTT, etc... it could be integrated through the Kasa cloud and not via HE.
You could cut that off by disabling the "Cloud Binding" on the device page. That should then only allow local control via HE or the Kasa app, anything else would be cut off.
Also make sure to check the Kasa app on your phone to make sure you haven't accidentally setup a schedule through it. Could also use it to check for firmware updates in case there is a firmware bug.
Pretty sure we are on the same page for the most part. I think I will disable the "check" today, and watch tomorrow what happens when I"m at work tomorrow.
