For over a year, I've been facing an issue where my Hubitat C-7 hub, updated to the latest version 2.3.9.147, loses connection with some of my Kasa devices (such as smart switches) whenever the internet goes down and then comes back on.
To resolve this, I have to conduct a scan for Kasa devices to re-establish their connections. Once done, they function normally again. Could someone please assist me in addressing this frustrating and persistent problem?
One more note: I know the device is not working because I have a very simple routine to turn the switch on and off in Webcore.
The common cause of this "disconnect" is the IP address changing as your router reboots. Per the installation instructions, it is highly recommended that a Static IP Address (DHCP reservation) be created in your router for Kasa devices.
In general, all smart devices should have an address reservation in the router. It doesn't matter if it is a Kasa, Hubitat, or Alexa. These smart devices work better together, and more consistently in general, if they are aware of where they and other devices are located on the network.
I'm having the same problem, but it happens w/out an internet outage. About once every three days, one or more Kasa devices will no longer respond to hubitat commands, so I have to rerun the Kasa integration app. For good measure, I also update Alexa and Google Home apps. All kasa devices have reserved IP addresses. It's driving me nuts!
all static and even though the interface (broken wifi icon) ws showing down.. i could ping all devices fine.. and as i said saving prferences got rid of it.. i think the app itself has a bug and is either not polling or incorrectdly showing down.
So I have been using 3 HS200 and 2 HS220 Kasa switches for about a year.
I have not experienced any issues as you described.
I am using the most recent hub firmware version.
Are you able to replicate this every time by simply rebooting your router?
Do you have the Kasa app on your phone? I just looked at mine; and noticed the HS200 has a firmware update available (1.0.11 to 2.0).
As an aside; my modem has rebooted at least 20 times in the past year, and I've never lost connection to the devices, and I don't use static reservations (I know I should; just haven't had a conflict yet).
I was an IT consultant for 35 years. No, no "rogue" DHCP servers. I have a router and 4 wired access points around the inside perimeter of my home. No device is more than 20 feet & 1 wall away from an AP. DHCP expiration? Do you mean lease times? 48 hours.
And while we're at it, if this is a wifi problem pls explain why I can access and control these devices all the time with the Kasa app (android & windows) even when HE can't.
More data on your Hubitat installation is needed. Specifically:
Kasa Device: Hardware Version
Hubitat Device details :: Current States :: "Connection" and "Comms Error"
Hubitat Device details :: Device Info :: "Device IP" and "DevicePort"
Since I can not duplicate on my system, this is just the first step so that I have some idea on what portion of code to look at.
I think I figured it out. For reasons unknown to me, 2-3 devices are somehow changing to "CLOUD" rather than LAN when I run the Kasa integration. When that happens, HE reports that they are offline. If I manually add the IP and port, they reappear and function normally. I happens w/ plugs, bulbs, and switches.
I'm keeping a daily record of what the integration finds. It'll be interesting to see what happens w/ the devices that I've manually reassigned to LAN.
It happened again. I left the system alone for 2 days and another plug switched from LAN/IP:9999 to CLOUD:CLOUD when I used the Kasa integration app. Before it switched the signal strength was listed as -12 dBm - that's because that plug is about 2 feet from my router.
