Motion detector and door sensor went silent yesterday evening

@haertig Sorry to hear this. I had the same thing happen a couple days ago. It happened after we had a momentary power outage. Tried remote restart but that didn’t fix it. I believe this A power cycle did fix it.

Hopefully somebody at the senior living center could go in and unplug and replug the camera. You would instruct them to do it at the wall socket, so that the camera is not disturbed.

For future in critical usage like this, you might want to consider putting a Wyze Plug (or other brand) between the wall socket and the power adapter so that you can power cycle remotely. Also, if she has her own modem/router, you might want to consider getting something like this to automatically power-cycle the modem/router in case the internet connection goes down. These would, of course, probably have to wait until you can visit.

@Loki - That internet-sensing remote reboot device is an excellent idea. I didn’t think of that. We had similar things we used at my work. They weren’t automatically triggered by internet loss though. They controlled power to our networking gear - routers, switches, etc. We accessed them by telephone dial-in (old school!) From there you had access to power cycle any/all of the power ports on the device (and there were many).

I like your suggestion so much that I think I will implement this using a Raspberry Pi. The code would be simple, and I could customize things like “Power cycle modem, wait 2 minutes, power cycle WiFi Router, wait 2 minutes power cycle multiple Wyze cameras and other hardware”. Remotely controlled plugs are a dime a dozen these days, I’d just have to pick a brand/model that I could learn how to control with a Pi (maybe requiring some kind of hub as intermediary for local device access, but maybe not). Maybe Wyze could enhance their power plugs to allow direct local control from things like Raspberry Pi’s (hint, hint!)

I do currently have things (but unfortunately not the WyzeCams) plugged into multiple power strips so I can instruct my mom to cycle “power strip #1” then cycle “power strip #2”. That has worked for years, although using this method has rarely been needed. But now mom is losing the ability to follow these kinds of instructions, especially since the power strips are found in different locations in her place, and some of them are tucked under furniture and such. I am also starting to lose my memory of where each strip is and what is plugged into it. I used to know, but those memories have faded over the years as we found little need for power cycling things like this. My fault for letting my memory slide on this, without documenting things. Live and learn. I never expected something to preclude my access to mom’s place. I was always expecting a ten minute drive over there, a quick look around, and I could investigate and fix any problem. That plan worked fine. Until present day lockdown.

Another Pi project I am considering is a remotely controllable TV remote (“IR Blaster”). So I can remotely login from home and send commands to her TV setup when she invariably calls with the “No Signal” complaint after inadvertently changing the input from HDMI to Composite or something equally as deadly for an elderly person. With the WyzeCam being able to see the TV as well as the rest of the room, I could send TV and cable box commands remotely and observer their effect on the TV using the Wyze app viewing video.

Ideally, TV’s, cable boxes, cameras, and all kinds of other stuff would accept direct control remotely, but there are still a lot of gaps there. Heck we’ve been trying for years to get TV/cable box designers to support discreet on and off rather than toggle, but they still seem resistant. So we have TV’s and cable boxes that get out of sync power-wise. Grrr. That’s as bad as the “No Signal” problem (why don’t TV manufactures implement a configurable lockout for input source change?)

We are halfway to our automation goal with things like WyzeCams and Raspberry Pi’s, but it’s still the wild, wild west regarding this and it’s really only accessible by techie geeks currently.

1 Like

After almost exactly 7 days (within an hour), my motion and door sensors came back online. No reboots, no known general power failures that would have triggered a reboot. There is no way to determine with the app how long the camera/bridge has been up (a.k.a. the Linux “uptime” command). Something like that would tell us if the camera rebooted for other, unknown reasons.

The sensors just “fixed themselves”. Now this entire 7 day long error condition looks like it could be something on the Wyze end just as likely as it could have been something on my end. Were the sensors not sending (as was my assumption) or was Wyze not receiving/storing/displaying (this appears just as likely at present). If Wyze developers know anything, it would be nice if they tell us, so we can know what happened.

1 Like

Sorry for the delay @haertig. I did a remote restart of the camera via the app, and it brought things back online for me.