this post was submitted on 06 Feb 2026
87 points (97.8% liked)

Selfhosted

56402 readers
971 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:

  1. Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.

  4. Don't duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

  7. No low-effort posts. This is subjective and will largely be determined by the community member reports.

Resources:

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

Questions? DM the mods!

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