What's the current state of Kasa devices going "unavailable"?

I’ve done some research and from what I can tell: (1) there was a very recent Kasa API change that that broke HA but only impacted UK users, (2) there’s been a long standing issue in which Kasa devices go unavailable given enough time.

I think I’m fighting #2 as reloading the integration works for a few days. I saw mention of a rewritten Kasa library from back in Sept. I think the PR got accepted. How can I tell if I’m running the latest Kasa integration and is there confirmation that this has fixed the issue? I also saw a comment that assigning them a static IP address helps, but it wasn’t clear if that’s confirmed.

Unfortunately, if I can’t get this resolved. I’m going to have give up on HA for the time being. I have too many Kasa devices and the reliability makes this a non-starter for the family. I’m not happy with Kasa (lack of openess as well as back peddling on HomeKit support) overall so long term I’ll be moving away from them picking up other options as I see good deals pop-up.

I have about 30 Kasa devices. Since assigning static IP addresses, I’ve had no problems.

I only have a few TP-Link devices, but at some point in the past month or two the problem of them showing up “unavailable” has stopped.

It seems TP-Link devices, and the HA integration, and frankly WiFi-based devices in general, are sensitive to network reliability. I can’t help but wonder whether 30 of them on the same subnet would make it worse. Especially, if there’s other normal traffic like streaming video on the same network. Obviously I don’t know how much effort you’ve put into network design, so I’m only speculating.

Oh, and… Yes, it’s essential that they have static IP addresses. Some have reported better results hard-coding the IP addresses in configuration.yaml, too. My experience is the exact opposite. So try it both ways.

Thanks for the advice. I just set all my devices to static IPs. Let’s see how it does