wAP-AC loses a radio after CAP upgrade

I’m configuring a 20 AP CAPs-MAN system using wAP-AC

When I start each access point with button in CAPs mode, it is recognized by manager, the upgrade to required ROs is OK but the access point restarts (with new firmware) with only 2,4GHz radio managed by CAPsMAN (5GHz led turned off)
I have to repeat the button procedure to reinitialize both radios managed by system.

Am I wrong with something ?
Is this a (known) issue ?

Thanks

Just… I’m wondering if they will restart with a single radio at every further upgrade once all are installed :frowning:

You can enable them from the terminal, no need to press the reset button

/interface wireless cap
set bridge=bridgeLocal discovery-interfaces=ether1 enabled=yes interfaces=\
    wlan1,wlan2

Yes, it seems a simple workaround

But I don’t understand why after ugrade Wap-AC restarts in single radio mode rather than dual-radio as it was before…
CAP mode remains , so ?

Imagine a working environment; tomorrow I’ll go for Manager upgrade, consequentially (wanted or by power loss) all working AP upgrade themselves, reboot and place in single-radio
Should I re-enable each of them every time ???

I realized it is (perhaps) a version issue :

The out-of-the-box wAP-ac come with 6.35.4 ROs

Disconnected from Manager (or auto-upgrade disabled) , each time I set them in CAP mode by power-on button , they enable ONE RADIO ONLY (2.4GHz)

After upgrade to 6.38.5 they keep the one radio configuration by previous setup, but after a further power-on button CAP mode restart they come up with both radios enabled

Probably 6.38.5 has the startup CAP script to enable both radios that 6.35.4 hasn’t.

Can anyone confirm this ?