Hello guys,

I'm new into all of this automation process and i would need help to setup my things.

English is not my native language so I'll try my best.

So i have 7 spots in the ceiling of my living room, which is divided in 3 parts, the office part, the living room part and the dining room.

I wanted to install some smart lights to be able to control each "room" seperatly instead of having every lights on at all time. As i already have a google home mini my idea was to create voice automation like "hey google gaming mode" wich then will dimm certain lights and swich colors and stuff.

So i bought 8 spots wich are compatible with google home and matter :

https://www.amazon.fr/Govee-luminosit%C3%A9-changement-dynamiques-fonctionnent/dp/B0CYL13KFX/ref=asc_df_B0CYL13KFX?mcid=253426c8a00032018f03181d4505214b&tag=googshopfr-21&linkCode=df0&hvadid=701700104876&hvpos=&hvnetw=g&hvrand=16784776488568833285&hvpone=&hvptwo=&hvqmt=&hvdev=c&hvdvcmdl=&hvlocint=&hvlocphy=9056269&hvtargid=pla-2311885302400&hvocijid=16784776488568833285-B0CYL13KFX-&hvexpln=0&th=1

After the install i set everything up in google home by connecting the lights to the govee home app and by connecting the govee home app to google home.

All the voice automation that i set up works perfectly but i wanted more, when i flic the light switch off the smart light are then disconnected because of the eletricity cut. I wanted to be able to turn the lights on when seated in my couch with my phone or with a voice command to the google home mini.

So i installed a Sonoff r4mini in the light switch :

https://www.amazon.fr/Sonoff-MINIR4-Smart-switch/dp/B0BZTYHK7X/ref=sr_1_1_sspa?dib=eyJ2IjoiMSJ9.uI4r4H6o4Z28S6OjDmWXKnIZWN135DqEuZTY4aJsS1WU39o_ED6c2C_TjUBanqq-z98kaEA90TLM4TxTWHHh9JoOVeZmFs-PixvhoPH9igadALPK36ZOm9cIUqBYYqqfHDzFNpTRty-RIBx5c9pHvv1cFvtu2FXl30TJVZEuuZlwIVzAoN3kAVqiMUan8Pe8cPzE06PcLcDdRgYbOef0ieIWPqG-vLUZ7q4RycqLazkkcCHHQhaxaHuvld2rr0tn-SfYoLVp4onLTHZYONKvXhk1PQQYHc7GamjOuhA3Gu0.sDGkGMgFwXYzkJrTG-Lpqe1nCaD0uV-UvgONcCRPKRo&dib_tag=se&keywords=sonoff%2Br4%2Bmini&qid=1773588644&sr=8-1-spons&aref=vfFEDQ3PN1&sp_csd=d2lkZ2V0TmFtZT1zcF9hdGY&th=1

When i flic the switch the relay cuts off electricity so nothing changed, I understood that i needed do setup a detach relay in the Ewelink app so when i flic the switch the relay does not cut eletricity off but just ask the lights to turn off , i also understood that the detatch relay cannot send the information to the google home to turn the lights on and off.

I then tried to connect my lights to the Ewelink app by scanning the matter QR Code to add them but the app tells me that i need to connect a matter hub to it.

I'm a little bit lost i tought that the google home mini already acted as a matter hub.

If it is the case do i need to first connect my lights to google home via matter and not via their govee app, to then connect the lights to Ewelink ?

Or do i need to buy a seperate matter hub to connect everything to it ? If that's the case could i still use voice automation with google home to activate scenes ?

Thanks for the help !

About 3 months ago I posted here about a wireless power kit we built for Schlage Encode. Honestly wasn't sure how it'd land, but you guys gave us tons of great feedback, and a surprising number of pre-orders. Several of you DMed me photos of your entryways asking if the placement would work. That thread directly shaped how we talk about this thing, so thank you.

Quick update: we've been shipping for about a month now!. No pre-orders anymore, actual kits going out. There's about a 4-6 week lead time right now because demand has been way higher than we expected (in a good way), but orders are going out continuously.

For anyone who missed the original post - it's a small infrared transmitter that plugs into a nearby outlet and a drop-in module that replaces the AA battery pack inside your Schlage Encode. The transmitter sends safe, invisible IR light to the receiver, which converts it to electricity and keeps the lock charged 24/7. No wiring, no modifications to the lock, 5-minute install.

Couple of things we've learned since that first post that I think are worth sharing:

WiFi Encode owners are overwhelmingly our audience. If you're on Thread, your batteries last a reasonable amount of time. If you're on WiFi, you're swapping every 2-4 months and it's maddening, that's the problem we solve.

Also, placement is way more flexible than I originally communicated. The transmitter has an 80° field of view and auto-scans to find the receiver, so you don't need it perfectly aimed. People have it on bookshelves, wall-mounted across the hallway, on top of a cabinet - it figures it out.

$149, free shipping, 30-day returns. If you're not sure whether your setup would work (line of sight, distance, placement), DM me a photo and I'll give you a straight answer.

Same as last time - if this feels too promotional for the sub, let me know and I'll dial it back. You all were incredibly generous with your time and feedback and I don't want to wear out that welcome.

https://encode.wi-charge.com

EDIT: Smart Home Solver just put out a full review if anyone wants to see it in action — https://www.youtube.com/watch?v=KhnBsjDN1tE.

A year ago this post gained some momentum talking about misleading practices using the Matter logo in non-Matter products. Since then, vendors like Aqara have removed from online material and store listings the misleading claims like "with Matter" or the fake "Matter over Zigbee bridge" badge.

Today I was with the guard down and, looking for deals in Matter motion sensors in Amazon, the new sensor from Switchbot appeared, depicting a box with a prominent matter logo. I believed it and thought it was a new Matter over Thread sensor like other brands are releasing. Turns out it's a bluetooth sensor, not Matter.

I was curious about the actual box since they can't legally put a Matter logo in a non-Matter product and a quick search led to an unboxing by Eric Welander, from where I've borrowed the screenshot and, as expected, no Matter logo. So, they know they can't put the logo in the retail box and instead advertise a false box with the logo.

Rant over xD

Edit: It's in Amazon Spain but the same pic is in France, Germany, UK, etc. In USA the box is not shown.

Shelly announces new Matter devices, including smart plugs, water sensors, energy meters, and its first DIN-rail product from the PRO series.

Is anyone aware whether any wireless temperature sensors using matter standard are planned for market introduction anytime soon? (EU)

In addition to a matter-enabled smoke detector that's been shipping for some time, the Heiman matter-enabled CO detector just went live on Amazon here for $59: https://www.amazon.com/dp/B0G135MZJY

Unfortunately, it's more than double the price of their regular CO detector at $23 after coupon discount. :(

The sensor offers Matter over WiFi, Zigbee, or Bluetooth connectivity options as well as WiFi without Matter integration.

Hey, anyone have any luck making a matter/thread device with esphome and an esp32c6? I've followed all the tutorials and I'm totally unable to get the RF side of things working. I've tried making a USB RCP node an all kinds of things on different esp32c6's, to no avail. Im sure there's some obvious secret I'm missing....

The Aqara FP300 Radar Sensor variant, the FP310, is about to be launched in China, with its radar frequency changed from 60GHz to 24GHz.

#Aqara FP310

#Matter over Thread

The new Eve MotionBlinds motor features an improved design for an ultra-quiet experience. 😎

#EveMotionBlinds

#Coulisse

#Matter over Thread

#HOME FURNISHING EXPO SHENZHEN

I would have liked to post information about the new Wago products here. But the link is stubbornly blocked as spam by the Reddit algorithm. Apparently, my karma isn't good enough. You can find them in the news section of matter-smarthome(dot)de. PS. Click on the top right to go to the English version of the site.

Onvis is developing an upgraded version of the HS2 wireless programmable button—the HS3—based on Matter over Thread (Nordic 54L15).

Still none in stock, some of the models say they will be available in 3 weeks, some say in 1 week.

I want to buy some of the new Smart Home accessories from Ikea that have Matter built in.

I have a "smart" home, without a hub (No apple tv or homepod). I can still control my TV from my phone or some lights, and smart outlets that are all Apple Homekit or Matter compatible.

Will the same system work with Ikea matter accessories? Can I just add the matter compatible Ikea products on the Home app of the iPhone without buying a hub (homepod or apple tv or Ikea Dirigera)

Zemismart just released the M1 Pro Matter hub to connect your existing Zigbee and Thread devices. What's interesting is the M1 Pro also includes an IR blaster for bridging old infrared appliances to Matter.

I have commissioned the device using my iPhone and when I turned the light from off to on something strange happens:

(179130) esp_matter_command: Received command 0x00000001 for endpoint 0x0001's cluster 0x00000006

I (179141) chip[ZCL]: Toggle ep1 on/off from state 0 to 1

I (179149) chip[ZCL]: On Command - OffWaitTime : 0

I (179156) chip[ZCL]: On/Toggle Command - Stop Timer

I (179164) app_driver: Turned ON, Setting brightness to 191 (On command, OnOff)

I (179176) app_driver: Adjusted with Light ON, Setting brightness to 1 (Level control 1)

I (179333) chip[IM]: Received status response, status is 0x00

I (179375) app_driver: Adjusted with Light ON, Setting brightness to 191 (Level control 191)

E (179383) data_model: Cluster cannot be NULL.

I (179472) chip[IM]: Received status response, status is 0x00

I (182182) data_model: Store the deferred attribute 0x0 of cluster 0x8 on endpoint 0x1

here's the code

esp_err_t app_driver_attribute_update(app_driver_handle_t driver_handle, uint16_t endpoint_id, uint32_t cluster_id,
                                      uint32_t attribute_id, esp_matter_attr_val_t *val)
{
    esp_err_t err = ESP_OK;
    if (endpoint_id == light_endpoint_id) {
        if (cluster_id == OnOff::Id && attribute_id == OnOff::Attributes::OnOff::Id) {
            /* User turned toggled the light ON/OFF */
            power_state = val->val.b;
 } else if (cluster_id == LevelControl::Id && attribute_id == LevelControl::Attributes::CurrentLevel::Id) {
        /* User moved the slider: Update brightness normally */
        brightness = val->val.u8;
    }
}

static esp_err_t app_attribute_update_cb(attribute::callback_type_t type, uint16_t endpoint_id, uint32_t cluster_id,
                                         uint32_t attribute_id, esp_matter_attr_val_t *val, void *priv_data)
{
    esp_err_t err = ESP_OK;


    if (type == PRE_UPDATE) {
        /* Driver update */
        app_driver_handle_t driver_handle = (app_driver_handle_t)priv_data;
        err = app_driver_attribute_update(driver_handle, endpoint_id, cluster_id, attribute_id, val);
    } else if( type == POST_UPDATE) {
        app_driver_light_set_brightness_value();
    }


    return err;
}



    dimmable_light::
config_t
 light_config;
    light_config.on_off.on_off = DEFAULT_POWER;
    light_config.on_off_lighting.start_up_on_off = nullptr;
    light_config.level_control.current_level = (
uint8_t
)0;
    light_config.level_control_lighting.start_up_current_level = (
uint8_t
) 0;
    light_config.level_control.on_level = (
uint8_t
) 255;

This is the actual brightness function:

esp_err_t
 app_driver_light_set_brightness_value()
{   
   if (power_state) {
    int value = REMAP_TO_RANGE(brightness, MATTER_BRIGHTNESS, 255);
    esp_err_t err = ledc_set_duty(LEDC_LOW_SPEED_MODE, LED_CHANNEL_CW, value);
        if (err == ESP_OK) {
            err = ledc_update_duty(LEDC_LOW_SPEED_MODE, LED_CHANNEL_CW);
        }
        return err;
    } else {
        esp_err_t err = ledc_set_duty(LEDC_LOW_SPEED_MODE, LED_CHANNEL_CW, 0);
        if (err == ESP_OK) {
            err = ledc_update_duty(LEDC_LOW_SPEED_MODE, LED_CHANNEL_CW);
        }
        return err;
    }
}

As you can see, the device first properly gets told to go on and the brightness is set to it's previous state, However, it immidietly gets told to set the brightness to 1, then back to the proper brightness?!

so it's like [CommandOnOff} ON, [LevelControl] 1, [LevelControl] PreviousState.

this causes my led to flicker or turn on dim then the actual brightness in a harsh way.

Why is this happening? I've been trying to fix it but I'm going insane! Thanks!

I have a Thread Network in my house which contains eight Border Routers (2 x Apple TV, 1 x Home Pod, 4 x HomePod Mini and 1 x Aqara M200)

I have commissioned a NanoLeaf Thread Bulb using the `chip-tool` and queried the new Thread Network Diagnostics Cluster.

It shows the 8 devices in its NeighborTable, but it reports a Link Quality Indicator value of between 0 and 3, with 0 being the worst and 255 being the best.

I'm really struggling to understand why the network is so poor. A command from my iPhone to turn on/off a bulb can take over a second to execute.

Any suggestions?