-
Notifications
You must be signed in to change notification settings - Fork 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
[Device Support Request] TS0601 _TZE204_vawy74yh Smoke detector #3421
Comments
Managed to patch something together and I'm getting attribute values now . Anyone with deeper knowledge please comment if I'm on the right track :) Thanks! Sources used:
Using ZHA-toolkit for entities, let's see how it is going to work. |
Hello, I've just made a pull request for the smoke detector to be seen: #3447 I hope that others a little more at ease than me will know how to add the battery status... |
Sorry, but what does it mean exactly? |
The modification I've proposed allows the device to indicate whether it detects smoke or not. |
After HA restart it start to populate values correctly. It works, but I don't have much confidence in it :) |
.. and when I triggered an actual alarm on a device itself I got num8.undefined_0x00 reading value for smoke attribute. Any ideas for quirk? |
Thanks, but what exactly must I do now to get it working? |
Removed my device from HA, emptied my custom quirks folder including pycahce, full restart of HA and then tried to add the device again. It still does not seem to work. |
This will be available in the next HA release, 2025.1. |
OK, Thanks! |
Problem description
Please provide support for the device TS0601 _TZE204_vawy74yh
Solution description
Looks like it is working with Z2M - https://www.zigbee2mqtt.io/devices/ZSS-HM-SSD01.html
Screenshots/Video
Screenshots/Video
[Paste/upload your media here]
Device signature
Device signature
[Paste the device signature here]
Diagnostic information
Diagnostic information
[Paste the diagnostic information here]
Logs
Logs
Custom quirk
Custom quirk
Additional information
No response
The text was updated successfully, but these errors were encountered: