I have recently setup capsman. It seems to work perfectly until I reboot the cap and then the cap is never detected again.

I can resolve this by logging into the cap and disabling the Capsman feature and then renabling it. Then the cap is seen by Capsman and I can log on fine. However, we get some odd power outages and I dont want to have to manage this remote cap ( or all caps) this way. How can I resolve this ?

Here is my config output -

# jan/14/2018 12:52:27 by RouterOS 6.41
# software id = Q84A-JBH2
#
# model = RouterBOARD cAP 2n
# serial number = 654805306FAC
/interface wireless
# managed by CAPsMAN
# channel: 2412/20-Ce/gn(30dBm), SSID: Cap_upstairs, CAPsMAN forwarding
set [ find default-name=wlan1 ] mode=station-bridge ssid=Webbguest
/caps-man interface
add disabled=no l2mtu=1600 mac-address=E4:8D:8C:F5:A7:0F master-interface=\
none name=cap1 radio-mac=E4:8D:8C:F5:A7:0F
/caps-man security
add authentication-types=wpa-psk,wpa2-psk encryption=aes-ccm,tkip name=\
security1 passphrase=2866Mountview
/interface list
add name=WAN
add name=LAN
/interface wireless security-profiles
set [ find default=yes ] authentication-types=wpa-psk,wpa2-psk group-ciphers=\
tkip,aes-ccm mode=dynamic-keys supplicant-identity=MikroTik \
unicast-ciphers=tkip,aes-ccm wpa-pre-shared-key=justforfun2011 \
wpa2-pre-shared-key=justforfun2011
/ip hotspot profile
set [ find default=yes ] html-directory=flash/hotspot
/caps-man manager
set enabled=yes
/interface bridge port
add bridge=cap1 interface=wlan1
add interface=ether1
/ip neighbor discovery-settings
set discover-interface-list=!dynamic
/interface list member
add interface=wlan1 list=WAN
add interface=ether1 list=WAN
/interface wireless cap
#
set discovery-interfaces=ether1 enabled=yes interfaces=wlan1
/ip dhcp-client
add dhcp-options=hostname,clientid disabled=no interface=ether1
/ip dns
set servers=8.8.8.8
/ip route
add disabled=yes distance=1 gateway=192.168.88.10
/system clock
set time-zone-name=America/Vancouver
/system identity
set name=Cap1