DoubleTapDownToParam56 behavior is not consistent

I have a few of the Blue Fan Canopy Modules installed (VZM36, firmware 1.01) and bound to Blue 2-1 Dimmers (VZM31-SN, firmware 2.18). I see the following behavior in all of them.

tl;dr: The “MinimumLevel 1” setting doesn’t constrain all operations to that minimum.

In the fan module, MinimumLevel 1 is set to 60 so that the light doesn’t get too dim. MinimumLevel is also set to 60 on the switch.

On the switch, “DoubleTapDownToParam56” is enabled, and BrightnessLevelForDoubleTapDown is set to “2”. My expectation is that the “2” will be constrained by the “60” minimum - it should go no dimmer than “60”.

If I double-tap down with the light already on, that’s exactly what I observe. The brightness reduces to the minimum I desired - it goes to the same level as if I had held down “down” to dim the light.

But if I double-tap down with the light off, the light comes on as if not constrained by the MinimumLevel - it’s very dim, like it’s going down to the unscaled “2”. To get it to the desired minimum, I have to increase the brightness beyond that minimum, then I can double-tap down to take it to the desired minimum.

Is it possible to configure it so that double-tapping always obeys the minimum brightness, whether starting from off or on?

Here are the relevant(?) configurations parameters:

  • Canopy Module
    • MinimumLevel 1: 60
    • OutputMode 1: Dimmer
  • 2-1 Dimmer
    • MinimumLevel: 60
    • DoubleTapDownToParam56: Enabled
    • BrightnessLevelForDoubleTapDown: 2
    • BindingOffToOnSyncLevel: Disabled (also tried Enabled)
    • OutputMode 1: Dimmer

I could list all the various combinations I’ve tried that also don’t work in one way or another, but the running thread is that BrightnessLevelForDoubleTapDown seems to scale according to the MinimumLevel 1 when activated from on, but not when activated from off.

Thanks in advance.