The Raspberry Pi isn’t the bargain Home Assistant server it used to be


For a long time, a Raspberry Pi was a common suggestion for people looking to set up their first Home Assistant server. While it wasn’t perfect, it was good enough for many setups. Sadly, the Raspberry Pi is no longer the bargain that it once was.

The Pi was a great option for beginners

A Rasbperry Pi in an official Raspberry Pi case next to a Home Assistant sticker. Credit: Adam Davidson/How-To Geek

Not so long ago, if you were to ask on Home Assistant forums what hardware would make a good first Home Assistant server, there was a good chance that someone would recommend a Raspberry Pi. The official Home Assistant installation guide still has the Raspberry Pi as one of the listed DIY options.

There are plenty of reasons why the Raspberry Pi used to make sense as a Home Assistant server. You could buy one for around $40, so it didn’t feel too painful to dedicate it to the single task of running your smart home. The power draw was low enough that it didn’t matter if you left it running 24/7, and there was a ton of community support if you ever hit any snags.

My first Home Assistant server was a Raspberry Pi 3B+, and it ran my smart home for several years with very few issues. Some Raspberry Pi users had issues with microSD cards failing due to data constantly being written to the card, but mine never hit that issue, and I eventually moved to using an external SSD instead of a microSD card.

raspberry pi 5-1

Brand

Raspberry Pi

Storage

8GB

It’s only recommended for tech-savvy users, but the Raspberry Pi 5 is a tinkerer’s dream. Cheap, highly customizable, and with great onboard specs, it’s a solid base for your next mini PC.


The price of a Raspberry Pi has gone through the roof

Memory prices are mostly to blame

Raspberry Pi 5 on a blue and orange hexagon background. Credit: Raspberry Pi

Unfortunately, the Raspberry Pi is no longer the easy recommendation that it once was. It’s still a low-power device, and there’s plenty of community support if you need it. What’s changed is the price. The Raspberry Pi can no longer be considered a low-cost option.

The current retail prices are now much higher than the original launch prices. A 4GB Raspberry Pi 5, which is a reasonable baseline for a typical Home Assistant setup, is currently around $110, while the 8GB model, which can run heavy add-ons such as InfluxDB, is around $175. The 16GB model can cost more than $300, which sounds insane for a supposedly low-cost single-board computer.

You can opt for a model with less RAM, with the 2GB model costing around $65 and the 1GB model around $45. However, Home Assistant’s own Raspberry Pi guide suggests 2GB as the minimum requirement, and even then, you may struggle to use add-ons such as ESPHome.


Close-up of RAM module on U.S. dollar bills: highlighting the cost of technology components.


RAM prices have doubled, here’s my plan to survive the ‘RAM-pocalypse’

Some of us have rather short memories…

These weren’t always the prices of the Raspberry Pi models. When the Raspberry Pi 5 first launched in 2023, the 4GB model cost around $60, and the 8GB model cost around $80, so the prices have essentially doubled.

There are several reasons why this is the case. The cost of RAM has skyrocketed as AI server demand has consumed much of the supply of memory, so it’s far more expensive to produce an 8GB Raspberry Pi than it used to be. Raspberry Pi Holdings also went public in June 2024, and now has to answer to shareholders who are expecting returns on their investments.

The full cost of a Raspberry Pi Home Assistant setup

You need more than just a Pi

A Raspberry Pi 5 in a 3D pritned case compatible with active coolers. Credit: Sydney Louw Butler/How-To Geek

If you want to set up a Home Assistant server, the Raspberry Pi isn’t all you’ll need. In practice, you’ll also want a case, a power supply, and an SSD rather than relying on a microSD card. You may also want to add a Zigbee dongle and active cooling, too. You can easily spend more than $200 even with a 4GB Raspberry Pi.

It’s not really accurate to call the Raspberry Pi a “low-cost” option for a Home Assistant server when you need to spend upward of $200 to run one. The reality is that there are better options for the same price, and alternative options that can do the job for far less.

Better options are available for the same money

You can get a lot more bang for your buck

A Raspberry Pi used to be a good choice for a Home Assistant server because it was cheap enough that it didn’t matter that you were only using it for one dedicated purpose. If you’re going to spend $200 or more, however, then you want a device that can do more.

A mini PC is a more sensible option. You can currently buy a Beelink Mini S12 for under $300 from some retailers and use it to run multiple services. For example, I use the Proxmox virtualization software on my mini PC and run a whole host of services, including Home Assistant, Pi-hole, Jellyfin, Uptime Kuma, n8n, budgeting software, and more.

If you’re not planning to run other services, you can get a Home Assistant Green for under $200. This is a dedicated Home Assistant server and is as close to a plug-and-play option for Home Assistant as you will find.

If you’re looking for a cheaper option, you can often find second-hand small form factor (SFF) PCs such as Dell Optiplex on sites such as Facebook Marketplace for under $100. These little powerhouses are great for running other services alongside Home Assistant, too.


The Raspberry Pi is no longer the affordable option

The reign of the Raspberry Pi as the Home Assistant server hardware of choice is sadly coming to an end. At current prices, it no longer makes financial sense. Your best bet is to consider something else.



Source link

Leave a Reply

Subscribe to Our Newsletter

Get our latest articles delivered straight to your inbox. No spam, we promise.

Recent Reviews


The Samsung Keyboard supports glide typing, voice dictation, multiple languages, and deep customization through Good Lock. On paper, it’s a very capable and perfectly functional keyboard. However, it’s only when I started using it that I realized great features don’t necessarily translate to a great user experience. Here’s every problem I faced with the Samsung Keyboard, and why I’m permanently sticking with Gboard as my main Android keyboard.

I have been using Gboard and the Samsung Keyboard on a recently bought Galaxy S24, which I got at a massive discount.

Google’s voice typing doesn’t cut me off mid-sentence

Fewer corrections, fewer cutoffs, faster dictation

I might be a professional writer, but I hate typing—whether it’s on a physical keyboard or a virtual one. I type slower than I think, which I suspect is true for most people. That becomes a problem when I have multiple ideas in my head and need to get them down fast. It’s happened far too often: I start typing one idea and forget the other. Since jacking my brain into a computer isn’t an option (yet), I’ve been leaning more and more on voice typing as the fastest way to capture my thoughts.

Now, both Samsung Keyboard and Gboard support voice typing, but I’ve noticed that Gboard with Google’s voice engine is just better at transcription accuracy. It picks up on accents flawlessly and manages to output the right words. In my experience, it also seems to have a more up-to-date dictionary. When I mention a proper noun—something recently trending like a video game or a movie name—Samsung’s voice typing fails to catch it, but Google nails it.

That said, you can choose Google as your preferred voice typing engine inside Samsung Keyboard, but it’s a buggy experience. I’ve noticed that the transcription gets cut off while I’m in the middle of talking—even when I haven’t taken a long pause. This can be a real problem when I’m transcribing hands-free.

Gboard offers a more accurate glide typing experience

Google accurately maps my swipe gestures to the right words

Voice typing isn’t always possible, especially when you’re in a crowded place and want to be respectful (or secretive). At times like these, I settle for glide (or swipe) typing. It’s generally much faster than tapping on the keyboard—provided the prediction engine maps your gestures to the right word. If it doesn’t, you have to delete that word, draw that gesture again, or worse—type it out manually.

Now, both Samsung Keyboard and Gboard support glide typing, but I’ve noticed Gboard is far more accurate. That said, when I researched this online, I found a 50-50 divide—some people say Gboard is more accurate, others say Samsung is. I do have a theory on why this happens.

Before my Galaxy S24, I used a Pixel 6a, before that a Xiaomi, and before that a Nokia 6.1 Plus. All of my past smartphones came with Gboard by default. I believe Gboard learned my typing patterns over time—what word correlates to what gesture, which corrections I accept, and which ones I reject. After a decade of building up that prediction model, Gboard knows what I mean when my thumb traces a particular shape. Samsung Keyboard, on the other hand, is starting from zero on this Galaxy S24—leading to all the prediction errors. At least that’s my working theory.

There’s also the argument for muscle memory. While glide typing, you need to hit all the correct keycaps for the prediction engine to work. If you’re even off by a slight amount, the prediction model might think you meant to hit “S” instead of “W.” Now, because of my years of typing on Gboard, it’s likely that my muscle memory is optimized for its specific layout and has trouble adapting to Samsung’s.

Swiping vs typing.


Is Swiping Really Faster Than Typing on a Phone Keyboard?

Which typing method reigns supreme?

I mix three languages in one message, and Gboard just gets it

Predictive multilingual typing doesn’t get any better than this

I’m trilingual—I speak English, Hindi, and Bengali. When I’m messaging my friends and family, we’re basically code-mixing—jumping between languages in the same sentence using the Latin alphabet. Now, my friends and I have noticed that Gboard handles code-mixing much more seamlessly than Samsung Keyboard.

If you just have the English dictionary enabled, neither keyboard can guess that you’re trying to transliterate a different language into English. It’ll always try to autocorrect everything, which breaks the flow. The only way to fix this is by downloading a transliteration dictionary like Hinglish (Hindi + English) or Bangla (Latin). Both Samsung Keyboard and Gboard support these dictionaries, but the problem with Samsung Keyboard is that it can only use one dictionary at a time.

Let’s say I’m writing something in Latinized Bangla and suddenly drop a Hindi phrase. Samsung Keyboard will attempt to autocorrect those Hindi words. Gboard is more context-aware. Since my Hinglish keyboard is already installed, I don’t have to manually switch to it. Gboard can detect that I’m using a Hindi word even with the English or Bangla keyboard enabled, and it won’t try to autocorrect what I’m writing. This also works flawlessly with glide typing, which is a huge quality-of-life improvement over Samsung Keyboard.

This isn’t just an India-specific thing either. Code-mixing is how billions of people type every day—Spanglish in the US, Taglish in the Philippines, Franglais across parts of Europe and Africa.

Gboard looks good without me spending an hour on it

I don’t have time for manual customization

Samsung Keyboard is hands down the more customizable option, especially if you combine it with the Keys Cafe module inside Good Lock. You get granular control over almost every aspect of the keyboard—key colors, keycaps, gesture animations, and a whole lot more. While for some users, this is heaven, I just find it too overcomplicated and a massive time sink.

I don’t have the patience to sit and adjust every visual detail of my keyboard. Sure, it gets stale after a while, and you’d want to freshen it up, but I don’t want to spend the better part of an hour tweaking a virtual keyboard. This is where Gboard wins (at least for me) by doing less.

Android 16 brings Material 3 Expressive, which automatically themes your system apps using your wallpaper’s color scheme. With Gboard, all you have to do is change the wallpaper, and the keyboard updates to match—no Good Lock, no manual color picking. It’s a cleaner, more seamless way to keep your phone looking good without putting in the extra legwork.


The keyboard you don’t think about is the one that’s working

I didn’t switch to Gboard because Samsung Keyboard was broken. I switched because Gboard made typing feel effortless. If you’re a Samsung user who’s never tried it, it’s a free download and a five-second switch. You might not go back either.

Pixel 7 with the 8vim keyboard.


I Tried the Weirdest Android Keyboards So You Don’t Have To

Can strange layouts and gestures beat the good old-fashioned QWERTY?



Source link