Common scenario to implement STP/RSTP/MST on network switches is to enable is on all ports and configure access ports with portfast. This is also the recommendation within the configuration guide on the tp-link website: https://www.tp-link.com/us/configuration-guides/configuring_spanning_tree/?configurationId=18218#using_the_cli_2_2

However, within Omada one can enable STP/RSTP on the switch and subsequently on the ports using profiles or port overrides. There is however no option to enable portfast. I've checked the switch using the CLI, to check the switchport configuration, as maybe the choice was made to enable portfast on ports carrying only one untagged vlan (as these are typically access ports). However this was not the case.

It seems, portfast cannot be configured using Omada, and as STP/RSTP without portfast is known to cause issues on access ports (e.g. PXE boot or fast booting devices), the common best practice implementation of STP/RSTP is just not possible.

In addition, MST cannot be configured at all, I think that the strength of a sollution like Omada should be the easy implementation of complex network designs and MST is a great example of where Omada could have real added value.

Nit picking: The auto creation of non editable porfiles on VLAN creation is not helpfull. There are enough cases where VLANs are never used as a single untagged vlan on a port, and in addition, if the default configuration is not what you require, you need to create a new seperate profile for the same VLAN. The automatically created profiles (for each VLAN) should be editable or deletable (would not mind if they are even never created automatically). As now the omada profile page is cluttered with unused and unneeded default profiles.

Kind regards,

Jorg