Error when setting up

[Sc00bs110]

Hi Werner,

I am getting an error when I try to add the location in the setup.

Is there a problem at the moment with the API or is it something I am doing when I search for the suburb?

[Sc00bs110]

My existing Home Assistant has also stopped working (not the one I am trying to set up) and is no longer displaying any load shedding forecast

[wernerhp]

Did you "See Logs for details."? Please post them here.

[wernerhp]

Are you on the latest version 1.2.0 from HACS?

[Sc00bs110]

Did you "See Logs for details."? Please post them here.

Found this in the logs

Unable to get area schedule: Free account abuse detected - Limited access 🙀. Please pay if you can. 16:22:48 – (ERROR) Load Shedding (custom integration) - message first occurred at 3 June 2023 at 15:07:12 and shows up 1479 times

any idea what could be causing this?

[wernerhp]

Read the Eskom Se Push API license agreement. Probably used more than one API key from the same IP. Reach out to ESP https://eskomsepush.gumroad.com/l/api

[wernerhp]

It might clear after a day or two if the abuse is no longer detected.

[Sc00bs110]

Read the Eskom Se Push API license agreement. Probably used more than one API key from the same IP. Reach out to ESP https://eskomsepush.gumroad.com/l/api

Ahhh, I think that two API keys from the same IP may be the case. I have been trying to do a video on setting your integration up on a second Home Assistant box, obviously uses the same IP address. Will send them an email.

Thanks for the great integration :-)

[wernerhp]

You can use the same key on two different installs if you need to get a paid key to use multiple keys on the same IP.

[Sc00bs110]

Will do that, going to delete the other key I created then

[tinuva]

Werner. It is worth pointing out some of these pitfalls on the Readme where you instruct people on where and how to get a key.

On Sun, Jun 4, 2023, 4:50 PM Sc00bs110 @.***> wrote:

Will do that, going to delete the other key I created then

— Reply to this email directly, view it on GitHub https://github.com/wernerhp/ha.integration.load_shedding/issues/68#issuecomment-1575597566, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABJKVUXSH4DGAUWZHNFSR3TXJSOB5ANCNFSM6AAAAAAYQGGNLY . You are receiving this because you are subscribed to this thread.Message ID: @.*** com>

[wernerhp]

Yeah, you can let me know or even better update the readme and create a Pull Request.

The instructions to get an API key are pretty straightforward from the integration's config flow (but I am biased) 😅

[threefoxco]

Hi Werner,

I have the same issue. I am getting this error: Unable to reach Provider. See Logs for details.

I checked the logs and the only error I am getting is:

2023-08-08 02:20:19.338 WARNING (SyncWorker_3) [homeassistant.loader] We found a custom integration hacs which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant

I am running v1.32.1 of HACS

Any suggestions?

thanks Jacques

[wernerhp]

There should be more in the logs. Clear logs and try again. Please double check logs and be sure to not use more than one API key from the same IP. Screenshots of your error may also be helpful. What version of HA and the integration are your running?