Have you tried changing the dimming speed? What kind of lights are you using? I am only using Philips Hue lights and for me the dimming works fine on both Z2M and ZHA.
I just found out that Z2M has a simulated_brightness feature which might help for the dimming, will need to check how to use it exactly.
For the double click in z2m, have you tried tapping it at different speeds? To see if it might trigger the double tap at a different speed. Z2M can have higher latency, even though for me I didnât notice a difference and it works on both with the 1-buttonâŚ
hi sorry for the slow respons.
- the dimming speed seems okay, i tried adjusting it but it did not change it.
Itâs not that it dims to quickly or to slowly, itâs just that it doesnât want to do the entire range from 0-100%, it seems more like it each times chooses an random range where it will dim between.
- i tried clicking quickly and slowly in the double click function, but it just acts as single clicks, this i can also see in the activity log of the switch, it just shows up as 2 single presses
- i have my whole house running on innr lights, those seem to work perfectly in HA (i read multiple fora and reddit posts before i chose innr)
I moved a second four gang switch from zha to z2m, here the double click doensât work too.
I wanted to make sure it wasnât an issue with that exact switch
It took some more time as it was hard to diagnose. But I tink I have nailed it now. It responds the same for my 1-button with ZHA and Z2M now. Update will be released soon.
New Update Available (2026.01.9)
Fix double-press detection, remove helpers, and remove adaptive lighting triggers
Breaking Changes:
- Removed helper requirements - blueprint no longer needs input_text helper for double-press detection
- Removed adaptive lighting auto-adjust triggers - adaptive brightness/color now handled by adaptive-lighting blueprint (schedule-based auto-adjust preserved)
Whatâs Fixed:
- Double-press detection now works reliably for both ZHA and Z2M using event bus architecture without external helpers
- ZHA double-press detection - removed command filter to allow event catching during mode: single blocking
- Z2M double-press detection - added elapsed field validation to ensure events within 300ms window
- Duplicate instance execution - changed mode from queued to single with max_exceeded: silent
Whatâs New:
- Silent max exceeded handling prevents error logs when buttons pressed too frequently
- Universal double-press support for all 4 buttons on both ZHA and Z2M integrations
Upgrade Instructions:
- Delete the input_text helper you created for v2026.01.8 - no longer needed
Iâll test it tomorrow.
I have noticed another thing in the previous build that we might need to take a look at.
I noticed that some lights are quite warm/yellow and some other are quite white/cold.
In the blueprint is an option to set the temperature of the light, but it seems that this doesnât effect anything.
I can set this to the warmest or the coldest as possible, the light keeps the same temperature (ofcourse i saved the adjustment and put the light out and back on again)
I think it has to do something with the blueprint, because when i adjust the lights manually (in the devices page) and use another switch (that is not using the blueprint yet) it turns on on the color i just set it too.
If i press the switch with the blueprint, it turns back to cold/warm
Have you set the Adaptive Lighting or Schedule Helper settings? Or are you using the Static option to use the settings that you can hard set in the settings? With all of them you also need to have the Reset to Defaults on Short Press On/Off enabled, otherwise they are ignored.
I used the Schedule Helper myself and moved to the Adaptive Lighting Scheduler blueprint when I released that, which works great for logical Brightness/Colour throughout the day/night.
Hi,
It tested the new update, but first iâll give an update about the temperature.
I toggled the set to default on short press off and on again and now this function works.
Adaptive lighting is something i have in my todo list to set up once i migrated everything to z2m and updated all switches to your blueprint.
Regarding the new update.
Iâm afraid it did not work.
Double click doesnât work and the dim function broke too.
Dimming down work, dim up doesnât work anymore
edit: this is only in z2m, zha seems to work fine
Did you check the new instructions for Z2M to enable Elapsed and Disable/re-pair if you have Simulated Brightness enabled?
For ZHA all functions work?
Zha seems to work fine in the last 2 (or 3?) iterations.
The upgrade instructions were âdelete the input helperâ so i deleted that one.
I donât use adaptive lighting, simulated brightness or anything else
Or do i understand it wrong?
Open the Zigbee2MQTT settings portion in the Blueprint.
It should show:
Important: Do NOT enable Z2M Simulated Brightness for Niko switches.
Leave simulated_brightness_delta and simulated_brightness_interval EMPTY in Z2M device settings. If already configured, you must remove and re-pair the device. The blueprint provides optimized dimming.
Optional: Enable Elapsed in Z2M Settings â Advanced for improved double-click reliability.
Canât find anything on any device with simulated brightness.
Looked in HA in the devices, looked in z2m in the devices, so i assume i did not set anything for it and it is emtpy?
Simulated Brightness is an optional setting in Z2M yes. By default it is not set. It is not visible in HA as an option.
The Elapsed setting is important for better double tap detection.
Oke, i did not adjust anything about brightness in z2m, so that should be fine
Did you enable Elapsed in the Advanced settings of Z2M and try the double tap again? As it is an extra value that is sent with each Z2M message so the blueprint can measure the time between taps.
This is fully handled by the blueprint, there is no way for you to see the double press in the raw messages from Z2M, as it simply does not exist there.
I enabled the elapsed in z2m.
Double click doesnât work.
And dimming also doesnât work like said in previous post
New Update Available (2026.01.10) Fix Z2M dimming stop detection for multi-button Niko switches
Whatâs Fixed:
- Z2M brightness dimming up now works properly for buttons 2, 3, and 4
- Added missing
value_json.brightness is not defined filter to 6 MQTT stop triggers (buttons 2-4, move up/down)
- Buttons 2, 3, and 4 now have identical Z2M stop detection logic as button 1
Upgrade Instructions:
- Simply re-import the blueprint and reload Automations
- All changes are backward compatible
- ZHA users: no changes needed, everything works as before
Thanks for checking. Can you check again with the new update released just now?
Hi i tested.
Dimming completly doesnât work anynmore (before dimming worked but dimming up diddnât anymore, now both donât work)
Double click doesnât work nether
I checked in the activity log, he registers the dim up/down action, he turns on/off the light 1 step, but there it stops, it doensât keep going up or down
New Update Available (2026.01.11)
Normalize Z2M to ZHA format for unified handling
Whatâs Fixed:
- 4-button Z2M dimming and double-click issues resolved through unified action handling
- Removed useless brightness filters that served no purpose
Whatâs New:
- Z2M actions now normalized to ZHA format internally (endpoint + command + move_mode)
- Single unified command mapping handles both ZHA and Z2M identically
- Eliminated complex 60+ line device-model-specific Z2M action mapping
- Major code simplification makes blueprint easier to verify and maintain
Upgrade Instructions:
- Simply re-import the blueprint and reload Automations
- All changes are backward compatible