TL-MR3020 Goes offline after every new firmware update. **solved**

[wilkerjnc]

Platform:

Code: Select all

System
Platform:	TL-MR3020   (no USB hub)
RAM:	29364 kB total, 3316 kB free (88% used)
SW Version:	Meteobridge 5.1 (Feb 7 2021, build 14307), FW 1.4
Uptime:	7 hours, 49 minutes    Buffer: 2 items (0%)

Weather station:

Code: Select all

Weather Station (primary)
Model:  Vantage
Description:   Davis Vantage Vue, Pro2, Pro1 (FW B), Envoy
Connection: USB Serial
Device:  /dev/ttyMH

(not checked) no restart of logger when lacking data from this station

Every time a new firmware gets pushed, my MB goes off line, and of course no data gets sent to my upload sites, disrupting the integrity of my weather station (i.e Weather Underground, I lose my gold seal).

I also run weewx on my PC on the same network, using MB as the bridge to push the missing records to Wunderground when this happens.

Are there any logs I can get from the openwrt interface to see why this happens?

Can I just disable automatic software updating?

[admin]

Your Meteobridge device does not realize, when a new update is released.
It just loads the most recent SW when doing a reboot initiated by you.

[galfert]

Maybe some other problem or issue is causing the reboot....which then results in a firmware update (if a new one is available).

[wilkerjnc]

Hi,

I could not see where the MB actually rebooted, only that the firmware level had changed.

Are there any logs I could pull other than what I can see on the web interface?

[Challenger007]

Enable manual update. The program will simply inform you that there is a new version. Then you can update the program exactly when it suits you, without losing data.

[jeremyamoore]

I am having a similar issue. Seems to drop off the network after a day or so over the past few weeks - cannot recall when I started having the issue other than after a power outage or a wifi network update/reboot (on UniFi AC WAPs). Has been rock solid otherwise. When I power cycle, it does not seem to come up unless I power cycle it a second time. I am going to force it to stick with v5.0 and see if I get any more stability.

[wilkerjnc]

OK, I have set to stick with version 5

Code: Select all

System
Platform:	TL-MR3020   (no USB hub)
RAM:	29364 kB total, 2892 kB free (90% used)
SW Version:	Meteobridge 5.0 (Jan 1 2021, build 14213), FW 1.4
Uptime:	0 hours, 2 minutes    Buffer: 1 items (0%)

so lets see how this holds up.

[jeremyamoore]

That test did not work for me. My device was offline this morning. I am going to try and run off of ethernet connection and use the latest firmware to see if there is any more stability.

[admin]

Enable manual update. The program will simply inform you that there is a new version. Then you can update the program exactly when it suits you, without losing data.

There is no "manual update" option. We are talking about Meteobridge.

[jeremyamoore]

Update Feb 14... Has been stable for me running over ethernet and latest version - 4 day 12 hours uptime.

[wilkerjnc]

I set to

Code: Select all

Maintenance
Version Control: stick to version 5.0

and no more reboots now for

Code: Select all

System
Platform:	TL-MR3020   (no USB hub)
RAM:	29364 kB total, 3500 kB free (88% used)
SW Version:	Meteobridge 5.0 (Jan 1 2021, build 14213), FW 1.4
Uptime:	5 days, 12 hours, 53 minutes    Buffer: 1 items (0%)

so we seem to have at least solved that issue, stick to 5.0.....

Will a future update be able to stick to 5.1?

[admin]

I prefer solving bugs instead of sticking to old versions and 5.1 is not know to be instable. But do as you like and lock in to the past But what is the way out?

[wilkerjnc]

I am certainly all for running the most current firmware, but how, as in which logs from where; can I see what made the MB restart like that? If I can know that, then I can go back to the current FW and then monitor accordingly.

[wilkerjnc]

OK, so set to get latest FW on reboot and now have:

Code: Select all

System
Platform:	TL-MR3020   (no USB hub)
RAM:	29364 kB total, 3608 kB free (87% used)
SW Version:	Meteobridge 5.1 (Feb 9 2021, build 14308), FW 1.4
Uptime:	3 hours, 0 minutes    Buffer: 1 items (0%)

from the MB log

Code: Select all

Messages
wnetd  (15.02.2021 18:42:37): process started.
system (15.02.2021 18:42:37): start of logging process initiated.
wnetd  (15.02.2021 18:42:37): send data thread started (pid:2331 tid:2333)
logger (15.02.2021 18:42:37): historical data loaded (25 records).
logger (15.02.2021 18:42:37): data logger (version 5.1e, build 14308) started.
logger (15.02.2021 18:42:38): connect station 0 (Vantage via USB serial).
logger (15.02.2021 18:42:39): station 0 (Vantage), wakeup sent.
logger (15.02.2021 18:42:42): sensors are now providing data.
logger (15.02.2021 18:42:42): services started.
logger (15.02.2021 18:42:42): station 0 (Vantage), no need to update console date/time.
logger (15.02.2021 18:42:42): station 0 (Vantage), setup script executed.
logger (15.02.2021 18:42:43): station 0 (Vantage), internal logger activated.
logger (15.02.2021 18:42:43): station 0 (Vantage), syncing.
logger (15.02.2021 18:42:53): station 0 (Vantage), gettime request sent.
logger (15.02.2021 18:42:53): station 0 (Vantage), no Vantage time offset.
logger (15.02.2021 18:42:53): station 0 (Vantage), eeprom request sent.
logger (15.02.2021 18:42:53): station 0 (Vantage), rain collector size 0.01 inch per tick.
logger (15.02.2021 18:42:53): station 0 (Vantage), transmitter 1 active as station type #0 "ISS".
logger (15.02.2021 18:42:53): station 0 (Vantage), firmware version request sent.
logger (15.02.2021 18:42:53): station 0 (Vantage), firmware version 3.80 (supports LOOP2)
logger (15.02.2021 18:42:53): station 0 (Vantage), no reading of Vantage's internal logger.
logger (15.02.2021 18:43:13): station 0 (Vantage), 10.243.1.149's request on port 22222 accepted.

Let's see how this holds up.

[wilkerjnc]

OK, so perhaps the cycle of forcing the older code, then restoring the get newest on boot seems to have solved the MB stability issue as there have been no further issues with respect to the MB:

Code: Select all

System
Platform:	TL-MR3020   (no USB hub)
RAM:	29364 kB total, 3472 kB free (88% used)
SW Version:	Meteobridge 5.1 (Feb 9 2021, build 14308), FW 1.4
Uptime:	9 days, 14 hours, 37 minutes    Buffer: 1 items (0%)

Thanks for the responses.