[TS0042 (Push_LO) / _TZ3000_dfgbtub0] ???

Open
  • Is something wrong?
#33,642 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
55/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Tech stack
typescript
Domain
backend, embedded-iot

Research direction

Start by locating the Marmitek Push_LO definition and its action handling, then compare its button event payloads with the Aqara double switch mentioned in the report. Reproduce with the DS-EMOS switch and inspect the MQTT values for each button; done means button 1 and button 2 publish distinguishable actions. The issue provides no file or test names, so finding the relevant definition will require reading around the device support code.

Written by the indexing model from the issue text.

Description

problem
What happened?

EMOS Double switch - recognized in zigbee2mqtt - yes
Recognition: 1_single , 1_double , 2_single, 2_double
No Recognition: x_hold

in Homeassistant 2026/10 and 2026/11 ... mqtt entry : Action gets only "SINGLE" or "DOUBLE" - not knowing which button is pressed. Both buttons results in the same values.

Any trick here to get this correct reported to HA / mqtt. All components are latest releases.

What did you expect to happen?

I expect that mqtt also gets the difference if Button 1 or Button 2 is pressed.

Aqara Double Switch works as expected - btw. maybe this information helps.

How to reproduce it (minimal and precise)

First learning the DS-EMOS Switch to zigbee2mqtt, then check the mqtt values in HA ...
I did this now for 5 times. - Maybe I made some config fault.

Zigbee2MQTT version

2.14.3 (unknown)

Adapter firmware version

{"maintrel":114,"majorrel":2,"minorrel":6,"product":0,"revision":"0x26720700","transportrev":0}

Adapter

ConBee2/RaspBee2

Setup

os: #1 SMP PREEMPT_DYNAMIC Tue Oct 27 13:21:12 UTC 2026 - 6.18.58-haos - x64
node: v24.22.1
ha: true

Device database.db entry

No response

Debug log

No response

Notes
Device

definition: Push_LO - Marmitek (v0.0.0)
software_build_id: 1.0.2
date_code: ``
endpoints:

{"1":{"bindings":[],"clusters":{"input":["genBasic","genPowerCfg","genOnOff"],"output":["genOta","genTime"]},"configured_reportings":[],"scenes":[]},"2":{"bindings":[],"clusters":{"input":["genPowerCfg","genOnOff"],"output":[]},"configured_reportings":[],"scenes":[]}}
Health

time: Sun Nov 08 2026 11:33:13 GMT+0100 (Mitteleuropäische Normalzeit)
os.load_average: 0.01, 0.05, 0.07
os.memory_percent: 30.6577
process.memory_percent: 2.6066
process.uptime_sec: 586204

{"leave_count":0,"messages":193,"messages_per_sec":0.0003,"network_address_changes":0}
Dominant language
TypeScript
Stars
15.8k
Forks
2.1k
Avg merge
1d 6h
Merged PRs (30d)
38

Getting set up

Open in Codespaces

Starts the project's dev container in your browser, under your own GitHub account.

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.

More from Koenkk/zigbee2mqtt

All issues in Koenkk/zigbee2mqtt

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.