Kasa Plug Switch does not trigger app

🛎️ Get Help
1

C8 Pro
Platform: 2.4.3.177
IP Address192.168.0.254 (Ethernet),
192.168.0.24 (WiFi - home)
Most devices are Kasa with the occasional Tapo.

I had automations set up using the Kasa built in. I reset all the switches and other devices and reinstalled them when I added the hubitat.

All the devices show up in the Hubitat device page.

All of my devices show up on the Tapo phone app and respond appropriately. Some of my devices work just fine following rules. Some rules work well when triggered with "run now" but the major problem seems to be that most of the switches do not trigger the rule.
One HS200/5.6 consistently works triggering a basic rule.
Another HS200.5.6 will not trigger a simple rule.

Rules that are triggered by the hub (sunrise/sunset) work well.

What can I do to get the data needed to fix this?
Thanks

bill

2

I noted the directions to not have wi-fi and ethernet connected simultaneously. I disconnected the wi-fi. Early testing shows no improvement.

bill

3

How are you turning the Kasa devices on/off -- most notably, are you doing so through the Hubitat hub somehow, or are you doing it with the Kasa mobile app; Alexa, Siri, etc. (with a native integration); or something else?

2 Likes
4

Note, the triggers for automations are based upon the driver sending the hub event, which is the trigger that is used. That event is sent when the attribute value in the driver is updated.

You should see on the driver page for the device, that when the automation does not trigger, the driver did not update the attribute. The switch attribute in the driver should update when you change the state of the switch.

So, confirm that the Hubitat driver is actually working, it sounds like it is not. Turn on debug logging for the driver and see what kind of logs it gives when you expect it to update from a state change.

5

Thank you [chrisbvt] and [bertabcd1234].
Combining the information you both provided gave me the answer.
I had been thinking that the automation was triggered by the sending switch not the hub event. So, changing my mindset it is clear that I was sometimes changing the device state by using the Tapo phone app, which, of course did not change the Hubitat state and therefore did not trigger the automation. If I use the device page to set the initial condition it does change the hub state for that device and the automation does trigger when the state changes.

Thank a lot to both of you.