question

mvader (Victron Energy) avatar image
mvader (Victron Energy) asked

Venus OS v3.31~4 available for testing

UPDATE 2024-04-24 - v3.31 has now been released - https://professional.victronenergy.com/news/detail/242/

Good day!

Per just now, we released beta version v3.31~3 to be tested.

This version is mostly fixes and stability improvements, and assuming that its a clean result then we're keen to release this already early next week. Directly after that we'll continue the testing of the v3.40-beta series that include gui-v2.

Feedback appreciated! Please keep it clean: no feature requests, no questions about why gui-v2 is not available. All I'm interested in now is that all available functionality is stable and working as it should; as well as that the mentioned fixes are effective.


Instructions: 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: How to post an issue?

By posting an answer below. Do please keep all findings organised: one answer issue per issue. So first check the existing threads if your issue has already been seen. And if it does, add a comment saying "me too". And preferably some more details. And in case its not listed yet, add a new Answer.

Note that Answers and Comments are two different things on this portal.

Lastly, before posting issues, 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 include information about the results/differences in behaviour in your report.


Instructions: Node-RED, Kevin’s GuiMods or other add-ons?

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

GuiMods and other 3rd party add-ons: don’t report your gui issues here. Do it elsewhere instead.

Changes made by us can cause a compatibility issue with the GuiMods; and these betas report pages are for official firmware only.


Change log

v3.31~4

  • Fix EVCS firmware updates over VRM failing on fast network connections.


v3.30 -> v3.31~3

  • fix gui getting stuck sometimes, showing a small green square locally on the GX Touch and Ekrano GX as well as causing Remote Console to not work. This issue was introduced in v3.30.
  • gui: fix alarm icon showing while there is no alarm, issue was introduced in v3.30
  • gui: remove DESS Minimum SOC menu entry, since that is now configurable on the VRM portal rather than in the GX menu structure.
  • Dynamic ESS: fix bug where PV from grid-inverter was fed back into the grid rather than used to charge the battery, in certain conditions.
  • VM-3P75CT Energy Meter: fix power readings not properly available when using multiple of these energy meters on the same VE.Can network.
  • FlashMQ, an internal tool : update from v1.9.1 to v1.11.0 as well as allow empty usernames. Allowing empty user names fixes certain MQTT clients not being able to login as well as other tools that used to work up to Venus OS v3.20 but didn't since we switched to FlashMQ. For the complete FlashMQ change log, see https://github.com/halfgaar/FlashMQ/tags. And for more details on this issue see https://github.com/victronenergy/venus/issues/1257.
  • Add mosquitto_pub and mosquitto_sub clients to the standard toolset on Venus OS.
  • Venus OS Large, signalk-server:




Venus OS
3 comments
2 |3000
Toggle Comment visibility. Current Visibility: Viewable by all users

Up to 8 attachments (including images) can be used with a maximum of 190.8 MiB each and 286.6 MiB total.

Tony avatar image Tony commented ·
Installed v3.31~3 on my Cerbo GX yesterday and everything seems to be working fine. The touch 50 boots up much quicker, than before when the Cerbo was running v3.30.
0 Likes 0 ·
mvader (Victron Energy) avatar image mvader (Victron Energy) ♦♦ commented ·

Updated to Venus OS v3.31~4 - fixes firmware updates on EVCS via VRM not working on fast network connections.

The plan is still to release on Monday or Tuesday next week.

Have a good weekend!

0 Likes 0 ·
johanbakker avatar image johanbakker commented ·
Installed production version of v3.31. All works fine AND PV is no longer fed into the Grid at low tariffs, while the battery was far from full. Thanks, excellent improvement!
0 Likes 0 ·
13 Answers
gerd-weiss avatar image
gerd-weiss answered ·

Hello,

I observe at least since the last release, that DESS does not take care for the switch "allow feed-in" (sorry if this is not the correct term, my version is localized in German). I have to set a reasonable grid-feed-in limit in order to allow feeding into the grid instead, the indication in the menu always says "Grid-feed-in limit active: yes". Is that a know issue?


Regards,

Gerhard

2 |3000
Toggle Comment visibility. Current Visibility: Viewable by all users

Up to 8 attachments (including images) can be used with a maximum of 190.8 MiB each and 286.6 MiB total.

blindbadger avatar image
blindbadger answered ·

Update went smooth for me from ~2 to ~3. Everything else appears to be working so far. Running the "large" image with Node-Red enabled.


EDIT: Removed talk about gui-v2

2 comments
2 |3000
Toggle Comment visibility. Current Visibility: Viewable by all users

Up to 8 attachments (including images) can be used with a maximum of 190.8 MiB each and 286.6 MiB total.

Evgeniy Labunskiy avatar image Evgeniy Labunskiy commented ·
Please read announcement, gui beta is not a part of this update
2 Likes 2 ·
blindbadger avatar image blindbadger Evgeniy Labunskiy commented ·
Ah I missed that line. Thanks!
1 Like 1 ·
kerbal avatar image
kerbal answered ·

This has nothing todo with this version (i also had this issue in 3.30 and 3.40), but i hope it could be fixed in that version (or maybe in a future release).

I have an ESS system with one Multiplus II 3000, 2 US3000C and the energy meter VM-3P75CT.
The grid setpoint is set to -10W.

Why does it take such a long time to get back to the grid setpoint. Is that the normal behavior for an ESS? Should i switch to a EM540? Do i have missed some configuration?
The VM-3P75CT is connected via VE.Can.

Pls have a look at the video that i have taken:

https://stroblinger.com/owncloud/index.php/s/WnOLJYO3l7F628V

2 |3000
Toggle Comment visibility. Current Visibility: Viewable by all users

Up to 8 attachments (including images) can be used with a maximum of 190.8 MiB each and 286.6 MiB total.

Jaco Reinecke avatar image
Jaco Reinecke answered ·

Getting this error after the update, access new interface via VRM Portal.
1713431380232.png

Access to new interface using IP address gives 404 Not Found.


1713431380232.png (11.5 KiB)
3 comments
2 |3000
Toggle Comment visibility. Current Visibility: Viewable by all users

Up to 8 attachments (including images) can be used with a maximum of 190.8 MiB each and 286.6 MiB total.

Juha Tuomala avatar image Juha Tuomala commented ·
New interface is part of beta testing releases, v3.4x series. V3.3x series are stable and doesn't have it.


Now why stable is updater over v3.4x beta is something I don't know as its minor release number is smaller than beta's.

1 Like 1 ·
Matthias Lange - DE avatar image Matthias Lange - DE ♦ commented ·
Please read the first post and disable automatic updates!

This is a quick beta for a 3.3X Version.

There can be only one beta so 3.40 is currently down for 3.31.

0 Likes 0 ·
Show more comments
Enzo avatar image
Enzo answered ·

Hello, no access to the web interface possible after update to v3.31-3

How can i return to v3.31 without the web interface?

Thank you

1 comment
2 |3000
Toggle Comment visibility. Current Visibility: Viewable by all users

Up to 8 attachments (including images) can be used with a maximum of 190.8 MiB each and 286.6 MiB total.

blindbadger avatar image blindbadger commented ·
Can you access the remote console from VRM?
0 Likes 0 ·
andrii-podanenko avatar image
andrii-podanenko answered ·

Installed 3.30~3 after 3.40~beta on my multiplus II setup with DESS, no PV.

nodered works

DESS works

No issues whatsoever.

1 comment
2 |3000
Toggle Comment visibility. Current Visibility: Viewable by all users

Up to 8 attachments (including images) can be used with a maximum of 190.8 MiB each and 286.6 MiB total.

andrii-podanenko avatar image andrii-podanenko commented ·
Upgraded MultiPlus-II to 510fw

Lost ESS assistant (VRM upgrade)

Restored it from backup

Confirming DESS is working @mvader (Victron Energy)

0 Likes 0 ·
ektus avatar image
ektus answered ·

Went ahead and installed this version, coming from 3.22. Running okay so far, will have to wait and see if it is more stable. current result of top:

Mem: 532988K used, 497096K free, 3180K shrd, 23016K buff, 140420K cached
CPU:  53% usr   8% sys   0% nic  35% idle   0% io   1% irq   0% sirq
Load average: 1.46 2.01 2.18 2/307 8244
  PID  PPID USER     STAT   VSZ %VSZ %CPU COMMAND
 1106  1089 root     S     145m  14%  12% /opt/victronenergy/gui/gui -nomouse -display Multi: LinuxFb: VNC:size=800x480:depth=32:passwordFile=/data/conf/vncpasswor
 2053  1116 nodered  S     220m  22%  10% node-red
 1157  1141 root     S    22048   2%   5% {dbus_systemcalc} /usr/bin/python3 -u /opt/victronenergy/dbus-systemcalc-py/dbus_systemcalc.py
 1941  1938 root     S    31972   3%   5% python /data/dbus-shelly-3em-smartmeter/dbus-shelly-3em-smartmeter.py
 1940  1939 root     S    32040   3%   4% python /data/dbus-shelly-3em-inverter/dbus-shelly-3em-inverter.py
  828   826 messageb S     4412   0%   4% dbus-daemon --system --nofork
 1104  1079 root     S    39532   4%   3% {vrmlogger.py} /usr/bin/python3 -u /opt/victronenergy/vrmlogger/vrmlogger.py
 1163  1149 root     S    21344   2%   2% {dbus_generator.} /usr/bin/python3 -u /opt/victronenergy/dbus-generator-starter/dbus_generator.py
 1132  1122 root     S    26236   3%   2% {localsettings.p} /usr/bin/python3 -u /opt/victronenergy/localsettings/localsettings.py --path=/data/conf
 1129  1081 root     S    19808   2%   1% /opt/victronenergy/venus-platform/venus-platform
 1135  1126 root     S     8636   1%   1% /opt/victronenergy/hub4control/hub4control
 1180  1165 root     S    11300   1%   1% /opt/victronenergy/dbus-fronius/dbus-fronius
 2129  2121 root     S    56356   5%   1% /usr/bin/flashmq
 2128  2123 root     S    21148   2%   1% {vesmart_server.} /usr/bin/python3 -u /opt/victronenergy/vesmart-server/vesmart_server.py -i hci0
 1788  1738 root     S     3668   0%   1% /opt/victronenergy/mk2-dbus/mk2-dbus --log-before 25 --log-after 25 --banner -w -s /dev/ttyS4 -i -t mk3 --settings /data/
 2782  2780 root     S     3376   0%   1% /opt/victronenergy/vedirect-interface/vedirect-dbus -v --log-before 25 --log-after 25 -t 3 --banner -s /dev/ttyUSB1
 1762  1760 root     S     3376   0%   0% /opt/victronenergy/vedirect-interface/vedirect-dbus -v --log-before 25 --log-after 25 -t 0 --banner -s /dev/ttyS7
 1740  1737 root     S     3376   0%   0% /opt/victronenergy/vedirect-interface/vedirect-dbus -v --log-before 25 --log-after 25 -t 0 --banner -s /dev/ttyS6
 1767  1763 root     S     3376   0%   0% /opt/victronenergy/vedirect-interface/vedirect-dbus -v --log-before 25 --log-after 25 -t 0 --banner -s /dev/ttyS5
 1776  1773 root     S     3376   0%   0% /opt/victronenergy/vedirect-interface/vedirect-dbus -v --log-before 25 --log-after 25 -t 3 --banner -s /dev/ttyUSB0
 2436  2432 root     S    64136   6%   0% python /data/SetupHelper/PackageManager.py
 1155  1137 root     S    19548   2%   0% {dbus_vebus_to_p} /usr/bin/python3 -u /opt/victronenergy/dbus-vebus-to-pvinverter/dbus_vebus_to_pvinverter.py
 1127  1092 simple-u S    12592   1%   0% /bin/simple-upnpd --xml /var/run/simple-upnpd.xml -d
 1932  1923 root     S     3648   0%   0% /opt/victronenergy/vecan-dbus/vecan-dbus -c socketcan:can0 --banner --log-before 25 --log-after 25 -vv
 3883  3855 root     R     2780   0%   0% top
 1175  1147 root     S    45568   4%   0% {dbus-modbus-cli} /usr/bin/python3 -u /opt/victronenergy/dbus-modbus-client/dbus-modbus-client.py
 1179  1171 root     S     3484   0%   0% /opt/victronenergy/dbus-adc/dbus-adc --banner
 1985  1980 root     S     3176   0%   0% /opt/victronenergy/can-bus-bms/can-bus-bms --log-before 25 --log-after 25 -vv -c socketcan:can1 --banner
    7     2 root     IW       0   0%   0% [kworker/u4:0-ev]
 1131  1120 root     S    23264   2%   0% {netmon} /usr/bin/python3 -u /opt/victronenergy/netmon/netmon
 1174  1167 root     S    21936   2%   0% {dbus_digitalinp} /usr/bin/python3 -u /opt/victronenergy/dbus-digitalinputs/dbus_digitalinputs.py --poll=poll /dev/gpio/d
 3836  1933 root     S     5524   1%   0% sshd: root@pts/0
 1128  1098 root     S     3044   0%   0% {serial-starter.} /bin/bash /opt/victronenergy/serial-starter/serial-starter.sh
  813     2 root     SW       0   0%   0% [RTW_CMD_THREAD]
   51     2 root     IW       0   0%   0% [kworker/0:4-eve]
   11     2 root     IW       0   0%   0% [rcu_sched]
   72     2 root     IW       0   0%   0% [kworker/1:4-eve]
 2125  2119 root     S    40592   4%   0% {mqtt-rpc.py} /usr/bin/python3 -u /opt/victronenergy/mqtt-rpc/mqtt-rpc.py
 1112  1085 root     S    34836   3%   0% {venus-button-ha} /usr/bin/python3 -u /opt/victronenergy/venus-button-handler/venus-button-handler -D
 1158  1143 root     S    27824   3%   0% {dbus_shelly.py} /usr/bin/python3 /opt/victronenergy/dbus-shelly/dbus_shelly.py
  905     1 root     S    22740   2%   0% php-fpm: master process (/etc/php-fpm.conf)
  906   905 www-data S    22740   2%   0% php-fpm: pool www
  907   905 www-data S    22740   2%   0% php-fpm: pool www
3 comments
2 |3000
Toggle Comment visibility. Current Visibility: Viewable by all users

Up to 8 attachments (including images) can be used with a maximum of 190.8 MiB each and 286.6 MiB total.

ektus avatar image ektus commented ·

The watchdog has triggered several times this afternoon. System load looks rather high, including some processes that are not needed yet still are running:

1157  1143 root     S    21156   2%   3% {dbus_generator.} /usr/bin/python3 -u /opt/victronenergy/dbus-generator-starter/dbus_generator.py

I don't have a generator configured in the system. The Multiplus 2 is lacking a generator input anyways and with ESS running will disconnect the batteries if the generator kicks in. Or does "generator" mean something else here?

1166  1145 root     S    11272   1%   2% /opt/victronenergy/dbus-fronius/dbus-fronius

This system is Victron only with some Pylontech batteries. No Fronius anywhere.

Is it possible to change /etc/watchdog.conf to try raising the trigger level? CPU load was always fine, just the number of processes waiting was on the high side.

0 Likes 0 ·
Al avatar image Al ektus commented ·

@ektus I think both those processes run for every system, I see them on mine.

Your top looks better than mine, maybe install then look at htop to see what causes spikes and the overload, as it may be one of your mods:

wget -O /usr/bin/htop https://raw.githubusercontent.com/mr-manuel/venus-os_helpful-scripts/master/htop/armv7/htop
chmod +x /usr/bin/htop

As you are also using Mods, (SetupHelper/PackageManager) are you running GuiMods? This isn't the best place to mention shutdowns with mods on stock Venus, or NodeRed.

But, If you are on a Cerbo, I have also found the Cerbo 2 core CPU cannot cope with a few mods, It will only run stock. I run GuiMods, BatteryAggregator, dbus-serialbattery x 3, and have quite a few other standard devices, but it's also just too much for the Cerbo, so I'm looking at getting a rpi4.



0 Likes 0 ·
ektus avatar image ektus commented ·

I'm on a Cerbo 1, and I do run a mod to interface with 2x Shelly 3EM power meters and also Venus OS large with node-red as described in https://community.victronenergy.com/questions/276890/cerbo-gx-random-reboots.html

I've got htop installed now, but don't believe it shows better information than the regular top.

The system is running okay for hours on end, but reboots several times a day. I've not been able yet to find a real reason, as CPU load is not the limiting factor. It's always been watchdog issuing a reboot because of 5 minute load exceeding 6.0.

Todays reboots at least didn't end with the GUI not starting properly, so that's a win, but my overload problem persists. I'm trying to circumvent this by increasing the threshold, but don't know if that will work. Do I have to reboot in order for the change to /etc/watchdog.conf to take effect, will the change survive a reboot and is it possible to manually restart the watchdog without trigfgering a reboot?

I've yet to add code to my node-red to store and retrieve the current settings so that they survive a reboot. But I'm afraid this is outside the scope of this thread.

0 Likes 0 ·
synker avatar image
synker answered ·

We seem to be unable to turn on Cerbo's relay 1 from the Cerbo interface if it's configured as a generator switch.

3 comments
2 |3000
Toggle Comment visibility. Current Visibility: Viewable by all users

Up to 8 attachments (including images) can be used with a maximum of 190.8 MiB each and 286.6 MiB total.

mvader (Victron Energy) avatar image mvader (Victron Energy) ♦♦ commented ·
Hey @Synker have you tried to use the Manual starts/stop feature that is available when having that relay configured for generator start/stop? That should work.
0 Likes 0 ·
mvader (Victron Energy) avatar image mvader (Victron Energy) ♦♦ mvader (Victron Energy) ♦♦ commented ·
ps. we changed that relay menu in the previous version, v3.30. The option to toggle the relay in the Settings -> Relay menu is now only available when its configured as a manual switch.


The problem was that it otherwise, when configured for alarm or generator start/stop for example, conflicts with those processes that are driving it.

0 Likes 0 ·
synker avatar image synker mvader (Victron Energy) ♦♦ commented ·
with 3.31.4 everythings works fine again
0 Likes 0 ·
ektus avatar image
ektus answered ·

Once again reboot due to alleged overload. There was also a brief message in VRM stating "real time updates disabled due to Cerbo overload" (not exactly in this words)

/data/log/messages.0 shows

Apr 19 09:38:17 einstein daemon.info connmand[915]: ntp: time slew +0.042066 s
Apr 19 10:46:33 einstein daemon.info connmand[915]: ntp: time slew +0.040898 s
Apr 19 11:18:28 einstein daemon.err watchdog[689]: loadavg 10 7 5 is higher than the given threshold 0 6 6!
Apr 19 11:18:29 einstein daemon.err watchdog[689]: repair binary /usr/sbin/store_watchdog_error.sh returned 253 = 'load average too high'
Apr 19 11:18:29 einstein daemon.alert watchdog[689]: shutting down the system because of error 253 = 'load average too high'
Apr 19 11:18:29 einstein daemon.err watchdog[689]: /usr/sbin/sendmail does not exist or is not executable (errno = 2)
Apr 19 11:18:39 einstein syslog.info syslogd exiting
Apr 19 11:20:55 einstein syslog.info syslogd started: BusyBox v1.31.1
Apr 19 11:20:55 einstein user.notice kernel: klogd started: BusyBox v1.31.1 (2024-04-12 20:52:11 UTC)
Apr 19 11:20:55 einstein user.info kernel: [    0.000000] Booting Linux on physical CPU 0x0

Last display of top at that point was:

Mem: 602200K used, 427884K free, 3188K shrd, 74568K buff, 140788K cached
CPU:  62% usr   7% sys   0% nic  27% idle   0% io   1% irq   0% sirq
Load average: 10.39 7.04 5.10 4/308 15305
  PID  PPID USER     STAT   VSZ %VSZ %CPU COMMAND
 1106  1089 root     R     145m  14%  14% /opt/victronenergy/gui/gui -nomouse -display Multi: LinuxFb: VNC:size=800x480:depth=32:passwordFile=/data/conf/vncpasswor
 2053  1116 nodered  R     232m  23%  10% node-red
 1157  1141 root     R    22048   2%   6% {dbus_systemcalc} /usr/bin/python3 -u /opt/victronenergy/dbus-systemcalc-py/dbus_systemcalc.py
  828   826 messageb S     4476   0%   5% dbus-daemon --system --nofork
 1940  1939 root     R    32296   3%   5% python /data/dbus-shelly-3em-inverter/dbus-shelly-3em-inverter.py
 1941  1938 root     S    32228   3%   5% python /data/dbus-shelly-3em-smartmeter/dbus-shelly-3em-smartmeter.py
 1104  1079 root     S    39532   4%   5% {vrmlogger.py} /usr/bin/python3 -u /opt/victronenergy/vrmlogger/vrmlogger.py
 1163  1149 root     S    21344   2%   3% {dbus_generator.} /usr/bin/python3 -u /opt/victronenergy/dbus-generator-starter/dbus_generator.py
 1129  1081 root     S    19808   2%   2% /opt/victronenergy/venus-platform/venus-platform
 2128  2123 root     S    21404   2%   2% {vesmart_server.} /usr/bin/python3 -u /opt/victronenergy/vesmart-server/vesmart_server.py -i hci0
 1135  1126 root     S     8764   1%   2% /opt/victronenergy/hub4control/hub4control
 1180  1165 root     S    11300   1%   2% /opt/victronenergy/dbus-fronius/dbus-fronius
 2129  2121 root     S    56872   6%   2% /usr/bin/flashmq
 1132  1122 root     R    26236   3%   2% {localsettings.p} /usr/bin/python3 -u /opt/victronenergy/localsettings/localsettings.py --path=/data/conf
 1788  1738 root     S     3668   0%   1% /opt/victronenergy/mk2-dbus/mk2-dbus --log-before 25 --log-after 25 --banner -w -s /dev/ttyS4 -i -t mk3 --settings /data/
 1740  1737 root     S     3424   0%   0% /opt/victronenergy/vedirect-interface/vedirect-dbus -v --log-before 25 --log-after 25 -t 0 --banner -s /dev/ttyS6
 1767  1763 root     S     3424   0%   0% /opt/victronenergy/vedirect-interface/vedirect-dbus -v --log-before 25 --log-after 25 -t 0 --banner -s /dev/ttyS5
 2782  2780 root     S     3424   0%   0% /opt/victronenergy/vedirect-interface/vedirect-dbus -v --log-before 25 --log-after 25 -t 3 --banner -s /dev/ttyUSB1
 1776  1773 root     S     3420   0%   0% /opt/victronenergy/vedirect-interface/vedirect-dbus -v --log-before 25 --log-after 25 -t 3 --banner -s /dev/ttyUSB0
 1762  1760 root     S     3376   0%   0% /opt/victronenergy/vedirect-interface/vedirect-dbus -v --log-before 25 --log-after 25 -t 0 --banner -s /dev/ttyS7
 1932  1923 root     S     3648   0%   0% /opt/victronenergy/vecan-dbus/vecan-dbus -c socketcan:can0 --banner --log-before 25 --log-after 25 -vv
 2436  2432 root     S    64136   6%   0% python /data/SetupHelper/PackageManager.py
 1155  1137 root     S    19548   2%   0% {dbus_vebus_to_p} /usr/bin/python3 -u /opt/victronenergy/dbus-vebus-to-pvinverter/dbus_vebus_to_pvinverter.py
 1179  1171 root     S     3484   0%   0% /opt/victronenergy/dbus-adc/dbus-adc --banner
 1175  1147 root     S    46592   5%   0% {dbus-modbus-cli} /usr/bin/python3 -u /opt/victronenergy/dbus-modbus-client/dbus-modbus-client.py
 3883  3855 root     R     2780   0%   0% top
23520     2 root     IW       0   0%   0% [kworker/u4:1-ev]
 2125  2119 root     S    40592   4%   0% {mqtt-rpc.py} /usr/bin/python3 -u /opt/victronenergy/mqtt-rpc/mqtt-rpc.py
 1131  1120 root     S    23264   2%   0% {netmon} /usr/bin/python3 -u /opt/victronenergy/netmon/netmon
  962     1 root     S     9072   1%   0% /usr/sbin/wpa_supplicant -u -O /var/run/wpa_supplicant -s
  915   912 root     S     4928   0%   0% connmand --nodnsproxy --nodaemon
 1985  1980 root     S     3176   0%   0% /opt/victronenergy/can-bus-bms/can-bus-bms --log-before 25 --log-after 25 -vv -c socketcan:can1 --banner
 1128  1098 root     S     3044   0%   0% {serial-starter.} /bin/bash /opt/victronenergy/serial-starter/serial-starter.sh
 2054  1117 root     S     1752   0%   0% multilog t s25000 n4 /var/log/node-red-venus
  813     2 root     SW       0   0%   0% [RTW_CMD_THREAD]
12017     2 root     IW       0   0%   0% [kworker/1:1-eve]
 1112  1085 root     S    34836   3%   0% {venus-button-ha} /usr/bin/python3 -u /opt/victronenergy/venus-button-handler/venus-button-handler -D
 1158  1143 root     S    27824   3%   0% {dbus_shelly.py} /usr/bin/python3 /opt/victronenergy/dbus-shelly/dbus_shelly.py
  905     1 root     S    22740   2%   0% php-fpm: master process (/etc/php-fpm.conf)
  906   905 www-data S    22740   2%   0% php-fpm: pool www
  907   905 www-data S    22740   2%   0% php-fpm: pool www
 1174  1167 root     S    21936   2%   0% {dbus_digitalinp} /usr/bin/python3 -u /opt/victronenergy/dbus-digitalinputs/dbus_digitalinputs.py --poll=poll /dev/gpio/d
 1127  1092 simple-u S    12720   1%   0% /bin/simple-upnpd --xml /var/run/simple-upnpd.xml -d
  118     1 root     S    11672   1%   0% /sbin/udevd -d
Connection to 192.168.0.80 closed by remote host.ctronenergy/venus-access/venus-access
Connection to 192.168.0.80 closed.
1 comment
2 |3000
Toggle Comment visibility. Current Visibility: Viewable by all users

Up to 8 attachments (including images) can be used with a maximum of 190.8 MiB each and 286.6 MiB total.

mvader (Victron Energy) avatar image mvader (Victron Energy) ♦♦ commented ·

Hey @ektus , can you please stop posting these messages here?


You are running modifications, which is the likely cause for CPU overload.


And there is a busy thread already elsewhere; please keep it there - thanks!


https://community.victronenergy.com/questions/276890/cerbo-gx-random-reboots.html

0 Likes 0 ·
ak68 avatar image
ak68 answered ·

I thought, login to Cerbo GX without username/ password should be possible now ?!

It doest´n work in my installation (just with MQTT-Explorer)

Changing of flashmq.conf + "allow_anonymous true" doesn´t have an effect

Do have to add anything else ?

1 comment
2 |3000
Toggle Comment visibility. Current Visibility: Viewable by all users

Up to 8 attachments (including images) can be used with a maximum of 190.8 MiB each and 286.6 MiB total.

mvader (Victron Energy) avatar image mvader (Victron Energy) ♦♦ commented ·

Hi, when running Venus OS v3.31~4, or later, you don't have to change any flashmq.conf file. So I think there is some confusion here.


I tested it myself just now, and logging with an empty username works ok now. Logging in without username/password was never an issue.


Also, using MQTT Explorer was never an issue - I thought it was but that was a mistake.


For further details, see here: https://github.com/victronenergy/venus/issues/1257

0 Likes 0 ·
heikki avatar image
heikki answered ·

Hi, It seems that Pylontech Force L1 does not work with Venus OS v3.31~4 version. It crash connections to GX even without loads. Going back version Venus OS v3.40~2 works well.

2 comments
2 |3000
Toggle Comment visibility. Current Visibility: Viewable by all users

Up to 8 attachments (including images) can be used with a maximum of 190.8 MiB each and 286.6 MiB total.

mvader (Victron Energy) avatar image mvader (Victron Energy) ♦♦ commented ·
Hey @Heikki , did it work well on Venus OS v3.30?
0 Likes 0 ·
heikki avatar image heikki mvader (Victron Energy) ♦♦ commented ·

Hi, I cant remember if it works with v3.30. Force L1 does not like fast growing current (eg. 10 kw load like sauna stove). I have made questions to that problem from Pylontech. They told that problem is with Victron software. We have Easysolar II 48V 5000VA 70-50 MPPT 250/100 GX and two MultiPlus II 48/5000/70-50 and Pylontech Force L1 17,6 kw system.

0 Likes 0 ·
pwfarnell avatar image
pwfarnell answered ·

Running V3.31~3 for a few days now. Boat install, Cerbo, Multiplus 12/3000/120, MPPT 150/60, BMV702, Tank 140 with 3 tanks, 2x Mopeka LPG, 4 x temp sensors, 1 x Ruuvi, 2 float switches on digital inputs as bilge alarms.

2 days running I have had spurious bilge alarms on the digital inputs at the same time. The reason I know that they are spurious is that the digital input count is still at 0 on the first input and at 1 on the second input which is the test I gave the system in 2021. If the wiring were to blame then the Cerbo would count that. Also, the 2 switches do not have any common wiring. As the digital input counter does not register then event I assume it is something internal in the logic and the only way to reset is to reboot the cerbo. I can not find anything common that occurs when these spurious alarms occur. I only started getting them with V2.80 and others have also reported odd behaviour. I noted it some time ago but as it typically happens infrequently I have not followed further. However, the frequency has increased since V3.31~3.

https://community.victronenergy.com/questions/132672/spurious-digital-input-alarms-bilge-level-switches.html

https://community.victronenergy.com/questions/119339/digital-inputs-stay-stuck-on-280.html

1 comment
2 |3000
Toggle Comment visibility. Current Visibility: Viewable by all users

Up to 8 attachments (including images) can be used with a maximum of 190.8 MiB each and 286.6 MiB total.

mvader (Victron Energy) avatar image mvader (Victron Energy) ♦♦ commented ·
Hi @pwfarnell thank you for the report, we’re looking into it
0 Likes 0 ·
johanbakker avatar image
johanbakker answered ·

Been running v3.31 for almost a week now and it is behaving very well! Good strategy, sensible distribution between grid and batteries at the right times and the right tariffs. Excellent, thanks for all the good work!

2 |3000
Toggle Comment visibility. Current Visibility: Viewable by all users

Up to 8 attachments (including images) can be used with a maximum of 190.8 MiB each and 286.6 MiB total.

Related Resources

Victron Venus OS Open Source intro page

Venus OS GitHub (please do not post to this)