Siglis ZFP-1A-CH
Model | ZFP-1A-CH |
Vendor | Siglis |
Description | zigfred plus smart in-wall switch |
Exposes | light (state, brightness, color_xy), light (state, brightness), cover (state, position, tilt), action, linkquality |
Picture | ![]() |
Options
How to use device type specific configuration
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
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
invert_cover
: Inverts the cover position, false: open=100,close=0, true: open=0,close=100 (default false). The value must betrue
orfalse
Exposes
Light (l1 endpoint)
This light supports the following features: state
, brightness
, color_xy
.
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": ""}
.color_xy
: To control the XY color (CIE 1931 color space) publish a message to topiczigbee2mqtt/FRIENDLY_NAME/set
with payload{"color_l1": {"x": X_VALUE, "y": Y_VALUE}}
(e.g.{"color":{"x":0.123,"y":0.123}}
). To read the XY color send a message tozigbee2mqtt/FRIENDLY_NAME/get
with payload{"color_l1":{"x":"","y":""}}
. Alternatively it is possible to set the XY color via RGB:{"color": {"r": R, "g": G, "b": B}}
e.g.{"color":{"r":46,"g":102,"b":150}}
{"color": {"rgb": "R,G,B"}}
e.g.{"color":{"rgb":"46,102,150"}}
{"color": {"hex": HEX}}
e.g.{"color":{"hex":"#547CFF"}}
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
}
2
3
4
5
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
}
2
3
4
5
Light (l3 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_l3": "ON"}
,{"state_l3": "OFF"}
or{"state_l3": "TOGGLE"}
. To read the state send a message tozigbee2mqtt/FRIENDLY_NAME/get
with payload{"state_l3": ""}
.brightness
: To control the brightness publish a message to topiczigbee2mqtt/FRIENDLY_NAME/set
with payload{"brightness_l3": VALUE}
whereVALUE
is a number between0
and254
. To read the brightness send a message tozigbee2mqtt/FRIENDLY_NAME/get
with payload{"brightness_l3": ""}
.
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
}
2
3
4
5
Light (l4 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_l4": "ON"}
,{"state_l4": "OFF"}
or{"state_l4": "TOGGLE"}
. To read the state send a message tozigbee2mqtt/FRIENDLY_NAME/get
with payload{"state_l4": ""}
.brightness
: To control the brightness publish a message to topiczigbee2mqtt/FRIENDLY_NAME/set
with payload{"brightness_l4": VALUE}
whereVALUE
is a number between0
and254
. To read the brightness send a message tozigbee2mqtt/FRIENDLY_NAME/get
with payload{"brightness_l4": ""}
.
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
}
2
3
4
5
Light (l5 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_l5": "ON"}
,{"state_l5": "OFF"}
or{"state_l5": "TOGGLE"}
. To read the state send a message tozigbee2mqtt/FRIENDLY_NAME/get
with payload{"state_l5": ""}
.brightness
: To control the brightness publish a message to topiczigbee2mqtt/FRIENDLY_NAME/set
with payload{"brightness_l5": VALUE}
whereVALUE
is a number between0
and254
. To read the brightness send a message tozigbee2mqtt/FRIENDLY_NAME/get
with payload{"brightness_l5": ""}
.
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
}
2
3
4
5
Cover (l6 endpoint)
The current state of this cover is in the published state under the state_l6
property (value is OPEN
or CLOSE
). To control this cover publish a message to topic zigbee2mqtt/FRIENDLY_NAME/set
with payload {"state_l6": "OPEN"}
, {"state_l6": "CLOSE"}
, {"state_l6": "STOP"}
. To read the current state of this cover publish a message to topic zigbee2mqtt/FRIENDLY_NAME/get
with payload {"state_l6": ""}
. To change the position publish a message to topic zigbee2mqtt/FRIENDLY_NAME/set
with payload {"position_l6": VALUE}
where VALUE
is a number between 0
and 100
. To change the tilt publish a message to topic zigbee2mqtt/FRIENDLY_NAME/set
with payload {"tilt_l6": VALUE}
where VALUE
is a number between 0
and 100
.
Cover (l7 endpoint)
The current state of this cover is in the published state under the state_l7
property (value is OPEN
or CLOSE
). To control this cover publish a message to topic zigbee2mqtt/FRIENDLY_NAME/set
with payload {"state_l7": "OPEN"}
, {"state_l7": "CLOSE"}
, {"state_l7": "STOP"}
. To read the current state of this cover publish a message to topic zigbee2mqtt/FRIENDLY_NAME/get
with payload {"state_l7": ""}
. To change the position publish a message to topic zigbee2mqtt/FRIENDLY_NAME/set
with payload {"position_l7": VALUE}
where VALUE
is a number between 0
and 100
. To change the tilt publish a message to topic zigbee2mqtt/FRIENDLY_NAME/set
with payload {"tilt_l7": VALUE}
where VALUE
is a number between 0
and 100
.
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: button_1_single
, button_1_double
, button_1_hold
, button_1_release
, button_2_single
, button_2_double
, button_2_hold
, button_2_release
, button_3_single
, button_3_double
, button_3_hold
, button_3_release
, button_4_single
, button_4_double
, button_4_hold
, button_4_release
.
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
.