03/26/2026 4:37 PM PT - Our team has found the cause and the Wyze app should start working normally soon. We thank you for your continued patience. If you continue to experience issues please contact our support team at Wyze Customer Support.
4:06 PM PT - Our team is currently looking into issues being reported with the Wyze app and devices. More info will be posted here when we have it. We apologize for any inconvenience and thank you for your patience.
WyzeJason. Thank you. Have you considered modding the app to allow you to easily âturn on and offâ a âService Advisoryâ? Not a notification sent to the phone, but a small message appearing on the app main screen, when we open it. Then when service is restored, you âturn it offâ ???
I will have to ask the engineers if they can do something like that. I am not an engineer by any means and my main question would be how we can send a message to the app screen in an instance where we cannot talk to the app until service is restored.
Right! Reminds me of the old, âWhy didnât I get an email telling me the email server is downâ?
This is a good idea! 
I will offer Wyze a great way to implement this:
If I was going to try to design something like this, the way I would handle it is to use the following fail-over logic flow that isnât dependent on a pushed message:
The app follows a âfallbackâ diagnostic path:
With this logic flow it doesnât require a sent message from the server and doesnât slow down recovery. The message is automatic based on a fail-over workflow trigger with a safety check to know if The lack of connection is due to the person not having internet access, or whether they do have internet access and thereâs just a problem connecting to the wyze server. The messaging could even be changed to not necessarily say that the problem is on your end, but to just suggest there is a connection problem and they can check your status page to see any official updates about it. I think itâs a highly professional & user friendly suggestion that people would appreciate.
WyzeJason, and Wise Jason. Thank you. Its that kind of positive (possibilities) attitude that we love to see. âIâll ask if we can do thatâ, is 1,000 times more customer service oriented than âI donât think thatâs do-ableâ. We appreciate you asking.
And big +++ to Carver for his idea.
Iâve often wondered why they donât have a dedicated subdomain for this, like status.wyze.com, similar to what many companies seem to do (e.g., https://status.discourse.org/). I tend to use a sidebar custom section link to https://go.wyze.com/servicestatus and also like that because itâs easy to remember.
I do like the idea of a button or some other means to report as long as it can be protected from spam or other abuse. I wonder if the bot in the Help Center could be trained to recognize user outage reports and also linked to some kind of back-end system that would notify the engineers if users above a given threshold are telling the bot that something is down.
Sad to say but this is closer to impossible now with the availability of openclaw.
Though, the mitigation is to make it not worth the token and electricity expense. A button can work or a form with static multiple choice options so there is no input spam area. Then limit reports to a particular IP address/range only once in a given period. Maybe use browser fingerprinting to limit matching fingerprint results to a set internal too. Basically, even a disgruntled customer with an openclaw agent trying to punish the company by repeatedly reporting outages could be mitigated with enough foresight to make it so they arenât really detected as an outage pattern and theyâre just wasting tokens or electricity.