Closed aquemy closed 1 year ago
It's not ideal but you might be able to use the "manage Zigbee device" -> "cluster" dialog to change the attributes on one of these clusters at the moment:
on MmwRadarManufCluster
: https://github.com/zigpy/zha-device-handlers/blob/fe65de18df765449bef8dda706f8e93227891f6d/zhaquirks/tuya/ts0601_motion.py#L121-L149
I am not certain which attribute exactly I should modify.
In fact, I have two attributes (dp_102 and dp_4) with value 600. I suspect it to be a time in ms.
However, I tried to modify it in the field "Value" using "Write attribute" but when I "Read attribute" again it is back to 600. Apologies if the question is stupid but I've never modified any attribute through this UI.
There are no stupid questions, but we can't always give the expected answers. We are working on improving the interaction through the UI, but on some devices it is still quite limited, and some manufacturers do not help us in this regard.
The steps you have taken are correct. If the device does not accept the values, it is possible that the quirk requires some more adjustment.
Some people has been working in another implementation for this devices. If you want to try, here is the implementation:
You will need to enable the local quirk in your instalation. There is a guide about enabling custom quirks:
Create a ts0601_motion.py
in your local quirk folder and put the suggested quirk in the file.
Restart HA, remove and pair you device again. Check that the device is loading the quirk and that the device signature has changed.
Also, make sure to leave the "manufacturer override code" field completely empty:
Only change the value in the upper field and then press "write attribute". You can check if it wrote successfully by checking "read attribute". But again, make sure the lower field is completely empty all the time.
As I've mentioned in issue #1645 I also can't get the new values to stay set. Hitting 'read value' shows the original/factory setting again.
I confirm that the custom quirk in #1645 works perfectly.
I am re-opening with a strange issue.
I now have _TZE200_ztc6ggyl
but also _TZE204_ztc6ggyl
. For some time the quirk specified in #1645 worked perfectly, so I adjusted the settings and forgot about the sensor that works perfectly since then,
Yesterday I added the new _TZE204_ztc6ggyl
to ZHA with the exact same quirk. I was surprised that I could not modify any setting although the entities/sliders were there. Whenever I tried to modify one of these sliders, it was reset to the original position after the sensor got triggered. I thought this was due to this particular model but I then tried to modify the setting of the other one ( _TZE200_ztc6ggyl
) and got the exact same result.
What is crazy is that I can set the Sensitivity parameters, but none of the others. I clearly see that when I modify the sensitivity, the service is called (see below), but not for any other parameter.
See the logbook: we clearly see the service number.set_value
triggered by myself, but the slider min range moved to the max did not trigger anything (and 2 sec later was reset to 0s).
My quirk for both:
The devices signatures:
There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.
Hi,
Is your feature request related to a problem? Please describe.
I have a Tuya TS0601 mmWave and light motion detector. It is paired properly and works OK out of the box. However, there is no way to control anything that the sensor is supposed to expose (see here).
I have seen that there is an issue opened for the same sensor here https://github.com/zigpy/zha-device-handlers/issues/1850 but in my case, the quirk is properly loaded:
Describe the solution you'd like Being able to access the attributes/entities in such a way:![image](https://user-images.githubusercontent.com/1913007/197584024-37a7a2f3-da13-4356-ab8e-c2ac2c2848fc.png)
Device signature
```yaml { "node_descriptor": "NodeDescriptor(logical_type=Diagnostic information
```yaml { "home_assistant": { "installation_type": "Home Assistant OS", "version": "2022.10.5", "dev": false, "hassio": true, "virtualenv": false, "python_version": "3.10.5", "docker": true, "arch": "aarch64", "timezone": "Europe/Warsaw", "os_name": "Linux", "os_version": "5.15.61-v8", "supervisor": "2022.10.0", "host_os": "Home Assistant OS 9.2", "docker_version": "20.10.17", "chassis": "embedded", "run_as_root": true }, "custom_components": { "miio_yeelink": { "version": "0.1.12", "requirements": [ "construct==2.10.56", "python-miio>=0.5.6" ] }, "hacs": { "version": "1.27.2", "requirements": [ "aiogithubapi>=22.2.4" ] }, "danfoss_ally": { "version": "v1.0.7", "requirements": [ "pydanfossally==0.0.26" ] }, "bodymiscale": { "version": "3.0.3", "requirements": [ "cachetools==5.1.0" ] }, "ble_monitor": { "version": "4.6.2", "requirements": [ "pycryptodomex>=3.10.1", "janus>=0.6.1", "aioblescan>=0.2.8" ] }, "localtuya": { "version": "4.1.0", "requirements": [] } }, "integration_manifest": { "domain": "zha", "name": "Zigbee Home Automation", "config_flow": true, "documentation": "https://www.home-assistant.io/integrations/zha", "requirements": [ "bellows==0.34.2", "pyserial==3.5", "pyserial-asyncio==0.6", "zha-quirks==0.0.83", "zigpy-deconz==0.19.0", "zigpy==0.51.3", "zigpy-xbee==0.16.2", "zigpy-zigate==0.10.2", "zigpy-znp==0.9.1" ], "usb": [ { "vid": "10C4", "pid": "EA60", "description": "*2652*", "known_devices": [ "slae.sh cc2652rb stick" ] }, { "vid": "1A86", "pid": "55D4", "description": "*sonoff*plus*", "known_devices": [ "sonoff zigbee dongle plus v2" ] }, { "vid": "10C4", "pid": "EA60", "description": "*sonoff*plus*", "known_devices": [ "sonoff zigbee dongle plus" ] }, { "vid": "10C4", "pid": "EA60", "description": "*tubeszb*", "known_devices": [ "TubesZB Coordinator" ] }, { "vid": "1A86", "pid": "7523", "description": "*tubeszb*", "known_devices": [ "TubesZB Coordinator" ] }, { "vid": "1A86", "pid": "7523", "description": "*zigstar*", "known_devices": [ "ZigStar Coordinators" ] }, { "vid": "1CF1", "pid": "0030", "description": "*conbee*", "known_devices": [ "Conbee II" ] }, { "vid": "10C4", "pid": "8A2A", "description": "*zigbee*", "known_devices": [ "Nortek HUSBZB-1" ] }, { "vid": "0403", "pid": "6015", "description": "*zigate*", "known_devices": [ "ZiGate+" ] }, { "vid": "10C4", "pid": "EA60", "description": "*zigate*", "known_devices": [ "ZiGate" ] }, { "vid": "10C4", "pid": "8B34", "description": "*bv 2010/10*", "known_devices": [ "Bitron Video AV2010/10" ] } ], "codeowners": [ "@dmulcahey", "@adminiuga", "@puddly" ], "zeroconf": [ { "type": "_esphomelib._tcp.local.", "name": "tube*" }, { "type": "_zigate-zigbee-gateway._tcp.local.", "name": "*zigate*" }, { "type": "_zigstar_gw._tcp.local.", "name": "*zigstar*" } ], "dependencies": [ "file_upload" ], "after_dependencies": [ "onboarding", "usb", "zeroconf" ], "iot_class": "local_polling", "loggers": [ "aiosqlite", "bellows", "crccheck", "pure_pcapy3", "zhaquirks", "zigpy", "zigpy_deconz", "zigpy_xbee", "zigpy_zigate", "zigpy_znp" ], "is_built_in": true }, "data": { "ieee": "**REDACTED**", "nwk": 27220, "manufacturer": "_TZE200_ztc6ggyl", "model": "TS0601", "name": "_TZE200_ztc6ggyl TS0601", "quirk_applied": true, "quirk_class": "zhaquirks.tuya.ts0601_motion.MmwRadarMotion", "manufacturer_code": 4098, "power_source": "Mains", "lqi": 255, "rssi": -65, "last_seen": "2022-10-24T19:02:24", "available": true, "device_type": "Router", "signature": { "node_descriptor": "NodeDescriptor(logical_type=Additional context
It looks like the actual quirk is missing these features.
I've never touched quirk and Zigbee dev but I'd be happy to participate if anyone can guide me.