-
-
Notifications
You must be signed in to change notification settings - Fork 3.6k
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
[tplinksmarthome] Add support for TP-Link HS107, HS300, KP200, and KP400 #5051
Comments
In regard to the open questions:
The same code when sent to the KP200 switches on/off both outlets. I have not figured out how to automate switching the KP200 outlets individually.
|
@babela do you mean the kp200 instead of the hs200? |
Sorry, yes, I meant KP200. I have updated the original comment. Separate from OpenHab, I am using tasker specifically to turn switches on/off when phone's charge is at a certain percentage to maximize the useful lifespan of the battery... The comment was to answer the question of turning on/off all sockets at once on the KP200. This does work via the same methods as the already supported devices. My OpenHab is currently down so I can not test via OpenHab currently. I have not figured out or found any info on controlling the KP200 individual sockets. It certainly is possible. Hoping to find time to do some packet sniffing in the near future. |
@Hilbrand I have a Kasa HS300 6-outlet power strip, and I'd be happy to help you test! |
I have a HS300 too, and would appreciate the support for it. I can help with the test as well. |
Another project seems to have had a lot of luck developing support for the HS300, and it's currently licensed MIT: https://github.com/plasticrake/tplink-smarthome-api/ The API documentation would probably shed a great deal of light on the questions you have about how the device behaves: https://github.com/plasticrake/tplink-smarthome-api/blob/master/API.md |
@babela, @mythbai and @c6fc I've create an initial version supporting HS107, HS300, KP200 and KP400. The binding is available through the Eclipse IoT marketplace and can thus be installed from PaperUI when the MarketPlace is enabled in PaperUI -> Configuration -> System with Maturity Level Beta. Let me know what works and what doesn't. If you are experiencing problems please enable log level TRACE. In karaf console: |
I've made some changes. I changed the channels of the power outlet devices to channel groups. So it shows up nicer. If you had the experimental binding installed before this day you need to re-add the new things as the channels have changed. |
Hilbrand: |
… and KP400 Closes openhab#5051 Signed-off-by: Hilbrand Bouwkamp <hilbrand@h72.nl>
…, KP400 (openhab#5716) Closes openhab#5051 Signed-off-by: Hilbrand Bouwkamp <hilbrand@h72.nl>
…, KP400 (openhab#5716) Closes openhab#5051 Signed-off-by: Hilbrand Bouwkamp <hilbrand@h72.nl> Signed-off-by: Maximilian Hess <mail@ne0h.de>
…, KP400 (openhab#5716) Closes openhab#5051 Signed-off-by: Hilbrand Bouwkamp <hilbrand@h72.nl>
…, KP400 (openhab#5716) Closes openhab#5051 Signed-off-by: Hilbrand Bouwkamp <hilbrand@h72.nl> Signed-off-by: Tim Roberts <timmarkroberts@gmail.com>
HS107, HS300, KP200, and KP400 are devices with more than 1 outlet on the same device. The HS107, KP200 and KP400 all have 2, and the HS300 has 6 outlets. These outlets can be controlled separately and also have the ability to read power usage. Because of this they also have different control commands and require additional programming to be supported by the tplinksmarthome binding.
This issue report is also to report some work already has been done to add support for these devices. However since not all commands are known it's still a work in progress. And since I don't have either device I can't test this.
Anyone who has such a device and is interested in support for one of these devices please comment in this item.
Power outlet devices:
Open questions
The following questions remain open with regards to how the devices work:
The text was updated successfully, but these errors were encountered: