@hilbrand, thanks for the heads-up.
It does appear that there has been some talk over on HA github pages about adding support for the new encryption protocol on these devices? https://github.com/python-kasa/python-kasa/pull/117
Just an FYI in case you were not already aware.
Has anyone else had issues with more than just HS100 and HS110? the TPLink forum posts seem to claim that the related firmware update is limited only to UK-sold HS100 and HS110 models. But my experience over the last few days is that in addition to HS100 and HS110 not working, now I have at least one of each models HS105, HS200, HS210, and HS220 not working. I have bought many of them on eBay, so it’s possible that they are grey market UK, but they are all USA plugs so I find this very improbable.
Everything that is not working seems to have TCP port 9999 no longer open
The weird part for me is that I do still have 1 x HS105 and 1 x HS210 still working from OpenHAB. NMAP shows them as having tcp port 9999 still open. But for both of those devices still working with OpenHAB, the Kasa app shows them as having identical HW and FW revisions to other HS105 and HS210 devices in my network which no longer are working with OpenHAB, and whose port 9999 show as closed in NMAP.
I’m pretty disappointed in TP-Link for this, although I work in software myself and I am sympathetic to the idea that sometimes stuff gets broken. I guess I’ll wait a bit to see where this goes, but at this point, the Shelly.cloud stuff is looking very attractive as a replacement for TPLink. Their stuff is cheap, they advertise an open and local API, and the single Shelly 1PM device I have has worked consistently for me so far…