Always add one device at a time, even though Matter allows you to do a bundle now.
4 Likes
Oh you’re right! Didn’t thought about this kind of redundancy “backup” but this is a pretty good point you got here!
1 Like
Same here. I only have a few Zigbee devices, so that network isn’t as robust as my Matter network. The M3 hub does an okay job of bridging those Zigbee devices to Matter. I say “okay” because it would be nice if the device names would propagate, and the fact that Matter does not yet have a lot of custom characteristics.
2 Likes
The problem I’m finding with the M3 is what version of Matter it supports. Officially, I found, it is 1.3 but it has not implemented all of 1.3, such as power information.
2 Likes
Zigbee. Whoever invented this QR-code thing is braindead. You have to collect the Stikcer and note which device is where becaus ethe code is very often not accessible when installed. Nice to have a standard for all but those who set the standard should think before they write.
4 Likes
HomePass does a great job.
3 Likes
I vote for Zigbee. Matter is over hyped because Apple adopted it, then all others.
1 Like
You do know that Nest invented it and google also embraced it with their purchase. Then Apple got on board.
4 Likes
Yeah, i know, but since Apple embraced it, got a big hype. We all know it
1 Like
so you just don’t like it because Apple does? No thought about if it is a better technology, etc?
1 Like
It’s not really about Apple for me. I’m looking at it from a practical point of view.
Matter has some real advantages on interoperability and onboarding, especially if you want the same devices exposed cleanly across multiple ecosystems. But for my setup, Zigbee still feels more mature and predictable. The device support is broader, battery devices are well understood, and in day-to-day use I’m not seeing enough performance benefit from Matter over Thread to justify switching everything.
So I’m not anti-Matter at all. I just don’t think the current reality matches the hype yet. Right now I prefer Zigbee because it’s stable, proven, and does what I need.
1 Like
now that is a much better answer.
I agree that Zigbee is more mature and is probably more stable at the moment. I’d not even try to convince someone to replace zigbee devices with Matter over Thread, but I would suggest that new devices are Matter over Thread.
I do have an Apple ecosystem and I am now Matter First, Apple Home 2nd, anything else 3rd. I don’t really run Zigbee except for my energy management system which I had no choice over at the time. However, I am gradually replacing Apple Home specific devices with Matter devices if the Apple Home device breaks or if there is significant change in functionality.
5 Likes
I’m using HomePass to keep track of my devices and Matter codes as well! So I can suggest this app as well!
1 Like
This is smart because at the moment, when enabling Thread on the Eero routers it creates its own Thread network with no ability to optionally join it to an existing Thread network in the home.
I had to do the same, and disable the Eero Thread network.
4 Likes
I also had to disable Eero and suddenly Thread devices started playing nice with each other again. Well not suddenly but within a short amount of time.
1 Like
I’m going back from Matter to Zigbee because the network on Matter is not very stable/reliable once you have more than a handful of devices. I have around 40 to 50 to migrate back.
4 Likes
I can totally relate to your decision! I’m thinking about doing the same. Somehow some device will go offline on one of the platforms. Sometimes on all of them at the same time. I even set up a whole new thread network to sort out any issues beforehand but at the moment I’m not 100% satisfied with matter over Thread. I‘ll double check my network settings to see if I oversee something that leads to the issues I have
I just completed that small project. I removed 15 Thread devices and moved them back over to Zigbee and in some cases removed (deleted) the devices from the network and replaced them with FP300 devices in Zigbee mode.
When looking over my Thread Network I found the Motion and Light Sensor P2’s were always wondering around the Thread Network and disconnecting constantly. (sucking up battery time) and causing Network errors.
Since removing the problem children and adding the FP300’s I’ve had no errors or Thread Network issues.
I also added another Thread Antenna which may have helped the P2’s but I never gave them a chance and just moved on to the FP300’s. They perform better in certain circumstances anyway.
Zigbee is very mature, proven and works great. Thread needs works and I feel like I’m part of a Beta program. Which version of Thread is the most recent? Who uses the most current Thread version? What a mess.
4 Likes
Hi, yes, I completely agree with you. I always said that “universal” is not always good (I’m talking about Thread). Zigbee has never let me down in a critical moment in 99%.
Interesting choice. What smart home system are you using? e.g. I find that Apple Home with Aqara is bullet proof. However, I have one specific Nanoleaf device (I have a few) that as soon as I introduce that one it causes instability. (I’m working this with Nanoleaf on this.)
The design of Thread should actually be something of stability considering its mesh nature.
There are known issues with Thread though. 1.4 is supposed to make that much better… particularly around removing islands of Thread.