Additional Logs: 1202229, 1202258
1 Like
Are these from it happening today?
2 Likes
Is there any way to grab multiple logs (if it’s happening multiple times a day) or do I have to catch it each time and grab a log right then?
1 Like
There isn’t a way to grab multiple, just grab one when you notice it happen even if it has been a few hours. I am mainly looking for logs from it happening today.
3 Likes
Log: 1202573
I noticed it was down again a few hours ago and power cycled. I couldn’t tell you if it was from today or not but I think it was (I kind of gave up on checking them because it happens so often). I’ll start checking more often.
Keep in mind, I could just manually kill wifi for a moment and then wait an hour before grabbing a log if your main concern is it not reconnecting rather than the initial disconnection itself.
1 Like
Hopefully we can trace why it is disconnecting also, so try and let it disconnect naturally.
3 Likes
Log# 1202654.
2 Likes
Yes these are from today.
3 Likes
Came home tonight and both Pan V3s down again. Just power cycled, here are the logs. Would have been some point in the past 24 hours.
Logs:
Pan V3 #1: 1203630
Pan V3 #2: 1203633
Edit: Wait, are these log IDs sequential? You’ve had over 1,000 logs submitted in one day? Wow.
2 Likes
Yes. They are. But you also have to consider that the entire Alpha and Beta Testing Community is out there testing hardware, firmware, and Apps on every version currently in testing. That is always a ton of logs submitted.
3 Likes
Ah, okay. I figured alpha/beta testing would be on its own channel. Still, even considering that, 1,000 a day is a ton! When I’m working on code in testing I start getting overwhelmed at, like. 80 reports in a day. They must have a much bigger team than I thought.
1 Like
In addition to Alpha and Beta producing logs, there are also a lot of people who submit logs as feature or product requests and the most frivolous things you can think of. I’ve seen posts from people saying they submit dozens of logs every single day about the exact same frivolous thing that isn’t even a bug. Or there are the people submitting logs for things that aren’t even Wyze’s fault, like a third-party extension cord not providing enough power to the camera.
2 Likes
The two way communication is in separate channels, but all the Wyze Devs and PMs pull logs from the same log inbox. The logs bin isn’t monitored actively. It is just an unmonitored inbox. They have to be selectively pulled by number by the Devs and PMs out of the inbox to be inspected. That is why log numbers have to be posted. They have to know where to go look for it.
3 Likes
This has been a problem for YEARS with many wyze products. I dont personally have that much trouble with my cameras for some reason, but for me the PLUGS are the annoying thing. I we have a power flicker and the wifi goes down, it needs to be up before the plug (or camera) is up, or you are in a situation where the Wyze firmware will NEVER again try to connect to wifi, so you have to reboot. There’s another thread with tons of people complaining about this and Wyze hasn’t even responded to my knowledge.
This is the very reason I installed a 1500VA UPS to maintain my ONT, Root Router, HMS, and various other electronics when there is a power issue. I just had a momentary outage last night and every device on the network came back online perfectly.
Untrue. There have been many occasions when I neet to reboot and\or power cycle my routers and ONT, thereby severing the power and internet connection to the ONT, all router nodes, and WiFi to every device that remains powered on my network. All devices log back into the network when the ONT and routers power back up and restore WiFi to the network. This includes 16 Wyze 2021\2022 CFH Plugs and 27 cams, 4 if which are PanV3, that never fail to log back in.
While it is easy to consider the cam as the issue of not regaining WiFi connectivity, the router is making all the decisions as to what devices get a new IP. If my router was doing that, I would seriously consider replacing it with one that did a better job of reboot DHCP management.
1 Like
I think the issue isn’t that it doesn’t try to reconnect, but that once it attempts to and fails it seems to mark that network as “unavailable” or whatever either permanently or for an extended period of time. Whether it’s the default behavior (it should be) or an option, once it loses connectivity it should do two things:
- Scan available networks, and see if any saved SSIDs are available. If not, sleep for one minute and repeat.
- If a saved SSID is available, attempt to reconnect. If connection fails, try the next one. If there are no others to try, sleep for one minute and repeat from 1.
Not just v3s; my Pan Cam v1 does the same thing.
1 Like
Log 1204893
not from today, but weeks ago (I gave up climbing a ladder to power cycle the cam, did it so many times it’s frustrating)
I think somebody stole some tools from my carport. Good thing I’ve got a Pan V3 out there! Went outside, disconnected again.
Log: 1205620
Edit: it shows a recording around six hours before now, so it died within six hours of this log.
Edit: other one is down. Within the past couple hours.
Log: 1205632
What about the SD card recordings? Even if it is offline, it should still record to the SD card, right?