I'm planning to build several WiFi connected devices for home automation: an AC remote control and air quality sensors. These devices would send data and be controlled through a local server. I'm considering two approaches: running custom software on a server PC (hardware to be determined) or integrating with Home Assistant's protocols and purchasing their hardware. Would using Home Assistant be excessive for this use case?

all 52 comments

sorted by: hot top controversial new old
[–] 55 points 9 months ago* (15 children)

In terms of software, yes. But HA can be run on nearly anything—there’s no need to buy their hardware to use it.

  • source
  • hideshow 15 child comments
  • [–] 17 points 9 months ago (7 children)

    Adding to this, I recommend a used mini PC. There's lots of cheap used office hardware out there on eBay that is more powerful, more serviceable, and more flexible than the hardware they sell or a raspberry pi.

  • source
  • parent
  • hideshow 7 child comments
  • [–] 12 points 9 months ago

    Companies are throwing away old hardware (like 8th/9th gen Core i5) that's perfect for running Home Assistant. See if there's an e-waste recycler near you - they might let you buy an old system for a nominal fee.

  • source
  • parent
  • [–] 2 points 9 months ago (5 children)

    While there are some problems with used minipcs (notably drivers), i don't think they are relevant if it is only going to be used as a Home Assistant

  • source
  • parent
  • hideshow 5 child comments
  • [–] [S] 2 points 9 months ago (4 children)

    That's a good point. This can help me with things like adding a DNS server (I'm assuming pi-hole can be run standalone on a mini PC)

  • source
  • parent
  • hideshow 4 child comments
  • [–] 4 points 9 months ago

    If you're going to run Home Assistant OS you'd be able to run anything that can run in docker. Some things are available to install directly inside the Home Assistant apps system, otherwise you can install portainer and run any docker capable software.

  • source
  • parent
  • [–] 16 points 9 months ago (5 children)

    Just be careful with SD cards if you're using SBCs. Home Assistant does a lot of writing and if your SD card can't handle repeated writes you may suddenly lose everything. Keep backups to another device and have a replacement SD card ready if extended downtime is going to be a problem for you.

  • source
  • parent
  • hideshow 5 child comments
  • [–] 1 point 9 months ago (2 children)

    Always run mine in a VM along with everything else, no need for special hardware.

    Get yourself a PoE Zigbee and/or Z-wave receiver and you are good to go, can even live migrate HA if you are fancy

  • source
  • parent
  • hideshow 2 child comments
  • [–] 49 points 9 months ago (10 children)

    If you aren't locked in yet, I'd recommend against WiFi devices. Check Zigbee or similar. It won't clutter your LAN and is independent. You usually need some kind of central station for that but it's worth it imho.

  • source
  • hideshow 10 child comments
  • [–] 12 points 9 months ago (1 child)

    The exception here would be ESP32 devices. These have been some of the most reliable devices in my home and the most versatile, no Internet access required. Zigbee works well, but runs in the same frequency space as wifi and Bluetooth. Matter and thread are the new hotness and run in that space too. They all work well together, but something to consider. Z Wave is in a separate frequency space, but is a less open protocol. I have at least a few of all of these and they all play nice. Consider your priorities and choose what's best for your application.

  • source
  • parent
  • hideshow 1 child comment
  • [–] [S] 3 points 9 months ago (6 children)

    Will do. Is it more for security purposes? Reliability?

  • source
  • parent
  • hideshow 6 child comments
  • [–] 9 points 9 months ago (2 children)

    Both! Connecting Iot devices to your LAN is a security risk, since they sometimes carry malware. Many DDOS these days are performed by smart bulbs or the like. May even sniff in your network. Of course you can firewall them, but why bother with wifi at all then? Zigbee is pretty reliable and works even if your router goes down (you probably can't access Home Assistant Web interface anymore, but zigbee light switches etc will still trigger zigbee bulbs, zigbee thermeters will still report their sensor values etc).

    I'm a Zigbee user so I use that in the examples but I'm sure the other options are fine as well.

  • source
  • parent
  • hideshow 2 child comments
  • [–] [S] 4 points 9 months ago (1 child)

    Thank you for the info! I'm guessing that I could use a mini PC with a zigbee adapter to create my own dashboards or bridge to home assistant, unless zigbee hubs offer similar capabilities

  • source
  • parent
  • hideshow 1 child comment
  • [–] 3 points 9 months ago

    Home Assistant has a great integration, ZHA, which "drives" the Zigbee device. So having the Zigbee dongle on the machine HA runs on is very common. In my case it's a raspberry with a RaspBee dongle but every MINI PC will do. Recommended devices: https://www.home-assistant.io/integrations/zha#recommended-zigbee-radio-adapters-and-modules

    The other common setup is using Zigbee2MQTT which allows different devices that communicate over LAN. it's been the go to recommendation as it has some compatibility improvements for devices that don't properly follow the Zigbee standard. ZHA is keeping up though and is natively supported by home assistant. I'm using ZHA and check for compatibility before buying devices.

    You can theoretically switch later, but you'll have to reconnect all devices which can be a hassle.

  • source
  • parent
  • [–] 7 points 9 months ago

    Most wi-fi smart devices use cheap components and will often drop off the network for seemingly no reason. As long as you do some basic planning, Zigbee and Z-Wave are pretty solid. There are some folks here who will say one or both of these technologies are on their way out because Matter & Thread. I’m not sure I agree with them, but even so, HA supports Matter, so… when Thread devices become as ubiquitous as Zigbee & Z-Wave devices, you can replace them as they die.

  • source
  • parent
  • [–] 7 points 9 months ago (1 child)

    Most WiFi devices these days are cloud-based, at least on the American market.

    If you can find a Zigbee or Z-Wave (or the up-and-coming Thread), those only work locally. The only way to get remote control is to expose HomeAssistant (or a similar hub) to the internet - usually using a VPN from your remote devices into your network.

    It’s a bit more upfront work, but no one can track your devices, they’re off grid/much harder to hack remotely, etc.

  • source
  • parent
  • hideshow 1 child comment
  • [–] [S] 3 points 9 months ago

    I'm planning on assembling and coding w/e needs coding on microcontrollers, and a mini PC/HA hardware won't be connected to the cloud. But generally speaking yes: most IoT devices in the US connect to someone else's computer these daya

  • source
  • parent
  • [–] 24 points 9 months ago

    As others have said, you can run Home Assistant on anything if you want to just test it out. Their own hardware is a great choice though.

    But to answer your broader question, yes. Home Assistant is the choice. It works better with literally everything else out there.

  • source
  • [–] 21 points 9 months ago*

    HA isn't the only option. I think there's two other open source smarthome solutions out there(?) And you could probably do with just an MQTT broker and a Python script, or something like that...

    But HA isn't a bad choice. They're doing a phenomenal job. And related projects like ESPHome make it really easy to integrate microcontrollers. And if you want to do more smarthome stuff, it has a plethora of features, integrations, an app...

    Extra hardware isn't absolutely necessary. I have one server at home which does NAS, and I use 4GB of it's RAM to run a virtual machine with Home Assistant. That's enough for it, including a bunch of Addons.

  • source
  • [–] 8 points 9 months ago (5 children)

    HA will connect to almost anything, maybe there is a connector for your AC unit and there are many air quality sensors

  • source
  • hideshow 5 child comments
  • [–] [S] 1 point 9 months ago (4 children)

    My AC is offline, I was thinking I'd just put an infra red LED on a microcontroller in front of it 😅

  • source
  • parent
  • hideshow 4 child comments
  • [–] 4 points 9 months ago*

    Even if you build your own thing to communicate with the AC, Home Assistant is still useful since it lets you easily automate things and interact with other devices, and you get a bunch of things included (nice UI, storage of historical data, dashboards, etc). You could build your thing as a Home Assistant integration.

  • source
  • parent
  • [–] 2 points 9 months ago (1 child)

    That might depends on how your AC is working, I recently did the same at my dad's house and run into issues because the temp control for the unit is reading from the remote. So when I sent infrared command to turn off unit, it worked as expected for some minutes then turned back on because remote sent back command as temp wasn't meet. Still need to do a lot of testing to find a way to make it work, might need to disable remote and use some temp sensors for the triggering part but not sure how that will work, might need to use some hysterisis friendly climate addon for that...

  • source
  • parent
  • hideshow 1 child comment
  • [–] 6 points 9 months ago

    I would suggest to go with home assistant. I have been running it for couple of years now and I am very happy.

    I would also suggest to purchase a Home Assistant Green. While not needed, you can self install on a Pi or a standard pc, it's a small price to support the project and the Green is a nice solid and super stable piece of hardware, I am very happy with it after using first an old laptop, and then a Pi. The green is a clear upgrade from both.

  • source
  • [–] 6 points 9 months ago (2 children)

    I don't run a home automation system, but if you want an open solution and are willing to do some configuration, my understanding is that the main contenders are OpenHAB and Home Assistant.

    I'd also suggest !homeautomation@lemmy.world as a more-specialized resource than !selfhosted@lemmy.world, though I imagine that there's overlap.

  • source
  • hideshow 2 child comments
  • [–] [S] 2 points 9 months ago (1 child)

    Thanks. I thought the already thought out protocols and configurations would make it easier to program the micro controllers to plug in with that rather than building something on my own

  • source
  • parent
  • hideshow 1 child comment
  • [–] 4 points 9 months ago

    It's been a while since I messed with home automation, but ESPHome was amazing to program ESP microcontrollers (i.e. you most likely wouldn't have to write any code). You can use ESPHome devices with both Home Assistant and Openhab (using MQTT, IIRC). The last I checked, it was easier to program your own functionality in OpenHAB than Home Assistant.

  • source
  • parent
  • [–] 6 points 9 months ago

    HA is definitely the largest adopted. OpenHab is probably more geared for developers, but has a more concise and powerful automation system.

    As for hardware to run it on: get a cheap n100 Minipc and be done with it. Uses 6-12W, and it's going to miles.kore efficient for this use than a regular PC.

  • source
  • [–] 5 points 9 months ago (1 child)

    Yes. If there’s another open source project that has the coverage I’m not aware of it.

  • source
  • hideshow 1 child comment
  • [–] 8 points 9 months ago (2 children)

    I’ll also vote to reconsider WiFi. Home Assistant supports a variety of local mesh networks that by default can’t connect to the cloud and whose devices are cheaper and lower power.

    I use all three of zwave, Zigbee, and thread; ha works with whatever you need.

  • source
  • hideshow 2 child comments
  • [–] 1 point 9 months ago (1 child)

    Can you comment further on the three mesh networks rhat you use?

    I only use zigbee, but would consider branching out

  • source
  • parent
  • hideshow 1 child comment
  • [–] 2 points 9 months ago* (last edited 9 months ago)

    I got into each mesh technology for specific devices. Home Assistant supports them all and they seem to coexist just fine in my use case.

    I have a small to medium setup with only a few simple automations and a focus on voice control and scheduling

    Preference

    • Thread - given Apple, Amazon, and Google support and the standardization work, I expect this to be the future. Eventually. But I’m getting impatient. If I’m buying a device, I prefer Thread but usually it’s not yet
    • z-Wave - my first, and most devices. Basically this was what was most available at local stores when I started. No complaints
    • Zigbee - by far the biggest selection of simple, cheap sensors. I need to more of those
    • all too much is WiFi but I try to avoid

    But it also helps that my approach is generally switches and outlets. Hard-wired, predictable network, tend to be repeaters. I have comparatively fewer leaf nodes.

    This approach also fits in with my biggest challenge. While my house is small, it’s an older one with dense materials that blocks a lot of radio signals. For example I have no cell phone reception inside yet strong signal just out any door. My focus on switches and outlets overcome this with a repeater in every room

    So for example a few years back I got a z-wave IR blaster to control a mini-split AC because at the time I mostly used z-wave. I already had a z-wave light switch in the same room, acting as a repeater, so no worries about connectivity. Now I have both z-wave and Zigbee light switches in that room so expect both meshes to be strong for any future devices in that room

  • source
  • parent
  • [–] 4 points 9 months ago

    @Trilogy3452 #HomeAssistant on the server, #ESPHome on the sensors.

  • source
  • [–] 2 points 9 months ago

    I've tried Domoticz when my Pi was too old for HA, before upgrading to HA. It was good enough to control only a few devices.

  • source
  • [–] 3 points 9 months ago*

    you are Apple-centric:homebridge

    There’s a mix: homebridge

    You are out of mood stabilizers: arduino and an ESP32

  • source
  • [–] [B] 1 point 9 months ago* (last edited 9 months ago)

    Acronyms, initialisms, abbreviations, contractions, and other phrases which expand to something larger, that I've seen in this thread:

    Fewer Letters More Letters
    DNS Domain Name Service/System
    HA Home Assistant automation software
    ~ High Availability
    IoT Internet of Things for device controllers
    MQTT Message Queue Telemetry Transport point-to-point networking
    NAS Network-Attached Storage
    PiHole Network-wide ad-blocker (DNS sinkhole)
    PoE Power over Ethernet
    SSD Solid State Drive mass storage
    VPN Virtual Private Network
    Zigbee Wireless mesh network for low-power devices

    10 acronyms in this thread; the most compressed thread commented on today has 15 acronyms.

    [Thread #65 for this comm, first seen 6th Feb 2026, 21:20] [FAQ] [Full list] [Contact] [Source code]

  • source
  • [–] -2 points 9 months ago (2 children)

    Before HomeAssistant, OpenHab was the undisputed king. I still like them because they let you remotely access you home without having to subscribe to anything or set up any remote access methods

  • source
  • hideshow 2 child comments
  • [–] 2 points 9 months ago*

    I choose to pay for remote access, but it’s for convenience and to support the developers. You are free to configure it yourself in a couple ways (and there is decent documentation) or do without remote access

    I don’t know how you set up remote access for OpenHab, but from a quick glance at the web site it looks similar

  • source
  • parent