quite some time ago i tried to incorporate this kind of behavior in the fousb driver. that worked, but only with specific usb hubs, and only if you got the device and port right (and only if the device and port did not change when the system rebooted).
if i were to do it again, i would probably make it more generic, so it could be a standalone service, a separate process, or perhaps a module that could be used by any driver. one approach is a weewx service - do a check every loop or archive to see if the station is alive, and if not, tell the hub to power cycle the port. the check might be as easy as checking for an rssi value or sensor data. another approach is a separate process - check the database every archive interval, if no new data, then tell the hub to power cycle the port. having the check in the driver potentially lets you detect a failure more quickly, and to distinguish between different types of failure. for example, a station might miss data for awhile, then collect data later without any intervention - it really depends on the hardware. having the check as a service or process would be more generic, but might end up power cycling when it is not necessary. m -- You received this message because you are subscribed to the Google Groups "weewx-user" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
