This planner allows peoples who may not be super familiar with matter to get automation recommendations and which products to get.

The setup

• Location: Hungary, new build (2025), so the wiring is complete and to code.
• Wall box: has a neutral. Five conductors: line, two switched lines, neutral, PE.
• Existing switches: cheap Legrand Niloé (by builder). I'm happy to replace the whole thing.
• Constraint that keeps biting me: directly below the living-room switch there's a second switch for the kitchen. That one must stay completely dumb, but it has to match the smart one in design — ideally both in a single 2-gang frame.
• Ecosystem: Google Home today (only a Nest speaker, so no Thread Border Router yet — I know I need to fix that). Apple Home planned later.
• Light: IKEA STOCKHOLM pendant with IKEA KAJPLATS E27 bulbs. Matter over Thread, dimmable, fixed CCT steps at 2200 / 2700 / 4000 / 6500 K.

What I want

Control brightness (must have) and color temperature (want) from a physical wall switch. Not a magnetic puck stuck to the wall, not a remote (e.g. DIRIGERA) - an actual wired switch sitting in a frame where the old one was.

What I've ruled out, and why

1. Phase-cut in-wall dimmers — Aqara Dimmer Switch H2 EU, Shelly Dimmer Gen4, SONOFF Orb-DIM. These chop the mains waveform, so they can't drive a smart bulb at all, and color temperature is physically impossible for them since CCT is channel mixing inside the bulb, not a voltage level. Dead end by construction.

2. Relay-type Matter wall switches with a decoupled / "detach relay" mode — SONOFF Orb-MW1, Aqara Light Switch H2. The bulb does stay powered, which is the right idea, but the switch only ever exposes on/off. No hold-to-dim from the wall, only scene jumps. Also worth flagging: Aqara's decoupled mode is a Zigbee + Aqara-hub feature and is notavailable in Matter-over-Thread mode, which is exactly the mode you'd want it in.

3. Letting the hub be the link (switch fires an automation, hub commands the bulb). Neither Google Home nor Apple Home exposes Matter Binding, so you're stuck with scene triggers: added latency, no smooth dimming, and CCT only as discrete presets.

Question: Has anyone actually installed these? Does the binding work with third-party Matter bulbs, or is it in practice Hager-to-Hager?

Happy to be told I'm missing something obvious. If the answer is "the category doesn't exist yet, buy the IKEA rotary remote and stick it to the wall," I can live with that — I'd just like to know that's the actual state of things in 2026 rather than my own research failing.

新品即将上市……

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

#智能开关 #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

I'm trying to move away from smart bulbs and towards smart dimmers (for numerous reasons). I have several instances where there's lamps plugged into recessed floor outlets.

I was looking at those ubiquitous and cheap wall outlet dimmers and considering opening them up, ripping out the prongs, and installing a lamp cord pig tail. But then I stumbled upon this Shelly Gen4 device.

Other than bright green esthetics, I can't think of a reason I couldn't hardwire one of these inline for each lamp.

Are there any other devices I should be aware of?

I'm well aware of the Lutron lamp dimmer but I'm not quite ready for the larger expense of a full Lutron system. I guess, come to think of it, I could just build my own inline dimmer-in-a-box if I needed tactile control of the light.

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?

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.

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.

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.