One of the things that I am missing from my Insteon dimmers are the fact that when you tapped up or down the lights began dimming immediately (and if you double clicked them they just interrupted the ramp rate and went right to 0%/100%).
With all of the Inovelli switches even if you have the multi-tap delay set to 300ms there is still a noticeable delay between the button press and the lights starting to do something, which reduces the spouse factor significantly.
My desire is that when this feature is enabled when you click the switch up or down it immediately starts the dimming (or on/off) action, but waits the configured timeout before counting/sending the multitap event. This way you get the local action as fast as possible but still allow for multi-tap events to happen, really the best of both worlds.
This feature request actually kills two birds with one stone. In my opinion multi tap events should always turn the connected load on/off but also send the correct multi tap event. (Aka if you tap up 1 or 7 times the light should come on, and also send the number of taps)
Iām fairly confident Inovelli is the only modern paddle dimmer switch that doesnāt function like @sryan2k1 is describing, and I too find myself wishing for this behavior.
From a broader perspective: I think it important that Inovelli switches by default behave like all other similar switches on the market (familiarity eases adoption, aka spouse factor), but have the ability to expand as desired by the user to be as customizable as possible. The current multi-tap implementation is customizable, but implemented in a way that breaks the default expected behavior.
Requiring a delay for multi-tap events makes sense if the final action may have nothing to do with setting the dimming level. For example, I could assign various scenes to double- or triple-taps. These could be up or down switch presses, and starting the dimming process immediately in such case before the final action was determined would be undesirable. Of course, because the multi-tap command is simply sent to the controller the command could be for anything. This is a powerful feature, but requires a delay to determine if the switch is receiving a single-press command it is supposed to act upon vs a multi-press command that it is simply passing along. Unfortunately, this required delay is not the expected behavior a lay user (who has only ever had taps translate directly to dimming levels) would expect.
I therefore propose that there should be an option added to the firmwares to simultaneously disable sending multi-tap events to the controller and change behavior so that double-taps always go to the maximum or minimum dimming levels. This could be easily implemented by disabling the button press delay and multi-tap controller notification if either the ā2x Up to Maxā and ā2x Down to Minā parameters are enabled.