Hello Dylan,
(EDIT: Which app do you mean by “Official Tuya Cloud app”? It doesn’t exist:
Theres one “official” Tuya app by Athom, not usable by new users;
And there’s one “community” Tuya Cloud app by Jurgen Heine > the one you seem to bash.)
Wow…I really appreciate your work and dedication, but I just read your last long-ish update and couldn’t really believe my eyes: I hope you’ll remove this childish and blunt comparison to the Tuya Cloud app:
Community developers should not bash eachother like you do here, right? You actually give Jurgen “the finger” from what I read… Don’t go down to that level, you don’t really need that, honestly.
I think it’s just cheap and very unfriendly.
Thx.
Of course you can emphasise the benefits of zigbee over cloud connections in general, like privacy, dependency and such. Nothing wrong with that.
About the bullets:
1.
Absolutely not true. The API is fine, but to use it for free, longer than 6 months, users need to prolong that supscription twice a year.
Many don’t know / forgot and then complain the app just stopped working.
People have difficulties configuring the app, because they don’t follow instructions to the letter. This is not because the API or app is faulty.
It’s all in the very extended manual in post 1 of the TC community app topic.
I’d like to see a test please. The Tuya wifi devices respond almost faster than Homey zigbee. Note the word almost 
3
And? Many Homey apps out there need API keys or additional accounts, whatever, nothing new.
Yes Zigbee doesn’t need that, true. But that’s just the nature of a local protocol and a cloud protocol.
1 Like
Hi @dlnraja
Updated to v2.15.46 this morning and tried to add my devices again with the same results “unknown zigbee device”. Here are the devices I tried adding them as (being unsure which one will work):
Motion sensor with lux detection:
Motion sensor with battery
Motion sensor PIR battery
Motion sensor with illuminance (battery)
PIR Motion sensor
PIR Motion sensor advanced
PIR Motion sensor battery
Smart button:
Remote switch
Wireless switch
Aqara button
SOS emergency button
Sorry it was generated by my IA.
This section is removed on the original post
Best regard and thx a lot.
Sorry i don’t want to give any finger or to have any problem kindly sorry.
The feedback is very ussefull to understand the situation thx a lot.
Please add the débug log of the app and tell me diagnose report from développeur dashboard on the zigbee section pour understand features of your zigbee device ( interview report ).
Hi Dylan I installed version 2.15.49 and tried it again but still no changes, diagnostic report: 1c9d6ce6-21d8-4811-ae81-71a12be7fe0e
Thanks again for all your effort.
Good night and best regards Peter
okay iu will try another patch 
try tomorrow, i gonna sleep. the publish is on github action and will be published.
I posted it to Johan’s issues list and I’m pretty sure you said they’d been added. I’ll link to them again, hopefully you can find something new from them after having learned more about it all.
okay i will try another fix, you can check on te morning afternoon
v2.15.54 - GitHub Issues #1267 & #1268: ZG-204ZL + TS0041 4-Gang Fix
GITHUB ISSUES RESOLVED:
#1267: HOBEIAN ZG-204ZL PIR sensor with lux support
#1268: _TZ3000_5bpeda8u TS0041 4-gang button CRITICAL endpoint fix
SOURCE:
- Device Request - Zigbee PIR Sensor with lux - HOBEIAN / ZG-204ZL · Issue #1267 · JohanBendz/com.tuya.zigbee · GitHub
- Device Request - Zigbee Smart Button - _TZ3000_5bpeda8u / TS0041 · Issue #1268 · JohanBendz/com.tuya.zigbee · GitHub
FIX #1: motion_temp_humidity_illumination_multi_battery
FILE: drivers/motion_temp_humidity_illumination_multi_battery/driver.compose.json
CHANGE: Added ‘ZG-204ZL’ to productId array
IMPACT:
- HOBEIAN ZG-204ZL variant can now pair
- Illuminance sensor (lux) now functional
- Motion, battery, temp, humidity all supported
- AliExpress item 1005006918768626 users can now use device
FIX #2: wireless_switch_4gang_cr2032 (CRITICAL MULTI-ENDPOINT)
FILE: drivers/wireless_switch_4gang_cr2032/driver.compose.json
CHANGE 1 - Manufacturer ID:
- Added ‘_TZ3000_5bpeda8u’ to manufacturerName array
CHANGE 2 - Endpoints Structure (CRITICAL):
BEFORE (BROKEN):
{
‘1’: { clusters: [0, 4, 5, 6, 8], bindings: [1] }
}
Problem: Only 1 endpoint, buttons 2-4 don’t work!
AFTER (FIXED):
{
‘1’: { clusters: [0, 1, 6, 57344], bindings: [1] },
‘2’: { clusters: [1, 6] },
‘3’: { clusters: [1, 6] },
‘4’: { clusters: [1, 6] }
}
ENDPOINTS STRUCTURE (per Zigbee interview):
- Endpoint 1: [0, 1, 6, 57344] - Button 1 + basic + battery + Tuya cluster
- Endpoint 2: [1, 6] - Button 2 + battery + onOff
- Endpoint 3: [1, 6] - Button 3 + battery + onOff
- Endpoint 4: [1, 6] - Button 4 + battery + onOff
CLUSTERS CORRECTED:
- Removed: 4, 5, 8 (not in device interview)
- Added: 1 (powerConfiguration for battery)
- Added: 57344 (Tuya custom cluster)
- Kept: 0 (basic), 6 (onOff)
IMPACT:
- _TZ3000_5bpeda8u variant can now pair
- ALL 4 BUTTONS NOW WORK (was main complaint)
- Battery reporting functional
- Tuya cluster support
- Flow cards per-button work correctly
- AliExpress item 1005008942665186 users fixed
REFERENCE: Memory c001af1c
Multi-gang endpoint configuration pattern:
- 1gang: endpoint ‘1’ only
- 2gang: endpoints ‘1’ AND ‘2’
- 3gang: endpoints ‘1’, ‘2’ AND ‘3’
- 4gang: endpoints ‘1’, ‘2’, ‘3’ AND ‘4’ ← Applied here
USER BENEFITS:
- ZG-204ZL: Motion + Illuminance working
- TS0041: All 4 buttons functional (not just button 1)
- Proper SDK3 cluster configuration
- Matches actual Zigbee interview data
TESTING REQUIRED:
- Pair ZG-204ZL → verify motion + lux
- Pair TS0041 → test all 4 buttons
- Create flows with button-specific triggers
DOCUMENTATION:
- GITHUB_ISSUES_ANALYSIS.md - Complete analysis
- FIX_GITHUB_ISSUES_1267_1268.md - Implementation details"
Hello,
I saw your question in the GitHub thread regarding the number of buttons for the device. I can see why the AliExpress picture is confusing!
Here is the technical explanation for the device interview you posted:
1. The Physical Reality: It’s a 1-Button Device
The device model TS0041 (with the manufacturer _TZ3000_5bpeda8u) is actually a single-gang (1-button) Scene Switch. Looking at the typical AliExpress listings for this model, it is a small, portable button or a wall switch with just one pressable area.
2. The Technical Reason: Why Homey Sees 4 Endpoints
The reason the Zigbee device interview is reporting four endpoints (Endpoints 1, 2, 3, and 4) is due to the generic Tuya firmware:
* Endpoint 1: This is the primary endpoint, handling essential device data like the battery status (powerConfiguration) and basic info.
* Endpoints 2, 3, and 4: These are “ghost” endpoints. Tuya often uses the same underlying firmware for its 1-gang, 2-gang, 3-gang, and 4-gang switches (TS0041, TS0042, TS0043, TS0044). Even though your physical device only has one button, the firmware internally exposes up to four “potential” buttons.
Therefore, the app recognizes the maximum potential of the firmware but has to focus on the actual functionality.
3. How Homey Should Handle This (1 Button, 3 Actions)
Since this is a single physical button, the app typically ignores the phantom endpoints and focuses on the multiple actions sent by the one button you can press:
| Physical Action | Event in Homey Flow Card |
|—|—|
| Short Press | Single press |
| Double Press | Double press |
| Hold / Long Press | Long press or Hold |
You should be able to trigger three different flows from this single device once the driver is correctly implemented.
I hope this clarifies the mismatch between the image and the technical logs!
So that why it’s now implemented as wireless_switch_4gang_cr2032 on the app
Thanks for the explanation, @dlnraja.
From a user experience (UX) point of view, the user is looking for a description of the product they purchased, not how it works in the code. So, something more like the title they read when they purchased the product or an image, like Johan’s app works. That speaks more to the user than the technical definition. In the case of the user buying a product that’s called a 4 Gang Switch that makes sense though!
I just tried your new update that targeted my devices and I’m sorry to say I had no luck. I’ll be honest, I only tried adding the motion sensor to about 3 different times and gave up, not knowing which one it was meant to be.
Hopefully you can figure it out tomorrow, or someone with some expertise in all of this cough cough Johan take some pain away for you 
please try the v2.15.54 or later
v2.15.63 = same results.
okay i will move bacl to 1 gang back on the next pr _TZ3000_5bpeda8u Best regard
## FIXES NOW AVAILABLE IN v2.15.64
### **Your Specific Issues - NOW MUST BE RESOLVED:**
#### 1. **TS0041 Device (_TZ3000_5bpeda8u) - FIXED **
**Before v2.15.64:**
```
Device: TS0041 (_TZ3000_5bpeda8u)
Shows as: “4-Gang Wall Switch”
Physical: 1-button remote
```
**After v2.15.64:**
```
Device: TS0041 (_TZ3000_5bpeda8u)
Shows as: “1-Button Wireless Scene Switch (Battery)”
Physical: 1-button remote
```
**Technical Change:**
- `_TZ3000_5bpeda8u` **moved** from `wireless_switch_4gang_cr2032` → `wireless_switch_1gang_cr2032`
- Driver name changed: “Gang” → “Button” terminology
--
#### 2. **Motion Sensor Pairing - IMPROVED **
**Enhanced Driver Names:**
| Driver | Technology Label | Clarity |
|--------|-----------------|---------|
| Motion Sensor (Battery) | **Motion Sensor (PIR, Battery)** | Clear |
| Motion Sensor mmWave (Battery) | **Motion Sensor (mmWave Radar, Battery)** | Distinguishes from PIR |
**All 9 Motion Sensor Drivers Audited:**
- PIR technology clearly labeled
- mmWave/Radar clearly labeled
- IAS Zone support verified on all
- Manufacturer coverage: 34-61 per driver
could you tell me withc device is it
| Model | Description | Status | Driver |
|---|---|---|---|
| ZG-204Z | PIR Motion | v2.15.65 |
motion_sensor_pir_battery |
| ZG-204ZL | PIR + Lux | v2.15.54 |
motion_temp_humidity_illumination_multi_battery |
| ZG-204ZV | PIR + Temp + Hum + Lux | v2.15.54 |
motion_temp_humidity_illumination_multi_battery |
| ZG-204ZM | PIR + mmWave Radar |  looks not zigbee |
TBD |
Hey @dlnraja
Mine is the ZG-204ZL. I’ve just checked the store and it’s still saying .63 is the latest so I’ll keep checking in and let you know how it goes when the update shows up.
Thanks again for the efforts!
Hi Dylan Good morning 
and you’ve been working almost whole time through 
as I can see.
I’ve installed version 2.15.63 this morning and tried if the Motion was being detected on the HOBEIAN Multi sensor but still nothing happens 
And also the SOS button still doesn’t react on pressing the red button
Even no reactions in specially created Flows to see if something happens there, but also no action processed there.
Diagnostic code: 015426b4-01de-48da-8675-ef67e5911b1d
Thanks again and best regards Peter.
Hello @dlnraja, thank you so much for al your work on this app!!!
I have 2 devices I’m trying to install.
The first is a temperature and humidity sensor that is recognized as a smoke detector:
TZ3000_akqdg6g7 / TS0201
The other is a soil sensor that is not recognized:
_TZE284_oitavov2 / TS0601
okay v69 released , might be fixed , same for @Peter_van_Werkhoven can you try to check if there is any evolution
Good morning! Thank you so much for testing v2.15.63 and sending the
diagnostic report. I’ve analyzed your logs in detail and I found the
exact problem! 
now it’s akmost fixed i hope
