Closed Lauriz7 closed 1 month ago
You added a logfile rather than diagnostics, could you please add the diagnostics as requested?
You added a logfile rather than diagnostics, could you please add the diagnostics as requested?
I just enabled diagnostics, so i would need to wait before the issue appears again I guess.
No, you just need to click download diagnostics - no need to enable anything or wait for anything
No, you just need to click download diagnostics - no need to enable anything or wait for anything
config_entry-energidataservice-781db64c7c5a73d8b25308ad6650d042.json
Thats the file available.
In to addition, i have other entity configured without tarrifs, and it does not stop working.
File for the working entity:
config_entry-energidataservice-781db64c7c5a73d8b25308ad6650d042 (3).json
Seems like this is somehow related to the 500 errors we have seen the last few days from Energi Data Service API. Handling of this should be fixed in the latest version of the integration, released today.
Describe the issue
After midnight the service stops reporting and is unavailable, i have running automatic restart when its unavailable, but it fails until manual restart of integration.
At 14:50 08-08-2024 i also experienced API returned error 500 and at 14:33 it was API returned error 400, Bad Request!
I do not have log of integration yet, but i think my HA core log says a lot.
What version of Home Assistant Core has the issue?
6.2
What was the last working version of Home Assistant Core?
6.2
What type of installation are you running?
Home Assistant OS
Diagnostics information
home-assistant_2024-08-09T07-02-49.851Z.log
Anything in the logs that might be useful for us?
Additional information
No response