Continuing the discussion from [APP][Pro] Universal TUYA Zigbee Device App - test:
Hi Kadir,
I have this exact device (_TZ3218_t9ynfz4x, Moes/Linptech ZSS-LP-HP02-MS / TS0225) working reliably in my own Homey app, including saving sensitivity/keep-time/LED/distance parameters.
Likely cause of the save error: this radar doesn’t use the standard EF00 DP protocol — its parameters live on a manufacturer-specific 0xE002 cluster instead. If the settings-save path assumes EF00-style datapoints (or a generic ZCL attribute write), the device will reject it.
Feel free to reuse the relevant driver files from my repo: GitHub - gpmachado/com.gpm.homesuite: Homey app for Zigbee/Tuya devices — switches, sensors, plugs and more · GitHub — the driver folder for the TS0225 radar (driver.compose.json + device.js) plus lib/ManuSpecificTuya3Cluster.js (the 0xE002 cluster definition) and lib/clusterRegistry.js (where custom clusters get registered). If you port it into another app, keep the capabilities and flow card definitions as declared under .homeycompose so pairing/settings behave the same way.
One more thing worth knowing: this radar is very chatty by firmware design and rejects configureReporting (UNSUP_CLUSTER_COMMAND) — so you can’t throttle its report rate from the app side. That’s expected, not a bug.
Please ask in the app topic:
Please give here the device diag logs and interviews or all yours devices and the app
Wow... It worked... Thank you so much!
@SergeP: The above discussion regards a MOES Zigbee device. Not sure whether you want to add support to your dedicated MOES app?
Hi SunBeech,
Ok, I must buy one ZSS-LP-HP02-MS unit before and then I’ll give a try.
It’s already ordered…
Regards,
SoPhos
@Gabriel_Pedrosa_Mach: See the above post for your info.
Hi SergeP,
Since I already have working drivers for a few MOES devices in my repo (GPL v3 — GitHub - gpmachado/com.gpm.homesuite: Homey app for Zigbee/Tuya devices — switches, sensors, plugs and more · GitHub), happy to point you at whichever’s useful once your ZSS-LP-HP02-MS arrives. A quick rundown beyond the radar:
Dimmer (3-gang) — includes a debouncing feature for rapid speed changes (enableDebouncing checkbox + debounceDelay in ms, under Advanced Settings, on by default but fully optional). I originally added it for driving a fan motor, but it’s a generic setting — works for regular dimming too, just turn it off or tune the delay if you don’t need it.
Remote (4-button) — flow-card based, straightforward if your device’s clusters match.
Availability tracking — the dimmer has rejoin detection (power-loss/restore) built in via a shared availability manager with passive frame monitoring and per-device timeout tuning; the radar has basic availability tracking too, just without the rejoin trigger specifically. The remote doesn’t track availability at all — it’s battery-powered and sleepy, only wakes on button press, so continuous availability doesn’t really apply there.
Since the code is GPL v3, keep in mind that’s copyleft — any derivative you publish needs to stay GPL-compatible with source available, not just “free to copy.”
