Hello fellow WX enthusiasts. I've been lurking since August last year. Thanks for your collective knowledge. Thank you also to Tom and the myriad of other contributors for creating and refining the software.
I've been running weeWX on a Banana Pi M1 since January. Initially I rolled my own FileParse driver and loaded archive data into weeWX from a VP2 connected to a Meteohub instance which was running on a Rapberry Pi Model B. This month I decommissioned Meteohub and weeWX is now reading the data directly from a Belfryboy USB logger. The platform Wireless VP2 with vanilla ISS (no insolation sensors) Banana Pi M1 storage - 32GB Class 10 SDHC hwclock - battery-backed DS3231 on the i2c bus network - TL-WN727N USB wifi adapter Armbian 5.31 (kernel pinned at 4.9.12-sunxi) weewx 3.7.1 (installed from the PPA using apt) Customisations non-root weewx user separate weewx log file Bootstrap-based website uploading to WUnderground and Weathercloud Additional packages sqlite3 zip lighttpd php php5-cgi php5-sqlite phpLiteAdmin fonts-freefont-ttf Historical observations were brought across from the Meteohub raw files using a custom perl script and wee_import. Installation and configuration wasn't entirely straight-forward. The hwclock required a custom systemd unit. The 4.11 series linux kernel broke wifi encryption (which is why I've pinned it at 4.9.12). Armbian uses a disk-backed memory store for /var/log and the voluminous log entries generated by wee_import filled the in-memory filesystem. These were relatively minor bumps in the road. If there's interest, I'm willing to expand on any aspect of the journey. Cameron -- 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.
