Node-RED, access to ESS Charge Schedules, gone since around 3.80 beta?

Node-RED
,
1

Hi!

After updating to 3.80~9 my flows are missing the possibility of changing the 5 “scheduled recharge” options in ESS.
(This is one thing I use for my own control of the ESS system, say, an own DESS version)

Formerly I used them with the ESS and ESS-Control Nodes, → “Venus settings” → “Schedule x State of Charge (%)”, and so on.
NOW, these nodes won’t work (just get that value one time, just after flow restart), and when placing a new ESS-control node, it isn’t selectable anymore.
Also I found no other node, giving access to this, including the custom control.
Even in the Victron Modbus node, these are not included.
When I look at the dbus docs, i can’t find them too.

There were other settings (e.g. MaxChargeCurrent + -Voltage, etc.) that stopped working via the nodes after the update, but these I were able to access through the Victron-Modbus node now.
But my ESS-Schedule: → ??
Then I consulted the Modbus Register list (found none newer than 3.71), where I also can’t find these settings. (What I was surprised of)

Does anyone know where these settings have gone?
And maybe you can advise some better (or newer) information source for me, than the above mentioned Wiki?

2

You’re running a beta. This will happen. Monitor the beta topics as there are already known issues and some fixes since -11.
If you need stability stick to GA versions.

3

No, I don’t need solid stability.
You say “This will happen”, so I assume that you see that as a glitch/bug. Which would be fine.
I was wondering where these settings moved, as you always move settings around and Nodes change.
What I found surprising is, that even in the dbus docs and the modbus registers, there is nothing documented. That led me to that may have been deprecated things and would not be supported from V3.80 on.
Sure i watch that Beta thread.
Good hint, there was a fix for settings-modes in ~11, so i will try asap.
Still: no modbus registers for these settings?
Or is that 3.71 modbus register list on the website outdated?
Just wondering.

4

For anyone finding this thread, the Solution:
It was just a bug, fixed in 3.80~11.

Still I would propose to make it accessible in the Modbus registers. (at least as an universal fallback option)