Understood. But what if the camera does not successfully connect to WiFi on the first try? I have had that happen in my presence. Usually it will connect on the second attempt, but I am there to pull the power to initiate that second attempt. If I’m remote only, as I am now, I only get one shot. I don’t trust the Wyze camera enough to attempt a remote reboot unless it’s the absolutely last option. In normal circumstances, I would attempt the reboot and if it failed, I’d just drive over there and fix it. But now, under lockdown of the facility, I don’t have that option.
My sensors went dark last night too, and this bridge restart advise brought them back up. Thanks!
@themdg - Did you do a physical power down restart of the camera/bridge, or did you do a remote restart of the camera via the app?
Mine went down last night also, I removed the bridge and plugged it back in.
I have my v2 cam/bridge setups connected to Wyze plugs and remotely power-cycled them this morning. Everything came right back up.
I have restarted the camera with the app in the past, remotely, and it always reconnected. I did this when a Wyze bulb went offline because of its distance from the bridge. That brought it back online. I’m sure notifications are important to you, then you have to weigh your options. As I mentioned, rebooting the camera from the app has never caused the camera to fail to connect to WiFi. This may sound obvious, but have you checked to see if universal notifications are turned on in the app as wellas the camera’s notifications?
It is not just notifications that are not firing off, events from the sensors are not showing up in the Event List, and that is not something that you have to enable. With no events being logged in the first place, I would not expect any notifications.
I will probably just have to bite the bullet and try a remote reboot. Normally I wouldn’t even blink an eye at doing this. But in the current situation, where I cannot physically access the camera/bridge for a local reboot and troubleshooting, I am hesitant to potentially nuke the more important camera while trying to fix the less import sensors.
FWIW, the Wyze cams runs an operating system (Linux) like a desktop computer that runs Windows or MacOS or Linux. Performing a soft reboot of a Wyze is no different than a soft reboot of a PC or Mac … as in System menu -> Reboot (and we all know, a Windows machine needs to be rebooted all the time). It’s not like the Wyze is gonna power off as with a Shutdown on a PC / Mac
MOD NOTE: Post edited to conform to the Community Guidelines.
I appreciate your responses. You appear to be insulted that I did not immediately run off and remotely reboot the camera on your suggestion. That response, I don’t understand. I am soliciting feedback from others here as well as from you, to get a feel for if they have had problems with their WyzeCams not reconnecting to WiFi on the first attempt. I have had such problems with the WyzeCam myself on occasion. And it’s not because I am ignorant or technically illiterate. My entire work career, since 1980, has been Unix (then Linux) system administration and systems programming, networking, computer security, etc. I really do have quite in-depth knowledge and experience with operating systems, routers, WiFi and most things that relate to WyzeCam operation.
However, I still have pause about doing a remote reboot because of demonstrable problems I have personally had with the WyzeCam in the past. And also because of my decades of experience at work having “remote things” go bad.
So now I am indecisive about exactly what to do. Should I gamble, or should I play it safe? I have a critical need to monitor my mom, who has dementia, in a remote setting that I do not have physical access to any more. And I must use the hardware that I chose and installed (Wyze), even if in retrospect that may not have been the most stellar decision of my life. I am not knocking Wyze. It is extremely good for what it is. But you have to remember what it is, and I did not. $50 worth of hardware falls into the hobbiest/toy category, but due to my own error in judgement, I put it to use in a more critical application. My choice to use Wyze was just fine for a long time … right up until [I was] denied physical access to it to fix problems. I am solely responsible for putting myself into this situation, and I’m just trying to find a way out of it.
I appreciate your responses. They are helpful. Thanks.
MOD NOTE: Post edited to conform to the Community Guidelines.
Understood. And we have similar backgrounds - me as a software engineer and site reliability engineer, and published author of a number of programming and OS books.
My wife purchased two Wyze cams with the sensor pack and installed them at her mom’s (80s) house to keep an eye on her … and we’ve been through this exact same scenario. Yes, a working camera is more important than a sketchy sensor.
Maybe a trusted neighbor can walk over and be of “physical assistance” to bounce the Wyze gear. (not a workable solution because of lockdown)
I have had a rule that resets all my cameras every night.
I had the same issues that you are having where my sensors all dropped connection. Once I reset my one camera with the bridge, they came back. I then made the reset rule, and included all my cameras. Never had an issue with them not coming back online.
@jwt, forum shows this top part is to you, it’s actually info for the group, the bottom quote is for you.
Bulbs connect to your wifi, not the wyze bridge.
You are correct. It was a Contact Sensor.
i have 1 wyze camera which for 7 months worked flawlessly also strangly went offline. i power cycled it multiple times, and it still wont reconnect. i can hear it clicking during the powercycle so i know its powering.
my option is to wait further to see if it is a wyze server issue or reset the camera.
i dread pressing the reset button and going through the setup again as it has a bridge & 12 sensors configured to it (along with a myrad of ITFFF actions)
does anyone know if i pressing reset button on the camera to reconnect a camera will lose the sensor names connected to its bridge? or can some kind soul with an extra camera/bridge try this please? thanks
Some posts were removed and edited that did not follow the Community Guidelines. Please flag posts that violate the guidelines so the moderators can respond appropriately.
The Community Guidelines require that discussion remain related to Wyze products and services. Please bear that in mind when posting.
Maybe it needs firmware update on bridge or camera. You can check this in app remotely. Mine stopped working when I forgot to update firmware.
@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.
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.
Sorry for the delay @haertig. I did a remote restart of the camera via the app, and it brought things back online for me.