MB reliance on Server?

[Mattk]

With regard the recent issue with operation of standard MB's and MB Pro's what is the reliance between the unit and the MB Server?

I can understand (almost) why some MB Pro's may have failed especially considering the ongoing updates and bug fixes requiring a re-boot. However not all MB Pro's were in a re-boot mode/cycle when hey failed and do not see any connection to why straight MB's became inaccessible at the same time, MB's that have been running for months without any reboots in the past many months.

Do MB's and MB Pro's regularly or continue to poll the MB server even after a re-boot during normal operation?

[admin]

short answer: No

long answer: Meteobridges connect to server on boot to get latest (or manually selected older)
application stack and to start operation when this is loaded. Version control drop-down
menu on "system" tab allows to define if newest application stack should been downloaded
(which is the default) or if an older one should be used (Versions 2.7 to 2.2 are currently available).
Meteobridges with a USB stick connected will store the application stack on the USB stick
each time Meteobridge downloads one from the server. When version control is set to "USB stick"
then no download from Internet is done, but latest stored version is used instead. In this
operational mode Meteobridge does not depend on getting data from the server on boot.

During normal operation Meteobridges will send sensor min/max data to Meteobridge server
every 10 minutes to make this data persistent over a reboot, power-fail, etc. When server
is not there, data will not be stored, but Meteobridge will not be forced into a reboot or
something like that.

Same rules apply to Meteobridge PRO with the difference that it does not need an additional
USB stick to hold last downloaded application stack. It is always kept on internal storage.
Nevertheless, when version control is set to "get newest on boot" (which is default)
Meteobridge PRO also depends on server to provide this data.

[Mattk]

Would there or should there then have been an access issue with MB's stuck to the last version of 2.5 (July 31. 2015 build 6790)? Confirmed there were running ok based from the output but was unable to login at any time during the server downtime.

[admin]

This will also rely on the server availability, as the archived 2.5 image is downloaded from there.
Only way to get totally independent is to add a USB stick, boot with the version interested in
(2.5 for example) and when unit comes up again tell it to use the USB stick for next reboot.