ExtremeCloudIQ Connect - Permanently disable LED

[jepla]

So I have an ExtremeCloudIQ account for a small environment, next to a larger Pilot environment. I know the setting to turn off the LED is unavailable in the ExtremeCloudIQ Connect portal, but it can be done over SSH. Point is, after an update from the portal the LED turns on again, overruling the SSH commands. Now first of all, I think it is kind of remarkable LEDs can't be controlled on a Connect account, since it would not be a feature corporations would move to the Pilot version for, but whatever. But is there a way to store this setting permanently so any updates from the portal would not turn these LEDs back on?

[w1f1n00b]

or anytime the power goes out.

[w1f1n00b]

I developed a workaround.

supplemental cli for connect LED

[tobias_s_jonsso]

I really would have loved being able to have Supplemental CLI in Connect.

My self have 3 settings I have to add on the terminal every time i change config.

[jepla]

So, is anyone aware of a way to make these SSH commands permanent? As stated before, they keep being overwritten on every policy update from the ExtremeCloudIQ portal.

I was thinking of a command to store settings permanently in SSH since the Extreme thinks turning off a LED requires a paid license...