I found another identical issue already open and I added our info to it: [Device Support Request] TS0601 Cover. Zemismart (Tuya) TZE200_5zbp6j0u curtain motor · Issue #1245 · zigpy/zha-device-handlers · GitHub
Sane issue here with _TZE200_a4bpgplm. Added to Home Automation but it exposes nothing.
What is the fix within HA?
PS
I read people has reported some success with zigbee2mqtt, but I had quite hard time trying to install, it worked for a while using docker, now is broken again and I’d prefer to stay fully within HA.
Hey, I got significantly further on this manufacturer last night with some help. I added my notes to the git but you’re pretty savvy and might be able to fix the last little piece: https://github.com/zigpy/zha-device-handlers/issues/1245#issuecomment-1053624641
1 Like
Hey Sebastian
What did you do to get the _TZE200_xaabybja motors to work? I have the same device signature as you but having problems.
Can you send me the quirk file you used & let me know if any other files need to be edited to make this work? init.py?
By the way, where do I find this file to edit it?
Thanks!
The _TZE200_xaabybja motors worked out of the box for me. I didn’t change any files for it. Maybe try updating to the latest HA release?
Can confirm. I have 3 that work fine.
_TZE200_rmymn92d is still problematic tho. The custom quirk is reading state but not controlling for several of us but confirmed to be working in zigbee2MQTT so I requested a new quirk pulled from that code, yesterday.
Any updates on this one? I have a curtain rod motor TZE200_cf1sl3tj, having the same issue. Probably should try Z2M instead
Hi, i also have a 4ch wall switch which would only sho w up the device, the entities are not shown.
Not exact same device/firmware so post new issue with device feature request to zha-device-handlers:
https://github.com/zigpy/zha-device-handlers/issues
Reason is that Tuya is horrible at folowing the Zigbee specification so almost every device need a quirk:
https://www.home-assistant.io/integrations/zha#zha-exception-and-deviation-handling
If you can code a little Python then read:
https://github.com/zigpy/zha-device-handlers/blob/4956114628a2aee435776c5e286a8e97d4f3df53/README.md
Same goes for Zigbee2MQTT as it also needs converters to workaround each Tuya device deviations:
https://www.zigbee2mqtt.io/advanced/support-new-devices/01_support_new_devices.html
1 Like
Was there a solution to this?
I have a zigbee blinds motor showing as “TS0601 by _TZE200_pw7mji0l” via ZHA. No entities appearing.
You will need to add a line for ("_TZE200_pw7mji0l", "TS0601") to existing quirk if there already is another Tuya device that only has a different Zigbee device signature, if not then it needs a new quirk.
Either add a custom quirk and submit code or submit a device feature request to the respective project.
https://github.com/zigpy/zha-device-handlers/issues/new/choose
https://github.com/Koenkk/zigbee2mqtt/issues/new/choose
ZHA needs a quirk/handler for zha-quirks just as Zigbee2MQTT need a converter for zigbee-herdsman:
https://www.home-assistant.io/integrations/zha#zha-exception-and-deviation-handling
(https://github.com/zigpy/zha-device-handlers)
respectively
https://www.zigbee2mqtt.io/advanced/support-new-devices/01_support_new_devices.html
(https://github.com/Koenkk/zigbee-herdsman-converters)
The reason why is explained here:
https://www.home-assistant.io/integrations/zha#knowing-which-devices-are-supported
and
https://www.home-assistant.io/integrations/zha#zha-exception-and-deviation-handling
Both of those are custom quirks implementations that add translations for deviations from standards.
2 Likes
Hi,
I have the same issue with blinds switch.
I am running Home Assistant on a container on Raspberry Pi 4, with the Sonoff Zigbee Dongle.
The signature of the device is
{
"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": 260,
"device_type": "0x0051",
"in_clusters": [
"0x0000",
"0x0004",
"0x0005",
"0xef00"
],
"out_clusters": [
"0x000a",
"0x0019"
]
},
"242": {
"profile_id": 41440,
"device_type": "0x0061",
"in_clusters": [],
"out_clusters": [
"0x0021"
]
}
},
"manufacturer": "_TZE200_jhkttplm",
"model": "TS0601",
"class": "zigpy.device.Device"
}
Any idea how to solve it?
Hello - I have a similar situation with a temp and humidity sensor. Can we get this added to the ZHA? It is adopted but no values.
TS0601
by _TZE200_qoy0ekbd
Connected via Zigbee Coordinator
Zigbee info
IEEE: a4:c1:38:a2:9d:1a:12:50
Nwk: 0x7a78
Device Type: EndDevice
LQI: 80
RSSI: Unknown
Last Seen: 2022-09-08T09:02:10
Power Source: Battery or Unknown
Can anyone help me make a custom quirk for this? Supposed to report temp, humidity, and battery level.
{
“node_descriptor”: “NodeDescriptor(logical_type=<LogicalType.EndDevice: 2>, complex_descriptor_available=0, user_descriptor_available=0, reserved=0, aps_flags=0, frequency_band=<FrequencyBand.Freq2400MHz: 8>, mac_capability_flags=<MACCapabilityFlags.AllocateAddress: 128>, 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=True, *is_full_function_device=False, *is_mains_powered=False, *is_receiver_on_when_idle=False, *is_router=False, *is_security_capable=False)”,
“endpoints”: {
“1”: {
“profile_id”: 260,
“device_type”: “0x0302”,
“in_clusters”: [
“0x0000”,
“0x0001”,
“0x0402”,
“0x0405”
],
“out_clusters”: [
“0x000a”,
“0x0019”
]
}
},
“manufacturer”: “_TZE200_qoy0ekbd”,
“model”: “TS0601”,
“class”: “zigpy.device.Device”
}
Hi.
I have the same problem in ZHA: Tuya Smart Zigbee Dimmer model EDM-1ZBB-EU shown as Light with Device info: TS0601 by _TZE200_dfxkcots not as a Dimmer.
Is there a solution for ZHA?
The only solution is ZIGBEE2MQTT ?
Looks like it’s already been worked.
The forum IS NOT the best place for ZHA device support. Devs don’t look here.
With Tuya, best to search for the manufacturer ID ( _TZE200_dfxkcots ) at:
1 Like
ZIGBEE2MQTT seems like the best that I have seen to date. ZHA didn’t work for me so I integrated an MQTT broker, added ZIGBEE2MQTT, and haven’t had any issues since. Works well for me. Good luck!
As mentioned, for ZHA device issues start by submitting a new device support request with signature and debug logs to ZHA Device Handlers → https://github.com/zigpy/zha-device-handlers/issues
ZHA will need a quirk/handler for zha-quirks if devices do not fully follow standard Zigbee specifcations, see → https://www.home-assistant.io/integrations/zha#zha-exception-and-deviation-handling
Similar issue here.
I bought a Beca smart thermostat for gas boiler, which identifies itself as being manufactured by “_TZE200_u9bfwha0”. Works fine with Zigbee2MQTT. Detected by ZHA but no entities shown.
I can see that the signature for this device was addedd in this commit 9 days ago, so I presume the support is already on place but the code didn’t reach the public yet.
Does anyone know how much time can take a fix to propagate to a HA stable version?
Thanks.
Generally new quirks will be in the next monthly release. So most likely it will be in 2022.10 if there wasn’t anything else going on with ZHA to delay it.
Looks like If you follow the links in the commit, you’ll find a custom quirk version of the fix you can install off cycle.