search

jamesbarnett91 / tplink-energy-monitor

An energy monitoring dashboard for TP-Link smart plugs
GNU General Public License v3.0
467 stars 104 forks source link

Anyone having detection issues with Firmware 1.2.5 HS110? #41

Open jheleniak opened 5 years ago

jheleniak commented 5 years ago

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

trystanj1 commented 5 years ago

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.

alexanderfitu commented 5 years ago

Yes, Same here unfortunately.

alexanderfitu commented 5 years ago

NB I am on firmware version 1.5.7 HW version 2.1

M1XZG commented 5 years ago

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 :(

manU135790 commented 5 years ago

Same issue with HS110 firmware 1.5.7, hardware version 2.1

esadun commented 5 years ago

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

jpveen commented 4 years ago

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