Thanks Matthijs, but as Murphy’s Law always applies at the worst moment, it seems that half of (dynamic pricing) Europe is switching to 15 minute pricing midnight tonight, rendering (at least right this moment) all Node-RED DESS implementations void. Logs running full of errors, 'Could not get energ…

We are looking into the time offset thing. It looks like that needs to be fixed on the API endpoint side. Considering setting the interval via the node. I just published (on npm) version 0.3.1 that removes setting it in the node, as it is something that is going to be determined based on the config…

Hi @dfaber - I am not totally sure if @UpCycleElectric and I have the same use case, but in our system we’ve had multiple occurrences where the system either hits (a) min SOC too early (causing unintended consumption from grid during peak hours), or (b) hits 100% too early (causing uncompensated exp…

And yet another thing to add, as it changed slightly more. From 0.3.2 on the fetching will always return the records in 15 minute buckets. If your contract is hourly based, the 4 buckets of the hour will contain the same value. Also the data will be fetched from the beginning of the day always and …

[image] Dirk-Jan Faber (Victron Energy): So first question is why it doesn’t work well for you. Can you give some specific use cases / dates + system where the algorithm failed to reserve enough energy? If you don’t mind please refer to the link below for the use case. And for the dates I can…

[image] Dirk-Jan Faber (Victron Energy): The other option, which we implemented in the VRM scheduler, is to always look at the period until next sunrise for the needed consumption energy. Interesting. And also a directt confirmation that VRM-DESS is based on assumptions that put unnessesary (…

[image] Jan: Fun fact: tomorrow prices are 0ct (before taxes) all day long. With no official VRM-DESS settings to ensure such an opportunity is being seized upon to charge all our batteries to the brim automatically when such an opportunity presents itself. I wasn’t the only one noticing: …

0.3.2 looks better, thank you for the changes. The schedule for tomorrow still looks a bit weird (like the schedule for yesterday) but this might be on the API side? I have not checked the price/time combo yet. Didn’t have much time today to tweak the conversion to the “old node-red implementation”…

[image] Dirk-Jan Faber (Victron Energy): At the moment there is still a minor thing on the final hour of tomorrow, but that will be fixed. I put some effort today in getting the date/times correct (they are “toLocaleString(“nl-NL”)”). The VRM issue depends on what timezone you’d like to use?…

Not getting the last slots has been fixed now on the API side. Also notice that I’ve released 0.3.3, which fixes a problem with setting the end time (which affected stats retrieval, not Dynamic ESS schedules).

will this be included in a v3.70 beta soon?

Node-RED DESS implementation issues with 15 minute pricing

Node-RED

UpCycleElectric (Jan) 3 October 2025 16:54 32

I wasn’t the only one noticing:

Topic		Replies	Views
Phasing out the Node-RED Dynamic ESS implementation Node-RED vrm , dess , dynamic_ess	76	3836	22 March 2026
Importing prices into Dynamic ESS with NodeRED Node-RED diy , vrm , dess , node-red	46	2098	15 March 2026
Dynamic ESS and 15 minute pricing DESS vrm , dess	33	1574	7 December 2025
Paging all DESSies: Who wants to actively participate in a community DESS fork effort? DESS diy , dess , node-red , victron_community	40	866	21 November 2025
DESS not honoring "zero sell to grid" today ? (2025-05-10 + 2025-06-16) DESS vrm , dess	35	552	18 June 2025

Node-RED DESS implementation issues with 15 minute pricing

Related topics