I'm having some of my Inovelli Red Dimmers incorrectly report scene buttons.
I have (what should be fairly safe) 6X up press to open a garage door set up in Button Controllers.
The problem is that this is being triggered by simply holding the dimmer in the up position (to raise the level of the dimmer).(upload://wH5Fsq7iqQ8zfAObzY5KhvZ0ISf.jpeg)
Here is a screen cap of my log, and the device page showing the last pressed button. What to do???
The Inovelli Red Series switches and dimmers do not support 6 taps in any direction; they max out at 5. Their button event naming and numbering is somewhat odd, but "button 6 pushed" as a Hubitat event corresponds to the real-world event of holding the paddle up. So, that is why you're seeing your app/rule get triggered when you hold the paddle up--that's just how Inovelli mapped these real-world actions to Hubitat events.
This is probably apparent now, but to be clear: chose a tap 2-5 up or down (buttons 2-5 pushed or buttons 2-5 held in Inovelli's event mapping, respectively) or the config button (button 7 pushed)--just any event that doesn't do something with the actual load the switch/dimmer is controlling.
I love it when the answer is so simple. Thank you for bringing me up to speed.
Just for future purposes in case someone stumbles on this thread, here's a KB article that outlines the button mapping across our devices:
Thanks @bertabcd1234 for the help on this!
Thanks for that Eric. Wish I had known about that (maybe it didn't exist yet) when I setup my first LZW36. I found what each did by observing logs, but that list would have saved me time.
I just wish the LZW36 wasn't so slow to control smart bulbs when using the Light Protection Setting. It's able to controls a standard (non-smart) LED bulb just fine when not using Light Protection, but as a button controller for a smart bulb, it's frustrating to have to wait 2 seconds each time a button is pressed before the light responds.
My first question to anyone would be does the light (Philips Hue connected via Hubitat Hue Integration) respond instantly from everything else, like the Inovelli driver page in the hub, or a Zigbee button controller?
It does indeed. Unfortunately, both of my LZW36 controllers respond with the same delay when pressing the buttons when Light Protection is enabled. I don't have any other Inovelli devices, but other owners here have said it is only the LZW36 that exhibits this delay issue. I do hope this can be corrected in a firmware update. It's an otherwise outstanding product, but that delay really doesn't win me any points with the family. 
Yeah, we need to do better at directing people to our Knowledge-Base. It's one of this years biggest projects (UI):
Hmmm.... we're working on enhancing the firmware, so I'm glad you brought this up.
Question for you -- Do you have any other Z-Wave scene controllers that you have that can test outside the LZW36?
Reason I'm asking is because it could be the Z-Wave to ZigBee conversion that takes some time? I'm honestly not sure as these small delays never bothered me (I'm not saying they're not bothersome, just that I think I've gotten used to them since I used to use Wink + GE Link bulbs and Tapt switches which had like a 8 second delay if they even worked 
)
I've tested the dimmer switch with 4x Philips Hue bulbs on a C5 and there's probably a 1-1.5 second delay before they turn on.
This is scene control with a dimmer and 2x Z-Wave bulbs and a lightstrip (about a 1 sec delay): Lightstrip-Bulbs.mp4 - Google Drive
I can see the ZigBee button controller as your Hue and the controller are the same protocol, but when you say the Inovelli driver page, what do you mean? I wasn't aware you could control your smart bulbs from the Inovelli driver page (I haven't played around with it in a bit, so maybe things have changed)?
Lol, well, we need to make sure you're getting points across the board, so let's see if we can get to the bottom of it.
Can you point me to some of the other threads where it calls out the delays? I'd like to figure this one out too as we're about to unload a bunch of technical docs on the manufacturer to improve our products.
Thanks Eric. I really appreciate your candor and your companies commitment to improving.
I don’t, so maybe my expectations are not inline with the capability. 
This was definitely a mistake and should have read “driver page in the hub”, meaning the driver of the device being controlled, not the Inovelli driver as I wrote.
I know I’ve responded to others that have commented on the same thing, but can only find one thread right now confirming what I am experiencing and suggesting it’s isolated to the LZW36.
Wanted to add, that if the response speed can be improved, having “released” events in the firmware for the dimmer buttons could allow smooth dimming of smart bulbs. The current scenario of, press and release, then wait for it to dim a set amount before pushing the dim up or dim down button again is a real bummer to use.
Download the Hubitat app
