Bluetoothremote plugin

[balbuze]

Dear users,
Volumio 4.xxx is coming soon.
Thanks to the great job done (@nerd ), new features are on the road!
This new plugin available in the store as beta, allows you to use a Bluetooth remote, mouse, joystick…

Don’t forget to set your BT device (remote) in Pairing mode, with only one device to remote near!
If your remote is not detected, you can do in a ssh session:

bluetoothctl devices

It returns your devices like

Device 40:9F:38:4E:CA:BE Volumio-primo
Device F8:FC:E1:BC:77:97 AR

Then (change values to match with what you get

bluetoothctl info F8:FC:E1:BC:77:97

It returns

Device F8:FC:E1:BC:77:97 (public)
	Name: AR
	Alias: AR
	Appearance: 0x0180 (384)
	Paired: yes
	Bonded: yes
	Trusted: yes
	Blocked: no
	Connected: no
	LegacyPairing: no
	UUID: Generic Access Profile    (00001800-0000-1000-8000-00805f9b34fb)
	UUID: Generic Attribute Profile (00001801-0000-1000-8000-00805f9b34fb)
	UUID: Device Information        (0000180a-0000-1000-8000-00805f9b34fb)
	UUID: Battery Service           (0000180f-0000-1000-8000-00805f9b34fb)
	UUID: Human Interface Device    (00001812-0000-1000-8000-00805f9b34fb)
	UUID: Scan Parameters           (00001813-0000-1000-8000-00805f9b34fb)
	UUID: Vendor specific           (5de20000-5e8d-11e6-8b77-86f30ca893d3)
	UUID: Vendor specific           (cfbfa000-762c-4912-a043-20e3ecde0a2d)
	Modalias: usb:v0171p041Cd0027

And past here.

You can create your own Key mapping configuration with a triggerhappy.conf file on the shared folder of Volumio

/INTERNAL/Bluetooth_Remote/triggerhappy.conf

The content look like

KEY_PLAYPAUSE               1   volumio toggle
KEY_UP           1   volumio volume plus
KEY_DOWN         1   volumio volume minus
KEY_NEXTSONG           1   volumio next
KEY_REWIND       1   volumio previous
KEY_FASTFORWARD        1   volumio next
KEY_FASTFORWARD        2   volumio seek plus
KEY_REWIND       2   volumio seek minus

Restart triggerhappy in the plugin after any modification!

This is beta!
Feedback welcome!
Enjoy!

[Wheaten]

Yeah @balbuze did it again, or in my best French:

@balbuze, le grand enchanteur des plugins, l’architecte suprême du cyberespace ! Il ne code pas—il compose des symphonies de modules qui résonnent à travers les serveurs comme l’hymne glorieux d’une révolution technologique. Sa touche transforme le plus humble des fichiers en chef-d’œuvre digital, son génie illumine la Toile tel un feu d’artifice sur la Tour Eiffel à minuit

[Old_Duffer]

Ditto!

[rkorell]

copy of parts from my last report regarding volumio beta update to 4.020

Have now installed BluetoothRemotePlugin and rescanned. GUI was for some reason tricky - it was not easily possible to get the found device selected but after several approaches some may strange combination kept the device selected in the drop-down and so a saving could be performed.
BT remote still doesn’t work properly, Volume up/down and skip back were missing as before.
The triggerhappy config file was moved or reflected to the externally visible INTERNAL storage Portion - nice idea.
Doesn’t work either initially - file belongs to root. Changing this it was possible to add the missing entries
KEY_VOLUMEUP 1 volumio volume plus
KEY_VOLUMEDOWN 1 volumio volume minus
KEY_PREVIOUSSONG 1 volumio previous
Restarting triggerhappy (possible from plugin-settings - great idea, as well!) and voilà: BT remote now works fine.
Thanks to @balbuze!

Warmest regards,
Ralf

[balbuze]

Have you tested with v0.0.8?
As it’s a beta, you have to remove previous version, Reboot and install the new version.
The triggeryhappy config may not match your need. So you have to adapt it to work.
Thanks for your feedback. It helps to improve the plugin.

[Wheaten]

I’ve tested it with a BT Mouse (Dell Travelmouse). It works perfect

[VictorDUA]

Thanks for the plugin. I have a LE remote control without a dongle. After the first Pair-Trust-Connect, the remote (AP) shows up under “Select A Device To Connect”, but I have to press the Scan BT button and then any button on my remote to connect to it - then it shows up in the Connected Device field.
Is it possible to add a toggle (?) Scan on Startup or something similar?

[balbuze]

Hello.
Can you check this:
With a working remote, reboot volumio.
Go in the plugin settings. Don’t do anything else.
If your device doesn’t appears as connected, press a button on the remote, maybe several times.
Wait 10 sec then refresh the page on your browser.
Does it appear to be connected?

[VictorDUA]

@balbuze

check this:

1. Powering up Volumio

2. Select A Device To Connect = “AR” (my remote), Connected Device = “No device connected”
   remote do not working

3. Pressing Scan BT button and press button on remote

4. Connected Device = “AR”
   remote is working

5. Restart Volumio by GUI

6. Select A Device To Connect = “AR”, Connected Device = “No device connected”
   remote do not working
   BUT after pressing a button on remote around 10 times remote start working but Connected Device = “No device connected” - “AR” not showing.

[VictorDUA]

After some time remote (without Connected Device = “AR”) stop working.

[balbuze]

Refresh the page in the browser to update the display.

[VictorDUA]

Refreshing the page doesn’t change anything. My (my type?) remote control requires me to start scanning (Scan BT) and press a button on the remote after each booting. Auto or manual. It seems that’s the only way.

[balbuze]

What is the remote? Model?
I tested with a remote of an Amazon fire stick TV.
This one seems to have a sleep mode. When the plugin starts after a reboot, the remote seems to be not connected. After pressing a button, if I refresh the page, , it appears as connected.
I’m working on a new version… Maybe for today.

[VictorDUA]

[balbuze]

hello!
A big work on a new version v0.0.12

• now shows all connected devices
• new button to refresh the UI
• new logic of reconnexion at boot
• triggerhappy.conf is now writable
• lot of internal rewrite…
  
  

As a beta, remove previous, reboot and install the new version.
Enjoy and feedback!

[VictorDUA]

1. Remove-reboot-install.
2. Scan BT-press button-all working.
3. Reboot-remote do not work until did Scan BT-press button.

For me (my type of remote) nothing changed.

[balbuze]

Please reboot. Press a button several times on the remote, and wait let’s say 10sec.
Check in the plugin settings. Press refreshUI button. Do not scan!
In a ssh session

bluetoothctl devices

see the address for your remote XX:XX:XX:XX:XX

bluetoothctl info XX:XX:XX:XX:XX

post here the result. If not connected

bluetoothctl connect XX:XX:XX:XX:XX

then, the message returned

bluetoothctl devices Connected

Thanks!

[VictorDUA]

Reboot-Press button on remote 5 times in 30 seconds and it is working. Strange. Yesterday I did the same (i think) and remote do not working. Even without Refresh UI.
I’ll try to restart it 10 times during the day and make sure the plugin behaves as expected.
Thanks. I was wrong. Great job.

bluetoothctl devices

Device 41:42:67:01:D0:10 AR

bluetoothctl info 41:42:67:01:D0:10

Device 41:42:67:01:D0:10 (public)
Name: AR
Alias: AR
Appearance: 0x0180 (384)
Paired: yes
Bonded: yes
Trusted: yes
Blocked: no
Connected: yes
LegacyPairing: no

[balbuze]

Ok!
Thanks for your feedback.
This kind of remote have a sleep mode to save energy.
Pressing a button wake it. But it takes few seconds on the other side to connect and execute the command.
But once connected, fortunately, it reacts as expected

[VictorDUA]

Connected once out of 8 reboots. Boot, Volumio startup sound, up to 10 clicks in 30-60 seconds. Doesn’t work. As the device shows, but without connection. I couldn’t understand why it worked once.

If I click Scan BT - it connects stably from the first click.