prefixkit Ask an engineerAsk Support RU

Zigbee devices Buttons and remotes

Shelly S4SN-0A24X

i4 Gen4. Works with Zigbee2MQTT with no vendor hub or cloud: it pairs with a Zigbee stick and shows up in Home Assistant.

Vendor
Shelly
Model
S4SN-0A24X
Type
Buttons and remotes
Power
mains: usually a router that extends the mesh
Firmware updates (OTA)
yes, through Zigbee2MQTT

Find it in shops: AliExpress

Links open a search in the shop; some are affiliate links: buying through them costs you nothing extra and supports this site. We do not sell devices or get them from manufacturers.

What it exposes

FeaturePropertyValuesControl
Action (button press)actioninput_1_on, input_1_off, input_1_toggle, input_1_single, input_1_double, input_1_triple, input_1_hold, input_2_on …read only
Switch type (sw1)switch_type_sw1toggle, momentarysettable
Switch type (sw2)switch_type_sw2toggle, momentarysettable
Switch type (sw3)switch_type_sw3toggle, momentarysettable
Switch type (sw4)switch_type_sw4toggle, momentarysettable
Momentary toggle binding (sw1)momentary_toggle_binding_sw1—settable
Momentary toggle binding (sw2)momentary_toggle_binding_sw2—settable
Momentary toggle binding (sw3)momentary_toggle_binding_sw3—settable
Momentary toggle binding (sw4)momentary_toggle_binding_sw4—settable
Wi-Fi statuswifi_status—read only
IP addressip_address—read only
DHCP enableddhcp_enabled—read only
Wi-Fi Configurationwifi_config—read only
Identifyidentifyidentifysettable

MQTT: state and commands

Zigbee2MQTT publishes the device state to zigbee2mqtt/my_device (my_device is the name you give the device). An example message:

{
  "switch_type_sw1": "toggle",
  "switch_type_sw2": "toggle",
  "switch_type_sw3": "toggle",
  "switch_type_sw4": "toggle",
  "momentary_toggle_binding_sw1": false,
  "momentary_toggle_binding_sw2": false,
  "momentary_toggle_binding_sw3": false,
  "momentary_toggle_binding_sw4": false,
  "dhcp_enabled": false,
  "linkquality": 120
}

Send commands to zigbee2mqtt/my_device/set:

mosquitto_pub -t zigbee2mqtt/my_device/set -m '{"switch_type_sw1":"momentary"}'
mosquitto_pub -t zigbee2mqtt/my_device/set -m '{"switch_type_sw2":"momentary"}'
mosquitto_pub -t zigbee2mqtt/my_device/set -m '{"switch_type_sw3":"momentary"}'
mosquitto_pub -t zigbee2mqtt/my_device/set -m '{"switch_type_sw4":"momentary"}'
mosquitto_pub -t zigbee2mqtt/my_device/set -m '{"momentary_toggle_binding_sw1":true}'

Watch the topics live from the browser: MQTT client.

Home Assistant automation example

Zigbee2MQTT creates Home Assistant entities from the device name. If it is called my_device, an automation in automations.yaml can look like this:

- alias: "Button"
  mode: single
  triggers:
    - trigger: mqtt
      topic: zigbee2mqtt/my_device
      value_template: "{{ value_json.action }}"
      payload: "input_1_on"
  actions:
    - action: light.toggle
      target:
        entity_id: light.living_room

Check the YAML: YAML checker.

How to pair it

  1. In Zigbee2MQTT click Permit join.
  2. Put the device in pairing mode: usually a long press of the reset button (5–10 s) until the LED blinks; bulbs: switch the power off and on 5–6 times.
  3. Keep the device close to the coordinator or a router while pairing.
  4. Give it a clear name: MQTT topics and Home Assistant entities are built from it.

Exact procedure and model notes: the device page in the Zigbee2MQTT docs. No coordinator yet: coordinator picker.

Similar devices

Idea?