DIYRuZ DIYRuZ_R8_8
Model | DIYRuZ_R8_8 |
Vendor | DIYRuZ |
Description | DiY 8 Relays + 8 switches |
Exposes | switch (state), power_on_behavior, linkquality |
Picture |
Notes
Deprecated click event
By default this device exposes a deprecated click
event. It's recommended to use the action
event instead.
To disable the click
event, set legacy: false
for this device in configuration.yaml
. Example:
devices:
'0x12345678':
friendly_name: my_device
legacy: false
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 (l1 endpoint)
The current state of this switch is in the published state under the state_l1
property (value is ON
or OFF
). To control this switch publish a message to topic zigbee2mqtt/FRIENDLY_NAME/set
with payload {"state_l1": "ON"}
, {"state_l1": "OFF"}
or {"state_l1": "TOGGLE"}
. To read the current state of this switch publish a message to topic zigbee2mqtt/FRIENDLY_NAME/get
with payload {"state_l1": ""}
.
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 (l2 endpoint)
The current state of this switch is in the published state under the state_l2
property (value is ON
or OFF
). To control this switch publish a message to topic zigbee2mqtt/FRIENDLY_NAME/set
with payload {"state_l2": "ON"}
, {"state_l2": "OFF"}
or {"state_l2": "TOGGLE"}
. To read the current state of this switch publish a message to topic zigbee2mqtt/FRIENDLY_NAME/get
with payload {"state_l2": ""}
.
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 (l3 endpoint)
The current state of this switch is in the published state under the state_l3
property (value is ON
or OFF
). To control this switch publish a message to topic zigbee2mqtt/FRIENDLY_NAME/set
with payload {"state_l3": "ON"}
, {"state_l3": "OFF"}
or {"state_l3": "TOGGLE"}
. To read the current state of this switch publish a message to topic zigbee2mqtt/FRIENDLY_NAME/get
with payload {"state_l3": ""}
.
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 (l4 endpoint)
The current state of this switch is in the published state under the state_l4
property (value is ON
or OFF
). To control this switch publish a message to topic zigbee2mqtt/FRIENDLY_NAME/set
with payload {"state_l4": "ON"}
, {"state_l4": "OFF"}
or {"state_l4": "TOGGLE"}
. To read the current state of this switch publish a message to topic zigbee2mqtt/FRIENDLY_NAME/get
with payload {"state_l4": ""}
.
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 (l5 endpoint)
The current state of this switch is in the published state under the state_l5
property (value is ON
or OFF
). To control this switch publish a message to topic zigbee2mqtt/FRIENDLY_NAME/set
with payload {"state_l5": "ON"}
, {"state_l5": "OFF"}
or {"state_l5": "TOGGLE"}
. To read the current state of this switch publish a message to topic zigbee2mqtt/FRIENDLY_NAME/get
with payload {"state_l5": ""}
.
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 (l6 endpoint)
The current state of this switch is in the published state under the state_l6
property (value is ON
or OFF
). To control this switch publish a message to topic zigbee2mqtt/FRIENDLY_NAME/set
with payload {"state_l6": "ON"}
, {"state_l6": "OFF"}
or {"state_l6": "TOGGLE"}
. To read the current state of this switch publish a message to topic zigbee2mqtt/FRIENDLY_NAME/get
with payload {"state_l6": ""}
.
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 (l7 endpoint)
The current state of this switch is in the published state under the state_l7
property (value is ON
or OFF
). To control this switch publish a message to topic zigbee2mqtt/FRIENDLY_NAME/set
with payload {"state_l7": "ON"}
, {"state_l7": "OFF"}
or {"state_l7": "TOGGLE"}
. To read the current state of this switch publish a message to topic zigbee2mqtt/FRIENDLY_NAME/get
with payload {"state_l7": ""}
.
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 (l8 endpoint)
The current state of this switch is in the published state under the state_l8
property (value is ON
or OFF
). To control this switch publish a message to topic zigbee2mqtt/FRIENDLY_NAME/set
with payload {"state_l8": "ON"}
, {"state_l8": "OFF"}
or {"state_l8": "TOGGLE"}
. To read the current state of this switch publish a message to topic zigbee2mqtt/FRIENDLY_NAME/get
with payload {"state_l8": ""}
.
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, l1 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_l1
property. To read (/get
) the value publish a message to topic zigbee2mqtt/FRIENDLY_NAME/get
with payload {"power_on_behavior_l1": ""}
. To write (/set
) a value publish a message to topic zigbee2mqtt/FRIENDLY_NAME/set
with payload {"power_on_behavior_l1": NEW_VALUE}
. The possible values are: off
, on
, toggle
, previous
.
Power-on behavior (enum, l2 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_l2
property. To read (/get
) the value publish a message to topic zigbee2mqtt/FRIENDLY_NAME/get
with payload {"power_on_behavior_l2": ""}
. To write (/set
) a value publish a message to topic zigbee2mqtt/FRIENDLY_NAME/set
with payload {"power_on_behavior_l2": NEW_VALUE}
. The possible values are: off
, on
, toggle
, previous
.
Power-on behavior (enum, l3 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_l3
property. To read (/get
) the value publish a message to topic zigbee2mqtt/FRIENDLY_NAME/get
with payload {"power_on_behavior_l3": ""}
. To write (/set
) a value publish a message to topic zigbee2mqtt/FRIENDLY_NAME/set
with payload {"power_on_behavior_l3": NEW_VALUE}
. The possible values are: off
, on
, toggle
, previous
.
Power-on behavior (enum, l4 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_l4
property. To read (/get
) the value publish a message to topic zigbee2mqtt/FRIENDLY_NAME/get
with payload {"power_on_behavior_l4": ""}
. To write (/set
) a value publish a message to topic zigbee2mqtt/FRIENDLY_NAME/set
with payload {"power_on_behavior_l4": NEW_VALUE}
. The possible values are: off
, on
, toggle
, previous
.
Power-on behavior (enum, l5 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_l5
property. To read (/get
) the value publish a message to topic zigbee2mqtt/FRIENDLY_NAME/get
with payload {"power_on_behavior_l5": ""}
. To write (/set
) a value publish a message to topic zigbee2mqtt/FRIENDLY_NAME/set
with payload {"power_on_behavior_l5": NEW_VALUE}
. The possible values are: off
, on
, toggle
, previous
.
Power-on behavior (enum, l6 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_l6
property. To read (/get
) the value publish a message to topic zigbee2mqtt/FRIENDLY_NAME/get
with payload {"power_on_behavior_l6": ""}
. To write (/set
) a value publish a message to topic zigbee2mqtt/FRIENDLY_NAME/set
with payload {"power_on_behavior_l6": NEW_VALUE}
. The possible values are: off
, on
, toggle
, previous
.
Power-on behavior (enum, l7 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_l7
property. To read (/get
) the value publish a message to topic zigbee2mqtt/FRIENDLY_NAME/get
with payload {"power_on_behavior_l7": ""}
. To write (/set
) a value publish a message to topic zigbee2mqtt/FRIENDLY_NAME/set
with payload {"power_on_behavior_l7": NEW_VALUE}
. The possible values are: off
, on
, toggle
, previous
.
Power-on behavior (enum, l8 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_l8
property. To read (/get
) the value publish a message to topic zigbee2mqtt/FRIENDLY_NAME/get
with payload {"power_on_behavior_l8": ""}
. To write (/set
) a value publish a message to topic zigbee2mqtt/FRIENDLY_NAME/set
with payload {"power_on_behavior_l8": NEW_VALUE}
. The possible values are: off
, on
, toggle
, previous
.
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
.