title | description |
---|---|
Lubeez 12AB control via MQTT |
Integrate your Lubeez 12AB via Zigbee2MQTT with whatever smart home infrastructure you are using without the vendors bridge or gateway. |
To contribute to this page, edit the following file
| Model | 12AB | | Vendor | Lubeez | | Description | zigbee 3.0 AC dimmer | | Exposes | light (state, brightness), effect, linkquality | | Picture | |
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). Note that this value is overridden if atransition
value is present in the MQTT command payload.
This light supports the following features: state
, brightness
.
state
: To control the state publish a message to topiczigbee2mqtt/FRIENDLY_NAME/set
with payload{"state": "ON"}
,{"state": "OFF"}
or{"state": "TOGGLE"}
. To read the state send a message tozigbee2mqtt/FRIENDLY_NAME/get
with payload{"state": ""}
.brightness
: To control the brightness publish a message to topiczigbee2mqtt/FRIENDLY_NAME/set
with payload{"brightness": VALUE}
whereVALUE
is a number between0
and254
. To read the brightness send a message tozigbee2mqtt/FRIENDLY_NAME/get
with payload{"brightness": ""}
.
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":0.5}
.
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
}
Triggers an effect on the light (e.g. make light blink for a few seconds).
Value will not be published in the state.
It's not possible to read (/get
) this value.
To write (/set
) a value publish a message to topic zigbee2mqtt/FRIENDLY_NAME/set
with payload {"effect": NEW_VALUE}
.
The possible values are: blink
, breathe
, okay
, channel_change
, finish_effect
, stop_effect
.
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
.
Although Home Assistant integration through MQTT discovery is preferred, manual integration is possible with the following configuration:
{% raw %}
light:
- platform: "mqtt"
state_topic: "zigbee2mqtt/<FRIENDLY_NAME>"
availability_topic: "zigbee2mqtt/bridge/state"
brightness: true
color_temp: false
xy: false
hs: false
schema: "json"
command_topic: "zigbee2mqtt/<FRIENDLY_NAME>/set"
brightness_scale: 254
effect: true
effect_list:
- "blink"
- "breathe"
- "okay"
- "channel_change"
- "finish_effect"
- "stop_effect"
sensor:
- platform: "mqtt"
state_topic: "zigbee2mqtt/<FRIENDLY_NAME>"
availability_topic: "zigbee2mqtt/bridge/state"
unit_of_measurement: "lqi"
value_template: "{{ value_json.linkquality }}"
icon: "mdi:signal"
{% endraw %}