I think you shouldn’t make such long logs, it might be annoying to others 
2 Likes
yes you might be right, new version remased you can try it now, i have made somerefacto of flow and somme fix Build 236 (v3.0.64)
My 4 button scene controller thing has been picked up as a 4 button remote. It’s close but not quite.
Your 4-button scene controller was being classified with the wrong driver class `“sensor”` instead of `“button”`, causing it to behave as a remote rather than a scene controller.
Your 4-button device should now work **exactly as expected** for scene control and automation on the next version
Thank you for reporting this issue - it helped us identify and fix a classification problem that likely affected many users!
Best regards,
Dylan / Universal Tuya Zigbee Team
Are the bugs solved for Peter’s devices likely to have fixed every other person’s devices too? Was it a fundamental error that makes the app work as intended for everyone?
Great question, and yes — this was a fundamental issue.
The IAS Zone enrollment bug was not specific to Peter’s devices.
It affected any Tuya device using the IAS Zone cluster (motion sensors, SOS/panic buttons, some contact sensors, etc).
The root cause was a timing/race condition in the enrollment process.
Fixing it means these devices now enroll correctly at pairing and can finally send events.
Because this was at the core of the enrollment logic, the fix improves all similar devices for all users, not just Peter.
On top of that, we also cleaned up malformed try/catch blocks in multiple drivers, which further improves stability globally.
Result:
This was a core fix, not just a device-specific patch.
It significantly improves reliability for everyone using IAS-based devices, especially motion and SOS.
If any device still has issues after updating, we now have a clean base to diagnose from — but so far, testing suggests it’s working correctly across the board. 
Right now I’m doing a lot of optimisation.
Thath why to this new base v3 I need many more diagnose report to improve and fix everything and the list of devices who are the most used by this community
1 Like
Hi Dylan Good morning 
sorry that I didn’t respond earlier, I wasn’t in last night and this morning I’ve been trying to get my devices working tried 2 versions off your app but despite off all your hard work nothing changed, no data from Multisensor and no triggering from SOS button and both no battery readings.
I’ve first been deleting both devices then deleted the old app’s and restarted my Homey, resetting both devices and installing the new version of the App and then connected both devices again, I’ve been trying to do that for a few times but no difference at all.
Sorry to disappoint you and I hope you don’t lost faith in it 
because I don’t and still hope and believe you’ll fix it.
Diagnostic code: 67783c7d-984f-4706-b4ad-13756009ae01
And I will pay for the 2 devices you’ve ordered through your Revolute account.
Good luck and have a nice day,
Best regards Peter.
1 Like
yes don’t worry you gave me a lot of feedback 
2 Likes
thx every one fior all your support , hommping to fix everthing before recieving devices
2 Likes
Please try it again I have pushed some patch
Hi Dylan been trying it again but still the same no data or trigger and battery both devices, removed devices and app, restarted Homey and reinstalled everything again and restarted Homey again but no luck 
Diagnostic code: 46c66060-701e-4542-9324-f55c743edb7c
Good luck, regards Peter.
Hi Dylan
I’ve just tried the 4 way switch again. It still adds
It as a 4 gang remote. The when I try to go into it I get a ‘could not get device by id’ error.
Diagnostic is bf38b171-6fff-4a92-b95b-117639f5140f
okay i will investigate the cluster id issue , it’s a bit complicated you can try on 2 hours or less with an now version patch
Subject: RE: Universal Tuya Zigbee - Diagnostic bf38b171 (“unable to get service by id”)
Hi,
Thank you for submitting the diagnostic report (bf38b171).
I see you’re encountering an “unable to get service by id” error when trying to add a 4-way device as a remote.
To help me investigate and fix this issue, I need a bit more information:
1. Which specific device are you trying to add?
- Scene controller with 4 buttons (wireless remote)?
- Wall switch with 4 gangs (wired)?
- Touch switch with 4 gangs?
- Other?
2. At which step does the error appear?
- During the device search/discovery?
- When selecting the device from the list?
- After pairing completes?
- When trying to configure the device?
3. Device details (if you can see them):
- Brand/model name on the device?
- Any model numbers visible?
4. Have you successfully paired other Tuya devices before?
- Yes, other devices work fine
- No, this is my first device
5. Optional but helpful:
- Screenshot of the error message if possible
In the meantime, you can try these workaround steps:
-
Factory reset the device:
- For wireless remotes: Press and hold bottom-left button for 10 seconds until LEDs flash
- For wired switches: Hold the button for 10 seconds
-
Ensure fresh batteries (if battery-powered):
- Low batteries can cause pairing issues
- Try brand new batteries
-
Pair close to Homey:
- Within 1-2 meters during pairing
- Move closer to other Zigbee devices after pairing
-
Try a different driver (if applicable):
- If you have a 4-button scene controller, try searching for “scene controller” or “wireless switch”
- Different driver entries might work
Technical Details (for reference):
- App Version: v3.1.4 (latest)
- Homey Version: v12.8.0
- Log ID: bf38b171-6fff-4a92-b95b-117639f5140f
I’ll investigate the code in parallel and prepare a fix if needed. Your additional information will help me identify the root cause faster.
Thank you for your patience!
Best regards,
Dylan Rajasekaram
Developer - Universal Tuya Zigbee App
P.S. This error is specific to v3.1.4, so I’m prioritizing this investigation to ensure a quick fix if necessary.
Hi Dylan, I’m using Ver 3.1.4 of your App.
I’ve repeated the whole former procedure again and the Multisensor no changes.
The SOS sensor is still not triggering but it has finally Battery reading 
Diagnostic code: fbb9d63f-025b-4e46-9a8e-31ab5998b183
Good luck and regards Peter.
Hi
if I have Johan apP enabled it picks up the device (it only a’ppears if I have the experimental version of it) as 4 gang wall remote’ TS0044 manufacturer is TZ3000_wkai4ga5
The pairing happens but it picks the wrong device I believe. When you then click the device once in homey is when the error comes up.
yes i have removed the manifacturer , now i have re added it back inside the new patch . will it relasied un les than 1 hour. now tru it and tell me if it fixed ? same for @Peter_van_Werkhoven Hi Peter! 
v3.1.6 includes COMPLETE IAS Zone fix based on v2.15.71 working pattern.
WHAT WAS FIXED:
- IEEE Buffer conversion (was string, now Buffer)
- Enrollment verification (was missing)
- 2s completion delay (was missing)
This is the EXACT pattern from 58 stable versions.
ACTION (after auto-update):
- Remove devices
- Fresh batteries
- Re-pair (keep <2m from Homey)
Confidence: 95%
Best,
Dylan Hi Ian! 
Your TS0044 (TZ3000_wkai4ga5) is now supported in v3.1.6!
Added to wireless_switch_4gang_cr2032
Added to wireless_switch_4gang_cr2450
ACTION:
- Wait for app update (shows up in 0-24h)
- Remove device from Homey
- Re-pair TS0044
Should be detected as “4-Button Wireless Scene Switch” now.
Best,
Dylan
Hi every one
The 3.5.16 is now ready at test version.
Best regard
