I have 4 Victron identical solar panels each 95 watts. One pair on a arch over the cockpit and the other pair on the coach roof. Because of shade issues they are wired parallel. The wires from each pair are then joined in parallel before the are attached to the Mppt 100/30.
Should the pairs be joined in series or parallel before the are connected.
No matter which way the controller can cope with volts and amps generated.
Which is the most effective way of connecting to get best out of panels and controller
Hi Victron, we are discussing in several threads a nearly similar question without an expert comment by victron-staff:
This main problem of an „symmetrical“ or „balanced“ ESS in a three phase grid-parallel setup is absolutely essential for the German and Austrian market. Please let us know what you think about it! Thank you very much!
I just setup an RPi running Venus OS 2.66. As an experiment I am trying to add a custom menu item to Settings. Currently there is a "Reboot?" menu in Settings -> General. I wish to add a "Restart GUI?" menu.
I've found the /opt/victronenergy/gui/qml/PageSettingsGeneral.qml file and the entry for the Reboot? menu so I have figured out how to add my custom menu.
I have also determined that the command "svc -t /service/gui" can be used to restart the GUI.
The part I'm missing is how to run that "svc" command from within the qml file.
Does anyone know the correct syntax?
Along those lines, is there any reference documentation for the "vePlatform" class from com.victron.velib? I can see there are commands such as "reboot()" by scanning the qml files but is there a complete list in some documentation somewhere?
I've been researching but doesn't appear that anyone has already asked/answered this, so apologies if this is a double-up. I'm new to the forum, Victron, raspberry and linux, so I'm learning my way :)
I'm wishing to have a safe shutdown option for a Venus Pi (preferably a 3b+) as it will be inaccessible and also likely experience power loss overnight during the winter months (off-grid DC setup, huge battery and solar but also a power hungry system).
I don't want to take the chance of just pulling the power, because any corruption of the micro SD card will be a huge pain to remedy. It would need to be a fully automated process (all of the Raspberry shutdown procedures I've seen need to be manually triggered) - and also having UPS functionality would be an added bonus.
The PiJuice HAT seems to be the most intuitive hardware option, however it appears that the 'soft shutdown' function only works through scripts on a Raspbian OS, and so doesn't appear to be compatible with the Venus OS.
It would seem to me that my options are -
1. Find someone who has PiJuice or similar properly working on a Venus OS, who can provide advice for activating automated safe shutdown
2. Find an old Venus package for Raspbian, and PiJuice should work out of the box (anyone have a link?)
3. An alternative software / hardware / UPS option which offers safe shutdown functionality (any suggestions?)
4. Get a Cerbo instead? (assuming they won't be affected by sudden power loss)
Has anyone come across this situation before and provide any advice please? I'm not looking to reinvent the wheel, I can reasonably follow other people's coding but have zero coding experience of my own.
Could someone help with my easy solar system its a 48 /5000/70-100/230/240 v.
I have just up graded with 2 BYD batteries LVS 4.0 premium.
this fault comes up System overview - GX Error # 48 DVCC with incompatible firmware : warning.
I have tried everything - is there a easy fix?
If I was to set up a pi zero2w or a pi4 would I be able to connect to my Bluetooth enabled devices, or would I have to connect a wire to each of them?
I would like to install the ffmpeg package on venus OS with raspberry Pi.
This package is not included in the standard repository of Venus os, i tried:
opkg install ffmpeg
i also tried to find a correct package which has the .ipk archive, but no result.
Does anybody have succesfully installed ffmpeg package onto a raspberry Pi with Venus OS?
Cerbo GX configuration
the configuration software does not find MK3 interface . Therefore is no electrical connection
between Interface and Cerbo GX. What can I do ? Is there any idea ?
I have spent days upon days, pulling my hair out trying to figure out how to accomplish a method of integrating some platform that would allow me to setup triggers and such that would adjust the parameters of the VenusGX, or allow it to communicate status updates that would fire home automation triggers. Eventually, after a lot of trial and error, and many a late night staring at my computer screen to get this working, I got a working implementation which functions beautifully.. I do hope someone else will find this helpful.
*This guide will show screenshots, and discuss functionality that is from my own flavor of Home Automation Controller, for which I use HomeSeer 4, however should work in a very similar fashion with any other platform that has support or a plugin for MQTT; a quick Google search reveals Home Assistant and SmartThings appear to have support for MQTT as well*
I will begin this guide with a screenshot here which gives you an idea what you can accomplish:
Having access to this functionality opens up a world of possibilities inside a Home Automation Controller, henceforth referred to as an "HAC".
A few examples of what I have done with automations:
What you need:
Phase 1 (VenusOS):
Phase 2 (Node-Red):
*Alternatively, as suggested by Marcus, you can follow these instructions to install Node-Red on the VenusOS device itself, if your HAC does not support this: https://www.victronenergy.com/live/venus-os:extended
Phase 3 (HAC):
1. Assign your HAC a static IP. I won't go into details here as there are too many variables.
2. If you are running your HAC as a software implementation on a Windows box, or other OS which has a software firewall, you will need to unblock port 1883
3. Install any required components to enable MQTT, in my implementation using HS4, I used the mcsMQTT plugin
4. Make sure the implementation of MQTT on your HAC is running a local broker, you may need to familiarize yourself with MQTT a little bit here, but this step is usually pretty easy, and think was configured as default in my instance
Phase 4 (Connecting VenusOS -> HAC):
Now it's time to set up your "flows", these are sort of like little customized data paths in Node-Red, which I will do my best to explain without making it sound too intimidating I hope.
Basically the idea is this, you connect a "receive node" to the VenusOS device, which then grabs that bit of data every time VenusOS updates the value. You then implement some intermediary "nodes" which convert that bit of data into a more usable format. The reason for this being, is that "bit of data" is really a packet which contains a few pieces of information, only 1 of which we really care about.
For example, the packet of data which contains my AC Input value (the number you see "Grid" listed as in the HUD of the VenusOS device) looks like this when it first comes in:
N/985dad8185e7/vebus/261/Ac/ActiveIn/P : msg.payload : Object
So we need to strip that away until a single string is left with a value "-3147"
The reason for this being that my HAC knows exactly what to do, "If AC_Input < 1000", but not so much if "AC_Input=objectvalue: -3147"
I will provide my exported flows in NodeRed so you can easily import and tweak them, but wanted to explain how it works so everyone can understand what is happening to the data.
Here are some screenshots for each phase from this flow, which I will try to explain as I go:
This one is fairly simple. The first node is the "MQTT in" node, which connects to the VenusGX, looks for a topic (I will provide a list of all topics toward the end), this topic is the "AC Input" value, as mentioned before, which is listed as "grid" in the HUD. It then stores the data in a parsed JSON object, this format breaks up the packet into different bits which can easily be grabbed.
To add your own VenusOS device here, all you need is to plug-in the IP address from Phase 1, by clicking the edit button
Next, we have a "change" node, which takes only msg.payload.value, and passes it on, if you recall here, the output from the first step looks like this:
N/985dad8185e7/vebus/261/Ac/ActiveIn/P : msg.payload : Object
So this node takes that whole packet, and only passes on what is to the right of "objectvalue:"
Finally, we have the MQTT out node. This takes the data we just stripped down, and sends to to my HAC, by publishing to a topic, Energy/Grid
That's it for this phase! We now have the data flowing to the HAC for Ac Input.
Phase 5 (HAC):
We now have data being sent to the HAC, but the HAC hasn't been told what to do with it yet. To get your HAC to process this data, we now need to "subscribe" to the topic. This will be very different for you, depending on your HAC and how it implements MQTT, but in general subscribing to a topic is one of the easiest functions and should be immediately obvious when you access the MQTT functions.
With my instance of MQTT, when you subscribe to a topic, a virtual device is created that allows you to fire a trigger, or just read the value. In my case, device #724 (seen in the very first screenshot at the top) was created, and I renamed and customized with some icons of my choosing, and then grouped it together with other such devices. This whole process again will vary greatly depending on your HAC. I can provide specific instructions for HomeSeer if anyone is interested however.
MQTT Topics (data channels):
I will cover the topics that the VenusOS MQTT broker publishes, and subscribes (listens) to. These can be used to read various bits of data, or write to them and thusly alter settings in VenusOS itself.
As far as connecting Node-Red to your HAC, you can pick and choose your own topics. I simply choose Energy/Grid in my example, because that seemed logical to me at the time.
Let's look at my example: N/985dad8185e7/vebus/261/Ac/ActiveIn/P
The first segment, "N" signifies a "get" or a "read" command, if you will. If you setup Node-Red with a "MQTT in" node to read data from VenusOS, you are always going to start your topic with this part. I don't know why the programmers chose this, but there you go.
To write a value, alternatively, you begin a topic with "W/" which makes a little more sense I suppose.
Next we have this big, ugly alphanumeric string. This is your VRM Portal ID, which if you followed Phase 1 Step 4, you will have ready to copy paste.
Following this, we have the first path to the data you are looking to read or write. I think most useful bits of data are located under the vebus path, but there may be some stuff in system or settings as well. I would recommend this app to fully explore your VenusOS device: http://mqtt-explorer.com/
Going down the vebus path, you will next need to specify your vebus device ID, which you should have handy from Phase 1, step 5.
From there, there is lots of stuff to choose from depending on what you're looking for. I will outline a few key ones here that I use
N/985dad8185e7/vebus/261/Dc/0/Temperature - Multiplus Temperature
N/985dad8185e7/battery/258/Soc - Battery SOC*
N/985dad8185e7/vebus/261/Ac/ActiveIn/P - Reading on the AC Input side ("grid" value)
N/985dad8185e7/vebus/261/Ac/ActiveIn/Connected - Grid status, publishes a 0 or 1
N/985dad8185e7/pvinverter/21/Ac/Power - PV inverter power, "21" will be your inverter ID
*Not entirely sure how I obtained "258", I probably used MQTT explorer as linked above. It's definitely not the same as your vebus ID though.
*ESS Assistant Required* These can either be read, or written to with N or W
N/985dad8185e7/settings/0/Settings/CGwacs/MaxDischargePower - Self-explanatory, I hope
N/985dad8185e7/settings/0/Settings/CGwacs/AcPowerSetPoint - "Grid set point"
N/985dad8185e7/settings/0/Settings/CGwacs/BatteryLife/State - ESS Mode, 9=Stay Charged, 10=Optimized w/o battery life, and I think 11= Optimized w/battery life
*I will continue updating and adding to this guide, I am just burnt out from typing all this out so far for now. To be added still is how to now get your HAC to talk back to the VenusOS device.*
It has been discussed earlier whether Venus OS can work on a Raspberry Pi Zero 2 W. Has there been any changes in 2022? Is it still impossible?
I am a recent and enthusiastic convert to the Victron philosophy ie its a sincere approach to the black art of Lab charging. I wish I had discovered this source sooner. I have got an IP65 24/8 charge block for my mobility scooter battery 24v 80 Ah. I am delighted with the Android app run on a tablet that allows customisation and very important data logging of history. My charger is indoors and the battery is in an outside shed so battery temp comp will be wildly wrong say 10C vs 25C. There is no way AFAIK to input a manual temp for the battery and no external temp probe for the charger.
I can only see a work around where you adjust the abs volts up at -.32mV/C. So for 10C I would go from 27.6 to 27.7 (-4mV/C x 15)
Is this reasonable? IMHO the app should include a feature to allow manual input of assumed battery temp (for normal low charging plan)
I thought i´d share some of my installation pics. (if someone is interested?)
It is in a 2017 Fiat Ducato made by Pössl.
It is a wonderful system and i have totalcontrol.
Not exactly a question - but I thought someone may find this helpful with utilising the MQTT data available through the Venus MQTT broker.
I've recently installed a small solar PV system using a Victron MPPT charger and Inverter. I've had an MQTT based home monitoring system running for some time and was pleased to see the Venus OS was available for the Raspberry Pi as my home system is all Arduino & Raspberry Pi based. Having installed and set up Venus OS and the MQTT broker I found it very difficult to utilise the myriad of topics and data available, even when adding a topics list to the keepalive message, due to the varying topic formats.
In my relatively simple MQTT structure each data source has an MQTT broker and publishes topics in a fixed format 'Source/DeviceParameter/Data'. A central MQTT broker is 'bridged' with each of the sources, and I use a simple Python script (found online) to accumulate data into an InfluxDB database, which is then displayed using Grafana. The Python script expects the fixed format topics and is where I was struggling to incorporate the Victron data.
The solution turned out to be very simple, without any programming :-) I installed 'Venus OS Large' and enabled MQTT and Node Red. The MQTT broker doesn't publish any data if you never send it a 'keepalive' message. Using Node Red I added Victron Energy nodes for the Charger and Inverter data I wanted and connected each to an 'MQTTout' node set up to publish topics in the simple format I use, direct to the Victron MQTT broker. Voila, the Venus MQTT now broker publishes the data I want, in the format I want, directly into my existing system by doing nothing other than bridging the Venus MQTT broker into my system :-)
Not rocket science, but it has proved a lot easier than modifying my existing system to accomodate the Victron format MQTT data :-)
Info only for those who are interested.
the below works on all 123 smart BMS - Gen 2 and Gen 3 BMS systems.
GX Units MUST BE on FW 2.80 or latter
123 smart have released a free app that installs to all GX devices, they can also supply a small USB interface /or you can supply your own - that connects to the 123 end board ext data out connection and then via USB to the Cerbo,CCGX,Venus
this then adds another battery monitor to the system if you have more than one
you can also add extra 123BMS USB interfaces if you have more than one BMS to monitor
you can then see the Highest and the lowest cell voltage
also if a high or low even occurs then a alarm is sent to the notifications area.
The software is added by inserting a sdcard into the gx units SD card slot, Softare can be downloaded from 123smarts site. Download site HERE
(Edited 23/01/2022 ) I now used Kevins GuiMods program to install - as onced the GuiMods Package manager is installed you can also select to install the 123smart BMS software = Plus GuiMods updates the software if a new release is issued by 123 = Download Gui Modes Here
Copy of the screen displays are below.