Koenkk / Koenkk/zigbee2mqtt

[TS0505B (TS0505B_1_1) / _TZ3210_mja6r5ix] ???

Open
#32,859 1 comment 0 reactions 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?

2 dieser Geräte reagiert nicht mehr plötzlich und zeitgleich.

What did you expect to happen?

2 dieser Geräte reagiert nicht mehr plötzlich und zeitgleich.

How to reproduce it (minimal and precise)

No response

Zigbee2MQTT version

2.13.0 (unknown)

Adapter firmware version

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

Adapter

ZStack3x0

Setup

os: #1 SMP PREEMPT_DYNAMIC Thu Jul 30 12:44:18 UTC 2026 - 6.18.39-haos - x64
node: v24.18.1
ha: true

Device database.db entry

No response

Debug log

No response

Notes
Device

definition: TS0505B_1_1 - Tuya (v0.0.0)
software_build_id: z.1.0
date_code: undefined
endpoints:

{"1":{"bindings":[],"clusters":{"input":["genBasic","genIdentify","genGroups","genScenes","genOnOff","genLevelCtrl","lightingColorCtrl","touchlink"],"output":["genOta","genTime"]},"configured_reportings":[],"scenes":[]}}

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

No source file or test is identified. Start by obtaining the device database.db entry and a debug log, then reproduce the simultaneous failure on the two TS0505B devices. Done requires a confirmed cause and a verified fix.

Written by the indexing model from the issue text.

Assessment

Domain
embedded-iot
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.