Skip to content
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

Detect RFID Removal - Play only with RFID on reader #863

Closed
MalteHST opened this issue Mar 18, 2020 · 1 comment · Fixed by #869
Closed

Detect RFID Removal - Play only with RFID on reader #863

MalteHST opened this issue Mar 18, 2020 · 1 comment · Fixed by #869
Labels

Comments

@MalteHST
Copy link
Contributor

MalteHST commented Mar 18, 2020

Hello guys,

just installed the recent develop branch without Spotify on my PI zero with a PhatBeat attached and a fresh Buster Lite image.
So far I think everything works fine after I modified GPIO-buttons and disabled the rotary knob in the settings.
Before I installed the latest develop version my Jukebox ran with the Stop-on-removal feature by the hardware hack which is described here:
#62

Unfortunately I don´t exactly understand the new structure of gpio-buttons.py code. So I saw that @dertobes in the meatime made a pull to add the to the default code of gpio-buttons.py. But this doesn´t work with the new structure as he already mentioned in his pull request here: #667

So this is a request to anyone who is able to explain here or modify the code making the stop-on-removal feature usable again.

(The reason for this is that my kid should trigger the music by toy figures with an attached RFID chip and a metal plate on the bottom. The Jukebox has a small magnet in the centre of the RFID reader so that the figures find the right place by its own and keep in place.)

Hoping for some help. I could test the function anytime and give feedback here.

Best regards.

@MalteHST MalteHST added the bug label Mar 18, 2020
@s-martin s-martin linked a pull request Mar 21, 2020 that will close this issue
@MalteHST
Copy link
Contributor Author

Solved it on my own and made a pull request ( #869 ) for the solution. Never thought it is that easy. ;)
@UndIch have a look at the commit, if you are still having the same issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant