autoSteve
commented
1 month ago I am absolutely torn by this, @gcoan.
The title is changed because as I understand the code if a new rooftop is seen then a "dopast" forecast get is called, which also gets the future forecast. So new users should see data on initial config even if they have not yet configured an automation. If they do not configure one then the forecast eventually runs out, then they log an issue, then I label it as "Read the readme".
For your circumstance it may or may not make sense. For the "not make sense" argument, a new user could see that there is an issue with forecasts, restart the integration and all would seem right for seven days. Issue logged again (which they would have done anyway I guess)... On the other hand, this prospect intrigues.
gcoan
Is your feature request related to a problem? Please describe. Came back home today after 2 weeks away, a week and a half of that with HA not working and no remote access to fix. [Weirdly HA seemed to loose outbound IP connectivity, it was still running but couldn't talk to anything]
So all my Solcast entities were empty.
Restarting HA fixed the remote connectivity but of course no Solcast data until I remembered why and manually ran the Solcast update automation.
For new users (and people like me which have had a broken HA), this extra step to manually run the Solcast update is something that could be improved upon.
Describe the solution you'd like When Solcast integration starts and detects that there is no Solcast data and/or zero API calls made today, it automatically calls the update_solcast service.
One disadvantage of this auto-retrieve is that users may not realise that this retrieve is a 'freebie' and they have to write the automation for future polls, but its pretty clear in the documentation
Describe alternatives you've considered Leave as-is, users have to remember to create/run the automation themselves.
Additional context I don't have the logfile any more as I ended up restarting HA and the PC my HA guests upon multiple times [because some weird reason my HA server had been allocated a different IP address, despite having a fixed IP]
But the logfile was pretty clear, it loaded the sites data, the API calls from Solcast and all the 'data for' from the cache were zero where now it shows data loaded from the cache: