Releases: wernerhp/ha.integration.load_shedding
v1.5.0-beta.2
What's new
v1.5.x
- Adds support for Load Reduction Fixes #96
- Fixes long-standing bug where area sensor didn't update. Fixes #71 🤞
- Improves error handling
v1.4.0
- Migrate config flow to version 5
- Converts areas from map to list
- New defaults
- Minimum event duration is now 31min by default. Hides events shorter than 31min
- Multi-stage events are now enabled by default. Shows one event when stage changes mid-event,
- e.g. Stage 6/Stage 5 14:00-16:30 instead of Stage 6 14:00-15:00 and Stage 5 15:00-16:30
- Multiple areas
Configuration | Remove Area |
---|---|
Multiple Areas (Garsfontein / Lynnwood Glen) |
---|
|
Support
If you find this integration useful, please consider supporting my work by buying me a coffee or making a donation in the form of Bitcoin.
Sign-up for a free Luno wallet using this invite link or enter the code X48WY in the Rewards section and we can both earn R 25.00 free BTC after investing our first R 500.
v.1.4.0-beta
What's new
- Migrate config flow to version 5
- Converts areas from map to list
- New defaults
- Minimum event duration is now 31min by default. Hides events shorter than 31min
- Multi-stage events are now enabled by default. Shows one event when stage changes mid-event,
- e.g. Stage 6/Stage 5 14:00-16:30 instead of Stage 6 14:00-15:00 and Stage 5 15:00-16:30
- Multiple areas
Configuration | Remove Area |
---|---|
Multiple Areas (Garsfontein / Lynnwood Glen) |
---|
|
Support
If you find this integration useful, please consider supporting my work by buying me a coffee or making a donation in the form of Bitcoin.
Sign-up for a free Luno wallet using this invite link or enter the code X48WY in the Rewards section and we can both earn R 25.00 free BTC after investing our first R 500.
v1.3.3
What's new
- Unbreak My Card Fix the Status Alert card
Support
If you find this integration useful, please consider supporting my work by buying me a coffee or making a donation in the form of Bitcoin to my BTC address 3EGnQKKbF6AijqW9unyBuW8YeEscY5wMSE
.
Not into crypto?
Sign-up for a free Luno wallet using my invite link or enter the code X48WY in the Rewards section of the app and we will both earn R 25.00 free BTC when you -some day in the future- decide to invest R 500 in BTC.
v1.3.2
What's new
- Remove old
card1.yaml
andcard2.yaml
dashboard examples - Update Status Alert dashboard card to be less brittle Fixes #91 a13c9fe
Support
If you find this integration useful, please consider supporting my work by buying me a coffee or making a donation in the form of Bitcoin to my BTC address 3EGnQKKbF6AijqW9unyBuW8YeEscY5wMSE
.
Not into crypto?
Sign-up for a free Luno wallet using my invite link or enter the code X48WY in the Rewards section of the app and we will both earn R 25.00 free BTC when you -some day in the future- decide to invest R 500 in BTC.
v1.3.1
What's new
- Updated README
- Updated dashboard examples
- Updated automation examples
Support
If you find this integration useful, please consider supporting my work by buying me a coffee or making a donation in the form of Bitcoin to my BTC address 3EGnQKKbF6AijqW9unyBuW8YeEscY5wMSE
.
Not into crypto?
Sign-up for a free Luno wallet using my invite link or enter the code X48WY in the Rewards section of the app and we will both earn R 25.00 free BTC when you -some day in the future- decide to invest R 500 in BTC.
v1.3.0
What's new
- A new configuration option to set minimum event duration in minutes (
Defaults: 30
) for it to be included in the area sensor's forecast and the calendar sensor.
Support
If you find this integration useful, please consider supporting my work by buying me a coffee or making a donation in the form of Bitcoin to my BTC address 3EGnQKKbF6AijqW9unyBuW8YeEscY5wMSE
.
Not into crypto?
Sign-up for a free Luno wallet using my invite link or enter the code X48WY in the Rewards section of the app and we will both earn R 25.00 free BTC when you -some day in the future- decide to invest R 500 in BTC.
v1.2.0
What's new
Multi-stage events
When there's a stage change during scheduled event, this options lets you show this as two calendar events or a single multi-stage event.
Disabled (default) | Enabled |
---|---|
Support
If you find this integration useful, please consider supporting my work by buying me a coffee or making a donation in the form of Bitcoin to my BTC address 3EGnQKKbF6AijqW9unyBuW8YeEscY5wMSE
.
Not into crypto?
Sign-up for a free Luno wallet using my invite link or enter the code X48WY in the Rewards section of the app and we will both earn R 25.00 free BTC when you -some day in the future- decide to invest R 500 in BTC.
v1.1.0
What's New?
- The
stage
sensor'sforecast
attribute has been renamed toplanned
. This sensor updates every hour. - The
area
sensor'sforecast
attribute is now derived from theplanned
stage data and events are clipped when a planned stage starts/ends in the middle of an area schedule. This sensor updates once a day. - A new
load_shedding_forecast
entity contains events which are based off the Area sensor'sforecast
attribute. - A
load_shedding_sepush_api_quota
sensor tracks hour API usage. This sensor updates every 30 minutes. - Updated Cards to use Mushroom Chips for Status and Antomic Calendar Revive for the new Forecast Calendar. The calendar has data for the upcoming week, but shows 3 days by default. Check out Example Card 4
- The integration can now be reloaded from the UI
Support
If you find this integration useful, please consider supporting my work by buying me a coffee or making a donation in the form of Bitcoin to my BTC address 3EGnQKKbF6AijqW9unyBuW8YeEscY5wMSE
.
Not into crypto?
Sign-up for a free Luno wallet using my invite link or enter the code X48WY in the Rewards section of the app and we will both earn R 25.00 free BTC when you -some day in the future- decide to invest R 500 in BTC.
Breaking Changes
- Fixed #33 - Sensor entity IDs have been renamed. You may need to update Cards and Automations to accommodate this change.
In the past they were based off the name field returned from the Eskom SePush API, which recently changed quite a bit. This lead to the sensor's entity ID changing. This release uses the Area ID for area sensors and a key for the Stage sensors. From here on, sensors entity IDs should be more constant. The Name field, which was previously used, is still used for the Sensor's Friendly display name. - The stage sensor's
forecast
attribute has been renamed toplanned
Full Changelog: v1.0.1...v1.1.0
v1.0.1
This version uses the Eskom SePush API. Get a Free (50 requests per day) API Key from Eskom Se Push. You can also pay to get a higher request limit.
See the README for more.
Upgrading from v0.4.0
Upgrading from v0.4.0
ℹ️ NOTE:
If you have set up a version of this integration prior to v0.6.0, please update it in HACS, delete the integration,
restart Home Assistant,
then setup the integration.
v1.0.0 switches from scraping data from Eskom Direct and calculating data for City of Cape Town to using the Eskom Se Push API.
Support
If you find this integration useful, please consider supporting my work by buying me a coffee or making a donation in the form of Bitcoin.
Sign-up for a free Luno wallet using this invite link or enter the code X48WY in the Rewards section and we can both earn R 25.00 free BTC after investing our first R 500.
v0.5.0-experimental
This release is experimental. Things could break if new stage schedules come out. If that happens, I recommend you roll back to v0.4.1.
- Updated to latest version of load-shedding
- Add
next_stage
,next_start
,next_end
andforecast
attributes to stage sensor
Code
type: markdown
content: >
{% set stage_forecast = state_attr("sensor.load_shedding_stage", "forecast") %}
<table width="100%" border=0>
<tbody>
<tr>
<td width="10%"><ha-icon icon="mdi:calendar"></ha-icon></td>
<td align="left" colspan=2>Stage Forecast</td>
</tr>
{% for f in stage_forecast[:3] %}
<tr>
<td></td>
<td align="left">{{ as_timestamp(f.start_time) | timestamp_custom("%-d %B", True) }}</td>
<td align="left">{{ as_timestamp(f.start_time) | timestamp_custom("%H:%M", True) }} - {{ as_timestamp(f.end_time) | timestamp_custom("%H:%M", True) }}</td>
<td align="right">{{ f.stage }}</td>
</tr>
{% endfor %}
</tbody>
</table>
If you find this integration useful, please consider buying me a coffee or sending me some Bitcoin.
Bitcoin: 3EGnQKKbF6AijqW9unyBuW8YeEscY5wMSE
ℹ️ NOTE:
If something doesn't work, please uninstall the integration, remove it from HACS reboot Home Assistant, then reinstall from HACS and setup the integration.
Full Changelog: v0.4.1...v0.5.0