When a device is running WifiWave2 CAPsMAN, it cannot set its own wireless interfaces as CAPs. This is a known limitation, due to how the driver works, there is a “hidden” (system level) provision rule for local interfaces, which makes them incompatible with local CAPsMAN.
Though you can just pass the same configuration manually for local WifiWave2 interfaces, as you would via provisioning rules - just use “/interface/wifiwave2/ set wifiX configuration=X”, which could be argued that it is more simple to do, than configuring “/interface/wifiwave2/cap” and setting “configuration.manage=r” to capsman-or-local/capsman.
The end result is the same, as WifiWave2 CAP interfaces and regular WifiWave2 interfaces use the same exact system, it’s not divided into separate menus as original CAPsMAN and regular wireless was.
On a separate note, make sure you don’t set “configuration.manager=capsman”, in the configuration profile that you assign via provisioning rules, this setting should be set on CAP device "/interface/wifiwave2 set " itself, and must not be passed to CAP that has already joined CAPsMAN.