Wrong data fot the next day

[jan3858-cmd]

I have only got data for the 14 of jan. and not for today (13 of jan). And the prognosis is much to high for tomorrow. If I look at the diagnosis it says a 0.56 kWh for today and that looks normal. But in the attributes there are no hours for today.
Until last night the integration never had problems.
Any idea's? Or just s temporary bug and wait till tomorrow?

[gcoan]

At the moment you have provided so little information that it's not going to be possible to provide any help to you.

Please help yourself by providing logs to show what the Solcast integration was doing and checking whether your forecast in Home Assistant matches what is shown in the Solcast website.

If the Home Assistant values match Solcast website (which is almost definitely the case) then this suggests a misconfiguration of your solar array details in the Solcast website. The integration retrieves what Solcast predicts, so if you misconfigure your solar array then you'll get wrong forecasts.

[jan3858-cmd]

Dag, In de logs vind ik niks vreemds. Als ik de diagnose download, zie bijlage, zie ik dat de data voor vandaag wel binnen zijn gekomen, maar ze staan in HA niet bij de attributen. Daar staan alleen cijfers voor morgen en die lijken overigens ook nog eens veel te hoog. Groeten, Jan Doornbos Op di 13 jan 2026, 11:45 schreef Geoffrey Coan ***@***.***>:

…

At the moment you have provided so little information that it's not going to be possible to provide any help to you. Please help yourself by providing logs to show what the Solcast integration was doing and checking whether your forecast in Home Assistant matches what is shown in the Solcast website. If the Home Assistant values match Solcast website (which is almost definitely the case) then this suggests a misconfiguration of your solar array details in the Solcast website. The integration retrieves what Solcast predicts, so if you misconfigure your solar array then you'll get wrong forecasts. — Reply to this email directly, view it on GitHub <#452 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BZLCOXLNNPUL3KI24ZP2DBL4GTEDLAVCNFSM6AAAAACRQZMXWSVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTKNBYGQZTOMI> . You are receiving this because you authored the thread.Message ID: ***@***.*** com>

[autoSteve]

Several ideas.

• What happened last night?
• How long have you been using the integration?
• Which "attributes" in which entity? There are many.
• What is contained in your logs? This is generally the first place to look when diagnosing any issue.
• DEBUG level integration logging is your friend and ours when shared. We provide instructions in the troubleshooting FAQ.
• We are not mind-readers. (Although I am often called on to dust off my crystal ball. 🔮 In this circumstance it is most cloudy, and even looks a bit scratched.)

[jan3858-cmd]

Excuses, ik vergeet de bijlage. Groeten, Jan Doornbos Op di 13 jan 2026, 11:52 schreef Jan Doornbos ***@***.***>:

…

Dag, In de logs vind ik niks vreemds. Als ik de diagnose download, zie bijlage, zie ik dat de data voor vandaag wel binnen zijn gekomen, maar ze staan in HA niet bij de attributen. Daar staan alleen cijfers voor morgen en die lijken overigens ook nog eens veel te hoog. Groeten, Jan Doornbos Op di 13 jan 2026, 11:45 schreef Geoffrey Coan ***@***.***>: > At the moment you have provided so little information that it's not going > to be possible to provide any help to you. > > Please help yourself by providing logs to show what the Solcast > integration was doing and checking whether your forecast in Home Assistant > matches what is shown in the Solcast website. > > If the Home Assistant values match Solcast website (which is almost > definitely the case) then this suggests a misconfiguration of your solar > array details in the Solcast website. The integration retrieves what > Solcast predicts, so if you misconfigure your solar array then you'll get > wrong forecasts. > > — > Reply to this email directly, view it on GitHub > <#452 (comment)>, > or unsubscribe > <https://github.com/notifications/unsubscribe-auth/BZLCOXLNNPUL3KI24ZP2DBL4GTEDLAVCNFSM6AAAAACRQZMXWSVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTKNBYGQZTOMI> > . > You are receiving this because you authored the thread.Message ID: > ***@***.*** > com> >

[autoSteve]

En wij spreken geen Nederlands.

[autoSteve]

But Google is our friend, at the price of expediency, @jan3858-cmd.

Een paar ideeën.

• Wat is er gisteravond gebeurd?
• Hoe lang gebruikt u de integratie al?
• Welke "attributen" in welke entiteit? Er zijn er veel.
• Wat staat er in uw logbestanden? Dit is over het algemeen de eerste plek om te kijken bij het diagnosticeren van een probleem.
• Logbestanden van de integratie op DEBUG-niveau zijn nuttig voor ons en voor u als u ze deelt. We geven instructies in de FAQ voor probleemoplossing.
• We kunnen geen gedachten lezen. (Hoewel ik vaak gevraagd word om mijn glazen bol af te stoffen. 🔮 In dit geval is die behoorlijk troebel en ziet er zelfs een beetje bekrast uit.)

It's a fun game, but how about we all slow down, take a deep breath, organise our thoughts (and logs), and then start again.

[jan3858-cmd]

Dag, HA heeft waarschijnlijk gisteravond om 22.30 de gegevens niet binnen kunnen halen. Ik heb daarvoor een achtervang in gebouwd, dat hij om 3.15 uur nogmaals een poging doet. En dat heeft hij vannacht ook gedaan, blijkt uit het activiteitenoverzicht. En hij gebruikt dan wederom de sensor solcast pv Forecast tomorrow. En dan krijgt hij gegevens van morgen. Ik had deze achtervang recent ingebouwd na een logmelding dat de api niet bereikt was om 22.30 uur en er niet bij stil gestaan dat dan de gevens van een dag later worden binnen gehaald. Dommigheid van mijn kant. Groeten, Jan Doornbos Op di 13 jan 2026, 11:53 schreef Steve Saunders ***@***.***>:

…

Several ideas. - What happened last night? - How long have you been using the integration? - Which "attributes" in which entity? There are many. - What is contained in your logs? This is generally the *first* place to look when diagnosing any issue. - DEBUG level integration logging is your friend and ours when shared. We provide instructions in the troubleshooting FAQ. - We are not mind-readers. (Although I am often called on to dust off my crystal ball. 🔮 In this circumstance it is most cloudy, and even looks a bit scratched.) — Reply to this email directly, view it on GitHub <#452 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BZLCOXKTORVPJARAXZUVJLD4GTFCJAVCNFSM6AAAAACRQZMXWSVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTKNBYGQ2DGNI> . You are receiving this because you authored the thread.Message ID: ***@***.*** com>

[autoSteve]

For those playing along at home... (Would a Dutch translation of the integration be of use? You could curate the GitLocalize translation...)

[autoSteve]

https://gitlocalize.com/repo/10621

[gcoan]

Google is indeed your friend. Would be nice to contribute a Dutch translation

[autoSteve]

NL could be added with a machine version down at GitLocalize. Few clicks, and a bit of [!TIP]-bending in the README.md, and then link updates from the other readme files. But that does not beat human native tongue review and curation...

Every translation added in readme especially is another click-bend-review on update by BJ or I, in a ham-fisted way, and more readme links to get right. Google rocks, but it does not rock everything right.

The string files are easy-ish. Translating the README.md has nuance, and will be a pain in terms of linkage the more translations there are, because every readme in every language will want updating. That should likely change.

[gcoan]

I would focus on just localising the messages in the integration. People can use Google translate or inbuilt browser translate support for the readme. Otherwise it becomes an absolute mountain for ongoing support. I think that's pretty consistent with the way other repositories have localised their integrations/addons

[BJReplay]

My forecast is that this could be a contender for the hall of shame.

But a recovery might have been achieved.

But switching to Dutch half way through still makes it a potential contender:

Don't blindly restore from backups, and hope for the best.

Yes, I know that you don't have the benefit of a Dutch language readme, but a) most Dutch people are bilingual having learned English in school, and b) you can use Google translate.

[jan3858-cmd]

Hello, The reason for switching to dutch was that I got a answer in dutch and thought you were dutch to. Otherwise I would have stuck tot english. Your answer was translated I guess. Greetings, Jan Doornbos Op wo 14 jan 2026, 00:09 schreef BJReplay ***@***.***>:

…

My forecast is that this could be a contender for the hall of shame. But a recovery might have been achieved. But switching to Dutch half way through still makes it a potential contender: Don't blindly restore from backups, and hope for the best. Yes, I know that you don't have the benefit of a Dutch language readme, but a) most Dutch people are bilingual having learned English in school, and b) you can use Google translate. — Reply to this email directly, view it on GitHub <#452 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BZLCOXK5EXGK6FWYC3JXXC34GV3L3AVCNFSM6AAAAACRQZMXWSVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTKNBZGAZDONQ> . You are receiving this because you were mentioned.Message ID: ***@***.*** com>

[gcoan]

Err, no, you started replying in Dutch to our queries in English:

Dag,
In de logs vind ik niks vreemds. Als ik de diagnose download, zie bijlage,
zie ik dat de data voor vandaag wel binnen zijn gekomen, maar ze staan in
HA niet bij de attributen. Daar staan alleen cijfers voor morgen en die
lijken overigens ook nog eens veel te hoog.

Groeten,

Jan Doornbos

Op di 13 jan 2026, 11:45 schreef Geoffrey Coan @.***>:
…

[BJReplay]

Fast heading towards the hall of shame: lack of situational awareness that you are reading automatically translated replies in your email client is putting it right up there.

[jan3858-cmd]

No, your answer came in dutch in my phone, but it's oke so. Greetings, Jan Doornbos Op wo 14 jan 2026, 11:21 schreef BJReplay ***@***.***>:

…

Fast heading towards the hall of shame: lack of situational awareness that you are reading automatically translated replies in your email client is putting it right up there. — Reply to this email directly, view it on GitHub <#452 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BZLCOXMZNP4TB6LTUHGC4CT4GYKDLAVCNFSM6AAAAACRQZMXWSVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTKNBZGQ2DMMQ> . You are receiving this because you were mentioned.Message ID: ***@***.*** com>

[BJReplay]

There it is. Hall-of-shame worthy.

I am replying in English, but my reply is appearing in Dutch in your phone, so it is my fault.

I have worked with some lovely Dutch people, and I love how they are direct, and say what they are thinking.

But usually they are not wrong, and unaware of just how wrong they are.

Here's a tip; you can, and probably should turn off the option to automatically translate English to Dutch that you turned on in the first place so that you don't reply in Dutch to the next reply in English that your phone automatically translates to Dutch because, while not paying attention, you asked it to always automatically translate English to Dutch.

[autoSteve]

I've had enough. Locked.

Shame it, BJ.