# Plugin Basics

**URL:** <https://discourse.beets.io/t/plugin-basics/803>\
**Category:** Help\
**Created:** [June 11, 2019, 7:27pm UTC](https://discourse.beets.io/t/plugin-basics/803 "2019-06-11T19:27:17Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![rascruggs](https://avatars.discourse-cdn.com/v4/letter/r/e19b73/32.png) [@rascruggs](https://discourse.beets.io/u/rascruggs)\
**Post date:** [June 11, 2019, 7:27pm UTC](https://discourse.beets.io/t/plugin-basics/803/1 "2019-06-11T19:27:17Z")

</div>

I’m really liking beets, but I need a little help getting thew plugs working.  
I’m on a raspberry pi  
Beet Version gives me:

beets version 1.4.9  
Python version 2.7.9  
plugins: chroma, missing

config.yaml is:  
directory: /mnt/usb/disk1/music  
library: /mnt/usb/disk1/beetsdb/musiclibrary.db

import:  
move: no  
copy: yes  
resume: yes  
from\_scratch: yes  
log: /mnt/usb/disk2/beetslog.txt

plugins: chroma missing

chroma:  
auto: y

missing:  
format: $albumartist - $album - $title  
count: yes  
total: no  
paths:  
default: /mnt/usb/disk1/music/$genre/$albumartist/$album/$track $title  
singleton: /mnt/usb/disk1/music/Non-Album/$artist - $title  
comp: /mnt/usb/disk1/music/$genre/$album/$track $title  
albumtype:soundtrack: /mnt/usb/disk1/music/Soundtracks/$album/$track $title

If I type: sudo beet missing -a  
I get:  
error: unknown command ‘missing’

Same with sudo beet fingerprint  
error: unknown command ‘fingerprint’

I’m sure I have something wrong. Just not sure what it is.

Thanks in advance for the remedial tutoring.

---

<div class="post-metadata">

**Author:** ![fortes](https://yyz1.discourse-cdn.com/flex029/user_avatar/discourse.beets.io/fortes/32/8_2.png) [@fortes](https://discourse.beets.io/u/fortes)\
**Post date:** [June 11, 2019, 8:31pm UTC](https://discourse.beets.io/t/plugin-basics/803/2 "2019-06-11T20:31:03Z")

</div>

Is there any reason you’re using `sudo` before your commands? Try calling without `sudo`.

Alternatively, try making your call something like:

```auto
beet -c /path/to/config.yaml missing

```

In order to make sure you’re picking up the `config.yaml`

---

<div class="post-metadata">

**Author:** ![adrian](https://yyz1.discourse-cdn.com/flex029/user_avatar/discourse.beets.io/adrian/32/4_2.png) [@adrian](https://discourse.beets.io/u/adrian)\
**Post date:** [June 11, 2019, 10:03pm UTC](https://discourse.beets.io/t/plugin-basics/803/3 "2019-06-11T22:03:22Z")

</div>

`beet version` is also a good way to check which plugins loaded, and `beet -v version` shows you where the configuration is being loaded from.

---

<div class="post-metadata">

**Author:** ![rascruggs](https://avatars.discourse-cdn.com/v4/letter/r/e19b73/32.png) [@rascruggs](https://discourse.beets.io/u/rascruggs)\
**Post date:** [June 11, 2019, 11:27pm UTC](https://discourse.beets.io/t/plugin-basics/803/4 "2019-06-11T23:27:47Z")

</div>

Thank you both.  
I’ve been using sudo because my linux skills aren’t that great, and I was trying to make it work easier…  
of course, it worked instantly when I didn’t use it. Now to chown my output directory!