I have 2 OG cams (1st generation cams) both have been in use,
one registered on 12/3/2024,
the second one registered on 1/24/2023.
In the last few weeks BOTH OG’s cams have been going “offline”
with the 1/24/2023 older activated OG cam,
much more often, than the 12/3/2024 OG activated cam.
Both have the same Firmware version (1.0.98)
The one I have removed/deleted form the setup, thinking that would help
And it did for about 4 days, and now it has started to go “Offline” again.
I unplug it, and wait 10 -20 minutes,
Plug it in again, and same issue
Then try it again, same issue
Then try it again, and then it takes, and is back online
Until it starts happening again
I can only correlate this has to be with multiple Wyze updates in the received in the last few weeks.
As both Older model OG cams were previously rock solid in reliability, since installed in 2023 and 2024.
============================
Here is a Side issue I have also realized with the 1st Gen OG cams
When they register in DNS/DHCP, the OG cams have the same names…where all other Wyze cam’s
Register their name that includes a MAC address in the Wyze cam name.
Having multiple 1st Gen OG cam, with different IP addresses, BUT the SAME OG cam names is a problem.
If a DNS query is performed by the app, or user, By name, it points to multiple “” WYZE_CAM_OG “” default automatically named cams in DNS, with each separate OG cam having a different IP address, but the automatically Wyze generated “” “” WYZE_CAM_OG “” DNS Name.
The DHCP/DNS issue likely isn’t anything to do with it. If a device doesn’t report a hostname, or reports the same name as another device, it is up to your router how to handle it, some will just assign a generic name based on the MAC address, some will just not register the second name in DNS. They also often show a different name in the GUI than what they actually register in DNS.
The DNS name of the cam isn’t actually used by anything, it is all done by IP and MAC, so shouldn’t affect anything either way. I have DHCP reservations for all my cams (I like to organize my IPs) which lets me set custom hostnames for them too, so that’s an option if you want to clean that up, but shouldn’t change anything with connectivity.
If you have two cams that started experiencing intermittent connectivity issues at the same time, the most likely explanation is a change in the wifi environment. If nothing changed with your hardware (new router, firmware updated, settings changed, etc) then someone near you may have put in a new router, started using 40mhz channels, etc. If your router has the option to disable beamforming, try that, as that can cause instability of signal and it generally offers no benefit. You may also want to try a different channel, or just reboot the router so it scans and picks a better one (not sure if you’ve tried rebooting the router yet, I’m assuming so, but if not definitely do that first).
It could even be interference in your own house from a new bluetooth device or something like that. If you can reposition or relocate your router to get better signal to the cams, that will help them overcome any interference.
The only other thing that I can think of that might explain it would be a power surge, you could try a different power adapter to see if it makes any difference (any USB adapter or phone charger with at least 1000mA rating will work, even 750mA is probably plenty).
I have 4 OGs in use and haven’t seen any connectivity issues, I’m on the latest android app.
I do understand what you are saying, and do understand the cam name in the app, is not the same as the name in the DNS record.
Overall I wasn’t saying the DNS/DHCP matter was the cause, it just that Wyze, for some odd reason, on the Old OG model cams, did not make it a standard to register the OG Cam, with it Mac Address including in the model name, like all the other cams do…So there is 3 OG cams, Different IP for each, but all have their DNS name being the same…“” WYZE_CAM_OG “”.
Overall that is bad practice Wyze implemented goes against DNS proper practices
Only time with networks/networking/datacenters, there are 3 or more devices with the same name and different IP address for each device, is in Clustering or load balancing, that I know of.
Overall all my Wyze devices register DNS/DHCP with 2 Windows Active Directory Domain Controllers…there is no reliance on DNS/DHCP from the network routers.
Primary and Secondary DHCP/DNS within an Active Directory environment.
Overall, these 2 older model OG cams have been working fine for some years…Ironically, it only started to happen around the same time, as all the Wyze Updates I had received it the last few week, ( 3, it may have been 4 updates) —
One of the updates I went to find out what was changing/ or being updated, and Wyze had no posting info on it, and it was a small update…
Thought that was very odd…
yes, same here, all my devices on my network that are not assigned a static IP, are registered in DHCP with reservations. All Wyze devices are reserved IP/Mac addresses in DHCP.
No new devices or bluetooth devices added to network,
actually the last device I had added to the network, and Removed, were those 2 problematic New Version OG cams back in June/july, that wasted a lot of my time, and I ended up replacing it with the Wyze Cam V4 which worked from the “get go”
All my other cams, are split between 2 Wireless Routers, Front of house and back of house…The problem OG cam there are 5 other cams on that same wireless router, that don’t have any problem, so to me that would rule out any wireless interference issue…
Yep, Did that already, also changed USB cable just to make sure neither were the cause.
Summary Of checks
– I have already tried changing power adapter to another – problem still shows itself
– Changed USB cable to another. – problem still shows itself.
– Deleted Cam from network, and added again, problem is still there
– No changes or updates to my Wireless Network that could have affected it.
— Rebooted Router
– Checked Wifi Channel, and area congestion from surrounding homes. SSID is at an optimal setting based upon surrounding traffic/channel/s load
the 4 OG’s you have
New or Old OG’s versions?
Overall I have reached a point of instead of waste time to pinpoint what is going on with the OG cam, I just ordered a new V4 replacement… I look at it, as my time is more valuable with other life matters, than trying to pin point the OG problem, for a old OG model cam that had been working well for a few years, to just start dropping off the network.
I also start to wonder, This OG cam is outdoors, in the direct sunlight, and raises the question, how long can a Wyze cam last in an outdoor environment..
Welcome to the long winded crew. Our leader is @carverofchoice, myself and @Crease are honorable members. I realize most people don’t read it all, but those who do hopefully gain some knowledge.
Actually what I meant is that what your router displays under the client list may not match what is in DHCP/DNS. Not all devices report a hostname (I believe all my Wyze cams do) and when one doesn’t, or when there is a conflict, your router just assigns something based on whatever the programmers thought would be appropriate. In your case using separate DNS servers that could be even more true. My only static IPs are my router and switch and a linux server. I let my APs and everything else use DHCP reservations, and general clients just get random IPs from the DHCP scope.
Eh, you’d be surprised, the cheap wireless radios in IOT devices can vary a ton between models. So can’t totally rule it out. Even the antenna placement and stuff like that comes into play.
One note on that is that you need an AP or wifi adapter capable of doing proper spectral analysis. Just looking at networks can be very misleading. In my case, the channel with the most available RF bandwidth is one that you’d never pick going off number of networks alone. If you don’t have one of these devices, then often letting the router/access point pick a channel (which it does after brief spectral scan) is sometimes the best thing to do.
All are the old version, I actually have 4 OGs and an OG-TEL, all pre-2025.
I replaced one of my OGs with a v4 quite a while back, just out of curiosity. Overall it is a better camera especially in color night mode. The OGs aren’t really getting much attention as far as things like RTSP being added, so the v4 seems more future proof too. Though now that they’ve made the OG interface very similar to the others, at least navigation is the same. But all my OGs have an issue with very slow navigation of the SD card. Not enough of a problem to replace them though. I will note though, the OG oversaturates colors, and the v4 seems to undersaturate them a bit, possibly due to the higher resolution sensor. Most noticeable at night, but definitely not a problem. I posted a comparison at some point that you can search for if you want to see images side by side.
My guess would be the wifi chip in it may have just started dying, seems you’ve ruled out everything else. Or possibly a solder joint cracked/came loose.
In my case - OG and OG TEL (all pre 2025) are at 3.5 years in direct afternoon sun (high 90s in the summer), rain, snow, and single digit temps in the winter. I have one Panv3 that is the same, and one that is at about 3 years. My v4 is at about 2 years. The OGs and Panv3s have yellowed a bit from the sun, but otherwise, all working perfectly. Of course, there will always be some that just aren’t quite as good. The solder wasn’t quite as hot one day, or a batch of chips was made at the end of the day on a friday, etc.
Worth noting all my outdoor cams have a drip loop in them. I use the notch in the mounting base of all the cams and have it angle down pretty sharply when it leaves the back of the cam. Water can track into the cam through the rubber boot, which can cause problems like this.
Your network sounds like mine before around 2015 or so when I realized that the cost of electricity and static IPs to run my rack was absurd compared to what I could get with a decent hosting provider. I initially overcorrected and went to an Asus router (which with Merlin firmware, was actually outstanding) and now have regressed a little bit by going back to Ubiquiti for my wireless, and am using one of their routers and switches too (the Cisco stuff I have is loud and overkill for my needs, Ubiquiti fits the bill perfect).
I have my pick of the “previous gen” enterprise equipment from work, have a stack of equipment (worth millions when new, 3 years later, worth a tiny fraction of that, network gear depreciates faster than cars) that I only use for lab testing, the noise and power is just not reasonable for any other use. So instead I run a little linux server hosting some internet facing stuff, just to have something to dabble with when I’m bored. 10 watt power draw and a free cloudflare VPN so I don’t need static IP. I do miss the visibility and control of onsite domain controllers, exchange servers, SNMP monitoring, full blown web servers, and DHCP/DNS onsite. It’s a bit of an addiction. But in my defense, it is hard to go from having complete and total visibility in my professional life using every advanced monitoring tool known to man, to more basic “prosumer” or “small business” stuff. But I’ve adapted. I’m proud of myself for not trucking home a bunch of Cisco 6513Es that we decommissioned. they do make good space heaters but 2x 4000 watt power supplies at 30 cents per KWH, no thanks.
Long tangents aside, I think swapping it with the v4 is the way to go. Tinker and learn and troubleshoot to a certain extent, then realize it is not worth the time (which is a hard realization to come to, I don’t like to give up).
Couple notes on the v4 swap:
The “pigtail” on the v4 is a bit shorter, so you need a bit of slack in your power cord to make up the difference. Maybe an inch or so.
It won’t mount to the OG mount without a thread adapter (which would look kind of dumb), the thread sizes are different. I used the v4 mount with a single screw in the same hole as one of the two OG screws and it hasn’t moved even with slamming doors and wind. It covers the other hole, but I put a bit of caulk in it anyway.
In my case, the spot I have it in looks out at an angle and needs to tilt sideways a bit. The OG mount allowed this when mounted straight. The v4 mount I had to tilt the mount itself at a bit of an angle. Not an issue if you’re looing straight out though.
Wow This is a long post resppnse
to wake up to in the morning,
It’s going to take 2 cups of coffee
to get through the post
I do understand
Its more like a Netbios name, compared to DNS name
The 2 are not the same.
I use a good utility called “Advanced IP Scanner”, reports all IP’s, Mac ad’s, Netbios names, and lots of other stuff… Makes it easy to know what is using what IP address, and also identifies and servers or equipment that may be running services, that one doesn’t want running on.
I understand,
I had experienced issues like what you are speaking of many years back
With motherboards, where the mfg, changed a few of the onboard chips, to other models/brands, but still kept the main board as the same name…the lesser quality chips on board, were not as good… All about the $$, not consistency or quality.
I use a Wifi Scanner App overall, I am not looking to get deeper than that,
As I try to manage my time daily efficiently, and this is another area of tech, that can eat a persons time up… overall, there are too many areas of tech, that a person can dive into a rabbit hole.
For me, I turned off letting the Router choosing the channels, as I found that is was not good at it, and speed was slower… This is with 2 Netgear RAX 15 routers (2019-2020 routers)..
( which if more spare money in my life appears, I would like to upgrade my 2 routers, to the latest — Mesh preferably )
I think as of this morning, I may be narrowing down what is causing the issue with the 2- OG cam’s. Mainly 1 cam, the 2nd only did it 2 times, the 1st over a dozen times,
I think it may be the USB cables, all the ones that I tried were aftermarket, and are at least 3-5 years old.
Chinese aftermarket product quality/ standards
are not the same as Mfg standards of the cables
that come with Wyze cams
They may use less copper in the wires, and such
This morning the OG cam is working after moving the USB cable around
( also in the last few months, Electric company has be replacing Utility poles, in the entire area/town, and the power is better, more reliable, but I had noticed a few anomalies in the last few months, after utility pole replacements/transformers in the area. overall just keeping aware of any and all possibilities.
But as of this morning, the more problematic OG cam is working
I am going to order a few new USB cables, ( Chinses of course) and once replaced with new, I want to see if the issue stops…
1 of my outdoor cams, has the aftermarket cam enclosure, the other 3 don’t… but have been doing well V3 and OG connection wise.. The outdoor ones though, are yellowing, and 2 of the older V3 cams the lens is starting to get haze on it…I know plastic does not last in outdoor settings for very long,
so I know one day very soon I am going to have to replaced that/those cams.
I think it is a factor many people who have outdoor cams, will realize over time.
For me, my network servers are all Windows Servers 2025, running active directory, file services, DND/DHCP, and about 2 dozen Virtual servers including Sophos network firewall. Overall they have been in place for at least 15 years. Older Intel 3rd/4th gen XEON CPU’s/Motherboards aftermarket.
Overall, electricity wise, it’s not bad, but the cost of electricity has gone up quite a bit in the last 5-6 years her in NJ, but the draw from the servers and network equipment is not bad…If the servers were say DELL rack servers it would be a different story, since they draw a lot of juice.
I agree, I also don’t like to give up pinpointing tech issues, but as I get older I tend to pick and choose where, and what, I want to dive into, and blow time.
Right now I am dealing with taking care of an just turned 87 yr old mother yesterday, and a elder brother who is at the hospital on his deathbed and expected not to last the week. So tinkering with Wyze cam issue is not at the top of my list, and just want it to work.
Yes, these cams are very sensitive to voltage drop. If the cables are long or too thin, that will definitely cause some intermittent issues, usually manifests in wifi connectivity and SD card issues. How long were the aftermarket cables? The included Wyze cables work fine for me and they are relatively thin/flat, but they’re only 6 feet long. People seem to run into issues when trying to go longer than stock, that’s when the cable quality seems to start coming into play. Of course the connectors could have just gotten some corrosion on them or maybe a bit of water inside. Where the pigtail meets the USB cable I put a bit of silicone (dielectric) grease inside the “boot” and also wrap them in white electrical tape.
Overall the electric company has been busy around the town replacing poles, pole wires, and transformers. They did finish our area about 2+ months ago, but I have experienced 2 anomalies where power went out in just 1 area of the house, but the circut breaker did not trip. Never seen happen before in all the decades we have lived in our home…It was very odd, because I was home both times it happened.
I know from past experience in IT, electricity can cause very odd anomalies in electronics, so overall, it is something I am keeping a continued eye on.
As the same time, the problem OG cam, is on the same network segment, and electrical outlet, as the other outdoor cam is, and that one, a V3 points up our alleyway to the street, and has no problems ( other than age, starting to fog the lens).
I have 3 cams outdoors, but the USB cable is fed through the base of the window with hole, and are plugged into internal outlets, so the power source is indoors.
The only cam I have using a longer USB cable is the V3 cam, which feeds into the base of the window through a hole I had made at the base/under window. And powered internally …And that cam has no problems, other than the age starting to affect the lens (clouding up /fog like)
The problem OG cam has the 6ft USB cable, but its a aftermarket USB cable not the original, I also tried a second cable that was after market 10ft…but experienced the issue with both cables.
I don’t yet have 100% confidence this is the problem, as time will prove the results.
I think it is easy for many to fall into the trap of blaming Wyze Code as the main cause of an issue, as we have to keep in our minds the environment the cam is in High Heat, Moisture, Sun, electrical environment, all play a role, more so over time…
The OG cam is older model, and has been outside the window, in high sun, snow, sleet, rain, wind etc since it was purchased…So I have to keep that in mind, as the OG cam is discoloring, as was the previous USB cable … and sunlight / ultraviolet light breaks all things down over time…
The silicone grease is a good idea
have to pick some up
That usually means one of the two legs into your house (assuming you’re in the US) went down, probably in the process of moving the wires over to a new transformer. Really not a good situation to be in as it can screw up various devices. But the power companies don’t really seem to care. They’re replacing all our meters around here and even if you call and ask them to schedule a time or notify you, they’ve just been showing up, yanking the old meter, and shoving the new one in, sparks and all.
When you lose one leg you lose half of your 110/120V breakers and all the 220/240V ones either go totally off or get undervolted to half (depending what they’re feeding).
I am in Northern NJ, across from midtown NYC, about 1/2 mile away from the Hudson River. Dense population/electrical demand
The odd electrical issue experienced is the power went out
but it only affected one room upstairs…one of the 2 rooms in the house I have my most of my computer equipment
Never happened before,
The electrical company was not working directly in our area
But they were in the next town
It did not trigger our circuit breaker/s
I have my suspicions that it is tied to the work they were doing,
even though they were not directly around our area.
