B-Hartley

Looks interesting. Will be following with interest.

I do re-start quite a lot as I'm still at the tinkering stage with home assistant and changing things a lot. Reloading rest sensors for example seems to duplicate them,...

Could be a bit of a cludge. But could you write the api result out to json when received. Then you could read that back in if it was still...

Yes, ideally I wouldn't want any automated fetches if I've switched off auto_fetching. Restoring the entities at startup would be great, and a remaining API counts sensor would be a...

ok, that all makes sense. Thanks for your work on this. Regards, Bruce.

that makes sense too. I'm not interested in the Solcast "history". If I turned the API limit down to 1, would it stop fethcing history then I could just manually...

Hi, Have installed and tested. It seems to restore the main sensor value. But it isn't restoring the attributes, so the "tomorrow" attribute is null after a restart. Is it...

That's cool. I'd be very happy if you added those extra sensors for each forecast day. Keeping them as attributes of the main sensor to avoid the breaking change ?...

No problem. So can two sessions of your integration be added in it’s current form. could I make copies of it and change one to solcast2 or something.

As a temporary fix, I've made a copy of thecustom component under the domain "solcastx" and that way I can run two separate instances and add them together. If anyone...