[New device support]: TS0603 from _TZE608_q5fvikim
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 74/100
- Issue type
- Feature
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- typescript
- Domain
- embedded-iot
Research direction
Start with the provided TS0603 external definition and locate the Tuya converter tests for comparable TS0603 garage modules. Add an official definition with DP 1 exposed as a switch and DP 2 as a binary contact sensor, then verify identification and that the relevant converter tests pass.
Written by the indexing model from the issue text.
Description
Link
https://www.amazon.de/dp/B0F1YC7LSN?ref=ppx_yo2ov_dt_b_fed_asin_title
Database entry
"The database file (.db) was not directly accessible in my file view, but the exact device signature is _TZE608_q5fvikim with model TS0603 (Tuya 2-gang/garage module utilizing datapoint 1 for switch and datapoint 2 for contact sensor)."
Zigbee2MQTT version
2.14.2 (unknown)
External definition
import * as m from 'zigbee-herdsman-converters/lib/modernExtend';
export default {
zigbeeModel: ['TS0603'],
model: 'TS0603',
vendor: '_TZE608_q5fvikim',
description: 'Automatically generated definition',
extend: [m.identify()],
};
What does/doesn't work with the external definition?
Das ist nach dem langen Hin und Her jetzt tatsächlich der sauberste und schnellste Weg. Die Entwickler von Zigbee2MQTT fügen fehlende Tuya-Geräte (TZE608...) meist innerhalb weniger Tage offiziell in den Hauptzweig ein, wenn man ihnen einen sauberen Bugreport mit allen nötigen Daten gibt.
Hier ist eine präzise, englischsprachige Fehlerbeschreibung, die du direkt für das GitHub-Issue bei Zigbee2MQTT verwenden kannst. Sie enthält alle technischen Kennungen, die der Entwickler braucht:
Title:
New device support: Tuya Garage Door Opener (TS0603, _TZE608_q5fvikim)
Description:
Hello team,
I would like to request official support for a Tuya-based garage door opener module (QS-Zigbee-C03). Currently, the device is recognized as a generic router with TS0603, but it lacks proper exposes and control entities.
Device Information:
Model: TS0603
Manufacturer: _TZE608_q5fvikim
Device Type: Router (Powered)
Endpoints / Clusters: (From the frontend / interview)
Endpoints: 1
Standard Tuya datapoints (tuya.fz.datapoints / tuya.tz.datapoints):
DP 1: Switch / State (Impulse for garage door trigger)
DP 2: Contact / Binary sensor (Magnetic door sensor)
Notes
software_build_id: undefined
date_code: ``
endpoints:
{"1":{"bindings":[],"clusters":{"input":["genBasic","genIdentify","genGroups","genScenes","manuSpecificTuya"],"output":["genTime","genOta"]},"configured_reportings":[],"scenes":[]},"242":{"bindings":[],"clusters":{"input":[],"output":["greenPower"]},"configured_reportings":[],"scenes":[]}}
- Dominant language
- TypeScript
- Stars
- 15.8k
- Forks
- 2.2k
- Avg merge
- 1d 16h
- Merged PRs (30d)
- 47
Getting set up
Starts the project's dev container in your browser, under your own GitHub account.
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from Koenkk/zigbee2mqtt
-
Difficulty 2/5 1-3 hours Newbie friendliness 83/100
Koenkk/zigbee2mqtt#33613 · 1 comment ·
Maintainers usually reply within 1 day
-
problem
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Koenkk/zigbee2mqtt#33611 ·
Maintainers usually reply within 1 day
-
problem
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
Koenkk/zigbee2mqtt#33596 ·
Maintainers usually reply within 1 day
-
problem
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Koenkk/zigbee2mqtt#33592 ·
Maintainers usually reply within 1 day
-
new device support
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Koenkk/zigbee2mqtt#33577 · 1 comment ·
Maintainers usually reply within 1 day
All issues in Koenkk/zigbee2mqtt
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
transitmatters/shutdown-tracker#155 ·
Maintainers usually reply within 2 days
-
Popping out a single panel leaves its always render overlay in the main window, blocking clicksOpenbug triaged
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
Maintainers usually reply within 1 day
-
"Claude Code request is missing its initial user message" when the prompt starts with an image pathOpen
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
earendil-works/pi-claude-code#31 ·
Maintainers usually reply within 8 days
-
bug pending triage
Difficulty 1/5 Under an hour Newbie friendliness 92/100
privatenumber/cleye#48 ·