search

wernerhp / ha.integration.load_shedding

A Home Assistant integration to track your load schedding schedule.
MIT License
113 stars 21 forks source link

Editing Area Sensors #67

Closed Clayton1212 closed 5 months ago

Clayton1212 commented 1 year ago

Hi Thank you so much for this integration. I have been successfully using it for a few months now and love it.

One small complication I have run into since Ethekwini have released new schedules, ESP created a new area for the new schedules and the old ones are no longer in use. How do I edit the sensors to update it to the new area? I have looked all over to find this but just can’t seem to work it out.

Thank you for your help

Interquip commented 1 year ago

Have a similar issue - in COJ they moved us from block 16 to block 8.

DravenSA commented 1 year ago

What i did when they move our block was remove the integration and then installed it again. I had to then go and edit my front end, but it should only be in one or two laces if you used something lie

{% set area_sensor = "sensor.load_shedding_area_jhbcitypower2_16_yourarea" %}

And then you should be back on track

unless you are just using the forecast section then you shouldn't need to change anything

wernerhp commented 1 year ago

Yes, the easiest is to remove and reconfigure the integration. Changing areas is not something that happens that often so it was not built into the integration. Will likely add this functionality when multiple areas are supported.

StefMicro commented 10 months ago

installed the integration, all working great except there is a Cape Town stage sensor with Cape town schedules it seems, when it should be Tshwane. The rest of the sensors reflect my area. Updating it did not help.

wernerhp commented 10 months ago

installed the integration, all working great except there is a Cape Town stage sensor with Cape town schedules it seems, when it should be Tshwane. The rest of the sensors reflect my area. Updating it did not help.

There are always two stage sensors, one for Eskom and one for Cape Town, because CoCT has different stages from the rest of the country. These reflect the planned stages. If you are not in CoCT you can just ignore it.

There will also be an area sensor for your area with the forecast. Forecast is where your area schedule intercepts with the stage sensor's planned schedule.

StefMicro commented 10 months ago

installed the integration, all working great except there is a Cape Town stage sensor with Cape town schedules it seems, when it should be Tshwane. The rest of the sensors reflect my area. Updating it did not help.

There are always two stage sensors, one for Eskom and one for Cape Town, because CoCT has different stages from the rest of the country. These reflect the planned stages. If you are not in CoCT you can just ignore it.

There will also be an area sensor for your area with the forecast. Forecast is where your area schedule intercepts with the stage sensor's planned schedule.

OK it's by design. Thanks Werner. Awesome integration BTW

wernerhp commented 5 months ago

Please help with testing the new beta https://github.com/wernerhp/ha.integration.load_shedding/releases/tag/v1.4.0