The solution is to port the ‘ScheduledSoC’ function to the VRM DESS scheduler (as an input to the scheduler, exactly as was functional in Node-RED DESS). That way we can finally sunset Node-RED DESS altogether. Alternatively and more elegant even, is to enable the ‘Scheduled charge levels’ under the ESS settings not to be silently ignorred with VRM DESS enabled. I bet you a good whisky that the latter suggestion will once and for all allow well defined easy to grasp (as in high level of abstraction Node-RED Flow logic) solutions to satisfy all the other constanly recurring feature requests for addittional custom DESS SoC settings.
And it would not hurt to also recognize that in the present or near future with 15 minute price windows, where three figure battery capacities (100kWh+) won’t be considered uncommon, a single (1.0%) percentage precision for the current timeslot SoC% target, will fully max out a MultiPlus II 5000 power capacity for those 15 minutes. From a systems control point of view this won’t cut it anymore, the precision for the current timeslot SoC% target will need to be increased by at least a full order of magnituide (10x) or simply need to be aligned to level of precision already delivered by the scheduler itself, which is three (3) digits if I recall correctly.
(End of rant, I’ll leave it at this for the time being)