-
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
Board Activity LED #15
Comments
It is built into the firmware. The Zigbee firmware has support for it, the Multi-PAN as well as the OpenThread RCP firmware do not have support at this point (or rather, I did not find something built-in, probably needs custom code). |
GIPO control is implanted in GSDK 4.3.0.0 but is not in stable / production status and need being implanted and tested before if someone is interested doing the code work. |
Yes noticed that in the release notes
|
So this is meant for a host component to control a LED. Not sure if I wonder why can't the Multi-PAN RCP firmware not control the LED directly, on RF activity? IMHO, since we only have a single LED, this would be the best and easiest way to control the LED. Otherwise OpenThread/Zigbeed would need to share a single LED which might be problematic even. |
There hasn't been any activity on this issue recently, so we clean up some of the older and inactive issues. |
not stale |
The activity LED is stubbed out in
|
One interesting function but its not what you is looking for:
|
FYI, Zigbee EmberZNet firmware shipping with ITead's Sonoff ZBDongle-E expose control for brightness of the indicator light LED: https://www.zigbee2mqtt.io/devices/ZBDongle-E.html#light-indicator-level-numeric Light indicator level (numeric)Brightness of the indicator light. |
Only their router firmware exposes the led. That is somewhat different as its just a standard Zigbee cluster. |
How does the activity LED work on the Yellow? Is there some code running on the Yellow that drives this LED? or is it built into firmware to display activity?
The text was updated successfully, but these errors were encountered: