@Pksparks Could you provide more information.  Specifically, is the management VLAN the Native Network (untagged) for the link between switch and AP?  Does the management SSID in WLAN Settings have the VLAN check box marked and a VLAN number placed in? 

  @JoeSea  to be short, on all your questions it is a yes.

and i am not to annoyed by it, if it is not possible, i even think it is a good security feature.

so i can also manage via tp link cloud.

so  i tried all settings, but as soon as i change away from managment vlan 1, my tablet gets good wifi on that ssid,and an ip adres.

  @KJK  thanks for the reply and testing. When i have time, i will try again. I guess i did something wrong in a setting.

i will try first in changing working vlan ssid into management ssid.

i let you know, but can take some time as of the time of year.

  @Pksparks Hi, I had to be away a couple of days.

What I've learned under Omada is, the SSID that is associated with the wired native network cannot have the VLAN option active.  To elaborate, in Omada the data on the native network on a switch port (regardless of VLAN number) has no VLAN information when sent out of the port.  When the AP receives the untagged packet, the AP does not know to assign a VLAN to the packet.  So the SSID that is intended for the untagged network cannot have a VLAN option on, since the AP doesn't see a VLAN with that number from the switch.  Going the other way, the AP will apply the VLAN tag, send it to the switch, and the switch will understand it belongs to the correct VLAN, since Omada does incorporate protection for double tagged packets.

Two solutions I would suggest.  Disable the VLAN option for the SSID that is to be connected to the native network.  Or have all SSIDs on a VLAN that is not the native untagged network.

I have had a change request in for a couple of months to add tagging for the switch port native network, since TPLink switches in standalone can tag outgoing packets for the native network.