Venus OS v3.70~37 available for public testing

Beta testing Venus OS beta testing
, , , , , ,
1

Good day!

A fresh thread for v3.70 beta feedback.

If you haven’t seen them yet, make sure to go through the v3.60 slides: public - Venus OS v3.60 Release - Google Slides .

Change log below, and first please make yourself aware with the beta testing instructions:

Instructions 1 of 3: Venus OS beta testing & how to join/install

In case you don’t know what this message is about, please start with reading this link, which explains the Venus OS beta program. Venus OS is the software running on all our GX devices, such as the Cerbo GX.

Instructions 2 of 3: How to report an issue?

Before posting, please check if your issue already exists, in which case please contribute by replying to that issue or up-voting it.

Only once you are sure its a new possible issue, start a new topic.

Lastly, before posting, preferably first revert to the latest official release, to double check if the issue you’re seeing was present there as well. Regressions require a different treatment than other issues and bugs. And let us know if you did that, and what the difference is. A perfect report contains:

  • How its expected to work
  • How it doesn’t work as expected
  • Details on the system
  • What you’ve already tried to make sure its not a setting or other issue.

Please take note that that this works quite differently than it used to do on the old version of Community:

  • For a new issue, open a new topic. Instead of adding a new reply at the bottom.
  • To add to an already open issue, aka topic, reply to that. Or just upvote it if you have the same issue. This will help us a lot in determining its importance and manage our priorities.

Instructions 3 of 3: using Node-RED, Kevin’s SetupHelper, GuiMods, dbus-serialbattery or other add-ons?

Node-RED or Signal K

In case you are running Node-RED or SignalK, then please at least say so in your bug report.

SetupHelper, GuiMods, dbus-serialbattery

Modifications such as the popular GuiMods, SetupHelper, dbus-serialbattery and other 3rd party add-ons: do not report your issues here. Please do it elsewhere instead; and make sure to check out the related issue tracker first.

These topics and beta testing and bug reports are only for clean systems.

Popular bug report / discussion threads:

Change log

v3.70~37

  • New UI

    • Add new Switch types, use Node-RED Virtual Switches to see them.
    • ESS: show self-consume from battery more often
    • EV charger: show correct charge current (fix clamped value)
    • EV charger: use sensible min/max defaults when setting charge current
    • Notifications: close card panes before showing notifications
    • Setting menus: reduce ListButton touch area, less chance of accidentally changing a setting.

  • include the cerbosgx in the einstein image

Venus OS Large

  • Victron Node Palette:
    • Virtual devices:
      • Switch: let default name of switch mimic the swich type instead of switch [1-4]
      • disallow changing the device type after deployment
      • set connection to show Node-RED and update product name
      • Switches: add supporting the UI control that allows to hide a control from the UI Switch pane.
      • Virtual battery: add configurable default
      • Introduce further virtual switch types:
        • temperature setpoint
        • stepped switch
        • numeric input
        • three-state switch
    • All above is node-red-contrib-victron 1.6.44 → 1.6.50

Developer:

  • Run initscripts on hotpluggable USB drives
    • Modified the script to look for venus-runtime-*.tar.gz at runtime. Adds to already existing feature that runs scripts at boot.
  • Update /opt/victronenergy/dbus-systemcalc-py/ext/velib-python/tools/dbus-signal-cntr.py to improve its formatting. Especially for developers this is a nice easy tool to check that you’re driver is not overloading the system by sending updates on dbus too often.

v3.70~35

  • Fix crash in systems where “Control MK3-USB connected inverter/charger system” was turned on, even though there was no USB-connected inverter/chargers. (Introduced in v3.70~30). Thanks to @ogps for reporting

v3.70~34

General

  • ESS: Fix bug in peak shaving function when the “Self-consumption from battery” setting is set to “Only critical loads”

New UI

  • Add option to disable each relay in the GX. Since setting it to manual now causes the relay to show up in the Switch pane, we needed to add an option to hide it when unused. That is now done.
  • Add option to set the polarity for the relays in the GX. Ie. make On close the relay, or make On open the relay.
  • Fix bug that caused input current limit settings to be 0.1A off from the value that was actually set. Ie. setting it to 13.5A resulted in the value ending up to be 13.4A. Bug was introduced recently, during v3.70 development
  • Small improvements to some of the switch pane controls.
  • Improve key navigation.
  • Various other small fixes and improvements

v3.70~33

  • No changes

v3.70~29 up to and including v3.70~32

  • DVCC: Add limited CCL control for second Multi aka VE.Bus systems connected to a GX using an MK3-USB. Having such control at all was introduced in a recent official release, but didn’t include CCL control of the second Multi. The use case for which it’s added now is when having each system connected to a different AC source, for example one to the grid and the other to a generator. And the feature us that when a BMS requests a complete stop of charging, for example due to low cell temperature or high cell voltage, it now also stops charging by the 2nd Multi.
  • wireless tank senders: Fix status remaining non-zero after correcting bad user settings.
  • fix communication issue (Remote Console on VRM for Classic UI + Node-RED on VRM + SignalK on VRM) on IPv6 only networks. And fix it for networks blocking outbound traffic on port 22. Both issues were introduced in v3.60 or earlier.
  • Fix potential issue with MGE Batteries regarding reporting of min/max cel voltages/temperatures. Introduced in v3.70.
  • Fix issue with the Energy Solutions SmartSwitch where the Show UI control was broken. Broken somewhere in v3.70.
  • NMEA2000-out: transmit alarms on the GX onto the N2K network. Garmin will visualize them. Still coming is a feature to disable this in case so whished.
  • MFD Marine HTML5 App: Adjust app theme (dark/light) when system theme changes and when in Auto Mode.
  • SolarEdge PV Inverters: Fix bug where limiter setup was repeated multiple times, increasing by one on each connection loss: after many connection losses, this would take progressively longer and longer to complete reconnection to an inverter.
  • SolarEdge PV Inverters: Fix bug where limiting would briefly be available even when disabled in settings.

Under water / developers:

  • Add /inject path which allows to create a notification in the UI
  • Fix memory leak causing a restart of an underlying service
  • NMEA2000-out: report language as ISO 639-1 string on VREG 0xE3E2.
  • Made valgrind work, and similar tools. Install using opkg.

v3.70~28

Various

  • ESS: Fix bug causing the “grid meter is missing” alarms to no longer show up when the meter was lost.
  • Marine MFD HTML5 app: fix possible light/dark/light (or the other way around) flickering when opening gui-v2
  • Fix issue that (sometimes) caused login information to get lost when accessing Remote Console on LAN, or for example in the GX Android Wifi Display App; when having the “Local network security profile” setting set to Secure or Weak.

Venus OS Large / Node-RED

  • Fix a bug that caused input nodes to not receive the initial value. Introduced in the previous beta version, v3.70~27, now fixed.
  • Included node-red-contrib version is v1.6.44

v3.70~27

Dynamic ESS

  • Fix bug related when having a (also small) negative grid set-point set in the ESS parameters by the installer/user.

DVCC

  • Fix bug causing a system with a Lynx Smart BMS, and Lynx Smart BMS NG, to stop all chargers, instead of only those configured to be charging the main battery bank (System instance is the same as the GX)

New UI / gui-v2

  • Fix onscreen keyboard no longer working. Issue was introduced earlier during v3.70 development.
  • Fix gui-v2 no longer working, as Remote Console, on certain Marine MFDs. Issue was introduced earlier during v3.70 development.
  • Fix issues related to power flow/electron direction
  • Add AC Loads and Essential Loads drill downs
  • Various UX related improvements to the Switch pane controls
  • Fix loading QML from filesystem on the GX, this restores the ability to alter QML files directly on the GX.
  • Various other stability improvements.

PV Inverter support

  • Fix issues related to Enphase limiting

Venus OS Large / Node-RED

  • Fix grid meter frequency not being updated for EM540 grid meters as well as a few other grid meters.
  • Fix “Not connected to D-Bus” error happing on certain nodes after doing a deploy from the Node-RED editor. The connection would restore after 20 to 60 seconds. Now the error doesn’t happen at all anymore.
  • A few more stability related improvements.
  • Above changes are all due to updating the node-red-contrib-victron to v1.6.43.

Thank you @ron_h, @M_Lange as well as others for your bug reports!

v3.70~26

N2K Motor drives:

  • Add support for function code 155 (motor) and 160 (engine gateway), while still allowing the (incorrect) function code 180 as well.
  • Add support for more brands/models of motor drives by adding support for the combustion engine PGNs 127488, 127489 and 127493. Available data through this set of PGNs is motor direction, rpm and motor temperature.

Venus OS Large / Node-RED

  • Update Victron Node pallette (node-red-contrib-victron v1.6.42):
  • restore cached values immediately on node re-deployment, thus preventing a dbus error on re-deploy.
  • Prevent crash of Node-RED when sending null or undefined for “text” when setting the status of a node
  • Reconnect to the dbus quicker in case the connection to the dbus does get lost. v3.70 already had faster reconnects defined than v3.60 did, per v1.6.42 its further sped up

v3.70~25

  • More RV-C improvements (I’ll detail all of it in the coming days)
  • MQTT: Add protection against brute force attempts
  • HTTP(S): login screen: fix layout issue + add protection against brute force attempts.

v3.70~24

Classic UI:

  • Fix order of menu entries. (Qt 6.8 changed how indices are looked up, the fix makes the show property function properly again.). Thank you @kwindrem , and others for reporting.

New UI:

  • Show relevant toast notification when second relay is changed to manual
  • Resetting gauge ranges resets boat page gauge ranges (backported to 3.64)
  • Show ‘power’ on BoatPage gauges when ‘current’ is invalid (backported to 3.64)
  • Show motor drive current when current is selected as the preferred measure (backported)
  • Overview: open genset page for dcgenset drilldown
  • Always show PageGenset for genset services
  • PvInverterPage should link to product page instead of device info
  • Battery settings: allow System menu to be opened (backported to 3.64)
  • Add registration and data link status to GSM page, logic fixes (backported to 3.64)
  • Refer to dcgenset inputs as “DC genset” instead of “Generic source”

New UI Web Version / Remote Console:

  • Apply CSS fixes to show GUI further on older MFD devices
  • Add visible error information UI loading fails
  • Save latest query param setting for css display type
  • Extend canvas to full height and center item in the window
  • Fix color flickering on loading
  • Fix logo colors on splash screen
  • Display loading bar when downloading UI

Venus OS Large / Node-RED:

  • Improve first time use of Node-RED on Venus OS: it is now no longer necessary to deploy once to be able to start configuring nodes. This fix was done by installing a flows.json that includes the required Config node; if there is no flows.json yet.

v3.70~22 and 23

  • GX GSM/LTE/4G modem: Few more improvements.

Developers

  • Add SDK to compile for 64bit targets (aarch64)

v3.70~21

  • GX GSM/LTE/4G modem: Fix gui-v2 menu saying Offline while it was actually working ok.

v3.70~20

  • GX GSM/LTE/4G modem: Make low-level modem command handling more robust and improve PDP context setup.

v3.70~16, 17, 18 and 19

  • Fix various device / system capability recognition issues at boot-up. Introduced recently. These are being considered for a v3.64 official version to be released soon.
    • Fix DESS sometimes not available / appearing to be switched off.
    • Fix BMSes not properly detected at boot-up in some cases (depends on boot-up speed and such)
  • New UI v1.2.7
    • Webbrowser version: fix issue causing DVCC max. battery voltage to round to full integers, ie. 55 V instead of 55.2 V. This issue is also present in v3.62 or v3.63, and will be made available as official release v3.64 soon.
    • Add note to Modbus-TCP Server configuration pages explaining where/how to change the unit-ids.
    • Add feature to change the WiFi Access Point password.
    • Fix wrongly showing with the DC generator label instead of the selected type (Electric Drive, Fridge, Water pump, and so forth)
    • Various other visualisation / rendering fixes
    • Update translations.

Venus OS Large / Node-RED

  • Fix Relay control node configuration; broken earlier during v3.70 development.

Under the hood

  • Switch from Qt 6.6.x to Qt 6.8.3

v3.70~15

  • Fix broken VRM remote updates for some types of products. Introduced earlier during v3.70 development.
  • Various of RV-C related improvements. Will be detailed later
  • Fix Venus GX rootfs being mounted read/write by default instead of read-only. Fixes modifications check page for Venus GX as well.

v3.70~10, 11 and 12 and 13

  • Add GX internal relays to the new Switch pane as well as add option to name them. To use this, go to Settings → Integrations → Relays, there set the function of the relay to be Manual. Once done, go to the Device list, where you’ll find the relay and can (a) give it a name, (b) set a group name, which is to organise multiple switches on the Switch pane, and (c) hide it from the Switch pane when wanted. For example when just used be a Node-RED flow and the intention is not to have it visible as a controllable output in the user interface.
  • New UI:
    • Add user option to disable all animations. This can save up to 40% CPU on a Cerbo GX.
    • Improve keyboard navigation
    • Fix bug in controlling generators from settings page
    • Show BatteryLife info toast in ESS control card
    • Temp Sensor: Use product name if custom name is unavailable
  • Classic UI: fix link local address not being visible (also available in Venus OS v3.63 official)

Venus OS Large / Node-RED

  • Major change to all the Virtual devices: it is now possible to set multiple properties of a Virtual device in one message. This reduces CPU as well as reduces clutter in your flow design.

Before:
[screenshot]

After:
[screenshot]

Under the hood:

  • Improve startup-time a bit for systems using GX genset start/stop
  • CAN-bms protocol: add 0x357 frame, as an alternative to 0x356 for the battery to transmit its voltage, current and temperature, but then with 4 bytes for battery current instead of 2. This is to accommodate very large systems which overflow the 2-byte current values in 0x356.

v3.70~8 and v3.70~9

  • Fix login screen shown in web browsers while it shouldn’t. Broken in v3.70~7
  • Fix link local ip address not visible. Broken in v3.60
  • New UI: fix bug that sometimes DC Loads weren’t shown on the brief and overview page.

Venus OS Large / Signal K Server

  • Update from v2.13.5 to v2.14.4, and update all plugins, webapps and other packages to their latest version.

v3.70~7
New UI

  • Fix issue in setting PV Inverter position from within the Device List. (Thanks for Combi Noord for reporting this to us).

Venus OS Large / Node-RED

  • Victron node palette updated (node-red-contrib-victron v1.6.36)
    • Fix bug in sending in initial value at GX start-up as well as when doing a re-deploy, for nodes configured to send messages only when the value has changed. This bug was introduced in Venus OS v3.60.
    • Virtual Switches: rename latching to toggle.
    • Fix issue when using the Victron Node-RED palette in other Node-RED installs, for example when having Node-RED installed as a plugin inside Signal K. This bug was introduced recently during Venus OS v3.70 beta series.

v3.70~6

  • Fix BMVs no longer showing up since Venus OS v3.60. Some (early) production batches of BMVs are affected, and what happens is that the BMV is no longer visible after updating to v3.60 or later. Broken per v3.60, coming in v3.63.
  • Fix NMEA2000 instance configuration, worked in Remote Console but not on the GX display (Ekrano GX, GX Touch) since recent official versions. Fix will also be available in a v3.63 official release soon.
  • DESS: Avoid buying from grid after intended discharge

RS Family

  • Add SOC and Time to go for Inverter RS, was only available for the Multi RS
  • Hide solar details from the UI for models without solar

Tank sensors

  • Fix some tank sensor settings, broken per v3.60. Fix will also be available in a v3.63 official release soon.
  • Add tank shape configuration and high/low alarm configuration for wireless tank sensors (Mopeka)

Classic UI

  • Fix backlight intensity slider issue, broken per v3.60. Fix will also be available in a v3.63 official release soon.
  • UX improvements that prevents needing to click / tab in twice in certain conditions.

Bluetooth for VictronConnect

  • Stability / connection improvements when using a USB Bluetooth dongle.

Underwater

  • changes to allow changing the Wifi AP password. But there is no UI for that yet, coming soon.

v3.70~3 till ~5

New UI - general features & fixes

  • Add keyboard navigation feature
  • Brief page: show centre details also when 4 circular gauges are enabled, instead of up to three
  • Fix active AC input shown as ‘241’ when inverting, instead of ‘Disconnected’ or similar wording. This fix will be released as v3.64 official soon. Thank you
  • Improve Modifications Checks page
  • Firmware page: add item that shows the type of installed firmware (normal/large)
  • Various small rewordings
  • Make StatusBar notification icon clickable
  • Show minimum SoC on ESS control card only when needed

New UI - web browser version / Remote Console

  • Set color scheme based on device (laptop/tablet/phone) selected scheme (dark/light)
  • Fix being unable to load on a slow internet connect, thank you @BartChampagne for reporting
  • Add device mockup frame for WASM builds
  • Improve speed of opening / connecting
  • When opened on lan, open UI in device frame.

Other

  • Solar Edge PV Inverters: fix bug where inverters without a certain limiter support would now show no data at all. Introduced in v3.60 and affects only some Solar Edge models. Thank you Tim Griffioen for reporting
  • Improve boot-up time
  • Fix missing Power factor for ABB B23 & B24 meter. Thank you Marcel B for spotting this

Modbus-TCP Server

  • Add option to set Modbus-TCP server to read-only. Allows for much more secure option. Thank you @Bob_Bobson for the idea.

Venus OS large / Node-RED

  • node-red-contrib-victron 1.6.32 → 1.6.33
    • Add virtual generator
    • Return of the virtual switch
    • Save state of virtual devices
    • Reconnect virtual nodes to the dbus after loosing connection
    • Library update
    • Update documentation
  • Update Node-RED itself from v3.1.15 to 4.0.9

v3.60 → v3.70~2

  • Fix FzSonic salt batteries, support for them was completely broken in Venus 3.60. Thank you @smueff1970 for finding the problem and solution.
  • Remove support for Shelly grid meters on the CCGX. To save a but of CPU and memory resources. Shelly as a grid meter has never been supported officially, is also not planned at at the moment.
  • Fix Venus GX ethernet for certain production. series of the Venus GX. Broken in v3.60 and also released as v3.61.
  • Fix NMEA2000 / VE.Can compatibility issue with products being configured with a label using UTF-8 characters. Thank you @MotoringMariah for the report!

Under the hood:

  • Improve startup performance : reduce boot time. Especially when going from one major version to another where, sometimes, lots of new user parameters or under water settings are added.

  • Energy Meters

    • Add power factor for ABB B21, B23 and B24 meters
    • Add power factor for Carlo Gavazzi EM540 and EM530 meters
      • Also works if meter is configured single phase.
      • Also works if L2 is used for a PV-inverter.
    • Further improve resilience against out of order packets and other wifi or lan network issues for the VM-3P75CT.

Modbus-TCP

  • Add register for Venus version (register 834)

EV Charging Station

  • Fix issue that could cause the EV Charger to reduce charge current while not needed, in combination with overload warnings of connected Multis/Quattros.

Node-RED

  • victron-vrm-api v0.2.14 & v0.2.15
    • Library update
    • Fix: Correct date calculation for Stats API
    • Improve debugging
2

The boss never sleeps does he? (That’s a compliment towards your dedication by the way)

On topic: Did the ‘virtual devices / device instance / system priority’ topic get touched upon? (ref: virtual GPS)

PS, I can’t find the menu for changing device instance numbers anymore. I have traversed all the normal and debug setting trees through the GUIv2 console settings page and still can’t find them anymore. I suspect I am overlooking something too silly to mention but I would nevertheless appreciate a hint towards where to look.

3

SignalK still on 2.14…. can we go to 2.15+ or directly to 2.16 please….

1 Like
4

Yes. And its not forgotten - some other things had priority; and v3.70 is not out for release yet. Coming!

1 Like
5

Here is a screenshot showing all switch types:

image
image822×554 39.6 KB

Note that I don’t know why the names all show up twice; something to fix later!

Its becoming the perfect & quite complete set of UI controls for your digital switching & Node-RED flows if I may say so myself!

1 Like
6

No not yet. When that is fixed it will be mentioned. One or two weeks I expect.

VRM Device instances can be set in Settings → VRM → VRM Device Instances.

1 Like
7

Aren’t you overly focused on feature development at the cost of maturing existing functionality? Just saying, don’t shoot the messenger please.

8

Unbelievable, I must indeed have overlooked that at least ten times. :folded_hands:

9

I don’t think so. But pls lets not make a long discussion on that here.

10

Ok

11

Hi Matthijs, this is a great new feature I was waiting for since the introduction of the virtual switches :+1:

I noticed, that one can also read/set the temperature setpoint state and the numeric input state by Node-RED, but I’m not able to read/set it in the UI either by double clicking or long pressing. Am I doing something wrong or is it still under development?

Cheers, luphi

12

Out of pure curiosity, what is your use case for your request for 2.15+…?

13

https://www.npmjs.com/package/@canboat/visual-analyzer

1 Like
14

Screenshot_2025-09-22-02-03-25-055
Screenshot_2025-09-22-02-03-25-0551339×800 137 KB

I’ve been exploring the virtual devices some more, the switches do look good, to be fair.

Then, I noticed a significant reduction in D-bus round trip times after the ~37 update, or better said, a return to the low 1ms averages from ~25 with higher values with the betas in between : 4ms for the ~33 and 6ms for the ~35.

This on a MP II 5000 GX with fairly extensive Node-RED flow processing

Another observation: the virtual battery does not allow setting a ’time to go’ longer then 1 x 24 x 3600 seconds (1 day) while the BMV Smartshunt goes up to 10 days - 1 second.

And there is no setting for the highest cell voltage, only for the lowest cell voltage without any ability to indicate which cell, defaults back to cell 0.

15

Another observation: the virtual battery does not allow setting a ’time to go’ longer then 1 x 24 x 3600 seconds (1 day) while the BMV Smartshunt goes up to 10 days - 1 second.

Good find. It looks like I missed a zero on that. I’ve fixed that to become part of the next release.

And there is no setting for the highest cell voltage, only for the lowest cell voltage without any ability to indicate which cell, defaults back to cell 0.

I’ve been following dbus · victronenergy/venus Wiki · GitHub, which doesn’t define an info field for the highest cell voltage.

16

That doesn’t make sense, both are required for safe operation. And IIRC, the normal (blue) battery nodes are rather sparse in addressable settings, forcing the use of the general (orange) input/control nodes.

What about this list below (and keep an eye out for the ability to register which cell of which string measures to have min / max cell voltage. I would love to be able to map our actual high performance battery build, based on 6S modules, 2 in series for 12S strings with upto 15 strings in parallel. (And a dedicated analog control system to keep that very well balanced and safe, but still need to be able to monitor and identify which are the minimum and maximum voltage outliers including their location). Same goes for temperature. All that data is readily available, would be very valuable to be able to access it from within the VenusOS platform/GUI.

Lynx Smart BMS & Lynx Ion Only:

/State

/ErrorCode

/SystemSwitch

/Balancing

/System/NrOfBatteries

/System/BatteriesParallel

/System/BatteriesSeries

/System/NrOfCellsPerBattery

/System/MinCellVoltage

/System/MaxCellVoltage

/System/MinCellTemperature

/System/MaxCellTemperature

17

While you’re at it, did you see the discussion about virtual devices instance numbering in relation to prioritizing hardware vs virtual devices as primary data source systemwide, and possibly the ability to free the boat page from those systemwide priority settings altogether, by introducing a boat page specific device selection table. (Another GPS, virtual, filtered or other. And even more useful another battery, virtual or otherwise). Seems a very logical functional improvement to allow decoupling of the boat page (propulsion related) data sources from those of the rest of the (house/AC power energy storage) system. Or the other way around, not a a very fitting system design limitation to force the propulsion system and the house/AC power system to run from a shared batterybank. On an electrical boat I strongly prefer to keep those separate to prevent a single point of failure capable of shutting down all electricity at once.

If you want Christmas to come early this year, taking the suggestions above onboard would pretty much do the job. Alternatively an update on making GUIv2 mods work across local and remote displays would potentially be an equally useful solution.

18

Thanks @mpvader! I noticed the peak shaving changelog item in the prior beta. Is it still on the roadmap to allow users to disable peak shaving completely?

1 Like
19

Yes this is quite interesting indeed.

As an example I created the following setup:

  • A BMV Smartshunt as Battery Monitor for the Boardnet Battery (wired to a Multiplus II)
  • The BMV relay set to ‘Charger mode’ (3 sets of 4 x 12V 250Ah GEL Lead-acid batteries)
  • A flow that switches the Multiplus II (ESS) between ‘keep batteries charged’ and ‘external control’ (passthrough) WHEN the BMV turns its (charger mode) relay on and off (no wiring, just by reading and parsing in Node-RED)
  • A virtual ‘Three-state’ Boardnet Battery Charger switch, that allows the skipper to override the BMV ‘Charger mode’ to ‘Manual mode’ and subsequently allows manual charging to be activated.

Functionally this setup ensures the MultiPlus II not to charge or discharge the battery when shorepower is connected, until the battery has been sufficiently depleted, while at the same time always providing contineous (shore or inverter) AC power on board. With the addition of an easy to access manual charging overide switch just in case.
And the actual BMV relay contacts are still free to use for a charge indicator light or even for switching on secondary charger bank on the other L2, L3 phases, not in use for the Multiplus II itself (L1).

image
image798×622 46.4 KB

image
image414×488 8.27 KB

image
image1001×322 30.9 KB

[
    {
        "id": "06bdc965eb50c8af",
        "type": "group",
        "z": "8fb5afb2b0b585a3",
        "style": {
            "stroke": "#999999",
            "stroke-opacity": "1",
            "fill": "none",
            "fill-opacity": "1",
            "label": true,
            "label-position": "nw",
            "color": "#a4a4a4"
        },
        "nodes": [
            "9f6f3040a4c57ace",
            "c17823e17ee98bde",
            "f3a7674aaf6c5a57",
            "20c42433f976c57c",
            "84b892ebb016bade",
            "c3dfefb10bc97e3e",
            "8df3a8241f381f16",
            "5fd958e4ae85c36c",
            "0337a8c7d829dbdc",
            "7cfb17ac60f0d034",
            "73267f268199e7b4",
            "a5d3873204823f72",
            "87badbbc49cce7db",
            "290f861a080a3319",
            "cfccbfe0c2d90d3a",
            "3a7d8bd2ecadb41a",
            "f88bcd321d138867"
        ],
        "x": 34,
        "y": 2539,
        "w": 1232,
        "h": 382
    },
    {
        "id": "9f6f3040a4c57ace",
        "type": "victron-input-ess",
        "z": "8fb5afb2b0b585a3",
        "g": "06bdc965eb50c8af",
        "service": "com.victronenergy.settings",
        "path": "/Settings/CGwacs/Hub4Mode",
        "serviceObj": {
            "service": "com.victronenergy.settings",
            "name": "Venus settings"
        },
        "pathObj": {
            "path": "/Settings/CGwacs/Hub4Mode",
            "type": "enum",
            "name": "ESS mode",
            "enum": {
                "1": "Optimized mode or 'keep batteries charged' and phase compensation enabled",
                "2": "Optimized mode or 'keep batteries charged' and phase compensation disabled",
                "3": "External control"
            },
            "mode": "both"
        },
        "name": "",
        "onlyChanges": false,
        "x": 170,
        "y": 2640,
        "wires": [
            []
        ]
    },
    {
        "id": "c17823e17ee98bde",
        "type": "victron-input-ess",
        "z": "8fb5afb2b0b585a3",
        "g": "06bdc965eb50c8af",
        "service": "com.victronenergy.settings",
        "path": "/Settings/CGwacs/BatteryLife/State",
        "serviceObj": {
            "service": "com.victronenergy.settings",
            "name": "Venus settings"
        },
        "pathObj": {
            "path": "/Settings/CGwacs/BatteryLife/State",
            "type": "enum",
            "name": "ESS state",
            "enum": {
                "1": "BatteryLife enabled (GUI controlled)",
                "2": "Optimized Mode /w BatteryLife: self consumption",
                "3": "Optimized Mode /w BatteryLife: self consumption, SoC exceeds 85%",
                "4": "Optimized Mode /w BatteryLife: self consumption, SoC at 100%",
                "5": "Optimized Mode /w BatteryLife: SoC below dynamic SoC limit",
                "6": "Optimized Mode /w BatteryLife: SoC has been below SoC limit for more than 24 hours. Charging the battery (5A)",
                "7": "Optimized Mode /w BatteryLife: Inverter/Charger is in sustain mode",
                "8": "Optimized Mode /w BatteryLife: recharging, SoC dropped by 5% or more below the minimum SoC",
                "9": "'Keep batteries charged' mode is enabled",
                "10": "Optimized mode w/o BatteryLife: self consumption, SoC at or above minimum SoC",
                "11": "Optimized mode w/o BatteryLife: self consumption, SoC is below minimum SoC",
                "12": "Optimized mode w/o BatteryLife: recharging, SoC dropped by 5% or more below minimum SoC"
            }
        },
        "name": "",
        "onlyChanges": false,
        "x": 170,
        "y": 2580,
        "wires": [
            []
        ]
    },
    {
        "id": "f3a7674aaf6c5a57",
        "type": "victron-output-ess",
        "z": "8fb5afb2b0b585a3",
        "g": "06bdc965eb50c8af",
        "service": "com.victronenergy.settings",
        "path": "/Settings/CGwacs/Hub4Mode",
        "serviceObj": {
            "service": "com.victronenergy.settings",
            "name": "Venus settings"
        },
        "pathObj": {
            "path": "/Settings/CGwacs/Hub4Mode",
            "type": "enum",
            "name": "ESS mode",
            "enum": {
                "1": "Optimized mode or 'keep batteries charged' and phase compensation enabled",
                "2": "Optimized mode or 'keep batteries charged' and phase compensation disabled",
                "3": "External control"
            },
            "mode": "both"
        },
        "name": "",
        "onlyChanges": false,
        "x": 1120,
        "y": 2640,
        "wires": []
    },
    {
        "id": "20c42433f976c57c",
        "type": "victron-output-ess",
        "z": "8fb5afb2b0b585a3",
        "g": "06bdc965eb50c8af",
        "service": "com.victronenergy.settings",
        "path": "/Settings/CGwacs/BatteryLife/State",
        "serviceObj": {
            "service": "com.victronenergy.settings",
            "name": "Venus settings"
        },
        "pathObj": {
            "path": "/Settings/CGwacs/BatteryLife/State",
            "type": "enum",
            "name": "ESS state",
            "enum": {
                "1": "BatteryLife enabled (GUI controlled)",
                "2": "Optimized Mode /w BatteryLife: self consumption",
                "3": "Optimized Mode /w BatteryLife: self consumption, SoC exceeds 85%",
                "4": "Optimized Mode /w BatteryLife: self consumption, SoC at 100%",
                "5": "Optimized Mode /w BatteryLife: SoC below dynamic SoC limit",
                "6": "Optimized Mode /w BatteryLife: SoC has been below SoC limit for more than 24 hours. Charging the battery (5A)",
                "7": "Optimized Mode /w BatteryLife: Inverter/Charger is in sustain mode",
                "8": "Optimized Mode /w BatteryLife: recharging, SoC dropped by 5% or more below the minimum SoC",
                "9": "'Keep batteries charged' mode is enabled",
                "10": "Optimized mode w/o BatteryLife: self consumption, SoC at or above minimum SoC",
                "11": "Optimized mode w/o BatteryLife: self consumption, SoC is below minimum SoC",
                "12": "Optimized mode w/o BatteryLife: recharging, SoC dropped by 5% or more below minimum SoC"
            }
        },
        "name": "",
        "onlyChanges": false,
        "x": 1120,
        "y": 2580,
        "wires": []
    },
    {
        "id": "84b892ebb016bade",
        "type": "function",
        "z": "8fb5afb2b0b585a3",
        "g": "06bdc965eb50c8af",
        "name": "mux",
        "func": "return msg;",
        "outputs": 1,
        "timeout": 0,
        "noerr": 0,
        "initialize": "",
        "finalize": "",
        "libs": [],
        "x": 610,
        "y": 2640,
        "wires": [
            [
                "c3dfefb10bc97e3e"
            ]
        ]
    },
    {
        "id": "c3dfefb10bc97e3e",
        "type": "function",
        "z": "8fb5afb2b0b585a3",
        "g": "06bdc965eb50c8af",
        "name": "translate",
        "func": "if ( msg.payload == 0 )\n{\n    msg.payload = 3;    // ESS external control\n} else\n{\n    msg.payload = 2;    // ESS keep batteries charged, pgase compensation disabled\n}\nreturn msg;",
        "outputs": 1,
        "timeout": 0,
        "noerr": 0,
        "initialize": "",
        "finalize": "",
        "libs": [],
        "x": 920,
        "y": 2640,
        "wires": [
            [
                "f3a7674aaf6c5a57"
            ]
        ]
    },
    {
        "id": "8df3a8241f381f16",
        "type": "victron-virtual",
        "z": "8fb5afb2b0b585a3",
        "g": "06bdc965eb50c8af",
        "name": "Boardnet Battery Charger",
        "device": "switch",
        "default_values": true,
        "battery_capacity": 25,
        "include_battery_temperature": false,
        "battery_voltage_preset": "24",
        "battery_voltage_custom": 24,
        "generator_type": "ac",
        "generator_nrofphases": 1,
        "include_engine_hours": false,
        "include_starter_voltage": false,
        "include_history_energy": false,
        "grid_nrofphases": 1,
        "include_motor_temp": false,
        "include_controller_temp": false,
        "include_coolant_temp": false,
        "include_motor_rpm": true,
        "include_motor_direction": true,
        "position": 0,
        "pvinverter_nrofphases": 1,
        "switch_count": 1,
        "switch_1_type": 9,
        "switch_1_min": "0",
        "switch_1_max": "100",
        "switch_1_initial": 0,
        "switch_1_label": "",
        "switch_1_unit": "",
        "switch_1_step": 1,
        "switch_2_type": 1,
        "switch_2_min": 0,
        "switch_2_max": "",
        "switch_2_initial": 0,
        "switch_2_step": 1,
        "switch_2_label": "",
        "switch_2_unit": "",
        "switch_3_type": 1,
        "switch_3_min": 0,
        "switch_3_max": "",
        "switch_3_initial": 0,
        "switch_3_step": 1,
        "switch_3_label": "",
        "switch_3_unit": "",
        "switch_4_type": 1,
        "switch_4_min": 0,
        "switch_4_max": "",
        "switch_4_initial": 0,
        "switch_4_step": 1,
        "switch_4_label": "",
        "switch_4_unit": "",
        "fluid_type": 0,
        "include_tank_battery": false,
        "include_tank_temperature": false,
        "tank_battery_voltage": 3.3,
        "tank_capacity": 0.2,
        "temperature_type": 2,
        "include_humidity": false,
        "include_pressure": false,
        "include_temp_battery": false,
        "temp_battery_voltage": 3.3,
        "x": 670,
        "y": 2580,
        "wires": []
    },
    {
        "id": "5fd958e4ae85c36c",
        "type": "victron-output-custom",
        "z": "8fb5afb2b0b585a3",
        "g": "06bdc965eb50c8af",
        "service": "com.victronenergy.switch/101",
        "path": "/SwitchableOutput/output_1/Auto",
        "serviceObj": {
            "service": "com.victronenergy.switch/101",
            "name": "Boardnet Battery Charger (101)"
        },
        "pathObj": {
            "path": "/SwitchableOutput/output_1/Auto",
            "name": "/SwitchableOutput/output_1/Auto",
            "type": "number",
            "value": 0
        },
        "name": "",
        "onlyChanges": false,
        "x": 1000,
        "y": 2820,
        "wires": []
    },
    {
        "id": "0337a8c7d829dbdc",
        "type": "victron-output-custom",
        "z": "8fb5afb2b0b585a3",
        "g": "06bdc965eb50c8af",
        "service": "com.victronenergy.battery/278",
        "path": "/Settings/RelayMode",
        "serviceObj": {
            "service": "com.victronenergy.battery/278",
            "name": "Boardnet Battery  (278)"
        },
        "pathObj": {
            "path": "/Settings/RelayMode",
            "name": "/Settings/RelayMode",
            "type": "number",
            "value": 1
        },
        "name": "",
        "onlyChanges": false,
        "x": 1070,
        "y": 2880,
        "wires": []
    },
    {
        "id": "7cfb17ac60f0d034",
        "type": "victron-input-custom",
        "z": "8fb5afb2b0b585a3",
        "g": "06bdc965eb50c8af",
        "service": "com.victronenergy.battery/278",
        "path": "/Settings/RelayMode",
        "serviceObj": {
            "service": "com.victronenergy.battery/278",
            "name": "Boardnet Battery  (278)"
        },
        "pathObj": {
            "path": "/Settings/RelayMode",
            "name": "/Settings/RelayMode",
            "type": "number",
            "value": 1
        },
        "name": "",
        "onlyChanges": true,
        "x": 230,
        "y": 2820,
        "wires": [
            [
                "f88bcd321d138867"
            ]
        ]
    },
    {
        "id": "73267f268199e7b4",
        "type": "function",
        "z": "8fb5afb2b0b585a3",
        "g": "06bdc965eb50c8af",
        "name": "manual - charger",
        "func": "if ( msg.payload == 0 ) // 0: manual\n{\n    msg.payload = 2;    // manual control\n} else {                // 1 : auto\n    msg.payload = 1;    // charger  control\n}\nreturn msg;",
        "outputs": 1,
        "timeout": 0,
        "noerr": 0,
        "initialize": "",
        "finalize": "",
        "libs": [],
        "x": 650,
        "y": 2880,
        "wires": [
            [
                "0337a8c7d829dbdc"
            ]
        ]
    },
    {
        "id": "a5d3873204823f72",
        "type": "victron-input-custom",
        "z": "8fb5afb2b0b585a3",
        "g": "06bdc965eb50c8af",
        "service": "com.victronenergy.battery/278",
        "path": "/Relay/0/State",
        "serviceObj": {
            "service": "com.victronenergy.battery/278",
            "name": "Boardnet Battery  (278)"
        },
        "pathObj": {
            "path": "/Relay/0/State",
            "name": "/Relay/0/State",
            "type": "number",
            "value": 0
        },
        "name": "",
        "onlyChanges": true,
        "x": 210,
        "y": 2700,
        "wires": [
            [
                "cfccbfe0c2d90d3a",
                "84b892ebb016bade"
            ]
        ]
    },
    {
        "id": "87badbbc49cce7db",
        "type": "victron-output-custom",
        "z": "8fb5afb2b0b585a3",
        "g": "06bdc965eb50c8af",
        "service": "com.victronenergy.battery/278",
        "path": "/Relay/0/State",
        "serviceObj": {
            "service": "com.victronenergy.battery/278",
            "name": "Boardnet Battery  (278)"
        },
        "pathObj": {
            "path": "/Relay/0/State",
            "name": "/Relay/0/State",
            "type": "number",
            "value": 0
        },
        "name": "",
        "onlyChanges": false,
        "x": 1090,
        "y": 2760,
        "wires": []
    },
    {
        "id": "290f861a080a3319",
        "type": "victron-input-custom",
        "z": "8fb5afb2b0b585a3",
        "g": "06bdc965eb50c8af",
        "service": "com.victronenergy.switch/101",
        "path": "/SwitchableOutput/output_1/State",
        "serviceObj": {
            "service": "com.victronenergy.switch/101",
            "name": "Boardnet Battery Charger (101)"
        },
        "pathObj": {
            "path": "/SwitchableOutput/output_1/State",
            "name": "/SwitchableOutput/output_1/State",
            "type": "number",
            "value": 0
        },
        "name": "",
        "onlyChanges": true,
        "x": 300,
        "y": 2760,
        "wires": [
            [
                "87badbbc49cce7db"
            ]
        ]
    },
    {
        "id": "cfccbfe0c2d90d3a",
        "type": "victron-output-custom",
        "z": "8fb5afb2b0b585a3",
        "g": "06bdc965eb50c8af",
        "service": "com.victronenergy.switch/101",
        "path": "/SwitchableOutput/output_1/State",
        "serviceObj": {
            "service": "com.victronenergy.switch/101",
            "name": "Boardnet Battery Charger (101)"
        },
        "pathObj": {
            "path": "/SwitchableOutput/output_1/State",
            "name": "/SwitchableOutput/output_1/State",
            "type": "number",
            "value": 0
        },
        "name": "",
        "onlyChanges": false,
        "x": 1000,
        "y": 2700,
        "wires": []
    },
    {
        "id": "3a7d8bd2ecadb41a",
        "type": "victron-input-custom",
        "z": "8fb5afb2b0b585a3",
        "g": "06bdc965eb50c8af",
        "service": "com.victronenergy.switch/101",
        "path": "/SwitchableOutput/output_1/Auto",
        "serviceObj": {
            "service": "com.victronenergy.switch/101",
            "name": "Boardnet Battery Charger (101)"
        },
        "pathObj": {
            "path": "/SwitchableOutput/output_1/Auto",
            "name": "/SwitchableOutput/output_1/Auto",
            "type": "number",
            "value": 0
        },
        "name": "",
        "onlyChanges": true,
        "x": 300,
        "y": 2880,
        "wires": [
            [
                "73267f268199e7b4"
            ]
        ]
    },
    {
        "id": "f88bcd321d138867",
        "type": "function",
        "z": "8fb5afb2b0b585a3",
        "g": "06bdc965eb50c8af",
        "name": "manual - charger",
        "func": "if ( msg.payload == 2 ) // 2: manual control\n{\n    msg.payload = 0;    // 0: manual\n} else {                // 1 :charger control\n    msg.payload = 1;    // 1 : auto\n}\nreturn msg;",
        "outputs": 1,
        "timeout": 0,
        "noerr": 0,
        "initialize": "",
        "finalize": "",
        "libs": [],
        "x": 650,
        "y": 2820,
        "wires": [
            [
                "5fd958e4ae85c36c"
            ]
        ]
    }
]
20

Indeed, not available yet in v3.70~37, hopefully this will be integrated soon.

Screenshot_20250922_223312_VRM
Screenshot_20250922_223312_VRM1080×547 49.3 KB