Custom devices (DiY) DNCKATSW004
Model | DNCKATSW004 |
Vendor | Custom devices (DiY) |
Description | DNCKAT quadruple key wired wall light switch |
Exposes | switch (state), power_on_behavior, action, linkquality |
Picture |
Notes
DNCKAT quadruple key wired wall light switch
Options
How to use device type specific configuration
legacy
: Set to false to disable the legacy integration (highly recommended), will change structure of the published payload (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
Exposes
Switch (bottom_left endpoint)
The current state of this switch is in the published state under the state_bottom_left
property (value is ON
or OFF
). To control this switch publish a message to topic zigbee2mqtt/FRIENDLY_NAME/set
with payload {"state_bottom_left": "ON"}
, {"state_bottom_left": "OFF"}
or {"state_bottom_left": "TOGGLE"}
. To read the current state of this switch publish a message to topic zigbee2mqtt/FRIENDLY_NAME/get
with payload {"state_bottom_left": ""}
.
On with timed off
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 switch will not answer to other on with timed off commands. Support depends on the switch 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}
.
Switch (bottom_right endpoint)
The current state of this switch is in the published state under the state_bottom_right
property (value is ON
or OFF
). To control this switch publish a message to topic zigbee2mqtt/FRIENDLY_NAME/set
with payload {"state_bottom_right": "ON"}
, {"state_bottom_right": "OFF"}
or {"state_bottom_right": "TOGGLE"}
. To read the current state of this switch publish a message to topic zigbee2mqtt/FRIENDLY_NAME/get
with payload {"state_bottom_right": ""}
.
On with timed off
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 switch will not answer to other on with timed off commands. Support depends on the switch 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}
.
Switch (top_left endpoint)
The current state of this switch is in the published state under the state_top_left
property (value is ON
or OFF
). To control this switch publish a message to topic zigbee2mqtt/FRIENDLY_NAME/set
with payload {"state_top_left": "ON"}
, {"state_top_left": "OFF"}
or {"state_top_left": "TOGGLE"}
. To read the current state of this switch publish a message to topic zigbee2mqtt/FRIENDLY_NAME/get
with payload {"state_top_left": ""}
.
On with timed off
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 switch will not answer to other on with timed off commands. Support depends on the switch 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}
.
Switch (top_right endpoint)
The current state of this switch is in the published state under the state_top_right
property (value is ON
or OFF
). To control this switch publish a message to topic zigbee2mqtt/FRIENDLY_NAME/set
with payload {"state_top_right": "ON"}
, {"state_top_right": "OFF"}
or {"state_top_right": "TOGGLE"}
. To read the current state of this switch publish a message to topic zigbee2mqtt/FRIENDLY_NAME/get
with payload {"state_top_right": ""}
.
On with timed off
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 switch will not answer to other on with timed off commands. Support depends on the switch 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}
.
Power-on behavior (enum, bottom_left endpoint)
Controls the behavior when the device is powered on after power loss. Value can be found in the published state on the power_on_behavior_bottom_left
property. To read (/get
) the value publish a message to topic zigbee2mqtt/FRIENDLY_NAME/get
with payload {"power_on_behavior_bottom_left": ""}
. To write (/set
) a value publish a message to topic zigbee2mqtt/FRIENDLY_NAME/set
with payload {"power_on_behavior_bottom_left": NEW_VALUE}
. The possible values are: off
, on
, toggle
, previous
.
Power-on behavior (enum, bottom_right endpoint)
Controls the behavior when the device is powered on after power loss. Value can be found in the published state on the power_on_behavior_bottom_right
property. To read (/get
) the value publish a message to topic zigbee2mqtt/FRIENDLY_NAME/get
with payload {"power_on_behavior_bottom_right": ""}
. To write (/set
) a value publish a message to topic zigbee2mqtt/FRIENDLY_NAME/set
with payload {"power_on_behavior_bottom_right": NEW_VALUE}
. The possible values are: off
, on
, toggle
, previous
.
Power-on behavior (enum, top_left endpoint)
Controls the behavior when the device is powered on after power loss. Value can be found in the published state on the power_on_behavior_top_left
property. To read (/get
) the value publish a message to topic zigbee2mqtt/FRIENDLY_NAME/get
with payload {"power_on_behavior_top_left": ""}
. To write (/set
) a value publish a message to topic zigbee2mqtt/FRIENDLY_NAME/set
with payload {"power_on_behavior_top_left": NEW_VALUE}
. The possible values are: off
, on
, toggle
, previous
.
Power-on behavior (enum, top_right endpoint)
Controls the behavior when the device is powered on after power loss. Value can be found in the published state on the power_on_behavior_top_right
property. To read (/get
) the value publish a message to topic zigbee2mqtt/FRIENDLY_NAME/get
with payload {"power_on_behavior_top_right": ""}
. To write (/set
) a value publish a message to topic zigbee2mqtt/FRIENDLY_NAME/set
with payload {"power_on_behavior_top_right": NEW_VALUE}
. The possible values are: off
, on
, toggle
, previous
.
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: release_bottom_left
, hold_bottom_left
, release_bottom_right
, hold_bottom_right
, release_top_left
, hold_top_left
, release_top_right
, hold_top_right
.
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
.