I would assume, yet _another_ standard. There are a bunch of them, and product builders are taking a long long time to properly implement, and often buggy. And they often result in the consumer need to buy yet another gateway/router, and learn the ins/outs and quirks of another protocol that won't work properly in years, all the while two new competing standards have been introduced. An example - how long has Matter existed? Yet, it hasn't had a profile for smart plugs with energy monitoring (eg the 12$ IKEA one). Such a basic use case...

And all this so Samsung et al can siphon off more user data and show more ads.

I fully understand the consumer viewpoint.

But, it's great news imo with sub-GHz (Suzi)!

I hope Zigbee stays. It’s widely used and works really well. Matter may be even better but it also makes it really hard for manufacturers to actually make products that can be sold cheaply. Zigbee is just good enough and I believe the push to replace it has ulterior motives.

The good thing is that at least for a somewhat technical crowd, there is absolutely no need to buy into any of this, as there have been proper solutions available since at least 2018.

Just buy Hue, maybe Aqara sensors, use zigbee2mqtt with Home Assistant and be happy while observing the shitshow that is this market from a safe distance.

> Threads

You mean "Thread"? Or "Matter over Thread", which some vendors also just call "Matter" (which technically can also stand on it's own, but in many cases implies a Thread requirement). I'm wondering if that muddiness in bad communication will be a significant factor in hindering consumer adoption.

More power usage though.

Multiple reasons like not enough v4 IPs, devices being able to sleep most of the time to conserve power, security cameras and IoT devices getting hacked and faling prey to by botnet operators etc.

I have to say that the Matter Cast standard sounded good, but ended up being an abomination, imo. Instead of ther being a boradly available platform for casting, my crude understanding is that to have Matter Cast work, there has to be some out of band way for an app that wants to cast to have a reciprocal app available on the target device. There's nothing provided to help facilitate this.

Where-as with DIAL and for the first decade of Google Cast, the device being cast to was basically a web browser & could run any url. It made it so any device could be cast to from any app. https://en.wikipedia.org/wiki/Discovery_and_Launch

It's been incredibly disappointing seeing Matter build a standard that completely fails to offer a usable path. I really want to be wrong here, but it sure seems like Matter Cast requires every device to have its own unique bespoke partnership & install already loaded, for everything that will be able to cast to it. It standardizes some protocols for how to communicate, but there's such an anti-standard vendor-controlled limited anti-ecosystem basis.

I really really want Matter to be a good better world. I hope Matter Cameras can bring some unity to streaming camera systems. But man I can not see how Matter Cast could be worse designed, more hostile to the freedom to cast that we've enjoyed, and I really worry for this ecosystem as a whole if this is what Matter is willing to ship.

I'd also really like to see affirmations that Matter is usable sans any big network, sans Google Apple and whomever else. That it really is something we can run ourselves. But I haven't seen validation that Matter really is as liberatory as it's promises, haven't seen evidence that folks really can undo the Internet of Shit damage with Matter. I hope it's just all us being extremely slow on the uptake, but I have heard just so little about running our own provisioning/control networks on Matter. I want so much to believe but my vibe is that we've been rug pulled again.

What I really don't like about thread/matter is that it is becoming the de-facto standard that thread border routers are connected to the internet.

This will in time result in IoT devices that actually mandate this connection (it was already stipulated in a recent version of the protocol). The end result will be that a new protocol was created, but rather than devices being able to run on their own, we end up with beds in heating mode, ie. the garbage we were trying to avoid in the first place.

So for me, zigbee it is!

> the facto *de facto

Any reason you prefer Matter rather than Zigbee? Zigbee has been a thing far longer than Matter, so I don't think the "one more standard" criticism is valid here.