What I can imagine is that the solar yield forecast total for the day from NodeRED is static, where the VRM range updates.
So if you look at both in the early morning, I expect them to match, but let’s say that from 8 AM to noon there is fewer sun than expected in the early morning, VRM adjusts, but the NodeRED ‘total expected for the day’ stays the same.
I think I’ve already seen that the Node-RED value also changes during the day, but I’ll look at this again in detail. Of course, it would be ideal if Node-RED would also adjust this every hour, for example. Otherwise the Node-RED value would be pretty useless.
Who would be the contact person in this regard? Dirk-Jan?
I suppose that Node Red gets data from VRM API and should also change during day.
But in VRM API there is still one field “solar_yield_forecast”. Is this also going to change into two (additional) fields min/max?
In VRM, the sum of the actual PV yield of the past hours and the current hour + the predicted PV yield of the following hours is displayed. What was forecast in the previous hours is not included in the displayed range. That’s OK.
In NODE-Red (VRM-API), on the other hand, the sum of all forecast values is displayed, including those from previous hours.
VRM-API in NODE-Red shows 42.02 kWh, which is the sum of all forecast values.
VRM shows 26 - 32 kWh. If you add up the actual yield up to and including 15:00-15:59 and the forecast yield for the following hours, you get 28.06 kWh. This is within the range displayed in the VRM.
VRM-API in NODE-Red is very well adjusted several times during the day. But only the hourly values that are still in the future. On the other hand, those for past hours remain unchanged in NODE-Red, even if they differ greatly from the actual yields achieved.
This is fine for me, as VRM-API in NODE-Red also provides an array with the hourly values in addition to the total sum and the forecast values in the future are actually adjusted continuously. And for control algorithms, I’m only interested in the future values anyway.
So everything is fine!
And btw, also the real production values can be read with VRM-API in NODE-Red:
Hi I’m not sure if this is related to yesterday release, but my Octopus Agile Prices for tomorrow 29/3/25 have not loaded into DESS.
I’ve tried turning DESS on and off and have also changed and updated the API key from Octopus. Any one else having the same issue or got a resolution? dessoctopus
@Barbara The consumption forecast, or rather the predicted SoC value of the battery, hasn’t been adjusting as usual since your last update. Is this intentional?
@Barbara Following on from our discussion from a few days ago. Over the next 2-3 days we’ll be in a typical situation that we wrote about a few days ago. Today, Saturday, we had plenty of PV production. Tomorrow, Sunday, we’ll have a PV shortfall, but prices will still be very, very low. We’ll also have a PV shortfall on Monday. The system plans to use the stored electricity until tomorrow, despite moderate prices, because it only plans until Sunday evening. I’m 100% convinced that prices will be higher on Monday. I can’t say how high with 100% certainty, but higher. Economically, it would make the most sense to have electricity drawn tonight with almost “0” production costs and, at least in Germany, only grid fees. But the system won’t notice this until tomorrow around 1-2 p.m. when it’s actually already too late, because prices are rising again. By then, many hours at very low prices will have already passed. I’m fully aware that this is a difficult situation. But purely speculatively, if the system had a price for Monday that would definitely be higher than the price on Sunday, the DESS could plan completely differently. The absolute price is still entirely secondary. And even if it’s the average price of the last four weeks, the main thing is that the system registers the shortfall. I have to admit, the situation is perfect for our discussion a few days ago. I’m 100% sure you’ll find a practical solution. Best regards from Germany.
@Barbara I am no longer able to change Dynamic ESS settings in VRM. For example, I am trying to adjust the maxcharge and discharge values. They save, but upon refresh the old numbers reappear.
Interface does not matter. Browser, beta gui, mobile app, VRM API using node-red. All the same result.
Not sure if others experience this. Will ask a friend to try as well.
Please avoid posting beta issues on production topics, it confuses things as betas have issues and this is already documented in the beta category.
It is important to be clear what versions are in use as well as any modifications, which often also contribute.
Confirmed by a friend using the latest stable (3.54 I think) all is good. I will upgrade to 3.60.53, check again and repost in the Venus beta forum. Thanks.
