@grzywek 

What is your DHCP IP pool? Make sure the DHCP pool has 10.0.0.17.

The "fixed IP" option here actually means DHCP reservation, so it's still related to the DHCP pool.

  @Somnus DHCP configuration is fine.

After rebooting the router and APs, DHCP did not work at all. None of the clients would get an IP assigned (DHCP range or fixed, no matter).

Then I changed the DHCP server to Disable, Save, Enable, Save and it started working.

So the thing is, I am almost certain that there is still something wrong with DHCP and the latest firmwares. I have NEVER had a problem with this basic functionality on my previous (other brand) devices.

I'm expecting TP-Link to look into this and release a fix, as at the moment I'm kinda scared to touch any settings or reboot devices (won't this work again?).

Thanks.

Dave

Hi, after upgrading ER605 to 2.1.1 the issue still exist.

Camera got DHCP assigned. After I clicked "Reconnect" it got the proper static IP assigned.

  @grzywek 

You seemed to be confused about how "static" versus DHCP works.  You can't use the Omada system to define a true static IP for a client device...period.  The only way to define a static IP address for ANY devices is directly on the device itself or in some cases via the platform used to managed it.  Individual client settings CANNOT be managed by the Omada system.  You can't assign a static IP address to a PC, camera, or anything else that's not an Omada device managed by the controller.  The thing you are trying to do in the GUI for that Tapo (or other client devices) is actually setting a DHCP reservation.  Yes, you are trying to make it such that the client device has an IP address doesn't change but that's not the same thing as a static IP.  That camera and pretty much any other out of the box client is doing DHCP.  Most IOT devices (like cameras) can't do static IP addressing period.  As another person stated, you must set the DHCP IP address reservation to an IP that is within your DHCP range.  If you didn't leave room for this in your DHCP range, you will need to expand that range and choose an IP address within that range.

@SingletrackMind 

I may be wrongly using terms "static IP" and "DHCP reservation" interchangeably, but it doesn't change the fact that it doesn't work.

My DHCP range is 10.0.0.200 - 10.0.0.254

Cameras have DHCP reservation enabled and IPs set to from range 10.0.0.10 - 10.0.0.20

And it happens (often during device reboots - either router reboot or camera reboot) that they get IP from DHCP range.

To me, it looks like the DHCP is already enabled but the "DHCP reservation module" not yet and when the device connects in this window, it gets IP from DHCP range and not from DHCP reservation list.

When I reconnect the camera, it gets the correct IP.

Currently, I feel scared of rebooting devices as it's totally unpredictable. Never had such an issue with other devices.

  @grzywek 

It absolutely DOES work.  I have quite a few DHCP reservations configured, all within my DHCP scope range, and all work 100%.  That's simply how DHCP and DHCP reservations work.  A DHCP server should only ever give out an IP that's within the defined scope range.

It sounds like you've just been "lucky" to find a bug in the DHCP server and reservation system allowing you to set a fixed IP (DHCP reservation in this context) that's outside of your DHCP scope range.  The router should NOT be giving out addresses outside that range, period.  I hear you that you are seeing some cases where the cameras ARE being allowed to get .10-.20 IPs but they shouldn't be.  The fact that they are is a bug, simple as that.  If you want them to get an IP address that truly doesn't change, assuming you can't manually connect to the camera itself and define a statid IP address/netmask/gateway, then you need to set the fixed IP to something within your DHCP scope range (or expland your scope down to .10.