I have found the Beta firmware releases for most products to be fairly stable.
The main ones I am careful with are the hub firmware (which seems to more frequently have severe issues), since I only have one hub and it is fairly important and central to all my automations…and once in a while some hiccups with some of the camera firmware, though that’s usually not too bad most of the time, and I feel safe in being able to flash those devices back if necessary, so I usually test a few unimportant ones first and if successful then I do the rest, if not successful, I can just flash them back to production…but can’t do that for the hub, so while I only have 1 hub I am now a lot more careful with it ever since that one firmware early on where you and I and others had so many problems with the hub freezing up. Now I wait until reports indicate it is safe first.
I’ll probably get a second hub in the near future and take more risks with that one, but not with my main critical hub anymore.
Are you guys still having problems with your hubs on this firmware? Or did Wyze fix some server related issue with it so it works fine now? Because I just saw message that this same Hub firmware is being pushed out to production and the general public and I haven’t heard whether your issues got resolved or whether we’re about to have a ton of upset Wyze users with the same issues:
My issues have cleared. Must have been something server side. The only issue I still have is related to turning on or off the Tune settings. I cannot seem to change it, I am doing some additional testing and will submit a log later tonight.
That’s great to hear. I was worried we were about to have a bunch of really upset users over this firmware update since the firmware didn’t change at all before it went to production. Like you said, it must’ve been a server-side update to fix it. That’s a relief.
Interested to see how it goes for public adoption.
Having major issues now with the HMS setup. I decided to see if I can get by the Loading issue of the devices as I have a few devices to add. I unplugged the power got notified the hub was running on battery held the button until the light went out and plugged it back in, the lights cycled and became solid. still no luck. Now none of my sensors are working and no Rules are firing when triggered by a sensor on the hub. The hub keeps cycling. 3 lights solid and then starts rotating as if it need to be paired.
Just got my Video Doorbell Pro installed today. It is wired and seems to function well. I believe this is a bug so I am reporting it, if I am incorrect, please let me know:
Item 1: There does not appear to be any ability for setting a Detection Zone.
Item 2: I was setting it up as I had the Original VDB and wanted to be able to record all motion and only Notify on AI (Person, Pet, Package). When I go to the Event Recording options, it only allows for an either / or for recordings. If I select AI, I cannot set all motion and vice versa.
Item 3: The LED around the button continually Pulsates Blue when connected to the Transformer. If on Battery, it will be a White Ring around the button until motion has been detected.
As indicated above, if this is the intended methodology, please let me know. Otherwise, I think it is a bug and should be corrected to make it more consistent with other camera’s.
I am fully using my VDB Pro and am liking it immensely. Appreciate the additions being done and provided. However, I have a couple of questions and potential bugs but would like your input as to if this is an issue:
As you may recall, I also have the VDB v1 and it worked as well. But I am finding the following:
The VDB v1 seems to capture motion further out and therefore notifies of AI events sooner. Here is a video showing it captured a vehicle on the road as it drove by:
The Pro version has not captured any cars nor has it captured anyone walking on the walkway from my driveway to the porch where the VDB v1 did.
When on Battery the VDB Pro has a White Ring around the button and then pulsates Blue when motion is detected. The VDB v1 has a white bell and then pulsates Blue when motion is detected. However, now that I wired the VDB Pro up to the Transformer, it is always pulsating Blue, to me this is indicative of motion. Shouldn’t there be a white Ring around the Button when no motion is detected? If this is an issue and the pulsating is only supposed to happen when the VDBPro senses motion, then this could also be causing item 1 above.
Curious on what to expect and to gain an understanding as to why there is a difference.
I am also providing a log for you to review in the event it helps out:
I would tend to agree. However, when I was testing in my office, I had a USB plugged into it and the battery would go down to 90% and then up to 100%, it was charging all the time and the Pulsating Blue Light only appeared when motion was detected.
My assumption, incorrectly, was that hooking it up to USB would be the same as hooking it up to the transformer. Instead, using USB still treated it as battery operated and there were subtle differences like the load time for live streaming. When connected to a transformer, it is almost instantaneous. When using USB or Battery it takes longer, similar to the WCO.
Here is what the icon shows when connected to Transformer:
So, hub firmware, plug firmware, switch firmware and the app all seem to be having problems right now. I believe I’ve also seen problems with robot vacuum, door bells and thermostats. The brouhaha over CamPlus and CamPlus Lite plus all the setting issues…
I think my statement about buggy products is fairly accurate right now.
I will agree that Wyze is experiencing some bug pains recently. I am wondering if it has to do with them changing things in the backend or how things are hosted. Sometimes after firmware updates, the reported bugs this year were resolved without changing the firmware again, which leads me to believe some of it may be back-end stuff. I do hope they can figure it out. I suppose my earlier statement was a lot more reflective of my overall experience in the previous 2 years. I had absolutely everything using beta firmware and rarely experienced serious issues. I am a little more cautious in 2022. I still install beta firmware on everything (except the hub now)…but I agree with your initial statement that Wyze should look into improving their QA procedures. One thing that should be discussed is more interaction in the beta threads by someone on the team for that product to ensure they’re aware of things that are reported (ie: the hub firmware bugs) before pushing it to production.
@R.Good asked me to check on something and I noticed it as well. Might be a little different but bottom line, I cannot scroll through all sensors on Android when accessing the Sense Hub v2. In addition, the Sensor Order is different in comparison to iOS.
Here is the info
On Android, I cannot scroll through all of the sensors. Image provided shows the top of one of the sensors (arrow pointing to it) and when I try to go to it, the spinning icon appears but nothing changes. I cannot scroll through the entire list of 33 sensors on Android:
Hidden Sensor ---------------------Spining GIF at bottom
Confirm that the app reports network connection
Are you able to arm/disarm using the keypad? Can you do it using the app?
Keypad - No - Wyze App - Yes
Try holding the Reset button on the hub to reboot it
When I reboot the Wyze Sense hub it goes into a reboot loop for a couple of hours. Finally comes back online after a couple of hours and then my rules stop working (more on devices below as related to iOS and Android)
If you’re having issues with your sensors, what is the message you see when they fail to pair? Is it failing 100% of the time or are you able to succeed sometimes?
I am now able to add devices to the Wyze Sense hub.
I have 35 devices attached to my Wyze Sense Hub used for Home Monitoring.
On Android Wyze App v2.29.0(114) On Android 12 (Pixel 6 and Galaxy Note 10+) I cannot see all of my sensors attached to the Wyze Sense hub I can only see the climate sensors and 1 Contact Sensor that I recently added.
On iOS Wyze App v2.29.0 (a25)
I can see all of my sensors associated to the Wyze Sense Hub
Log ID for Android Samsung Note10+ - 515832
Log ID for Android Pixel 6 - 515833
Log ID for iOS iPhone 12 Max Pro - 515835
iOS (All sensors show) --------Android (Only climate sensors and the latest added contact sensor show)
I’m now having major issues with the Wyze Sense Hub. I think it mostly started with the 126.96.36.199 firmware, however, I looked into updating it in the first place because I noticed not all of my sensors were listed under the settings for the hub. And that was when I was on version 188.8.131.52. After updating (to 184.108.40.206), it still does not show all of my sensors which are connected to the hub but now the problem seems worse. Any attempt I make to change the connection for the hub, from Wi-Fi to ethernet or vice versa, or changing the Wi-Fi network, results in all of my sensors losing connection to the hub. The hub still appears to be connected but none of the sensors are connected to it. Also, if I re-add the hub, with or without changing the internet connection first, it also loses all connection with the sensors. So then, I have to go and manually re-add all of my sensors to the hub. This way, they appear to reconnect and stay connected and I don’t have to mess with my rules at all. However, I’m afraid I may have to fully delete the hub and then re-add it. Last time I tried that, many of my rules were also deleted which included anything to do with the sensors that were connected to the hub. So I’m saving that as a last resort. I’m also wondering if I need to reset the Wyze Home Monitoring, if that makes any difference with this.
So, there’s an issue with reconnecting to the sensors after making any change to the internet connection to the hub, or re-adding the hub. Also, the settings for the hub does not show all of the connected sensors. When you pull to refresh, it just spins and continues to show the same sensors which does not include all of my sensors that are connected to the hub. This is quite annoying. Also, I already tried to submit a log, and for some reason I’m not able to. It gets to the last page but when I hit the submit button nothing happens. I’m not sure why this has to be so difficult. Can you please fix it. Also, I think I read somewhere that you were sending replacement hubs to people so they could send back theirs to figure out what is going on. I would be willing to do that if necessary to get this fixed.
Please let me know what I can do. Thank you.
After re-reading some posts, I decided to try toggling the home monitoring service from disarmed to home and back to disarmed. I did this a couple of times. I did It once from the keypad and once in the app. Then, after that I noticed that all of my sensors were reconnected to the hub and their status was showing correctly in the app. This was after I did a soft reset, so none of my sensors were connected because of the firmware bug or whatever. But it seems that toggling the monitoring service reconnected the sensors. So the bug must have something to do with the connection to the home monitoring service. Things seem to be working correctly now with the sensors and the rules. But I’m still not able to see all of the sensors under the settings for the hub. It just shows the first ones and then when you try to scroll down you just get a refresh circle but after refreshing, it still doesn’t show the other sensors. I’m not sure what all this means, but I thought it might be helpful for someone. Hopefully they get this fixed soon! If they fix it with a firmware update I’ll want to try it right away to see if the problem is fixed, but I’ll also be a little nervous based on what the last firmware updates have done. We’ll see I guess. I’m also still not sure why I can’t submit a log. I’m unable to submit it for the hub or for anything else. The submit button does not seem to work.
I figured it out. I didn’t realize you had to type in details. I just referenced these posts in those details. And I submitted the log. Log ID: 546883
Also, I’m not on beta. Sorry, I should’ve mentioned that. I’m just trying desperately to get this to work correctly again.