-
Notifications
You must be signed in to change notification settings - Fork 298
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unable to communicate with the HS110 plug anymore #70
Comments
Can anyone reproduce the problem? Can it be that TpLink has changed teh port number or the key? |
Sorry again guys! I have rebooted the router and I could access again the smartplug. I managed to send only one shutdown command successfully but not a second time. The plug returns again: "Cound not connect to host 192.168.1.2.:9999". Does anyone experience the same problem or my plug goes in conflict with another application that uses the port 9999? Is there a way to tell the plug to listen on a different port? |
I have the same issue. |
i tried now over udp with the tppd-client wihtout success. Quite annoying that tp-link does not offer any support for automatisation. |
@Hir0-84 just out of curiosity: why did you make the firmware upgrade in the first place? |
personally I didn't know there was a nice exploit like this, and anyway, there is a big button named update firmware it makes you want to press it. but it was a good lesson |
Haven't tried this myself but there are instructions for local upgrade online, so these just might work for a downgrade too. Of course the new firmware might specifically check for a downgrade and prevent it. |
Even a simple command to get the system info:
python tplink_smartplug.py -t 192.168.1.2 -p 9999 -j 'info'
returns "Cound not connect to host 192.168.1.2.:9999".
Recently I have installed the new firmware update v. 1.5.6 for the HS110 2.0 model. Could that be the reason?
I have also noticed that recently you have pushed a commit giving the possibility to pass a different port number. Did TPLink change the port? Btw, I have tested the latest version of the script and I still get the same error message.
The text was updated successfully, but these errors were encountered: