alexa-pi/AlexaPi

Playback and recording LED not working/reacting thru GPIO

Open

#421 opened on Oct 11, 2018

View on GitHub
 (4 comments) (0 reactions) (0 assignees)Python (1,324 stars) (402 forks)batch import
help wantedmagic mirrorquestion

Description

Thank you for reporting an issue with AlexaPi.

Make sure you are running the latest version of AlexaPi, and look through issues before submitting.

Check out our Wiki, and make sure to look at Debugging, and Audio debugging in particular before filing an issue.

In order to help troubleshooting, be sure to include the following information:

Output of the audio debugging script.

Your OS (including version) where you are running AlexaPi: Raspbian Strech Linux raspberrypi 4.14.70-v7+

Your hardware platform and model you are running on: Raspberry Pi 3B+

Python release (python2 --version): Python 2.7.13

Description of problem: Please help on issue with GPIO, AlexaPi doesnt activate GPIO 24 or 25 for Playback or record feedback, I dont see LED coming ON. LED is working fine on GPIO 24 or 25 if I use a small python script to turn LED ON and OFF, However thru AlexaPi is not reacting for Playback or Recording. I have verified on config.yaml, GPIO PINS are 24 and 25 for Playback and Recording. Checked changing the GPIO PIN number too. Am I missing something?

Expected: LED to reach for Playback and Recording

Problem-relevant config.yaml entries: platforms:

common config for all platforms (if they support the options)

can be overriden in the the respective platform sections

common:

chip: # GPIO Pin with button connected button: XIO-P1 # GPIO Pin for the playback/activity light plb_light: XIO-P3 # GPIO Pin for the recording light rec_light: XIO-P5

raspberrypi: # GPIO Pin with button connected button: 18 # GPIO Pin for the playback/activity light plb_light: 24 # GPIO Pin for the recording light rec_light: 25

Contributor guide

Tech stack
python
Domain
backend
Issue type
bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
PythonRaspberry Pi GPIOYAML
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
40
Research direction
Investigate the GPIO handling code in the repository, likely in the main script or a dedicated module. Check for proper initialization of pins 24 and 25. Review the comments in the issue for any additional troubleshooting steps. Consider testing with a simple script to confirm hardware functionality.