v1.1.3

• Fixes by @hawky358 for deprecation warnings

v1.1.2

• Added API key to configuration options (#27)

v1.1.1

• Added polling to calendar entities to improve entity update rates (#24)
• Fixed API key validation during integration configuration (#22)

v1.1.0

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.

v1.0.6

• Update entity.py by @ToxicDeathX in #15

v1.0.5

• Reduced the default number of attempts to the Eskom API, this should alleviate the startup delay while the API is returning -1. (#10)

v1.0.4

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)

v1.0.3

• Added version key to manifest.json (#8 )

v1.0.2

• Fixed an issue where certain OpenSSL versions would trigger WRONG_SIGNATURE_TYPE errors while querying the Eskom API (#2)

v1.0.1

• Fixed aiohttp-retry requirement
• Updated readme and HACS info
• Fixed device version