Contact Sensors issues

[TheGreatSkeeve]

Hello!

I'm able to pull contact sensors from my Wyze account, I can see nicknames, macs, rssi, etc, but all of them are showing as closed when this is not the case. sensor.is_open returns False for everything.

Additionally, it looks like the wiki might be mislabeled - It's got Contact Sensors and Entry Sensors, but the only thing under Entry Sensors is Motion Sensors.

I did try client.entry_sensors.info(device_mac=mac) but that returned nothing. Interestingly without device_mac=, that statement errors out. TypeError: ContactSensorsClient.info() takes 1 positional argument but 2 were given

Thanks!

[shauntarves]

Hey @TheGreatSkeeve,

Thanks for your interest in this library. I'm doing my best to maintain it but often lack the time. So, a few things about your specific issue(s):

1. The wiki is definitely confusing. I tried to name things in a way that didn't break my brain, but wyze calls the contact sensors "entry" sensors in their app. That's the reason both of those terms are used. But I agree with you that there's a mistake in the docs and the MotionSensorClient heading is wrong. I will fix that.
2. I don't actually have any contact/entry sensors at the moment. Someone was nice enough to share theirs with my account temporarily while I developed this and I no longer have them in my account.
3. If you'd like to debug this issue further, please try the following:

wyze_sdk.set_stream_logger('wyze_sdk', level=logging.DEBUG)

for contact in client.entry_sensors.list():
    print(contact.to_dict())

If you can paste the result of that here, I'll take a look. Hopefully just a simple bug somewhere.

[TheGreatSkeeve]

So, nothing actually gets returned when I run that command - entry_sensors is empty. Is it possible the newer ones aren't classified the same way?

I can send over the output via email, it essentially looks like a full dump of my Wyze config and even if I sanitize it I'll probably miss something I don't want public. I can also share entry sensors with you if that would be helpful.

Thanks again!

[shauntarves]

Yeah definitely send them. There is usually at least an error/warning if the device has a model number that I haven’t accounted for.

…

On Sun, May 1, 2022 at 2:19 PM THC-Lab ***@***.***> wrote: So, nothing actually gets returned when I run that command - entry_sensors is empty. Is it possible the newer ones aren't classified the same way? I can send over the output via email, it essentially looks like a full dump of my Wyze config and even if I sanitize it I'll probably miss something I don't want public. I can also share entry sensors with you if that would be helpful. Thanks again! — Reply to this email directly, view it on GitHub <#71 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABEDBMHLM6645JPW6CANJWDVH3DJPANCNFSM5TXM7J6A> . You are receiving this because you commented.Message ID: ***@***.***>

[shauntarves]

Looks like that was the issue - there are new model numbers for the entry and contact sensors. I don't have any of these newer ones to try out, but feel free to check out https://github.com/shauntarves/wyze-sdk/tree/71-contact-sensors-issues and let me know if it works for you.

I'll merge it into the main code base if I don't hear from you in a few days and we can investigate more if it doesn't work.

[TheGreatSkeeve]

Hey man-

That was it - the link your sent works for me. Thanks again, sorry for the late reply, been busy.

Take care!