-
Notifications
You must be signed in to change notification settings - Fork 135
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 Request - [ZY-M100 Series Breathing Presence Sensor] - [ZY-M100-1] / [TZE204_ya4ft0w4] #954
Comments
The sensor works but unfortunately only two states are detected: |
Is this sensor really added to latest release? The status is still open. I'm having one of these sensors and its not working yet. Am I missing something? I am having the non-ceiling version. But it has exactly the same name; _TZE204_ya4ft0w4. I think its not necessary to make a new request? |
hello, |
i also have a few ya4ft0w4 24G ceiling sensors - they are not added to app , only generic zigbee device .. so not usable. yet 😊 |
Same device ya4ft0w4 here as well and not recognized by the app. |
See if my previous suggestion is helpful to you. You need to add a “custom
quirk.”
You can review these instructions: WAY COMPLICATED:
https://pypi.org/project/zha-quirks/
Easier but less thorough:
https://www.youtube.com/watch?v=wwqDZ90Ugb0
…On Tue, Dec 17, 2024 at 2:56 PM HenkRenting ***@***.***> wrote:
Same device ya4ft0w4 here as well and not recognized by the app.
—
Reply to this email directly, view it on GitHub
<#954 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ALF3Q3CI6MA3SDO35BVC6E32GCFX5AVCNFSM6AAAAABOJ5HTI6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKNBZGYYTCNBQHE>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
|
Hmmm, sorry… I have absolutely no idea what to do with that… 🤣 |
Prerequisites:
Device Information
ZY-M100 Series Breathing Presence Sensor
_TZE204_ya4ft0w4
Zigbee 24ghz Ceilling presence sensor
Image
Device Interview
Additional Comments:
How to interview a device
The text was updated successfully, but these errors were encountered: