Captain Ron,

The situation you are describing is almost always caused because another process is running that is controlling the board. So when you "turn off" the led's they are being turned on again by the process that is running in the background. For instance if you started a script from the command line then opened up the airport edit utility, they are both trying to control the LED's on their own. So I would suggest rebooting the RPI, then using the utility to turn on/off the LED's. Please report back to lets us know if this helps. - Mark

@markyharris I'm having this same problem. Any further guidance? I'm not sure how to determine if there is anything else running in the background. Thanks.

I'm sorry, I haven't seen this for any other reason than what was discussed above. Typical startup would be to boot the RPI, if autorun is on, the map should come on automatically. If not, then from the editor you can start the map. Then when ready, you can shut off the map from the editor. If you are starting the map from the cmd line, you may need to stop the map from the cmd line. Each source creates its own process. If you have more info you can share, please post it here and I'll be happy to try to help. Sorry for the hassles. - Mark

So I had to go to Map Functions and Turn Off Map and then the Next button would cycle through the LED's

Ah, that makes sense. They are 2 separate processes. And they can step on each other. So the map needs to be off. Good catch. - Mark