this post was submitted on 09 Jul 2025
246 points (99.6% liked)

homeassistant

15339 readers
19 users here now

Home Assistant is open source home automation that puts local control and privacy first.
Powered by a worldwide community of tinkerers and DIY enthusiasts.

Home Assistant can be self-installed on ProxMox, Raspberry Pi, or even purchased pre-installed: Home Assistant: Installation

Discussion of Home-Assistant adjacent topics is absolutely fine, within reason.
If you're not sure, DM @GreatAlbatross@feddit.uk

founded 2 years ago
MODERATORS
top 50 comments
sorted by: hot top controversial new old
[–] Zagorath@aussie.zone 61 points 1 week ago (4 children)

Man there are way too many IoT standards. What's the difference between these two? How do they each compare to Matter?

[–] paraphrand@lemmy.world 64 points 1 week ago* (last edited 1 week ago) (1 children)

Thread is a wireless standard meant to sit next to Bluetooth and WiFi.

Matter is a home automation protocol can that be used over Thread or WiFi. Ideal Matter devices use Thread instead of WiFi because running a bunch of home devices like light bulbs or switches on your WiFi is a recipe for disaster.

Matter is important because it provides native compatibility among different platforms.

[–] VitulusAureus@lemmy.world 7 points 1 week ago (6 children)

What kind of disaster specifically? I hear everyone discouraging from using WiFi for home devices, but never understood what the actual risks are.

[–] spitfire@lemmy.world 2 points 4 days ago

There are also performance implications (a Zigbee coordinator can easily handle 100 devices, while many routers would struggle with that amount of clients), power saving (especially for battery powered sensors) - some Zigbee sensors can last years on a single coin cell battery.

[–] GamingChairModel@lemmy.world 3 points 6 days ago

Thread is a bit more power efficient, which matters for battery powered devices that aren't connected to permanent power and don't need to transmit significant data, like door locks, temperature/humidity sensors, things like that. A full wifi networking chip would consume a lot more power for an always-on device.

[–] AtariDump@lemmy.world 21 points 1 week ago (19 children)

Let’s say your lightbulb(s) become comprised. A bad actor now has a toehold into your network.

Maybe they run a spam relay through the bulb. Maybe they attack your network by attacking the printer that hasn’t had a firmware update in years.

Point is, there’s someone with access to your network that isn’t you.

https://old.reddit.com/r/Ubiquiti/comments/1fjspoc/what_is_the_point_of_having_a_separate_devices/

load more comments (19 replies)
[–] paraphrand@lemmy.world 12 points 1 week ago* (last edited 1 week ago) (6 children)

I see someone replied about security. But I was just taking about stability.

Most people don’t have super beefy wifi routers. Many have whatever shit their ISP sent them. These are fine for your average number of laptops and phones, etc. but if you then throw on 10 more 2.4GHz WiFi IOT devices, you are probally going to run into devices randomly dropping off the wifi, etc.

Additionally, wifi is usually chosen over other protocols by manufacturers due to the cost of hardware and development. So they are often lower quality. (This is only one reason)

But sure, if you have a super awesome 2.4GHz wifi setup and high quality wifi devices, maybe things will work out just fine. But my personal experience with WiFi tells me I shouldn’t clutter my WiFi.

Also, if you were curious, yes: almost all WiFi IOT devices are 2.4GHz only.

load more comments (6 replies)
load more comments (2 replies)
[–] Ptsf@lemmy.world 28 points 1 week ago* (last edited 1 week ago) (3 children)

An important difference between thread and zigbee/wi-fi I'm not seeing mentioned is that all thread devices automesh in a hub/spoke model as long as they're not battery powered. So your light bulbs, plugs, etc all become extenders and part of a self healing mesh network without a single point of failure. For me it works better than Zigbee for this reason.

[–] monogram@feddit.nl 45 points 1 week ago (1 children)

Zigbee does that too tho, right?

The wiki on zigbee says so at least

[–] KairuByte@lemmy.dbzer0.com 11 points 1 week ago (1 children)

Pretty sure than an underlying feature of both zigbee and zwave.

[–] Ptsf@lemmy.world 17 points 1 week ago* (last edited 1 week ago)

They're different in their implementation. Zigbee automesh is more of a centralized router-hub model with self healing relying on routing tables. This caused significant issues for me. Thread is true automesh with all devices acting as a hub in a hub/spoke model, so there's no centralized routing table to act as a single point of failure.

[–] CosmicTurtle0@lemmy.dbzer0.com 16 points 1 week ago

I exclusively use ZigBee. It automeshes.

[–] oppy1984@lemdro.id 10 points 1 week ago

Thread also works on the 2.4 GHz range but can utilize sub ranges of 868 in Europe and 915 in north America. The 868 and 915 GHz ranges are what LoRa operates on and provides a much greater range for low data rate transmissions.

In fact Meshtastic operates on LoRa on 915 here in the U.S. and I have a node in my second floor window with a 3db antenna and I have been able to message both ways up to 3 blocks away.

Long story short, utilizing 868 and 915 in these devices will make dead spots a thing of the past within a home, even with their lower gain internal antennas.

[–] elgordino@fedia.io 26 points 1 week ago

Thread is a network layer thing, comparable to WiFi or Bluetooth. Matter is an application later thing, comparable to HomeKit or Google home.

Zigbee is both network and application layer.

This article has a decent overview https://www.smarthomeperfected.com/zigbee-vs-thread/

load more comments (1 replies)
[–] arschflugkoerper@feddit.org 32 points 1 week ago (13 children)

I am pretty happy with zigbee so far. Is that a good thing? I haven‘t done anything with matter so far.

[–] Telodzrum@lemmy.world 24 points 1 week ago

It's just a technological step forward. Thread was designed from the ground up as an IPv6 protocol. Honestly, this kind of move is coming later than would have been ideal, given the massive growth in IoT devices.

[–] ThePantser@sh.itjust.works 14 points 1 week ago (1 children)

Yeah so far it doesn't matter because zigbee and zwave still work fine.

load more comments (1 replies)
[–] Guenther_Amanita@slrpnk.net 11 points 1 week ago (3 children)

@arschflugkoerper@feddit.org I have nothing useful to contribute, but I fucking love your username. Thank you for the smirk you gave me, have a nice evening mein Genosse 👋

load more comments (3 replies)
load more comments (10 replies)
[–] vaionko@sopuli.xyz 17 points 1 week ago (3 children)

Crap. I use pretty much exclusively Ikea stuff with my Home Assistant

load more comments (3 replies)
[–] ikidd@lemmy.world 16 points 1 week ago (2 children)

It makes sense. Hopefully it's more reliable than my Zigbee devices. I constantly have to power cycle devices made by a variety of manufacturers to get them to register again. And I've tried more than a few zigbee hubs. Can't say I'm a fan.

[–] Tja@programming.dev 9 points 1 week ago (1 children)

Check interference with wifi signals wifi on channel 1 and zigbee on channel 25 gives you the most separation. As long as a neighbor doesn't blast on wifi channel 11.

There is also software compatibility, I found hue to be the most stable for routers. Osram was terrible, recent firmware made it okay.

[–] ikidd@lemmy.world 7 points 1 week ago (2 children)

I'm in literally the middle of nowhere, the next nearest house is 4 miles away and I'm not even connected to the grid. If there's a wifi signal detectable, it'll be mine. So I've shifted frequencies around trying to get it to stabilize, with little luck. I've primarily been using Sonoff, Aqara, Ikea and SMLight, and hubs from each of them.

Honestly, I've been migrating to zwave since I don't seem to have issue with anything I use on that protocol.

load more comments (2 replies)
[–] IanTwenty@lemmy.world 6 points 1 week ago (1 children)

Never had this with ZigBee, one hub lots of different devices. Had to switch hub to USB2 at beginning to reduce interference but after that smooth sailing.

load more comments (1 replies)
[–] shortwavesurfer@lemmy.zip 11 points 1 week ago (1 children)

Isn't the HA cloud dongle able to do both because they're on the same 2.4 gigahertz or whatever?

[–] martini1992@lemmy.ml 14 points 1 week ago (1 children)

The dual stack firmware was deprecated because of issues, I believe.

load more comments (1 replies)
[–] CompactFlax@discuss.tchncs.de 10 points 1 week ago* (last edited 1 week ago) (2 children)

xkcd 927 in action right there.

Zigbee works just fine, but needs a hub to share out devices eg internet access or HomeKit. But it is quick. How thread compares remains to be seen.

[–] paraphrand@lemmy.world 17 points 1 week ago* (last edited 1 week ago) (9 children)

Remains to be seen? What other information are you waiting for?

I’ve been using Thread devices for ~5 years now.

load more comments (9 replies)
[–] Tja@programming.dev 8 points 1 week ago

Thread is basically the same thing, but with a different upper level layer (IP), lower lever is still 802.15.4

[–] elucubra@sopuli.xyz 6 points 1 week ago (8 children)

So, if I'm invested in zigbee, but want to future proof, I should consider threads/matter, and a hub that talks to both?

Can home assistant do that?

load more comments (8 replies)
load more comments
view more: next ›