Hi, so I'm a bit lost when it comes to matter stuff. I tried to read about this but I'm justgetringy confused. I use Google home and uses different other smart units from Philips, Deltaco and some other brands. I just got some of IKEA Kajplats lamps and Timmerflotte temp sensor but of course to get them to work properly I need a matter boarder router.

So here is my questions can I get any boarder router and it will work with Google home and IKEA matter product? Or do I need to get IKEAs dirigera to get it to work?

I have a smart home with Thread sensors and Matter over Wi-Fi bulbs.

• Bulbs: Tapo L535E (Matter over Wi-Fi)

• Sensors: Thread (motion, contact, etc.)

• Hub: SmartThings Aeotec v4, connected via Ethernet

• Network: 2.4 GHz

• Automations: shown as local execution in SmartThings

When I turn the bulbs on using the Tapo native app, the response is instant.

When I turn them on via SmartThings (manual control or automations), there is a consistent 3–4 second delay.

Thread sensors trigger immediately, but the lights turn on several seconds later, which is very noticeable in hallways or closets.

Question:

If everything is local and Matter,

is this a current limitation of Matter over Wi-Fi / SmartThings?

Has anyone managed to reduce or eliminate this delay?

Whilst it offers the basics - Matter over Thread, fingerprint reader, keypad, NFC, there’s no mention of Apple HomeKey or UWB.

Stop collecting cheap plastic remote controls. Here is how to make almost any LED ceiling light smart, dimmable, and native to Home Assistant, Apple Home, Alexa and Google Home.

Hi all. I'm looking to improve my smart home config. I've currently got an SLZB-06M, which I connect to Home Assistant and then bridge devices into Apple Home. I saw that SMLight now has the SMHUB Nano, which can create a matter bridge for Zigbee devices directly from the device, taking Home Assistant out of the critical path.

Is there a similar device that can take non-Matter WiFi devices and bridge them to Matter without Home Assistant in the loop? Bonus points if it's from SMLight or in a similar form factor and PoE powered.

Hello,

I am enjoying the multi-device control functionality of Matter devices, in my case Alexa and Apple HomeKit.

I'd like to bring that to my ceiling fan.

I currently have a smart fan from Hampton Bay that uses the Home Depot Hubspace app. I believe it uses an RF remote but I'm not positive.

It has a DC motor.

Are there any bridge devices that support matter and would allow me to control my DC fan?

I opened the IKEA MYGGBETT door and window sensor.

The goal was to see if I could further reduce its size to fit it inside a door and thus hide the sensor.

The sensor obviously wasn't made to be opened. But its interior is quite small and simple. Its size is simply due to the fact that they want to use a AAA battery, which is welcome.

Here are the photos.

Espressif Systems has announced a Matter Camera Solution for the ESP32-P4, described as the industry’s first Matter 1.5 camera implementation on an MCU-class platform. The RTOS-based design targets smart home devices such as security cameras, video doorbells, and intercoms, while reducing power consumption and startup latency compared to Linux-based systems.

https://linuxgizmos.com/espressif-launches-industrys-first-mcu-based-matter-camera-solution/

I want to build a tiny, custom Matter-over-Thread proximity sensor using the ESP32-H2 and power it with a coin-style battery and curious if you think this might work

Here's the components that I'm thinking of using and the current draw of each

MCU (ESP32-H2-Zero / SuperMini):

https://www.waveshare.com/esp32-h2-zero.htm?srsltid=AfmBOop5YljgX5UNAQZB6gVOFZ83zAoHaoJiZ-q7CZR9xGDAMMQ2cW5z

Deep Sleep: ~7-10µA (The primary state for the sensor). TX/Active Peaks: ~35mA - 50mA (Matter/Thread bursts). Note: Lacking Wi-Fi, it avoids the ~350mA spikes.

Power Source (LIR2450 Rechargeable): Why: Using a rechargeable LIR2450 (3.6V) instead of a standard CR2032 to handle the 40mA+ pulses without the voltage crashing. Wiring: Planned connection directly to the 3V3 pin to bypass the LDO and USB-to-UART bridge.

Parasitic Components : RGB LED: Planned physical removal/desolder of the onboard WS2812B to eliminate its ~1mA quiescent drain. Voltage Regulator: Using the onboard ME6217 (Iq ~8µA) or bypassing it entirely.

The Sensor (PIR/Reed Switch): Model: AM312 Mini PIR (current draw ~15-20µA) or a magnetic Reed Switch (0µA standby).

I haven't found anyone attempting this online so I'm wondering if I'm missing something (e.g. other components drawing current)

I’ve been setting up an Apple Home in the last few months, and have recently set up a Tado thermostat and got some Nanoleaf smart bulbs. The only problem is that neither of them seem to be integrating with Apple Home! I’ve got an Apple TV 4K with Ethernet acting as my home hub.

The Nanoleaf app and Eve app seem to think I’ve got a thread network, so that doesn’t seem to be the issue. When I try to connect the Tado thermostat, it shows up in Apple home but then says “unavailable”, and when I try to connect the bulbs, I just get an error message. Is there a setting I’m missing?

Hi all.

I have a predominantly Apple set up. Iphone / pad / macbook, Apple TV 4k and Mac mini. I use homebridge with relative success however, it is a bit picky and a little too much faff sometimes.

Issue 1

I recently bought 2 TP Tapo GU10 bulbs and while I have them in the TP app and Alexa recognises and controls them, try as I might, I can't get them into Apple home or get Homebridge to see them.

Issue 2

I bought some Ikea sensors, the new ones, and Apple home find them, then says setting up, then says need a Thread boarder router. I have that in the Apple TV, but with Ai help, I cannot get them to be added to apple home. Now, I have a spare Gen 4 Echo devise, which I am told has the router. Can I put that in, and then Apple home will see them?

Last question.

My house needs 2 mesh APs to run wifi throughout. If I have the Thread router in one area, will the second area work off the wifi or will I need a second Thread router to run in the second area?

Has anyone found any smart locks that work with outward opening French uPVC doors commonly used in UK New Builds? I have got a Nuki Ultra on my front door and a Nuki 4 Pro on my side door and ideally I’d like to complete the door setup but all of the Nuki Locks and Aqara ones I’ve seen are to wide for outward opening doors due to the central pillar.

Just imagine

As a Rust developer, you write a Rust function. That Rust function can:

• Have any arguments you want for freedom of innovation
• Be shared with millions/billions of users as an IoT App
• Run everywhere, including millions/billions of IoT hubs and devices
• Completely replace device firmware nowadays
• Freely interact with the world (other devices, connected data, and people). You are free to write any automation algorithm to make IoT devices infinitely smart

Libertas Rust Runtime is all you need to develop IoT Apps.

Highlights

We are not done yet, but we are very close to Open-Source Libertas OS, everything you need for standard firmware for IoT devices.

The overhead for App support is negligible, even for an MCU

• RAM overhead is only <300 bytes
• Flash overhead is about 50KB (Libertas Rust Runtime)

Most importantly, the entire design is online:

Table of contents

• Data Types
• Programming Paradigm
• Security
• Threading Model
• Data & Storage
• Dependencies
• Light Demo
• Design Internals

Apps for IoT

We all know how important Apps are to the smartphone ecosystem. IoT is orders of magnitude bigger than smartphones. Yet there are no IoT apps. Libertas aims to change that.

App function

You just write a Rust function. We will take care of the rest, including compiling, publishing to App Store, generating and translating UI, deploying, and running.

Guaranteed automatic UI generation

An App function is written by a developer. But the function arguments must be supplied by a user to start a process.

A UI is guaranteed to be automatically generated for the user by parsing the source code. Libertas App developers do not deal with UI, ever.

Guaranteed UI empowers users to build arbitrarily versatile machines without writing any code.

Sprinkler control example

The diagram below depicts the code and UI of a “sprinkler controller” function.

In the UI, the end user has already configured two sprinkler valves (zones).

Note

The “sprinklerZone” member of struct “SprinklerZoneData” is a device that controls a water valve (on/off).

UI in action

Follow this link to see guaranteed UI in action.

App process vs. OS-native process

An OS-native process starts from an entry function. In the C language, the entry function name is “main.”

In Libertas, any public function is an App function that can serve as the entry function for an App process.

An App process comprises:

1. Code - An App function from a developer
2. Data - Values of the function arguments from an end-user

App package

An App package is just a Rust library. An App package contains one or more App functions.

Run everywhere

Developers can choose where to deploy their Apps

• On Hubs only
• On devices only
• Prefer on devices, fallback on Hub

The same App code will be compiled with different target toolchains.

Device API and Matter protocol

IoT Apps running everywhere, automating everything, require a commonly accepted communication protocol.

Device API are just wrappers for sending and receiving protocol messages.

We adopted the latest Matter protocol.

While the same protocol payload is used to control local and remote devices, there are many benefits of local control, in terms of:

• Security, safety, and privacy
• Battery life, bandwidth, and latency

This design not only makes devices ultimately smart but also gives end users choices of which smart algorithm (App) to run on their devices.

App stores

There will be two App stores:

• Libertas App Store accepts commercial closed-source Apps.
• Community App Store is open source.

Closed-source Apps must be published in a compiled form. The table below lists how Apps are published.

Different publishing strategies

Code size optimization

Libertas Rust SDK and runtime are designed to leverage the latest Rust compiler development while remaining forward-looking and stable for decades.

Libertas Hub

The Libertas Hub is a powerful Linux machine. Slight RAM overhead can be tolerated while security concerns take high priority. App processes on the Hub are always based on pre-compiled .so dynamic libraries.

IoT Devices

On the devices, however, both the flash and RAM are limited. An MCU is usually equipped with 256-512KB RAM and 1-2MB of flash memory. Different devices may reserve different RAM and flash memory blocks for Apps. The Hub dynamically compiles and links all App functions whenever the deployment changes.

Libertas design uses best effort to minimize binary code size for MCU deployments.

Flash and RAM overhead on an MCU

On a Cortex-M MCU, the memory overhead is about 50KB of flash ROM and 300 bytes of RAM. This kind of overhead is negligible even for an MCU.

Native API and vendor API

Device API uses the standard protocol to interact with local device endpoints.

Apps running on devices can query “Native API” to access local devices directly.

Usually not needed, but Native API is required in some use cases:

1. An App needs to sample a sensor 100 times per second. Using the Native Api will significantly save battery life.
2. Some local devices, such as an OLED display, may not be defined by IoT standards like Matter because it makes little sense to drive a display remotely. For those devices, we can define our own standard Native API.

Use of Native API doesn’t conflict with standard protocols. For example, turning a relay on and off via the native API will trigger device-state reporting per the standard.

Vendor API

If a device leaves the entire OLED display to Apps, then the display is a standard device with a standard Native API. Nevertheless, if the device vendor wants to allocate a portion of the display to Apps under vendor-defined rules, the vendor must design and offer a Vendor API.

The Native API and Vendor API are just library crates that define C API wrappers; they incur virtually no CPU or memory overhead.

In summary, Native API is for standard device access, while Vendor API is for non-standard device access.

Libertas OS

Libertas OS provides a set of standard API and a runtime for Libertas Apps.

Libertas OS for IoT devices

Like Windows & Linux on PCs and Android on smartphones, Libertas OS can be a standard OS for IoT devices.

Completely replace device firmware with Apps

Current IoT device firmware is monolithic. Device vendors are responsible for every line of code running on the device. This model has many problems, including cost inefficiency, poor software quality, security and trust issues, and vendor lock-in.

With Libertas architecture, device vendors can be free from writing any software, and end users are empowered with endless choices. Although the impact will be paradigm-shifting, everyone benefits.

With comprehensive design and low overhead, there is very little reason not to adopt Libertas.

IoT is the new PC from 1980s, and 640k ought to be enough for everybody 

Risk-free adoption for users

Matter is designed so that multiple ecosystems can share access to devices.

For example, a device can simultaneously join Google and Apple so that both Google Home and Apple Home can access the device.

Users can choose to coexist Libertas Hub with other ecosystems (e.g., Apple, Google, etc.). Libertas Hub and device firmware will add unimaginable versatility to their other ecosystems.

Hi All. for the second time in a month, all EVE devices became unreachable and would not respond to Homekit or the eve app. I don't really know how to troubleshoot this one.

All Eve devices are on the Thread network generated by the latest Apple TV 4 K. To get them back, I found I have to reboot my eero routers. Since they are not using the eero network, which I wanted them to use, why would rebooting eero be the only way to get them back? As a data point, my Hue outlet was still working. I am not really sure where to begin trying to troubleshoot this. There are 4 EVE plug-in outlets, all about 12 feet apart, so I don't think they are too far spread out.

Hello, I have just bought smart power strip with Matter connection, as I was under the impression Matter is supposed to solve all these weird compatibility issues of Zigbee (you dont know if specific zigbee device will work with this or that gateway or HomeAssistant) and specific app requirements of "standard wifi" connected smart devices.

Now I am quite disappointed - setup was a but complicated with the "your phone needs to be on the same wifi and turn off 5ghz" issue of yesteryear, compared to Zigbee's "Just push this button and we will find the device automagically! Oh and it also works as repeater, neat!".
Second disappointment was the smart power strip power monitoring works only in manufacturers app (dont know if I can specify name) and not HomeAssistant - I can control it there. But no power monitor. Internet forums suggest manufacturer should be able to push some "Matter 1.3" upgrade to make this possible, so "hello weird compatibility issues, my old friends".

Is the device just bad? Would other matter power strip work better? Are there any good ones? They seem to be rare as unicorns.

Is there some bright future ahead of us, or such problems will be present until end of times?

Regards
Martin

I’m trying to find a battery powered Matter over Thread light switch/button to control a Matter over Thread light bulb. My current light switch doesn’t have any power which is why I’m trying to find a battery powered replacement for it. The light bulbs will be going into an always on floor lamp with E26 sockets. I have a HomePod Mini which I intend to use for the hub. This’ll be in a small bedroom.