[APP][Pro] Universal TUYA Zigbee Device App - test

Hi Cam,

Thanks for the diagnostic! I reviewed log `5d3e1a5d-701b-4273-9fd8-2e8ffcfbf2ee`. The app initialization is clean (all 183 drivers loaded), but I need more info to diagnose your **button** and **motion sensor**.

### What I Need

**1. Manufacturer IDs** (crucial for support):

For each device:

1. Homey → Settings → Devices → [Your Device]

2. :gear: Settings → Advanced → Zigbee information

3. Copy `manufacturerName` (e.g., `_TZ3000_xabckq1v`, `TS0042`)

4. Share here

**2. Better Diagnostic** (current one only shows startup):

1. Homey → Settings → Apps → Universal Tuya Zigbee → Diagnostics

2. **Before submitting:**

  • Press button 3-4 times

  • Wave at motion sensor

  • Wait 30s

3. Submit with message: “Testing button + motion”

4. Share new log ID

**3. Symptoms:**

- Button: Paired? Battery shown? What happens when pressed?

- Motion: Paired? `alarm_motion` capability exists? Detects motion?

### Quick Fixes to Try First

**Button:**

1. Factory reset (hold 5s → LED blinks fast)

2. Re-pair within 2m of Homey

3. Use correct driver:

  • 1-button → `wireless_switch_1gang_cr2032`

  • 2-button → `wireless_switch_2gang_cr2032`

  • 4-button → `wireless_switch_4gang_cr2032`

**Motion Sensor:**

1. Factory reset (battery out 10s → hold button 5s)

2. **During pairing:** Stay 2m from Homey, wait 60s (IAS Zone enrollment)

3. Use correct driver:

  • PIR only → `motion_sensor_battery`

  • PIR + temp → `motion_sensor_temp_humid_battery`

  • mmWave → `motion_sensor_mmwave_battery`

**TS0601 devices:** v3.0.35 fixed TS0601 init—if your devices are TS0601, re-pair them.

### Resources

- **IAS Zone Fix:** https://github.com/dlnraja/com.tuya.zigbee/blob/master/docs/fixes/PETER_IAS_ZONE_FIX_COMPLETE.md

- **Device Request:** Sign in to GitHub · GitHub

Once you share manufacturer IDs + new diagnostic, I can pinpoint the issue!

Best,

Dylan

-–

## Follow-Up Actions

### Check Support

```bash

# When user provides manufacturer ID

grep -r “_TZ3000_XXXXXX” drivers/

```

### If Not Supported

1. Add ID to appropriate driver

2. Test locally

3. Release patch

4. Notify user

### Common Issues

- **Button:** Wrong driver, missing endpoints, battery

- **Motion:** IAS Zone not enrolled, wrong driver, battery