@GaRv3 

yes if it doesn't work I don't understand anything. if port 4 on the router has all vlan enabled, and switch port 2 has profile all then you should be able to take out iot on any port on the switch

  @MR.S 

Yes, this is exactly what I don't understand.

  @MR.S 

If I change the port 10 of the switch to "IoT" and reconnect the device, it gets the correct fixed IP of the "IoT" VLAN.

As soon as I change it back to "All", the device cannot be reached any longer and after reconnecting it, it gets an IP in the "Default" VLAN.

  @GaRv3 

Port 10 is well connected to a TL-SG108E, it is an easy managed old switch, if you want to have vlan on it you have to configure it on the switch. I recommend that you throw that switch away and buy an omada switch

  @MR.S 

Yes, I know. The ordered SG3210X-M2 will arrive tomorrow.

But this will not resolve the issue because what I described im my previous post happened without the TL-SG108E connected. When I did what I described, the device was directly connected to port 10 of the SG3428X-M2.

  @MR.S 

I found that no client that is connected by cable to a switch port which is set to profile "All" can be configured to use an IP of the "IoT" network.

Clients connected wirelessly to an EAP that is connected to a switch at a port which is set to "All" can be assigned an IP of the "iOT" network

To be precise: The configuration is possible in both cases, but has no effect for wired devices - even after reconnect / power cycle.

  @GaRv3 

Ok, I don't know what it could be then, have you tried connecting a PC directly to the IoT port on the switch?

  @MR.S 

The port does not matter - and it happens on other switches to.

If I set a port to "IoT", all clients will be added to the "IoT" VLAN.

If I set it to "All", all clients will be added to the "Default" VLAN. No matter what I set in the static IP config.

Clients connected to EAPs can be set to any VLAN successfully.