To contribute to this page, edit the following file
Ubisys S1-R #
Model | S1-R |
Vendor | Ubisys |
Description | Power switch S1-R |
Exposes | switch (state), power, action, linkquality |
Picture | ![]() |
Notes #
Device type specific configuration #
How to use device type specific configuration
simulated_brightness
: Set totrue
to simulate abrightness
value (default:false
). If this device provides abrightness_move_up
orbrightness_move_down
action it is possible to specify the update interval and delta. This can be done by instead of specifyingtrue
:
simulated_brightness:
delta: 20 # delta per interval, default = 20
interval: 200 # interval in milliseconds, default = 200
OTA updates #
This device supports OTA updates, for more information see OTA updates.
Exposes #
Switch #
The current state of this switch is in the published state under the state
property (value is ON
or OFF
).
To control this switch publish a message to topic zigbee2mqtt/FRIENDLY_NAME/set
with payload {"state": "ON"}
, {"state": "OFF"}
or {"state": "TOGGLE"}
.
To read the current state of this switch publish a message to topic zigbee2mqtt/FRIENDLY_NAME/get
with payload {"state": ""}
.
Power (numeric, meter endpoint) #
Instantaneous measured power.
Value can be found in the published state on the power
property.
To read (/get
) the value publish a message to topic zigbee2mqtt/FRIENDLY_NAME/get
with payload {"power": ""}
.
It’s not possible to write (/set
) this value.
The unit of this value is W
.
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: toggle
, on
, off
, recall_*
, brightness_move_up
, brightness_move_down
, brightness_stop
.
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
.
Manual Home Assistant configuration #
Although Home Assistant integration through MQTT discovery is preferred, manual integration is possible with the following configuration:
switch:
- platform: "mqtt"
state_topic: "zigbee2mqtt/<FRIENDLY_NAME>"
availability_topic: "zigbee2mqtt/bridge/state"
payload_off: "OFF"
payload_on: "ON"
value_template: "{{ value_json.state }}"
command_topic: "zigbee2mqtt/<FRIENDLY_NAME>/set"
sensor:
- platform: "mqtt"
state_topic: "zigbee2mqtt/<FRIENDLY_NAME>"
availability_topic: "zigbee2mqtt/bridge/state"
value_template: "{{ value_json.power }}"
unit_of_measurement: "W"
device_class: "power"
sensor:
- platform: "mqtt"
state_topic: "zigbee2mqtt/<FRIENDLY_NAME>"
availability_topic: "zigbee2mqtt/bridge/state"
value_template: "{{ value_json.action }}"
icon: "mdi:gesture-double-tap"
sensor:
- platform: "mqtt"
state_topic: "zigbee2mqtt/<FRIENDLY_NAME>"
availability_topic: "zigbee2mqtt/bridge/state"
value_template: "{{ value_json.linkquality }}"
unit_of_measurement: "lqi"
icon: "mdi:signal"
sensor:
- platform: "mqtt"
state_topic: "zigbee2mqtt/<FRIENDLY_NAME>"
availability_topic: "zigbee2mqtt/bridge/state"
icon: "mdi:update"
value_template: "{{ value_json['update']['state'] }}"
binary_sensor:
- platform: "mqtt"
state_topic: "zigbee2mqtt/<FRIENDLY_NAME>"
availability_topic: "zigbee2mqtt/bridge/state"
payload_on: true
payload_off: false
value_template: "{{ value_json.update_available}}"