Random station disconnect from Meteobridge

[OldGray]

My station is a Davis Vantage Vue connected to a D-Link DIR 505 flashed with Meteobridge via a Davis WeatherLink USB Data Logger and a USB 2.0 hub. After inital setup, my problem was loss of connection to the station associated with daily scheduled wireless router reboots, as I previously posted. This was apparently solved by a power down of the station. Since then however the station disconnects from Meteobridge randomly 2-3 times per day and requires rebooting of Meteobridge to restore the connection. The station still connects to the desktop PC (Windows 10) just fine and sends data without interruption. An earlier post suggested that a bad USB hub could cause such behavior and since mine was ancient and of dubious provenance, I tried a new one, but the random disconnects continued. Here is the Meteobridge log of system messages from the most recent disconnect event:

logger (04.06.2019 10:29:29): child process received timeout signal (14).
logger (04.06.2019 10:29:29): disconnect station 0 (Vantage): exit
logger (04.06.2019 10:29:30): data logger stopped.
logger (04.06.2019 10:29:30): historical data loaded (21 records).
logger (04.06.2019 10:29:30): data logger (version 5.1b, build 12980) started.
logger (04.06.2019 10:29:30): connect station 0 (Vantage via USB serial).
logger (04.06.2019 10:29:31): wakeup sent.
logger (04.06.2019 10:29:34): waiting for sensors (wind0, rain0, th0, thb0) to provide data.
logger (04.06.2019 10:29:34): services paused.
logger (04.06.2019 10:29:43): execution of setup script failed (console is not responding).
logger (04.06.2019 10:29:43): internal logger activated.
logger (04.06.2019 10:29:43): syncing.
logger (04.06.2019 10:29:43): gettime request sent.
logger (04.06.2019 10:30:03): message above repeats 2 times.
logger (04.06.2019 10:30:13): disconnect station 0 (Vantage): timeout
logger (04.06.2019 10:30:43): connect station 0 (Vantage via USB serial).
logger (04.06.2019 10:30:43): execution of setup script failed (console is not responding).
logger (04.06.2019 10:30:43): internal logger activated.
logger (04.06.2019 10:30:43): syncing.
logger (04.06.2019 10:30:53): gettime request sent.
logger (04.06.2019 10:31:13): message above repeats 2 times.
logger (04.06.2019 10:31:23): disconnect station 0 (Vantage): timeout
logger (04.06.2019 10:31:31): give up waiting for sensors after 120 secs.
logger (04.06.2019 10:31:31): services activated.
logger (04.06.2019 10:31:53): connect station 0 (Vantage via USB serial).
logger (04.06.2019 10:31:53): execution of setup script failed (console is not responding).
logger (04.06.2019 10:31:53): internal logger activated.
logger (04.06.2019 10:31:53): syncing.
logger (04.06.2019 10:32:03): gettime request sent.
logger (04.06.2019 10:32:23): message above repeats 2 times.
logger (04.06.2019 10:32:33): disconnect station 0 (Vantage): timeout

After this, the last seven lines continue to repeat forever. I was lucky to catch this event while the initial disconnect was still in the log. I would appreciate any suggestions, otherwise I guess I'm stuck with using the PC and WUHU to get my data out.
Steve

[admin]

Your Davis logger does not return any data. Please power-cycle the Davis console to get its logger back to work and/or check if the logger is correctly inserted into the console. No problem with Meteobridge but with your Davis equipment.

[OldGray]

The station reconnects after rebooting Meteobridge, so if the Davis logger is the problem, rebooting Meteobridge temporarily corrects it. However the Davis logger works fine when sending data to the PC, the station has never disconnected when feeding data to WUHU on the PC. I tried power cycling the console. I confirmed that the Davis logger is correctly installed in the console. Maybe there is a hardware issue with the DIR 505 which I purchased for the sole purpose of using it with Meteobridge. I never actually used it as a router before flashing the Meteobridge firmware.

[admin]

Can you try another USB hub? May be there is some incompatibility there.

[OldGray]

I tried two different USB hubs, one powered, one un-powered. Same problem with either hub.
Steve