Koenkk / Koenkk/zigbee2mqtt

[lumi.ctrl_neutral2 (QBKG03LM) / LUMI] ???

Open
#32,712 0 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

problem
Dominant language
TypeScript
Stars
15.7k
Forks
2k
Avg merge
18h 55m
Merged PRs (30d)
35

Description

What happened?

Sometimes I see a warning in the Home Assistant logs:
Invalid event type single_both for event.hallwaykitchenlight_action received on topic zigbee2mqtt/HallwayKitchenLight, payload {"event_type":"single_both"}

So I checked the MQTT topic homeassistant/event//action/config and only saw the following event types:

"event_types": [
"release_left",
"release_right",
"release_both",
"double_left",
"double_right",
"single_left",
"single_right",
"hold_release_left"
],

I tried deleting the device in Home Assistant and adding it again, but the value of the "event_types" parameter remained the same.

What did you expect to happen?

Z2M should expose another event type "single_both" to the Home Assistant device configuration

How to reproduce it (minimal and precise)

Just click both switches at the same time

Zigbee2MQTT version

2.12.1 (unknown)

Adapter firmware version

{"maintrel":1,"majorrel":2,"minorrel":7,"product":1,"revision":20240710,"transportrev":2}

Adapter

ZStack3x0

Setup

os: #1 SMP PREEMPT Wed Jul 1 09:33:09 UTC 2026 - 6.18.34-haos-raspi - arm64
node: v22.23.0
ha: true

Device database.db entry

No response

Debug log

No response

Notes
Device

definition: QBKG03LM - Aqara (v0.0.0)
software_build_id: undefined
date_code: 04-25-2018
endpoints:

{"1":{"bindings":[],"clusters":{"input":["genBasic","genIdentify","genPowerCfg","genDeviceTempCfg","genOta","genTime"],"output":["genBasic","genTime","genOta"]},"configured_reportings":[],"name":"system","scenes":[]},"2":{"bindings":[],"clusters":{"input":["genBinaryOutput","genOnOff","genGroups","genScenes"],"output":[]},"configured_reportings":[],"name":"left","scenes":[]},"3":{"bindings":[],"clusters":{"input":["genBinaryOutput","genOnOff","genGroups","genScenes"],"output":[]},"configured_reportings":[],"name":"right","scenes":[]},"4":{"bindings":[],"clusters":{"input":["genMultistateInput","genOnOff"],"output":[]},"configured_reportings":[],"scenes":[]},"5":{"bindings":[],"clusters":{"input":["genMultistateInput","genOnOff"],"output":[]},"configured_reportings":[],"scenes":[]},"6":{"bindings":[],"clusters":{"input":["genMultistateInput","genOnOff"],"output":[]},"configured_reportings":[],"scenes":[]},"8":{"bindings":[],"clusters":{"input":["genAnalogInput"],"output":[]},"configured_reportings":[],"scenes":[]}}
Health

time: Fri Jul 31 2026 15:50:27 GMT+0300 (Moscow Standard Time)
os.load_average: 0.94, 1.47, 1.52
os.memory_percent: 24.1888
process.memory_percent: 1.7216
process.uptime_sec: 75700

{"leave_count":0,"messages":1421,"messages_per_sec":0.0188,"network_address_changes":0}

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the QBKG03LM device definition and the Home Assistant event configuration described in the issue, then trace how the simultaneous-switch event is represented. Reproduce the warning by clicking both switches together; done means single_both is included in the exposed event types and the invalid-event warning no longer appears.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
backend
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
50/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.