feat: Add support for PIN_USER_BTN_ANA on rak3401 companion usb and companion ble envs#2436
Merged
liamcottle merged 2 commits intoApr 30, 2026
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Add support for a physical button using the AIN1 pin (31) for the rak3401 companion radio usb/ble variant. This should now make the rak3401 with a screen act like the 4631 with a screen,
There was a bug in example/companion_radio/ui-new/UITask.cpp where an int declaration was missing in front of ev, preventing the firmware to build when the pin flag as set.