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

Slots are not accurate #4

Open
nickidw opened this issue Oct 3, 2022 · 8 comments
Open

Slots are not accurate #4

nickidw opened this issue Oct 3, 2022 · 8 comments

Comments

@nickidw
Copy link

nickidw commented Oct 3, 2022

Version of the custom_component

1.0.7

Configuration

Add your logs here.

Describe the bug

A clear and concise description of what the bug is.

According to the sensor my next loadshedding slot is only tomorrow 4 Oct at 08:00, but it's actually at 00:00, with nothing at 08:00

Debug log


Add your logs here.

image

@tinuva
Copy link
Owner

tinuva commented Oct 4, 2022

Hi @nickidw

From looking at the screenshot, it looks like the upcoming loadshedding slots are based on the current stage, stage 2, where as the loadshedding slot you mention is for stage3.

I haven't had time to have the upcoming slots take into account the stage changes and that would be the reason for what you observe here. It is definitely on a todo list to fix in the future.

@nickidw
Copy link
Author

nickidw commented Oct 4, 2022 via email

@tinuva
Copy link
Owner

tinuva commented Oct 4, 2022

Well in honesty, I am using EskomSePush's API for private individuals.

See: https://github.com/tinuva/home-assistant-config/blob/master/packages/energy/eskomsepush.yaml

This give me the most accurate upcoming loadshedding slots:

Screenshot 2022-10-04 at 14 03 05

@nickidw
Copy link
Author

nickidw commented Oct 4, 2022 via email

@Zodiac-69
Copy link

I have also seen discrepancies.
The Stage is correct, i am on CoCT, but the time-slot is not.
I compared yours with dalehumby/Eskom-Loadshedding-NodeRED, and his time-slot calculation are spot-on.

Not sure if it is https://d42sspn7yra3u.cloudfront.net// that is not reporting the correct time-slot for CoCT.

@tinuva
Copy link
Owner

tinuva commented Jan 19, 2023

Yeah unfortunately sometimes City of Cape town doesnt update the endpoint. The same issue then happen in the CoCT loadshedding app.

@Zodiac-69
Copy link

Zodiac-69 commented Jan 19, 2023

Is there a way to notify the CoCT that their portal has errors? It would be fantastic to get hold of a person that is responsible for this and see if we can assist in automating the process as far as possible.
It is a pain to use multiple apps to get the correct schedule.

With more people using "automation" to automate due to load shedding, the quality of the data is getting more and more important.

@geeneo
Copy link

geeneo commented Apr 21, 2023

Seems we are suck, no updates since the 17th :(

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

4 participants