Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Area Name Update #39

Open
adiweps opened this issue Nov 6, 2023 · 5 comments
Open

Area Name Update #39

adiweps opened this issue Nov 6, 2023 · 5 comments

Comments

@adiweps
Copy link

adiweps commented Nov 6, 2023

Good day,

Is there a way to update your area? ESP yesterday released new schedules and area names have changed.

@Dyltong
Copy link

Dyltong commented Nov 6, 2023

Same here

@RaidersPlay
Copy link

RaidersPlay commented Nov 6, 2023

What I tried. Does not work
Maybe someone else have better luck...

As far as I can figure out \\HomeAssistant\config\.storage\core.config_entries needs to be modified.
The variable "area_id" needs to be updated.

The ID can be obtain by going to https://reqbin.com/curl
Run script (from ESP)
curl --location --request GET 'https://developer.sepush.co.za/business/2.0/areas_search?text=Johannesburg' \ --header 'token:YourID'

@Dyltong
Copy link

Dyltong commented Nov 6, 2023

Under settings, devices and services, eskom integration (http://homeassistant.local:8123/config/integrations/integration/eskom_loadshedding)

I clicked "add entry", used the same API key as before, and then found my area in joburg which had "new" at the end.

I then deleted the old entry.

This worked.

@RaidersPlay
Copy link

Might be that the servers are being overloaded at the moment.
After a few retires, I got it to update via the eskom integration guid.
But still waiting for the schedule to update.

Was giving this originally...
image

@adiweps
Copy link
Author

adiweps commented Nov 6, 2023

Under settings, devices and services, eskom integration (http://homeassistant.local:8123/config/integrations/integration/eskom_loadshedding)

I clicked "add entry", used the same API key as before, and then found my area in joburg which had "new" at the end.

I then deleted the old entry.

This worked.

This worked, thank you

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants