I know many PV operators. Small, medium, and very large systems, with virtually all of them manufacturers represented in Germany. When I talk to these operators about their problems, especially with the control system, I’m always grateful to have landed at Victron. When I observe how other manufacturers are attempting to deal with dynamic pricing, forecast-based charging and discharging, and many other issues, I’m almost overcome with pity. When I show my VRM during these discussions, I receive envious looks. In this context, I find the criticism about where which button is placed… childish. Dear development team, let’s continue to make mistakes together, recognize these errors, learn from them, and further develop both the DESS and the VRM. THANK YOU
And get quicker on the market with those long announced future products! ![]()
I am referring to the rack mounted ones… ![]()
To have new material for ranting over… ![]()
The English equivalent to the German “Jammern auf hohem Niveau” would be “first-world problems” or “champagne problems”. So yes, we are lamenting about things other vendors may not even offer, but there is also another saying: “to rest on one’s laurels”
From my observation Victron is feeling the competitive pressure from other manufacturers (If I compare pricing today and 3-4 years ago), and the nifty integrated Victron ecosystem is an advantage - maybe even USP - today but no guarantee to fend off the competition forever.
And times are changing - rapidly.
If anyone is willing to take the bet that ME ALONE (+ some AI ofc) could re-develop VRM in a month (*) (I haven’t started yet) with some significant stake, I’m willing to do so. And if I can do it, what about Huawei et al.? I mean - I will do it anyway, but later (maybe spring 2026) and no rush.
(*) Including the necessary scalability, not talking about some PHP page here.
Looking back over the past few years, I can’t really see that anyone has rested. Considering how sobering the initial experiments with DESS were, I intervened almost daily during that time and deactivated DESS at critical moments. In the past few months, I haven’t been able to detect any serious errors in my investment. There are still many things that need improvement, and there are constant changes in market conditions in individual countries that we need to respond to. Therefore, there’s no reason to rest, but I don’t think anyone intends to either.
Sorry I’m butting in here as a complete newbie with Victron.
The thing that really struck me when I installed by MP2GX system and found what I felt was a bug was the total inability to record what I had found for others to comment, and for the putative bug to remain visible, not just lost in a forum.
To say that something is reported and may have been “overlooked” is to say that you do not have an adequate system for recording problems reported either internally or externally to the organisation.
I worked for many years as an ICT management consultant and one of my specialties (among many!) was call centres and help desks. I came across corporate help desks where they failed to record details of each call, what the issue was, who dealt with it, when it was closed and why, …
It seems to me that Victron needs such a system that anyone - Victron developer, end-user or installer - can report a problem and others can add or comment on it. And a subsection of that system could be suggestions for improvement. There should be someone in Victron responsible for periodically reviewing the bug/suggestions lists and closing any that are irrelevant, wrong or have been fixed.
You might think this is onerous, but once set up it would save Victron a lot of time, not least in debugging software.
Hello,
I am very satisfied with my Victron products, with these exceptions:
- Import / export CerboGX configuration.
Still not available despite several requests.
This is important for this type of product (breakdown or other). - New VRMS portal
The ergonomics are not as good as the previous one, we lose display space for nothing.
I preferred the old one, I am waiting for an improvement of the new one. - Multiplus II 8000
Mine dates from 2022, it is too noisy because of poor design: unsuitable fans and fixed hard.
I didn’t want to open the device to install the upgrade kit.
In renewal I would like a Multiplus II 10000.
I hope that the evolutions have really improved the dB of the current models (2025/2026).
Regards
On the whole, I am happy with how Victron and VRM works. Commendation for versatile and very customisable products; it must not be easy satisfying users’ demanding requirements.
For many months, VRM World seems broken. When you view an installation, the next installation has the same name, pictures and probably other details I have not discovered as the first installation viewed. I had reported this on the Victron website but the issue persists.
Additionally, I do not know why the feature does not work on mobile browsers or the VRM App. I found it useful exploring others’ installations when I was planning mine and got data and a few ideas from VRM.
Hi @Brian,
This might be the first place it is announced right now, but we are going to shut down the VRM World feature that allowed you to browse around the various different publicly accessible VRM sites shortly.
It was a nice idea and very cool to see the systems as VRM grew, but that specific feature was not used much at all any more, and given the issues you described, and probably more to come as time goes on, we have decided to turn it off.
Apologies to those few who were still using and enjoying it.
Regards,
Guy
This too is my experience, once I pointed a real problem out to them and they told me “Nah, we don’t get feedback of this happening very often so we don’t care”. The chaos of configuration softwares, communication protocols and even victron own physical connectors has just grown to a mass where Victron just can’t keep up on making all of it work, but also they give af about integrating all into one system (like make everything modbus tcp like many other manufacturers)
In defense of Victron, I can tell you that this is happening when you develop new products “on the run” and try to evolve from old style electronics/components to new style electronics/components. And probably switch hardware/software designers along the way.
In Victron product range you can clearly see that and also you can see various ideas of those different people involved.
But, because old people - that have the money to afford Victron prices - are conservative, that doesn’t mater. Problem arises when, at some point, because of the lack of old, they must switch to the new technology and then they hit the “wind of change” and don’t like it…
Also, seen these things happen when either a single person wants to exercise too much control over the team or when there is too much liberty allowed for the R&D team without paying attention to the market trends.
But, as seen lately, they try to recover and to implement the current industry trends, again, on the run…
Let’s hope for the best, but also prepare…
Viele nutzer und selbstbastler leider auch* nicht um anschliessend los zu gehen und nur zu meckern auf die Forums.
- dass ‘auch’ ist nicht zur Bestätigung des Benutzersquote.
This topic was automatically closed after 15 days. New replies are no longer allowed.