-
-
Notifications
You must be signed in to change notification settings - Fork 1.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
OSRAM Switch Mini - holding up not recognised? #13592
Comments
This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 7 days |
Unstaleing |
This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 7 days |
I have 2 of those switches. Both behave the same: Holding up works for me, but not holding down.
|
I used the "reconfigure" button in z2m for each of the remotes after pairing it to z2m.
Before that, it was something like this:
Fixed for me. |
What happened?
I have the OSRAM Switch Mini (https://www.zigbee2mqtt.io/devices/AC0251100NJ_AC0251600NJ_AC0251700NJ.html) and have set this up in Zigbee2MQTT with Home Assistant
I've tried both Legacy and non-legacy but for some reason a hold on the top button doesn't seem to report anything
I'm assuming it should report the opposite of the down button and therefore
brightness_move_up = up long press brightness_stop = up long press release
For reference, I've tested out what is reported and I get the following overall:
on = Up (short)
off = Down (short)
brightness_move_to_level = middle (short)
color_temperature_move = middle
nb. both trigger (colour slightly after)
move_to_saturation = middle (long press)
hue_move = middle long press hold
hue_stop = middle long press release
brightness_move_down = down long press
brightness_stop = down long press release
What did you expect to happen?
No response
How to reproduce it (minimal and precise)
No response
Zigbee2MQTT version
1.27.0
Adapter firmware version
20220219
Adapter
Sonoff Dongle 3.0
Debug log
No response
The text was updated successfully, but these errors were encountered: