Replies: 1 comment 2 replies
-
Thx., Robert for the detailed research. For my part, I was just surprised that the forecast period got reduced :-) I raised an issue over at If and when we have the fix in pysolcast, we can write in
and take |
Beta Was this translation helpful? Give feedback.
2 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hi,
thanks for the great work here!
It seems Solcast has changed the behaviour of the api. They now have the parameter "hours" and the one is by default set to 48 hours. So using this script I only get the forecast for the next 48 hours. The parameter is optional and can be set between 1 to 336. See Solcast Api documentation: https://docs.solcast.com.au/#58ca9bc0-27d4-4418-937f-03986331f01d
Unfortunately, I'm bad at python and could need some help implementing this parameter to the script. I'm also not sure if the used pysolcast (https://github.com/mcaulifn/solcast) needs to be changed?
What did I try?
In solecast.py I changed/added:
self.postDict = { 'hours':336 } # dictionary to post to solcat
self.params = {'hours':338 }
Did not work for me.
What did work:
I copied the classes and definition from pysolcast into the file solecast.py and changed this part:
to this:
Can someone help me understanding what I have to change in solecast.py so that I can give the params parameter when calling the function?
Kind Regards
Robert
Beta Was this translation helpful? Give feedback.
All reactions