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
It is possible to request data from multiple targets (and functions) using a single request, as is done for the discovery already. The regular update() cycle should be optimized to request all the necessary data to avoid consecutive calls to obtain some extra information.
This is necessary as some devices (mainly bulbs?) are known to have rate limits before they start dropping requests, and some downstreams (esp. homeassistant) want to obtain different sorts of data (status, current consumption, historical consumption) during each update cycle.
This combination will lead to unhappy users (and/or various hacks to go around the issue), so this should be fixed before the release.
It is possible to request data from multiple targets (and functions) using a single request, as is done for the discovery already. The regular update() cycle should be optimized to request all the necessary data to avoid consecutive calls to obtain some extra information.
This is necessary as some devices (mainly bulbs?) are known to have rate limits before they start dropping requests, and some downstreams (esp. homeassistant) want to obtain different sorts of data (status, current consumption, historical consumption) during each update cycle.
This combination will lead to unhappy users (and/or various hacks to go around the issue), so this should be fixed before the release.