Do you have the format fro using custom action "SetColor"?
I have 8 of these bulbs in my bathroom. They are reporting as spammy.
I suspect that rather than turning on/off. They report like this...
level 1
level 2
level 3
...
level 94
level 95
level 96
level 97
level 98
level 99
level 100
This jams up hubitat and my processor goes to severe...
I'd suggest that the matter driver is updated to ignore these reports somehow.
1 Like
Here is a log from one of the bulbs. I can't send any commands from hubitat to the bulb as the queue is full.
I'm guessing that this is a queue that holds the outbound matter commands.
Wow, it is more spammy than the spammiest Tuya devices I have dealt with ...
You got my attention!
1 Like
Between my chatty Tuya devices and these, my hub is ready to surrender.
1 Like
Besides the level, what else is sent as hub events too frequently?
Hue, saturation, color?
That's enough, turn all the logs off.
I noticed when I use hubitat to turn lights off, it fades thru every level. when I use google home, it instantly turns off.
1 Like
Same, except, I used Alexa.
Reporting for Matter RGBW bulbs will be reduced in next build
2 Likes
I'm really confused by this one....
These bulbs are reporting events from a webcore piston--I paused the piston and it is still doing it.
55 events on one bulb today (built-in generic RGBW bulb matter driver)
Oddly, when Alexa turns on and off the bulbs or changes colors, there is NOT such a huge uptick in events. So, this does NOT seem to be a reporting issue. Maybe a confirmation issue?
Take a look at this bulb that is rarely used...
I turned it on and off 5 times in Alexa (where the bulb was on-boarded)
Hub usage looked like this...
Then I turned it on/off 6 times using hubitat
And look at these stats!!!
Then I switched to that alpha driver from @kkossev ...
And there was really no difference in hub traffic...
I hope that this information was useful. If not, let me know what I can do and/or provide.
It seems like upgrading to 2.3.8.117 the Matter bulbs have quieted down.
Same action BEFORE upgrading...
Same action AFTER upgrading..
16 events vs 3 events.
Good Job Developers.
I still have some more testing, but this looks promising.
1 Like
Well, I was hopeful, but wrong...
These devices once again ate up all my hub memory and processing...
I'm going back to sending open/closed virtual contacts to Alexa and letting Alexa turn on an off the lights. Of course if my internet is down (rarely) or Alexa is down (even more rare), I will be in hot water when the bathroom lights don't turn on. 
1 Like
These 31K Hub actions are not normal.... Have you checked whether you are not creating some kind of loop from your WebCoRE piston ?
1 Like
Can you return only one of these bulbs (that has the slightest chance to affect the WAF) paired via Matter directly to the HE hub for further tests?
1 Like
I've been reading the release notes waiting for this feature. I just checked. On the App, adding a new device seems that the instructions are saying to pair with Alexa/Google/Apple first.
Am I (as usual) missing something?
My plan is to move the matter bulbs to HE once adding devices is supported. If there is a beta, I'd be glad to participate.
I have probably misunderstood what you are doing... No, HE still can not act as a Matter commissioner. You still need to pair it first to Alexa/Google/Apple, etc... (I can add Zemismart M1 hub to the list).
So what was your last change? The bulbs are still paired to both Alexa and HE, but you are not controlling them from HE - using virtual switches to Alexa instead? But the bulbs are still paired to HE, although not used for control?
