Hi,
what is the best practice to configure capsman (new wifi in 7.13) to distribute correctly (and then maintain) the frequency/channel for each managed AP? If After rebooting router with capsman, some APs are ending up on the same channel, and this I would like to prevent. Ideally to be able to scan background and visibility to each other AP and then automatically decide what channel to use.
Thank you!
Kaspik
If you want to keep automatic channel assignment, then you have to force CAPs to rescan at random times. When the whole system starts, all CAPs do the scanning at the same time and none are transmitting, so they likely end up selecting same channel. And no, channel selection is not CAPsMAN function, it’s done autonomously by CAP (out of capsman-provisioned list of allowed channels).
Or you can create different channel profiles and provision CAPs with big coverage overlap with different channel profiles. This means more work when configuring the whole system, but also means lower probability of adjacent CAPs ending up on same channel.
Manually config? Where is the automation, need some AI in this sprectrum business!!
Oh, you’ve got AI in your network already … Anav Intelligence 
The rest of us have different acronyms (@OP has KI, I’ve got MI, etc.).
“force CAPs to rescan at random times” - do you have a script example? 
Preferably to do the scan at random time after reboot to mitigate this: “When the whole system starts, all CAPs do the scanning at the same time and none are transmitting, so they likely end up selecting same channel.”. I kinda wonder why the heck the capsman wont stick with the channel that was assigned last time.
It’s bugging me, because everyone else has to have the same issue and Mikrotik does not ship any built-in feature to mitigate this?
Thank you!
Currently I don’t have any live caps-man installation, so writing from my memory. For sure you can run a script on AP which disables communication with capsman and enables it again (after a few seconds). In good ole days lost connectivity between cap and capsman meant pause in radio operation and reprovisioning (after connectivity resumes).
Another possibility might be to disable cap’s interface (as presented on capsman) and enable it again (after a few seconds) … but do check if radio does the proper channel scan after that.
If the later possibility works, then it would be the preferred one for me as it allows to do the rescan trick from one central device.
As I wrote: channel selection is autonomously done by caps … I guess that “setting preferred channel” from capsman could be done, but that’s a new functionality and I wish you good luck when persuading MT devs that this feature is worth their attention.