Open ghostseven opened 3 years ago
This issue is due to TP-LINK firmware update (ver 1.1.0). This only impacts HS100/HS110 (UK) Hardware Ver 4 variants.
Essentially, as others above have already discovered they have blocked access to the local api port.
There is/was a temporary beta firmware available on request (ver1.1.1)
You would request via a support ticket to support@tp-link.com and tell them the MAC address for the plug.
Unfortunately, they have stopped pushing this beta firmware since early Feb 2021.
Link here on the Home Assistant forum which has some good info https://community.home-assistant.io/t/tp-link-offers-way-to-add-local-api-back/248333/2
Issue thread here (specifically wrt Home Assistant but it's the same root cause) https://community.tp-link.com/en/smart-home/forum/topic/237614
Link to TP-LINK announcement about beta firmware 1.1.1 https://community.tp-link.com/en/smart-home/forum/topic/239364
Firstly sorry to post here about a different plugin, if this is not wanted I can remove it.
I have as of today, got a very hacky method (it calls command line methods of kasa) to get these plugs (HS100, HS110 HW:4.1 SW:1.1.0) working on homebridge. It is based on the work of @SimonWilkinson, who has done some fantastic work with the python-kasa repository. None of this is on a proper repo yet and it requires some manual install of a forked version of python-kasa and my plugin for homebridge.
You can look here https://github.com/ghostseven/homebridge-hs-plug for the plugin and here https://github.com/ghostseven/python-kasa for the fork of python-kasa. There are no full instructions yet but feel free to open issues on my repo to ask questions. I will try and write something up soon(ish).
Thanks @ghostseven. That's very good to hear. I just grabbed the code from the links and will take a look later on.
BTW: I appears the HS100/HS110 HW: 4.1 are now on the way out. Retailers here in Ireland are being told that are entering 'discontinued' status. Appears TP-LINK are replacing them with the Tapo branded plugs instead.
@ghostseven Hi Blake, When you have time I'd love to see the instructions for this. I cloned your repo (and Simon's but can quite figure out how to merge your changes into the python-kasa project. Thanks.
Sure, if you clone my fork of python-Kasa that should have the changes. (It was broken due to hs100 plugs not having energy meters).
I will try and write some instructions up soon :)
Thanks
Blake On 27 Feb 2021, 22:05 +0000, cliffordm notifications@github.com, wrote:
@ghostseven Hi Blake, When you have time I'd love to see the instructions for this. I cloned your repo (and Simon's but can quite figure out how to merge your changes into the python-kasa project. Thanks. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or unsubscribe.
@ghostseven Hi Blake - good news I got this working! Many thanks!
So, for the benefit of anybody else the arrives in the thread, I had one of my TP-LINK HS100(UK) Ver4 plugs that had been upgraded to firmware 1.1.0 (this version of the firmware shut off port 9999 and basically hoses local control of the plug - except via the official TP-LINK Kasa app. Using above instructs from @ghostseven I've once again able to gain control locally. (i.e. not using the Kasa app or using the tp-link cloud service)
Most importantly via command line using the python-kasa app. I've verified I can retrieve state from my device as well as toggle it on or off as needed.
Thanks again Blake. You're about to make a lot of people very happy over on the Home Assistance forums too :)
That is great news! I am sitting down today (currently in progress) writing up a more complete guide (it will be on GitHub) and getting the plug-in published on npm. That should make it all a bit easier!
Thanks
Blake On 28 Feb 2021, 14:07 +0000, cliffordm notifications@github.com, wrote:
@ghostseven Hi Blake - good news I got this working! Many thanks! So, for the benefit of anybody else the arrives in the thread, I had one of my TP-LINK HS100(UK) Ver4 plugs that had been upgraded to firmware 1.1.0 (this version of the firmware shut off port 9999 and basically hoses local control of the plug - except via the official TP-LINK Kasa app. Using above instructs from @ghostseven - I've once again able to locally. Most importantly via command line using the python-kasa app. I've verified I can retrieve state from my device as well as toggle it on or off as needed. Thanks again Blake. Your about to make a lot of people very happy over on the Home Assistance forums too :) — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or unsubscribe.
@cliffordm I have published the plugin now and there are better instructions. I hope this helps!
@cliffordm I have published the plugin now and there are better instructions. I hope this helps!
Maybe a duplication or similar to https://github.com/plasticrake/homebridge-tplink-smarthome/issues/153
All HS100 Hardware V4.1 devices suddenly stopped working (work fine from Kassa App). Have reset them, have tried different versions of plug-in and config settings. Even manually specified devices. I have also reset homebridge. They now do not discover or show up.
I think this is possibly due to a firmware update from TP Link. I have a selection of HS100 devices some on hardware 2.0 and hardware 2.1 (these are all working).
Expected Behavior
The device appear in discovery or when manually specified
Current Behavior
Device does not appear
Steps to Reproduce (for bugs)
Setup a HS100 with hardware V4.1 and Firmware 1.1.0 device will not appear.
Versions
node --version
v12.19.0homebridge --version
1.2.3Configuration
Homebridge Log / Command Output