Thank you very much for sharing all these details and for the work you’ve already done on your own drivers. This is really helpful for us.
If possible, could you also share the driver files, fingerprints, and DP mappings you are currently using? This would help our engineers reproduce and verify your implementation more quickly.
i think link from github will be fine.
thanks you , i will forward to our team.
Could you tell me which Zemismart switch models each of these corresponds to? For example, the 606 series, 808 series, ZMS-206, etc.
thanks in advance.
hanks for forwarding it! The switches I’ve been testing correspond to the TB25 series — TB25-1, TB25-2, TB25-3, TB25-4 and TB25-6 (1 to 6 gang), plus a 4-gang ZCL variant and a touch model. The touch model actually uses the exact same driver code as the others — I only split it into a separate driver because of its icon/artwork file, not because of any functional difference. That said, the code isn’t tied to exact model numbers — any device sharing the same clusters and functions should work with it as-is.
To be clear about scope, my driver goes well beyond basic on/off:
One thing I deliberately left out: countdown/timer. On Homey that’s easily done with flows instead, so I didn’t see a need to bake it into the driver itself.
One honest caveat: the SVG icons/artwork were done pretty roughly on my end — there’s definitely room for improvement there if anyone wants to help polish the graphics.
Hi Dylan Good afternoon, is the app using to much memory, because Flow’s don’t run and device’s are difficult to start I noticed since yesterday.
Diagnostic code e181bc15-ebb8-4a6f-a08a-b00b5fe71552
Also non of the devices still not function normal in your app. SOS, Smartbutton, Waterdetector and Door/Window sensors.
Diagnostic code 4577486f-4233-4106-9dcf-dc1fe4dc43ab
Good luck and thanks again for your effort, Peter.
Hi Dylan Good afternoon you achieved it the SOS buttons finally work again, great job 
Before I had to disable the app last night because Flow’s didn’t run and I also couldn’t switch off devices manually in Homey, this morning I updated the app to version 9.0.596 and deleted the SOS, Waterleak sensor and Smartbutton, restarted Homey and re-add the device’s and SOS working again and others not.
Diagnostic code 1cf775a2-be97-4b3c-88c4-c29c83bf11d4
Thanks and have a nice day, good luck Peter
for the 4 gang ZCL, you mean the module :ZMS-206 ? the one with screen
thanks for your reply!
The 4gang zcl device is a device sold in Brazil with the new digital brand. It is a 4-key touch device. In my repository there is his interview. com.gpm.homesuite/Homey_Interview/4G touch/_TZ3000_lwthnp7j.txt at main · gpmachado/com.gpm.homesuite · GitHub
It has the list of clusters, my app has already mapped the functions, provides a time cluster server, apparently the ZCL (novadigital 1,2,3 and novadigital 4gang touch) has a shared lib and only changes the settings for the number of gangs. The same with the novadigital 4 and 6 gang (Tuya Ef00).
That one returns a 404. I think you mean https://github.com/gpmachado/com.gpm.homesuite/tree/main/Homey_Interview?
Hey! Thanks for all the great work. I’m having issues with the TS0044 + _TZ3000_zgyzgdua 4-way switch. Similair to what I read above I doesn’t work with it’s physical buttons (in-app everything works). I got below error regarding the driver. However, it doesn’t matter which device type I select during pairing, I always get this notification.
(Homey Pro 2019 / MOES 4-way switch)
Hi Dylan Good evening, SOS button’s still working fine, only Battery is very Nervous/Glitchy
Contact sensors are not switching open/close but only acting as puls contact, also Luminance is not correct 1st picture is this contact Lum and 2nd picture is as it should be from another type contact/Luminance sensor.
Waterdetector and Smartbutton still not working.
Diagnostic code 0cea6870-69dd-4a98-abdd-e35273699e7d
Good luck and thanks again for your effort Peter.
Hi, I need support for a Tuya Zigbee DIN rail energy meter.
Device:
Homey Developer Tools successfully interviews the device and identifies it correctly as TS0601 / _TZE284_6ocnqlhn.
However, Universal Tuya does not recognize it when trying to pair it with the DIN Rail Energy Meter driver. During pairing it repeatedly detects another device called “Smart RCBO” instead of this energy meter.
Diagnostic report code:
3a1f196d-77e6-44f6-870e-d03d6a28da97
Could you please check the diagnostic report and let me know if this fingerprint can be added to the DIN Rail Energy Meter driver?
Thanks!
You really need to read the first post of the thread.
Hi Dylan Good morning 
and good News the Door/Window sensors are fine now, open close is working as on off now and Luminance seems also okay.
Waterdetector is sending puls now when it’s in the water so great work
Only Smartbutton to fix now because that’s still not receiving data.
Diagnostic code f647d35b-c401-4077-b758-da1356e523f9
Have a very nice day and thanks for fixing so far.
Best regards Peter.
Don’t worry I will check soon . I have also found a new work and will might start in September
Hi Dylan that’s good to hear, congratulations 
Could you re give me all the PID m+mfs name that not fully working on your homey box.
Best regards
Hi Dylan is this message for me or someone else.
Regards Peter.
First of all, thank you for your great work with the app.
I have the latest trial version. Thanks to these, the Moes presence detector was able to connect ZSS-LP-HP02-MS to the manufacturer ID: _TZ3218_t9ynfz4x.
Unfortunately, there is always an error message when saving patamers, such as sensitivity, etc.
Do you have a solution for this?
I use the current Homey Pro mini and the sensor is connected to Zigbee.
Thank you in advance and many greetings from Germany.
Kadir
