Hi,
by default you can turn on and off the LEDs at cAP ac by pressing "it", but after integrating cAP to CapsMan it not longer works.
How can I leave this much autonomy to the cAP that this continues to work?
Thank you!
Re: How to keep the "button" alive when cAP is controlled by CapsMan
What cap device are we talking about ?
Default it could be there is a script in place providing that function when the device is working standalone.
It could also be in caps mode, that little piece of config is not there.
So adding it again, might solve your problem.
Open terminal
/system default-configuration print file=anynameyouwish
Move file to your PC and open in txt editor.
Search for config handling that button.
Should be something with "system routerboard mode-button" or so (I think).
Add missing piece of config.
As reference:
on cAP AC it looks like this:
Default it could be there is a script in place providing that function when the device is working standalone.
It could also be in caps mode, that little piece of config is not there.
So adding it again, might solve your problem.
Open terminal
/system default-configuration print file=anynameyouwish
Move file to your PC and open in txt editor.
Search for config handling that button.
Should be something with "system routerboard mode-button" or so (I think).
Add missing piece of config.
As reference:
on cAP AC it looks like this:
Code: Select all
/system routerboard mode-button set enabled=yes
/system routerboard mode-button set on-event=dark-mode
/system script add name=dark-mode comment="defconf" source={
:if ([system leds settings get all-leds-off] = "never") do={
/system leds settings set all-leds-off=immediate
} else={
/system leds settings set all-leds-off=never
}
}Who is online
Users browsing this forum: No registered users and 4 guests