meteohub.de

Hi... My Ambient Weatherbridge (based on the TL-MR3020 v1.9) is stuck in a constant reboot loop after a recent power outage. What I think is happening is that it is retrieving the most recent MB software (it's config'ed for "update on boot") and crashing on the attempt to install it. In the brief time I have after booting (about 90 seconds), I have been able to SSH into the unit and kill the start process, which stops the rebooting but, obviously, leaves the unit in an error state (the MB server responds with its standard error page). i was able to screencap this process and related on the OpenWRT panel...
I've paid for the MB 2-year subscription update and I think it's still in effect... but even still, a non-updated subscription shouldn't brick my meteobridge.

1) Have there been any similar reports based on this config (TL-MR3020 v1.9 + VantageVue, sourced from Ambient)?
2) Is there a way for me to edit the config so it doesn't attempt an update on boot? Where is the config file on the server?
3) Can the MB server be launched at the command line when I SSH into it, allowing me to use the MB server itself to config that autoupdate setting?
4) Can I restore an older MB software package and reinstall, either with the OpenWRT panel or via SSH/Unix command line?

My bridge is effectively bricked right now. I am confident that it is connected to my router (I'm SSHing via WiFi), and I can see the MB "error message" page just fine. This is connected to a Davis VantageVue if the matters (and that console is communicating with the weather station fine). I am also confident that the unit is communicating with the Internet because it's able to do a time reset via NTP. I'm sure I can test this in other ways at the command line, but please assume internet connectivity isn't the problem.

Ambient has basically said, "it's your problem, talk to the MB guy." Please help!

Additional: This whole system has worked for >4 years, and nothing has changed in terms of equipment.

Sounds similar to my problem, I decided I wanted to reboot it after being on for like 60 days. Gets fresh updates etc. But it got stuck in reboot and not able to connect they wifi anymore....bi wonder if it's related..

I am totally connected to WiFi (the debugging I've done is totally with the unit attached as a client to my WiFi). I think the default "you're not connected" error page is in error and hasn't anticipated the condition I believe is happening.

I think the most recent MB SW update is either too large, or otherwise does not function on this device. I am looking to roll it back, or just launch what I hope is the functional-and-not-yet-updated SW already in the router, and use it to turn off the auto-update-at-boot feature until the problem is addressed.

I bought a new one and it to couldn't connect they wifi. But I was planning on buying one for my house when I get a weather station. They both work with direct cable and therefore I moved the station to buy router yesterday.

Looks like the old MR3020 version 1.x struggles with the size of the latest application image.
I will fix this shortly.

Boot loop error should be fixed by now.

It appears maybe the boot loop issue is back. I had a power outage today and I cannot get my Meteobridge to get out of the boot loop.

I don't think so. What did you do to analyse the problem?
Did you inspect "getting started" section of "meteobridge.com"?

I've had this particular unit for many years now so the "getting started" instructions are irrelevant I believe. It was functioning just fine up to today until a short power outage. It's been trying to reboot for hours now but constantly in the loop similar to what happened when the previous firmware update was applied. I have verified it is connected to my wifi with strong signal. It turns on, does slow flash for 60 seconds, then quick flashes for several minutes, goes solid for a few seconds and then starts the process all over again. I have changed nothing in the settings for quite some time...months at least and it is set to automatically update to latest firmware upon startup. The last time I had this issue was with the last update as described earlier in this string. I have attempted multiple restarts by pulling power since I cannot log in to the unit and I have attempted the 5-second button press to restart a couple times as well with no change.

Nevermind...I've reset the entire system. I'm really hoping this isn't something I'm going to have to do every single time I have a power outage.