You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I recently expanded the number of tapo devices I have connected to my hub to 12, and now note that even though my new devices are showing up, two of my older devices are no longer visible in the data returned from my H100 hub.
What is interesting is that hub.get_child_device_list_json() has a returned parameter "sum" which is 12, but the object only includes 10 devices.
I can confirm that the sensors are online and working correctly (one motion sensor T100, one temperature sensor T315).
Coincidence? Or something more fundamental?
The text was updated successfully, but these errors were encountered:
Congratulations on having a substantial number of child devices. You are the first user of this library to encounter (or at least report) this issue.
Upon closer examination of the decompiled Tapo app, I noticed that the get_child_device_list method includes a start_index parameter. This likely indicates that the request is paginated.
The implementation will need to be updated to accommodate this. I believe it would be best to internalize a mechanism for fetching subsequent pages, so the caller doesn't have to manage this themselves.
I recently expanded the number of tapo devices I have connected to my hub to 12, and now note that even though my new devices are showing up, two of my older devices are no longer visible in the data returned from my H100 hub.
What is interesting is that hub.get_child_device_list_json() has a returned parameter "sum" which is 12, but the object only includes 10 devices.
I can confirm that the sensors are online and working correctly (one motion sensor T100, one temperature sensor T315).
Coincidence? Or something more fundamental?
The text was updated successfully, but these errors were encountered: