Andrew, I'm doing something similar to Matthew's option 1. Outside is an Arduino Pro Min based logger, reporting to an inside Pi using RF24 library based code on both ends. I wrote the code. The Pi end of the channel publishes the data on my LAN as MQTT.
Inside I also have an Adafruit Feather Huzzah with an HTU21D temperature/humidity sensor attached reporting over the LAN, using MQTT. My desktop server runs a Mosqitto MQTT broker. It also runs weewx which uses https://github.com/morrowwm/weewxMQTT to subscribe to the MQTT and generate loop packets. All this could be on your inside Rpi. So, to answer "further thoughts on the concept", add something like the Adafruit device. On Thursday, 9 February 2017 00:14:14 UTC-4, Andrew Milner wrote: > > Thanks matthew - as ever some very helpful some food for thought in your > response. > Since posting I've realised I have a bigger problem to resolve though - if > the console goes outdoors I lose indoor temperature so now I have to work > out how to get an indoor temperature into the system!! At the moment this > is blocking progress and further thoughts on the concept!!! > > > On Wednesday, 8 February 2017 16:29:35 UTC+2, mwall wrote: > >> On Tuesday, February 7, 2017 at 11:14:25 AM UTC-5, 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?? >>> >> >> piA is rpi connected to wh2080 >> piB is rpi indoors >> >> option 1: mqtt. run weewx with fousb driver and mqtt uploader on piA, >> disable all reports except for a simple status report written to tmpfs, and >> logs to tmpfs. on piB, run an mqtt broker and weewx with an mqtt driver. >> piA sends each loop packet as json mqtt payload. weewx on piB is mqtt >> consumer and receives each loop packet via the mqtt broker. >> >> option 2: database replication using rsync. both piA and piB use sqlite >> database. run some process outside of weewx that does rsync of the piA >> database to piB between archive records. only run wee_reports on piB. >> >> option 3: remote database. make weewx on piA save to mysql database on >> piB. only run wee_reports on piB. >> >> option 4: self-hosted 'cloud'. piA runs a standard weewx installation, >> but with reports and logs to tmpfs. piA also runs rsync report that syncs >> the tmpfs reports (and logs?) to piB. piB does not run weewx - just a web >> server to display whatever reports piA has transferred to it. >> >> oops! now i see that you want loop data, and options 2,3,4 only do >> archive records. >> >> so many options, so little time! >> >> 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.
