-
-
Notifications
You must be signed in to change notification settings - Fork 110
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
S220 Device support #542
Comments
Same here - the S210 has no listed entities in the Integration. |
This would be great! |
As reported here buttons in general doesn't allow getting a "live click event". This is especially true for S200B button which doesn't report "is_on", but if S220 support "is_on" and report it, I will add suport for this |
Same here the S220 switch has no entities. |
Wow, thanks man - that's explaining so much. Couldn't believe it's truly a full non-local device in the moment of purchase. |
The Tapo s200b is simply a low power button and completely different. I can understand that this will simply act as a trigger and no more and is not stateful. The hub cannot know a state since its just a 'pulse' of 'on-off'. The s220 is a stateful power switch, which certainly should support entities in home assistant via the hub since it has defined on and off states and also battery level. |
If s220 is stateful, I can integrate It |
s210 is also stateful (has single switch instead of twin switch S220) |
I need your support to integrate them. You must run a python snippet and report here the state of your connected devices to hub Install
|
Im only posting the s220 part of the response and hidding all the IDs and region stuff here, but getting a response something like this. Is this response enough: {'parent_device_id': '...', 'hw_ver': '1.0', 'fw_ver': '1.7.0 Build 220620 Rel.170201', 'device_id': '...', 'original_device_id': '...', 'mac': '...', 'type': 'SMART.TAPOSWITCH', 'model': 'S220', 'hw_id': '...', 'oem_id': '...', 'specs': 'EU', 'category': 'subg.plugswitch.switch', 'bind_count': 2, 'slot_number': 2, 'position': 1, 'status_follow_edge': False, 'status': 'online', 'is_low': False, 'lastOnboardingTimestamp': 1687434540, 'rssi': -70, 'signal_level': 2, 'jamming_rssi': -118, 'jamming_signal_level': 1, 'nickname': '...', 'avatar': 'switch', 'device_on': False, 'led_off': 0, 'region': '...', 'latitude':..., 'longitude': ..., 'has_set_location_info': True} |
Thanks, I can integrate it |
You also need that script on the s210 or can you take data from s220 log ? Thanks for all your efforts! |
Having both is better ;) |
To help out I also include my result here. I have one S210 and one S220 for comparison and also in both ON and OFF stage. Here are my results: S220-1 ON |
The s220 devices seem to have no controls related to them in the devices menus in HASS. Can't add any automations, no info on the device, no entities etc. It |
Agree, that this is not closed. |
Agreed still no entities for a s220 switch |
Only S210 switches are working for me also. And I noticed another limitation as explained in issue #570. I am not sure since I can not debug it at the moment but they issye regarding S220 might be in tapo_hub.py
Maybe it should be
|
Working , much appreciated! |
I can’t find the update 2.10.1 in HACS. |
I've found it now. |
perfectly working on s210, much appreciated!🎉 |
Also the siren feature on the h100 hub is back. |
These devices should be added to the supported devices list. |
Please add full support for the Tapo S200 switch series so that entities can be revealed and utilised within Home Assistant
The text was updated successfully, but these errors were encountered: