title | description | addedAt | pageClass |
---|---|---|---|
HORNBACH 10454468 control via MQTT |
Integrate your HORNBACH 10454468 via Zigbee2MQTT with whatever smart home infrastructure you are using without the vendor's bridge or gateway. |
2024-08-01 11:23:41 -0700 |
device-page |
Model | 10454468 |
Vendor | HORNBACH |
Description | FLAIR Viyu smart LED bulb CCT E27 |
Exposes | light (state, brightness, color_temp, color_temp_startup), effect, power_on_behavior, 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). The value must be a number with a minimum value of0
-
color_sync
: When enabled colors will be synced, e.g. if the light supports both color x/y and color temperature a conversion from color x/y to color temperature will be done when setting the x/y color (default true). The value must betrue
orfalse
-
state_action
: State actions will also be published as 'action' when true (default false). The value must betrue
orfalse
This light supports the following features: state
, brightness
, color_temp
, color_temp_startup
.
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": ""}
.color_temp
: To control the color temperature (in reciprocal megakelvin a.k.a. mired scale) publish a message to topiczigbee2mqtt/FRIENDLY_NAME/set
with payload{"color_temp": VALUE}
whereVALUE
is a number between200
and454
, the higher the warmer the color. To read the color temperature send a message tozigbee2mqtt/FRIENDLY_NAME/get
with payload{"color_temp": ""}
. Besides the numeric values the following values are accepted:coolest
,cool
,neutral
,warm
,warmest
.color_temp_startup
: To set the startup color temperature (in reciprocal megakelvin a.k.a. mired scale) publish a message to topiczigbee2mqtt/FRIENDLY_NAME/set
with payload{"color_temp_startup": VALUE}
whereVALUE
is a number between200
and454
, the higher the warmer the color. To read the startup color temperature send a message tozigbee2mqtt/FRIENDLY_NAME/get
with payload{"color_temp_startup": ""}
. Besides the numeric values the following values are accepted:coolest
,cool
,neutral
,warm
,warmest
,previous
.
When setting the state to ON, it might be possible to specify an automatic shutoff after a certain amount of time. To do this add an additional property on_time
to the payload which is the time in seconds the state should remain on.
Additionally an off_wait_time
property can be added to the payload to specify the cooldown time in seconds when the light will not answer to other on with timed off commands.
Support depends on the light firmware. Some devices might require both on_time
and off_wait_time
to work
Examples : {"state" : "ON", "on_time": 300}
, {"state" : "ON", "on_time": 300, "off_wait_time": 120}
.
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}
.
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
"color_temp_move": 60, // Starts moving color temperature up at 60 units per second
"color_temp_move": "stop", // Stop moving color temperature
"color_temp_step": 99, // Increase color temperature by 99
}
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
.
Controls the behavior when the device is powered on after power loss. If you get an UNSUPPORTED_ATTRIBUTE
error, the device does not support it..
Value can be found in the published state on the power_on_behavior
property.
To read (/get
) the value publish a message to topic zigbee2mqtt/FRIENDLY_NAME/get
with payload {"power_on_behavior": ""}
.
To write (/set
) a value publish a message to topic zigbee2mqtt/FRIENDLY_NAME/set
with payload {"power_on_behavior": NEW_VALUE}
.
The possible values are: off
, on
, toggle
, previous
.
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
.