One possibility is to run some replication/synchronization process to make the inside (MySQL?) database an exact copy of the outside (sqlite?) database. Then run no driver on the inside weewx. Someone who knows the weewx architecture could tell us whether the rest of weewx will function with no driver running.
Another option would be to replicate the loop packets collected by the outside RPi on to the inside: maybe as simple text. The inside RPi could run one of the file reading input options. That would take some development efforts. On Tuesday, 7 February 2017 12:14:25 UTC-4, Andrew Milner wrote: > > I have been considering having an old RPi outdoors connected to my WH2080 > for the sole purpose of extracting the data from the station and would like > to get the loop data so read into another instance of weewx via Wi-Fi > running on another RPi indoors - also on the same local network. Thye > database and report generation would all take place on the second machine - > the sole purpose for the first one is to capture the data. Anyone got any > suggestions as to how to achieve this?? > > My reason for wishing to complicate things like this is twofold - a) I > have an old RPI hanging around which I don't mind putting outdoors but I > don't want HDD etc outside and b) I would be able to have the 2080 console > better positioned to avoid signal loss from the sensors. The indoor RPi is > an RPi3 with HDD running MySQL and lighttpd and is also connected to the > web. In my head I envisage the old rpi essentially just running fousb to > capture the data and build a loop packet - no database, no reportsd etc etc > - but how do I get this into the main weewx running inside? > > I'm sure there must be a simple and obvious solution which I have > overlooked!! > > > -- 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.
