At the HVAC control level it would be a Pico - for the development / maintenance time efficiency: I know how the tools work, I know the community support is there, the hardware is easy to find and available relatively reliably, although ESPHome on the ESP micro-controllers is pretty good too.
It’s impressive what a gentle breeze will do - if you can get a fan on your cabinet it will help a lot.
I filter my air and positive pressure the cabinet so the dust doesn’t build up (as fast).
Xfce on Debian is my preferred flavor these days - regardless of machine power.
I got my modem working in Slackware in 1997 - but the PPP driver (equivalent of WinSock - which worked in Windows quite well at the time) would only work during the first boot of the system. After a reboot, PPP would never return, and the best I got out of the internet about it at the time (mostly using my Windows PC) was “real men connect to the internet through ethernet.”
Between that an the useless (unless you enjoy frustration) sound drivers, I declared Linux “not ready for prime time,” and left it to others until starting back in via Cygwin in 2003, then Gentoo (for 64 bit access you couldn’t get any other way) in 2005.
I will say this: we had a big lightning strike a few years back and it conducted into the house via the internet cable, then spread via the ethernet cables taking out everything that was wired (over $7K in damage) - devices connected only by power and WiFi were mostly spared.
Don’t like the expensive version? Get a Zero 2 W which outspecs the original by a wide margin.
There was the supply shortage price spike, they really were stupid expensive then if you supported the hoarder/scalpers.
Since that has cleared… most of the Pi price increases (in inflation adjusted dollars) can be attributed to improved features like more RAM, or people acknowledging that having a good dedicated $20 power supply is preferable to dealing with the flakiness of that old phone charger you found under the bed.
Pi is popular with me because it’s time efficient. Meaning: when I am trying to get it to do something, it takes less of my time to make the thing actually happen on Pi hardware as compared with most of the other small / embedded alternatives. Notable recent exception: ESPHome on ESP32 hardware, but even there the more limited variation of Raspberry hardware makes it similar to those fruity phones, MP3 players and computers - since there are a limited number of variations, you can usually find information specific to EXACTLY your setup, instead of having to infer from something almost the same, but figure out little wrinkles here and there due to differences between what you are working with and what you are reading about on the internet.
Like: using the pi to manage your HVAC more efficiently.
My question is usually not how many flops, but how quickly and reliably those watts can give me just a few flops on demand.
Well, the idea scales, if your energy is 0.33 Euro per kWh take the watts x 3 and that’s your annual running cost.
Yeah, they’ve reversed that trend for sure.
My WiFi routers have historically struggled a bit, I’ve got a decent one now, but even it is slow to manage the DHCP lists for fixed assignments by MAC address.
For me it’s not about the bandwidth, it’s about the lag and reliability. I have had strong WiFi connections flake out a lot more than wired connections.
Also, I just prefer to not have 100+ WiFi devices kicking around my network when more than half of them could be wired, or on another protocol like Zigbee.
That depends if the mini-PC is something in the Celeron / N100 family, or the Core i5/i7 family.
A good “rule of thumb” to remember: if your electricity rates average (somewhere near) $0.11/kWh you can take the average power draw of a device in watts and that is equal to what it will cost to run that device 24-7 for 365 days.
So, if that cheap PC draws 50W more than an alternate solution, it’s costing you $50 more per year to use it.
Some tasks are beyond any RasPi, but it’s well worth evaluating if something like an N100 fanless mini-PC can handle it instead of loading up some Core i7 rig that’s going to cost more to run in the first year than the N100 costs to buy.
And they passively cool better that way much of the time too…
As a Pi Hole, the Pi 5 doesn’t require active cooling.
Now, I am running a separate Pi 5 with a HAILO 8 for Frigate monitoring of a bunch of video streams, and it does need a little air movement, so I built a box with a 200mm fan pulling through a filter and I just threw all my Pis in there along with the Frigate rig so they stay nice and cool… I’m thinking that I should probably switch Frigate over to a Pi 4 for the h.264 hardware decoder, but the 5 is working fine for my needs and endless tweaking gets boring…
I agree that the Zero is up to the task, but I prefer a wired connection for my home DNS/DHCP server and if I understand correctly the Pi5 has better wired ethernet than its predecessors… Yeah, utilization is laughable, but there’s something to be said for reduced lag time too:
Hostname: pihole
CPU: 0.2% on 4 cores running 318 processes (0.3% used by FTL)
RAM: 25.9% of 2.0 GB is used (7.4% used by FTL)
Swap: 35.9% of 512.0 MB is used
Kernel: Linux pihole 6.12.25+rpt-rpi-2712 #1 SMP PREEMPT Debian 1:6.12.25-1+rpt1 (2025-04-30) aarch64
Uptime: a month (running since Sunday, May 18th 2025, 17:54:59
I did OS-X for my MacBookPro daily driver 2006-2008 (said premium laptop dying because of mis-applied thermal paste by the factory) - and started using a bit of Debian and RedHat at the time… my observation was, and still is: they all suck, but in different ways. If you value stability and control, there’s no comparison to the open source model. Windows used to have the edge for hardware support, but that has eroded to the point that we had selected a WiFi card for our Linux system this year, but we’re having to change now that we’re moving to Win11 - no Windows drivers for that M.2 WiFi/BT card.