Hi Dylan thx but no changes with Ver 7.0.9
Good luck with best regards Peter.
Hi Dylan and thank you for the help!
The LCD sensor don’t work. It still appears as a Unknown Zigbee device. Do you need some more info?
Hi,
My presence sensors also stopped working with the latest version. I tried to re-add them again but now they are again found as an unknown zigbee device.
Because of that they are no longer connected to the app and so i cant create a diagnostic report.
Please let me know what i can provide to help.
Thanks for the feedback! In version 2.3.1, I made some adjustments based on your diagnostics and cross-referenced with Z2M. I noticed the confusion with the SNZB-01 and SNZB-01M drivers, so I tweaked the pairing process to make it clearer which device type to select.
If you’re still having issues, just try removing and re-pairing the devices, ensuring you choose the correct productId. This should help streamline the setup. Let me know how it goes!
Just pushed v7.0.11 to the test channel.
vpatch: New device support and stability improvements
Covers a huge range of Tuya devices at this point.
New build out — v7.0.10 on test.
v7.0.8: Fixed issues with device recognition for existing drivers., Added 3 new fingerprints to support additional devices.
Covers a huge range of Tuya devices at this point.
Hello, thank you so much for the app!
Are the wifi devices working? I cant get the
WiFi LED Strip RGBCW (Tuya Local)
To work. Whenever I try to add it, I don’t see any code to scan but just “waiting for code” which never pops up. Easy login does not work either, I haven’t tried the other methods.
Im attaching a screenshot.
Edit: using v. 7.0.11 experimental. Before I tried v. 7.0.8 experimental, same issue
Hello Dylan,
No luck with version 7.0.11 the Sensor is still an unknown zigbee device.
Greetings Ronald
So which one I have to pick for SNZB-01M. I see many '“SNZB-01M” in:
- button_wireless
- button_wireless_1
- button_wireless_4
And also, should I do something more about the github issue: SNZB-01M still detected as unknown Zigbee device · Issue #198 · dlnraja/com.tuya.zigbee · GitHub ?
Thks
Thanks for the detailed breakdown! In version 2.3.1, I made some adjustments based on your feedback and cross-referenced your diagnostics with Z2M. The SNZB-01M and TS0042 should now be more stable, and I’ve tweaked the handling for the TS1201 and TS0601 to improve compatibility.
If you’re still having issues, just remove the device and re-pair it, ensuring you select the correct driver based on the product ID. This should help clear up any lingering problems. Let me know how it goes!
My SNZB-01M is recognized by Homey 
But no buttons workings, looks like all events are silent.
v7.0.10 is up on test.
v7.0.8: Fixed issues with device recognition for existing drivers., Added 3 new fingerprints to support additional devices.
Covers a huge range of Tuya devices at this point.
Dropped v7.0.10 on the test channel just now.
v7.0.8: Fixed issues with device recognition for existing drivers., Added 3 new fingerprints to support additional devices.
Covers a huge range of Tuya devices at this point.
Using V7.0.11 still issues with all my devices. None working, error message “this.tuyaEF00manager.se ndDP is not a function”
0287ac39-a3b6-49eb-ba24-7ce7bd771045
Can you check please as this is pretty annoying.
Hi Dylan my device are all corrupted, need to stop all my flows because Luminance and Humidity is fluctuating all the time also Smart button stopped working, Contact sensor’s working in reversed order and SOS is still not working and tried to add the other one again but still Unknown ZigBee device.
Diagnostic code: af7b4f5e-7014-431f-b0d3-57bdf9ba1658
Multi sensor as it should be:
Multi sensor with unknown functions now:
Fluctuating:
Sensors and SOS trying to add:
Good luck and Best regards Peter
Hi Dylan,
Somehow, my curtain modules stopped working with version 7, error message “window covering cluster not available”
TZ3000_5iixzdo2 TS130F module
Why did you close my issue on GitHub? It’s not working
TZ3000_wzmuk9ai now works perfectly 
Many thanks for that, Dylan. Sent you a little coffee money 
The new fix doesn’t ? Works
Could you please give me the new diag log id on the GitHub comment issue , it will be reopened with a new comment .
And discribe what’s the evolution of the situation.
