There’s an interesting new feature of unreleased 54.x firmware spotted here, for Matter, Zigbee and ZWave:
Using this functionality give a huge latency improvement for handling these capability commands which is important when a driver is handling several commands all at once (i.e. a routine is triggered that toggles a bunch of switches)
Looking at the code, it looks like the first event is actually handled by the driver which registers the native handler if available - and I guess the driver’s handler will no longer be called, otherwise it will send the commands twice.
Hopefully 54.x will bring more surprises, like Matter 1.3 support, fixed Scenes and Groups cluster (current ones are broken) or even bindings (this will probably not happen) so we can use Matter dimmers.
I’m sure it will reduce the popcorn effect a bit, just like custom drivers with non-native groups do: it saves all the time of looking for the driver, calling the handler, etc. for each device. It will probably still send the commands sequentially but faster.
Maybe for the labels, icons, etc. so they can be updated with the driver without needing a firmware update?
I was looking at that a day or two ago. It looks like for Zigbee and Z-Wave they have added an option when registering default handlers but as we have observed previously the Matter drivers haven’t been using default handlers.
Yes, I guess that means they’re not fixing the default handlers for 54.x I kind of understand it since Matter is new and evolving so pushing a new driver update is easier than having to update the whole firmware.
I kind of understand it since Matter is new and evolving so pushing a new driver update is easier than having to update the whole firmware.