-
Notifications
You must be signed in to change notification settings - Fork 25
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
supported decives- T8222 #80
Comments
Just came here to add the same issue - I have two of these doorbells, first one added fine but the second one I set up for someone else shows the exact same error here and reports as a T8222-Z rather than T8222. Both identical from Amazon ordered a month or so apart. The newer doorbell also seems to run more recent firmware than my older one (which claims to be up to date) |
The I don't have access to any of these, so I just copy and adjusted another PullRequest that solved such thing. Are you able to check this, by e.g. checking out my branch and build a docker file yourself? |
Thanks Max- I'm not the most docker savy person (I let portainer handle everything) so I'm not really sure how I'd go about doing that |
I've created a release with support for T8222-Z, that Max added support for. It's building now... |
@wilflet1986 ready to test for you :) |
Sorry for not replying sooner I've been out of the house for a few days. |
In my log I get
""message":"Stored device: Doorbell (T8222*********- type: T8222-Z)","level":"info","timestamp":"2021-07-05T13:27:32.751Z"}
{"message":"DEVICE Doorbell NOT SUPPORTED! See: https://github.com/matijse/eufy-ha-mqtt-bridge/issues/7","level":"warn","timestamp":"2021-07-05T13:27:32.753Z"}"
When I follow the link to the supported devices t8222 is down as supported. Should my bell me working?
The text was updated successfully, but these errors were encountered: