Last month i spoke with Felicity Solar directly in Sibiu at a conference and i asked them for an mqtt exporter for theire batteries and inverters, they were opened to it. Not sure how long will take them to do it.
Iâve cleaned up all the posted email addresses in this thread.
All, speaking of security and data, please remember this is a public forum. Anyone /every bot can see everything posted here, logged-in or no. Please do not post email addresses, contact information, or anything else in a public forum unless youâre okay with the entire world having it!
The OP has updated the top post to provide a link to their external Discord server for direct contact and support on the project.
There was a question regarding future funding of this new app, but it was not really answered (at least from my view).
1.) Could you perhaps add the current thinking about i.e. purchase or subscription cost in the first announcement?
2.) How are you planning to avoid vendor lockin for this solution? (i.e. in case the funding is not enough to cover costs)
Sorry maybe i missed it or i lost it on the way trying to explain it.
- We do not have yet a final version of licensing. But we want to sell lifetime licenses in 2 forms. Software only for those wanting to host it on existing equipment and Software+Hardware for those who donât want to get âhands dirtyâ like a plug and play solution. For the subscription part, i think os needed to keep the updates going and pay the engineers maintaining. Also for industrial deployments or above 200kWh and SCADA integrations we will have a bussiness support subscription too.
- What do you mean exactly by vendor locking prevention? We would like the software to be modular with individual services. We started with Victron but we want to cover as many vendors as possible.
Our funds come from 2 sources, own investments and EU funding programs. For those who involve in the Victron testing and feedback we want to give something back and we will issue a full production license to them at launch.
**UPDATE1: new vm released, new images released
New Release: Automation, Integrations & Smart Energy Control**
Weâre excited to announce a major update to the app, focused on automation, device interoperability, and direct energy platform integrations. This release lays the foundation for powerful control across multiple ecosystems.
Tuya Integration (Cloud & Local)
-
Tuya Cloud integration is now live
Seamlessly connect and manage your Tuya devices directly from the app.
-
Tuya Local support added (WIP)
Local control is under active development and will be unlocked in upcoming releases for faster, cloud-independent automations.
Brand-New Automation Engine
A fully visual, node-based automation engine is now available, allowing you to build complex logic with ease:
-
Multi-provider sensors
-
Tuya devices
-
Cerbo GX
-
Additional providers coming soon
-
-
Logic blocks
- AND, OR, XOR, NOT, NAND, NOR, XNOR
-
Industrial-grade conditions
-
Normally Open / Normally Closed
-
Set / Reset coils
-
Priority flip-flops (RS / SR)
-
Edge detection (positive & negative)
-
-
Composable workflows
-
Chain sensors â logic â conditions â execution
-
Build anything from simple rules to advanced control systems
-
Command Execution
Take action directly from automations:
-
Tuya commands â control smart plugs, switches, and other devices
-
Cerbo GX commands â integrate energy and system control logic
-
Extensible execution layer â designed to support more platforms soon
Modbus Service (Early Preview)
Weâve started rolling out native Modbus connectivity for direct, local data acquisition:
-
Deye dataloggers â in progress
-
Huawei dataloggers â in progress
-
Direct device communication, no cloud dependency
-
Current implementation status: ~25% complete
Expect rapid iteration and new features in the next releases.
What This Means
This release marks a major step toward:
-
Unified automation across IoT, energy, and industrial systems
-
Cloud and local-first control
-
A flexible foundation for advanced energy management and smart infrastructure
PS: i will try to push the code changes to the repositories and update the Gist in 2h-3h
@bolchisb I am missing the actual risk you are trying to mitigate as the historical data I personally donât consider âcritical or even personal and since Victron measuring equipment is not certified, it is not suited to chargeback other than maybe demonstrating uptime to some customers with service contracts. Features such as firmware upgrades I simply cannot foresee in SP not only because of the added layers of overall complexity it will bring, but challenges to keep SP up to date with the multitude of products and manufacturer willingness to allows access to it. These are just some things a proper feasibility study would have highlighted. I would at least have liked to see a per second as opposed to 30s logging rate (greatly benefit problem solving) to be of any worth all the hassle and then the backup etc. considerations just adds other headache to the average user or even business to rather leave it to Victron. I even struggle to see how solar farms can benefit from it as ultimately they would already have highly specialised monitoring and management solutions in place to protect their revenue streams and contracts. Victron added many security measures at local and cloud level, which I very much welcome. In the most unlikely event that my system / a system was compromised, not that it would make any sense to target ânon-criticalâ assets and to what effect, disconnecting from the internet is easy and I can recover my sytem âoff-lineâ in a matter of minutes. As for the most unlikely risk of system downtime, I consider it no worse than a long dark winter with less almost zero production or those clouds and shadows. I regardless wish you sucees with your endeavour.
Hey @ejrossouw, thanks for taking the time to write such a detailed response I genuinely appreciate the perspective.
Just to clarify one point first: internally we already capable of scraping metrics at ~200 ms resolution, but weâre not exposing or visualising that granularity in the UI yet. At this stage, the presentation layer is intentionally coarser while we validate performance, storage, and usability trade-offs. The higher-resolution data mainly exists to support diagnostics and future capabilities rather than day-to-day monitoring.
On the broader goal: Sungrid Portal isnât trying to replace Victron, nor to compete with specialised solar farm monitoring platforms. The intent is different.
What weâre aiming to build is:
-
A cloud-free, self-hosted platform, designed to run entirely under the operatorâs control, with no mandatory dependency on third-party clouds.
-
A security-first architecture, with offline operation as a first-class scenario and a deliberately minimal attack surface.
-
A vendor-agnostic platform, explicitly avoiding lock-in. Victron is just one of the initial integrations the goal is to support multiple manufacturers and mixed environments over time.
-
Strong automation and control capabilities, not just observability. We integrate and orchestrate automations across different ecosystems, and recently added support for Tuya-capable devices, both local and cloud-based, depending on deployment and user preference.
-
Better near-real-time troubleshooting and correlation (power, system health, connectivity, environmental signals) to help explain why something happened, not just that it happened.
-
A foundation for analytics, optimisation, and fleet-level insight that sits above device-centric dashboards and can evolve independently of firmware lifecycles and vendor roadmaps.
An important additional driver for us is regulatory and cybersecurity direction in the EU. Upcoming and proposed regulations for the green energy and critical infrastructure sectors are increasingly focused on:
-
Stricter cybersecurity requirements
-
Reduced dependency on external and opaque cloud services
-
Stronger guarantees around data sovereignty and operational control
Today, a large portion of solar inverters and energy devices are permanently connected to manufacturer-controlled cloud backends, often hosted in non-EU (frequently Chinese) datacenters. While this may be acceptable today for many users, we expect increasing pressure both regulatory and contractual to isolate, harden, or fully remove those dependencies over time.
Sungrid Portal is designed with that future in mind: enabling users to retain control, operate locally, secure their installations, and still gain insight and automation, without being forced into vendor clouds or long-term lock-in.
We fully agree that historical data on its own isnât âcriticalâ in many scenarios, and that certified metering, billing, or chargeback use cases are out of scope for now. The value weâre targeting is primarily operational insight, automation, and faster problem resolution, particularly in distributed or heterogeneous setups where existing tooling can be fragmented or tightly vendor-bound.
Your points around complexity, upgrade paths, and user burden are absolutely fair and exactly the kind of feedback we want early, so we donât build something that adds friction without clear benefit. Thanks again for the candid input and for engaging with this so thoughtfully.
Short update for who is interested, We finished the 3 phase support for grid, we finished the DC coupled MPPTâs support, we finished the AC coupled PV inverters, the cards are showing more than 1 device if multiple are connected. The cards refresh and display data for the next device each 5s, if you click once on the card will automatically switch to the next one if you double click the card it will lock it in place. We support EVCS for now we had data only for one model but we wrote the code in such a way that it will automatically recognize the device and it should display correct data.
Feel free to join our Discord server and help us with feedback.
PS: Just to brag about it, we become a Victron Software integrators we are officially on the map:
