search

wernerhp / ha.integration.load_shedding

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

Unable to add "Area" on new Integration setup - Full Details - Error seems to be persistent. #53

Closed denzelm5 closed 1 year ago

denzelm5 commented 1 year ago

Home Assistant : VM Home Assistant 2023.1.7 Supervisor 2023.01.1 Operating System 9.5 Frontend 20230110.0 - latest

Log Relating to Integration :

Logger: homeassistant.helpers.template Source: helpers/template.py:540 First occurred: 9:34:56 PM (17 occurrences) Last logged: 9:49:56 PM

Template variable error: 'None' has no attribute 'eskom' when rendering '{{ state_attr('sensor.eskom_loadshedding_stage','status').eskom.stage}}'

Screen Shot : image

Summary : It accepts the API Token successful , at the screen where you have add in your area none of the parameter's work.

Regards Denzel

denzelm5 commented 1 year ago

Hi , This issue is now resolved as it was caused by a conflicting config relating to some custom settings.

JayMcG commented 1 year ago

I am having the same problem and cannot figure out where the issue is.

denzelm5 commented 1 year ago

@JayMcG can you post the related logs .

JayMcG commented 1 year ago

I added a logger and see that there was a suspected abuse so my account was blocked. Hoping it clears in a day or so.

denzelm5 commented 1 year ago

I suspected this was the issue. So the API complains when there are more than one instance from the same ip address . I also have this issue as im running more than one instance of home assistant on my network . it clears every 24hours.

wernerhp commented 1 year ago

If you have more than one instance of HA on the same network, you should use the same API key. EskomSePush blocks multiple API keys coming from the same IP.

wernerhp commented 1 year ago

Please post some logs HA > Settings > System > Logs

JayMcG commented 1 year ago

Update. Ok, everything has cleared again and is working properly. I was setting up an HA instance for a friend and used a different API key for his pi so that must have caused the issues.