I’m experiencing this problem with Android TV Remote integration on HA 2025.3.3.
I’m having the same issue with most of my Kasa devices and haven’t found anything in this thread that works for me.
Has anyone solved this yet? It’s very annoying and extremely unwanted.
was hoping they’d be a fix for this since it’s been ongoing for a year. alas, no 
i’ve got maybe 12 ESP’s of varying models registered with HA for many months without issue (maybe 40% of them are currently online). These have DHCP reservation IP’s set.
I received the HA Voice PE today, went through the setup and started to notice this warning.
Weirdly, the first occurance is being reported on one of the offline ESP devices. Figuring i had something else wrong i set the HA Voice device to a new IP, as DHCP reservation. The error changed to a DIFFERENT ESP device (also offline).
current error:
But when you actually click the repair message, it changes info to reference the HA Voice device:
Clicking submit will only make the error come back again.
HA Voice has not been “taken control” in ESPHome Builder at this point.
I’ve now just “taken control” in ESPHome Builder, repaired the message and after a few minutes the error comes back.
looks like i’ve got it sorted.
the device(s) that were coming up as the “authentication expired for $device” were re-flashed and the messages have not returned for about 40minutes now.
not sure if it had something todo with using unique API keys or not, but i still don’t understand why 1 device was causing this issue, especially offline devices. Devices were all within a DHCP range, so maybe something HA is doing with last-seen-IP caching? no idea. I’ve also updated to the latest HAOS 16.0 this morning too.
Hope that helps some others getting rid if this error.
Running HA Core 2024.8.1, Frontend 20240809.0 (from docker homeassistant/home-assistant:stable “/init” 12 days ago Up 23 hours homeassistant)
Two ESPHome devices.
After a power outage, got the “Authentication expired”.
Both devices have unique names and API keys.
First time, trying to re-auth rejected the correct keys. but it accepted the wrong (swap first with second devices) key. But nothing worked. Not totally surprising, since they are two (slightly) different devices; one a 16A, the other a 20A relay.
A few minutes later, the error popped up again (no reboots of server or devices). but this time they accepted the correct keys, and everything started working again.
We experience power outages regularly, so this is a problem.
Just popped a breaker and had all 5 of my Kasa/TP-Link HS-300s in the room do exactly this. I know the username and password are correct. It does not make any sense.
On 2025.10.
VERY frustrating.
That is on for me…
I have been having issues with this for a TP Link Occupancy Sensor Dimmer. What seemed to work for me was making sure all my TP Link cloud accounts where logging in with the same accounts. The Tapo App and the Kasa App can both manage your TP link devices. However the Tapo App can manage a bit more. I am assuming if you reset a password somewhere things get out of sync.
Once I reset my password on my TP Link account I logged into all the apps again and that seemed to fix it. I also have TP Link Omada which uses the same credentials also.
The only way I have been able to get this to work is to turn off 3rd party compatibility for over 1 minute, then turn it back on. VERY frustrating. TP-Link did something flaky in their code because this used to work and it seems by doing that, you reset that third party ability to get into the devices.
Thank you, I can confirm this worked for me.
Toggling this worked for me
Sept 2026 here. I never had this problem and it popped up today for me. Your reply was the one that got things working for me. All my TP-Link lights were showing the auth error, though the TP-Link wall switch was still working. This has me worried as it seems that these lights abosultely need:
- A working internet connection to operate properly. I had tried restricting the lights to LAN only when I first got them, with no WAN access, but there was constant problems with the lights untill WAN access was restored.
- A connection to TP-Link servers. Nothing has changed on my network in months, yet somehow every TP-Link light suddenly stops working?
Those 2 points makes it obvious that unless there is a constant connection to TP-Link, these lights at some point in the future will stop working properly. Maybe they can continue as dumb lights, but that it not why I purchased them, and would make them useless when TP-Link decides to stop supporting the lights and cut them off, unless there is something done to make them open. My next action is to search for any custom open firmware that can be flashed on these lights to free them from TP-Link control.