8000 HS110(UK) not discoverable · Issue #113 · python-kasa/python-kasa · GitHub
[go: up one dir, main page]

Skip to content

HS110(UK) not discoverable #113

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

Closed
robJolley opened this issue Nov 10, 2020 · 8 comments · Fixed by #147
Closed

HS110(UK) not discoverable #113

robJolley opened this issue Nov 10, 2020 · 8 comments · Fixed by #147

Comments

@robJolley
Copy link

UK smartSwitxh HS110(UK) is not discoverable, it can be accessed using its IP address. it is missing from tests\fixtures

@rytilahti
Copy link
Member

Could you try to remove the other query elements besides system:get_sysinfo from the discovery.py and try if the discovery works then? There is discussion (#105) that some newer hardware/software revision may not function like the earlier ones, breaking the discovery query that is being used currently.

Did it used to work, or have you had success with other tplink devices previously? The discovery uses broadcast, so if the devices are in a different network than where you are trying to do the discovery, you have to adjust the discovery target address (currently only available using the API, if you are using this as a library you will have to adjust the target parameter for the discovery() call).

@deosrc

This comment has been minimized.

@badguy99

This comment has been minimized.

@SimonWilkinson

This comment has been minimized.

@rytilahti

This comment has been minimized.

@SimonWilkinson

This comment has been minimized.

@wilsonnkwan

This comment has been minimized.

@rytilahti
Copy link
Member
rytilahti commented Nov 16, 2020

Check out the linked softScheck/tplink-smartplug comment thread, @chriswheeldon seems to have figured out much of the new protocol already.

edit: I'll hide the irrelevant comments from this thread, #115 is for tracking the new protocol. The issue original reporter has nothing to do with this as it is only discovery that was not working.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

6 participants
0