Forecast not available #4
Replies: 3 comments 13 replies
-
I have the same issue - just returned from a few days away and did some update catch up on HA versions .. after that I see "Failed setup - will retry" ... looking in the log I see: I need to spend some time on this... |
Beta Was this translation helpful? Give feedback.
-
I have implemented a solution suggested by "Speak to the Geek" |
Beta Was this translation helpful? Give feedback.
-
I've uninstalled it now and those logs have cycled, but it wasn't throwing any errors in the log, just not extracting any data apart from the current period forecast. |
Beta Was this translation helpful? Give feedback.
-
Hi, big fan of this integration, have been building automations to minimise grid carbon when charging my home battery.
Last night (2023-10-19) at around 22:00 the integration went offline. The API is still available but poking around today I think the issue is caused because the API forecast currently extends to 22:00 this evening (2023-10-20).
Turning on debug logging:
2023-10-20 14:26:18.686 DEBUG (MainThread) [custom_components.carbon_intensity_uk] Postcode setup: CB4 2023-10-20 14:26:18.686 DEBUG (MainThread) [custom_components.carbon_intensity_uk] Coordinator refresh triggered 2023-10-20 14:26:18.686 DEBUG (MainThread) [custom_components.carbon_intensity_uk] Coordinator update data async 2023-10-20 14:26:19.989 DEBUG (MainThread) [custom_components.carbon_intensity_uk] Coordinator update done 2023-10-20 14:26:19.989 DEBUG (MainThread) [custom_components.carbon_intensity_uk] update_data carbonIntensity response is: {'carbonIntensity': 32, 'fossilFuelPercentage': None, 'forecast': None, 'lowCarbonPercentage': None, 'status': 'very low', 'optimalTo': None, 'optimalFrom': None} 2023-10-20 14:26:19.989 DEBUG (MainThread) [custom_components.carbon_intensity_uk] Finished fetching carbon_intensity_uk data in 1.303 seconds (success: True) 2023-10-20 14:26:19.989 DEBUG (MainThread) [custom_components.carbon_intensity_uk] Coordinator refresh completed
I will continue to poke around - and this may fix itself if the API forecast is fixed, but want to know if others are seeing this issue and whether there's a work around to get access to the partial forecast.
Beta Was this translation helpful? Give feedback.
All reactions