Continuing the discussion from [RELEASE] Switch Bindings:
So, if you are referring to a manual change of switch state, i.e. you went up to the switch and changed it, since the Kasa devices are WiFi based, they do not report their status upon change and rely on polling to detect physical changes. If you look in the device page for the Kasa device you will see an option for Quick Polling, one note, you likely want to balance responsiveness with flooding your network with poll requests.
Good response. One add is you could possibly use the Kasa Skill in Alexa linked to a virtual switch in Hubitat via Kasa Routines. Not tested, just an idea.
Haven't logged on to the forum for a while, but thanks! This was the issue and I was able to find a workaround.
what work around did you end up using? I'm having the same issue where the state of the kasa switch isn't updated in Hubitat
Don't think there is any "workaround" you just have to enable polling on the device you want to bind. I have all 3 of my dimmers set to 5s polling.
The state should update at every poll interval (default to 30 minutes). And if you activate a switch/bulb through Hubitat, within 1 second. To capture someone MANUALLY pressing the switch, the 5 second poll gives a max response of 5 seconds (average < 3 seconds). The Kasa Phone app uses 3 second polling for device status update, so slightly faster.
Recommend you do not go below 1 minute unless you have a use case (i.e., you want a manual activation of a switch to cause some follow-on activity.
great thank you for the detailed response. I'm trying to have one wall switch trigger a couple of kasa devices - basically all the lights in an area turn on/off with one manual press of a kasa switch. So the I think for the switch binding to work I would need to decrease the polling interval to as low as possible? Otherwise when someone presses the master switch, they will have to wait 1 minute before the other lights turn on?
You are correct - rapid polling is needed for a manual operation of a Kasa switch to trigger other devices. Rapid polling multiple LAN devices can bog a Hubitat down, and that is one reason why @djgutheinz probably recommended more conservative polling. I agree with his recommendation.
The use case you describe would benefit from switches that directly report their state back to Hubitat - like z-wave+, zigbee, or Lutron devices.
I would recommend that also. I have one of the Kasa switches that was gifted to me, I use it in a place where I only want to turn that switch itself on/off via automations but I never need to know its current state very precisely so I just have it on 10min polling.
just reread your post - so if I'm understanding correctly, in terms of speed, there is no advantage for me to move all these lights/switches/plugs over to hubitat, and just keep using Kasa cloud for the binding automation correct? Only advantage of hubitat would be the local operation of the automation, so if my ISP goes down the automation will still work?
Maybe its time to invest in a bucket of Z-wave devices...
Correct.
Or Zigbee (or Lutron).
As others have said more eloquently, there was no perfect solution. I took out a kasa switch and put in a z-wave device to control the kasa device I wanted to use through switch binding. I did not want to slow down the hub with frequent polling.
Hi what is the delay time with your setup? Like from when you press the z-wave switch to when the kasa devices turn on?
There is a delay (the lights won't come on at exactly the same time) but tends to be around 250 ms.
It’s useful to bear in mind that automation times for the z-protocols are strength of mesh dependent.
This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.
Download the Hubitat app
