A brand new Wyze Cam v4 simply ignores a reserved IP address within our router. The address is not only reserved but static and in DHCP reservations. It’s simply not possible to override the Wyze Cam v4 IP address and manually choose from the available dynamic pool of available IP’s not in use. Even after connecting to a different WiFi SSID, the camera’s IP address insists on occupying the same IP as a reserved NAS drive. Net result: this camera can never connect to the WiFi as well as the firmware update does not occur. Error Code -3005. Wyze needs to allow a manual override of an IP address to resolve this issue. Unfortunately the camera is useless. Support had no answers other than to replace the device. Oddly the camera ‘did’ understand the Octet from the router such as 192.x.x._ _ _ _ just could not acquire a different IP on the last 3 digits. Bad design? No other devices has ever had this issue as reserves are always ignored.
The camera doesn’t “ignore” DHCP responses, it would not get any IP if it did.
Either the cam got that IP previously and you need to power cycle it to force it to get the new one (bouncing wifi can do it too) or your DHCP server is configured wrong and is handing back the wrong IP.
All else fails, factory reset, but I can’t see why that would be needed, I’ve changed mine from the random IP to a reserved IP on a few occasions and as long as the IP reserved for it isn’t in use, and the MAC is correct, rebooting the cam is all that is needed to get the new IP.
It is important to note that if the IP you’ve “reserved” for the cam already has a DHCP lease in your router for some other device, it won’t work. Rebooting the router is enough to clear out that old lease typically.
You should also ensure your DHCP range in the router does not cover any static IPs you have assigned on the network. Statics that you’ve configured directly on a device should come from a range outside of the DHCP scope (though in most cases it makes more sense to use DHCP reservations than true static IPs).
Reading back through your message I’m not really sure I understand. You’ve said you’ve set a static AND reserved an IP for the camera. You can’t set a static on the camera, nor does the camera “know” what IPs you’ve reserved. All it knows/cares about is the IP that your router tells it to use. So if it is getting the wrong one, your router (DHCP server) is to blame. Sounds like some address planning and cleanup of your router settings might be necessary.
It was power cycled, reset, deleted Device and so on including a factory reset with support on the line to verify the Factory reset was completed. I sent support a screen capture of the Device ID info which included the x.x.x.166 IP it “insisted” on using. They confirmed, you cannot change the IP address of the camera. Think about it, why would they give up and send a new replacement camera? Case in point. I’m a Sonicwall reseller and have setup hundreds of routers for clients since 1997. No, the DHCP range doesn’t include any reserved IP address in the Dynamic range, that wouldn’t make sense. I said I reserved a static IP on the NAS itself thus it doesn’t use DHCP. This reserve also has the MAC address of the NAS drive. No IP was reserved for the camera - that’s not possible as we assume they dynamically would request an IP from the DHCP server, you may have misread or misunderstood. The camera can’t find another IP address is the end result but the other 3 Wyze cameras had no issue they grabbed what was available in the DHCP pool, it’s just this one which ignores the reserves. Go figure.
Camera isn’t insisting on using anything. It can only be told what to use. It has no idea what your network is without DHCP telling it.
Because they couldn’t figure it out and that’s the easiest way to get you off the phone. They aren’t very skilled technically. They’re there to read off a screen and when it doesn’t fit one of those things, they send a replacement.
Which may or may not make you knowledgeable about DHCP and IP networking. Sonicwall is a security appliance, not typically going to be acting as a DHCP server. I’ve been a network engineer and architect for 25 years. I can help you figure it out if you want.
Actually, that’s the only way it would make sense. DHCP reservations must be in the DHCP scope range. If they’re not, that’s at least part of your problem (most routers prevent you from doing it, but not all). What you want to keep out of that range is manually assigned static IPs on devices that are not using DHCP, although a properly functioning DHCP server will still avoid those IPs if they are pingable, still best to isolate them.
Where did you reserve it? If you put a static IP on the NAS, the only “reserving” you can do is to ensure your DHCP range does not include that IP.
Again, where? If you’re using a static IP configured directly on the NAS, there is no reservation in your DHCP server nor MAC address. Your DHCP server doesn’t know anything about the NAS if it is a static IP.
OK I’m totally confused, you’ve said several times you had a manual DHCP reservation for the camera, but I guess you meant you have a reserved IP for your NAS and the camera is picking that IP? That means the DHCP server considers that IP available and is handing it out. It will continue handing it out as long as the lease exists in either the camera or the router.
Of course is is, that’s the entire point of DHCP reservations.
The camera does not “look” for IPs. It takes the IP the DHCP server gives it. That’s it.
Again, it has no idea what you’ve reserved. It has no way to. Your DHCP server keeps track of that.
If you get your DHCP/IP addressing fixed, your cam will work fine and you won’t have these issues in the future.
Assuming you don’t have a massive number of devices, below is a pretty reasonable layout
192.168.x.1 - Router
192.168.x.2 through 49 - static IPs or other purposes
192.168.x.50 through 199 - your DHCP range. All of your manual DHCP reservations (cams, whatever) should be in this range, and the rest will be handed out to other devices that don’t have reserved IPs.
192.168.x.200-254 - I like to leave this aside for potential future use or other static devices, but you can certainly combine this with the DHCP range.
Obviously you can adjust this as you see fit as long as the ranges are continuous and do not overlap.
Your NAS, if you are truly assigning a static IP on the NAS itself, should be in the 2 through 49 range. But in reality, I don’t know why you wouldn’t just do a manual DHCP assignment for that, like .50 or whatever.
Your cams, since they can’t be static, should have DHCP reservations in the 50 through 199 range. 50 through 55 if you want, BUT make sure you only pick IPs that don’t already have a lease for some other device (you can reboot the router while said device is off, which will make it lose its lease and get a different IP next time). Or if you don’t care what random IP the cams get, no DHCP reservations needed, DHCP gives them whatever is available in that range.
Get things set up correctly and you’ll be up and running. I think you’ve confused static IPs, manual DHCP reservations, and traditional dynamic DHCP and it is causing you issues.
Have you successfully done this procedure on a V4 or any other Wyze camera? If not, you are probably doing something wrong. Every router manufacturer has its own procedures for doing things. Why not state your router’s model number and maybe someone here has done that before?
Nothing in the way a Wyze camera is set up reminds me of how to tell it what a local IP it’s going to use. If you want a fixed lan IP, what usually happens in this case is to let the camera acquire a dynamic IP and then tell the router to reserve that particular IP for that particular device.
Why do you need a static lan IP anyway? It’s not really necessary.
Another thought, are you 100% certain you don’t have a second DHCP server on your network? Many NAS boxes can run a router and/or DHCP server. A second DHCP server could also explain what you’re seeing.
thanks for all the help. Ultimately I setup a VLAN off an Access point with a 172.x.x.x octet and connected all Wyze devices to this VLAN. Issue solved.
You may have just postponed another issue with some other device on that main network at some point, probably still makes sense to figure out what is set up wrong, but whatever works.
Having these cams on an isolated VLAN (preferably with firewall or other security isolating it) is a good idea regardless. Your stream will go via wyze servers instead of direct to the phone but that hasn’t been an issue for me.
Once you complete the scan you’ll see why you want them on an isolated network.
If the second router is running DHCP, it isn’t just an AP, it is running at least some routing functions. Preferable to have one DHCP server for your entire network, as long as it is VLAN aware, it can safely cover all segments and you have a central place to manage your IPs and DNS, and a single spot to enforce all your security, boundaries, etc.
Though some do hang multiple routers off their main router to create that isolation, but then you need to go to each one and block access to your main LAN and other networks, it is kind of a messy solution.
Combine a sonicwall that has routing and DHCP/DNS ability (I’m assuming they have models with that, but not positive) with a VLAN aware switch and APs and you’ll have a nice little setup. Or use PFSense/OpnSense in place of sonicwall, same idea.
If it is set up as an AP, it doesn’t have its own DHCP server, so I’m assuming your sonicwall or main router is serving the DHCP for that segment.
Simply having different subnets won’t protect you (no matter how different they are), whatever router/firewall you have in place needs to also block access between those subnets. Should be easy enough to do on sonicwall or any other similar appliance.
It is actually a common occurrence for people to put a second router behind their first thinking that creates an isolated network with no access to their main LAN, but that’s not the case. That setup even defeats the “guest” network restrictions that many routers have. Your main LAN is now just another subnet on the internet as far as that second router is concerned, so unless you either block the access on that router (using firewall or a dummy static route to blackhole the traffic) or on the upstream router, it actually ends up being a lot less secure than people assume.
But it doesn’t sound like that’s what you have set up, if the TP Link is AP mode, then your upstream router is taking care of everything and you can block access in there.
OK, an AP (or router running in AP mode) is just a bridge, has no ability to hand out DHCP leases. Doesn’t really matter, if you’ve got it working, close enough.