How To Set Matter Reporting Interval Configuration?

[mocelet]

@Trakker2

You can look at the code here .

Thanks, we follow similar approaches. The problem with SmartThings is that, even if you don’t send / emit any event, the hub is processing the reports anyway to call the driver, generate logs, etc. and cannot keep up because they generate faster than the hub can process them.

If you create a colour transition that is especially spammy with WiZ as noted before, there’s no filter that will save the hub from being saturated. So, in this case, either SmartThings or WiZ have to fix it.

For levels, well, since it only updates when it changes, if it’s only one light it’s fine. If you’re dimming three lights from 0% to 100% in few seconds, the hub will be busy for a while.

[mocelet]

@mocelet

A user there says the Nanoleaf is not so “chatty” when it comes to updates while transitioning, I’m so curious that I’ve just ordered one

While I was not able to connect it directly to SmartThings and is going through Google Home border router, I can confirm the Nanoleaf is waaaaay less chatty / spammy. It’s actually usable because it does not flood the hub as much as WiZ and with a filter it’s quite manageable.

The question still remains, is WiZ not following the reporting interval or is SmartThings not configuring it?

[Trakker2 (kkossev)]

I can confirm that NanoLeaf have improved a lot their Matter devices in the latest firmware updates - March 20, 2024 (3.6.173).
Make sure you have the latest NanoLeaf firmware versions.

[mocelet]

@Trakker2

NanoLeaf have improved a lot their Matter devices in the latest firmware updates - March 20, 2024 (3.6.173).

That’s what I’ve been reading, but I must have bad luck. Even with the latest firmware, it might be my worst experience with a smart home product. Not only I just can’t make it pair to the Aeotec hub (that feels like a bug in SmartThings though), it’s also not stable with the Nest Hub 2 and its own app also has its share of bugs, showing the light as unavailable even if it’s working with the smart home platforms.

[mocelet]

Turns out Nanoleaf Essentials is also spammy when it comes to reports while transitioning, but instead of doing it when transitioning colours it does it when transitioning colour temperatures!

Here you can see the constant stream of reports during a 2 minutes transition from 4000K to 2100K, even if the reported value is the same. A report every 50-100 milliseconds that’s it’s not needed at all. At least that cadence does not saturate the hub when using a filter, but it’s still a waste of resources.

Line  6: 2024-05-03T10:09:00.800097806Z INFO Matter Dev  <MatterDevice: c0c8b96f-eb21-4bef-9b11-cbf51c44805b [4CB43E8A550818D6-BAEA1F5C7ECCFE32] (Nanoleaf)> received InteractionResponse: <InteractionResponse || type: REPORT_DATA, response_blocks: [<InteractionResponseInfoBlock || status: SUCCESS, <InteractionInfoBlock || endpoint: 0x01, cluster: ColorControl, attribute: ColorTemperatureMireds, data: Uint16: \x01\x2C>>]>
Line 11: 2024-05-03T10:09:00.852407389Z INFO Matter Dev  <MatterDevice: c0c8b96f-eb21-4bef-9b11-cbf51c44805b [4CB43E8A550818D6-BAEA1F5C7ECCFE32] (Nanoleaf)> received InteractionResponse: <InteractionResponse || type: REPORT_DATA, response_blocks: [<InteractionResponseInfoBlock || status: SUCCESS, <InteractionInfoBlock || endpoint: 0x01, cluster: ColorControl, attribute: ColorTemperatureMireds, data: Uint16: \x01\x2C>>]>
Line 16: 2024-05-03T10:09:00.944532139Z INFO Matter Dev  <MatterDevice: c0c8b96f-eb21-4bef-9b11-cbf51c44805b [4CB43E8A550818D6-BAEA1F5C7ECCFE32] (Nanoleaf)> received InteractionResponse: <InteractionResponse || type: REPORT_DATA, response_blocks: [<InteractionResponseInfoBlock || status: SUCCESS, <InteractionInfoBlock || endpoint: 0x01, cluster: ColorControl, attribute: ColorTemperatureMireds, data: Uint16: \x01\x2C>>]>
Line 21: 2024-05-03T10:09:01.029249348Z INFO Matter Dev  <MatterDevice: c0c8b96f-eb21-4bef-9b11-cbf51c44805b [4CB43E8A550818D6-BAEA1F5C7ECCFE32] (Nanoleaf)> received InteractionResponse: <InteractionResponse || type: REPORT_DATA, response_blocks: [<InteractionResponseInfoBlock || status: SUCCESS, <InteractionInfoBlock || endpoint: 0x01, cluster: ColorControl, attribute: ColorTemperatureMireds, data: Uint16: \x01\x2C>>]>
Line 26: 2024-05-03T10:09:01.097281973Z INFO Matter Dev  <MatterDevice: c0c8b96f-eb21-4bef-9b11-cbf51c44805b [4CB43E8A550818D6-BAEA1F5C7ECCFE32] (Nanoleaf)> received InteractionResponse: <InteractionResponse || type: REPORT_DATA, response_blocks: [<InteractionResponseInfoBlock || status: SUCCESS, <InteractionInfoBlock || endpoint: 0x01, cluster: ColorControl, attribute: ColorTemperatureMireds, data: Uint16: \x01\x2C>>]>

I guess it’s clear companies are still trying to get the basics of Matter right and transition times, animations, scenes, etc. is not precisely a priority. It’s amazing all the functionality contained in the Matter standard that probably most users will never use (or devices won’t implement properly).

Transitions in Nanoleaf for instance with current firmware are particularly unpleasant, as in stuttery instead of smooth. WiZ colour and temperature transitions are beautiful but saturate the hub when transitioning colours. I’ve not tried Tapo Matter lights yet.

We’re not quite there yet with Matter.

[mocelet]

Also got a Tapo L535E

It… has bugs not fixed in months.

The current firmware is from August last year . Will not obey transition times as mentioned few comments above unless they are long and, more importantly, 1% brightness does not work, the light reports the correct value but you can see the light itself is not changing even if you were at 100%. Nanoleaf in some low brightness levels will just turn off, but guess that’s better.

Regarding reports, it’s not too spammy, level reports in every change like WiZ, colour reports and temperature are spaced around 500-1000 milliseconds so they’re usable in long colour transitions like sunrise simulations and that stuff.

Minimum brightness is higher than Nanoleaf and the standard 806 lumens WiZ bulb, maximum brightness too (those 1055 lumens are real, close to the Nanoleaf).

I would say when it comes to the light, the Nanoleaf is better, it can go down to 2100K, the Tapo only 2500K and the minimum brightness is also lower (which is my usual complain about WiZ and, now, Tapo). At full brightness Tapo and Nanoleaf colours are even better than the WiZ 1500lm bulb (the bulky one).

[mocelet]

Hi @Luis_Humberto_Medina , thanks for the answers in the other thread. Could you ask the engineering team if they’re setting the minimum reporting interval when subscribing to level and color clusters?

As mentioned in previous posts, it’s actually an issue trying to use Matter transitions because every light I tried will spam the hub with reports and make it sluggish while it processes the queue of reports. For levels they usually report when the unit changes, so that’s a maximum of 254 reports, if the transition is long that’s not a problem because they’re spaced in time, if it’s short it is. However, in temperature or hue/sat transitions the amount of reports is overwhelming while the transition lasts and the hub can be minutes processing the queue even after the transition has finished.

I tried a 30 minutes temperature transition with a Nanoleaf Essentials and just trying to turn on another light would result in a 10-20 seconds delay because the hub was busy processing the constant stream of reports and took all that time to get to process the “on” event. Same goes with WiZ when doing a hue/sat transition, I even unplugged the light and the hub was still processing messages for few minutes.

[Andreas_Roedl]

[mocelet]

Thanks, it’s funny they mention “a reduced reporting interval”, I hope they meant the opposite . Their color temperature transitions spammed the hub with lots of reports every 50-100 milliseconds.

I believe they were also working, at least in the beta, in the “smoothness” of the transitions. Guess I’ll check it out eventually, at least in one of the bulbs.

The update I’m most interested in is the support for Matter scenes (both from Nanoleaf and from SmartThings of course).

Edit: Updated one, turns out they did not fix the spamming of reports while doing a colour temperature transition.

2024-06-17T20:33:15.342511871Z INFO Matter Dev  <MatterDevice: d7867317-725e-4586-bc81-e5c017efdba4 [4CB43E8A550818D6-1CEAB4B77970F400] (Ambiluz Nano)> received InteractionResponse: <InteractionResponse || type: REPORT_DATA, response_blocks: [<InteractionResponseInfoBlock || status: SUCCESS, <InteractionInfoBlock || endpoint: 0x01, cluster: ColorControl, attribute: ColorTemperatureMireds, data: Uint16: \x01\x90>>]>
2024-06-17T20:33:15.498810455Z INFO Matter Dev  <MatterDevice: d7867317-725e-4586-bc81-e5c017efdba4 [4CB43E8A550818D6-1CEAB4B77970F400] (Ambiluz Nano)> received InteractionResponse: <InteractionResponse || type: REPORT_DATA, response_blocks: [<InteractionResponseInfoBlock || status: SUCCESS, <InteractionInfoBlock || endpoint: 0x01, cluster: ColorControl, attribute: ColorTemperatureMireds, data: Uint16: \x01\x92>>]>
2024-06-17T20:33:15.632475871Z INFO Matter Dev  <MatterDevice: d7867317-725e-4586-bc81-e5c017efdba4 [4CB43E8A550818D6-1CEAB4B77970F400] (Ambiluz Nano)> received InteractionResponse: <InteractionResponse || type: REPORT_DATA, response_blocks: [<InteractionResponseInfoBlock || status: SUCCESS, <InteractionInfoBlock || endpoint: 0x01, cluster: ColorControl, attribute: ColorTemperatureMireds, data: Uint16: \x01\x94>>]>
2024-06-17T20:33:15.758910121Z INFO Matter Dev  <MatterDevice: d7867317-725e-4586-bc81-e5c017efdba4 [4CB43E8A550818D6-1CEAB4B77970F400] (Ambiluz Nano)> received InteractionResponse: <InteractionResponse || type: REPORT_DATA, response_blocks: [<InteractionResponseInfoBlock || status: SUCCESS, <InteractionInfoBlock || endpoint: 0x01, cluster: ColorControl, attribute: ColorTemperatureMireds, data: Uint16: \x01\x96>>]>

And they did not fix the smoothness of the colour transitions, at least not in Europe with our 50Hz mains.

[Andreas_Roedl]

At least the nanoleaf is quiet when idle. The L353E seems to announce it’s current state every few minutes.

Imagine having 20 of them…

[mocelet]

@Andreas_Roedl

At least the nanoleaf is quiet when idle

I updated all the nanoleaf lights, they’ve actually improved the report spam in minutes-long transitions. And I’d say they’ve fixed an issue with low brightness levels so nice job. Must be the light with best comformance to the protocol right now.

They still have to fix the smoothness of the transitions, level transitions for instance are step-by-step instead of a continuous transition and colour transitions (even in their own scenes in the app) flicker a bit. People usually experience the flicker in transitions in low brightness levels but I notice it even at 100%.

Meanwhile I also notified WiZ again about their issues like the interval when reporting, not turning on when they have to and wrong brightness levels too (they report a brightness but the light is in another).

[Andreas_Roedl]

Now I have to find a way to update the firmware. The nanoleaf app didn’t like the QR code generated by Smartthings but that was just my first try.

Maybe it’s easier just to order a spare bulb, do the update first in the nanoleaf app, reset it, add it to my thread network and do some bulb shuffling.