@Horus107 The range in the second screenshot should be what controls the pool. Have you tried forcing the devices in question to release their existing IPs and renew for one in the pool? Easiest to do so if the devices in questions are PCs. (If they are, I would also double check for a static IP mapping.)

  @NeilR_M Yes, I tried to renew:

$ dhclient -d -v wlan0

Listening on LPF/wlan0/dc:a6:32:d6:87:28
Sending on   LPF/wlan0/dc:a6:32:d6:87:28
Sending on   Socket/fallback
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 3
DHCPOFFER of 192.168.0.4 from 192.168.0.2
DHCPREQUEST for 192.168.0.4 on wlan0 to 255.255.255.255 port 67
DHCPACK of 192.168.0.4 from 192.168.0.2

.2 is the switch, .4 is not in the range set.

  @Horus107 On your LAN settings, what device is set as the DHCP server device? 

  @NeilR_M It's Gateway. Which is technically not correct, as the switch is not the gateway, but it is the only option:

also, in the VLAN overview, the switch is marked as DHCP server:

Best Thanks!

  @Horus107 I was able to test on a switch here in our office as well and confirmed this behavior. I'll be passing this along to my engineers to see if they can figure out a solution or if they can confirm that this feature does not exist. Thanks for your patience. 

  @Horus107 Thanks for the research! As I am using the cloud controller, I guess I just have to wait for it to be released someday?

  @Horus107 Yes, however, the cloud controller will automatically update for you once the firmware is fully released.