Soil sensors pairing as "unknown" (#570 AOYAN AY-303Z, #571 QT-07S _TZE284_myd45weu), 2026-10-13
Reports: GH #570 (Homey SHS, v9.0.1444) and #571 (Homey Pro mini 2025, v9.0.1445), both Homey 13.5.1. Symptoms: pairing ends as "Unknown Zigbee device / no compatible app", and App Settings stays on its spinner.
What was checked
- Fingerprints: both couples are in
soil_sensorin the shipped app.json (AOYAN|AY-303Z, _TZE284_myd45weu|TS0601). Endpoint 1 declares clusters [0, 61184]; both interviews expose 0 and 61184 → the cluster filter is satisfied. No other driver claims AY-303Z, and_TZE284_myd45weulives only on soil_sensor (W4 OK). - Padded
"AOYAN "(cf581c339b, first shipped 9.0.1442): it only adds a Homey-side alternative, the plainAOYANstays listed, and it cannot explain #571 (other maker). Kept (additive); runtime identity now trims at every read path (ManufacturerNameHelper already did; DeviceIOFacade + HomeyCompensationLayer added). Test P2810. - Manifest size: app.json ≈ 2.478 MB, flat since at least 9.0.1425 (2,477,928 B) → 9.0.1445 (2,478,025 B); ≈912k mfr×pid combinations (9.0.1300: ≈921k). No size jump around 1442–1445.
- Structural diff 9.0.1438 → 9.0.1445: only manufacturerName/productId lists on siren, soil_sensor, switch_1gang, water_leak_sensor changed; no new keys, no invalid/empty/duplicate entries.
- Stable 5.12.407 (live) carries the same two couples (without the padded form), 1.75 MB manifest.
- Diagnostics (3 reports): the app boots normally (drivers init, deferred features ready ~1 min later); no error in the captured tail. Settings code calls
Homey.ready()synchronously (P2717), so a permanent spinner means the settings page never got the app's homey.js bridge, i.e. Homey considered the app not responsive.
Working hypothesis (not confirmed)
Not a fingerprint problem. Most consistent with the app not being "ready" on the Homey at pairing time (long boot on Pro mini / SHS, or a restart loop), which also explains the endless settings spinner.
Next data needed (to request from the reporters, through the owner only)
- App state in Settings → Apps right after a Homey restart, and time until Configure opens.
- Pairing again ≥5 min after the app shows Running.
- A/B: same device with the live 5.12.407 build (same couples, smaller manifest).
_Rescued by P3062 on 26/10/2026 from the soil-1013/wa-master worktrees; figures are those of 13/10. The read-time trim landed on master with test test/critical/p3062-padded-mfr-io-trim.test.js._