Bluetooth autoconnect

Quote from witokondoria

Maybe just a myself-reminder. but I have saved a gist with the udev rules needed for letting my LE box to autoswitch the output audio device on bluetooth connected device.

The outcome is:
BT connected -> pulse active (A2DP output)
BT connected -> alsa active (HDMI output)

Feel free to comment or suggest improvements.

What is the purpose of this? How the pulse and alsa can active together? Why the HDMI output when BT connected?

The purpose is to switch audio output to pulse/BT when a specific device (selected by MAC address) is connected.

Just to say I use this with audioprofilesswitcher, so instead of pointing to your bluetoothHandler.sh I use a couple of shell scripts to switch audio profiles.
eg as simple as

[code]
#!/bin/sh


/usr/bin/kodi-send --action="RunScript(script.audio.profiles,1)"

[/code]
It works great for me, many thanks for documenting it.

Quote from trogggy

Just to say I use this with audioprofilesswitcher, so instead of pointing to your bluetoothHandler.sh I use a couple of shell scripts to switch audio profiles.
eg as simple as

Code

[code]
#!/bin/sh


/usr/bin/kodi-send --action="RunScript(script.audio.profiles,1)"

[/code]
It works great for me, many thanks for documenting it.

Maybe this works better?

#!/bin/bash


PROFILE='1'


if [ $1 == "add" ]; then
  PROFILE='2'
fi


/usr/bin/kodi-send --action="RunScript(script.audio.profiles,"'$PROFILE'")"

Quote from Bloksel

Maybe this works better?

Bash

#!/bin/bash


PROFILE='1'


if [ $1 == "add" ]; then
  PROFILE='2'
fi


/usr/bin/kodi-send --action="RunScript(script.audio.profiles,"'$PROFILE'")"

Display More

I did think about combining, but I couldn't see an advantage. What am I missing?