- read mappings
- execute command line stuff
- get nfc-reader input
- get keyboard input
- threading
- logging
- get rid of dotenvy? - no, it's actually nice, to add environment variables from console
- get rid of crossterm?
- control spotify-player
- volume
- play tags
- control
- play random stuff
- nfc control
- keyboard input
- figure out deployment
- setup tmux
- figure out how to get keyboard input
- general control
- restart spotify player
- check network?
- shut down?
Used here to play the music.
Adjust default configuration via ~/.config/spotify-player/app.toml
, e.g. change
default name, volume or autoplay.
spotify_player get key user-playlists > data/spotify_playlists.json
spotify_player get key user-saved-albums > spotify_albums.json
spotify_player get key user-followed-artists > spotify_artists.json
- create the
nfc_mappings.json
andspotify_mappings.json
file following the example template files - fill the
nfc_mappings.json
with your nfc-tag-ids a. if ACR122u is used, following or similar commands can be used to get the nfc-ids
sudo modprobe -r pn533_usb
while true; nfc-poll | grep NFCID1 | sed 's/\(.*:\s\)\(.*\)\s\s/\2/' | xclip -selection clipboard; end
- fill the
spotify_mappings.json
with your desired album/artist/playlist and assign to the nfc-index - put the app on the respective device.
deprecated, use version below copy autostart to /etc
:
sudo cp scripts/juke-the-box.desktop /etc/xdg/autostart/juke-the-box.desktop
start the pi in headless and start and attach tmux in the login shell (to capture keyboard input):
if tmux list-session | grep nfc-jukebox; then
echo nfc-jukebox is running, not starting
else
echo nfc-jukebox not available, starting
~/workspace/nfc-jukebox/scripts/tmux-setup.sh
fi