This sucks. Matter is a closed ecosystem, enforced using a public key infrastructure (PKI) and device attestation certificates. Thread seems to require paying royalties if you want to ship devices. It’s disappointing that IKEA claims that this move is towards a more open ecosystem.<p>On top of that, the switch breaks compatibility with existing hardware (except for the Touchlink functionality). If you have a bunch of Zigbee devices, but at some point want to add some of the new ones, you need to start thinking about replacing all the perfectly working Zigbee devices or have a fragmented network.
> If you have a bunch of Zigbee devices, but at some point want to add some of the new ones, you need to start thinking about replacing all the perfectly working Zigbee devices or have a fragmented network.<p>Yes, if you're using the manufacturer's half-assed smartphone app, but if you're on Home Assistant, like basically anyone who's serious about their smart home, having multiple kinds of smart devices isn't really a problem. It's just one more radio to configure. Some people run both Zigbee and Zwave, some people run Zigbee + Wi-Fi or even Zigbee + Zwave + Wi-Fi + cloud integrations, Home Assistant doesn't care.
It is still somewhat annoying for those of us with solid walls.<p>I can't just add a new Thread device at the other side of my house as the walls attenuate the signal between it and the border router. Equally I can't start replacing Zigbee devices willy-nilly in case I create Zigbee dead zones.<p>Not the biggest problem in the world but it does mean I'll likely need to get some pointless Thread smart plugs as temporary network extenders when I add my first Thread device.
Perhaps I never put enough effort into it, but I've slowly coalesced on <i>only</i> having IKEA smart home products after years of acquiring piecemeal stuff and trying to wire it together with Home Assistant. I've shut down HA, and with every non-IKEA "smart" thing I have nowadays I just use the manufacturer's app (though I've become pretty sour on most smart devices overall and avoid them when possible).<p>I didn't really care for the way it became a sysadmin job where the stakes of a bad update or me not reading some release notes were that my light switches didn't work until I sat there and futzed around with it. I'm a programmer, enjoy Linux admin, run a whole bunch of servers....but having to dive into logs and YAML configs because the lights in my kitchen won't turn off is just not ideal. Similar issues with HomeKit, except when things mysteriously stop working there's even less ability to diagnose, given Apple's design principles that everything "just works", so apparently providing detailed error messages or diagnostics is gauche.
Home Assistant "just works". Yes it has a ton of knobs, but in the 3 years I've been running it, it's had no issues. Certain manufacturer devices being flaky, yes, but as a platform, it's been rock solid. I've not touched its config in over a year and everything works as it should.
I guess the fact that some manufacturer integrations are flaky is hard to reconcile for me as far as the promise of "having multiple kinds of smart devices isn't really a problem". Regardless of whose <i>fault</i> it is, those flaky devices contribute to a less stable system.<p>It's been a bit since I was operating it, but I did at times certainly have issues with updates—perhaps just individual plugins or system updates that created an issue, either way, still a situation where I had to sit at a terminal and debug. I only ever ran the Docker version, not the OS, so perhaps this is less problematic in a more completely controlled stack.<p>I don't think I'm alone in this view, broadly speaking: <a href="https://www.reddit.com/r/homeautomation/comments/18hvl3b/i_give_up_on_home_assistant_i_just_cant_make_it/" rel="nofollow">https://www.reddit.com/r/homeautomation/comments/18hvl3b/i_g...</a>
For my flaky devices, it it not a manufacturer integration, but over Zigbee. It's definitely the device as my other Zigbee devices are solid. Others have reported issues with the device in question (Aqara Temperature and Humidity Sensor)<p>I ran the docker version on a QNAP for a long time, now on a Home Assistant Green.
I second that. Home Assistant "just works". I have had it running on this cheap used HP EliteDesk 705 G3 Mini Desktop for more than 4 years now without a hiccup and barely any maintenance or hygeing work on it. Just sitting in my tv stand and doing it's work.<p><a href="https://homeautomation.substack.com/p/setting-up-home-assistant-on-a-refurbished" rel="nofollow">https://homeautomation.substack.com/p/setting-up-home-assist...</a>
> Certain manufacturer devices being flaky, yes, but as a platform<p>This makes me a little weary of your comment. I don't think I'd really care if my lights not working was due to a "manufacturer being flaky" if they worked yesterday, but don't today.<p>Are you talking about devices being flaky on first setup (which sucks, but is understandable), or are you talking about them being flaky after an update?
I have several Aqara temp/humidity sensors that intermittently lose connection. They don't affect the operation/stability of the rest of the HA platform and is not a problem with HA, as my other zigbee devices that report the same data work fine.<p>I should probably just remove them, but I don't have any automations that depend on them.
I think one solid way of handling the instability is to use high quality light automation (Lutron Caseta, for example) for the things you'll really notice, but for stuff you care less about (for me that's cameras, temperature sensors) you can use cheaper ZWave stuff w/ home assistant. The lights turn on and off when I expect, but temperature might update a little less frequently if HA is flaky.
If I had to guess, they're probably referring to the way that certain devices broadcast their APIs to external services. A lot of them have no intention of allowing open access to APIs (e.g., my mini-split controller requires a slight hack to get it connected to HA).<p>That is, the flakiness isn't due to HA updates breaking connections or an unstable server, but rather manufacturers designing closed and/or brittle systems. Try as they might, the HA authors and surrounding community can only do so much for such devices.<p>Also, I believe the word you're looking for is 'wary' (as in, to be skeptical or suspicious), not 'weary' (as in, to be tired). :)
It's the devices that is flaky. Some of the shitty bulbs I got don't always turn on in one command but that was true via their own app too. Basically shitty devices aren't magically better via home assistant.
Surprised at your issues with HA. Similarly to others that responded, my setup with HA / zigbee2mqtt and >30 zigbee devices (including some ikea buttons) has been pretty rock solid over many years, including easy migrations from an rpi3 -> rpi4 -> rpi5 (with ssd).<p>Usually when I had some zigbee issue, it was because of a crappy product (eg some wired air sensor that would spam the zigbee network every 1 second with a lot of data), so then I just stop using such devices and before I buy I check compatibility with HA / zigbee2mqtt.
That's exactly the reason I'm hesitant to dive into Home Assistant myself. I want my smart-home devices to Just Work. I want them to be <i>appliances</i>.
The problem I’ve run into is that once you’re running a lot of devices, you inevitably end up with a bunch of automations and logic that can’t really be simplified. With Apple Home/HomeKit, everything Just Works, but having dozens of automation rules and scenes configured in Apple’s low—information-density UI is worse than managing yaml config.
View above is bit outdated. Yes, there was a lot of yaml in the past. Right now you can just install Home Assistant OS and configure it from GUI.
For what it's worth, mine do. Nothing in my HA has ever broken after an update or randomly for some other reason.
I just lived half a year without Philips Hue remote control because it stopped working during an update and I couldn't bother to check why. It was some name change somewhere, might have been an issue with how I set it up, can't even remember. Simple fix but I did have to dive back to the config files.
ZWaveJS used to break frequently for me, but I run an HA container on a Linux box, rather than the HAOS or whatever. I control the updates, and can rollback if things break, so it's not really a problem.
I installed Home Assistant recently and the docs suggest HAOS is the strongly preferred option these days.<p>Something about HAOS uses docker to install and manage extensions, whereas if you run the HA docker container it can't as docker-inside-docker isn't supported (?), and thus some functionality is unavailable (at least at the surface level).
What you’re describing hasn’t happened to me yet with Home Assistant luckily, even after 5+ years of running it. I can’t remember an update ever breaking any of my stuff. I’m running a docker container though so YMMV. Might be different with the other install types.
I use SmartThings and ive never missed with any configs at all. Only ever one single app - smartthings. Ive been extremely happy after dozens of devices.
I just use Ikea's remote because I won't bother to link the light and the rmote through HA and set up scenes. It just works as a remote: on/off/dimmer. I can either pair the thing with the HA ecosystem or the remote, but the remote always works, regardlesif HA is on or not. I have just one set of lights.
I use HA and all my IKEA lamps are zigbee. Raspberry pi obviously doesn't have native zigbee radio support, so I have a USB zigbee antenna. Now this means if I buy any more IKEA lamps, I would need a second antenna, and the new lamps would not integrate into the zigbee mesh network. It really sucks.
Some USB zigbee dongles can be flashed to be "multi-PAN", but my experience is it's currently buggy and I would let them bake that for a bit longer.<p>Alternatively, both Sonoff and Home Assistant do a thread dongle for about $30 that you can use simultaneously with a zigbee one. Plus if you have any of the following, they can be used as a Thread border router: Apple TV, HomePod, Echo G4, Eero 6/7, Nest Hub, Nest Wifi, Google TV Streamer. There's also the OpenThread Border Router which can be used on certain ESP32 hardware (ESP32-S3 for $10 or ESP32-H2 for $6?) but that obviously requires more work.
I'm in the same boat; HA is making a considerable effort, but connectivity is challenging. I was a bit frustrated when I found out that the antennas don't support both Zigbee and Matter simultaneously, despite the claim. You can only support one at a time, so apparently we will need the second antenna.
Yes, but then you have a hard-dependency on HA for inter-network communication, which I try to avoid as much as possible (but I fail to, for a couple of subsystems).
My failure model is:<p>1) no electricity, everything down but fiber, wifi, HA and the doorbell (they run off an UPS)<p>2) internet down: no problem, you just cannot reach the home automation from outside<p>3) Home assistant down: zigbee devices are paired together (like buttons + bulbs) or I have physical zigbee relays controlling dumb bulbs.<p>But, as said, I have some subsystem not fully working when (3) happens, like a zigbee button controlling a tasmota-based fan control.
I consider it a requirement of any smart home that alternative methods need to be available during failures. Simply having other devices around that aren’t smart, like an old fashioned light bulb and physical switch to get you through until you can fix whatever is down. 100% uptime is very difficult for large, well-funded IT companies, so I don’t think it’s reasonable to expect it from these consumer-grade devices.<p>We survived for over 100 years by getting up and flipping a wall switch, so the risk of a few hours without smart features shouldn’t be a showstopper.
Yes and no.<p>Pairing a Matter device takes much longer than pairing a Zigbee device through Z2M in my experience, and the Matter add-on still sometimes needs restarting as it refuses to allow any more devices to pair after a while.<p>But - rather than need a Zigbee dongle (or manufacturer hub) if you've got Apple or Google devices such as HomePods you've got a ready made Thread network as they act as border routers.
HA doesn't care but your radio environment probably does. One of the great strengths of Zigbee is the mesh network - it doesn't matter where in my house I dump something, because all my bulbs are Zigbee repeaters it's going to get a signal and be able to route back to my HA box.<p>If I now get a _single_ Thread/Matter/Zwave device to replace one that's broken, ignoring the cost of a new radio for HA, I have to give very serious thought to where it's going to live vs signal availability as I build out yet another network.<p>tldr: HA is fantastic for coordinating disparate devices, but RF still bites.
zigbee has one great advantage over everything else: it's immune to DHCP and DNS failures and misconfigurations. if you're running a pihole or something, it can break iot devices in random ways if your DHCP server boots after your access points. (don't ask me how I know and the fix was to hard reboot my lights by cycling power in the distribution box. not great, not terrible.)
most people don't want to manage a self-hosted server just for interacting with some smart devices in their home
Agree. It’s a hassle to set up once but then you quickly forget about it.
I don't think that is entirely correct.<p>Just like Apple HomeKit you can add devices that aren't certified. It shows a warning, but apart from that it functions like a normal device (for as far as I can tell).<p>I have been using <a href="https://github.com/t0bst4r/home-assistant-matter-hub">https://github.com/t0bst4r/home-assistant-matter-hub</a> to expose my home assistant devices to Google Home without having to expose my Home Assistant to the cloud.<p>Second, certification is what separates Z-Wave from Zigbee which in my (n=1) experience means less issues in terms of compatibility.<p>Of course, with that GitHub package I shared all of that goes through the window, but who cares? I can clone the code and modify it.
Yeah and matter needs internet access in many cases. It was supposed to be the saviour of open home automation. But in practice it leaves too many strings attached that the manufacturer can take advantage of.<p>And despite it not being open enough for open source enthusiasts, it's also got a bad name with manufacturers. I work for one and I asked why we wouldn't implement matter and thread and it was laughed off because apparently marketing will never give up their own app as a data collection and cross selling vehicle. Of course those are exactly the reasons I don't want this.<p>I didn't even know about the certification that only big players can do and the locked firmware requirements. It's ridiculous. Why were thread and matter hailed as the open revolution when they're exactly the opposite?
Matter doesn't need internet access, it's an entirely local protocol even when you integrate to other vendor ecosystems.<p>Now, something like Google Home might decide to go online to talk to a Google Home Hub device, which is where Google wants to initiate all Matter communication from, but that's a Google thing, not a Matter thing.
>Why were thread and matter hailed as the open revolution when they're exactly the opposite?<p>Subterfuge PR or the subversion of original intention by greed.<p>Also, wasn’t there recent news that thread was being abandoned by manufacturers, even declaring it EOL? Or am I conflating that with something else?
I remember an interview [1] with the Nanoleaf CEO (they switched to Thread over Matter years ahead of everyone else) about why Thread/Matter was so difficult, why everyone else didn't adopt it, and that they're going to wait for Thread to get better before they launch new products with it.<p>On the other hand, I believe all the major Thread Border Router manufacturers (Apple, Google, Amazon, Samsung) have updated their Thread routers or committed to updating their Thread routers to Thread v1.4, which is a pretty major upgrade.<p>[1] <a href="https://matter-smarthome.de/en/interview/nanoleaf-ceo-gimmy-chu-on-thread-problems-in-matter/" rel="nofollow">https://matter-smarthome.de/en/interview/nanoleaf-ceo-gimmy-...</a>
> Why were thread and matter hailed as the open revolution when they're exactly the opposite?<p>Because consumers are lazy and dumb, and do not do any kind of research. They believe what is written on the tin. Why is OpenAI called "open"?
I didn't believe any of the information in this post is correct.
> Matter is a closed ecosystem<p>If "closed" means open to anyone that has their product certified to adhere to the rules, then I'm ok with that.
That's incorrect. Matter is an open standard.<p><a href="https://en.wikipedia.org/wiki/Matter_(standard)" rel="nofollow">https://en.wikipedia.org/wiki/Matter_(standard)</a>
>the ability to commission a finished product into a Matter network in the field mandates certification and membership fees,[15][16] entailing both one-time, recurring, and per-product costs.[17] This is enforced using a public key infrastructure (PKI) and so-called device attestation certificates.[15]<p>Thank you for the clarification?
To be clear, this is the same organization that developed Zigbee, which requires paid certification - without, you're not allowed to say the product supports Zigbee or to use the Zigbee logo.<p>You can connect devices without this, it just shows a warning during commissioning that the device is not certified. No impact whatsoever.
Matter is "open" in that it is published. It is not "open" in that you can make a matter device in your basement.<p>Here is the Silabs explainer on the certification process: <a href="https://docs.silabs.com/matter/latest/matter-certification/" rel="nofollow">https://docs.silabs.com/matter/latest/matter-certification/</a>
> <i>It is not "open" in that you can make a matter device in your basement.</i><p>You can! You just can't ship it/sell it without certification.<p><a href="https://www.reddit.com/r/homeassistant/comments/1adh8ah/esp32_c3_running_matter_firmware_connected_to/" rel="nofollow">https://www.reddit.com/r/homeassistant/comments/1adh8ah/esp3...</a>
> It is not "open" in that you can make a matter device in your basement.<p>I did exactly that last week... Certification is required if you want to use the trademarked logo in your marketing materials (same as with Wi-Fi and Bluetooth afaik).
This isn't entirely true, isn't it? I mean, the whole internet runs on a PKI and we need such a mechanism to ensure secure communication across devices in the network.
I understand home devices that contain all sort of sensors and actuators should be handled in a similar fashion, isn't it?<p>I mean, that PKI doesn't exclude non-approved manufacturers from producing Matter devices, you can always trust their PAA (their CA) in your border router if it's not a well-known manufacturer. And also, I am pretty sure that if this is the case the Matter border router should warn you of this and ignore the fact that the PAA is not in the local store of root CAs (as we did in the times when we had https without Let's Encrypt and didn't want to pay Comodo to sign our certs)
What a shit load of disinformation you are spreading. Read up on Matter and Thread, please.
I don't know why you're downvoted, it's the same reaction I had tbh.
Can I make a Matter device for myself?
My first reaction here was horror: Home Assistant and Zigbee integrate perfectly with IKEA’s devices, and the devices are beautifully designed! Please don’t take these away! Only the other day did I marvel at how a low battery indicator flashes on one of my remotes when I use it. A design flourish that I really appreciated.<p>But I read that Thread supports IPv6 via mesh networking. It did always feel a bit awkward having Zigbee networking and IP networking competing over the same site. It would be very nice to issue commands from any peer to any other peer, using standard networking. Can anyone here confirm that Matter/Thread will be a bright, open, and happy new future?<p>A lot of people I know would scoff at “smart home” stuff. I used to. Having a programmable house is incredibly useful though. When all your lights and sensors are available for programming you can do stuff that’s cool not because it is particularly innovative but because it is incredibly <i>easy to implement</i>:<p>- my partner can control a “do not enter, call in progress” red light bulb;<p>- my outside lights trigger off PIR, door sensors, or Ring motion detection;<p>- I have a series of indoor lamps come on in succession if motion is detected outside at night;<p>- we programmed a push button to turn a light green on one tap and red on a double tap for a fun game of twenty questions;<p>- and my indoor Ring cameras shut down unless both my partner and I are out of the house.<p>All of these things were <i>trivial</i> to do given that everything is available on one Home Assistant instance!
> Can anyone here confirm that Matter/Thread will be a bright, open, and happy new future?<p>Sorry, it’s a closed ecosystem. It relies on PKI and device attestation to ensure that only devices from approved partners are usable. It’s unlikely that small players can participate, and zero chance of any homebrew scene.
I disagree that there’s zero chance for a homebrew scheme; it’s pretty easy to enable development mode and commission self-made devices using Google Home or Apple Home on both iOS and Android.
And manufacturers tend to lock down their Matter devices, too, so you can't flash Tasmota or ESPHome on them.
See: Shelly, Sonoff.
What? You can buy a very cheap ESP32 with Thread and easily build your own device with Matter/Thread and it will work. Doesn't seem that closed. There is OpenThread that is an open source implementation of Thread. Home Assistant is compatible with Matter over Thread devices...
What's closed about this?
> <i>It’s unlikely that small players can participate, and zero chance of any homebrew scene.</i><p>I personally think the worst part of this is that China manufacturers are less likely to produce Matter/Thread equipment.<p>Cheap China equipment has been great for Zigbee adoption. They're much less reliable, but fantastic for getting a smart home going for cheap.
> It did always feel a bit awkward having Zigbee networking and IP networking competing over the same site<p>Funny, to me that's a feature. It makes the threat of a hacked device that exfiltrate data from within your network much less likely. I avoid any wifi device because of that.
This. The network fragmentation is the point, just like how some businesses would run IPX internally and use a proxy for web/IP traffic to protect corporate infrastructure from malicious devices or software.<p>Not <i>everything</i> has to be on TCP/IP. For smart home connectivity, I’d say that’s a feature, provided said networking standard is just as open as TCP/IP.
Yes, not to mention WiFi is so much more power hungry.
The thread border gateway (Apple TV, HomePod, Google Nest Speaker, etc) sends an IPv6 router advertisement to the network for the Thread IP space. Multiple border gateways can advertise the same IP space for redundancy.<p>I have/had a segmented network, so I made sure my router accepted this route so that devices on different networks could communicate with the Thread devices. It worked, usually. However, I ran into some challenges with the reliability of communicating from my phone to various devices. I never quite got mDNS reflection 100% correct, and I strongly suspect that's my problem. If you look at an mDNS entry for a device, you'll see some advertise all their IPv6 addresses including link local (fe80::). I suspected some clients were dumb, trying the first IP they found, and giving up when it didn't work. I was working on modifying the golang mdns-reflector project to filter these entries. I had some success, but I haven't finished.
[dead]
I don't understand the problem that thread solves that zigbee doesn't! The article says that thread doesn't require a hub but it require a border gateway that is almost indistinguishable from a hub. And as far as my home assistant setup is concerned, it doesn't require a hub, only a zigbee radio.<p>The only thing that seems to advantage thread is manufacturers support, but I don't see what's stopped them to regroup around zigbee.<p>Any one has clues on why Thread was needed when zigbee already existed?
Matter was created by the Connectivity Standards Alliance (CSA), formerly known as the Zigbee Alliance! Basically, Matter is the next generation Zigbee. Thread as a protocol predates Matter, and it is just one of the supported transports, together with Wifi and Ethernet (for now).<p>Edit: One thing Matter adds that was not in Zigbee is Bluetooth provisioning, letting you use your phone to add a device to your network without QR codes or numbers to type in.<p>Also fun fact; Homeassistant is part of the CSA and apparently, Google, Apple and others use HA for testing!
> Edit: One thing Matter adds that was not in Zigbee is Bluetooth provisioning, letting you use your phone to add a device to your network without QR codes or numbers to type in.<p>What follows are my two pennies as a developer working in home automation for 7 years. In this venue, readers may even have more knowledge regarding security, but I hope to speak to a common case.<p>I develop this exact feature though not for Ikea. Having made the sausage, some of these UX-first flows are worrisome.<p>Consider a lightbulb that factory resets given a rapid succession of power cycles. Most consumers won't have redundant power during a brownout, so there is an edge case where dirty power can mistakenly send the bulb to a reset state. (More plausibly, a child tugging at a light switch?) Now, any device in radio range has an opportunity to take over the bulb.<p>Provisioning is rare. Unless the owner enjoys tinkering, a residential IoT device is provisioned a handful of times in its life. I <i>personally</i> think it's a waste of time to optimize this flow if the improvements are also vulnerabilities.<p>Suppose I have a great new smart bulb. I'm ready for a larger market so I prepare a demonstration for Lowe's, hopeful for space in their lighting and rough electric aisles. Lowe's has seen this before. My bulb works fine but my users aren't technical. Lowe's replies, "we can't carry this. Users must deploy and control from a single app in 5 minutes." If I want my smart device to compete, my hand may even be forced to implement UX-first provisioning.<p>Companies like Lowe's and IKEA don't want to be in the tech support business. My bulb is a liability because their customers will call with complaints or questions.<p>I find QR codes to be a slick implementation. They don't even need electricity! Users can manage the system even when components go offline. Folks are trained on social security numbers and PINs for bank cards. It's easy to comprehend the QR code as a password.
I feel like the problem is a lack of realism about what is required to meet the usability standards of traditional analog switches. Like, I hear you talking about a tradeoff between security and usability for a "rare" provisioning event but I think in practice if you imagine a device has a 10 year lifespan, I would guess that making the provisioning hardware probably translates into at a minimum a full month of downtime over the lifespan of the device, with many devices being down for months or years at a time because no one can be bothered to figure out why.<p>The security concerns probably have typically zero impact on the operation of the device. I'm not saying that the security concerns are unjustified. Really I'm actually leaning more that this is completely impractical and not a good replacement for a dumb physical switch. The security issues are unacceptable and the downtime caused by even the useless security measures available is even worse. (Also, the security measures seem more concerned with whether or not I have a license to watch my video on that particular device than preventing people from turning on my toaster.)
> if you imagine a device has a 10 year lifespan, I would guess that making the provisioning hardware probably translates into at a minimum a full month of downtime over the lifespan of the device, with many devices being down for months or years at a time because no one can be bothered to figure out why.<p>Can you explain more about how you reached this conclusion? Why are devices offline for years now?
on the other hand - I had contractors install our Nanoleaf recessed light cans (thread over matter) in our new house. In all the hubbub, I forgot to make sure to save the light cans boxes that had the QR codes inside. I found around half the QR code stickers, but I lost the other half. The light cans also have the QR codes printed on the top, but we have nailed-down attic flooring that covers them completely. So I'm basically just praying that Nanoleaf's CS can give me the pairing codes based on my order number, haha.
Oof, yes that's certainly a way QR codes can go wrong. Ideally manufacturers print the QR code on the device such that it lasts the device's lifetime.<p>It would be nice if technical users (installers) could reset the certificates or keys too. Besides losing the QR code, secondhand owners also want some assurances.
while your example is correct, I have many many examples in my experience why scanning a qr code is simply infeasible in some situations and as a owner of a heavily automated home I welcome the development with open arms.
As I understand it, Thread can transparently extend its mesh over regular IPv6 (Ethernet, Wi-Fi, etc), whereas extending a Zigbee (or Z-Wave) mesh beyond useful mesh range is a mess. I have a Z-Wave network that uses two controllers, and it <i>sucks</i>. It’s utterly obnoxious to maintain, the whole concept of multiple controllers is barely supported by zwave-js-ui, it is far to dumb to recover quickly on its own if it transiently loses connectivity to a node, and roaming between controllers is a complete non-starter.<p>I haven’t tried Thread yet, but I’m delighted by the concept of having a couple of easy-to-maintain base stations (routers or whatever they’re called) connected to the local network and having devices automatically roam between them.<p>I am <i>not</i> delighted by the fact that an Apple Home Thread network, a Google Home thread network, and a Home Assistant native thread network appear to be different things that are not entirely compatible with each other.
I believe this is what thread v1.4 is attempting to solve. Apple has already updated their Thread border routers to v1.4, and Google, Amazon, and Samsung have all promised to update their border routers too.
Yes this is indeed a problem. You can get around this by piping the Z-Wave or Zigbee information into a MQTT server and basically run them as separate networks, with Home Assistant and MQTT tying it all together. But you will need some type of Zigbee to Ethernet adapter (Sonoff makes one, Raspberry Pi, etc.) or Z-wave to ethernet adapter (again Raspberry Pi). It's definitely clunky. But doable.<p>I am running multiple Zigbee networks near each other (in a house and in a detached garage) with Home Assistant, MQTT server and a Sonoff Zigbee bridge, with Tasmota.
> I am not delighted by the fact that an Apple Home Thread network, a Google Home thread network, and a Home Assistant native thread network appear to be different things that are not entirely compatible with each other.<p>Hmm, in what way? The Matter standard does demand that devices support at least 5 of such "fabrics" at once. Where is the issue in practice?
Maybe there isn’t one. Can I “pair” a Thread device with, say, an Apple TV and have it talk to the Apple TV via radio to an IKEA Dirigera hub and then IPv6 over Ethernet from the Dirigera to the Apple TV?
My understanding is that Thread is lower latency and lower power than Zigbee.
I am hoping that this is the thing that triggers Matter/Thread to go mainstream.<p>I'm currently blocked because Google and Amazon don't support "Generic Switches". Which means that if I switch over a light-bulb to being a smart one I can't use something like the Arre Smart Button to control them. Which seems like such a standard requirement that I do not understand why it's not supported.<p>If Ikea will let me set that up then I'll be delighted.
I'm not sure what I am missing, but isn't it completely possible to connect any kind of smart button to control a light bulb? Isn't this exactly what home assistant is being used for? I only tried it, but was able to add a generic smart button to HA and let it control a USB switch with some led lights. How is your use case different?<p>UPDATE: Ok, is this about the state of Matter implementation? I think I misunderstood that.
For how much hype Matter had (I remember everyone saying "Just wait! Any day now!") it sure... hasn't delivered
Yeah.<p>I've got it up and running with some Nanoleaf lights and Amazon Echo running as border routers, and it's rock solid nowadays. But my wife hates voice-controlled devices, so I can't put them in elsewhere until I can slap in some buttons to control them. And that's basically not supported, which leaves me thinking that either the spec is a disaster or Google/Amazon are deliberately kneecapping it.
Huh... anyone know what this will mean for people with legacy Ikea lightbulbs and hub?<p>e.g. if I add future Ikea lightbulbs or other equipment, will this mean managing them via a different system?<p>(By the by, I've been very happy with Ikea bulbs so far; while other people complain of LED bulbs with a short lifespan, [touches wood] I've not had a single failure with Ikea smart bulbs, with ~7 years and counting on one of mine.)
The newer DIRIGERA hub has both radios, and recently added full thread support in a firmware update, so you should be good if you have it. Otherwise, add that or an upcoming hub or migrate the old bulbs.<p>I love my Ikea smart home gear, it works really well. Odd that a cheap furniture store that sells meatballs seems to have a more coherent smart device strategy than major tech companies!
Looks to me like they'll continue to work. There are multiple mentions of backwards compatibility in the article.
Isn’t this the history of home automation? The money is in getting people locked into a “system,” but the systems are things that tend to rapidly become dated. So people will invest in a system and either get disillusioned due to the downside of lock in or the system goes obsolete and the newer stuff is not compatible because it’s a whole new system. Rinse, repeat.<p>There have been many attempts at industry standards but they fray around the edges. Nobody understands that a protocol and a spec is not a user experience, so the standards just become the basis for closed walled garden “systems.”<p>It’s why I stay away from it.
“[Matter in its current version] doesn’t really help resolve the key issue of the smart home, namely that most companies view smart homes as a way to sell more individual devices and generate recurring revenue.”<p><a href="https://staceyoniot.com/matter-only-solves-about-one-of-the-smart-home-core-issues/" rel="nofollow">https://staceyoniot.com/matter-only-solves-about-one-of-the-...</a>
That's the strength of a DIY approach backed by a community of users like homeassistant, it doesn't get obsolete.<p>I will just have make sure that I have a spare zigbee radio in case they eventually disappear from the market.
I mean... I have an Aqara Matter over Thread smart lock that connects via AppleTV (which is a Thread border router) to Home Assistant. And I can control the lock both with HA and Apple HomeKit. And this whole thing works flawlessly. Aqara, Apple, open source HA. Never thought this would be so smooth.<p>I think the whole point of Matter is that the devices are manufacturer independent and you can use any device with any hub.
The lamp+speaker is interesting. Wish it had usb-c for power, and or wireless charging.<p>A pity there's no home standards for audio streaming. Matter Cast is an abomination, unfortunately: from what I can tell it requires native apps for each device, and there's not really an app store system, and indeed seemingly many devices only can stream via the pre-installed software!!<p>Really emphasizes the incredible power of Netflix's DIAL protocol, which tells a device to go to a URL & opens some command channels. Which is, if you squint, what Chromecast 's protocol was for a long long time (now I think there's also the ability to ship native apps to devices too?).<p>Really glad to see Ikea on board here. This creates a lot of pressure for other devices makers to modernize & use the much improved Matter stack, with much better network performance & much more standardization for Apple Google & potentially other control fabrics to make viable home systems, something Z-wave and Zigbee weren't positioned to make great progress on.
Haha. Imagine a light switch that becomes obsolete like your wireless router.
First daim chocolate, now zigbee...
RIP. The ikea zigbee stuff was close to being best in class. Matter is still an unusable mess.
I have stuff that didn’t support Matter on launch, that I updated to Matter, and it seems exactly the same in practice.
In my experience, Matter already works better than Zigbee and Z-Wave ever did, and it gets better every year. I'm interested in what your unusable mess of a system consists of, if you don't mind elaborating.
Just look at how long this page is:<p><a href="https://www.home-assistant.io/integrations/matter/" rel="nofollow">https://www.home-assistant.io/integrations/matter/</a><p>Adding a device now requires a whole song & dance with bluetooth, a mobile phone and god knows what else.<p>Meanwhile zigbee is:<p>1. Buy a zigbee stick, there are dozens, they all work great<p>2. Press the permit join button in home assistant<p>3. Press a button on the device for 10 seconds or 3 times or whatever<p>4. You're done and it works!<p>Oh, and for some reason <a href="https://www.home-assistant.io/integrations/matter/#experiment-with-matter-using-a-esp32-dev-board" rel="nofollow">https://www.home-assistant.io/integrations/matter/#experimen...</a> involves google cloud in the process of me testing a device I created locally on my own network<p>The final nail in the coffin is:<p>> It is recommended to run the Matter add-on on Home Assistant OS. This is currently the only supported option. Other installation types are without support and at your own risk.<p>So I can't even officially use this stuff without uprooting my entire operating system.
Look, I agree with you and as someone with Home Assistant, I much prefer Zigbee.<p>But if you imagine a typical consumer, not a tech nerd, I think "smartphone and bluetooth" is by far preferable to your 4-step process.
To be fair, step 4 isn't a real step, step 1 is just buying the "hub" or "border router" or whatever, and step 2 & 3 are the same for Zigbee and Matter, the button is just somewhere else.<p>A typical consumer has bought a zigbee hub (like they need to buy a thread border router), then use their phone to press a button in the app and then they press a button on the device. Still dead simple and doesn't require flaky bluetooth from their phone, which in 2025 most androids still suffer from.
That’s been my experience. My older Zigbee/Z-Wave stuff seemed to work… up until it didn’t, and then cue wailing and gnashing of teeth. My Matter gear was initially a little flaky but is now vastly more reliable than Zigbee ever was.
I only recently discovered and invested in the IKEA ZigBee hardware, about the only product their MBAs havent destroyed. The hardware is very well built, and sensibly priced. What I liked most of all was that the hub was optional, and thus no cloud account required.<p>I ended up pairing mine with a 'ConBee II' and with a bit of Go code was able to receive sensor data with very little latency, and activate switches and lights very quickly.<p>What a shame they discontinue such a great product line. But I already decided this is the last home automation technology I'll invest in. ZigBee seems perfectly suited for this role, and no idea why we need yet another new standard. Although I also said that switching away from x10, if anyone still remembers that.
Unfortunately, the writing's on the wall for mainstream adoption of Zigbee. For me, Leviton not making any more Zigbee smart switches was the last straw and I've prioritized Z-wave devices where possible. I also get much better performance out of Z-wave. Sad to see though, as the Zigbee devices I do have are working just fine. I don't really get the point of Matter or Thread when Z-wave works so well.
It's pretty straightforward: Z-Wave is a closed (one company owns and controls the tech and brand) hub-bound mesh, and really should've been displaced by an open solution long ago. Matter is an industry-standard IPv6-based application layer that works over Thread (the successor to ZigBee) <i>and</i> Wi-Fi.
Yes - but it does feel over-engineered in some places (for good reason, having device profiles that everyone adheres to makes supporting a new device of a given class a doddle for smart home platforms) and it is definitely more finicky at present to pair devices than with Zigbee.<p>If I had to wipe and re-setup my smart home with 100 Zigbee devices and 18 Matter over Thread devices (Tado smart thermostat and TRV's) the Zigbee devices would take me about half an hour in total to have back up and running in HomeAssistant, the Matter over Thread devices would take me around 2-3 hours as you have to pair them one-at-a-time.
> <i>If I had to wipe and re-setup my smart home with 100 Zigbee devices…</i><p>FWIW, this is purely an HA issue, not a Matter one. Once HA includes the Matter credential store in backups/restores, the experience will be the same.<p>Out of curiosity, what is the reason you find yourself completely wiping and re-pairing all of your Z-Wave devices?
Z-wave also uses 900mhz in the US, which penetrates walls better and has less competition with 2.4 (Zigbee). So while its closed, it usually more performant than Zigbee (in my experience...)
So you dropped a dying ecosystem for a very dead and buried underground one?<p>Bold move.
This is horrible news. Zigbee has been trouble-free and Thread has been nothing but Trouble to the point I had to throw out everything based on Thread…
We could have had ZigBee Smart Energy Profile 2.0 running all of this, with the glory and righteousness of IP networking everywhere. Oh well...
What is the equivalent for zigbee2mqtt for Matter/Threads?
I don't know if there's an MQTT bridge yet. Generally, you run some kind of border router and connect through that. While the work doesn't seem complete yet, there's a guide to turn a Home Assistant install into a Thread border router if you have the necessary hardware: <a href="https://www.home-assistant.io/integrations/thread/#turning-home-assistant-into-a-thread-border-router" rel="nofollow">https://www.home-assistant.io/integrations/thread/#turning-h...</a><p>You can probably plumb Home Assistant into your MQTT server from there.
You just need a Thread border router and Matter devices connect to your HA without problems. I use Apple TV as a border router.
That is my sticking point - every border router I can find has a bunch of other things I don't want. I don't want my lights available from the internet, I just want to turn on the shed outside light from inside the house when I have guests. (since they are likely to park by the shed and walk to the house)<p>That is I don't want google/amazon/samsung/apple to control my house. Most border routers are also connect to our smart home system. (there are exceptions but it isn't clear if they are better)
While not a proper product, you can buy a small ESP32C6 devboard for up-to-5 USD/EUR and flash an example from esp-idf. This is paired with some software that runs on posix systems (think your HA host) that together form the necessary commissioning and border routing functionality. Its ends up being a relatively simple device that just takes IP packets off the radio and puts then somewhere else, so I've no doubt somebody will shortly make one (I've been working on one such for myself as an experiment.)<p>For what you're looking to do in principle you don't really need any of this after the initial commissioning. So long as the radio waves can reach the devices they will be able to talk to each other.
Just checked again, those ideas have started to mature to something that is possible now (vs 6 months ago when I last looked). I have kids and many other things in my life, so I'm don't have much time to work on projects like this. That might be what I end up doing, for now I just have a light that hasn't worked for months because I don't want to figure this out (the manual switch is broken. Since the switch is both rarely used and one I'd want remotely controlled anyway I've been hesitating)
SMLight also do their PoE sticks that can be flashed to either talk Zigbee or Thread (but you'll need a border router, such as the OpenThread border router).<p>Their latest one has two radios so you can do both Zigbee and Thread from a single device.<p>I've found however, that Thread prefers several border routers around my house to operate well.
This really sucks. I have a smart home with home assistant and most of my things are Zigbee and Ikea stuff are great. They are affordable and they are high quality. So now I have to find another provider of especially light bulbs.
My IKEA was missing a lot of Trådfri assortment when I visited this week. I started to have doubts if they had abandoned the home automation niche. Now when I am searching their site, much is gone. But I guess they are clearing the inventory for a Threads relaunch
That's such a shame. I bought quite a few IKEA devices as they were the cheapest in the market and were Zigbee-driven, which meant I could use it with my custom-made SmartHome software (which does what Home Assistant does but without a heavy runtime) and they connected with other manufacturer's devices (they form a mesh, so as long as you have a Zigbee device every few 10s of meters, the devices can communicate with the central hub even from very far away). I wonder if I will be able to connect to Thread devices at all now.
I'm pretty sure this is misreporting, and these devices actually support Matter as well as Zigbee.
Paywall bypass: <a href="https://archive.is/8S1un" rel="nofollow">https://archive.is/8S1un</a>
Warning: a bit of a rant incoming...<p>I've found Matter totally confusing. Given a device that supports Matter (e.g., a smart plug) and a set of devices I want to control that from (e.g., an Amazon Echo and an iPad) it is not clear to me what else I need.<p>Apparently I need a "controller", which is not necessarily the thing that I as a user would think of the controller--as a user I think of the controller as the device I issue command from. A Matter controller is apparently a hub for connecting the thing I'm using to issue commands to the IOT device I want to control.<p>And maybe I need a "Thread border router"?<p>As far as the controller goes, apparently at some point Apple added the ability for iPads to be Matter controllers, so you could use a Matter device with just an iPad (if the Matter device used WiFi...if it used Thread then you would need a separate Matter controller and I'd guess one of those Thread border routers).<p>I was able to briefly use a Matter smart plug with my iPad without having a separate hub, but it stopped working not too long after. I deleted the plug from the iPad and did a factory reset on the plug and tried setting up again, but now when the iPad searches for the device during setup it doesn't even see it.<p>Apple still has instructions on their site for setting up devices for direct use from iPad, but several sites on the net report that they actually dropped that support from iPad.<p>So lets say I go get an actual Matter hub. Do I need a separate hubs for using my Matter devices from my Apple devices and using my Matter devices from my Amazon devices? How about if I need a Thread border router--will I need one for Apple and one for Amazon? What if I add Home Assistant later--am I going to need a third hub?<p>All I'm really trying to do for now is use this one TP-Link Tapo smart plug that supports Matter from Apple Shortcuts without having to use the Tapo app. The Tapo app does integrate with Shortcuts but you have to be logged in to your TP-Link account on the app for it to work. Every so often you have to re-login, breaking your shortcuts until you do.<p>What I'm currently considering is installing Home Assistant somewhere, probably in a VM on my Mac for now but latter on a dedicated RPi if the experiments in a VM show that it will work, and setting it up to be my Matter controller for the smart plug. Shortcuts (or Siri) won't be able to directly use Matter to control the plug with that setup, but there is a Home Assistant app for iOS/iPadOS that can do so and that supports Shortcuts.<p>It will basically be like I'm doing now with the Tapo app but instead with the Home Assistant app and no need to be logged in to TP-Link (or to even have internet access).<p>PS: I wouldn't need any of this if Apple would just get around to implementing for iPadOS the same 80% charge limit option that they have had on iOS for ages. I'm using the smart plug and Shortcuts as a kludge while waiting for that. I charge through the smart plug and have a Shortcut automation to turn off the smart plug when the iPad's battery level rises above 80%.
Some Amazon devices (see a list here: <a href="https://www.amazon.com/b?ie=UTF8&node=37490568011" rel="nofollow">https://www.amazon.com/b?ie=UTF8&node=37490568011</a> ) already support Matter devices, so you might already have everything that you need. The Tapo 110M (M for Matter) plug for example can easily be paired with them and work flawlessly (an also much faster than the non-Matter counterparts). And yes, they don't need internet access to work.<p>You still need the TP-Link app for some more advanced functions like power metering though.
Matter has been very disappointing so far, with very unreliable connectivity and behavior (using Apple TV as a border gateway). I basically gave up on it and prefer to use non-Matter HomeKit hardware (usually WiFi) where I can. Don't know if Zigbee was better, but it can hardly be worse.
I use some sort of cobbled together solution with Philips Vue lights, a couple of LIFX lights, halfway set up HomeKit, the Vue app, some Alexa integration, some sort of gateway that I believe connects Zigbee to my LAN...<p>.. but all I can remember from growing up is the X-10 POWERHOUSE
Does Thread work without cloud?
The question doesn't really make sense this way. Thread is more or less like Wi-Fi. It's a transport technology and protocol. It's HOW your devices can talk to each other. It's how they can say "I'm here and I can see 'AirPurifier324' over there."<p>Matter is a bit like HTTP. It's WHAT your devices say to each other. It's a way for them to say "Hi, I'm a lightbulb and you can change my color and brightness."
Ok, let me ask another way.<p>Can it operate without an internet connection and with an open standard that lets the me, the user, to be in control using a hub (if necessary) and software I choose, including an open source option should I so choose?<p>Or do I have to use proprietary hubs and software to control the devices?<p>In short, are there any end user hostile features or can I use the devices like how Zigbee works?
I've done everything using old Particle Xenon boards (nrf52840 microcontroller) and didn't encounter anything 'user hostile'. Originally I had all the 'hub' stuff on one of the boards too, but the newer recommended way is to have the board be the 'radio' and to use a normal computer for the routing.<p>The matter network is just an IPv6 network, so I run coap server on my matter devices and then control them with command like 'coap-client -m post coap://[<ipv6 addr>]/open_button'.
Two devices can talk to each other if the hub helps them exchange keys <a href="https://community.home-assistant.io/t/how-to-implement-device-binding-between-two-matter-devices-via-ha/859948" rel="nofollow">https://community.home-assistant.io/t/how-to-implement-devic...</a>
Yes but since it routes IPv6 and hubs are usually connected to the Internet when set up by the average consumer, it is very easy for Thread devices to "accidentally" gain Internet access.
My understanding is that it can never be accidental since all access is mesh-local by default. You'd have to install a border router capable of supporting NAT64 features — SmartFriends™, I think this generally not possible with consumer border routers, correct? — and then explicitly enable it for a device.
Yes, local control is a key feature as well as multi-controller.
yes, that's the entire point of it
Leggi tutto
The new verge paywall seems to come out of no where, and seems to cover every article with no free limit?
Paywalled. <a href="https://archive.is/uOHVR" rel="nofollow">https://archive.is/uOHVR</a>
[dead]
[dead]
"A software development kit (SDK) is provided royalty-free,[13][14] though the ability to commission a finished product into a Matter network in the field mandates certification and membership fees,[15][16] entailing both one-time, recurring, and per-product costs.[17] This is enforced using a public key infrastructure (PKI) and so-called device attestation certificates.[15]"<p>So it's a closed ecosystem that makes money for a cabal of corporations
It's "closed" in the same way that all open wireless standards (Wi-Fi, Bluetooth, etc.) are closed. You can read the spec, use the open source SDK, and build devices without paying a cent.<p>If you want to participate as more than a hobbyist, you'll need to join the CSA (a non-profit mutual-benefit corporation). This will cost a bit less than half of what it cost manufacturers to join the equivalent organization for Z-Wave — a closed, single-vendor, non-IP-based solution that was state-of-the-art 25 years ago.<p>Money paid by commercial vendors funds stuff like test labs, interop events, and compliance support systems.
Apparently "smart home" means that it's now a knowledge worker job to operate a lightswitch.