Starting to recover. Bay area @5:11 pacific time.
Yep, same here.
Did y’all get any of these?
I didn’t, I think they were still connected and a cockroach got into the AWS server.![]()
![]()
I thought
was supposed to eat those:
I’ve had a sufficient (as my Canadian neighbor chided her ‘I’m full’ son to say in lieu.) ![]()
Negative. I happened to be checking one of my cameras that tends to pick up wildlife and got the error 43. I have, however, received those previously when my home internet stopped working last week.
If there is an outage, the server can’t push notifications to the app, so the notifications are only applicable when YOUR network or camera stops working, but AWS and the Wyze server is still up and running.
In past outages they have mentioned that they will often have the server handle missed notifications carefully so that it doesn’t overwhelm their server and cause another outage by trying to immediately catch up on stacked notifications. I don’t know what they do exactly, but if I were them, I would probably tell it that when there is an AWS outage, the server should ignore all the notifications about camera outages entirely because it will be pointless to send them so long after the outage is no longer relevant and it will be tying up the server for no reason.
However, I could see a legit rationale to send a notification telling people their devices are back online.
Well this explains why I get a disconnected notice 5 hours after it’s actually been disconnected. Thank you!
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.