Hi Phil- I always detect a key release I think? Let me do a test tomorrow and I’ll get back to you. Specifically on a BeoLink active?

You’re absolutely right Phil - just checked - pressing and holding LIGHT Step_Up_Continue does not generate a LIGHT_Key_Release when I release the key on my BeoLink active in Opt4. You get a key release after the light timeout is sent, but that’s not helpful as it takes around 5 seconds for that to happen. Another idiosyncratic ‘feature’ of the protocol!

If in the BLGW, I create a macro and I activate Capture, I see the Release Key:

Global/Bedroom/AV renderer/Beolab 4500/Light?Action=Key release&Command=STEP_UP

So, it's the BLGW that doesn't forward it to IP over the MLGWP protocol. 🙁

KEY_RELEASE commands just work fine on my BL actives and in all linkrooms and the mainroom (except the BL2000 room of course).

Tested right now on my BL active in option 4 in the office, sw 1.6, set to forward LIGHT- and CONTROL commands to MLGW, with non-navi BEO4 .

I`m using STEP_UP continue and STEP_DOWN continue commands to dim and brighten the lights driven by a KNX system. When I release the buttons after a long up/down command, dimming /brighten immediately stops. I can also see RELEASE commands in the Monitoring tool of my BLGW.

Hope this helps (?)

Stefan