Open KyGuy2002 opened 2 months ago
Does the video doorbell return something weird when we pull its status? Maybe the API is lying about its availability or the prop doesn't exist for some reason.
Using
await camService.update(cam)
print(cam.available)
on wyzeapy returns True, but in HA the switch entity is "Unavailable"
After digging deeper, it looks like the VDBP device is never getting updated.
In the HA logs it never logs the "Updating Device" for that camera.
After digging deeper, it looks like the VDBP device is never getting updated.
In the HA logs it never logs the "Updating Device" for that camera.
I wonder why that would be, it’s just added as a camera right? I don’t have one of those to play around with.
Does this also fix the Wyze notifications toggle switch? I used to be able to use it to turn on notifications in the Wyze app and turn them back off again. The switch is still available in Home Assistant but it doesn’t matter what I do. It does not change the Wyze app bell whether it has a line through it or not. Thanks for all your help on all this.
It does not fix the notification switch.
Thanks for your quick reply. Is there anyway to fix the notification switch or is that something you’re working on?
We are looking into that but currently stuck, so not sure when or if that will work.
On Fri, Jul 26, 2024 at 2:04 PM mikefrantz @.***> wrote:
Thanks for your quick reply. Is there anyway to fix the notification switch or is that something you’re working on?
— Reply to this email directly, view it on GitHub https://github.com/SecKatie/wyzeapy/pull/91#issuecomment-2253314187, or unsubscribe https://github.com/notifications/unsubscribe-auth/ASCYKZKROJRS5CGYQGIBQ6LZOKMTXAVCNFSM6AAAAABJLMOAACVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDENJTGMYTIMJYG4 . You are receiving this because you authored the thread.Message ID: @.***>
My assumption is they’ve changed the app at the beginning of this year so now in order to turn it off, you have an option. That may be why we are having issues with it. See screenshot below.
Yes. I was able to find the api endpoints and what data to send, but it seems to use a different authentication scheme than the others, so that’s where I’m stuck.
On Mon, Jul 29, 2024 at 9:17 AM mikefrantz @.***> wrote:
My assumption is they’ve changed the app at the beginning of this year so now in order to turn it off, you have an option. That may be why we are having issues with it. See screenshot below. IMG_1738.png (view on web) https://github.com/user-attachments/assets/bd2b2505-9523-482f-8a61-f08c894b4a3c
— Reply to this email directly, view it on GitHub https://github.com/SecKatie/wyzeapy/pull/91#issuecomment-2256217962, or unsubscribe https://github.com/notifications/unsubscribe-auth/ASCYKZNKJ7JCRI5Y7OTO7ELZOZMITAVCNFSM6AAAAABJLMOAACVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDENJWGIYTOOJWGI . You are receiving this because you authored the thread.Message ID: @.***>
I tested and fixed many of the control entities in this integration. I also added some that were unavailable and removed some that are not applicable to the device they are on.
Note: These changes were made to facilitate changes made to the ha-wyzeapi integration. PR: https://github.com/SecKatie/ha-wyzeapi/pull/607
Note: I squashed all my commits into one. This is the first major HA contribution I made so I wanted to clean up all the commits where I was troubleshooting the HACS integration installation stuff.
Changes
Not Working (Proprietary/Tutk Communication Protocol)
Could Not Get Working/Needs Testing