-
Notifications
You must be signed in to change notification settings - Fork 67
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
NB798 led issue on USB150 #203
Comments
Can you attach the /etc/board.json file? |
need to check if we have access to that led |
something may have changed when the mechanism for manipulating leds was moved to lua. leds worked as expected on 3.22.1.0. Here is the board.json file. |
My USB150 does exactly the same thing. Works as it should on 3.22.1.0, not on NB798. |
Ahhh. Could be the lua based linkled function
Thanks,
Darryl
… On Jan 18, 2022, at 6:02 PM, Andre Hansen ***@***.***> wrote:
My USB150 does exactly the same thing. Works as it should on 3.22.1.0, not on NB798.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you commented.
|
I'm sure. We changed how the LED light was determined in the lua code compared to the older perl code, simply pulling a specific led definition from the board.json info. It looks like this isn't going to work, or at least cause too many regressions, so I'm going to revert that code back to the original (which was just a copy of what Perl did). |
NB838 fixed this issue. USB150 link light now illuminates when linked. THX |
The GL.iNet USB-150 only has two leds. The bottom one indicates power, and the upper one should indicate when the USB150 is associated or meshed with other nodes. In my recent testing, the upper led remained unlit even when the unit was associated/meshed.
The text was updated successfully, but these errors were encountered: