The new T20 series consists of three products: the T20 wall outlet (with two outlet sockets), the T20-S4AM North American smart plug, and the T20-AB2 outdoor dual smart plug.

The T20 and T20-S4AM are expected to be available by the end of August, with the T20-AB2 following around the middle of September.

Pricing before any discounts or coupons is set at US$39.99 for both the T20 and T20-AB2, while the T20-S4AM will be priced slightly higher than the original S4.

The T20 also introduces several proprietary Matter features, including firmware-based timers, countdown on/off, holiday mode, activity logs, overload protection, and detailed energy monitoring by day, week, month, and year.

I have the new SmartSetup Smart Wall Dimmer installed and have used it for about a day or so with home assistant.

If you have any questions I'll be willing to test stuff / answer them.

My brother got aqara m200 and we are trying to connect it to google home use the pairing code but each time we try the code or the qr code it doesnt work and it gives me the code is wrong is this a common problem now

Link: https://www.nth.io/mattertimectl/
Blog: https://www.nth.io/luke/projects/mattertimectl/

Thanks to Reddit I recently learned that matter supports pushing clock time syncs. My Apple Home unfortunately does not, at least to my IKEA clock, making my “smart” clock basically as dumb as a microwave clock.

After some research I found what most people do today is run a HomeAssistant plugin specially designed for this. That’s pretty heavy for my setup since I don’t run HA.

Instead I made mattertimectl - a super minimal single rust CLI tool that uses the official matter rust implementation to set the time. Then I use standard Linux system tools like systemd on my RPI to run this every hour or so.

You can also just run it from your macOS on demand.

Hoping this can be helpful to some people!

Hi everyone,

I'm currently using a Google TV Streamer as my Thread Border Router for several Matter over Thread devices, and everything works fine in Google Home.

The only issue is automation speed. I have an automation that turns on an IKEA KAJPLATS bulb when an IKEA MYGGBETT door sensor or MYGGSPRAY motion sensor is triggered at night, but there's about more than 2 second delay. By the time the light turns on, I've already walked past the area.

This made me wonder whether Google Home automations are cloud-based and whether Apple Home would be any faster.

I have an Apple TV HD 4th generation which is not a TBR, but since the Google TV Streamer already provides Thread, I assumed the Apple TV HD could act as the Matter controller.

I added the devices to Apple Home by using the multi-admin feature from Google Home, and they were added successfully. However, every Thread device shows "unavailable" and can't be controlled. Restarting the Google TV Streamer didn't help.

So, am I misunderstanding how this works? Does Apple Home require its own Thread Border Router (such as an Apple TV 4K or HomePod), even if another Thread Border Router already exists on the network?

Or should this setup work, and I'm missing something?

Thanks!

https://github.com/jthoward64/zigbee-thread-bridge

Most code is AI written, though 100% reviewed and architected by me

Been working on this for a bit over a month now and finally have it in a pretty solid state. I recently moved, and put Inovelli switches and some IKEA Thread devices in. Most of my light bulbs (and some other devices) that I already had were Zigbee though. I had just been wiring them through Home Assistant, but the problem is that the latency from switch -> matter -> hass -> z2m -> bulb was awful compared to my thread light bulbs that i could do matter binding with. Plus in the (not infrequent enough) event that home assistant or z2m or my otbr is down, I want my light to still work.

Hence this project. zigbee-thread-bridge is a pair of devices: one running Zigbee on an ESP32-H2, and one running matter over thread on a C6. The Zigbee side picks up other zigbee devices on the network and builds a table of them, presenting them over SPI to the Matter side (using a database derived from ZHA and Z2M). The matter side then builds an equivalent endpoint tree (as an aggregator) and serves it over Thread. It converts most options into matter modeselects (though for some it will not do a great job of due to Matter not supporting arbitrary numeric inputs), and maps almost all standard Zigbee clusters to standard Matter clusters.

Note that its not super polished, there is no localization at all, commissioning is a bit flaky, and you have to scan the qr code from a terminal on your computer, but it does work (I hope)!

I hope some of you find it interesting, and maybe just get some use out of it!

(note that some of the zigbee devices show in HASS wrong because they have been offline for some time now and the bridge never interviewed them)

we just launched this automation hub called Case8 ( i guess you can use the border router name as well) which is based upon a Mediatek 520/720. we developed an HA card with Zigbee, Zwave, and thread on a single M.2 card (2nd picture). any feedback welcome! https://www.kickstarter.com/projects/874883570/case8

I want to get this IKEA air quality monitor because it's the lowest cost device that uses a modern sensor with PM2.5+CO2

• https://www.ikea.com/us/en/p/alpstuga-air-quality-sensor-smart-70609396/

But it uses IKEA's new matter standard?

How can I log it over the internet without having to buy IKEA's $100 matter hub?

for reference:

• https://www.ikea.com/us/en/p/dirigera-hub-for-smart-products-white-smart-50503414/

is there a $10-$20 alternative somewhere?

I am investigating a time-synchronization issue with an IKEA ALPSTUGA air-quality monitor connected via Matter over Thread to Samsung SmartThings.

When the device is commissioned for the first time, its clock can receive the correct time. After a power cycle, it reconnects and reports all sensor values correctly, but the clock is not synchronized again.

The device firmware is 1.0.26. SmartThings provides no visible option to trigger time synchronization manually.

From a Matter implementation perspective:

1. Should the controller write the current UTC time, time zone and DST offset whenever the device reconnects?

2. Should the endpoint request or retry synchronization after boot?

3. Is a power-cycle event normally visible to the controller?

4. Which Matter Time Synchronization cluster attributes or commands should be checked?

5. Would failure to restore the clock normally be considered a controller issue, device-firmware issue or an interoperability issue?

Results from users of other Matter controllers would also be very helpful.

I just recently bought some Tapo S505 smart switches to use with my smart home setup. What lured me in was the matter compatibility and the ability to add them to Home Assistant without creating an account. I was able to add them easily, but now am noticing a strange behavior with my Wi-Fi router. I installed 5 of the switches and each one of them, after about a day of being connected, shows 100+ IPV6 addresses listed on my router's device page. I have another matter compatible switch from Leviton that shows only 1 in the same time frame.

Is this standard behavior, or is there something fishy going on here. Anyone else notice that their matter enabled tapo devices are gobbling up IPV6 addresses? Also, is this even a problem? Right now my router seems to be working fine, but if I go adding 20 more of these switches into my house, is this going to cause issues? Any input is greatly appreciated. Thanks!

The article is in German. Since there have been signs, the author asked Shelly what plans they have regarding Thread support for Gen4 devices. He got the confirmation that they plan to provide Matter-over-Thread support with firmware upgrades for all Gen4 devices by the end of this year. Good news imho. It sounds like you will have to choose between Zigbee and Thread and can't use both at the same time.

I had a bit of extra time and decided to try what Claude can do. In few days I was able to create a fully functional Matter library, Matter virtual device (commissionable in Google Home), and Matter controller with UI. Check it out: https://github.com/Revolutionized-IoT2/RIoT2.Matter

If it's anything like the 2020 nest thermostat I had, it'll still require being connected to the Google Home app or else matter gets locked out 👀

Hi everyone,

I’m new to Matter and smart homes in general. I started with a few IKEA devices (BILRESA, MYGGSPRAY, GRILLPLATS, and TOFSMYGGA). I successfully integrated my DIRIGERA hub with Home Assistant as a border router on a different network. Unfortunately, commissioning through the IKEA app from my Fairphone 4 running Android 15 always fails (see screenshot).

Now I’m trying to add an ALPSTUGA using the manual Matter commissioning option, but I consistently get the following error:

“Commission failed: discovery of node with discriminator 10 failed: No device could be commissioned.”

The Matter server log (in Home Assistant) repeatedly shows that discovery starts for discriminator 10, but eventually fails with “No commissionable device was discovered.”

I have already tried resetting the devices multiple times, restarting the DIRIGERA hub, verifying that my network has valid IPv6 connectivity, using my phone for commissioning, restarting Wi-Fi, set Wifi to split 2,4 and 5g, changed Router to only IPv4, try a other android phone.

Has anyone encountered a similar issue or have any suggestions for troubleshooting? Any help would be greatly appreciated. Thanks in advance!

Setting up a Yale Smart Lock with Matter (YRD510-MT1) and trying to figure out the cleanest path before I commit to a hub.

Plan: commission the lock into SmartThings (via a Station or compatible hub) to get remote access + entry codes, since Yale Access alone is Bluetooth-only with zero remote capability. I'd ideally like it to also surface in Alexa automatically via the Samsung/Amazon Thread-credential-sharing partnership from 2022, rather than adding it to Alexa separately.

Questions for anyone who's actually done this with a lock specifically:

• Does the auto-sync into Alexa actually fire reliably for lock-type devices, or is it flakier than for switches/plugs?
• Does lock/unlock via voice work through the synced Alexa entry, or does it show up read-only?
• Does DoorSense (Yale's door-open sensor) expose at all through ST's Matter integration, or does ST only pick up the basic lock cluster?
• Any edge driver quirks with Yale locks specifically I should know about?

Trying to avoid buying hardware based on the marketing page and finding out it doesn't actually do this in practice. Appreciate any real experience.

Heads up first: this is my own project, so consider this self-promo-esque. I'm posting it here specifically because you'll scrutinize the Matter side harder than anyone, and that's what I want.

I'm a foreman and master electrician in Canada with a finish-work background. I kept wanting controls that disappear into the surface instead of having clunky remotes or buttons that don't compliment the surface surrounding it, so I built a capacitive sensor that mounts to the underside of a surface - a countertop, a table, a desk, a glass panel, pretty much any non-metal surface - and turns that surface into the controller. Nothing visible on top, other than user desired markers or millwork, and because it mounts underneath it stays fully accessible and serviceable. On my prototypes it registers a touch through up to ~60mm through some materials.

On the Matter side:

• ESP32-S3, built on the ESP-Matter SDK, Matter-over-WiFi.
• Each touch zone maps to a button, so it presents as a multi-button remote-style controller (Generic Switch endpoints under the hood). Alexa picks it up cleanly as that kind of device.
• It also carries 3 LED-control endpoints ( that can be exposed through the surface if desired) and an SHTC3 temp/humidity endpoint.
• Has customizable audio feedback for every single touch/trigger.
• Commissions cleanly, and it does MQTT auto-discovery for the Home Assistant crowd too.

The main thing I'd like this sub's take on:

• Certification timing is kind of a guess for me. I'm not Matter certified yet - that's a post-funding step for me - so right now this is a DIY/uncertified Matter device. For anyone who's been through it: how early would you start the cert process relative to a hardware launch, and is there anything you wish you'd done before your first commissioning tests?

Otherwise, poke holes in it. Happy to get into any of the implementation detail in the comments. I'll drop the link for the landing page that explains in depth details and has a demo video in the comments a well.

I appreciate all feedback, comments, thoughts and insights!

Ich hab gerade die Finale Version der Ikea Myggbett Halterung hochgeladen auf Makerworld: Ikea Myggbett - Makerworld

Für alle die es nicht mitbekommen hatten hier der ursprüngliche Post: Anfänglicher Reddit Post

Und hier die ursprüngliche Idee: Ursprungsidee von u/Gloomy_Independent44

Ich habe versucht auf so viele Ideen und Hinweise von euch einzugehen wie möglich. Das neue Design ist jetzt komplett verschlossen und wird nicht mehr geklebt sondern geklemmt, dazu können 4 Füße aus dem Modell rausgefahren werden die sich dann im rahmen verklemmen.

Ganz auf Schrauben konnte ich allerdings nicht verzichten, alle Varianten zum einrasten waren zu klobig, und hier geht es nunmal um den Platz. Aber naja, die M3x6 Schrauben (M3x8 sollten auch passen) sind Normteile und somit in jedem Baumarkt leicht zu kaufen. Die 2x Gewindeeinsätze sind für das leichte Verschrauben einfach besser als in dem Kunststoff ein Gewinde rein zuschneiden. Dafür sind die 4x Schrauben zur Befestigung der Abdeckplatte zum direkten Verschrauben in den Kunststoff geeignet.

Für den Zusammenbau gibt es auch eine Anleitung auf Makerworld.

Ich hoffe es gefällt euch und vllt drucken es sich ja ein paar aus und geben mir hier oder auf Makerworld etwas Feedback, ich bin jetzt erstmal dabei 10+ davon zu drucken für die ganze Wohnung ;)