-
Notifications
You must be signed in to change notification settings - Fork 102
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
change network communication port? #73
Comments
TPLink HS110s have also updated their firmware now, and closed the port. |
What do you mean by that? |
https://community.home-assistant.io/t/tp-link-hs110-smart-plug-disappears-after-latest-firmware-update/244229?page=2 |
Oh, that's terrible news, let's hope that there will be a solution. |
Since a few days, I do not get any of the plugs. However, I do not live in the UK and do not have the new firmware installed (HS110, HW 4.0, FW 1.0.4). Any ideas what could be the issue? The HS100 are also not detected (I know they are not in the GUI, but on the command line they were found). Very sad, cause my 86 old grandfather used to look on the monitor several times a day to check his solar panels. Are there any other tools out there which could be used instead? |
try restarting the Docker instance, if that is what you use. |
of course I tried that already, using compatibility mode, as admin, disabled firewall,... nothing helps! I am using Windows 10. |
would it be possible to change the port used to communicate with devices from 9999 to 6668? or, better, have the software attempt communication on both ports?
I have devices from another manufacturer that work with other applications designed for tplink, as well as tplink devices, but they do use the non-standard port of 6668 instead of 9999.
The text was updated successfully, but these errors were encountered: