Good day! A fresh new thread for v3.90 beta. Note: The naming of the betas has changed from ~ to beta! 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. Modifications such as the popular GuiMods, SetupHelper, dbus-serialbattery and other 3rd party add-ons: do not report new topics in Venus beta. 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. See Settings → General → Modification checks in the New UI. Popular bug report / discussion threads: Change log v3.90-beta9 22/10/26 Security Update php to v8.2.35. Fixes unauthenticated remote code execution. Update Node.js to v24.22.1 Node.js — Wednesday, October 21, 2026 Security Releases. Drop the compromised eMudhra intermediate certificates. https://emudhra.we-have-a-problem.com v3.90-beta8 21/10/26 Dynamic ESS Fix the maximum discharge rate for not being reached completely, when discharging from battery with a limit lower than the inverters capability. developers: Introduce a separate process for Dynamic ESS. It can be disabled when not needed. v3.90-beta7 16/10/26 New UI Access & Security Don’t allow a user to become superuser directly. Connectivity Clear Ethernet details when the cable is unplugged. Order Wi-Fi connections by state and signal strength. Overview Add temperature to the alternator widget. Settings Show write permission error notification for list items. Shelly Add enable option to the integration settings. Add automatic device discovery to settings. Shelly Now turns the output off when the Opportunity Loads connection closes. Fix devices whose channels are sometimes disabled when they reconnect. Fix EM capability sometimes not being probed. Fix custom device name synchronization for PM-only devices (e.g. Plug PM Gen3). Lazy-load S2python to save RAM. Opportunity Loads Fix lower-priority loads not starting when the battery reaches 100% SoC and the BMS does not report a charge-current limit (CCL). If “Activate following loads when battery reaches” was set to 100%, Opportunity Loads could continue setting aside effectively unlimited power for battery charging even when the battery was full. At 100% SoC, it now uses the configured “At 100% SOC” reserve power, allowing lower-priority loads to use the remaining surplus. Prevent battery charging from a generator or another non-solar source from enabling loads at night. The solar keep-alive feature now applies only when solar power is available. Power from another charging source is no longer mistaken for surplus solar available to loads. Correct DC-PV surplus calculations when “System has DC Loads” is enabled. DC-system consumption is deducted from DC-PV power so energy already used by DC loads is not counted as surplus for Opportunity Loads. Previously, GX Opportunity Loads could not handle a system with loads on both AC-In and AC-Out while the inverter was in Inverter-Only mode (off-grid operation). It raised the “Incompatible System” warning and skipped its normal control-loop work. It now continues operating with loads on AC-Out. In Inverter-Only mode, it stops managing controllable AC-In loads and does not use AC-In consumption or grid-side PV production when calculating the power available to AC-Out loads. Fix battery charging power not being set aside while Battery Life Support is active. When Battery Life Support needs to give charging priority, Opportunity Loads should hold back power from lower-priority loads. A bug made the calculation fail and leave no power set aside for charging. Treat consumers that have no AC position configured as connected to AC-In. In Inverter-Only mode, a consumer without a position value is therefore handled conservatively: it is not controlled. Stability improvements Node-RED Orion XS emergency charging can now be controlled from the alternator and DC-DC nodes. You can start or stop an emergency charge cycle, and read how long it has left to run or how long until a new one can start. The alternator and DC-DC nodes now also recognize the Orion XS “Reverse charging” and “Reverse charging blocked” states. VRM-API Correct the node statuses for Base Load, Heating, EV Charging, and AC Load Consumption. Installation stats with Start and End both set to “now” return the current value instead of nothing. Dynamic ESS stats now show the number of planned intervals in the node status. VRM Fix a problem where a corrupt backlog stored on an SD card can cause the GX device to stop logging. A corrupted SQLite file can cause read operations to fail, while writes still succeed, causing the backlog to grow forever but never being logged to VRM. This is now detected and logged to VRM. The system switches back to internal storage. If a read fails on internal storage, it switches to ramdisk. v3.90-beta6 08/10/26 Cerbo GX MK3: No longer reboots while plenty of free memory remains, and about 19 MB more RAM is available (also in v3.81). Multi RS: Fix issue where changing the switch position/Mode of a Multi-RS on the unit, or with VictronConnect, does not reflect on the GX. RV-C: Improve CAN-bus robustness (backport candidate). Handle CAN-bus disconnects with socketcan (same as vecan-dbus). Handle bus-off recovery (same as vecan-dbus). VE.Bus out: Fix race condition when setting the mode from RV-C (backport candidate). The inverter and charger enable is split across two DGNs. But when both DGNs are sent back to back, the multi could sometimes end up in charger only or inverter only. System: Fix a bug where disabling DynamicEss while the battery was idle would not completely disable DynamicEss on a Multi-RS. It would continue to idle until the GX device was rebooted. Use the Pylontech charge voltage control algorithm (used for 15-cell batteries since Venus 3.60) also for 16-cell batteries to prevent possibly too high battery voltages. For safety, always cap a Pylontech batterh to 57.6V even if it asks for more (3.6V per cell). Fix bug where the charge current limit (CCL) of 15-cell batteries were not correctly applied below C/4 rates, since Venus v3.80. VRM: Fix a bug that would stop logging all energy from a device if it has jumped by more than 250kWh in the past. Reduce Node-RED memory usage: nodejs: npm builtin config with maxsockets=1 (one registry connection instead of 15), lowering npm’s peak memory during palette installs node-red-venus: start Node-RED with --max-semi-space-size=2; npm inherits it. Lowers the peaks, not steady-state usage: Node-RED startup -24 MB (MK3) / -11 MB (Cerbo GX) v3.90-beta5 - 01/10/26 Node-RED Virtual EV chargers can now be set to an AC output or AC input position. Existing nodes keep their current behaviour. Virtual devices on a disabled flow now keep their VRM instance through a deploy or restart. Correct the units for virtual temperature sensor pressure and for generator oil pressure and engine hours. v3.90-beta4 VE.Bus Fix VE.Bus AC/DC Text values. This was mainly visible in the Classic UI. Marine MFD App Bug fixes and stability improvements Node-RED Update to v5.0.7. Full release log available at Releases · node-red/node-red · GitHub. Signal K Update to v2.33.0. Full release log available at Releases · SignalK/signalk-server · GitHub v3.90-beta1 Bluetooth Restore preliminary support for the SuperPack NG. System Use/log AC input configuration from the system configuration instead of local settings This allows the AC input configuration of a Multi-RS to be used, ensuring PV-inverter energy is allocated correctly. Communicate the PV-inverter power (on AC-out) to the Multi-RS Summarise/publish the AC-input configuration so there is one place for both Multis/Quattros, but also Multi-RS. No longer force SVS for Pytes batteries. Pylontech: Extend the improved voltage control used for 15-cell batteries also to 8-cell (24V) batteries. Fix a race condition that can sometimes cause a battery to show up twice in Battery Measurements AC coupled solar Add support for Growatt and Solis inverters, and possibly more. Fix a bug with Fronius inverters where per-Tracker information was incorrect early morning and late evening. Node-RED add DESS grid/battery flow forecast attributes. SignalK has been updated to v2.30.0 (and yes there is a 2.33 release, but it causes trouble, so will be updated later) Developers: Modbus: New register for VE.Bus Weak AC Input setting (register 129) software updates rust: Upgrade to v1.98.1 nodejs: upgrade to v24.21.0 go: upgrade to v1.27.1

Thanks for adding the Ruuvi air quality score! [Screenshot_20261017_110555_VRM]

Venus v3.85 has been released. As you might have read in the news or from the VRM pop-up, PHP released fixes for a critical bug yesterday. It will have less impact for GX devices than for web servers, since most will not be accesible directly over the internet, but it is a good thing to have this patched as soon as possible. The intermediate certificates being compromised is also critical (although there is no official rating, since there is no CVE assigned because of its nature). It makes man in the middle attacks for https connections possible. The Node.js issues are rated as high (but like PHP an attacker must be able to reach the device in the first place). So this is a bit an unusual release, but solves these vulnerabilities. The public changelog still has to be written. So that will follow later (This is rather technical description obviously).

Venus v3.56 is now available for the Color Control, which contains the PHP fix and the removal of the compromised certificates. A Color Control can’t run Node.js / the Venus Large image , so it is not vulnerable for that.

Venus OS v3.90-beta9 available for public testing

Beta testing Venus OS beta testing

Topic		Replies	Views
Venus 3.70 released Q&A and troubleshooting venus_os	16	2346	20 March 2026
Venus OS v3.50 official release - New User Interface, Security and Generator Improvements Q&A and troubleshooting 350-new-ui	16	13021	27 January 2025
VRM release notes 25-09-2025 Q&A and troubleshooting vrm , dess	35	3408	19 October 2025
Venus OS 3.79 released for Multi RS 48/6000 Q&A and troubleshooting dess , multi_rs	6	544	6 September 2026
V3.64 Node-RED - Not connected to D-Bus error Node-RED diy , domestic , node-red , gx_device , cerbo_gx	47	1506	24 October 2025

Venus OS v3.90-beta9 available for public testing

Related topics