On Thursday, December 14, 2017 at 12:10:49 PM UTC-8, Joe Percival wrote: > > Another, perhaps simpler, approach just occurred to me. On the snow depth > RPi run apache with php and have a function that returns the snow depth > value upon a web request. On the weewx machine, write a custom service > that makes the web request, parses the returned value and stores it. Then > I could use all the suggestions in the documentation for a 2nd data > source. I'd just have to anticipate error conditions and figure out how to > deal with them. > > I've posted on this a few times over the years, but I have a raspi running nginx outside that makes DS18B20 temperatures etc. available via nginx. I generate the file every few minutes via cron, and write a JSON-formatted file out that nginx can server up.
On my weewx system I wrote a custom service that does a web query for that data and saves it to a custom db on the weewx server, which also has lightly tweaked skins to grab the info from that second database as needed. That gets me the benefit of having a really simple outside Pi setup, and an essentially not-hacked weewx setup. My outside data and normal-weewx data are in separate db, which works great. Stuff is in https://github.com/vinceskahan/vds-weewx-local-skin/tree/with-raspi if you have interest (be sure to be on the 'with-raspi' branch). There are definitely cleaner ways to do the extension, mine is kinda brutal, but it's rock-solid in several years of use. Also has the skins with how to reference the second db for the pi-generated data. Feel free to email as needed.... -- 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.
