Universal Tuya docsHomeSupported devicesRequest a deviceFAQChangelogArchitectureKnowledge baseCreditsSourcesContributing

P3077 — phantom couples: one couple, one driver

Owner request t614u (dlnraja, 27/10/2026 Paris): check online whether each mfr+pid couple is real and decide keep / move / edit / remove.

Method

Batch 1 — 18 mfr moves (wrong class, unattested on the source driver)

mfrremoved fromstays onreal pidhardwaresourceauthor
_TZ3000_nbnmw9ncdimmer_wall_1gangbulb_dimmableTS0501ALidl/Livarno dimmable bulblinkzigpy ZHA quirks contributors
_TZ3000_nosnx7imdimmer_wall_1gangbulb_dimmableTS0501ALidl/Livarno dimmable bulblinkzigpy ZHA quirks contributors
_TZ3210_dbilpfqkdimmer_wall_1gangbulb_dimmableTS0501Bsingle-colour dimmable LED (ts0501bs)linkzigpy ZHA quirks contributors
_TZ3210_dxroobu3dimmer_wall_1gangbulb_dimmableTS0501Bsingle-colour dimmable LED (ts0501bs)linkzigpy ZHA quirks contributors
_TZ3000_qd7hej8udimmable_led_stripbulb_rgbTS0505A/TS0505B/ZB-CL01RGB E27 bulblinkJohan Bendz
_TZ3210_mja6r5ixdimmable_led_stripbulb_rgbTS0505A/TS0505B/ZB-CL01RGB E27 bulblinkJohan Bendz
_TZ3000_q50zhdscdimmable_led_stripbulb_rgbTS0505A/TS0505B/ZB-CL01RGB E27 bulblinkJohan Bendz
_TZB210_zdvrsts8bulb_rgbwbulb_rgbTS0503BSkydance WZ5 RGB controller (RGB only, no white channel)linkKoenkk / zigbee-herdsman-converters contributors
_TZ3210_ttkgurpbwall_dimmer_tuyabulb_rgbwTS0504BMiBoxer FUT038Z RGBW LED controllerlinkKoenkk / zigbee-herdsman-converters contributors
_TZ3210_huzkzqykwall_dimmer_tuyalcdtemphumidluxsensorTS0201/TS0222LCD temperature/humidity/lux sensorlinkJohan Bendz
_TZ3210_k1pe6ibmwall_dimmer_tuyargb_led_strip_controllerTS0503A/TS0503B/TS0504B/TS0505BRGB LED strip controllerlinkJohan Bendz
_TZ3210_r0xgkft5led_controller_cctrgb_mood_lightTS0505A/TS0505BRGB mood lightlinkJohan Bendz
_TZ3000_cymsnfvfbutton_wireless_2plugTS011FZP-LZ-FR2U smart pluglinkKoenkk / zigbee-herdsman-converters contributors
_TZ3000_ew31dmgxbutton_wireless_2plugTS011FTS011F smart pluglinkJohan Bendz
_TZ3000_hyfvrar3button_wireless_2plugTS011FSM0212 smart pluglinkKoenkk / zigbee-herdsman-converters contributors
_TZ3000_kdi2o9m6button_wireless_2plugTS011FTS011F smart pluglinkJohan Bendz
_TZ3000_plyvnuf5button_wireless_2plugTS011FLidl HG06337 pluglinkKoenkk / zigbee-herdsman-converters contributors
_TZ3000_upjrsxh1button_wireless_2plugTS011FLidl HG06337 pluglinkKoenkk / zigbee-herdsman-converters contributors

Note: the local KB labelled _TZ3210_ttkgurpb as FUT089Z; the zhc source (miboxer.ts) says FUT038Z RGBW controller, so it stays on bulb_rgbw.

Kept on purpose (same device class on both drivers, or attested on both)

Publish budget (publish caps 15500)

Porting P3055 and batch 1 to master first pushed the capped publish payload to 15662 combos (limit 15500). The cause was not the new guard pins: 31 _TZ3000_9ni6xxld couples (x2 case forms) that P3055 had removed from gas_sensor_switch as parasites were still "owned" by plug_energy_monitor, where the mfr sits next to 77 productIds. The baseline resolver re-pinned them there, adding 28 productIds x 12 mfrs (+336 combos).

Fix: resolveBaselinePins now honours an exemption before it looks for a new owner (the gate already keys exemptions on mfr+pid), and the 62 P3055 9ni6xxld removals got their exemption. No exempted couple is attested (checked against data/kb/couples.json). Result: 15497 combos, P3024b all 14227 couples present, no sacred pin missing, no attested couple lost (973 attested couples in the capped payload vs 959 before).

_TZE284_6ycgarab + TS0205: P3067 gave it a single owner (smoke_sensor); the P3055 decision rows now say so.

Batch 2 (27/10/2026, owner t614u)

Each mfr below sat on a second driver only through the mfr x pid product. It stays on the driver of its real hardware.

mfrdropped fromstays on (real pid)hardwaresource (author)
_TZ3000_c8ozah8npir_sensor_2motion_sensor (TS0202)battery PIR (ZP01 family)https://github.com/Koenkk/zigbee2mqtt/issues/26084 (activa73)
_TZ3000_mmtwjmaqpir_sensor_2motion_sensor (TS0202)battery PIRhttps://github.com/Koenkk/zigbee2mqtt/issues/11663 (jocamane), #7881 (1iverea9er)
_TZ3000_wamqdr3fplug_energy_monitorplug (TS011F)Lidl Silvercrest HG06337 FR plug, no meteringzigbee-herdsman-converters lidl.ts (Koenkk and contributors)
_TZB000_42ha4rsccurtain_motor_shuttercurtain_motor (TS030F)Lidl Livarno HG09648 roller blindzigbee-herdsman-converters tuya.ts whitelabel (Koenkk and contributors)
HOBEIANsensor_contact_zigbeecontact_sensor (ZG-102Z)HOBEIAN door sensorzigbee-herdsman-converters hobeian.ts (Koenkk and contributors)
_TZ3000_dpo1ysakplugsmartplug (TS011F)TS011F plug with meteringhttps://github.com/Koenkk/zigbee-herdsman-converters/pull/3076 (dmaasland), #3107 (kloknibor)

_TZ3000_42ha4rsc (a _TZ3000_ copy of the Lidl _TZB000_ id that no outside source lists) stays on curtain_motor_shutter: data/mfs_db.json knows it and the anti-purge guard forbids dropping it. Owner review. Only dpo1ysak on plug was in the last Athom package: 12 couples (2 case forms x 6 pids) got a t614u exemption. Paired devices keep working: Homey does not re-match an existing device.

Kept after review: HOBEIAN on gas_sensor (ZG-225Z), siren (ZG-229Z), ir_blaster (ZG-IR01), curtain_motor (ZG-301Z-MOTO), because hobeian.ts keys these by vendor zigbeeModel and the audit only knew TS pids. _TZ3290_ixd9mvv4 (TS0049 LYAI-14) stays on both valve drivers per P3055. _TZ3000_pzui3skt is really a TS0041 one-button remote (zigbee2mqtt #8500 by snp88, Johan Bendz README), but the knob entry is pinned by rotary-knob-ssot (P2448), so it waits for the owner. 9ni6xxld and heiman are reviewed duals.

Batch 3 (27/10/2026, owner t614u): manufacturer ids used as productIds

water_leak_sensor and water_leak_sensor_tuya listed _TZ3000_kyb656no and _TZ3000_eit6l5 (both case forms) as productIds. Homey crossed them with every mfr of the driver: 146 phantom couples (76 + 70), none in the last Athom package. _TZ3000_kyb656no is a real manufacturerName (Meian SW02 whitelabel, TS0207, zigbee-herdsman-converters tuya.ts) and stays as a mfr on both drivers; _TZ3000_eit6l5 is a cut-off id no source reports. P3055 already dropped the same two pids from gas_sensor_switch. q9mpfhw looks like a cut-off id too but is a real zigbeeModel upstream, so it stays.

Batch 4 (27/10/2026, owner t614u): TS130F curtain switches off curtain_motor_shutter

Six makers are TS130F curtain/shutter wall switches in zigbee-herdsman-converters tuya.ts (Koenkk and contributors): _TZ3000_5iixzdo7 (LoraTap SC500ZB-v4), _TZ3000_bs93npae (BSEED EC-GL86ZPCRS31), _TZ3000_74hsp7qy (Zemismart ZN-LC1E), _TZ3000_8h7wgocw (Danor SK-Z802C-US), _TZ3000_vw8pawxa (Zemismart TS130F_ZEMISMART), _TZ3210_xbpt8ewc (QA QACZ1). curtain_motor lists TS130F and the runtime map already sends them there; curtain_motor_shutter has no TS130F, so its 24 case forms only produced phantom couples (lights, climate and TS0601 pids). They leave curtain_motor_shutter; the 72 couples of the last Athom package that came from that product carry t614u exemptions.

Batch 5 (27/10/2026, owner t614u): heobian is a typo, not a device string

heobian / Heobian / HEOBIAN sat on 18 driver composes (41 entries, about 2090 couples) as "Athom forms" of HOBEIAN. No device reports that string: zigbee-herdsman-converters hobeian.ts (Koenkk and contributors) uses the vendor HOBEIAN, ZHA, deCONZ, Blakadder and Johan list only HOBEIAN, and the one web hit is a spelling slip in a Homey forum message about a HOBEIAN ZG-222Z (community.homey.app topic 140352). The forms leave every compose and the pairing form list (brandAthomForms) shrinks to HOBEIAN / Hobeian / hobeian. The read-time alias stays: normalize() still maps heobian to hobeian, so lookups, diags and collision tools treat both as one brand. The 10 couples of the last Athom package (button_wireless_1, heobian/Heobian × 5 pids) carry t614u exemptions; the sacred pin heobian|ZG-101ZL is dropped (it guarded against a bot strip, not a real device).

Batch 6 (27/10/2026, owner t614u): pzui3skt and the HOBEIAN ZG-101ZD knob

Batch 7 (27/10/2026, owner t614u): _TZ3000_42ha4rsc is a parasite

Batch 8 (27/10/2026, owner t614u): the Loginovo ZG-101Z SOS button

Batch 9 (27/10/2026, owner t614u): Nous E8 smoke sensor and the short dcnsggv dimmer id

Batch 10 (27/10/2026, owner t614u): 4mh6tyyo prefix copies, amp6tsvy pinned

Batch 11 (27/10/2026, owner t614u): Zbeacon TS020x no longer duplicated on doorwindowsensor_4

Batch 12 (27/10/2026, owner t614u): TS0502A CCT lights, one driver

Batch 13 (27/10/2026, owner t614u): ZG-101ZD, a HOBEIAN-only modelId

Batch 14 (27/10/2026, owner t614u): gjnozsaz, a plug and not a button

Batch 15 (27/10/2026, owner t614u): dfgbtub0, two pids and two drivers

Batch 16 (27/10/2026, owner t614u): amp6tsvy belongs on 1-gang only

Batch 17 (27/10/2026, owner t614u): claeh5ds is a tunable-white bulb

Batch 18 (27/10/2026, owner t614u): three reviewed duals, fixing the runtime hints only

These three manufacturers are in data/native-matrix-reviewed-duals.json, where the owner decided on 2026-10-04 to keep the old entry next to the exact couple. Nothing is removed from any compose here. Only the runtime hints are corrected to point at the attested driver. Removing the old entries needs an explicit override from the owner.

Batch 19 (27/10/2026, owner t614u): water-leak trio on water_leak_sensor

Batch 20 (27/10/2026, owner t614u): two bulbs and a dimmer back on their drivers

Flow batch 1 (orphan WiFi triggers)

Flow batch 2 (radar distance, soil temperature)

Flow batch 3 (siren cards)

Flow batch 4 (shutter movement, vacuum cleaning)

Flow batch 5 (temperature, humidity and soil thresholds)

Flow batch 6 (power exceeds the flow's own threshold)

Flow batch 7 ("Left open for duration", shared bounded timer)

device_din_rail_meter: dehumidifier cards kept, never fired (owner decision 27/10/2026)

Orphans left out: they need a capability the driver does not have

These are not wired, and no capability is invented for them:

Pending

← Knowledge base index · source