Skip Navigation

What Are Your Favorite SBCs (Single Board Computers), Why, and How Did You Get Into Them?

Like most people, I entered COVID as a normal hobby geek with a Linux server I played around with and a healthy hardware habit with a side of home automation and DD-WRT. I emerged from COVID enrolled in college, now with two servers (one new build, one rebuilt from my first one), two Pi, multiple instances of Home Assistant (one dedicated) and putting sensors on everything a sensor could go on and rewiring switches for wifi control of overhead fans, flashing every compatible router I could find on Amazon Warehouse with DDWRT in my home for an ad hoc mesh network (no, it didn't work, but I didn't care) while cabling everything to switches and creating a really hilarious network deathtrap tripping hazard, a massive media library (discovered Handbrake and making multiple resolutions) and a Sonos home theatre system. And yes, played an unhealthy amount of Animal Crossing and got an NVIDIA Shield Pro for streaming and Plex, as you do. I'm sure everyone can relate.

SBC's were the natural escalation; I had credit card bills to pay off and that's going to take a while.

I gatewayed with Pi like ten years ago but it took off during Later COVID when I noticed my credit score and started testing it as a NAS, Media Server (later: Cassiope Media Server, my second end to end Linux build), then got into learning about the kernel itself. I already had an Odroid (Home Assistant Blue) so why not go on, so project-based SBCs seemed healthy; I had a reason for buying one. This led to more Pi's--as I couldn't use Kernel Pi (Eurydice) for it and Andromeda Pi was masking my personal network, then I needed one for a Pihole (Iphigenia, Hecuba), which is how I ended up with a BeagleBone Black (Medusa) for an Open Thread Border Router. Still pretending I wasn't just collecting them like cats, I networked them together and just enjoyed looking at them and making them matching banners with figlet with the excuse I was learning how to do network-wide deployments over SSH (true) and learn Debian OS (technically, I am doing that) and started PoEing things (my credit card bills may not be getting lower, no).

The count stands at a total of 9: one (1) Pi Zero W, one (1) Pi Zero 2 W, one (1) Raspberry Pi 4B 4G, two (2) Raspberry PI 4B 8G, one (1) Odroid N2+, one (1) Beaglebone Black, one (1) PocketBeagle, and one (1) BeaglePlay. (Other: two Linux machines, Watson and Cassiope). Yes, they all have names and technically, each is associated with a project. The BeaglePlay's (Circe) associated project is 'create my own documentation on what it does because Beagles don't document'.

So which ones do you use, why, origin story, feelings: go.

(I'm moving in a week and half my hardware is being packed. I'm about to have to take down my network and Home Assistant and may be freaking out. I'm not sure I know where any light switches are here, either.)

98 comments
  • I consider SBCs drastically overhyped these days. RaspberryPi was nice enough when it was released a decade ago, but these days you can just get a Beelink or similar miniPC, which is much more capable and often even cheaper. It doesn't have the GPIO, but even if you need that, you are generally better served with a cheap MCU connected to USB.

    My old RaspberryPi's all just work as webcam these days.

    • Often even cheaper

      Where can I find a cheaper mini PC? They all seem to be like $250+ on Amazon, Beelink included.

      Before RPis went up in cost they were $35. Isn't there anything in that price range?

    • I consider SBCs drastically overhyped these days. RaspberryPi was nice enough when it was released a decade ago, but these days you can just get a Beelink or similar miniPC, which is much more capable and often even cheaper. It doesn’t have the GPIO, but even if you need that, you are generally better served with a cheap MCU connected to USB.

      I would put it another way; they're ideal for You Have One Vital Job Only projects; Home Assistant and Pihole are my two specific,, but robotics, a router, even a dedicated NAS would be a use case. I could run a lot of things on a mini PC with a hypervisor--soon, I shall start be experimenting with that--but One Vital Job Only projects are ones that do their thing without me ideally ever noticing them other than maintenance, if that makes sense. And even more important, things I should not tinker with because they're just fine, which is why I ended up building a second, dedicated Media Server/media ripping/encoding/NAS machine; once I did that, I finally had a stable media library I could access for more than a month at a time before I got An Idea That Would Be Fun and Oops Time To Reinstall (seriously; before I built that machine, I had to run my media and plex from a Pi (aka One Vital Job) because if I put it on my main machine, I'd tinker it to death; hence, separate everything. I am basically hiding the cookies from a three year old and I am the three year old).

      Tentatively--and this applies to a much smaller population--they're perfect for deconstructing the Linux kernel and operating systems in general because you get to work at a reduced scale. I have the repository for the Pi kernel in my bookmarks and go to just read through it and get familiar when I have some time or if I remember something I want to look for (my usb wifi dongle testing project was invaluable for how much kernel homework I had to do, it's hilarious). I know and can write in basic C++, I know how to compile, but I still don't pretend to understand the kernel; with the Pi's scale, though, I can grasp it, if that makes sense. I can recognize the structure and begin to get how things fit together. I can even--tentatively--find specific parts, identify drivers, especially when it comes to specific removable hardware where it's fairly obvious and easy to follow (following actual driver files....that's in progress). My goal before I die is to be able to read and follow the entire kernel end to end; I think I'm going to need to look into the benefits of reincarnation or cryogenics admittedly, but hope springs eternal.

      (BeagleBones--if nothing else--has seriously upped my game on Figure It Out For Yourself. Which yes is a very me-specific use case, requires more homework to get context than literally every class I'm taking combined including TCP/IP class, and I literally don't have time to do in more than sprints, but did lead to me literally being able to making my first Universal New Install Checklist (covers every Linux operating system I've ever used including all my personal configurations and scripts, in order, with all exceptions) and my first foray into creating an auto-install-and-configure script I can run on a new machine. Yes, those Beagles had me doing a clean install that many times. No idea what I'm doing there and I really wish there was a universal template for that.)

      Having said that, I haven't jumped into MiniPC/hypervisor culture so I am up for changing my mind the minute I make the leap. And seriously, this thread has moved it actively up my priority list, which I did not see coming, so thank you for that.

  • I have 2 Odroid C4 SBC's that I use as desktop replacements and an Odroid C1 that is my pi hole and Quake 2 server.

    All very capable for their intended purpose. Very happy with them. I chose them because they were more powerful than contemporary rpi devices.

    • ODroids are massively underrated. The first Pi we bought is dead. The second one is now so underpowered for what we want that it's been turned into retro arcade machine. It still finds ways to cause problems too. Whereas our first ODroid is still going strong after many years of faithful service. We added an ODroid toaster to the mix a couple of years ago that's also given us zero issues and works wonderfully.

    • I bought Home Assistant Blue from Ameridroid, which was Home Assistant's first (and happily still continuing) jump into making Home Assistant more accessible and easy if you weren't a hobbyist or tinkerer: Odroid N2+ preloaded with Home Assistant OS, a super adorable blue case, and power supply. That was my first experience with that board and with eMMC; 128 GB of it, talk about turning my head (also 4 GB RAM). Honestly, the only reason I didn't get another is I didn't have a project that required it; the reason I even found out the Beagles existed was the Open Source Border Router project I wanted to do had it as an option for the walk-through and gave me a reason to test drive.

      But I have to agree: I've been running it straight for three years now and the Odroid does its job with zero issues. Home Assistant and its parts have given me problems, but Blue (yes, it's name is Blue, it was just there) never does.

  • I started with an RPi 1b to read out my weatherstation (WH1080 clone) and post it online with weewx. Then a Bananapi R1 entered to replace my intel system as firewall/core router (savings on power usage, a lot). The RP 1 got replaced by a RPi 2, and tne 1 moved to the smartmeeter for readout. The main server (huge AMD tower) got replaced by a RPi 3 (again, power savings), Bpi R2 replaced the R1 when bananian development stopped. RPi 3 died on me (sd slot failed) and I got a replacement. As the 1st RPi3 was dead anyway, I tried to repair it (only use of the solderings at the side proved to be to keep the slot in place) and used it to replace the Bpi R2 as support got problematic.

    The main server got upgraded to a RPi 4 8GB, with the RPi3 replacing the RPi2 that was handeling my weatherstation. I got an rflink, so I added domoticz and that now powers my kaku (dutch power switching system) in a mixed old/new setup. The RPi3 that was my main router (internet router via fiber) got replaced hh an RPi4 witn 4 GB mem, as the 2 GB mem version wasn't available. (Not a bad move, with the on-board non-usb 1GB interface and a tad over 2 GB mem use)

    The freed RPi3 is now for the smartmeter, so all RPi are 64 bit. (All running aarm64 Debian) Both Bpi's and RPi 1 and 2 are collecting dust, as I haven't found a use for them... yet. Looking for projects to use them. As media server they're to light. (Although, Bpi R2 could be useful for that)

    • Oh, this is a nice collection!! If you want to experiment, either RPi will support Open Thread Board Router if you're into that, or a NAS; I ran one off Pi 4 with OpenMediaVault and it did not even dent its resources.

      I am now wondering if I should start looking into my own firewalls.

  • I haven't gotten one yet, but Orange pi 5 plus.

    Why

    "Can't use if I can't maintain" -- low power usage > performance, pretty much. And I'm 100% down on ditching my desktop PC for a couple of those little guys.

  • I get the appeal of the single board computer but it never held much interest for me. That could possibly be because my manual dexterity isn't that good and I found the assembly side of the SBC to be daunting. I've been more interested in using the tiny form factor Dell Wyse and Lenovo micro machines.

    • One of my friends set up Proxmox on a Lenovo M93 he got on Amazon and runs Home Assistant, Pihole, and some other things off there, and I seriously seriously want. I've been curious about hypervisors since we went over them in class, and seeing his interface hit my 'yes now' button.

      What do you use yours for?

      • I have a Dell OptiPlex 7050 micro with 16GB of RAM and 256GB SSD. All it's doing is running OpenBSD as my firewall and router. But it is doing some complex routing and traffic shaping and queueing. It's also a VPN termination point for the WireGuard tunnel between my cloud VPS and home network. My cloud VPS is, in this case, a reverse proxy.

  • I've been using a Zima Board for my home network. I have the mid-range, 4Gb memory, 32GB onboard. It's got two SATA ports, dual gigabit Ethernet, an Intel processor and PCI express port that I'm eventually going to use to run an old wifi card so i can isolate my IOT devices on a dedicated wifi network.

    The only problem i have with it is RAM and transcoding. I have 22 containers running things from the "arr" suite (Prowlarr, Radarr, Readarr, ect), pihole, Jellyfin, Home Assistant, etc. I stay around 80% memory usage, so i should have gotten the 8GB. And forget about trying to transcode Blu-ray rips, which most of my devices can't stream natively, so transcode is the only option. The audio stutters and playback pauses every ten seconds or so. I don't have a problem streaming the file through samba, it just doesn't have the "omph" that it needs for hardware transcoding of Blu-ray.

    All that being said, i would get another one over the Raspi. Case/heatsink built in, SATA, PCI-E, dual gigabit, everything i need for a basic server.

    • Friend, this reply is beautiful. And reading the Zima site, I may be sold. What do you use to run the network? OpenWRT, DDWRT, Tomato?

      And forget about trying to transcode Blu-ray rips, which most of my devices can’t stream natively, so transcode is the only option.

      Ninety-nine percent of the time, I am unqualified to advise on anything; thanks to COVID, I got deathly into making a media server and ran into the transcoding problem followed by making a spreadsheet and experimenting and documenting my results.

      My results (other can disagree): all my transcoding problems came down to audio streams and subtitles. None of this may apply to you, but just in case.

      I approached it from three points: a.) I got the NVIDIA Pro to run Plex as NVIDIA can handle anything; b.) I made a server just for my media processing and storage (it also runs Plex as a secondary instance when my Shield is in use). I use MakeMKV for the raw rip into an mkv container with all audio streams. The rip I process through Handbrake so I can get as close to a clone as I can (4K to 4K, 1080p to 1080p, etc) with full original audio then make a copy of each and every audio stream into the equivalent container that was compatible with the sound limitations of whatever I was planning to stream it on. Example: my Sonos speakers wanted Dolby: DTS 7.1 to TrueHD. I also did a third copy of each stream into the equivalent AAC containers: TrueHD to AAC 7.1 to future proof. I also added a fourth copy that's a basic AAC 2.0 that rolls with anything; and c.) Subtitles: turn them off and use open subtitles files so no one has to deal with bitmaps. I tested through Plex to make sure, and watched for the switch from direct play to transcode, then reverified on my Windows machine, etc.

      Yes, it will eat hard drive space like whoa--uncompressed audio streams do that--but with surprisingly few exceptions, I can get direct play for 4K on pretty much anything now, not just Plex. I also create multiple resolutions using either original rip 4K or original rip 1080p as source but with the same audio mapping (that's a me-thing and also, Covid). I know this sounds like a ridic amount of work, but once I set all the profiles, it's basically a batch job. My total movie library sits at 400 movies with about 1200 files; last year I re-audited my Handbrake profiles, deleted everything but my source rips (and actually did a mass re-rip on the older ones that I did before I started compiling the latest ffmpeg to use when compiling MakeMKV), and re-encoded everything using those profiles. Total time was about two weeks end to end; I did them in batches of fifty and checked in every six hours to move completed files back into my media drives and also restart.

      The only ones now that need me to personally go in and make corrections are the remastered releases like Apocalypse Now and Scarface (my files were twice the size of the original, it was unreal). Every one of them rips huge and needs slightly different profile tweaks, so those I oversee personally.

      I don't know if any of this is relevant to your setup, but I reverified running Plex on one of my Pis and it could direct play at least 90% of the 4K and anything lower, and the 4K problems seem to all be with those remasters.

  • At work we develop instrumentation used in outdoor surveys, and I am writing a new version of the software which downloads the data logger and so forth. This is done by connecting a little USB dongle to the instrument.

    Lately, I've been thinking about the possibility of adding an SBC to the dongle itself. My new generation of the software has a low-level component written in C++ which handles the USB I/O and a GUI component written in Python. So the idea is the C++ tool would run on the SBC and the Python would be a client that could run on any machine with LAN access to it.

    So I am wondering at this point what would be a good candidate for the SBC? It would not need to be particularly high performance I think? Low power requirements would be good. And it should support wifi and ethernet and be rugged enough for outdoor use. (It would be protected by the metal enclosure of the dongle but may still be subject to temperature swings and some rough handling.)

    • I am seriously regretting that I haven't bought more SBCs so I could give you an informed opinion and I desperately hope someone answers this.

      With my Pi and Beagle limitations: the Pi Zero 2 with an ethernet hat and battery hat or power block would probably do it; the hats aren't hugely expensive and if there's one thing the Pi ecosystem has in abundance, it has cases for eveyrthing (Argon has a jawdropping modular case design for the Pi Zero; it's like art and that costs more than even the ridiculously inflated price of a Pi Zero 2, which is saying something). Right now, it's also--for what it is--overpriced. I'm trying to decide if the BeaglePlay would be worth your time to look into; it has wifi, bluetooth, ethernet and single-pair ethernet and integrates with Freedom Connect but it's very new, the documentation is bad to literally non-existent, you'd need to custom build the case, and it's design seems geared toward IoT, automation, monitoring and controlling remote sensors with any existing network protocol, and existing as a vague super cool enigma I am still not sure what to do with as it has a lot of onboard functionality built in and no idea how to use most of it.

      I am totally watching this thread for people's suggestions.

  • I initially got a Z80-MBC2, a Z80-based SBC that runs CP/M and other operating systems, as I had developed an Intel 8080 cross assembler and wanted to run on actual hardware the code assembled with it. It was so fun I got a V20-MBC, an SBC by the same maker that features a Nec V20 (8088 + 8080) and can run CP/M-86.

    Both SBCs led me down a fascinating retrocomputing rabbit hole.

98 comments