Hi Dylan Good evening, I deleted the Smartbutton again and restarted Homey, re-added the Smartbutton again but still no response from it.
Diagnostic code cfbf687f-fcce-4cbe-b5ea-d7d245e6eee6
The Waterdetector sensor is fine now, no more errors that it needs another driver. 
Good luck and thanks again and have a nice evening.
Regards Peter.
Hi @dlnraja ,
Could you please check this as well? Updated diagnostic ID and interview data have been provided.
Thanks in advance!
Hi @dlnraja
I’ve noticed that if I delete the presence sensor and reconnect it, it works fine, but after a while (it seems to coincide roughly with updates), it switches to “blind mode” and goes haywire, continuously detecting presence and movement.
Do you know what might be causing this?
I’m also getting this notification on the timeline for both sensors (I have two installed in different rooms).
Thanks!
please share :
Hi VicHY — thanks for the detailed report, that helped a lot.
I found the cause on the clrdrnya mmWave radars. After an app update, some radar setting DPs (sensitivity, range, delay) were being restored as curtain/blind capabilities from stored data. That’s the “blind mode” UI, and one of those DPs was also feeding motion, which explains the stuck presence.
Delete + re-pair works until the next update because it clears that stored state temporarily.
Fix is in Test 9.0.790+: phantom caps are stripped automatically and DynCap no longer re-applies them on update. Please update, restart the app, and check both sensors. Re-pair only if they still show as blinds.
The “flooding the Zigbee network” timeline message is the app rate-limiting ~200 msg/min from the Tuya firmware — related to the stuck presence spam, and it should calm down once the sensor is healed. Let me know if it persists after 9.0.790.
Thanks a lot for the quick response and the explanations. I’ll give it a try and let you know. Regards.
Hi @dlnraja
I had version 9.0.791 installed, and it was working correctly as a mmWave PIR sensor; however, after the version updated, the sensor switched to “curtain” mode and stopped working again. If I delete and reinstall it, it works correctly. The Zigbee network saturation warning no longer appears, but the battery warning persists (even though they don’t use batteries; they are connected to 220V). Here is the report number (c5165a37-2208-47a8-baaf-7a4190c4f97a).
Thank you very much.
Hi @dlnraja,
Thanks a lot for your work on this app.
I have a tubular roller blind motor with a built-in Tuya Zigbee receiver that is not recognised. It pairs fine but always ends up as “Unknown Zigbee Device” — tried Curtain Motor Shutter, Cover Controller, Curtain Motor Wall and 2 Gang Curtain Module on v9.0.809, same result every time.
Fingerprint
_TZE284_fodv6bkrTS0601[0, 4, 5, 61184, 0, 60672][25, 10]No windowCovering cluster (258), so everything goes through the Tuya EF00 datapoints as expected.
Note: this cluster list is identical to _TZE284_libht6ua, which is also a roller blind motor and already has support — the datapoints are probably the same. Might be an easy one to add.
Device details
What I’d need exposed: open / stop / close and position in percent. Motor direction would be a nice extra.
I couldn’t find this manufacturer ID anywhere — not in this app, not in the zigbee2mqtt database. Looks like a recent batch.
Full interview output:
{
"ids": {
"modelId": "TS0601",
"manufacturerName": "_TZE284_fodv6bkr"
},
"endpoints": {
"ieeeAddress": "70:c5:9c:ff:fe:c2:14:52",
"networkAddress": 36459,
"modelId": "TS0601",
"manufacturerName": "_TZE284_fodv6bkr",
"endpointDescriptors": [
{
"status": "SUCCESS",
"nwkAddrOfInterest": 36459,
"_reserved": 24,
"endpointId": 1,
"applicationProfileId": 260,
"applicationDeviceId": 81,
"applicationDeviceVersion": 0,
"_reserved1": 1,
"inputClusters": [0, 4, 5, 61184, 0, 60672],
"outputClusters": [25, 10]
}
],
"deviceType": "enddevice",
"receiveWhenIdle": false,
"capabilities": {
"alternatePANCoordinator": false,
"deviceType": false,
"powerSourceMains": false,
"receiveWhenIdle": false,
"security": false,
"allocateAddress": true
},
"extendedEndpointDescriptors": {
"1": {
"clusters": {
"basic": {
"attributes": [
{ "id": 0, "name": "zclVersion", "value": 3 },
{ "id": 1, "name": "appVersion", "value": 67 },
{ "id": 2, "name": "stackVersion", "value": 0 },
{ "id": 3, "name": "hwVersion", "value": 1 },
{ "id": 4, "name": "manufacturerName", "value": "_TZE284_fodv6bkr" },
{ "id": 5, "name": "modelId", "value": "TS0601" },
{ "id": 6, "name": "dateCode", "value": "" },
{ "id": 7, "name": "powerSource", "value": "battery" },
{ "id": 65502, "dataTypeId": 32 },
{ "id": 65504, "dataTypeId": 72 },
{ "id": 65505, "dataTypeId": 72 },
{ "id": 65506, "dataTypeId": 32 },
{ "id": 65507, "dataTypeId": 72 },
{ "id": 65533, "name": "clusterRevision", "value": 2 },
{ "id": 65534, "name": "attributeReportingStatus", "value": "PENDING" }
],
"commandsGenerated": "UNSUP_GENERAL_COMMAND",
"commandsReceived": "UNSUP_GENERAL_COMMAND"
},
"groups": {
"attributes": [
{ "id": 0, "name": "nameSupport", "value": { "type": "Buffer", "data": [0] } },
{ "id": 65533, "name": "clusterRevision", "value": 2 }
],
"commandsGenerated": "UNSUP_GENERAL_COMMAND",
"commandsReceived": "UNSUP_GENERAL_COMMAND"
},
"scenes": {
"attributes": [
{ "id": 0, "dataTypeId": 32 },
{ "id": 1, "dataTypeId": 32 },
{ "id": 2, "dataTypeId": 33 },
{ "id": 3, "dataTypeId": 16 },
{ "id": 4, "dataTypeId": 24 },
{ "id": 65533, "name": "clusterRevision", "value": 2 }
],
"commandsGenerated": "UNSUP_GENERAL_COMMAND",
"commandsReceived": "UNSUP_GENERAL_COMMAND"
}
},
"bindings": {
"ota": { "attributes": [] },
"time": { "attributes": [] }
}
}
}
}
}
Happy to test any build and report back — the motor is installed and accessible. Let me know if you need anything else.
Thanks!
Hi Dylan, I have a MOES ZC-LS / AM43 blind motor that is not working with Universal Tuya.
Diagnostic code: 1fa26737-2acf-4255-b07d-2f7b65083da5
Manufacturer ID: _TZE200_icka1clh
Product ID: TS0601
The device pairs correctly, but opening/closing does nothing and Homey returns UNSUPPORTED_CLUSTER.
Device type: enddevice
Receive when idle: false
Could you please check the diagnostic and add/fix the driver/fingerprint for this AM43 blind motor?
Thanks!
Hi Dylan Good evening, the Smartbutton is responding now but not very consistent, connected lights are switching on and off or flickering or staying on at 1 Click and dubbele click the first and the second light are switched on or flickering, hold the button is like disco sometimes al the 3 lights are flickering and light 1 stays on, so really weird behavior.
Diagnostic code 048cff91-d453-4659-ae1c-fe94bf4bc50d
And no battery reading.
Thanks again so far and have a nice evening.
Best regards Peter.
Helo @dlnraja, can you see that?
I don’t think I’ve seen anything about that in the new versions.
Thank you very much!
Hi Dylan Good evening, after update to your latest app and reading the changelog where you wrote that you’ve changed things to the Smartbutton I’ve tried to reinstall it after Homey restart but no luck, totally no response and still no battery reading.
Diagnostic code 8afffc76-a36c-4588-9714-4e196c50aab3
Thanks so far and good luck with best regards Peter.
Hi Dylan Good morning and great job again Smartbutton is responding and switching normally now 1, 2 click’s and hold works well switching the lights on or off
Only no battery reading yet and still no History tab there.
App version 9.0.881
Diagnostic code 1e071a86-093b-4d47-8af0-ce2ff5a19680
Thanks and have a great day, best regards Peter.
