Hello, is it possible to calculate a shading or is there an automatic function that can adjust the whole thing? my panel that points south only gets sun off from 1 pm, according to Solcast, the yield should go up before that, because it is assumed that there is already from 8 o’clock sun on the panel. Even from 6 pm there is no direct sun because a house provides shade.
This is especially the case in clear skies when there is no difufusen radiation.
That’s what the damping factor allows you to do.
You have to calculate the values yourself for each hour and put them in.
I have a solcast account with two rooftops, headings east and west. But I notice a difference with what is on the site and what is being shown in HA. It looks like the two rooftops are being added wrong in the solcast addon, or there is a comma in the wrong place or something like that. When I look on the solcast account I see at the moment 0.04 for both directions (pretty clouded with rain) but in HA solcast it gets added to show 0.8608 W. It only seems to happen when there is a zero after the comma. When there is a different number behind the comma (like 0.4) the numbers seem to match.
Suggest you raise it as a github issue on the bjrelay fork, assuming that’s what you are using
Just wondering if anyone here using the apex charts have this. For some months, I have no idea why, the values for battery and house power are set to 0 even though the sensors work fine and I can use them normally on HA.
Anyone saw or still see this happening?
It’s very odd, the other values are fine and even if I edit and check the auto complete, i can see the value there as well.
Same here. OK as well
I swear I used to have more than 10 API calls/day.
Have solcast changed the limit for long term users ? I thought it was only new users that had a 10 api call limit.
And of course the reset password functionality for the web doesnt seem to work, so i cant even login to the web app at the moment.
You don’t have multiple API keys configured in the integration do you?
If so then the lowest limit of all keys configured will apply for the BJReplay repo because all API keys are polled for an update at the same time.
@BJReplay has 50 calls, so maybe he can chime in, @sh00t2kill.
I do not — but if you recall i did hit a logic path that should have only triggered if i had > 1 API key.
I definitely dont though.
Sorry about the late reply - I haven’t visited the forum for a while. Not for me 
Still the original early adopter quota of 50 - but I was very early.
I definitely used to have 50, but now only 10 
at least according to the integration.
The integration no longer reports the number you have, because the API that it relied on has been turned off by Solcast.
You need to tell the integration how many calls you have.
It defaults to 10.
There may have been an issue when you upgraded to 4.1.3 that it couldn’t retrieve the existing limit, so defaulted to 10.
See Release v4.1.3 · BJReplay/ha-solcast-solar · GitHub
Edit your config and set it to 50 to see what happens.
Thanks!
I did try that but i think solcast was having issues at the time as it wouldnt update.
Will try.
ED: My bad. i got config confused with the service. No wonder it didnt work.
Looks like its working now. Apologies, I feel a little silly as I missed quite a few updates because i hadnt updated the repository in HACS.
Integration v4.2.5 is released at BJReplay/ha-solcast-solar GitHub - BJReplay/ha-solcast-solar: Solcast Integration for Home Assistant.
There is much improved. Much refined.
(Watch the install config if coming off an old release. The APi limit must match your actual limit, because Solcast ditched an API call, and this needs to be set right. Gah! Do re-read the readme.)
There are improvements to hard limit function. Improvements in documentation. Improvements to re-start corner cases, and many improvements in versions past like adding auto-update again.
Any and all feedback will be welcome at v4.2.5 · BJReplay/ha-solcast-solar · Discussion #210 · GitHub.
6 Likes
Thank you very much @autoSteve and all contributors for all the great work in maintaining and evolving this. Absolutely love the new granular dampening functionality.
3 Likes
I followed the note on BJReplay’s repo that said you could download the new integration over the top of the old one but now in HACS it looks like I have both. Is there a way I can remove the old one now. I am guessing that removing it via HACS isnt an option because that would remove both
Hi, can you turn on debug logging for both (instructions here Troubleshooting FAQ · BJReplay/ha-solcast-solar · Discussion #38 · GitHub for BJReplay, adjust as needed for the old one) and raise an issue on my github with screen shots and directory listing of your custom components directory as well, please?
We’re trying to work out how two integrations with the same custom component folder name can both exist at the same time.
Once you have captured the information, remove both the old one.
Even if it removes both (and I am struggling to understand how it can, if you can add two where the second should install over the top of the first), you can always re-install the new one again.
And a reminder to all; please seek assistance at the github repo either by raising an issue or creating a discussion - I don’t spend a lot of time here 
.
Removing both is not an issue as far as preserving the Solcast data. This is stored in a solcast.json file in the /config folder, and is not removed when removing the integration, or when messing with custom repositories in HACS. Nothing touches it except the integration (or you…) Killing both integration folders with fire (if there are two), then starting again with the bjreplay repo will do the trick.
It would be great to know if this is still HACS 1.x, or whether you have (likely) switched to 2.0. The Oziee repo was removed from the HACS library a while back, so should not be acquirable that way. If you had it set up to pull releases from his custom repo then that could co-exist in HACS with @BJReplay’s. But BJ would win, because Oziee’s repo does now not exist. I don’t know what HACS caches though.
If this is still messed up @Breddo, then BJ and I would really appreciate the info that he requested. In any event, if you’ve got it all working, then welcome! BJ’s is just better in a whole bunch of ways…
This double-install should not happen, I can’t reproduce it, and I don’t have much to go on to prevent others falling foul of it.
Then again, given > 5000 users of the BJ evolution it may become a moot point. I can’t recall how many downloads Oziee peaked at to know for sure, and the repo is gone preventing a check.
1 Like