Universal Tuya docsHomeSupported devicesRequest a deviceFAQChangelogArchitectureKnowledge baseCreditsSourcesContributing

Method coverage (P3017): family × method

Generated by scripts/kb/method-coverage.js from lib/zigbee/MethodCoverage.js. ✅ = implemented and applied, — = not applicable (reason below), ❌ = missing.

#methodgroupimplementation
M1read.zcl_attrreadlib/zigbee/MethodChain.js → standardReadSteps
M2read.ef00_dpreadlib/zigbee/MethodCoverage.js → refreshCapability
M3read.private_clusterreadlib/zigbee/MethodCoverage.js → PRIVATE_READS
M4read.alt_endpointreadlib/zigbee/MethodChain.js → standardReadSteps
M5read.pollingreadlib/zigbee/FallbackChains.js → readSensorWithFallbacks
M6read.dataquery_0x03readlib/zigbee/MethodChain.js → standardReadSteps
M7read.derivedreadlib/zigbee/MethodCoverage.js → DERIVED
M8write.zcl_cmd_to_dpwritelib/zigbee/CapabilityCommandRouter.js → writeCapabilityWithFallbacks
M9write.attr_vs_cmdwritelib/zigbee/CapabilityCommandRouter.js → writeCapabilityWithFallbacks
M10write.mfr_specificwritelib/zigbee/ZclFrameHeader.js → parseZclHeader
M11startup.magic_packetstartuplib/zigbee/TuyaMagicPacket.js → sendTuyaMagicPacket
M12startup.time_sync_0x24startuplib/zigbee/.tuya/TuyaMcuTimeService.js → buildEf00TimePayload
M13startup.reporting_to_pollingstartuplib/zigbee/FallbackChains.js → readSensorWithFallbacks
M14unknown.unsupported_memoryunknownlib/zigbee/UnsupportedRegistry.js → getRegistry
M15unknown.interpreterunknownlib/zigbee/UnknownCommandInterpreter.js → interpretDp
M16unknown.learningunknownlib/zigbee/UnknownLearning.js → teach
M17unknown.flow_eventunknownlib/zigbee/.flow/UnknownCommandFlowCards.js → register
M18chain.failover_winnerchainlib/zigbee/MethodChain.js → runChain
M19chain.reprobe_backoffchainlib/zigbee/MethodChain.js → BACKOFF_MS
M20chain.never_remove_capschainlib/zigbee/MethodChain.js → runChain
familyM1M2M3M4M5M6M7M8M9M10M11M12M13M14M15M16M17M18M19M20
switch_plug✅✅✅✅✅✅✅✅✅✅✅✅✅✅✅✅✅✅✅✅
dimmer_light✅✅✅✅✅✅✅✅✅✅✅✅✅✅✅✅✅✅✅✅
cover✅✅✅✅✅✅—✅✅✅✅✅✅✅✅✅✅✅✅✅
thermostat_trv✅✅✅✅✅✅—✅✅—✅✅✅✅✅✅✅✅✅✅
climate_sensor✅✅✅✅✅✅—✅✅✅✅✅✅✅✅✅✅✅✅✅
motion_presence✅✅—✅✅✅—✅✅—✅✅✅✅✅✅✅✅✅✅
ias_contact_water_smoke✅✅—✅✅✅————✅✅✅✅✅✅✅✅✅✅
button_remote✅✅✅✅✅✅——✅—✅✅✅✅✅✅✅✅✅✅
meter_din✅✅✅✅✅✅✅✅✅—✅✅✅✅✅✅✅✅✅✅
valve_irrigation✅✅✅✅✅✅✅✅✅✅✅✅✅✅✅✅✅✅✅✅
siren✅✅✅✅✅✅✅✅✅—✅✅✅✅✅✅✅✅✅✅
lock✅✅—✅✅✅—✅✅—✅✅✅✅✅✅✅✅✅✅
fan✅✅✅✅✅✅✅✅✅—✅✅✅✅✅✅✅✅✅✅
soil✅✅✅✅✅✅————✅✅✅✅✅✅✅✅✅✅

Why some cells are "—"

P3019: per-cell justification

Every cell that is not ✅, and every ✅ that comes from a P3019 complementary layer (optional, never required at pairing, never removes anything). Re-checked against Z2M tuya.ts, ZHA quirks, deCONZ DDF, kkossev, SmartThings Edge, tuya-local/localtuya/tinytuya, Johan + forks.

familymethodstatusjustification / source
coverM7 read.derived—none of the family capabilities can be computed from siblings (alarm_battery is not derived: project rule, never both alarm_battery and measure_battery)
thermostat_trvM7 read.derived—none of the family capabilities can be computed from siblings (alarm_battery is not derived: project rule, never both alarm_battery and measure_battery)
thermostat_trvM10 write.mfr_specific—TRV settings are EF00 DPs (M8); no private-cluster write sourced
climate_sensorM7 read.derived—none of the family capabilities can be computed from siblings (alarm_battery is not derived: project rule, never both alarm_battery and measure_battery)
motion_presenceM3 read.private_cluster—radar/PIR settings travel as EF00 DPs (M2), no private ZCL attribute in Z2M/ZHA
motion_presenceM7 read.derived—none of the family capabilities can be computed from siblings (alarm_battery is not derived: project rule, never both alarm_battery and measure_battery)
motion_presenceM10 write.mfr_specific—radar settings are EF00 DPs (M8); no private-cluster write sourced
ias_contact_water_smokeM3 read.private_cluster—IAS zone only; Tuya extras (sensitivity DP9) are EF00 DPs, covered by M2
ias_contact_water_smokeM7 read.derived—none of the family capabilities can be computed from siblings (alarm_battery is not derived: project rule, never both alarm_battery and measure_battery)
ias_contact_water_smokeM8 write.zcl_cmd_to_dp—sleepy IAS sensors; sensitivity DP9 is read-only in the drivers (no sourced write path)
ias_contact_water_smokeM9 write.attr_vs_cmd—sleepy IAS sensors; no writable attribute used by Z2M for this family
ias_contact_water_smokeM10 write.mfr_specific—no manufacturer-specific write found for this family in Z2M/ZHA/deCONZ
button_remoteM3 read.private_cluster✅ (P3019)genOnOff 0x8004 tuyaOperationMode read (TS004F family, passive + one read for new devices); source: z2m tuya.ts TS004F operation_mode (genOnOff tuyaOperationMode 0x8004); ZHA TuyaSmartRemoteOnOffCluster
button_remoteM7 read.derived—none of the family capabilities can be computed from siblings (alarm_battery is not derived: project rule, never both alarm_battery and measure_battery)
button_remoteM8 write.zcl_cmd_to_dp—remotes have no capability to command; mode change is an attribute write (M9)
button_remoteM9 write.attr_vs_cmd✅ (P3019)genOnOff 0x8004 attribute write when the user changes button_mode (writeAttributes, then raw fallback); source: z2m tuya.ts TS004F operation_mode (write genOnOff tuyaOperationMode)
button_remoteM10 write.mfr_specific—E001 0xD020 switch_mode belongs to wall switches (TS0726/TS0012), not remotes
meter_dinM10 write.mfr_specific—DIN meters use EF00 DPs or standard ZCL; no private-cluster write sourced
valve_irrigationM10 write.mfr_specific✅ (P3019)0xE001 setCountdown 0xFE (HZ-WT02, TS0049 _TZ3000_kz1anoi8), opt-in setting ts0049_water_countdown; source: z2m tuya.ts HZ-WT02 manuSpecificTuyaE001 setCountdown 0xFE (tzLocal/fzLocal.ts0049_countdown)
sirenM10 write.mfr_specific—sirens use EF00 DPs or IAS WD; no private-cluster write sourced
lockM3 read.private_cluster—Tuya locks use EF00 DPs (M2) or standard doorLock; no private ZCL attribute sourced
lockM7 read.derived—none of the family capabilities can be computed from siblings (alarm_battery is not derived: project rule, never both alarm_battery and measure_battery)
lockM10 write.mfr_specific—locks use EF00 DPs or doorLock; no private-cluster write sourced
fanM10 write.mfr_specific—fans use EF00 DPs or fanControl; no private-cluster write sourced
soilM7 read.derived—no derivable capability (moisture/temperature/battery are measured)
soilM8 write.zcl_cmd_to_dp—calibration DPs exist (Z2M) but Homey soil settings are software offsets: writing them too would apply the offset twice
soilM9 write.attr_vs_cmd—sleepy EF00-only sensor: no ZCL attribute to write
soilM10 write.mfr_specific—no private-cluster write for soil sensors in Z2M/ZHA

Write through another endpoint

Evaluated in P3019 and not added: no source (Z2M, ZHA, deCONZ, kkossev) needs a write on a second endpoint for a single-endpoint device, and on multi-gang devices a fallback endpoint could switch the wrong gang. Reads may use the alternate endpoint (M4); writes stay on the capability endpoint.

Chain order and behaviour

zcl-native → zcl-raw-numeric → tuya-dp → tuya-private → alt-endpoint → poll → magic-query → derived (lib/zigbee/MethodChain.js). Unsupported (0x81/0x84/0x86/0xC3) demotes at once; timeout demotes after 2 in a row; other errors fail over without demotion. A demoted method is re-probed after 15 min, 1 h, 4 h, 12 h, then every 24 h. The winner is remembered per device (store method_chain_state, at most 60 domains). Capabilities are never added or removed by the chain. Entry points: device.refreshCapabilityChain(cap), readSensorWithFallbacks(..., { failover: true }) (used by the reporting → polling fallback), writeCapabilityWithFallbacks.

← Knowledge base index · source