All TP-Link KL125 bulbs suddenly stopped working with built-in Kasa Integration

I have a current-generation Hubitat Elevation running the latest available platform software. All 11 of my TP-Link Kasa KL125 bulbs recently stopped communicating with Hubitat’s built-in Kasa Integration this morning. Anyone else?

The bulbs are still online and work normally through the Kasa mobile app. They can be turned on and off there without a problem.

Hubitat logs repeated warnings every five minutes: [method:handleCommsError, errCount:644, msg:udpTimeout,
command:{"system":{"get_sysinfo":{}}},
TRY: do CONFIGURE]

did you recently upgrade the firmwares.. it is recommended that you no longer update the firmware as newer firmwares can break the local api

Yes, I probably did a few days ago, but it has been working since then.

Try pairing it to the Tapo app. I had that problem with a few of my Kasa switches about half of them worked on the Tapo app the other switches I replaced with Kasa Matter switches. They're all happy and working with no problems.

The error is indicative of the device not being at the ip address. One thing to check is the device IP in the Kasa phone app and that in Hubitat.

In the phone app, go to the device and find the HW and FW version (and any notes associated with these). I would be interested in what this says. TP-link released new on August 7. So .....

To all - remember, turn off auto update. Kasa is doing some weird things relative to security in devices.

I got it working again, thanks, all. I deleted the app, reinstalled it, and added the devices again, and it seemed to work. I don't know if it was a token issue or what it was.