Fetches loadshedding data from Eskom
The entire integration has been reworked to use the EskomSePush API to obtain loadshedding status and schedule information.
Users are now required to supply their own EskomSePush API key in order to use this integration.
The following entities are now exposed:
Entity | Description |
---|---|
sensor.loadshedding_api_quota |
The EskomSePush API quota associated with your API key. |
sensor.loadshedding_national_status |
The current national loadshedding stage for Eskom-supplied customers. |
sensor.loadshedding_cape_town_status |
The current loadshedding stage for City of Cape Town customers. |
sensor.loadshedding_local_status |
The current loadshedding stage for your specific area. |
calendar.loadshedding_local_events |
Calendar of upcoming loadshedding events for your specific area. |
calendar.loadshedding_local_schedule |
Calendar containing the full 7-day loadshedding schedule for your specific area. |
By default the sensors will update every two hours. This can be edited in the integration configuration, but users are responsible for monitoring their own API usage.
-1
. (#10)The integration now returns a stage of 0 if it was not able to get a meaningful stage from the API after a number of retries. This is to accommodate for some current issues with the API. (#10, #11)
WRONG_SIGNATURE_TYPE
errors while querying the Eskom API (#2)aiohttp-retry
requirementThis is the initial release of the Eskom Loadshedding Interface integration for Home Assistant.
Currently this exposes a single sensor to Home Assistant, which provides information on the current loadshedding stage.