Hi, an idea why can’t open my Home Monitoring Page using the Wyze Beta App on my android device. I called Wyze Customer Service and they walked me through some fixes, but none worked. Don’t have this problem with the Wyze app only Beta. Thanks
Mod Note: Post moved to appropriate category and topic.
Which version of the Beta app are you running? I’m not seeing any other posts about this in this thread, but it may be that you need to update the firmware as is required for the HMS change in this beta.
Thanks, I’ll try that
I’m on the Android Beta App w\ Home Monitoring and haven’t had any issues with opening or using functions in the Monitoring Tab or the Home Monitoring Settings.
@carverofchoice may be able to speak to this. Not sure is it is the same sort of issue experienced.
What are you seeing when you try to connect?
A blank page that says “Failed”. I know I’m in the Wyze Beta App, but here comes the silly question, “Is there only one 2.40 version”??
I saw that yesterday as well with HMS and others reported it as well. It is working now a s started last night.
I tested on a Samsung phone, pixel phone and iOS. All gave failed but different points.
I would do a clear cache from the app in the account > App settings area
Then shut the app down and long press on the icon ( if you are using Android). Select app info then force stop. Go to storage and cache and clear cache from there as well. Restart your phone or tablet and then try again. Your camera images may be gone, but they will come back when you live stream.
By the way, I am running 2.40.0.b180 with the hub running firmware 4.32.12.534
This beta has improved the laggy ness and app hanging but it is popping back up more and more frequently again. It seems like it could be a memory leak issue. I would like to see this resolved sooner rather than later.
I can’t thank you enough for noticing this! I have been having this problem for several days. I have tried so many things. I even reset my HMS service, which finally restored access to the monitoring tab without saying “failed”, but I could not get past the step to setup a “Home” as it kept failing on the address and telling me it was invalid. I’ve been working with some employees Wyze on this issue, and they’ve tried a few things, but nothing worked.
I am SOOOOO glad you suggested using the production app. I went and used my daughter’s phone with the production app version 2.39.0.179 on it to try to do the setup, and it actually worked!!! So there is some kind of bug related to the Beta App which is not in the Production. Seriously, I’ve been dying trying to figure out how to resolve this.
Now I can use the monitoring tab just fine on the production app, but when I try the beta app on my primary phone, it still gives the “Failed” notice on the monitoring tab.
I guess I just need to uninstall the beta app. I don’t know why this is only happening to a select few of us, but this is a pretty critical bug that needs to be looked into before this app version is released to the public and it starts to affect more people.
Additional Rules Action Toggle Conflicts. Tested on V3, V3Pro, PanV3. Suspect it is on all cams w\ siren.
Turn On Siren and Turn Off Siren are conflicting Action commands that can be set to execute simultaneously on the same cam.
I am hoping that eventually Wyze will update their rules engine to work sequentially like how Alexa does it. Then we can have a wait x amount of time rule and use seemingly conflicting roles like this… Ex: Turn on the siren, wait 10 seconds, turn off the siren.
Absolutely! Even if they do keep it the way it is, I would just like to see the ability to reorder the list sequence.
You are not alone. It’s happening to me on the 240 beta. Same with IOS. Droning back to the production release restores function …. at least on th IOS version.
I’ve cleared cache on the Android app with no difference.
Re 2.40.0.(3) on iOS.
The same thing happened to me last night. HMS failed to load. This morning HMS wants me to start over and reset HMS info. When I add the home address it keeps telling me the format is wrong. Now it wants me to add all of my sensors to the HMS hub even though the app shows all 37 of them working just fine. I’ve tried all the stop/start/reboot/clear cache fixes but nothing works. My wife’s phone with the production app works fine. Support office is closed so I’m at a lose for what to do. I dread adding all sensors back to the hub - some are not very accessible.
Having read others experience, I am doing nothing and waiting to see what transpires with the server mods being made or a new Beta release. I am using just the keypads for now.
This is one of those times when it would be really convenient to be able to run the production app and the beta app on the same device.
If it becomes a game changer, I will delete the beta app and revert to the production app.
If I delete the beta app and install the production app, do I have to set up the entire system like new to include reattaching all the sensors to my two hubs?
I think it really depends on what you have done in the Beta app after it stopped connecting. If you haven’t changed any of the original setup, deleted the hub or sensors, or modified any settings, everything should still be on the server for the production app to pick up. Since it’s still working on your Wife’s production app, chances are good it will still work on yours when you roll back.
Reports are that is is only the Beta app and doesn’t affect the production app.
Same problem on all of my Android phones and tablets. I tried clearing cache, log out/in, restart device, uninstall/reinstall beta app to no avail. I had to revert to production app version 2.39.0 (179) on my primary phone to be able to control HMS remotely.
No joy. I just deleted the iOS beta and installed the production version and the HMS wants me to complete the 15 step HMS setup even though the app is showing all 37 sensors working from the hub.
Update: I had to setup HMS but was able to skip the reinstall sensors step by just selecting the Continue option on the Add Devices page.
Log: 906849
