In the unlikely event that you have an issue with sidekick, here are some tips

default patch hanging on loading

you should still be able to get back to the sidekick menu, but if you cannot for some reason, then reboot norns, and whilst it boots hold down button 1 (top left) this will prevent the 'default' patch loading, and bring you to the sidekick menu

loading any other patch, will now make it the default.

(if you don't want to load patches by default on startup see sidekick.json details)

log files

journalctl -u sidekick

restarting sidekick from cmd line

sudo systemctl restart sidekick

stopping sidekick from cmd line

sudo systemctl stopping sidekick

running sidekick manually

note: make sure you stop sidekick service first (see above)

cd ~/sidekick
/usr/local/sidekick/sidekick

sidekick not starting, or osc not working

sidekick listens by default udp port /3001 for osc you can check if sidekick is listening, or if another process has the 'grabbed' the port using

ps auxwww -q `fuser 3001/udp`

this tells you the details of the process (if any) using port 3001

Editing sidekick.json, wont boot

if you edit your sidekick.json file, and sidekick stops booting you can get back the original file by doing

cp /usr/local/sidekick/sidekick.json ~/sidekick

anything not covered here?

then post on the lines forum, on the topic Orac, Sidekick, Pure Data and SC for Norns

perhaps the community can help, I also check regularly - though I don't have much time, so I appreciate you checking this wiki for answers first.