Closed homeassistant348 closed 1 month ago
I just updated this morning and noticed the same. I use a lot of automations related to the state of the Sense Hub. Thankfully I was able to roll back to 0.1.24 and it is working again.
Any logs? I don’t have sense hub so I probably won’t be much help.
Attached is a log file and a couple images for Working/Broken.

On May 23, 2024, at 10:55 AM, Brian Rogers @.***> wrote:
Any logs? I don’t have sense hub so I probably won’t be much help.
— Reply to this email directly, view it on GitHub https://github.com/SecKatie/ha-wyzeapi/issues/591#issuecomment-2127739306, or unsubscribe https://github.com/notifications/unsubscribe-auth/ARWWQM7SJLWTI4MDH74AAJ3ZDYUPXAVCNFSM6AAAAABID55AXGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCMRXG4ZTSMZQGY. You are receiving this because you authored the thread.
Here are some logs from me as well. My card looks identical to @homeassistant348's.
home-assistant_wyzeapi_2024-05-23T18-08-18.592Z.log home-assistant_wyzeapi_2024-05-23T18-07-39.955Z.log
Same issue, upgraded from 1.24 to 1.26 and now the Sense hub is no longer available. This is what I see
@brg468
I see the "https://github.com/SecKatie/wyzeapy/pull/86" discussion link and based on what I am reading, you don't have the HMS setup to do formal testing.
If you need me to install and test potential fixes, please reach out. I would be glad to install updates and test the potential fixes, if needed.
@spamoni4 thanks for the offer. I don’t have the ability to test the HMS stuff, but since it worked before we changed the auth check, I assume changing back should fix it. If you want to try downloading from my branch and putting the wyzeapy folder from it in your config folder and restarting, you can test out the updated version.
@spamoni4 thanks for the offer. I don’t have the ability to test the HMS stuff, but since it worked before we changed the auth check, I assume changing back should fix it. If you want to try downloading from my branch and putting the wyzeapy folder from it in your config folder and restarting, you can test out the updated version.
Thanks, will try it this weekend and let you know
@brg468
Want to make sure I replace the appropriate items so I have a few Questions, Here is where I think I need to replace (/homeassistant/custom_components/wyzeapi), is this correct?:
I am asking because I don't see a services folder, I would assume that is new and used for references.
Is there a method which will allow me to access the folder via Windows Explorer or a Mac?
@brg468
I just did exactly what you asked and put the wyzapy in the root config folder. I then went to my dashboard and HMS seems to be working again,
Perfect! Sorry I didn’t get to you in time but yes that’s what I meant.
Perfect! Sorry I didn’t get to you in time but yes that’s what I meant.
Figured that is what was meant. So it does seem to fix the issue with HMS. Great job. Shall I delete the folder/files you wanted me to test?
One additional question, if you don't mind: Will you all be adding Leak Sensor Support? or does this fall into the same issue as with the contact and motion sensors?
You can leave the folder there until a new version of Wyze is published, then delete that folder.
I don’t know anything about how the leak sensor operates, if it’s part of the HMS platform it might be possible but without having one it’s hard to add support.
You can leave the folder there until a new version of Wyze is published, then delete that folder.
I don’t know anything about how the leak sensor operates, if it’s part of the HMS platform it might be possible but without having one it’s hard to add support.
I see, HMS Hub has the Contact, Motion, Leak, and Humidity Sensors as part of it. If I can provide anything to see about making this happen, let me know.
I also have a spare hub and some sensors. :)
This should be fixed in the latest version, 0.1.27
This should be fixed in the latest version, 0.1.27
Installing now, will let you know if it corrects the issue.
EDIT
Just installed the 0.1.27 and HMS seems to be working fine. I did remove your code in the Config file and restarted HA.
Great job and thanks for the quick fix
Describe the bug With version 1.25 and 1.26 the Wyze Sense Hub (Alarm Hub) shows as unavailable and no longer is controllable!
To Reproduce Steps to reproduce the behavior:
After update, Wyze Sense Hub shows as unavailable and is no longer controllable by HA or Apple Home.
Expected behavior Worked fine in version 1.24