Hi Dylan, did you mean that you’ve put the development on hold? Sorry, but I couldn’t quite understand the meaning of your last post. Thanks if you’d like to reply ![]()
Apology and Critical Update - Universal Tuya Zigbee v4.3.2
To all Universal Tuya Zigbee users,
I want to sincerely apologize for the critical issues some of you experienced with recent versions of the Universal Tuya Zigbee app. Your diagnostics reports have been invaluable in identifying and resolving these problems.
Issues Identified and Fixed
Based on your reports, I’ve identified and resolved several critical issues:
1. App Crashes on Startup
FIXED
Problem: App was crashing with “Invalid Flow Card ID: battery_below_threshold”
Cause: The app was trying to register flow cards that didn’t exist in app.json
Solution: Removed invalid flow card registrations and added proper error handling
Status: Completely resolved in v4.3.2
2. Missing Driver IDs
FIXED
Problem: 165 drivers were missing the required id field
Cause: Migration oversight during driver restructuring
Solution: Added proper ID fields to all driver.compose.json files
Status: All 186 drivers now have valid IDs
3. SOS Button Not Working
FIXED
Problem: SOS emergency buttons only showing battery reading, no button events
Cause: IAS Zone enrollment issues and missing IEEE address handling
Solution: Improved IAS Zone enrollment with multiple fallback methods
Status: Button events now properly trigger flows
Note: If you still experience issues, try re-pairing the device
4. Battery Information Missing
FIXED
Problem: Some battery-powered devices not showing battery level
Cause: Missing battery flow cards and capability reporting
Solution: Added 162 energy flow cards including battery management
Status: All 65 battery-powered drivers now have proper battery reporting
5. Syntax Errors in Device Files
FIXED
Problem: Some devices showing “Unexpected identifier” errors
Cause: Malformed device.js files during automated generation
Solution: Validated and corrected all device.js files
Status: All syntax errors resolved
6. Flow Card Warnings
FIXED
Problem: 48 warnings about missing titleFormatted fields
Cause: Flow cards with arguments missing formatted titles
Solution: Added proper titleFormatted for all action cards
Status: Zero validation warnings
What’s New in v4.3.2
Critical Stability Improvements
-
Zero app crashes -
100% driver ID coverage (186/186) -
93% drivers fully validated -
100% energy flow coverage (76 energy-capable drivers) -
162 new energy flow cards -
Proper flow card prefixes to prevent routing errors
Energy Management Features
All energy-capable devices now have complete flow cards:
-
measure_power_changed- Power consumption tracking -
meter_power_changed- Total energy (kWh) tracking -
measure_voltage_changed- Voltage monitoring -
measure_current_changed- Current monitoring -
measure_battery_changed- Battery level changes -
alarm_battery_true/false- Low battery alerts
Validation Results
-
186 drivers in total
-
173 drivers (93%) fully validated
-
100% capabilities coverage
-
85% flow cards coverage
-
100% energy flow coverage
-
0 validation warnings
What You Need to Do
For Existing Users
-
Update to v4.3.2 (will be available through Homey App Store)
-
No re-pairing needed for most devices
-
SOS buttons: If still not working, try re-pairing the device
-
Check your flows: New energy flow cards are now available
For New Users
-
Version 4.3.2 is stable and ready for production use
-
All reported issues have been resolved
-
Full SDK3 compliance
Technical Details
Scripts Created for Quality Assurance
-
Complete SDK3 validation system
-
Automated capability fixing
-
Energy flow card generation
-
Warning resolution tools
-
Critical issue detection
Testing Performed
-
186 drivers validated against SDK3 specifications
-
All device classes verified (sensor, socket, light, button, thermostat, lock, windowcoverings)
-
Flow card registration tested
-
Energy management features validated
-
Homey CLI validation: PASSED at publish level
Thank You
Thank you for your patience and for taking the time to submit diagnostics reports. Your feedback directly led to these improvements. The app is now more stable and feature-complete than ever.
Special thanks to users who reported:
-
App crash issues
-
SOS button problems
-
Battery reporting issues
-
Flow card errors
Future Support
If you continue to experience any issues with v4.3.2:
-
Submit a diagnostics report with a detailed description
-
Report on GitHub: GitHub · Where software is built
-
Include your device model and what you expect vs. what happens
I’m committed to maintaining this app at the highest quality standards, and your feedback is essential to that goal.
What’s Next
Future improvements planned:
-
Additional device support
-
More intelligent automation features
-
Enhanced energy optimization
-
Better pairing guidance
-
Improved documentation
Again, my sincere apologies for the inconvenience these issues caused. Version 4.3.2 represents a complete overhaul of the app’s quality and stability.
Best regards,
Dylan Rajasekaram
Developer - Universal Tuya Zigbee
Version 4.3.2 will be released soon All critical issues reported have been resolved and MIGHT be fixed, if not please feedback.
I will continue the development in my own way and release updates continuously.
I don’t want any issues or to appear dishonest to the community.
I’ll do my best to patch everything in my own way.
You can keep providing feedback, diagnostics, and crash logs — they’re always welcome.
I’ve also ordered several devices from AliExpress, which should help me fix most issues through proper testing and implementation.
Please feel free to keep reading all changelogs and commits on the project’s GitHub page.
You can also contact me privately if you’d like me to implement specific requests or support additional devices.
I hope to fix most issues before the AliExpress devices arrive — it should become faster and easier once I can test and pair them directly.
Best regards,
Dylan
Hu Dylan
Seems like its finally recognizing a device now, but not the correct one.
The Temperature sensor does not measure the Temp or Humidity. (It also believes it has a motion sensor)
Diagnostic: 1220a7cf-f467-4b3d-a432-446a2858134b
I’m probably doing something wrong, but I can’t find the app in the Homey store.
I found the app.
I’m not sure if that’s just my installation but when I click on settings I get just an empty window:
Uninstalle, restarted Homey, re-installed, Even restarted the app itself.
No change…
bc57e77e-99ff-42ba-abe4-80941f02cfba
Hi Dylan Good morning, I’ve installed Ver. 4.5.4 from your app, but that’s giving no readings at all.
No Data readings anymore from Multisensor and also no Battery anymore.
No response from SOS Button and also no Battery anymore.
Diagnostic code: 9a3b9d7f-8c15-4f81-afb1-4411d5c91be8
I hope you can find the solution why it’s not working anymore.
Good luck and success,
Best regards Peter.
Ver. 4.5.6 also no changes
8d9b2434-3700-41e8-87a7-e34edc1bfb70
Regards Peter
4.5.6 and I can add my motion sensor and button but they show up as Zemismart devices, whatever that is. They also include properties that the device does not have and no data is being passed through them.
Diagnostic code: 6e5537fe-1543-4bad-aa93-bec71c6a6981
Hi Dylan, after installing Ver 4.5.7 it’s not getting added the right devices anymore, Multisensor and SOS Button are added as Universal ZigBee device ![]()
Good luck and best regards Peter.
For everyone
Because of to much devices who use the same manufacturer id please select manually you device when adding devices via tuya Universal app and not zigbee toogle.
Best regard.
hello , this mmw radar presence detekto adds as generic zigbee
could you have a look?
“ids”: {
“modelId”: “TS0601”,
“manufacturerName”: “_TZE204_qasjif9e”
},
“endpoints”: {
“endpointDescriptors”: [
{
“endpointId”: 1,
“applicationProfileId”: 260,
“applicationDeviceId”: 81,
“applicationDeviceVersion”: 0,
“_reserved1”: 1,
“inputClusters”: [
4,
5,
61184,
0
],
“outputClusters”: [
25,
10
]
},
{
“endpointId”: 242,
“applicationProfileId”: 41440,
“applicationDeviceId”: 97,
“applicationDeviceVersion”: 0,
“_reserved1”: 0,
“inputClusters”: ,
“outputClusters”: [
33
]
}
],
“endpoints”: {
“1”: {
“clusters”: {
“groups”: {},
“scenes”: {},
“basic”: {}
},
“bindings”: {
“ota”: {},
“time”: {}
}
},
“242”: {
“clusters”: {},
“bindings”: {}
}
}
}
Good to see your devices are in ![]()
It will be easier and quicker to fix the error’s of those devices ![]()
Good luck with fixing ![]()
Best regards Peter.
Hi Dylan, Tried Ver.4.7.2 same issue that they are only added as Universal ZigBee device.
Goodnight and sleep
well.
Best regards Peter.
v4.9.5 and same result for my devices. Doesn’t matter what I choose for the button it always gets added as a 1 gang switch (which it isn’t) and has all of these extra flow cards that are irrelevant for the device (and the readouts for battery don’t work).
41afb781-6af5-4f9d-9724-5dc239d27df5
Hi Dylan good morning
I’ve installed Ver. 4.9.5 of the App and SOS Button is recognized now but not triggering and no battery reading. Multisensor still not recognized only Universal again.
Diagnostic code: a623c419-9f7b-4123-9264-c68996a4e63f
Have a nice day and good luck ![]()
BR Peter.
Hi Dylan Good evening, I’ve been trying every new version today upto now Ver 4.9.19 but Multisensor still not recognized as sensor, still universal ZigBee device and SOS is recognized but not triggering and no battery reading.
I don’t know what’s happening now, are you testing yourself because of all the new version’s and if so, are you letting us know when you’re making progress and devices are all working.
Thanks very very much for all your effort.
Good night and best regards Peter.









