question

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

Venus OS v2.85~5 available for testing

update April 21nd: v2.85 was officially released earlier this week.


Good afternoon,

Today we released v2.85~5 for testing. Compared to the previous beta version, v2.85~3, this new one makes for the WiFi SSID of units produced after feb 1st 2022 to no longer change when updating, better. And it updates the PHP version.


Plan for v2.85

Release next week.


Change log

This is the complete change log, compared to v2.84.

  • Fix an issue with VRM for some of the Cerbo GXes produced after February 1st 2022. Their data would not being processed at VRM, even though in the Settings -> VRM Portal menu all seemed OK. This issue is fixed by changing the VRM Portal ID to be derived from the WiFi MAC address, rather than the Ethernet MAC address, for all units produced after Feb 1st 2022. Effects:
    • Any unit already reporting OK to VRM will keep reporting OK after updating to v2.85.
    • All units, including the affected units, can be updated via the online download mechanism, as well as using the offline one, using USB stick or sdcard.
    • The label on Cerbos produced after Feb 1st 2022 will indicate the wrong VRM Portal ID. The VRM Portal as shown in the GUI is the right one. Adding a new Cerbo on the VRM Portal using the ID that's on the label will make VRM (soon, not yet!) guide the user to use the WiFi MAC address instead, which is on the label as well.
    • Note that downgrading, after first updating to v2.85 or later, causes a problem: the VRM Portal will reject all received data. Even if it worked before the update.
  • Improve support for the Lynx Smart BMS
    • Add alarm notifications for fuse blown events as well as a loss of connection to the Lynx Distributor
    • Remove obsolete BMS errors
    • Add status
  • Complete support for currently available uses of Multi RS.
    • Add full DVCC support
    • Fix overviews where necessary
    • Fix missing data points in transmission to VRM portal
    • (excludes ESS, three phase, parallel, and operation with a generator)
  • DVCC: reduce (possible) latency of data transmitted by the GX to VE.Can, by sending values immediately rather then on a 4 second interval. Parameters included:
    • Voltage sense, Temperature sense, Battery currents, State of charge.
  • Fix display of manually configured IP settings (as opposed to setting it to DHCP): in some situations, the user interface would show dashes for the default gateway, while there actually was one configured.
  • Fix productid transmission to VRM for a few data models, including DC Load, DC System and Multi RS.
  • Update PHP to v7.4.28. CVEs: CVE-2021-21703 CVE-2021-21706 CVE-2021-21707 CVE-2021-21708. Note that due to the way PHP is used (extremely minimal), the CVEs were not exploitable on a GX Device.


All the best, Matthijs

Venus OS
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.

3 Answers
nickdb avatar image
nickdb answered ·

Not sure if it was introduced by this version or not.

On ESS, having manually raised the minimum SOC by 20% (to prevent battery discharge and force charge from grid) both mppt's went to sleep and would not provide PV beyond 5W. The Venus needed to be rebooted, then both started producing PV again.


Also, having raised the min SOC, the system does not report ESS state 1. It simply says recharging.

The change was made via the VRM control option, not the GX.

edit: following the reboot, the mppt's slowly drift back down towards zero PV again.

Reducing the minimum SOC to just below the actual SOC and mppts function normally.

Seems it is not happy when ESS is recharging from Grid.

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 ·
Hi Nick, that won't have anything to do with v2.85. Strange, I'll ask a colleague to check whats going on on your system. Thank you for the report, Matthijs
0 Likes 0 ·
Show more comments
fish avatar image
fish answered ·

Not quite sure where to post but wanted to report a bug in V2.85 release version in that the ESS scheduled charging uses UTC and not local time. I had seen this had been picked up in V2.8 when changed to Python 3. I'd assumed it had been fixed in the later version but it would appear not.


So to confirm, I am seeing V2.85 using UTC time not Local as intended for ESS scheduling.

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.

info-6 avatar image
info-6 answered ·

I just updated to 2.85~5 and realized that the Ruuvi sensors disappeared. Rollback to ~3 brought them back, but in ~5 they're gone.

Edit:
With v 2.85 it's the same

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)