this post was submitted on 06 Feb 2026
95 points (98.0% liked)

Selfhosted

60911 readers
1138 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules:

Detailed Rules Post

  1. Be civil.

  2. No spam.

  3. Posts are to be related to self-hosting.

  4. Don't duplicate the full text of your blog or readme if you're providing a link.

  5. Submission headline should match the article title.

  6. No trolling.

  7. Promotion posts require active participation, with an account that is at least 30 days old. F/LOSS without a paywall has exceptions, with requirements. See the rules link for details. Tags [CBH] or [AIP] are required, see the links in Rule 8 for details.

  8. AI-related discussions and AI-involved promotional posts have additional requirements for tagging, as noted in Rule 7 and the AI & Promotional Post Expanded Rules post, and find example disclosures here.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 3 years ago
MODERATORS
 

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?

you are viewing a single comment's thread
view the rest of the comments
[–] jaxxed@lemmy.world 1 points 5 months ago (1 children)

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

I only use zigbee, but would consider branching out

[–] AA5B@lemmy.world 2 points 5 months ago* (last edited 5 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