Future forecasts missing reported, auto-update errors #429
-
|
I've been using this integration for a long while and in the last few months i've often got alerts saying Logs below. |
Beta Was this translation helpful? Give feedback.
Replies: 3 comments 1 reply
-
|
This is a possible bug, @alpriest, although that surprises me. The class Why I am surprised is because I wrote a
The test is highly synthetic, not real-time, and possibly flawed, so I am going to verify this exact scenario with my simulator rig. If that matches your report then I'll convert this discussion into an issue and build a fix for it. To get you going without using an automation, bring up the integration options and manually set 'Auto-update' to the desired setting. This is what the repair fix does (or tries to in your case). A reminder that the 'API Limit' setting is the number of API calls of total quota to reserve for forecast updates (not estimated actuals and forced updates if you're doing those), and it is this limit that informs how many auto-updates occur during the specified window. For me, a limit of 6 gets me three auto-scheduled updates for my two rooftop sites. Investigating the root cause of why your roll-your-own automation either isn't firing, or the integration cannot get an update would be of interest to me. Simply switching to auto-update may resolve nothing. Examination of your logs may reveal some occasional networking issues. I have seen folks fall foul of IPv6 issues, which have prevented the integration from reaching the Solcast API. If you've got IPv6 enabled in HA and you are not certain that IPv6 is working well with your router/network, then maybe disable it in HA (or fix IPv6) to see if things get more reliable. The symptom is usually name resolution, i.e. canot resolve
|
Beta Was this translation helpful? Give feedback.
-
|
Thanks for the quick response. I went into the configuration and it was set to 'no automated updates'. I changed it to 'from sunrise to sunset', and rebooted to clear the previous error message and I have forecasts again. I did try clicking the error message before rebooting and got |
Beta Was this translation helpful? Give feedback.
-
|
PR #430. Target v4.4.10. |
Beta Was this translation helpful? Give feedback.


This is absolutely verified as a bug. Thanks @alpriest.
Identical logged palaver.