Looking for Testers and Feedback: Secure, Local-First Monitoring Platform for Victron Systems

Apparently I didn’t read well enough and I was under the impression this was a Victron or at least a Victron-backed initiative.

To make things easier i opened a public Github Gist for those who want’s to test it and provide some feedback, i added some steps how to run it on you machine (i recommend an Apple computer or Linux machine, i don’t have a windows machine) For questions you can contact me and i will try to support you.

Thank you.
But if you’ll put the normal user to do all those in order to use your application, you’ll have a problem…
Not so many will have the inclination to do all those. It needs to be greatly simplified.

An idea…
As the VirtualBox is one of the easiest to install virtual machine hypervisors, it’s free and exists for all platforms, maybe you could make a VM image with all that’s needed (software, server, database, docker etc.), properly configured in advance and you ship that VM image for all to use.

that would work too, i plan to write a script to, just one line of code and it should work perfectly fine. I do what i can, i’m down 2 developers this year. I hope to get some EU funding to hire 2 developer and 1 UI/UX specialist.

I was suggested that from experience…
During covid, some practical courses that involved a maritime liquid cargo handling simulator were difficult to implement.
Not all students have proper IT&C training and/or expertise and try to teach them how to install on their machines a complex control process engine and simulator and set it up. Almost impossible, but all had to pass that course.
So, it needed to be as simple as possible.
The solution was to make a virtual machine, install there all the software, configure it and give it to the students.
All they had to do is to install the hypervisor as any other software, launch it and open the vm image like you open any document, press on play, wait for the vm to boot and then double click on an icon on the vm desktop to launch and play with the simulator.
Almost 100% success rate… A single image for all platforms… Linux, Windows, Mac.

Hello Bolchisb,
Your UI interface looks much better than the VRM interface !
I should very much like to test it, my email address is :[moderator edit: removed private email address].
Regards and have a nice Christmas time !
Jan Renkens

Hello Bolchisb,

interesting work done. I will be willing to be a tester and provide objective feedback for your attention.

Thanks

Where should support questions be sent? I have installed everything but get a 404 page not found error on all the 808X ports.

Hi i have added a VM image too, fully configured, i have an email address on the Gist page since i am not able to write one here without getting deleted.

Use this gist, you have there a VM too

Will this solution be free, as VRM is?

Is it really fair to copy the VRM design and integrate other brands—especially brands that are restricted or banned in some countries due to data sovereignty and control concerns outside the EU?

When it comes to cybersecurity, has Victron ever been at fault? No.

The narrative is therefore built around risks that do not actually exist, simply because it is the easiest way to attract customers. You copied Victron’s design and are now trying to recruit testers using Victron’s own community platform.

I find this unacceptable for multiple reasons.

Lucian, let’s separate facts from assumptions and keep this discussion technical and fair.

1. “Free” does not mean “without cost.”

VRM is not free in any meaningful sense. It is paid for with data centralization, long-term telemetry retention outside the user’s control, and architectural lock-in. Users exchange operational data, usage patterns, and system metadata for convenience. That is a valid model—but it is not “free,” and it is certainly not neutral from a data-sovereignty perspective.

Sungrid takes a different approach: self-hosted by design, data stays on infrastructure the user controls, with no mandatory cloud dependency and no implicit data monetization.

2. This is not a copy of VRM—architecturally or conceptually.

A dashboard showing PV, battery, grid, and load is not proprietary design—it is a domain inevitability. Every solar monitoring platform converges visually because the physical system is the same.

Where Sungrid fundamentally diverges is under the hood:

  • Decoupled ingestion via MQTT → NATS JetStream

  • Explicit separation between control, persistence, realtime streaming, and forecasting

  • No vendor cloud dependency

  • No opaque data pipelines

  • Designed for auditable, inspectable operation

Calling that a “copy” is like claiming every Kubernetes dashboard copied the first one that showed pods.

3. Data sovereignty is not a narrative—it is an engineering choice.

Stating that “Victron has never been at fault” misses the point entirely. Security is not judged solely by past incidents, but by architecture, threat surface, and jurisdictional exposure.

Sungrid exists because:

  • Many users do not want their energy infrastructure dependent on external SaaS

  • Some operate in regulated, air-gapped, or privacy-sensitive environments

  • Others simply want ownership of their data and operational logic

These are legitimate use cases, not fear-based marketing.

4. On brands, deployment, and accountability

Sungrid’s goal is broad compatibility: we want to integrate with all major brands, not restrict users to a single vendor ecosystem. The difference is where and how that integration runs.

Sungrid is meant to be deployed by engineers on the customer’s own infrastructure, so telemetry, credentials, and control paths remain self-contained—owned and operated by the customer. That enables:

  • Data sovereignty by default (no mandatory third-party cloud)

  • Local control and deterministic operation (even if the internet is down)

  • Security boundaries defined by the operator (network segmentation, IAM, logging, retention)

Compatibility is a feature; self-hosted control and data ownership is the principle.

5. Community and testing

There is nothing unethical about inviting users—many of whom already understand Victron systems—to test an independent, self-hosted alternative. Competition and experimentation are how ecosystems stay healthy.

Sungrid is not anti-Victron. It is Victron-compatible and user-centric.

Here are 5 real, consumer-focused examples showing how home smart devices — especially cameras and IoT gear connected to cloud/SaaS services — have led to privacy/security failures*. These illustrate why self-hosted and privacy-aware architecture is not just theoretical:

  1. Wyze camera breach exposed strangers’ feeds

    In early 2024, about 13,000 Wyze home camera users were accidentally shown live/thumbnail footage from other people’s cameras due to a server-side caching issue — a stark example of cloud-managed device logic going wrong and invading home privacy. Wyze Labs - Wikipedia

  2. Millions of smart home records exposed (2.7 billion)

    A massive IoT breach exposed 2.7 billion records linked to smart home devices, including device identifiers, network names/credentials and logs, due to an unsecured cloud database tied to consumer IoT ecosystems. Smart Home Data Breach Exposes 2.7 Billion Records | ZoneAlarm Security Blog

  3. 40,000+ internet-connected cameras streaming publicly

    Security research found over 40,000 home and office security cameras worldwide streaming without passwords or any protection — meaning feeds intended to secure private spaces were discoverable and viewable by anyone online. Massive privacy concern: over 40,000 security cameras are streaming unsecured footage worldwide | Tom's Hardware

  4. Authentication bypass vulnerabilities in home IP cameras

    Government security agencies (e.g., CISA) warned that popular IP cameras widely used in consumer homes contained critical flaws that let attackers bypass authentication, potentially exposing live video feeds if left unpatched. https://cybernews.com/security/security-flaws-in-dahua-cameras-being-exploited/?utm_source=chatgpt.com

  5. Smart home device maker’s database left open to the world

    A widely sold smart home vendor left an IoT database publicly accessible without authentication, exposing sensitive user and network data — including information that could be used to target individual homes. Massive IoT Data Breach Exposes 2.7 Billion Records, Including Wi-Fi Passwords

Finally, it’s worth stating the obvious: personal indifference to data privacy does not invalidate other people’s requirements.

Some users are perfectly comfortable trading data, telemetry, and long-term behavioral patterns for convenience. Others are not. That difference does not make one side irrational—it simply reflects different risk models, regulatory constraints, and personal values.

Privacy and data ownership are not ideological positions; they are engineering and governance choices. The fact that you may not care where your data goes does not mean:

  • homeowners,

  • engineers,

  • privacy-conscious users,

  • or regulated environments

are wrong to care deeply.

Sungrid exists precisely because choice matters. Offering an option that keeps data local, auditable, and under the user’s control does not attack existing solutions—it acknowledges that one size does not fit all.

Why an AI response? It’s a valid question from Victron.

Other inverter manufacturers too offers VRM-like data monitoring services.
Should they get upset that Victron or anyone else, for that mater, has a similar service?

Saying that a monitoring service resembles Victron’s, it’s like saying that the Netflix resembles HBO-Max or any other streaming service.

As long as Victron has implemented MQTT and Modbus and, more of that, is teaching others in video tutorials how to collect and show the data independently (see Grafana), is quite strange to turn against people that are really trying to do that.

Regarding integration of other brands… come on… how many times the Victron users asked for integrating data from other manufacturers onto Victron products? And Victron did that for their users, for some other products. Now you are using that as an argument?

As per cybersecurity… It’s not about security of cloud based systems, it’s about data privacy. My data, my way, my storage.

Never at fault until you are. If you’re on the internet, you’re at risk, period.

(I’m a certified ethical hacker, so for a change I know what I’m talking about :slight_smile: )

For a better translation and better expressing the information in english since i am not a native english speaker. Just to eliminate misunderstandings. The content still remains valid.

I could use your expertise if you are willing to help.

Hello, I’am ok for using this application. you can contact me : [moderator edit: removed private email address]

Hello,

Will this allow me to see dc loads as historical consumption when using a Lynx ve.can 1000A m10 shunt?

Because this is something Victron refuses to do for whatever reason with venus os/VRM, to allow for dc loads to appear as consumption with the lynx shunt, while it works perfectly fine with all smart shunts. I started my build with a 500A smartshunt so can imagine my disappointment when I “upgraded” to a 1000A lynx shunt and lost the ability to track consumption.

Zit er prima uit

[moderator edit: removed private email address]

From The Netherlands