-
Notifications
You must be signed in to change notification settings - Fork 401
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
Feature/configureable gpio buttons #906
Feature/configureable gpio buttons #906
Conversation
Would this implementation replace the existing gpio-buttons.py file completely? If yes, then we should think about how we roll this out. One idea could be to leave like it is for 2.0 and maybe provide a howto how interested users could use it and migrate their installation. For 3.0 we could then make it the default implementation, but then we should provide a (automatic) migration of existing settings. |
This is only a check for this component. but probably a good idea to somehow define what is required for automatic testing of components... |
damn i didn't wanted to create confligting files... made something wrong when rebasing /merging develop (I am not used to the github fork workflow...) |
79589e2
to
63d39f6
Compare
Hi
I had a little bit of time to include two simple LEDs in the new gpio_control class.
One which lights up as soon as the gpio_control is started(device=LED), the other one only when a connection to MPD/mopidy can be established (MPDStatusLED)
I am NOT yet checking on a regulary basis if the connection is still there but that would be the next step. Also included an example config but the pins should probably be updated to correspond to the right pins....
( I also did a minor refactoring and moved the VolumeControl class)