Aqara Wall Switch H1 No Neutral: Zigbee2MQTT + Home Assistant
The H1 EU no-neutral switch can control its relay directly or send button actions for Home Assistant automations. The single-rocker model is WS-EUK01 and the double-rocker is WS-EUK02. Check the label first: QBKG38LM is an E1 no-neutral single-rocker switch. If that is your model, use the E1 notes below alongside the shared relay and button-automation steps.
Prepare the installation and Zigbee network
- A correctly installed H1 EU no-neutral or E1 QBKG38LM switch, with a load permitted by that model’s manual.
- A supported Zigbee2MQTT coordinator and MQTT broker.
- Home Assistant’s MQTT integration with discovery enabled.
Have a qualified electrician confirm wiring, load compatibility and box space. This guide begins after installation. It does not require the Aqara M2; the switch joins your coordinator’s network instead.
Use the matching device entry: WS-EUK01, WS-EUK02, or the separate QBKG38LM E1. Firmware requirements for one radio family cannot be applied to every adapter sold under a similar name.
If your switch is the E1 QBKG38LM
Use the QBKG38LM device entry for its adapter-firmware requirements and the E1 manual for its pairing-button sequence. Open Permit join, put the installed E1 into joining mode, wait for its interview and confirm QBKG38LM before closing joining. The H1 button timings below are not E1 instructions.
In Exposes, the E1’s operation_mode selects control_relay or decoupled, and its button actions are single and double. Use the single-rocker decoupling message and automation below with the E1’s own friendly name, discovered device ID and target entities. Perform both presses to discover their triggers; do not add a hold trigger.
The E1 definition lists OTA support. That does not establish H1 EU support or guarantee an available E1 firmware image. Check the OTA result for your exact model, and use the E1 manual for permitted loads and electrical installation.
Pair the correct model
Enable Permit join in Zigbee2MQTT. For WS-EUK01, its notes specify a roughly ten-second hold until the blue light blinks and stops, then releasing and waiting. For WS-EUK02, hold the right button for about five seconds until the blue LED blinks.
Wait for the interview, confirm the reported model and assign a useful name such as hall_switch_h1. Close joining, then check the discovered device under Home Assistant’s MQTT integration.
If pairing fails
Check the exact model’s instructions, adapter firmware and Zigbee2MQTT log. Improve coverage near the installed switch with an appropriate router or better coordinator placement. Do not remove or handle an energised wall switch to move it beside the coordinator.
The no-neutral models are end devices, so they do not extend the mesh themselves. If a device joins but its interview fails, record that distinction before resetting it again.
Readings, controls and actions
The H1 EU entries expose relay state, operation mode, power-outage memory, indicator settings, internal temperature and diagnostic counts. mode_switch offers anti-flicker and quick modes. Availability in Home Assistant depends on discovery and enabled entities.
WS-EUK01 lists single and double actions. WS-EUK02 uses endpoint-specific names such as single_left, double_right and single_both. Neither current entry lists a hold action. Do not assume a countdown control exists just because another switch family has one.
Test the relay in Home Assistant
Open Settings → Devices & services → MQTT and select the switch. Check the actual switch entity, then test on and off with the installed light. For the double-rocker model, verify the left and right load mapping separately.
If Zigbee2MQTT sees the switch but Home Assistant does not, check broker connectivity and the Home Assistant discovery setting. This is the same discovery path used by the Door and Window Sensor T1 and temperature and humidity sensor T1.
Use a button without toggling its relay
In control_relay mode, a physical press operates the relay. In decoupled mode, the button sends an action without directly changing that relay. Home Assistant can use the action for a scene or another light.
Decoupling does not itself keep the relay on, solve a minimum-load problem or make a smart bulb electrically compatible. Aqara’s H1 no-neutral guidance excludes certain smart and remote-controlled loads. Use the button to control another suitable target only after the connected circuit has been approved.
Enable decoupled mode
For WS-EUK01, change operation_mode to decoupled in Exposes or publish the following message:
Topic: zigbee2mqtt/hall_switch_h1/set
Payload: {"operation_mode": "decoupled"}
For WS-EUK02, use operation_mode_left or operation_mode_right for the intended rocker. control_relay restores direct relay control. Check the reported setting and test the physical press afterwards.
Example: single press for a scene, double press for a light
This single-rocker example uses discovered MQTT device triggers. In Home Assistant’s automation editor, choose a trigger from the actual switch and inspect its YAML to obtain the device ID; it is not the entity ID or friendly name. Perform both gestures first if their triggers have not been discovered.
alias: "Hall switch H1 — button actions"
description: "Single press activates evening scene; double press toggles hall lights"
triggers:
- platform: device
domain: mqtt
device_id: YOUR_DEVICE_ID
type: action
subtype: single
id: single_press
- platform: device
domain: mqtt
device_id: YOUR_DEVICE_ID
type: action
subtype: double
id: double_press
actions:
- choose:
- conditions:
- condition: trigger
id: single_press
sequence:
- action: scene.turn_on
target:
entity_id: scene.hall_evening
- conditions:
- condition: trigger
id: double_press
sequence:
- action: light.toggle
target:
entity_id: light.hall_group
mode: single
Replace YOUR_DEVICE_ID, the scene and the light. For WS-EUK02, choose the discovered trigger for the intended rocker and use its exact action subtype. This example covers single and double presses; it does not add a hold action.
No-neutral load compatibility
A no-neutral switch powers its electronics through the connected circuit. Some LED drivers respond poorly to that current, causing flicker, glow when off or loss of switch power. A wattage threshold alone does not prove a particular lamp will work.
Check the exact model’s permitted loads and minimum rating. Aqara’s H1 FAQ includes restrictions for the no-neutral version. If the load is unsuitable, have the installer choose an approved alternative, which may involve a neutral-wire model or a separate wireless control.
Do not add a generic bypass capacitor or a wire jumper on the assumption that it works with every no-neutral switch. Decoupled mode changes button behaviour, not the electrical design.
Restore state, indicator settings and timers
power_outage_memory is a boolean that enables or disables restoring the previous relay state. flip_indicator_light reverses the LED’s relationship to the relay; led_disabled_night enables the H1’s night-disable behaviour. Check each setting on the installed switch.
The documented timed-on mechanism uses on_time, with optional off_wait_time cooldown, and depends on firmware support. It is not an exposed countdown setting. Test it before using it; use a Home Assistant timer when that better suits the rule.
Check firmware support for the exact model
Do not infer H1 EU OTA support from the QBKG38LM E1 page. The current H1 EU pages do not list the same OTA support statement. Check Zigbee2MQTT’s current device notes and OTA results for your installed model and firmware before planning an update.
A firmware download, when supported, can need internet access even though everyday Zigbee control is local.
Frequently asked questions
Is QBKG38LM the H1 single-rocker? Zigbee2MQTT identifies it as E1. H1 EU no-neutral models are WS-EUK01 and WS-EUK02. The E1 setup notes above retain the shared single-rocker relay and button-automation path for QBKG38LM owners.
Can I use a hold trigger? The current H1 EU action lists include single and double presses, with rocker-specific names on WS-EUK02. Use the actions actually reported by your device.
Does decoupled mode fix flicker? It changes the button-to-relay relationship. Load suitability still needs to be checked.
Does it extend the Zigbee mesh? The no-neutral version is an end device. Plan coverage using suitable router devices.