How do you use it without an account. The stupid thing made me create an account before I could set up anything. Luckily I read this thread and blocked the devices access to the internet as soon as I set it up so it shouldn’t auto update (and is working great so far).
Thanks for this. So probably just a weird coincidence. All except for one are back and working fine now. I’ll have to make sure they are blocked from any updates to keep it that way!
1 Like
After installing the Kasa for Mobile App (Android), select “Create an account.”
You can then select “Skip” at the bottom of the “Create an account” page.
Presumably the iOS app works similarly.
AWWWWWW! I missed the skip button. Darn! Now I’ll have to set things up again without an account. I’ve blocked my switch from accessing the internet but still…
If you can get the plug to return back to the factory state (i.e., opening the wifi ap), you can also use python-kasa to provision it: https://python-kasa.readthedocs.io/en/latest/cli.html#provisioning
There is also a PR (as mentioned also previously in this thread) that promises to add support for the new protocol, so all is not lost (yet), it will just take some time to make these things happen: https://github.com/python-kasa/python-kasa/pull/117 
2 Likes
This can be done by holding the cog button on the top of the HS100/HS110 for about 10 seconds. Note: Must be more than about 5 as this is the smart config reset that doesn’t erase all settings.
1 Like
To all who are waiting for / needing plug downgrades:
I got fed up of waiting for mine to downgrade so I emailed again and just got this:
Sorry for the delay.
I consulted the senior engineer about it. Currently, the notification is not pushed cause we need collect more users. But it is in process.
Apologize for any inconvenience.Best Regards
Olivia Ding
So it looks like they are collecting as many affected users as they can before the push.
Please can anyone and everyone with this issue email [email protected] and give them MAC addresses of affected units and their Kasa account email if you have not already done so.
Thanks 
1 Like
Been following along with this thread, got my 3 HS100’s out today as I only use them for Christmas decorations. Re-provisioned in the app and then blocked from internet access so they didn’t update, all turned up in HA fine with the integration. I’m still on really old firmware so no point in contacting TP-Link to role back. 1 is HW 2.0, FW 1.5.8, 1 is HW 2.0, FW 1.4.4 and 1 HW 1.0, FW 1.2.6 so a right mixed bag. Will be looking forward to the fix so I can update with confidence, although don’t see the point in unblocking their internet access now.
1 Like
As an aside…
I had a pile of HS100s. One got upgraded (gosh, that sounds like a Cyberman reference), and reset the others to be on a non-account setup, as suggested as an workaround.
Should anyone do this, just be aware that any upgraded plugs can be added back into the app, but will then disappear, rendering them useless.
That essentially means that an account is now being enforced, just to use any plug on the latest firmware.
Oh, wow. Are you saying that you can’t control the updated plug via the TP-Link Kasa app unless you’ve set an account in the app? Even after a reset to re-pair it?
That’s ominous. If true, that reinforces my concern that TP-Link’s direction may be to disable what they called “unauthorzied” apps (anything but Kasa and their cloud.)
Yep. A bit rum.
I’ve been looking at updating the python-kasa library with support for the new protocol. But that work has got a bit bogged down, and python-kasa itself isn’t integrated into Home Assistant yet. So, in the interests of being able to turn my Christmas lights on, I made a quick and dirty fork of the pyHS100 library to support plugs using the new firmware. As there’s no way of supplying a username and password via Home Assistant, the library will only support new-firmware plugs without an account set for them.
Details of how to install the replacement library are in the Home Assistant ticket - https://github.com/home-assistant/core/issues/43088#issuecomment-739513071
So I still haven’t had my plugs downgraded. I’ve received 2 Sonoff S26’s and a further 4 Sonoff S26’s from AE in the time that’s gone by! I want to use some of my TP-Link plugs for Christmas lights, so I emailed again. Yesterday, I got this back:
Dear Customer,
We’re sorry for the inconvenience caused.
Listening to the feedback from customers using third-party smart home software integrations, we have developed Beta firmware that will re-enable the local API communication. Please note that you acknowledge and accept the potential risks associated with integration with local APIs. Please refer to the Kasa user agreement and privacy agreement.
If you agree, please reply “Yes”.
After your agreement, the beta firmware will be pushed to you via Kasa app in 10 working days. We will need your confirmation to continue with the Beta firmware upgrade from the app. Once installed, the Beta firmware will enable you to use third-party local control smart home software and platforms again. We recommend that customers applying the new firmware maximize WLAN security by using complex Wi-Fi passwords and choose the maximum encryption level available.
Thank you for your continued support of the Kasa brand.
PS：
kasa user agreement: Kasa Care Service Agreement | TP-Link
Kasa privacy agreement: Privacy Policy - Kasa Smart Home | TP-Link
Best Regards
Olivia Ding
So I strongly advise anyone with this issue to keep emailing.
1 Like
Cheers, just emailed them again - taking ages to get this sorted!
1 Like
Hopefully it won’t be too much longer!
Reading that, the good news is they acknowledged the problem and it seems they’ve formalized the response a bit. Looks like they got Legal involved in drafting the standard response you received, too.
I guess it’s too early to expect any indication as to their future plans for allowing (or not) third-party integrations. I’d feel a lot safer buying their products if I saw some sort of commitment in writing.
I just won’t be buying their products in future tbh. I have 2 HS100s and did plan to buy some more in the new year, but no matter what the final outcome of this issue it is clear to me that tp-link is not the ‘smart home hardware developer’ that I thought they were.
I’m a great believer in voting with my wallet, and I won’t give money to companies that I disagree with, so they’ve lost a customer in me. Maybe it won’t break the bank for them and they won’t care, but I’ll feel like I did my bit 
2 Likes
Yes, I agree.
Which smart plugs are recomended? (with energy consumption monitoring, of course).
I have a Fibaro Z-wave that is just great, but the price…
Thanks
Bruno
I’d look at ZigBee. These have just popped up at Lidl for a very cheap price. https://www.lidl.co.uk/en/p/product-recommendation/silvercrest-smart-usb-extension-lead/p37577
The Lidl ones don’t appear to have energy monitoring, but are competitively priced. If you look at the Zigbee2MQTT supported devices page and search for energy, there are lots there.
Another option would be to cut into the wire of the appliance if 240v and add a Shelly 1PM… you’d have to put it in a small ABS box or something. You could also make a single gang extension lead with one. These have energy monitoring and are surprisingly cheap for what they are. There’s a Shelly integration in HACS that works well.
Edit: Corrected Shelly 1 to Shelly1PM (PM= power measure)