Skip to content
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

Open
wilflet1986 opened this issue Jul 5, 2021 · 6 comments
Open

supported decives- T8222 #80

wilflet1986 opened this issue Jul 5, 2021 · 6 comments

Comments

@wilflet1986
Copy link

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?

@racingsnake91
Copy link

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)

MaxWinterstein added a commit to MaxWinterstein/eufy-ha-mqtt-bridge that referenced this issue Jul 6, 2021
@MaxWinterstein
Copy link
Contributor

The -Z thing was seen multiple times before. There are other Cameras that also have some -Z twin.

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?

@wilflet1986
Copy link
Author

The -Z thing was seen multiple times before. There are other Cameras that also have some -Z twin.

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

@matijse
Copy link
Owner

matijse commented Jul 7, 2021

I've created a release with support for T8222-Z, that Max added support for. It's building now...

@MaxWinterstein
Copy link
Contributor

@wilflet1986 ready to test for you :)

@wilflet1986
Copy link
Author

Sorry for not replying sooner I've been out of the house for a few days.
I did manage to pull the new image before leaving- everything seems to be working fine for a few days now and the error no longer appears in the log.
Thanks guys

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants