Wundert mich nicht. Das machen Firmen immer. Indem sie kritische Statements löscht und nicht einsehen wollen. Das sie Mist produziert haben. Das VRM-Portal ist absolut unübersichtlich geworden. Aber das Team von Victron muß ja dem Vorstand beweisen. DAs sie gebraucht werden. Dabei gehören alle Verantwortlichen gefeuert. Denn die IT von Victron zeigt es immer wieder. Sie kann es nicht.
Victron betreibt keine ernsthafte Forschungs- und Entwicklungsanstrengungen. Denn dann würden sie nicht ständig am Portal Herumdoktern. Wenn man die Jahre mal so beobachtet. Hat Victron nie wirklich auf die Probleme und Sorgen seiner Kunden reagiert sondern immer ihr eigenes Ding gemacht. Das sieht man jetzt topp am VRM-Portal. Victron versucht es als großen Wurf zu verkaufen. Obwohl Victron es besser weiß. Das es kein Wurf war und ihnen kurz oder später auf die Füße fallen wird.
Beim Cerbo GX z.B. lässt sich oft neue Firmware gar nicht installieren oder sie friert immer wieder beim Betrieb ein. Steckverbindungen, wie z.B. Sensor für Batterietemperatur sind teilweise eine Frechheit. Das die so verkauft werden.
Ich persönlich kann Victron seit dem VRM-Portal Desaster nicht mehr empfehlen. Für Anfänger ist es einfach zu unübersichtlich geworden.
Hi @Joe9911
I have moved your generalised criticism of Victron out of the release notes post.
If you have useful specific criticism to offer, please phrase it constructively and we will hear it.
You have said “Cerbo GX, for example, new firmware often cannot be installed at all” -
What do you mean by this?
I don’t know of any issues with installing firmware on the Cerbo GX?
I haven’t seen you or anyone else post any report of this before either?
Please focus on one topic at a time and we can make some progress.
10 Likes
Please find out how far other manufacturers have progressed with forecast-based charging, charging and discharging at dynamic pricing and similar, and then reconsider your criticism.
9 Likes
@Sarowe1990 I couldn’t agree more! Thank you Victron for your great products!
1 Like
While his criticism is very general and probably not entirely constructive, he’s not wrong that Victron IS ignoring feedback - sometimes for years.
Or let’s be benevolent and more precise here: Maybe not ignoring, but “knowing about it and living with it”.
From own experience I know that if you insist, then the final explanation is “not enough capacity/manpower to fix things, there are priorities”.
Can’t really argue with that, because then I would have to take it from the technical domain to management domain and … yeah.
I assume Victron really wants someone to reimplement VRM as soon as such an endeavor becomes the lesser problem cough Claude Code cough.
This thread here VRM related, but I could assemble my own private Victron-related list of still open feedback/issues since 2019. You might be surprised.
2 Likes
Hope you get this as constructive…
Count the number of times the word “Fix” or “Fixing/Fixed” is appearing in the Cerbo’s firmware changelog.
I can count about 596 occurrences in the current one…
About 50 this year only and the year is not finished yet.
Can we consider that those were bugs or mistakes?
Do you believe it’s normal?..
To be honest, this is the reason I’ve remained at 3.32 for Cerbo and 1.16 for Multi RS and made my own fixes and modifications.
If you go to the effort of doing so, I will take the time to give some feedback on it 
4 Likes
People… just consider the fact that we are all actually participating in the development of a completely new technology. The alternative would be to wait 1-3 years until the “DESS” product is fully developed. Of course, this is also entirely up to everyone. Updating to the latest version is, as far as I know, mandatory. For my part, I am very grateful to be able to participate in this development, and even influence it through suggestions. Some mistakes, setbacks, and misguided developments, and the resulting learning experience, are part of it. As already mentioned, the alternative would be to wait.
3 Likes
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. 
(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. 
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
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.
Is that what is meant by “new firmware often cannot be installed”?
It’s really hard to say what is normal because for most products I use their either isn’t regular updates, or the release notes are vague and say something generic “we are regularly improving”.
It’s also ok and recommended to not update firmware if the system is working, by default Victron products do not update firmware unless there is a very good and hopefully rare reason. Usually maximum 1 or 2 times a year only for a compulsory update for a product.
So most updates are continuous improvements.
1 Like
5 posts were split to a new topic: VRM Zoom Reset Button Placement
We have since then implemented a method to set your own preferred custom scale for VRM using the custom widgets feature.
Already trying to use that helps understand why it’s not easy to have an automatic y-axis scaling detection system that works in all cases, but then it is possible to make your own if the system gets it wrong if necessary.
Major backend changes are underway for the improvement to the firmware update release process. This is a major change that involves almost the entire R&D of company at some point, as most of our products have updatable firmware, and multiple teams who are involved in front end and back end software that delivers it.
One thing I can say right now is opacity of the changelog will be massively improved, beyond that will have to wait for the release, and I am very excited to see it as well.
We have an entire public community section dedicated to Venus OS testing, so probably best to ask your specific question in greater detail there.
When a report is made and no one else confirms it or comments on it, it may have just gone unnoticed. Sometimes I see them, but sometimes I don’t, and if no one else is commenting then it’s more quickly pushed out of the front page and then hidden until someone replies.
I have some processes in place to try and catch things that I think should get my attention, but one of those things that helps me see it is that when a bug report or feature request is made, that there is more than one person making it.
If you make a report, and no one else has the same issue, or doesn’t feel strongly enough to post in agreement, and you still feel strongly that there is something wrong that Victron should fix, then the next thing to try to get some more attention on it from others in the community by posting some follow up comments.
Nothing wrong with the vrm portal, much easier now and faster to get to where you want to go. If you have problems finding your way it is propably not the layout which is the problem?
5 Likes
-
on iPhone the bottom menu bar doesnt respect safe areas. Sometimes you’re hitting the buttons instead of swiping away the (web)app.
-
when you hit the < button (that’s partly cut off due to the safe areas been ignored), the menu opens and then it triggers the multiple installations menu from there. This feels kinda like my nephew just started coding.
-
When you swipe from left to right the installations menu directly shows but once the animation finalized it closes again to open again as page.
-
When the ESS status in the menu doesn’t reflect the ESS status of the local machines, the menu keeps flickering the options. To optimized to keep charged, to optimized etc.
-
When you fully scroll down the page suddenly respects safe area and there is a whole gap in light colored background mismatching the menu bottom bar background color.
-
sometimes when scrolling you hit the “hide forecast” button, it seems the buttons are very trigger happy for touch events.
-
If you swipe trough the graph in mobile you accidentally selecting the page.
-
In the DESS graphs the buy and sell price are sometimes twisted. They still reflect the correct color, they just sometimes top and sometimes bottom.
This one specifically will be fixed in the next release. Agreed that it’s a confusing button.
It will be changes so that it’s clear what clicking on the button will do, not just an ambiguous back arrow.
I will pass on the other feedback as well, thanks.
I would just give a little positive shoutout here to the Victron team. I have been working with other suppliers as well (Mastervolt anyone?) and the sheer fact that we have such good development here (and yes, that always comes with bugs) is what makes Victron so valuable! Being a nerd myself also helps off course 
12 Likes