-
-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Still using old forecast collector #342
Comments
Please make sure:
|
Hello,
thank you.
So the problem is obviously the yml file. I never touched this file and was
not aware that I have to include environmental variables in there.
That means I have to delete all variables starting with forecast and have
to enter all new solcast vars manually. Plus editing. env file.
May be you should write this in the readme file on github, für dummies -))
not familiar with docker.
Any yml example, link on github? I could not find any. I scanned yml file
on github but solcast vars are not included.
Danke /thx
Reiner Müller
Georg Ledermann ***@***.***> schrieb am Mi., 19. Juni 2024,
13:05:
… Please make sure:
1. FORECAST_PROVIDER=solcast is included in your .env
2. The new env-vars are referenced in your docker-compose.yml
3. You have the latest image by docker compose pull
4. You have restarted your containers by docker compose up -d
—
Reply to this email directly, view it on GitHub
<#342 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ASERTZJNHBE6QQEG4IV5LV3ZIFQZBAVCNFSM6AAAAABJRUYYF2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCNZYGM4TQNRWGM>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
ledermann
added a commit
to solectrus/hosting
that referenced
this issue
Jun 20, 2024
You are absolutely right, the configuration of |
Hello,
yes thx I changed my yml and. env this morning. I didn't remove old. env
entries for forecasting, it's working fine according to the log.
My problem was the API key and the recource ID, API key is a little bit
hidden, so I mixed these two items. But know it's clear.
kind regards
Reiner Müller
Georg Ledermann ***@***.***> schrieb am Do., 20. Juni 2024,
13:20:
… You are absolutely right, the configuration of solcast.com is missing in
the hosting guide. I have just added
<solectrus/hosting@3fffc57>
it.
—
Reply to this email directly, view it on GitHub
<#342 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ASERTZLYW4JNHYO44CJWTGLZIK3H5AVCNFSM6AAAAABJRUYYF2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCOBQGQZTANRQGM>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
Just added support for solcast.com to the configurator, so this issue can be closed. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hello,
when I enter the new lines of configuration to use the new forecast collector and comment the old configuration lines in the. env file I can see in the log files that solectrus still tries to use old forecast provider. Of course this fails now because of missing configuration statements. I believe I miss a step to use this new forecast provider.
thx
The text was updated successfully, but these errors were encountered: