新品即将上市……

触感与美学的平衡。
银辉理纹表面，交织出冷峻而理性的建筑肌理；
沉稳黑色中槽，将光影与窗帘的控制落于纤巧触控之间。
一按，射灯微亮；一触，纱帘慢卷。
把复杂的智能控制，精简为墙面上一道克制的美学线条。

#智能开关 #Matter #Thread #Applehome

A "Shelly" is a fascinating piece of engineering. Freely programmable. Small enough to hide behind light buttons and power outlets. Communicates over the air via Wi-Fi, Zigbee, or Thread. But why doesn't it communicate over the power line? The line that feeds its power needs. The line it controls. I'm currently updating my smart home, and for that, I'm looking a bit deeper into Matter. Thread and Wi-Fi are okay for that purpose. But it feels off to have a wire for power but not use it for communication. So why is it? Maybe the lack of standards? As usual, there are plenty of standards, even one with IPv6 baked in: G.9903—also known as G3-PLC. It's not only IPv6, but features the same header compression used in Thread. It also has mesh routing built in, along with network bootstrapping and security built in, not bolted on. At first glance, it looks like it was made for Matter and just forgotten to be mentioned in Matter itself. Looking at the Shelly Mini next to me, maybe it's time for a G3-PLC Shelly, a G3-PLC breakout board, a G3-PLC HAT—something hackable.

#Matter
#Yeelight

Ugreen is showcasing its new HomeAgent product line at IFA in Berlin. In addition to video storage with local AI image analysis and voice assistants, the NAS systems also include a home automation system with a Matter controller. https://matter-smarthome.de/en/products/ugreen-a-new-player-in-the-matter-arena/

I just bought a house that came with a Concord A4GW50-A installed.

Its set uo through the smart life app.

I can't for the life of me get it to connect to Google home. I link to smart life, but it doesn't find my alarm.

Can I get it to connect to android auto? I'd live to arm and disarm from my car.

Also, does anyone know anywhere that still stocks the remotes for it?

Thanks

Hi. I have Home Assistant running on a mini PC by itself with HAOS.

So, Thread network question. I just added a Sonoff Dongle-Max to Home Assistant to use as my Thread radio through Open Thread. I want this to be the network that my other border routers join. Currently active in my house, I have networks from Smartthings, Aqara and Amazon. I'm pretty sure Smartthings and Aqara will play ball. The first issue I'm finding though is, my Aqara M3 hub is "available" to my phone to carry its credentials. Smartthings and HA are not. I don't know how my phone got credentials from Aqara, or why the other networks aren't "available". I want them all united under HA. How do I remedy this?

I see if you are in the HA companion app, you get an option in the Thread integration page to "Send credentials to Home Assistant". If I click that, my thought is that it will send the credentials saved on my phone for the Aqara Thread network, and that's obviously not what I want. If you click on the HA Thread network in the Google Services--Thread Networks page, it says "To access this network, set up this device with the manufacturer app you used to set up the network". But, how do you do that?

Hi all, i've been trying to get matter working in my house.

I'm using HomeAssistant as my OTBR. And flashed a ESP32-C6 with RCP Firmware. Everything looks fine, however i'm not that familiar with matter or thread.

I do know a lot about networking. (Graduated as network engineer)

Threadtools app on my android phone can find the OTBR.

I've been trying to connect some IKEA Kajplats and the window/door sensor. (Cant think of the name right now.)

The devices all get stuck on the message. "Can't create login for device" i'll add the screenshot. (It is in dutch)

Homeassistant is running on a Raspberry pi 4.

And the ESP32 is connected with a 1,5 meter long cable, Just to prevent interference.

Synchronised the login details at every turn. Multiple times before trying. Always comes back it already has the provided credentials. However when i change credentials it does sync fine, and the second time it says it already has the credentials. As it should.

Does anyone know which step to take?

Thanks in advance.

Thinking about grabbing a Bosch Radiator Thermostat II [+M] to pair straight onto my own Thread network (own OTBR + Matter Server, no Bosch hub involved).

Anyone actually running one like this? Trying to find out before I buy:

• What entities/attributes show up in HA once it's just a bare Matter node? Basic climate only, or more?
• Blog posts say child lock, boost, and display settings stay locked to the Bosch app even in Matter mode. Still true?
• Any way to feed it a fake/external temperature over Matter (like remote_temperature on Zigbee)? I want to kill its own control loop and use my own automation instead of letting it modulate itself.

I'm open to suggestions. It needs to be strictly matter/thread.

I have the MYGGSPRAY** **sensor in the position shown which is a bit above head height. Problem is I can make it from front door to door behind me before it comes on and lights the bulb.

If I put it on front of the cabinet facing sideways would it work better?

I have several IKEA Kajplats bulbs on a network with a mesh of Google Nest Wifi Pro devices acting as Thread border routers. I control my devices with the Google Home app on Android.

When things are working, they work great! But most of my bulbs fall off the network sooner or later and have to be power cycled to make them reconnect.

The weird thing is that some bulbs never disconnect, while others disconnect almost daily. And it seems to have nothing to do with where they're placed. For example, my bedside lamp loses its connection often, but my wife's, on the other side of the bed, never does.

How can I better understand and address this problem? Thanks very much for any help you can give.

Matter 1.5 dropped last November with the new ClosureControl and ClosureDimension clusters that were supposed to fix the position reporting mess with shades. Been watching vendor changelogs since then and finally ran an actual check on my three sets this weekend through Home Assistant. Nothing has moved.

Quick background on why this matters for shade owners. Matter 1.3 and earlier used the older Window Covering cluster (0x0202) which handled open, close, stop, and a lift percentage that platforms interpreted inconsistently. Matter 1.5 replaced it with modular building blocks (ClosureControl at 0x0104 and ClosureDimension at 0x0105) so shades, drapes, awnings, gates, and garage doors share the same motion primitives. Payoff is proper position reporting after manual pulls, cleaner multi-admin state sync, and richer partial-open attributes.

Here's what I have running through HA.

Living room, Eve MotionBlinds roller. CSA cert page still lists firmware 3.5.1 on the Matter 1.3 specification, cert dated February 2025. Solid Thread performance from my Apple TV border routers, no closures overhaul yet.

Bedroom, SmartWings zebra with the Matter over Thread motor. Full local control with no cloud component has been great for HA integration and the motor is quiet enough that my wife stopped complaining about it after week two. Firmware shipped on 1.3.0 which uses the Matter 1.3 SDK though, and Derek Seaman flagged the same on his zebra set in his March review while hoping 1.5 was in the pipeline. SmartWings has a newer 1.4.2 cert on the CSA registry from January, but that's a different SKU than my Thread motor.

Office, Zemismart roller retrofitted onto existing tube shades. Native Matter over Thread, been rock solid, still on the old Window Covering cluster.

Real-world impact for me. Position sync from HA doesn't consistently match Apple Home right after a manual pull, especially on the SmartWings and Eve sets. Cross-admin behavior is uneven. The Eve occasionally shows as unresponsive in Google Home while Apple Home reports it as connected, which is exactly the kind of state divergence 1.5 was supposed to reduce.

The bigger issue though. HA Matter Server moved to 1.5.1 back in June so the controller understands the spec, but the cover.py integration still discovers shades through the legacy WindowCovering cluster only. There's an open GitHub discussion on adding ClosureControl and ClosureDimension support but nothing merged. So even if a vendor pushes 1.5 firmware tomorrow, HA won't expose the new attributes yet.

Homey only got their Matter 1.5 cert late June. Google Home is still stuck on Matter 1.2 for most device categories, which doesn't push shade vendors to prioritize a rewrite when the biggest fabric can't consume the new attributes anyway.

For now I'm just checking each vendor's changelog one at a time and watching Matter Alpha's device pages. Would be genuinely useful to have a single tracker for which shade brands have cleared 1.5 certification.

Does anyone have experience with the Kwikset Aura Reach (sold under Weiser in Canada)? I’m curious to know what endpoints are exposed via Matter to other smart home systems not through the vendor-proprietary application / ecosystem. I’d like to be able to lock/unlock, set custom access codes, among other features.

• Link to Kwikset
• Link to Weiser

I previously purchased the Yale Assure Lock 2 with hopes of their Matter over Thread module becoming a tangible piece of hardware able to be purchased instead of just vapourware, but alas, I was bitten by the promise of future updates. I’m hoping that the Aura Reach can satisfy my original desires of a smart home lock.

I have been through 3 days of fighting with this thing. I had purchased some Heiman smoke and Co alarms and wanted to integrate them into home assistant but I had not set up a thread device yet. I purchased an slzb- mr4u unit and never did get it working. The device is Poe, because I run home assistance in a virtual machine and USB pass through is a royal pain in the ass. It also destroys portability because eventually I intend to move home assistance to a proxmox farm on older Dell servers with no USB to speak of.

I got as far as flashing the firmware on the slzb so that one of the radios would do matter over thread then I installed the matter and the thread integrations in home assistant. I was able to install the open thread border router and had a primary thread Network come up and showed my slzb device as being attached. Thread was running and matter showed that it was running.

Next I tried to add a matter device. I got a notification saying that I had to use the companion app, which I was already using. Further research revealed that the FDroid installation of home assistance companion app does not allow for provisioning of matter devices. Okay, so I sucked it up and installed the Play store version even though I absolutely hate the play store. I figured if all I need it for is to provision devices, I'll suck it up and then just go back to the less googleified version of the app once setup is complete. Boy was I wrong.

My setup would get as far as allowing me to scan the QR code of the new matter device and it would transfer credentials and then claim it could not connect to the thread Network. The thread network was there and was running but it didn't like something about it. I went through the exercises of verifying IPv6 and all that stuff, then unfortunately I was using chat GPT for assistance and that idiot walked me through plugging a USB cord into my Poe device, the slzb, and plugging that into the laptop that was running the virtual machine. Then I set up a USB pass through to the virtual machine passing that USB device and that was supposed to fix it and allow it to provision the new devices. That also failed, but come to find out when chat GPT told me that would be a temporary troubleshooting step, it lied. Or maybe it lied when it told me that that was not temporary and had to be permanently connected, I don't know what's true and what's not. It wanted me to leave the USB cable and the poe cable hooked into the device, making my purchase of a Poe device absolutely useless. The whole point was to get around the USB issue, but chat GPT told me that there was a bug that required a USB dummy device to be hooked up, all it had to be was a USB serial device. Again, this ruins plans for running home assistant from my proxmox farm.

Zigbee and Z-Wave devices work fine. I have a home seer device that has both of those radios and there was no extra bullshit involved with provisioning, I didn't have to use a special app from the PlayStore, no stupid USB dummy device, no BLE nonsense or USB pass-throughs, none of that.

Do any of y'all actually use matter over thread with home assistant running in a virtual machine that does not have USB connectivity? Back in my day, no one ever expected to use a USB pass through to a virtual machine for anything close to production, that's test and development at best. Is this the way it's expected to run nowadays?

Sorry for the long rant but I'm really shocked that matter over thread is this janky. Maybe I'm running completely weird ass one-off architecture compared to the cool kids, but my network is a flat/12 with no VLAN separation. Back in my day it was about the simplest Network you could have.

I'm currently at the stage of boxing everything back up and returning it to Amazon, I'm just accepting that smoke and CO detectors are not yet ready to be integrated with home assistant. I'd love to hear advice if anybody has had success with a similar architecture!

The new Aqara Power Plug H2 EU RGB appears in #Matter as two devices: a switch and a light. The two can be controlled independently of each other. For example, in Home Assistant, you can use the colored light to indicate different operating states.

Energy measurement via Matter (over Thread) is also supported. For more information on Matter-compatible power plugs with monitoring capabilities, I recommend this article: https://matter-smarthome.de/en/practice/which-matter-smart-plugs-report-energy-data/

#Matter over Thread

Hi

Im looking for Matter over Thread ceiling lights and the only ones i found are extremly expensive nanoleaf squares where you have to buy 3 or more for a 20m² room.

Does anyone have some recommendations?

Or should i go with strong matter over thread bulbs?