I have one sensor that won’t clear as closed. Tried arming the system in the app but it just spins with the arming message. Then tried to switch back to disarmed but just kept spinning. Force closed the app. Things are broken.
Update: V1 sensors are working fine when connected back to the camera bridge. Nothing works on the hub.
Unplug the power and let the battery die so you can force a reboot. See if that helps.
Battery last 10 hours…not going to do that and listen to it complain about no power.
I don’t remember who posted this but my eternal gratitude…unplug hub from power, hold reset button 30 seconds or so for a power off. Plug back in and it should reconnect.
Mine is back online and many things are working. However, there is confusion between the hub and my camera bridge as to which controls some of my V1 door sensors. I’ll see if that works its way out.
Thank you for the update here. Next time my sensors freeze up I will try this reboot technique. I was afraid holding the reset button so long would flash it or remove my dozens of sensors and cause me a ton of extra work. I am very pleased to hear it worked out okay for you. Please keep me updated on this.
Serious Question though. I am going to be moving sometime this month…is there no way to turn off the Hub while I am moving houses? Do I just have to let it complain about power for up to 10 hours until I move it and plug it back in at the new place?
Hmm…another reason why the app (which is secure) should have an option for us to tell the hub to turn off…then pressing the reset button can turn it back on. Consider these thoughts Wyze. Lots of people do change residence several times in their lifetime.
(Nevermind on my crossed out sentences, you just said if the hub is unplugged and reset button held, it powers off, then plugging back in powers it back on. So this will work.)
Well, it seems to have only worked for a short period of time. At least one sensor seems to be stuck again.
Now I feel foolish…door really was open.
Spoke too soon. Now all sensors connected to the hub are offline.
Unplugged the power and the hub immediately rebooted. Now all the sensors I moved to the bridge are back on the hub and several are stuck as open.
With this new Firmware my motion and contact sensors just stop updating. Resetting solves it for a little bit then about 12 hours later they stop responding with updates.
I am not experiencing this issue, hopefully I wont either. But I do have a question, do you still have your Bridge connected to a V2? Asking, because I decided to disconnect my Bridge after mapping everything over to the new HMS Hub.
If you do, I wonder if there is an issue similar to the Ghist rules where the Bridge still thinks the sensors are connected to it even though they are on the new hub. Maybe try disconnecting the Bridge - if you can.
No bridge is connected, just the new sense hub. All motion and contact sensors just stop responding after about 12 hours.
Unplugging and holding down the button on the back seems to be a device reset and the sensors started updating again, I’ll update if they continue to be an issue.
Can’t disconnect the bridge as I have some sensors still connected. Seems to be some sort of ghosting since the sensors still think they are connected to the hub. I may just reset the hub.
Yeah, about every 12 hours I have to reset the hub. You don’t need to unplug it to reset it, just hold the button down for about 15 seconds and it will reboot the device. Once it’s rebooted the sensors start working.
This can’t be a coincidence that so many people had perfectly reliable hubs and sensors on the hub for months, and then suddenly several of us start having reliability issues exactly after installing this update. There has to be something in this firmware somewhere. I hope the logs help.
@Stilkdog can you submit and post a log for the hub the next time it happens. The more logs they have, the more likely they can detect some pattern and resolve it.
Yeah I’m waiting for it to happen again.
Funny. Not paying too close attention, I thought it said “Tone Settings” 
I agree with you.
Maybe I am missing how it works, but I think the entry sound volume should be separated from the alarm volume. I want alarm volume max, and the entry volume low.
I have turned off the entry tone sound for now.
My sensor lock up issue has happened several more times over the weekend. As suggested, I alternated switches, and nothing else is having problems on any of the other switches I had the hub connected to, only the hub which means it can’t be the router/switch when only the hub locks up and nothing else does, even on the same connections.
I also tried leaving everything on the same switch and just rebooting the Wyze hub by holding the button for 10-15 seconds, and when it boots back up all the sensors start working with a proper connection again…but if the switch connection was bad, you’d think it would still not work. And since other devices will work on the same connection, it’s a strong indication that it is the hub having a problem.
All of my tests indicate the Hub/firmware is the problem. I LOVE the new tune settings that come with this firmware, but it isn’t worth having my hub lose connection 1-3 times per day and forcing me to reboot it to get it to work properly again. If it were possible to revert the firmware back to the previous firmware, I would do it tonight and wait for acknowledgement that this is being resolved first.
I can continue to submit more logs if necessary to help out. I very much look forward to the next firmware iteration to see things go back to being reliable like they used to be. 
I’ll probably be disconnecting most of my smart devices for a week or so while I move to a new house here. I am not worried, both because I am confident the hub is still under warranty and because I am sure Wyze will figure out this connection issue, especially since only a fraction of people are experiencing it. Lots of users have no problems at all. Absolute worst case scenario I’ll buy another hub. Sometimes it comes with the territory with beta. I knew what I was getting into. I probably won’t consider that until at least seeing what happens after the next firmware release though. Maybe even switching to WiFi after moving to my new house. See if that makes a difference in some way for me.
But again, I love the tune settings, they’re so instantaneous! WAY faster than using Alexa to make chime sounds. And I believe they work even when there is no internet, just like how the doorbell will chime even when internet is down because it connects locally. So cool, and so fast.
This release is very buggy. It has randomly gone offline on me where I cannot enter my pin at any keyboard or in the phone app. Once, when I came in the door while in Away mode, it would not take my PIN causing the Alarm to go off and contact Noonlight. All while I am desperately trying to repeatedly enter my PIN, even in the App after the alarm was blaring.
Also, when trying to arm the system for Away, very often it will report an error message that it can’t complete the mode change. That is really frustrating when I am trying to quickly leave the house to pick up my grandkids!
The door opening chime is great (although its a weird sounding “cluck sound”, but I’m sure that will change as it gets thru Beta.
Happened again, submitted my logs this time.
Has anyone actually heard from a Wyze Rep about this? Seems that this isn’t getting through to whoever is responsible for the firmware.
I wanted to also update that when my sensors stop working it’s actually the entire system. My keypad doesn’t respond and I can’t even change my devices security system status until a reboot is done.
@WyzeAndy We haven’t gotten one response from you. This update doesn’t work. My Wyze HMS entire system is messed up with this release. Can we get a hot fix or ability to revert to previous app version?
I have mixed feelings about this. On one hand I took the risk of downloading Beta software (mainly to get the door opening chime to get my wife off my back for trading in our old reliable security system), so that is on me. But I really am shocked that Wyze would release software as buggy as this to the Beta program. I have been struggling with connectivity issues all weekend. I don’t think there are many of us who could afford or have the time to buy and “play” with a system that is as problematic as this. After all, this isn’t a vacuum or lamp that if it fails to correctly “map a room” or “dim properly”, I can say “we’ll, no big deal”. This could actually be placing my family in danger since I’m expecting the alarm to go off if someone breaches my door - if it randomly fails, that could potentially be serious.
I really expected beta software to be somewhat stable enough that I can still use it effectively and I’m just getting to test/evaluate changes in the UI or an additional feature. I should not be expected to test the basic core functionality of connectivity and reliability that seems to be the issue here.
The Hub goes on and off line by itself, the backup battery sometimes doesn’t work when I unplug the power supply, entry sensors randomly do not connect with the Hub and alert when opened, and sometimes the hub is totally offline so I can’t disarm the system in the middle of an entry countdown. I am curious, is this happening to people’s HMS that are not in the beta program or are these all beta SW issues? Either case is scary.
My biggest gripe is that I have not really seen any formal “release notes” for when a new release drops. I am the head of a software development team myself and I would think they would proved us with a list of things that were changed/updated so that we could focus our testing and provide feedback on those items. But instead the Wyze Beta Program feels unprofessional and more like a poor high school science experiment instead of a methodical approach to development and release testing.
I’m not completely sure how to back out of the Hub firmware to return to a stable release. Is that possible? This needs to happen ASAP so we can reliably use our system again.