Cumulus Support

I did some searching a week or so ago to find out how to disable this message and found a page showing how it's done but no matter how I search now, I'm having problems finding it.

I seem to remember it involved adding a switch to the URL and configuring a password in a file somewhere but I've spent an hour hunting this morning with little success.

Can someone point me in the right direction please. I'm going to repurpose an old iPad as a console and would like to leave it on the gauges.

Running CumulusMX v3.9.1 (3096) on a Pi Zero.

Thanks.

Its around line 47 in gauges.js - the default password is "its-me"

http://<url_to_gauges>?pageUpdate=its-me

Thanks Mark - I just get a 404 if I try that though..
*clicky*

I'll reset the password when I get it working (and yes, I appreciate it's not too secure).

Sorry it should be a "?" not a "&" in the url..
https://qso365.co.uk/weather/gauges.htm ... ate=its-me

Feek wrote: ↑Mon 30 Nov 2020 2:49 pm I'll reset the password when I get it working (and yes, I appreciate it's not too secure).

It isn't, but it will stop 99.99% of people camping on the page.

mcrossley wrote: ↑Mon 30 Nov 2020 2:53 pm Sorry it should be a "?" not a "&" in the url..

Gottit, thanks. The gauges.js file needs updating as well, that shows an & in the example

Yep, I noticed that. How many years has it been wrong!

All good, password reset and tested so thanks again.

Hmm, I actually don't think it's working. I thought the gauges had stopped updating so I made a note of the temperature and left it.

After a while, I noticed this..



When I did a cmd-r to refresh, the temperature changed by over a degree and the counter reset.

So although the auto-update limit message doesn't appear, it does stop updating.

Your site, including gauges seem to be updating fine and realtimegauges.txt is current https://qso365.co.uk/weather/gauges.htm
By default setting, the gauges will stop updating after being open in a browser for a while so would need a refresh.

Enjoy,
Paul

PaulMy wrote: ↑Tue 01 Dec 2020 3:18 pm By default setting, the gauges will stop updating after being open in a browser for a while so would need a refresh.

Thanks Paul,
I thought the point of adding the ?pageUpdate suffix to the URL was to stop it timing out and and allow it to continue updating without intervention. Is that not the case?

Was it possibly a network glitch - or data file not available (being FTP'd)? I tested my page and it worked OK. That script doesn't recover too well from some types of failure.

Has this method changed with the new web site? I've updated gauges.js with a new password but I'm getting the auto-update limit reached message again.

Feek wrote: ↑Sun 28 Feb 2021 1:29 pm Has this method changed with the new web site?

Nope.

I left your page running for 35 minutes with the default password and it did not time out.