-
Notifications
You must be signed in to change notification settings - Fork 26
Description
Hello, Zaptec devs are here!
We’ve noticed that your integration is making sequential calls to the following endpoints:
GET api/chargers/[id]/state
GET api/chargers/[id]/settings
Just a quick note: the state endpoint already includes all the data returned by the settings endpoint — in fact, settings is simply a subset of state. While you might occasionally see slight differences in overlapping fields, this typically happens when a charger hasn’t updated its values yet. Once it does, the accurate value will be reflected in state.
Additionally, please note that the settings endpoint is considered internal. It is subject to change or rate limiting without prior notice, and we recommend avoiding reliance on it for production use.
We kindly ask that you remove the settings call (https://github.com/custom-components/zaptec/blob/master/custom_components/zaptec/api.py#L604-L613) if you're already using state, because we have plans to forbid usage of this endpoint by external parties.
We truly appreciate your support in optimizing the integration. If you have any questions or need help making this adjustment, feel free to reach out.
Thanks again for your cooperation!