Phasing out the Node-RED Dynamic ESS implementation

Yes I was afraid it would do just that. Even more worrying is the notion that Victron is planning to phase out the only working option to set even only a single target SOC at a specified hour all together, without first enabling the scheduled SOC targets available through the GUI settings (currently disabled when running DESS). I just don’t understand why they would do that. Basically I’m hoping either to be misunderstanding Victron’s intentions to do so (as per @dfaber remark mentioned above) or to be able to draw the devs attention to the foolishness of such a regression of functionality. I welcome any help to get clarity on this situation, both from Victron staff as well as other DESS end users and community members. Preferably with enough time left to create and test alternative solutions before the 15 minute price scheduling goes life for dynamic pricing here in NL (and other EU countries such as DE as well).

The way I understand it, is that Node-RED DESS will not be updated to function with 15 minute price scheduling. And with that the whole ability to run DESS in mode 4 will cease to work (as-is at least) once the dynamic pricing energy supplier switches over to it. That’s why I started to create that monster of a hybrid DESS Trade flow, to keep DESS actively running in mode 1 (auto) while still using the schedulers ability to calculate an alternative schedule targeted to mode 4 operation (with b_goal SOC and hour functional) and using that alternative schedule to time a charge run when certain conditions are met (price far enough below a running average ánd the alternative mode 4 schedule trying to charge as well).

I got that working good enough to be able to leave the system alone for days on a row but not much longer really. Also not getting clarity on this issue took the wind out of the/my sails to invest more time into it as well to be honest. The only area I didn’t really do a deep dive into is the (alleged) ability of VRM-API to somehow feed a new or modified schedule back to VRM for it to be picked up by the VRM DESS dashboard and actual DESS schedule execution engine in the Cerbo GX/ inverter. Should be under VRM-API “Installations" somewhere if I recall correctly. (EDIT: that would be one or a combination of Installation: Get Dynamic ESS configuration, Modify Dynamic ESS configuration and/or Add Dynamic ESS configuration). Unfortunately the documentation on these VRM-API calls seem to be missing or at least to hard for me to find.