Future roadmap #655
Replies: 9 comments 16 replies
-
Component NegotiationTo achieve the second point, I need your contribution to collect information about all available components. I need you run a simple python script using my plugp100 library.
async def main():
# create generic tapo api
credentials = AuthCredential("<tapo_email>", "<tapo_password>")
client = TapoClient.create(credentials, "<tapo_device_ip>")
components = (await client.get_component_negotiation()).get_or_raise()
print(components.component_list)
print(await client.get_device_info())
if __name__ == "__main__":
loop = asyncio.new_event_loop()
loop.run_until_complete(main())
loop.run_until_complete(asyncio.sleep(0.1))
loop.close()
|
Beta Was this translation helpful? Give feedback.
-
|
I figured I also need but I'm still having errors, this time I get this: |
Beta Was this translation helpful? Give feedback.
-
|
Have you tried with pip install urllib3? |
Beta Was this translation helpful? Give feedback.
-
|
Full code therefore is: import asyncio
from plugp100.common.credentials import AuthCredential
from plugp100.api.tapo_client import TapoClient
async def main():
# create generic tapo API
# I'm a special case of having username not being an email. You just put your email in, unless you know what you're doing ;)
credentials = AuthCredential("msprg", "dontPutYourPasswordsOnline")
client = TapoClient.create(credentials, "IPaddrOfTapo")
components = (await client.get_component_negotiation()).get_or_raise()
print(components.component_list)
print(await client.get_device_info())
if __name__ == "__main__":
loop = asyncio.new_event_loop()
loop.run_until_complete(main())
loop.run_until_complete(asyncio.sleep(0.1))
loop.close()For your convenience, by yours truly. |
Beta Was this translation helpful? Give feedback.
-
|
model: P110 |
Beta Was this translation helpful? Give feedback.
-
|
Mine Matter enabled P110M, EU plug: {'device': 2, 'firmware': 2, 'quick_setup': 3, 'time': 1, 'wireless': 1, 'schedule': 2, 'countdown': 2, 'antitheft': 1, 'account': 1, 'synchronize': 1, 'sunrise_sunset': 1, 'led': 1, 'cloud_connect': 1, 'iot_cloud': 1, 'device_local_time': 1, 'default_states': 1, 'auto_off': 2, 'energy_monitoring': 2, 'power_protection': 1, 'matter': 2, 'current_protection': 1} Success({'device_id': 'I_WOULD_RATHER_NOT', 'fw_ver': '1.0.4 Build 230825 Rel.115051', 'hw_ver': '1.0', 'type': 'SMART.TAPOPLUG', 'model': 'P110M', 'mac': 'I_WOULD_RATHER_NOT', 'hw_id': 'I_WOULD_RATHER_NOT', 'fw_id': '00000000000000000000000000000000', 'oem_id': 'F031I_WOULD_RATHER_NOT91C', 'ip': '192.168.0.8', 'time_diff': 0, 'ssid': 'I_WOULD_RATHER_NOT', 'rssi': -51, 'signal_level': 2, 'auto_off_status': 'off', 'auto_off_remain_time': 0, 'latitude': 0, 'longitude': 0, 'lang': '', 'avatar': '', 'region': '', 'specs': '', 'nickname': 'I_WOULD_RATHER_NOT=(base64encoded apparently)', 'has_set_location_info': False, 'device_on': True, 'on_time': 2409, 'default_states': {'type': 'last_states', 'state': {}}, 'overheated': False, 'power_protection_status': 'normal', 'overcurrent_status': 'normal'}) Unclosed client session Has it errored on me? |
Beta Was this translation helpful? Give feedback.
-
|
Super keen to get S200B & S200D Buttons and Dimmers working - hoping to get whole house light switches replaced with the double gang covers. I think it would be a big win for TP-Link as they are cheap, even for a hub and you could split half the house on different hubs etc. Notes:
Output: {'device': 2, 'firmware': 2, 'quick_setup': 3, 'inherit': 1, 'time': 1, 'wireles s': 1, 'account': 1, 'synchronize': 1, 'sunrise_sunset': 1, 'led': 1, 'cloud_con nect': 1, 'iot_cloud': 1, 'child_device': 1, 'child_quick_setup': 1, 'child_inhe rit': 1, 'control_child': 1, 'alarm': 1, 'device_load': 1, 'device_local_time': 1, 'alarm_logs': 1, 'localSmart': 1, 'matter': 3} |
Beta Was this translation helpful? Give feedback.
-
|
Thank you for all your support on this integration! Here's a sample from my P100 plug and L630 bulb P100 Output: L630 Output: |
Beta Was this translation helpful? Give feedback.
-
|
@keeragh, is your P100 on old firmware? I get this, which I believe is due to TAPO having changed their authorization protocol on a number of devices |
Beta Was this translation helpful? Give feedback.
-
|
model: L930 |
Beta Was this translation helpful? Give feedback.
-
|
@PilotFlying hiya, according to Tapo's website my P100 is on latest FW version (1.2.1) for the HW version (2.0) reported (it's also set to auto update during the night as needed) |
Beta Was this translation helpful? Give feedback.
-
|
Thank you for this info! BTW, the issue I mention is resolved now, I can add my P100s to HA. (I don't yet see how it was fixed, there were no updates to this repository) |
Beta Was this translation helpful? Give feedback.
-
|
Hi, great work so far! I'm using your integration in my home with several Tapo P100 and it works like a charm. Did you had a look at this? I wonder if your integration and the plan to bring it to the Core Integrations still makes sense, if there are any reasons/features why someone should still use your integration in favor of the core integration? |
Beta Was this translation helpful? Give feedback.
-
|
I actually believe that this integration should partially replace the one in home assistant. |
Beta Was this translation helpful? Give feedback.
-
|
So there still seem to be some reasons to keep this integration for Tapo devices. But honestly, I don't really like having two integrations for devices from the same vendor. To me it would actually make more sense to try to contribute all the features and improvements to the core integration instead. Any thoughts on this? |
Beta Was this translation helpful? Give feedback.
-
|
Sounds reasonable to have one codebase and if that is the version that comes by default , even better. |
Beta Was this translation helpful? Give feedback.
-
|
I have already asked the developers of the integration in HA core if they could participate in the development, but I have not received any response. |
Beta Was this translation helpful? Give feedback.
-
|
The core integration didn't support most of the devices I an interested in! |
Beta Was this translation helpful? Give feedback.
-
|
At the risk of being annoying, I've just added a new .venv, with same code. Code is: IP address is taken from the tapo app, looking at the specific device.
I get this: |
Beta Was this translation helpful? Give feedback.
-
|
I'm really happy to announce that version 3.1.1 is out now, with a lot of stability improvements, better support to tapo devices with components design! 🥳 Also add diagnostic report, to help me to help you, and new firmware management offically supported by HA. Thanks to testing, plupg100 library is more stable, of course, there can always be problems to fix, since it is reverse engineering. I hope in few next days to make this integration the official one on HA. There is still much work to be done! Thanks everyone for support EDIT: please refer to 3.1.1 with a minor fix 🙏 |
Beta Was this translation helpful? Give feedback.
-
|
I just wanted to drop you a quick note to say how impressed I am with the work. It's really outstanding! |
Beta Was this translation helpful? Give feedback.
-
|
Ditto both of those: it is really impressive |
Beta Was this translation helpful? Give feedback.
-
Hi guys, I'm working on a new major release of this integration. I will define here a sort of future roadmap, I hope to respect it.
My goal is to move this integration to homeassistant core integrations.
In some roadmap points, probably I will ask for your support to collect as much device's information as possible.
Draft of roadmap:
component_negotiationof tapo api to get information about specific cability of each device instead of "hardcoding" intoconst.py.Happy holidays 🎄
Beta Was this translation helpful? Give feedback.
All reactions