If you're only using InfluxDB for WeeWX, then a RPi is fine. However, I feed my entire home data collection into it and it would quickly overwhelm both the I/O rates of the RPi as well as memory (CPU would be fine). My InfluxDB instance is using just short of 3GB of real memory and 60+GB of virtual. I ended up moving it and Grafana off to a dedicated box (and a bunch of other monitoring tools) a while back as it was causing I/O issues on my home server. If don't have a drive connected to your RPi for the data you are also going to kill your SD card with the number of writes InfluxDB does. It's a stretch even for the high-write rated cards. I tend to avoid putting anything that requires high data writes on a RPi for that very reason.
I am tempted to get an 8GB RPi 4 with an external drive and move a bunch of things off to it though and retire one of my older server boxes... I'm using HA for MQTT, it gives me a central place to send it and lets me use it for driving home automation tasks. That includes my power monitoring (Brultech GreenEye), WeeWX output, and motion activation from my cameras (BlueIris). Funny you mention docker, as that's how I'm running most of my applications these days unless they are on a RPi. It makes them easy to move around from system to system and to manage upgrades. I run very little in docker on my NAS though, it just doesn't have the CPU power (although it is where I'm running Plex). My LMS server is in Docker however on the NAS because it's easier than dealing with Synology's package that they break from time to time. As for the music player -- the RPi is the player, not the streamer. Since the NAS doesn't have audio output, I need something to feed the music to my stereo (and the speakers in the bathroom). It pulls the music directly from the NAS and the one in the bathroom has a 7" display on it so it can be controlled either locally or from a phone or tablet. We don't have VoIP, our phone lines terminate in a analog-to-voip box from GrandStream. We don't really need the PBX, but it does give me a way to make telemarketers go away as the home phone only rings after some either goes through a IVR (which robocallers can't figure out) or comes from a known number. On Thursday, June 4, 2020 at 5:28:34 PM UTC-7, Xant wrote: > > > Daniel > > Thanks for your feedback, but think there is a misconception. Think that > RPi can handle much more load than you think. Underneath, is snapshot of my > RPi4, which runs: > > - WeeWX > - Belchertown skin > - MQTT (which I forgot to mention in original post) > - Influx + Grafana > - Nagios > > To note, RPi4 takes all as a breeze, with much more room to spare (and > that's why looking for other "RPi projects" to investigate). > > My RPi4 Grafana monitor dashboard: > > > As it can be notice, CPU usage is almost 'none', and can take more... > > Similar to your posting, thought Influx/Grafana would be too much for RPi, > and tried install in the NAS first... Big mistake, too much trouble and > docker, while Influx/Grafana in the RPi is how its supposed to be. > > The only reason I'm using Pi-hole in the RPi3 (which it was the one now to > spare), is that its now my main wholehouse DNS, and don't want to > reboot/shutdown at times. > > Per your feedback: > > - Home-assistant - will investigate > - Asterisk - though about it, but it is a PBX thing, not a VOIP; a PBX > is too much for home use, while I continue searching for a VOIP own > hosting > option... if it ever exist; so far, I have Ooma > - Stratum - will investigate > - Conserver - will investigate > - Flightaware - will investigate > - Music Player - not for the Pi; have Plex on NAS > > Xant > -- 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]. To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/e8b04754-5d5c-47b7-bba6-b247642eceeao%40googlegroups.com.
