v4.1.6 #164
Replies: 2 comments 15 replies
-
Tracking here, @gcoan. |
Beta Was this translation helpful? Give feedback.
-
|
For those wishing to follow along, the branch Post-v4.1.6 at BJReplay explicitly sets a state_class for every sensor. I am running this code in prod, and it is committed. So I am commited. I have just sent it for the good of community. I could not be arsed setting up a play pen to see what happened, because I suspect the answer will be, "Meh. Not much...", and a real live dev set-up would have impacted my prod severely given limitations on API calls. (If you're listening Solcast peeps, @billy-solcast then here's one for your suggestions box... How about a programme for genuine registered developers that allows more than a measly ten calls per day without violating your terms of agreement by using multiple email addresses to get multiple API keys??? I don't do that, by the way, so I suffer, and I am slowed down in development. But developers get it. We do our best to not flood you with requests because efficiency. We try to be the reason that many thousands of people do not flood you. But sometimes we need a little space for creativity, like running three servers at once working three different problems... Even the fifty calls of old would be gold.) @gcoan, the worst that will happen is that I will lick my wounds and wind back the branch commit and restore from backup. But for now I am just sending it because API limits. I'll pick up the pieces later. Reviewing the fallout tomorrow. |
Beta Was this translation helpful? Give feedback.
-
I am pretty sure that there are some pre-defined locations in the API specification that you can get the forecast for that are free to call. Ha, found it https://docs.solcast.com.au/#unmetered-locations |
Beta Was this translation helpful? Give feedback.
-
|
Fair @gcoan, but that is targeted at testers, not developers and supporters of developed code, who probably have a corporate contract and can do what they like. It's just a lousy few more API calls for "power users" / "developers" (that I'd be willing to pay for) is all that would be required to spin up more dev instances. You get how much I love this baby @gcoan. But I can't support it well at times. If I spin up two more instances then you'd think I am at only three-per-day max per instance for the three total. But configs need to be changed in all, including my prod instance. Prod gets the bulk (six calls), everything else gets just two call per day, which are usually exhausted in short order. Dev is slowed down, or like this evening I just decide, "I've had enough. Just send it to production." This does not sit well with me, working at a bank, and the regulator APRA would have kittens, but it is what it is. And this is a missed revenue opportunity, Solcast... This results in slower development for our community. I have prod usually at eight calls. Then I have one dev, which is very much a second-class citizen that gets a couple of API calls per day. I guess that everybody I support now must live at the Taj Mahal... Pack ya virtual bags, because you're being spun up in Agra folks (with much hacking to do so), but not so much real world. |
Beta Was this translation helpful? Give feedback.
-
|
The state_class changes have been rolled back for now. This change would opt-in those sensors to LTS, and I am not convinced that this is a good thing, so will test it over the longer term. |
Beta Was this translation helpful? Give feedback.
-
|
The LTS side effect doesn't surprise me. No issues with rolling back, we need to understand how this change affects everything |
Beta Was this translation helpful? Give feedback.
-
|
Curiously HACS hasn't prompted me to upgrade despite there being a new version. Didn't get prompted for the last release but thought I had fixed that. Anyway, feedback item to raise that the readme page will need updating for the new configuration dialogue |
Beta Was this translation helpful? Give feedback.
-
|
With HACS 1.x updates were checked every three days, when one restarted HA, or when updated information was manually requested (I think those were the only circumstances). I'm not sure about the behaviour of HACS 2.x. Some text has subtly changed, with that initial configuration dialogue now reading, "API limit (optionally comma separate multiple values for each key)". That all? |
Beta Was this translation helpful? Give feedback.
-
|
I thought HACS 1.x polled every day but only once a day 🤷♂️ Was poking around in HACS and all of a sudden it noticed that there was an update for solcast and predbat. Can't remember if this was before or after I restarted HA so no conclusions there. Haven't yet upgraded to the new version but I thought that the configuration was now all in one large dialogue so the sequence of screens in the readme were out of date now? |
Beta Was this translation helpful? Give feedback.
-
|
The initial config (when it is first installed) is just the key and limit, and that's unchanged from how it was. Subsequent You can see the new dialogue further down in the readme where dampening and other options are chatted about. |
Beta Was this translation helpful? Give feedback.
-
|
Jolly good. Thanks for the clarification |
Beta Was this translation helpful? Give feedback.
-
What's Changed
A change occurred in HA 2024.9.0 that caused an issue in the
configureinitial dialogue for this integration. So it's fixed, but it's even better. Now most everything is on a single dialogue, with only manual dampening factors a separate configuration.Prior beta changes in v4.1.4 and v4.1.5:
Full Changelog: v4.1.3...v4.1.6
Beta Was this translation helpful? Give feedback.
All reactions