This is great! Running Merlin with YazFi, and this is helpful! Thanks!
My Asus router glitches in the guest networks when swapping between settings any combination of WPA2 <~> mixed mode <~> WPA3. Doing so will result in unpredictable wonky behavior; as if only half each protocol working sort of a broken WPA2.5beta mode. I thought the Wyze OG supported WPA3 because of this. You can read about how it left me looking like an idiot here:
—————————————————————
The following worked for me, it may also work for your Asus tuf AX3000v2:
Make a fresh new guest network, new SSID, new everything, set it to WPA3, press apply. Wait for soft reboot to finish, then do a hard reboot (manually turn off router/unplug, wait 30+ seconds, turn back on, wait for lights to stabilize. Connect Wyze cam v4.
1. Factory reset the WyzeCam right before attempting the connection.
2. Temporarily set guest settings [Client isolation-NO] [Internet access-YES] [Access to Intranet-YES] you can change these if desired afterwards if success is achieved.
3. Connect phone onto that new WPA3 guest network and verify internet is working, and etc.
4. Phone bluetooth-ON, Wyze App requested permissions all-ON (Temporarily)
My v4 (and all my Wyze cams) connect fine with Intranet access disabled (which also enables client isolation). I have not tried them with WPA3 though, but that should not matter.
With the way Asus handles guest networks (especially Guest Network 1, or all of them when you have their Pro firmware) a reboot after changing guest network settings is always a good idea.
When setting mine up I was surprised that it worked with intranet access disabled (which also enables client isolation so two devices on guest can’t talk to each other). But the way the asus does it, certain things do “slip through”. It mostly blocks the return traffic and broadcasts so it ends up being enough to work for the setup process.
This is on Guest Network 2 or 3 though, it probably would only work on Guest 1 if both devices are in the same band since each band gets a different VLAN and subnet.
If using Guest 1, disabling and enabling intranet access actually makes a ton of changes on the backend, so be sure to reboot the router after doing each one if anyone tries that. Still a good idea with 2 and 3 but from what I’ve seen, not as critical there. I actually haven’t tried these cams on an Asus Guest 1, so not sure how it would impact the setup process. Mine are on a totally segmented wifi AP which eventually comes into the Asus on a dedicated VLAN through a firewall.
I’ve already tried every setting, but it still doesn’t work, so I’m giving up. I read that it’s better to set up a stable WPA2 on the guest network with a 62-character special password because it’s unhackable. It’s a much better combination than using WPA3 on the local network.
There really isn’t a huge benefit to WPA3 regardless, especially if you also have WPA2 running alongside it.
WPA2 can get deauth attacked, no matter how long the password is. It is also crackable, again no matter how long the password is. The likelihood that anyone in your area is doing that sort of thing is low. There is no longer a such thing as “unhackable” on WPA2.
You can’t believe everything you read places, there are many sources of information out there, some better than others.
You could get it working, but I think you’re trying to do too many things at once based on stuff you’re reading at various places and just getting confused. In reality, until all your devices support WPA3, there isn’t a big urgency to implement it.
I’ll wait a bit until someone finds a solution because I haven’t figured out why it doesn’t work for me.
One thing is certain: access to the internal network is not required because WPA2 connects just fine, even without internal network. Asus is restricting something that prevents it from working only on the guest network, but I don’t know what it is.
Not sure if it is relevant but just noticed no WiFi5 baseband?
@Lenovomen if your main 2.4g network is WPA3 and devices are working fine on that. Try connecting the camera to that. If it’s still doesn’t then something went wrong with that camera since Nov 2024. If it was mounted outside, a defective water seal from factory combined with the elements could condensation and corrosion on the insides. Even though it looks great externally.
Other than every thing covered already in this thread.. I’m all out of ideas.
Well as others mentioned, give it a shot on your main network just to see.
It may be an asus bug with mixing WPA2 on one wireless network and WPA3 on another, since they technically use the same wifi radio and chip. It should be able to handle it, but could be a firmware problem.
