-
Notifications
You must be signed in to change notification settings - Fork 728
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Device Support Request] ZY-M100 #2378
Comments
relates to Koenkk/zigbee2mqtt#17483 |
Details
{
"home_assistant": {
"installation_type": "Home Assistant Container",
"version": "2023.5.2",
"dev": false,
"hassio": false,
"virtualenv": false,
"python_version": "3.10.11",
"docker": true,
"arch": "aarch64",
"timezone": "Europe/Berlin",
"os_name": "Linux",
"os_version": "6.1.21-v8+",
"run_as_root": true
},
"custom_components": {
"zha_toolkit": {
"version": "v0.8.39",
"requirements": [
"packaging>=20.8",
"pytz"
]
},
"xiaomi_miio_fan": {
"version": "2022.8.0.0",
"requirements": [
"construct==2.10.56",
"python-miio>=0.5.12"
]
},
"localtuya": {
"version": "5.0.0",
"requirements": []
},
"avanza_stock": {
"version": "1.2.0",
"requirements": [
"pyavanza==0.6.0"
]
},
"xiaomi_miot": {
"version": "0.7.8",
"requirements": [
"construct==2.10.56",
"python-miio>=0.5.6",
"micloud>=0.3"
]
},
"hacs": {
"version": "1.32.1",
"requirements": [
"aiogithubapi>=22.10.1"
]
},
"auto_backup": {
"version": "1.3.2",
"requirements": []
}
},
"integration_manifest": {
"domain": "zha",
"name": "Zigbee Home Automation",
"after_dependencies": [
"onboarding",
"usb"
],
"codeowners": [
"@dmulcahey",
"@adminiuga",
"@puddly"
],
"config_flow": true,
"dependencies": [
"file_upload"
],
"documentation": "https://www.home-assistant.io/integrations/zha",
"iot_class": "local_polling",
"loggers": [
"aiosqlite",
"bellows",
"crccheck",
"pure_pcapy3",
"zhaquirks",
"zigpy",
"zigpy_deconz",
"zigpy_xbee",
"zigpy_zigate",
"zigpy_znp"
],
"requirements": [
"bellows==0.35.2",
"pyserial==3.5",
"pyserial-asyncio==0.6",
"zha-quirks==0.0.99",
"zigpy-deconz==0.21.0",
"zigpy==0.55.0",
"zigpy-xbee==0.18.0",
"zigpy-zigate==0.11.0",
"zigpy-znp==0.11.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"
]
}
],
"zeroconf": [
{
"type": "_esphomelib._tcp.local.",
"name": "tube*"
},
{
"type": "_zigate-zigbee-gateway._tcp.local.",
"name": "*zigate*"
},
{
"type": "_zigstar_gw._tcp.local.",
"name": "*zigstar*"
},
{
"type": "_slzb-06._tcp.local.",
"name": "slzb-06*"
}
],
"is_built_in": true
},
"data": {
"ieee": "**REDACTED**",
"nwk": 37381,
"manufacturer": "_TZE204_sxm7l9xa",
"model": "TS0601",
"name": "_TZE204_sxm7l9xa TS0601",
"quirk_applied": false,
"quirk_class": "zigpy.device.Device",
"manufacturer_code": 4417,
"power_source": "Mains",
"lqi": 255,
"rssi": -31,
"last_seen": "2023-05-10T16:50:41",
"available": true,
"device_type": "Router",
"signature": {
"node_descriptor": "NodeDescriptor(logical_type=<LogicalType.Router: 1>, complex_descriptor_available=0, user_descriptor_available=0, reserved=0, aps_flags=0, frequency_band=<FrequencyBand.Freq2400MHz: 8>, mac_capability_flags=<MACCapabilityFlags.AllocateAddress|RxOnWhenIdle|MainsPowered|FullFunctionDevice: 142>, manufacturer_code=4417, maximum_buffer_size=66, maximum_incoming_transfer_size=66, server_mask=10752, maximum_outgoing_transfer_size=66, descriptor_capability_field=<DescriptorCapability.NONE: 0>, *allocate_address=True, *is_alternate_pan_coordinator=False, *is_coordinator=False, *is_end_device=False, *is_full_function_device=True, *is_mains_powered=True, *is_receiver_on_when_idle=True, *is_router=True, *is_security_capable=False)",
"endpoints": {
"1": {
"profile_id": "0x0104",
"device_type": "0x0051",
"input_clusters": [
"0x0000",
"0x0004",
"0x0005",
"0xef00"
],
"output_clusters": [
"0x000a",
"0x0019"
]
},
"242": {
"profile_id": "0xa1e0",
"device_type": "0x0061",
"input_clusters": [],
"output_clusters": [
"0x0021"
]
}
},
"manufacturer": "_TZE204_sxm7l9xa",
"model": "TS0601"
},
"active_coordinator": false,
"entities": [],
"neighbors": [],
"routes": [],
"endpoint_names": [
{
"name": "SMART_PLUG"
},
{
"name": "unknown 97 device_type of 0xa1e0 profile id"
}
],
"user_given_name": null,
"device_reg_id": "adde545ae3ac7c4a6087c835d1180281",
"area_id": null,
"cluster_details": {
"1": {
"device_type": {
"name": "SMART_PLUG",
"id": 81
},
"profile_id": 260,
"in_clusters": {
"0x0004": {
"endpoint_attribute": "groups",
"attributes": {},
"unsupported_attributes": {}
},
"0x0005": {
"endpoint_attribute": "scenes",
"attributes": {},
"unsupported_attributes": {}
},
"0xef00": {
"endpoint_attribute": null,
"attributes": {},
"unsupported_attributes": {}
},
"0x0000": {
"endpoint_attribute": "basic",
"attributes": {
"0x0004": {
"attribute_name": "manufacturer",
"value": "_TZE204_sxm7l9xa"
},
"0x0005": {
"attribute_name": "model",
"value": "TS0601"
}
},
"unsupported_attributes": {}
}
},
"out_clusters": {
"0x0019": {
"endpoint_attribute": "ota",
"attributes": {},
"unsupported_attributes": {}
},
"0x000a": {
"endpoint_attribute": "time",
"attributes": {},
"unsupported_attributes": {}
}
}
},
"242": {
"device_type": {
"name": "unknown",
"id": 97
},
"profile_id": 41440,
"in_clusters": {},
"out_clusters": {
"0x0021": {
"endpoint_attribute": "green_power",
"attributes": {},
"unsupported_attributes": {}
}
}
}
}
}
}
Nwk: -- the device looks like the same as
duplicated the |
Thanks for the hint! 👍
|
Hello, I just had the same issues with zigbee2mqtt: The _TZE204_ztc6ggyl has different "datapoints" then the _TZE204_sxm7l9xa so it is not done with just adding the manufacture id. Never worked with quirks but will try to check if possible |
Here is the description for the datapoints: 104 - Lux |
I tried to modify this file but the code is not working. The sensor doesn't use the quirk! Mhh! Where is there error? |
Did you just added the manufacturer Id? _TZE204_sxm7l9xa I think we have to do a new matching for the datapoints in the new quirk |
No, I tried to match the data points according to your table above -> #2378 (comment) |
Never used a quirk before, this is also new to me. |
I can confirm the behavior. The Quirk does not seem to be used: The following message appears in the logger:
|
I also tried several quirks and stuff but the device doesn’t use them |
Really not sure which of the many threads about this device to post on, but I've managed to get the ZHA quirk working for me with the basic occupancy sensor and illuminance using this quirk that I put together from various others floating around:- Its based on the _TZE204_sxm7l9xa variant. Its basically Wolf's altered quirk above but I've changed the device signature to work with the _TZE204_sxm7l9xa variant. If anyone can extend it to expose the configuration options that would be amazing. |
For whatever it's worth, the quirk you've provided didn't work with my _TZE204_sxm7l9xa. Similar result as above with the other quirk(s), my device just doesn't use the quirk. In case it's relevant, I do also have a _TZE204_ztc6ggyl which I'm using with the other quirk that provides all of the configuration options. That one uses its quirk, and seems to work fine. |
Same for me the quirk is not used |
Can you post the device signature for the _TZE204_ztc6ggyl and your _TZE204_sxm7l9xa and I'll try to see why it's not picking up. |
Is this everyhting you need?
Edit: I dont know why it is not formatted |
Go to the device in zha click the the dots next to the reconfigure button. Then choose manage zigbee device then click signature and paste those for both your devices. I have the _TZE204_sxm7l9xa working again. I must have broken something in the file I posted. I will upload in about an hour or so. I am away from my pc atm. |
Can you also post the sig for _TZE204_ztc6ggyl |
Here. This device works and also exposes the config values to the fronted
|
Could you unload your working quirk on _TZE204_ztc6ggyl then reload HA and show me what the sig looks like without the quirk loaded. Then you can put it back again. |
I'll post my working basic quirk for _TZE204_sxm7l9xa in about 45 minutes when I am back. |
This is the signature without the quirk. But without the quirk it does not exposed the config to HA |
Thats fine, i just wanted to compare both against _TZE204_sxm7l9xa, as I'm no quirk expert. Here is the correct quirk that gives at least some functionality. I've also corrected the original link above. I'll see if i can figure out how to expose the config entries. |
Great. Looks good. The occupancy sensor is now exposed. Thank you
This is the quirk which exposes the config |
Ok, through a fair bit of trial and error, I think I have a working quirk with config options. I think you might need that sensor working for the min and max range config options to work (I'm guessing). |
For me looks good. I am not sure if the value are used but I can configure it |
If you could test the settings, let me know if they seem to be effective. |
I tried this quirk.... I can see all options, the illuminance sensor works, but the Occupancy sensor is not working.... Edit: After 5 minutes it starts to work.... I'll test if it's working right. |
Huh strange. I can't get it to work at all, even after many HA restarts, removing and re-pairing the device, and even deleting pycache. |
Is there any chance there is something in the room keeping the detection on ? |
I don't think so, since I can't even get it to trigger on. It always thinks the room is empty. |
Thats really strange. All i can say is that that happened to me originally, until I changed the fading time to zero. Since then its worked:- Interestingly, fading time seems to no longer be a supported config option in this quirk, HA has now greyed it out. (Its still in the cluster values). Are you changing the fading time in endpoint 5, or endpoint 1 ? I've done it in both just to be sure:- and |
I modified existing quirk with zigbee2mqtt converters datapoints and result seems to work well. ts0601_TZE204_ijxvkhd0_presence.zip Please try it and tell your results. I need to reset device (hold button some seconds) unpair and pair again and, at least for me, all is working ok. I have it working perfectly in a small bathroom, with only 5 seconds of fading time. Max range value are in cm, and seems only acceptable resolution are 1mt Motion and presence sensitivity acceptable values are 1..9, but device returns multiplied by 10. I need to put a lambda function converter only for returned values. I didn't have time to test different values, but, at least, values are stored correctly. |
Looks good. Illuminance sensor didn't initially show up, and an HA restart and it appeared. This happens on the other tuya mmwave sensors too for some reason... Good job! Fading time now definitely works. Will test out the sensitivity and see. |
Thank you both for your help. @rofo69, I didn't realize there was a second fading_time in Endpoint 1. I tried changing that one too, but no luck. Next, I deleted my current quirk and uploaded the one @fracarvic shared. To be safe, I also made sure to remove the sensor from HA, deleted pycache, and restarted HA. After re-pairing, the device is picked up and I see @fracarvic's changes... but occupancy still always says "Clear." I've tried various settings to no avail, including matching the screenshot above as well as setting the sensitivity and max_range to the maximum. Nothing seems to work. I'm stumped. For what it's worth, I recently purchased a Tuya hub just to make sure the device isn't defective. The device seems to work perfectly in the Tuya app. So I just need to figure out why I can't get it to work with Home Assistant. |
Just a warning to others. |
My _TZE204_ijxvkhd0 keeps working prefectly more than a week. @MasterDevwi , testing other quirks my device stops working and always report clear occupancy. Maybe other quirks send incorrect values, and seems that unpair and repair doesn't reset device config values. My solution was unpair, hold reset button of device a couple of seconds, and pair again. Maybe this can help you. @rofo69 , I enable zha debug and our device sends always, every second, target distance. If theres nobody on the room, always report 0 as target distance, always, every second. I only have 4 zigbee devices and this didn't cause problems for me, but people that have a lot of devices maybe are affected by this traffic. Anyway, I order a ceiling version of _TZE204_clrdrnya device for testing, as @evgenln says it's a better device. |
Even just a couple of days since deactivating the device i can see a noticeable improvement in stability on my zigbee network, which has around 60 devices on it. I think I might put his in the 'spares' drawer for now, and use something else like an EP1 or EPLite. I might also remove my other older ZY-M100 as it also spams the zigbee network.. approximately every 1.5 seconds. |
It is regrettable that the behavior of these devices is not corrected, as they are great value for money and work very well for what they propose. I have a little more than 70 ZigBee devices, including 4 ZY-M100 presence sensors. I didn't understand why my network became completely unstable and even compromised the zigbee2mqtt service by activating the watchdog whenever I tried to add more than 70 devices. I updated firmware, changed dongle, same problem. Having more than one dongle, I decided to migrate to zha, but as these devices and two others are not or were not compatible, I kept Z2MQTT just for them. My surprise, more than 70 working perfectly on both networks. This only confirms the warning of network overload by mmwave tuya. I don't intend to stop using them, even if I have to maintain both networks. The best option would be a firmware update via Tuya for these presence sensors. |
@andregoncalvespires - Exactly my thoughts. They seem to work well enough in isolation, but these network issues are a deal breaker for me, unless I move them to their own network as you have done. In the end, I've gone down the everything presence route. These are EspHome/WIFI based, but more importantly, only broadcast when a state changes. I found that even with just 2 tuya mmwave sensors, it was getting harder and harder to pair devices to the network, and random devices would randomly drop off the network or fail to respond correctly. |
@fracarvic, I have the model TZE204_e5m9c5hl and with your file it works correctly, I just had to rename the file and modify the line 211 where the model is declared. |
Same here. I installed two TZE204_e5m9c5hl yesterday and did the same. Works fine. |
Thank you @fracarvic. Your quirk worked perfect with my _TZE204_ijxvkhd0. |
I just found this issue, thanks god... It seems to work, but the occupancy always on Detected state. Are you also getting stuck to Detected? Also, I dont know how to set the value correctly, there is a good combination that you use? |
try to set defaults sensitivity |
I am having the same issue with the Device Handler being stuck on "Detected" for Occupancy. My device is TS0601 |
I have set fade time 2sec and Occupancy works with a few second delay |
Finally using the latest quirk of fixtse It works. |
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. |
Oh well, there we go. Another perfectly fine issue getting shut down because of an aggressive bot while maintainers didn't have the time to go through it. |
I have a TZE204_qasjif9e and tried several quirks now but I don't get any controls for that sensor |
Looks like _TZE204_ijxvkhd0 is also available here. Can a quirk be created from it like _TZE204_sxm7l9xa, _TZE204_e5m9c5hl? |
Problem description
It apears in HA, but without any sensor.
Solution description
Any
Screenshots/Video
Screenshots/Video
[Paste/upload your media here]
Device signature
Device signature
Diagnostic information
Diagnostic information
Logs
Logs
Custom quirk
Custom quirk
Additional information
No response
The text was updated successfully, but these errors were encountered: