Criticism of VRM and Victron

It might - for starters - be enough (end easy for me) to look up my older posts.
https://communityarchive.victronenergy.com/users/5391/petajoule.html - of course if victron didn’t make communityarchive so darn unusable. :grinning_face: (404)

How about this?

it’s a trivial task with great usability benefit. (petajoule asked • Aug 01 2020 at 9:42 AM) Unchanged to this very day.
And I really hope there is no discussion that the current implementation of the zoom button violates about any UI/UX best practice there is.

In light of the new VRM release and my 2c about scaling and legend issues:

(petajoule asked • Oct 19 2020 at 8:33 AM)
”Thanks for your very detailed post, very useful for us. There is definitely room for improvement, and I’ll see what we can do.”
=> and sure, my request may clash with someone elses. But this means that sooner or later ambitious DIYers will move away from VRM to

  • idk - grafana or stuff. And maybe some providers will offer their customers a similar step as “value add”.

As for what @alexpescaru wrote above about bug fixes, I had this small article:

Where in retrospect you actually can see FW versions you better never would have touched.

Care to write something about the testing that is being done by Victron before a FW release?
Because I was looking for any mention of TDD, a test suite, unit tests or ANYTHING actually in

and all I found was the mention of “testing” distribution in do_release.sh
I’d argue that this is 90ies SW-development, but maybe my memory is hazy in that regard.
Fortunately the GX devices steer solar and not nuclear power plants. :wink:

Until today, what you see on the X-axis between 10:00 and 11:00 is not what is shown in the graph for the time between 10:00 and 11:00

:man_shrugging: And no answer - (petajoule asked • Aug 04 2023 at 9:47 AM) - I mean: what is one supposed to do with that “black hole” mode of Victron handling feedback?

I could continue, but I’d really like to see some credible reaction to all this first.