I read “Designed for integration with Home Assistant or custom dashboards” as if you were building a Home Assistant integration and publishing it that way. But looking back, I may have read it a bit too quickly. I also don’t want to be responsible for controlling other people’s systems in that way, that’s why I mentioned Node-RED.
If the solver could just be a node people can import, they could use it to build their own DESS. Node-RED runs on the Cerbo and has easy access to system parameters. The maintenance burden, forecasting implementation, and most importantly the responsibility would then lie with the end user. Plus, they could build in their own system-specific quirks.
Just thinking out loud, I’ll maybe look into it when I have some time next week. Anyway, I really like your implementation @bartm 
I haven’t written any code yet to translate from the solver to strategies. However, here are some helpful sources: all the ModbusTCP registers are available (MQTT control is also possible and generally easier), and Victron’s own strategy interpretation is open-source and available in the file dynamicess.py