OSRAM 4062172044776_4
Model | 4062172044776_4 |
Vendor | OSRAM |
Description | Zigbee 3.0 DALI CONV LI dimmer for DALI-based luminaires (with two devices and pushbutton) |
Exposes | action, light (state, brightness), linkquality |
Picture |
Notes
Set default power on/off transition
Various Osram/Sylvania LED support setting a default transition when turning a light on and off.
TOPIC: zigbee2mqtt/FRIENDLY_NAME/set
{
"set_transition": 1
}
INFO: Value is time in seconds (integer, float values are not supported)
Remember current light state
Various Osram/Sylvania LED support remembering their current state in case of power loss, or if a light is manually switched off then on. Lights will remember their respective attributes (i.e. brightness, color, saturation, etc.). NOTE: This must be executed every time you make changes to a light’s attributes for it to then ‘remember’ it.
TOPIC: zigbee2mqtt/FRIENDLY_NAME/set
{
"remember_state": true
}
INFO: Value is true, false (boolean)
OTA updates
This device supports OTA updates, for more information see OTA updates.
Options
How to use device type specific configuration
-
transition
: Controls the transition time (in seconds) of on/off, brightness, color temperature (if applicable) and color (if applicable) changes. Defaults to0
(no transition). The value must be a number with a minimum value of0
-
state_action
: State actions will also be published as ‘action’ when true (default false). The value must betrue
orfalse
-
simulated_brightness
: Simulate a brightness value. If this device provides a brightness_move_up or brightness_move_down action it is possible to specify the update interval and delta. The action_brightness_delta indicates the delta for each interval. Example:simulated_brightness: delta: 20 # delta per interval, default = 20 interval: 200 # interval in milliseconds, default = 200
Exposes
Action (enum)
Triggered action (e.g. a button click).
Value can be found in the published state on the action
property.
It’s not possible to read (/get
) or write (/set
) this value.
The possible values are: toggle_s1
, brightness_move_up_s1
, brightness_move_down_s1
, brightness_stop_s1
.
Light (l1 endpoint)
This light supports the following features: state
, brightness
.
state
: To control the state publish a message to topiczigbee2mqtt/FRIENDLY_NAME/set
with payload{"state_l1": "ON"}
,{"state_l1": "OFF"}
or{"state_l1": "TOGGLE"}
. To read the state send a message tozigbee2mqtt/FRIENDLY_NAME/get
with payload{"state_l1": ""}
.brightness
: To control the brightness publish a message to topiczigbee2mqtt/FRIENDLY_NAME/set
with payload{"brightness_l1": VALUE}
whereVALUE
is a number between0
and254
. To read the brightness send a message tozigbee2mqtt/FRIENDLY_NAME/get
with payload{"brightness_l1": ""}
.
Transition
For all of the above mentioned features it is possible to do a transition of the value over time. To do this add an additional property transition
to the payload which is the transition time in seconds.
Examples: {"brightness":156,"transition":3}
, {"color_temp":241,"transition":1}
.
Moving/stepping
Instead of setting a value (e.g. brightness) directly it is also possible to:
- move: this will automatically move the value over time, to stop send value
stop
or0
. - step: this will increment/decrement the current value by the given one.
The direction of move and step can be either up or down, provide a negative value to move/step down, a positive value to move/step up.
To do this send a payload like below to zigbee2mqtt/FRIENDLY_NAME/set
NOTE: brightness move/step will stop at the minimum brightness and won’t turn on the light when it’s off. In this case use brightness_move_onoff
/brightness_step_onoff
{
"brightness_move": -40, // Starts moving brightness down at 40 units per second
"brightness_move": 0, // Stop moving brightness
"brightness_step": 40 // Increases brightness by 40
}
Light (l2 endpoint)
This light supports the following features: state
, brightness
.
state
: To control the state publish a message to topiczigbee2mqtt/FRIENDLY_NAME/set
with payload{"state_l2": "ON"}
,{"state_l2": "OFF"}
or{"state_l2": "TOGGLE"}
. To read the state send a message tozigbee2mqtt/FRIENDLY_NAME/get
with payload{"state_l2": ""}
.brightness
: To control the brightness publish a message to topiczigbee2mqtt/FRIENDLY_NAME/set
with payload{"brightness_l2": VALUE}
whereVALUE
is a number between0
and254
. To read the brightness send a message tozigbee2mqtt/FRIENDLY_NAME/get
with payload{"brightness_l2": ""}
.
Transition
For all of the above mentioned features it is possible to do a transition of the value over time. To do this add an additional property transition
to the payload which is the transition time in seconds.
Examples: {"brightness":156,"transition":3}
, {"color_temp":241,"transition":1}
.
Moving/stepping
Instead of setting a value (e.g. brightness) directly it is also possible to:
- move: this will automatically move the value over time, to stop send value
stop
or0
. - step: this will increment/decrement the current value by the given one.
The direction of move and step can be either up or down, provide a negative value to move/step down, a positive value to move/step up.
To do this send a payload like below to zigbee2mqtt/FRIENDLY_NAME/set
NOTE: brightness move/step will stop at the minimum brightness and won’t turn on the light when it’s off. In this case use brightness_move_onoff
/brightness_step_onoff
{
"brightness_move": -40, // Starts moving brightness down at 40 units per second
"brightness_move": 0, // Stop moving brightness
"brightness_step": 40 // Increases brightness by 40
}
Linkquality (numeric)
Link quality (signal strength).
Value can be found in the published state on the linkquality
property.
It’s not possible to read (/get
) or write (/set
) this value.
The minimal value is 0
and the maximum value is 255
.
The unit of this value is lqi
.