Bug: VenusOS updated itself although forbidden?

DIY
,
1

I have a system, MP2, VenusOS on Raspberry, 2 Batteries, DBus-SerialBattery, Setuphelper

In Setuphelper i use BatteryAggregaor and the RPIDisplay-Plugin

Last week i wondered about high Consumption from the net - found out VenusOS is no longer seeing BatterAgregator

After some investigations - Setuphelper was compeletely gone

After reinstall - everything back to normal

Only almost - next night battery stopped discharging at 45%

In the end i found oit that VenusOS was updated to V3.64, deleted setiphelper and changed minSOC

I definetly had the option “only check” in the firmware section activated , myself was far away from a PC the moment it happened

How could i avoid this in the future?

2

It is impossible for a system to self update unless approved remotely via VRM or set to auto-update.

Or, possibly, changing between large/small images.

3

i also thought like that, but saw it happen

4

You would be the first.

Goto VRM look at event logs. Post the screenshot here.

5

There is something strange, at least…
For example, I have the autoupdates disabled completely… Not check, not anything else, DISABLED.
See below that, after boot, the script exits.

BUT !!!

From time to time, it seems that it still checks for updates, even if disabled, on its own, without user intervention.
And it fills the menu with update available, etc…
See the log below.

So, it seems that victron still has the ability to force, at least, the check for updates, even when disabled…

2
2490Ă—284 32.3 KB

1
11272Ă—389 155 KB

6

Hi Alex,

This is probably caused by pressing by scanning for firmware updates via the VRM website. This causes the update scan to trigger on the GX device and the result is then automatically shown in the GUI. This however does not explain a possible automatic update as it triggers only a check and not an update.

With kind regards,

Thiemo van Engelen

1 Like
7

the problem happened August the 8th 7:05pm

Absolutely nothing in the event log:

victron1
victron11838Ă—1166 124 KB

8

Hi Thiemo @thiemovanengelen
You are right, I remember that I’ve checked through the VRM for firmware updates at some point.
Forgot about that, sorry… :blush:
Probably because the check for updates from VRM does not get logged on VRM event logs, on August 6, 11 and 18 as shown on the previous messaga… See below.
Maybe this should be logged…
Thank you,
Alex

1
1962Ă—531 47.8 KB

9

Hi Alex,

No problem… It is not exactly logical that a firmware check via the VRM website results in the GUI showing whether here is an update or not.

And I will forward the idea internally whether we want the firmware check to be logged… To me it does not sound like a bad idea.

Regards,

Thiemo van Engelen

10

Today i had the Problem again, Low Bat warning, System no longer working

I found that i have now Venus V3.66 although automatic Update was not allowed

I had to reactivate dbus-seriallbattery, setuphelper and dbus-aggregatebatteries

–> Victron-Team: there is somethig really strange going on

Why does the system update by itself although forbidden?