I do something similar, though less interesting than what you are doing. I have an external building with a raspi model-B and a couple DS18B20 temperature sensors. A cron job captures the sensor data and writes a json-formatted file to ramdisk, which is linked into a nginx web document root. My weewx system inside the house runs a custom extension to grab that file and save the data in a separate custom weewx database. My local skin grabs data from both weewx db and the custom db containing just the data from the custom sensors.
So I guess it's Tom's option (4) from his response. My thoughts were: - it's easy on the outside pi to capture the data and make it available on LAN via nginx - it wasn't too hard to write the custom extension to add to weewx inside - I didn't have enough compute to run multiple copies of weewx inside anyway, I run on a 128MB ram ARM processor ala a pogoplug notionally All the MQTT magic things came out years after I had my custom solution in place, so they weren't available way back then....but they sure seem cool to say the least. I'd probably go that way if I was going to do it over again. But definitely store your data in a custom db in weewx, that is really helpful especially if your outside sensors throw some bad data occasionally that you need to clean up. That way you won't need to rebuild or touch anything in your primary weewx db. -- 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.
