Cumulus MX Software Upgrade Available Check Feature

[galfert]

The Cumulus MX software upgrade check feature is new. Just wondering how it works. I see that a new version is out 3.9.4 build 3099 but my system still shows Upgrade Available status as green (active - no upgrades). So the question is how often does it check for updates? Just once daily? ...and at what time(s)?

CMX Upgrade Check.jpg

I didn't expect for it to be instantaneous. I know 3.9.4 build 3099 just landed. I'm just wondering how frequent the check is.

[mcrossley]

On start-up, and once a day at a random time for each run of MX.

[galfert]

Well here we are more than 24 hours since 3.9.4 build 3099 was released and my Cumulus MX dashboard notifications still does not show that an update is available (running 3.9.3 b3098). Now to be fair maybe my daily random check hasn't occurred yet. I'm just waiting in anticipation to see this feature work. ....any minute now right? ... I hope.

[Cortmalaw]

Mine seems more fundamentally 'not working properly' than that.

Until today, the alarm for Update available was enabled and correctly displaying as pale green. Today, the light has changed to 'off' (grey) even though the alarm is still enabled in Settings. And I've just restarted CumulusMX which should have ensured immediate detection that an upgrade was available?

Presently on build 3098

[galfert]

I remember when 3098 first was released that it was grey for the initial day (first version with this feature). Then it went green sometime the next day. So I don't think your install is not working. Since you've just restarted it will probably in the next 24 hours go from grey to red.

I did notice though that the feature does not work in all browsers. It seems to light up green on Chrome in Windows, Linux Mint, and Android Chrome. But on the Raspberry Pi Chromium browser the light does not work. Seems like a limitation of the Chromium browser on the Pi...so probably not a Cumulus MX problem.

[radilly]

I was looking forward to this too, because I run on a Pi under systemd (as a service), so I was watching ServiceConsoleLog.txt for a message about a new version. I noticed the indicator yesterday and just updated now. Do you see that file in MXdiags?

Upgrade_Available_Check_Feature_Sticky.jpg

I noticed however, that the indicator was still shown. I believe that happened with the last update as well, and after a time it cleared. So it feels a little sticky for some reason. ServiceConsoleLog.txt is not showing a newer version is available. That stickiness may go both ways...?

[Cortmalaw]

Update: the alarm is simultaneously showing as 'active' (green) but not 'triggered' (flashing red) in Edge and Firefox, but as 'inactive' (grey) in Chrome. Other alarms correctly show as 'active' (green) in Chrome.

Other alarms show as 'inactive', 'active' and 'triggered' when expected in all 3 of the above browsers.

[Mapantz]

As far as I am aware, green means the alarm is active, flashing red means the alarm is triggered. So a green 'update' means no update available.

[freddie]

As far as I am aware, green means the alarm is active, flashing red means the alarm is triggered. So a green 'update' means no update available.

This is how I understand it too. It is working for me using the Chrome browser (on Windows 10 and Android 11). I checked the alarm before I updated to the current release, and sure enough it was flashing red.

[Cortmalaw]

Yes, those are the colours I expect too. And Mark said:

On start-up, and once a day at a random time for each run of MX.

So, as I have recently rebooted, it should have detected update available - but hasn't. Here is an example with Low Temp showing as triggered:

Update.jpg

[radilly]

Here's what I see across 3 browsers - AFAIK the latest versions.

Upgrade_Indicator.jpg

I've never seen anything but green and gray.

[galfert]

My PI Chromium browser just showed me a pop-up that localhost wanted to show notifications....I had never seen that before. I said yes and now for the first time I see the green for Upgrade available. Although I'm actually by now expecting a red light as I'm still on 3098.

[Cortmalaw]

It seems to have disappeared, but I posted an update yesterday where I identified a likely cause/solution.

The clue was: soon after reboot, I saw the Upgrade indicator flash red, but only once.
In Settings / Alarms, the default for this alarm is set to latching for 0 hours (whilst all the others are at 24 or 12 hours). I had assumed this meant 'latch forever, until upgrade performed', but it seems to effectively be the same as 'do not latch'

After changing the latching value to a high number, it is now detecting and displaying as expected.

EXCEPT: after this alarm has been shown and CumulusMX is restarted, the latching duration becomes reset to zero, and the alarm is not shown again even if the upgrade has not been performed
@mcrossley this does not seem to be the most desirable behaviour. Not urgent, but maybe should be on your 'to be fixed' list?

[mcrossley]

I'd make the following suggestions...

1. Make sure you have copied over all the latest /interface files including all sub-folders
2. Flush your browser cache - Ctrl-F5, clear cache from settings, or launch the dev tools and refresh the page

The latch time of zero means - do not latch. The alarm should will only be active until the condition clears - which may be very quick for some alarms. The Upgrade alarm should stay active until you upgrade. But I'll double check the logic on alarm clearing and latch times....

[mcrossley]

Correction...

"Latches" being unticked means do not latch. If that is not enabled (as it is not by default for the Upgrade alarm) the latch behaviour is not to latch and auto-clear.

The Upgrade alarm does not need to latch as the alarm condition will not clear until you upgrade MX and restart it anyway.

There is a problem with the latch clearing code, by it does not affect the upgrade alarm. It means alarms will be cleared after the latch time, even if latching is not enabled. I'll fix this for the next release.