supported decives- T8222
Opened this issue · 6 comments
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?
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 -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?
The
-Zthing was seen multiple times before. There are other Cameras that also have some-Ztwin.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.
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