My phone is also android and it gives me preference options in the settings. It normally chooses between the 5g, 4g, 2.4, LTE, and a few others depending on which signal is best but I can “prefer” one option over all the others. So I picked the 2.4 during setup and then let it switch back to the best available and it seems to have worked.
I can’t say why Wyze has decided to stick with the tech being universally phased out like the 2.4 thing or making cameras power with USB-old school C, or making smart plugs that don’t have USB spots to plug in stuff I actually use. I’m not the most tech savvy or futuristic gal, but I can say these things already do and will continue to be problems down the road. Hopefully they are already working to join the party in the future with updates or patch these oversights so that we don’t put these products on a shelf next to our vcr and floppy disk drives in a history museum for kids to see how silly people used to be.
If your network is a combined multiband single SSID network, that is that all bands: 2.4GHz, 5HGz, and 6GHz, share the same Network Name and password, then the phone should be able to install the 2.4GHz cam without any issue at all since the SSID and Password for the network are being supplied to the cam from the phone. Just be sure to have your location services on when doing the setup so that the Setup can auto-populate the SSID and Password directly from the phone network login so you don’t have to worry about a typo.
Some have also gone the extra step and temporarily disabled the 5GHz band within the router settings to insure the phone utilizes the 2.4Ghz band since the Phone will automatically default to the 5GHz nearly every time unless it is a considerable distance from the router.
If you are running a segregated network, wherein each band has an individual SSID network name and unique password, your phone must be logged into the 2.4Ghz network.
I have a segregated network, so I’m used to physically choosing 2.4 for Wyze.
thanks everybody, i’m going to see what happens with the new cams.
Just read some of the posts
Just throwing in a thought, maybe it was already said prior.’
But is the Wireless SSID on the 2.Ghz/5 Ghz router set to broadcast the network ID?
As a previous user mentioned also.
Making sure the phone is connected to 2.4ghz when you do the setup, and then you can switch the phone back to 5Ghz after the setup has been completed.
I
thanks again everyone. the problem is the cams. the new one i just got setup perfectly without changing anything on my phone or router, as it should be. i am going to keep playing around with the broken ones just to see if i can do anything. i will NOT be updating the firmware on the new cams.
Cool beans
Now the question is why those cams had problems, is there something bigger going on with the cams.
I didn’t install the update and my doorbell has stopped. Wyze updates are notorious for causing their cams to stop working. Then they take months to figure out the problem. I’ve gotten rid of all of my wyze products except the doorbell. That will go in the trash today.
I have only had 1 cam have problems since I started using Wyze products. It is a V3 Cam, where the memory card slot no longer works. I have 7 other cams (v2,v3, 2 OG’s) over the last 3-4 years, and have not had any problems with those.
The one thing I think everyone should keep in mind, when dealing with failed electronics. Is that the quality of the electric supplying a home, plays a HUGE factor in stability in electronics, and also the failure in electronics, and that sometime, a failure may have nothing to do with the electronics manufacturer, but has to do with the electric being supplied to ones home, or business ( business electricity is dirty, meaning not stable, compared to electric supplied to a home) and this are issues that can cause electronics to fail.
Just some thoughts
As the new Security Updates have been pushed since the .9 version, most of the cam models have been experiencing failed updates.
Note I say Failed Updates rather than Bad Firmware. The update process is failing, not the new Firmware versions. I have successfully updated all 16 of my V3 cams to every Beta Firmware and Production Firmware version releases since installing them oh so many moons ago. I have yet to experience a failed update or the need to flash a cam to recover it, on any model I own.
But, I do it one single cam at a time and I am running my IoT on a rock solid, 100% connectivity uptime, 4 node Mesh.
I have also gone thru the process of taking a recently updated V3 cam and flashing it back to each of the last multiple update versions and then flashing it back forward. The Flash Process also works and none failed. The Firmware is solid even though there may be some feature and functionality bugs that need fixed. But, they still boot and run.
The problem, IMO, is in the file transfer and install loosing integrity. The cam is getting incomplete package delivery and install. The cam can’t help but puke when the Smart bits in the logic are missing.
“”" As the new Security Updates have been pushed since the .9 version, most of the cam models have been experiencing failed updates.
Note I say Failed Updates rather than Bad Firmware. The update process is failing, not the new Firmware versions. “”“”"
Interesting…at the same time amazing or should I say concerning.
Could it be, that the network connections overall, are starved for bandwidth, (since many people have multiple devices on their networks (load levels) that is causing the wireless networks to sputter the updates, while the cameras or devices are expecting a quality/steady stream when updating…that may be cause many to experience the update issues?
I only have 1 bad cam, Cam works, but the microSD slot no longer works, but If my memory serves me, this happened around the same time I had updated the cam, ( not through downloading firmware to card and then updating, but straight through the app firmware update. )
That is my theory, but I don’t have any empirical data to prove it. I only have anecdotal experience and educated guesses.
It is also what led me to submit this Wishlist feature request: Progressive Bulk Firmware Updates
Something changed in the Security Updates pushed with .10 forward. That is when I started seeing all the notes:
It is also when all the reports of user update issues began to come in. If you also look at the notes under each update version, that is when we started seeing halts, gradual releases, pauses, and update issues.
The same has been reported on the V3Pro and the PanV3.
Totally agree with you on the Bulk Update issue, I am actually surprised Wyse allows multiple devices to receive updates at the same time on a network. Its a recipe for problems, as you mentioned…Since most user networks have everything from SmartTV, Game Consoles, phones, PC’s, Security Cameras, along with many other devices, adding to this list, is that many apps, on computers have their own automatic update processes, all at different times, with most users not even knowing all the stuff going on, on ones network in the background. Then add in mutiple Wyze devices being updated att eh same time, to me, this sets the stage for Update Sputtering/ Failures, or a host of other issues, and not just with Wyze devices. – In reality, we have lost total control of our own networks.
In regards to the firmware update, do they state any specifics on what has changed? I normally just read the quick notes they publish with the firmware releases which tends to be 1 or 2 lines on the changes made…and then they usually state " and other fixes addressed" or something to that nature…
When it comes to security… Never. This is by design. They probably don’t want the ne’er-do-wells to to have a map to the castle grounds. When it comes to feature additions and bug fixes, they don’t provide much detail, but it is usually listed.
I would think if there are a moderate amount of users experiencing issues with the latest firmware updates, that another Firmware update may be coming sooner, rather than later.
And would believe they wont provide much details, other than " other bug fixes, and updates included" in the firmware release text. 
For the V3, Production is all we have. There is no Beta beyond that in the pipe.
So based on what you have mentioned V3, and I would think older cams are falling off the production/development cliff.
Not surprised, as all device companies move forward, and then end up no longer developing code for the older devices, as it also it not cost efficient for a company.
Problem is, many users end up not knowing their devices fall off the development cliff, or security update cliff, and then it starts exposing user devices to the bad guys.
Routers and network switches are a good example
Companies tend to stop developing code updates for older models, and then the device/s become security risks for users/companies.
Tends to be about 5 years or so, before older devices fall of the update cliff, and then the devices start becoming a risk/liability.
V2 cams I would have to believe are nearing that point?
my 2 new cams setup properly, i got a bunch of old firmware updates from someone and will try to resuscitate the dead cams. problem is probably in the update procedure, maybe hiccoughs in the data stream even though everything else on network works fine. thank you all for your help and suggestions.
Great news
Hopefully the dead cams can be rescued !
Hope that work out for you
Best
I have tried an update and got a solid red light brick v3 cam.
Reset does not work.
I have a 32GB FAT32 formatted with the latest firmware bin on it. Upon powerup while holding the setup button, the camera enters flashing mode (violet light), however, it remains there indefinitely, and no power cycling or reset is possible. Upon power cycle, the solid red light persists.
Any ideas of possible actions to unbrick?
Thanks!