Github Gist: osram_switch_mini_zigbee2mqtt.yaml · GitHub
Main features
Define actions for each button press type (up, up_hold, up_release, down_release, circle_release, circle_hold, down, down_hold, circle_click).
Supported device
This blueprint supports the OSRAM AC0251100NJ/AC0251700NJ device through Zigbee2MQTT only.
Prerequisites
You need to find the Zigbee2MQTT topic name for your device, for instance zigbee2mqtt/Osram Remote Kitchen and set this as the mqtt_topic input variable.
Blueprint
Click the badge to import this Blueprint: (needs Home Assistant Core 2021.3 or higher)
Or import this Blueprint by using the forum topic URL:
blueprint:
name: Zigbee2MQTT - OSRAM Smart+ switch mini (AC0251100NJ/AC0251700NJ) actions
description: >
Define actions for your OSRAM Smart+ switch mini using Zigbee2MQTT.
This blueprint requires a MQTT topic for your button and the actions you want to take for each button press type. domain: automation
domain: automation
author: freakshock88
homeassistant:
min_version: "2024.10.0" # Due to updated trigger syntax
input:
mqtt_topic:
name: OSRAM Smart+ switch mini MQTT topic
description: MQTT topic for OSRAM Smart+ switch mini. e.g. "zigbee2mqtt/Osram Remote Kitchen"
remote_button_up:
name: Up Press
description: Action to run on up press
default: []
selector:
action:
remote_button_up_hold:
name: Up Hold
description: Action to run on up hold
default: []
selector:
action:
remote_button_up_release:
name: Up Release
description: Action to run on up release
default: []
selector:
action:
remote_button_circle:
name: Circle Press
description: Action to run on circle press
default: []
selector:
action:
remote_button_circle_hold:
name: Circle Hold
description: Action to run on circle hold
default: []
selector:
action:
remote_button_circle_release:
name: Circle Release
description: Action to run on circle release
default: []
selector:
action:
remote_button_down:
name: Down Press
description: Action to run on down press
default: []
selector:
action:
remote_button_down_hold:
name: Down Hold
description: Action to run on down hold
default: []
selector:
action:
remote_button_down_release:
name: Down Release
description: Action to run on down release
default: []
selector:
action:
mode: restart
max_exceeded: silent
# Each option is explicitly defined as a trigger because sensor reports empty values as well.
# Not defining explicit triggers causes the automation to show up in the log multiple times per button press.
triggers:
- trigger: mqtt
topic: !input mqtt_topic
payload: "on"
value_template: "{{ value_json.action }}"
id: up
- trigger: mqtt
topic: !input mqtt_topic
payload: brightness_move_up
value_template: "{{ value_json.action }}"
id: up_hold
- trigger: mqtt
topic: !input mqtt_topic
payload: brightness_stop
value_template: "{{ value_json.action }}"
id: up_release
- trigger: mqtt
topic: !input mqtt_topic
payload: brightness_move_to_level
value_template: "{{ value_json.action }}"
id: circle_click
- trigger: mqtt
topic: !input mqtt_topic
payload: move_to_saturation
value_template: "{{ value_json.action }}"
id: circle_hold
- trigger: mqtt
topic: !input mqtt_topic
payload: "off"
value_template: "{{ value_json.action }}"
id: down
- trigger: mqtt
topic: !input mqtt_topic
payload: brightness_move_down
value_template: "{{ value_json.action }}"
id: down_hold
- trigger: mqtt
topic: !input mqtt_topic
payload: brightness_stop
value_template: "{{ value_json.action }}"
id: down_release
action:
- choose:
- conditions:
- condition: trigger
id: "up"
sequence: !input remote_button_up
- conditions:
- condition: trigger
id: "up_hold"
sequence: !input remote_button_up_hold
- conditions:
- condition: trigger
id: "up_release"
sequence: !input remote_button_up_release
- conditions:
- condition: trigger
id: "circle_click"
sequence: !input remote_button_circle
- conditions:
- condition: trigger
id: "circle_hold"
sequence: !input remote_button_circle_hold
- conditions:
- condition: trigger
id: "circle_release"
sequence: !input remote_button_circle_release
- conditions:
- condition: trigger
id: "down"
sequence: !input remote_button_down
- conditions:
- condition: trigger
id: "down_hold"
sequence: !input remote_button_down_hold
- conditions:
- condition: trigger
id: "down_release"
sequence: !input remote_button_down_release
Changelog
- 2021-03-01: Initial version
- 2025-01-11: Updated for Z2M v2 which no longer has the button sensor entity, but instead we use an MQTT trigger with a configured topic.
If you have any issues or questions, please let me know 
I’ve updated the opening post and the gist.