Experience is what you get when you don't get what you want. What I want is to upload the data from my 5-in-1 to WU more frequently than every 15 minutes. What I got was experience, which I am sharing. ]( "Brick wall")
First and foremost is a simple executive summary of the two Meteo products, which isn't clear in their product docs and forum stickies here:
MeteoHub - Older product, flexible, supports multiple consoles/sensors/data sources, only has support for AcuRite 1025/1035/1525 consoles connected via USB. (No AcuRite Bridge support!) Runs on a Raspberry Pi B/B+, plus several SheevaPlug-type embedded computers. My 1035 console plugged straight into the USB port of a Raspberry Pi B+ with no issues, and read for several days.
MeteoBridge - Newer product, very inflexible, only supports one console/sensor source, has both USB and Bridge support for AcuRite consoles. Runs embedded in cheap home router hardware, dedicated to this purpose. Apparently downloads actual MeteoBridge program from the web whenever it boots, meaning that it has a dependency on their web server running. It also apparently logs summary stats by MAC address to their server, since it can't store them locally in the limited hardware. The hardware being used has issues with USB 1.1 HID devices (like the AcuRite consoles), requiring a USB 2.0 hub to be used as a converter.
MeteoHub's addition of features has been neglected while MeteoBridge was being developed, most notably AcuRite bridge support.
The AcuRite bridge interface is providing multiple data sources, and MeteoBridge does not provide a mechanism to select which sensors should be uploaded to WU and other services. Not a problem if you live in a Faraday cage with only one 5-in-1 sensor, but knowing which one is being sent becomes an issue if have a second 5-in-1 unit and/or an indoor tower sensor that MeteoBridge sees and could possibly upload as valid outdoor data. MeteoHub has the ability to deal with multiple sensors and even let you select which one you want to upload...but it can't read the bridge as an input source! One product can handle multiple sensors but not read the AcuRite Bridge, whereas the other one can read the Bridge but not address multiple sensors if it sees them. Talk about catch-22!!!![#-o]( "d'oh!")
I *really* want to write a check for one of these package! A sensor-selection menu in MeteoBridge is on their wishlist, and back-porting the AcuRite Bridge support from MeteoBridge to MeteoHub apparently isn't on their radar yet.
Fortunately, the USB-to-ethernet adapter that I ordered also came in today, so I can get back to trying to get George's software running on the Pi using the Bridge.....
](http://www.wxforum.net/Smileys/default/eusa_wall.gif "Brick wall")
First and foremost is a simple executive summary of the two Meteo products, which isn't clear in their product docs and forum stickies here:
MeteoHub - Older product, flexible, supports multiple consoles/sensors/data sources, only has support for AcuRite 1025/1035/1525 consoles connected via USB. (No AcuRite Bridge support!) Runs on a Raspberry Pi B/B+, plus several SheevaPlug-type embedded computers. My 1035 console plugged straight into the USB port of a Raspberry Pi B+ with no issues, and read for several days.
MeteoBridge - Newer product, very inflexible, only supports one console/sensor source, has both USB and Bridge support for AcuRite consoles. Runs embedded in cheap home router hardware, dedicated to this purpose. Apparently downloads actual MeteoBridge program from the web whenever it boots, meaning that it has a dependency on their web server running. It also apparently logs summary stats by MAC address to their server, since it can't store them locally in the limited hardware. The hardware being used has issues with USB 1.1 HID devices (like the AcuRite consoles), requiring a USB 2.0 hub to be used as a converter.
MeteoHub's addition of features has been neglected while MeteoBridge was being developed, most notably AcuRite bridge support.
The AcuRite bridge interface is providing multiple data sources, and MeteoBridge does not provide a mechanism to select which sensors should be uploaded to WU and other services. Not a problem if you live in a Faraday cage with only one 5-in-1 sensor, but knowing which one is being sent becomes an issue if have a second 5-in-1 unit and/or an indoor tower sensor that MeteoBridge sees and could possibly upload as valid outdoor data. MeteoHub has the ability to deal with multiple sensors and even let you select which one you want to upload...but it can't read the bridge as an input source! One product can handle multiple sensors but not read the AcuRite Bridge, whereas the other one can read the Bridge but not address multiple sensors if it sees them. Talk about catch-22!!!
I *really* want to write a check for one of these package! A sensor-selection menu in MeteoBridge is on their wishlist, and back-porting the AcuRite Bridge support from MeteoBridge to MeteoHub apparently isn't on their radar yet.
Fortunately, the USB-to-ethernet adapter that I ordered also came in today, so I can get back to trying to get George's software running on the Pi using the Bridge.....