I’ve got a Lenovo M720q running as my main server in my home and it’s more than powerful enough for anything I could be doing right now. However, I also have a Le Potato lying around that I’d like to do something with. Any suggestions?
You must log in or register to comment.
Donate it.
Using it just draws more power.
- DNS resolver, like pi-hole, unbound with adguard, diversion, etc.
- RMS server: a lot of Remote Desktop software has the option to install a listener on a low power device elsewhere on the network that can use wake-on-lan to access computers within the network without keeping everything on 24-7.
- Log aggregator: would be useful for anyone who troubleshoots stuff regularly, but historical info of any kind can come in handy.
Simplest form might be a scribe server. Network gear often has an option to send logs to a particular URL, so if you added the scribe server IP/port to the field you’d have historical network logs.
Additional loggers could also be run on-device, such as a wifi connectivity checker or a Fing server.
If you have a smart home setup, you could also log state data or energy monitoring history at a particular interval, or run a homebridge or homeassistant instance.
Edit: list subitem formatting messed up
Add to the list running a Kodi home theater box.
Sensors. Especially sensors in your living space where fans or other noise from the proper server would be distracting, or in a tight space - inside your HVAC, for example - where a proper server wouldn’t fit.
Media front-end. Most of those SBCs are more than enough to run a kodi or jellyfin frontend, fanless for minimum distraction.
Robot. Low power requirement so it could be mobile; but there are lots of stationary possibilities. GPIO libraries are great for running servos and there’s tons of libraries to facilitate.
Home Assistant for family members
Media server client, pihole, emulation, programming or home automation project. You could even prop it up as a standalone web server and make some kinda creative thing.
I have an Rpi4 4gb model and run Uptime-Kuma who’s sole purpose is to monitor my server and alert me if it should go down. I also have it acting as a Tailscale exit node.
I run Pi-hole and PiVPN on my Pi 0W.
Lower power draw is about it. But there are now x86 SBCs that can also run on as little as 6W so there’s no reason to compromise and use ARM’s non-standard fragmented BS.
Which x86 SBC is that? I’m interested!
The LattePanda Mu is configurable and can operate on as little as 6W up to 35W depending on your use case. The much more affordable Radxa X4 can operate on as little as 18W up to 25W if you need to power peripherals via USB.
Both use an Intel Processor N100 SoC which is surprisingly powerful and efficient given that the Processor N series is the new branding for what used to be called Celeron.
The prices are also competitive. The X4 for example sells for exactly the same price as the Raspberry Pi 5 with the same amount of memory at every memory capacity tier while having a CPU that’s twice as powerful and compatible with way more software and OSes and a GPU that is absurdly more powerful and fully publicly documented such that there are open source drivers for every OS under the sun.
As an OS developer both professionally and outside of work I have to say I really despise non-x86 platforms and ARM in particular for how fragmented they are and their vendors’ utter disregard for any form of standardization at the platform, firmware, or peripheral levels. That’s why I’m really thankful that devices like these exist and are affordable.
Single board computers have GPIO and interfaces like SPI and I2C. They also tend to have lower power consumption and can run from 5 volts. If you want to interface with low level hardware or run from batteries, the SBC will usually be the better choice.
If you’re interested in home automation, I think that there’s a reasonable argument for running it on separate hardware. Not much by way of hardware requirements, but you don’t want to take it down, especially if it’s doing things like lighting control.
Same sort of idea for some data-logging systems, like weather stations or ADS-B receivers.
Other than that, though, I’d probably avoid running an extra system just because I have hardware. More power usage, heat, and maintenance.
EDIT: Maybe hook it up to a power management device, if you don’t have that set up, so that you can power-cycle your other hardware remotely.
