VRM monitoring, DESS, VRM-API, Node-RED DESS monitoring, its all down with no solution in sight and ..edit.. communication from Victron slowly surfacing (see next message).
I’m not anti cloud perse but without an officially supported self hosting option or other high availability fail over solutions, the current situation present a single point of failure problem with an enormous user base wide impact. High availability is difficult to impossible achieve when VRM and services linked to it (DESS) are only running on Victron’s cloud.
I think an open discussion is needed on the future of VRM / DESS and officially supported ways of limiting or removing all together the dependency on the single point of failure situation that is manifesting right this very moment.
And no “just dont use it” is not the answer. VRM is officially and critically part of the value proposition that has many like us and our customers buying into the whole Victron platform in the first place. And we are very happy with what it offers for good reason too. But that can’t mean we cannot discuss basic issues such as this one.
You can use Grafana for local monitoring and NodeRed to build your own DESS.
I can’t remember that there was ever such a problem with VRM in years. IMO a (partially) down time of one or two days in over 10 years is totally fine.
Of course it’s annoying but such things can and will happen with every system. A VRM downtime isn’t a life threatening situation.
I know the VRM team is working hard right now to get it back running ASAP and they also will be looking for ways to prevent that in the future.
I am not going to get into this argument. It distracts from the real issue.
RE: Closing of this topic by @Nickdb : I do not mind helping to keep discussions centralized. I do mind having a topic closed that tries to adress the higher level issue in play: Who owns all the monitoring data, who owns the IP of the DESS algorithm. I my opinion the former is the customer base, the latter is Victron. That is what should be discussed.