Event viewing has been back online for some time now. You should see events populated in the Events tab in the app. If you do not, I’d suggest force-quitting the app and restarting and/or restarting your phone. If you still do not see events, you should contact Customer Support.
Data is the new oil. Oil is lucrative and messy. Spills happen.
Thank you for the update. As of now, I still have one of my 8 cameras that I can’t get back online. Please advise: Cam v2/USB powered.
I still have a couple of V2s that I have not gotten around to fixing. Others have reported that factory reset gets them working again.
Update: turns out my offline V2s were due to a power cable being disconnected.
I also want to see a better explanation. The emails make it sound as though caching layers that experience high load will naturally return wrong data, which doesn’t make sense to me as a software developer. There is obviously more to it than this, and I think it’s reasonable for us to expect a more detailed and credible explanation.
Hello WYZE Cam. I was able to get the cameras back online this morning. Thank you for taking responsibility for the issue . I will continue supporting your cameras.
I’ve got both the second and third mail.
In my case I guess it was not a big deal, since at that time I only had 3 outdoor cameras online, so my event videos were of people and cars passing by, recorded from a distance. Paranoid me always powers down indoors cameras when we are at home.
But just to put this in perspective, several years ago there was a similar bug on Microsoft’s Terminal Server (on the print spool subsystem) that, in my country, led to users getting other users’ listings printed on their local printers. So I Guess no company is free from this kind of issues.
I will let them know that many are asking for the name of the caching library.
Correct
Are any accounts compromised?
In the sense that someone could log into and access someone else’s account? No, nothing like that has been reported.
My only issue is that my v2 door and motion sensors have not been online since the 16th. It is not the 19th. Is this caused by the outage or do I have another issue.?
My cameras, door locks, doorbell and thermostat all work fine.
Actually they seem to be online in my app, they are just not reporting movement.
I am sorry you still have offline sensors. Can you verify if your hub is online? If it isn’t I would try a reboot of the hub, do this by pressing the button on the back for approximately 10 seconds. You will see the lights change at this point let go of the button and devices should reconnect. If your hub is online or this does not work I would recommend contacting our support team.
Thank you for the email report, not an ideal situation for sure. Thank you for your long hours over the weekend investigating this and building securities to hopefully prevent another incident. We appreciate your honesty and transparency as well as your willingness to grow, be better and do better. We will remain loyal to Wyze and continue to value your dedication to provide reliable quality products at incredibly reasonable rates.
Although some added features in the updates have been welcome, I start worrying when more features can add more problems. I think security should be focused on more and give extra features a break for a while.
It is online as the door beeper goes off when I open the doors and windows. Just nothing is recorded. I did reboot the hub, my modem and my router.
Yes, and that link is pretty much a joke. This is really bad with no help in sight. You guys screwed the pooch on this one.
Security Breach
“Wyze users received thumbnails from cameras that were not their own”. from your email…
Wait, so you STORE ALL video on a central computer? So as our Wyze is pointing towards our driveway, you know when we leave the house empty?
[Mod Note]: Your topic was merged to this Wyze News announcement topic for better visibility.
I’m glad Wyze took the time to investigate this before sending out the email(s). This sounds like the initial AWS issue triggered interrelated effects, and will surely need further analysis.
I would recommend that before the next renewal of the contract/service agreement with AWS, terms be included in the language of the contract to better hold AWS responsible for failures like this on the part of AWS. There should be penalty payments in consideration for service issues that impact Wyze as a customer.
I would also recommend that Wyze diversify who it purchases server services from, to include multiple service providers. This will avoid vendor lock-in, and also foster better price competition between service providers. Wyze should definitely avoid putting all of its eggs in one basket (AWS, in this case), and have multiple providers online, between which Wyze can shift loads as circumstances require.
And this is how @WyzeJasonJ feels this morning.
I have notified the team is there any way you can send in a log and give me the log number?