tplink-energy-monitor icon indicating copy to clipboard operation
tplink-energy-monitor copied to clipboard

Anyone having detection issues with Firmware 1.2.5 HS110?

Open jheleniak opened this issue 5 years ago • 7 comments

Trying to detect with firmware 1.2.5 and cannot see devices. Is it just me or an issue?

jheleniak avatar May 22 '19 17:05 jheleniak

Yes, same here on Win 10 with HS110

EDIT: Now on firmware version 1.5.5 but was able to get the application running on Windows using Node and NPM method mentioned in the README rather than using the Windows zip package.

trystanj1 avatar Jun 13 '19 16:06 trystanj1

Yes, Same here unfortunately.

alexanderfitu avatar Jul 12 '19 21:07 alexanderfitu

NB I am on firmware version 1.5.7 HW version 2.1

alexanderfitu avatar Jul 13 '19 20:07 alexanderfitu

I'm having a similar problem except it will find ONE of my HS110's on v 1.2.5, but it won't find the others. I have a total of 4 x HS110's and 1 x HS100 (which it finds but ignores as it doesn't have powering monitoring).

EDIT: A little more digging and the devices that can't be found aren't pingable but the other 2 are, which is odd since they're all on the same wifi network. I also notice that port 9999 is no longer open on the devices that are not being found. It looks like TP-Link has done some odd security update which looks like the API might have been removed?

EDIT 2: Ok, a bit more digging .. all my devices still respond on port 9999/tcp, however, only 2 of them send back clear text json. The other 3 that I really need to work are only sending back some sort of encrypted data. Many other smart plug makers use AES encryption and now I'm wondering if TP-Link is rolling it out for their devices? I can't find anything on TP-Link's site. Whatever has changed it's broken my scripts used to control my sockets :(

M1XZG avatar Jul 31 '19 17:07 M1XZG

Same issue with HS110 firmware 1.5.7, hardware version 2.1

manU135790 avatar Aug 05 '19 11:08 manU135790

Anyone resolve this? I haven't found a way to manually downgrade the firmware, assuming that would fix it.

esadun avatar Nov 08 '19 20:11 esadun

I thought I had the same problem. However using another PC (on the same network) no problem at all.

jpveen avatar Jun 06 '20 10:06 jpveen