Same Here. I'm beginning to think that the Bridge can't continue to function unless MBY is up. I'm curious to know how its firmware functions. I'm wondering if it is programmed to reboot if it does not receive a specific response from the Acurite server when it attempts to upload data. So, when it looses contact with the mothership it begins its reboot cycle and thus the Meteobridge is left with no data to sniff.
I use a Raspberry Pi setup that allows me to run independently of MBW. I designed it for times when my link to the Internet might go down for issues like severe weather.
My scripts don't look for a response code from MBW. Under normal circumstances, however, it does return the string:
{ "success": 1, "checkversion": "126" }
after each transmission. I've never caught it changing, but that "126" probably refers to the most recent version number of the firmware available.
During the last outage, I was only getting the "success" code half the time. I'm not sure if that means half the data was being lost, or if MBW was just too sick to respond properly.