-
Notifications
You must be signed in to change notification settings - Fork 784
[Device Support Request] Tuya TS0601 _TZE200_kyfqmmyl triple light switch #716
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
Comments
Hey there, i have the same problem, but with single and double switches. I also tried modifying the single switch without luck. i would also highly appreciate if there was a chance to support the tuya switches. |
My device is supported by zigbee2mqtt |
Post "zigbee device signature" from the device card and / or log from pairing the device. If you have very urgent need of support of on new device then making one PR from the instruction https://github.com/zigpy/zha-device-handlers#building-a-quirk. |
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,
I'm trying to connect a 3-gang Tuya wall switch to ZHA. It connects, but doesn't show any switches, only appears as router (which is weird as it is a no-neutral switch, it shouldn't be a router). I tried modifying singleswitch.py quirk to match manufacturer and other parameters, but without success as I'm not a programmer. I don't think ZHA sees my modified quirk, I see that pycache in Tuya folder doesn't get regenerated. I'm running HA supervised in docker container. I saw this problem a couple of times here, but didn't find a solution.
Device signature:
Thanks!
The text was updated successfully, but these errors were encountered: