diff --git a/docs/configuration/bluetooth.md b/docs/configuration/bluetooth.md
index 8e4bf12..48956f0 100644
--- a/docs/configuration/bluetooth.md
+++ b/docs/configuration/bluetooth.md
@@ -12,6 +12,22 @@ Then restart the qube. From now on you should have a tray icon and be ready to c
 
 In the picture above I had a sys-net combined to use USB devices too. The procedure stays the same.
 
+Note: if you're using a separate sys-usb, and need to attach your bluetooth module to a AudioVM or MediaVM, 'blueman-manager' won't run without a recognized adapter from 'blueman-applet'. Once you attach, you can run 'blueman-manager' and with a script like the below in your AppVM's `rc.local` auto-connect to your preffered device:
+
+```
+address="XX:XX:XX:XX:XX:XX"
+
+while (sleep 1)
+do
+connected=`sudo hidd --show` > /dev/null
+if [[ ! $connected =~ .*${address}.* ]] ; then
+sudo hidd --connect ${address} > /dev/null 2>&1
+fi
+done
+
+```
+The loop should be the last thing in rc.local or appended with `&`. This is a simple solution. (Something more robust would require extra work with `udev` perhaps.) 
+
 ## AudioVM
 
 For the most secure scenario, one should be running an AudioVM rather than rely on having PulseAudio in dom0. The creation of such a VM is beyond the scope of this guide.