@bcopeland and @kkossev...I've got some updates for both of you. Over the last week, I've been creating a Hubitat Device Driver from scratch for the Inovelli White and tracked down the issue with Generic Switch/Buttons from a multi-tap perspective. matter.attributePath () method works fine for any single press button (00 → 01 edge = pressed, 01 → 00 = released).
To get multi-taps, hold, and release working, I had to use the matter.eventPath () method. This was not a fun adventure for a two big reasons: (1) for whatever reason the Inovelli switch does not use persistent subscriptions with Matter. It is constantly re-subscribing on its own (verified with Inovelli). This causes the second issue: (2) an Event subscription causes the device to send a backlog/history dump. I've worked around it by suppressing all Events for 5 seconds after a subscribe call is made. This workaround does what is needed to allow multi-taps to work. It's not ideal, but does allow the Inovelli White to be fully used in a Hubitat environment.
With the above said, Bryan or whichever @Hubitat_Staff member that is in charge of the Matter implementation, is it possible to get Subscribe Response Action Information (per spec 8.5.x) to be passed to device drivers? This is the missing piece that our drivers need in order to not use workarounds. Basically, it would tell the driver that the device is done with its backlog/history and that everything from that point forward is live. Basically, my ask is can Hubitat add "Subscribe Response Action Information" as a report that gets passed to the parse(description) routine or perhaps to its own method.