"ishotjr" reported that his mag was originally set up with the auto config to use all the Leds built in and had the user control widget set to purple.
They later came back and saw two of the lights were on the first and third, but it should have been all of the lights still, Until the user rebooted into a clean slate.
And I can only guess that the status LED pixels were effectively still in a timer and not properly de initialised once the user took control of the LEDs.
The other potential issue is the single core nature of the s2 and whether that could have been PWM timing issue or something (like huzzah i2c vs pwm).
The other potential one is not properly publishing received messages and things like that Potentially the flow could have been interrupted there would have in theory relinquish control of the status Leds.
"ishotjr" reported that his mag was originally set up with the auto config to use all the Leds built in and had the user control widget set to purple.
They later came back and saw two of the lights were on the first and third, but it should have been all of the lights still, Until the user rebooted into a clean slate.
And I can only guess that the status LED pixels were effectively still in a timer and not properly de initialised once the user took control of the LEDs.
The other potential issue is the single core nature of the s2 and whether that could have been PWM timing issue or something (like huzzah i2c vs pwm).
The other potential one is not properly publishing received messages and things like that Potentially the flow could have been interrupted there would have in theory relinquish control of the status Leds.