Hi, anybody had any luck getting a fireTV Alexa remote control working with the Vero4k/4K+?
I can get the remote connected fine using the MyOSMC addon or direct from the command line using bluetoothctl, but none of the buttons respond inside Kodi.
I have a generic S905 box running LibreElec and the Amazon remote works fine on that, I just can’t get it working on my Vero4K+
Any ideas?
I think the Fire TV remote works with OSMC (I remember we added support for it a while ago). Is this a new version?
We may need to add an eventlircd map.
Sam
Umm… It’s the new one that comes with the fireTV 4K stick. It’s got the volume/mute buttons, I think the old one didn’t have these.
How would I go about creating my own eventlircd map?
Using evtest – but this has probably already been done for this remote.
Ok, so that really doesn’t help me 
I’ve run evtest and these are the available devices it finds:-
Available devices:
/dev/input/event0: gpio_keypad
/dev/input/event1: cec_input
/dev/input/event2: OSMC Remote Controller USB Keyboard Mouse
/dev/input/event3: OSMC Remote Controller USB Keyboard Mouse
/dev/input/event4: meson-ir
/dev/input/event5: eventlircd
/dev/input/event6: lircd
Testing number 2 gives output from the original OSMC remote but none of the others give any output from the Amazon remote.
Is the remote paired?
Sam
bluetoothctl says it is
osmc@osmc:/home$ bluetoothctl
[NEW] Controller 10:D0:7A:B2:6E:C1 osmc [default]
[NEW] Device B0:FC:0D:05:A7:C5 AR
[AR]# paired-devices
Device B0:FC:0D:05:A7:C5 AR
[AR]#If it is Bluetooth I believe you just need to do the mapping via keymap editor no need for evtest
Yep, but the problem is none of the button presses register. I can get keymap editor to the point where you are asked to press the new button however none of the buttons on the Amazon remote respond.
Under LibreElec the navigation/select and back buttons worked out of the box as soon as the remote was paired I just had to use Keymap editor for the rest and they all registered fine, but OSMC just doesn’t seem to see any of the button events.
Well I guess starting point is to compare logs between the two. Or if you have LibreElec running on a Pi maybe try OSMC on the Pi to see if it is a generic OSMC issue or just a Vero issue
I’ve checked LibreELEC’s eventlirc implementation.
It only has one Amazon Remote definition and we have the same evmap.
So I don’t think that’s the issue.
The evmap only remaps inputs.
The fact that evtest does not present it at all suggests a pairing issue to me.
Sam
I’m at a loss then, here’s my bluetoothctl session:-
osmc@osmc:~$ bluetoothctl
[bluetooth]# scan on
Discovery started
[CHG] Controller 10:D0:7A:B2:6E:C1 Discovering: yes
[CHG] Device 40:CB:C0:E2:20:2A RSSI: -56
[CHG] Device 0D:B1:69:10:B0:F5 RSSI: -57
[CHG] Device 6F:14:DB:69:90:D2 RSSI: -62
[CHG] Device 40:CB:C0:E2:20:2A RSSI: -43
[NEW] Device B0:FC:0D:05:A7:C5 AR
[CHG] Device 40:CB:C0:E2:20:2A RSSI: -58
[CHG] Device 40:CB:C0:E2:20:2A RSSI: -43
[bluetooth]# pair B0:FC:0D:05:A7:C5
Attempting to pair with B0:FC:0D:05:A7:C5
[CHG] Device B0:FC:0D:05:A7:C5 Connected: yes
[CHG] Device B0:FC:0D:05:A7:C5 ServicesResolved: yes
[CHG] Device B0:FC:0D:05:A7:C5 Paired: yes
Pairing successful
[AR]# trust B0:FC:0D:05:A7:C5
[CHG] Device B0:FC:0D:05:A7:C5 Trusted: yes
Changing B0:FC:0D:05:A7:C5 trust succeeded
[CHG] Device 40:CB:C0:E2:20:2A RSSI: -55
[AR]# info B0:FC:0D:05:A7:C5
Device B0:FC:0D:05:A7:C5
Name: AR
Alias: AR
Appearance: 0x0180
Paired: yes
Trusted: yes
Blocked: no
Connected: yes
LegacyPairing: no
UUID: Human Interface Device (00001812-0000-1000-8000-00805f9b34fb)
ManufacturerData Key: 0x0171
ManufacturerData Value: 0x04
ManufacturerData Value: 0x13
RSSI: -52
[AR]# scan off
As you can see bluetoothctl reports that the remote is paired, trusted and connected and correctly identifies it as a Human Interface Device.
Ok, finally got it working by updating bluez from 5.43 to 5.50 on my Vero, works perfectly now. Thanks guys.
can you explain how you did this?
Sure, from an ssh session run the following:-
wget http://www.kernel.org/pub/linux/bluetooth/bluez-5.50.tar.xz
tar xvf bluez-5.50.tar.xz
cd bluez-5.50
sudo apt-get install -y libusb-dev libdbus-1-dev libglib2.0-dev libudev-dev libical-dev libreadline-dev
sudo apt install build-essential
./configure
make
sudo make install
Then reboot your Vero. Pairing the remote is a bit strange, you need to use run bluetoothctl. Then put the Amazon remote into pairing mode then in bluetoothctl do the following:-
scan on
Put the Amazon remote into pairing mode by holding Home and Select until the orange light flashes in the top right corner of the remote. Look for the address of your Amazon remote it will be labeled as AR, if it’s not there type devices and press return and it should pop up.
Then do the following command replacing with your remotes address from above (bluetoothctl supports tab completion so you can type the first few characters of the address and then press tab to auto complete). After issuing each command wait for a response, don’t just go mad and type everything as fast as you can 
pair <address>
trust <address>
connect <address>
Now check if the remote works in kodi, if it doesn’t then do the following:-
disconnect <address>
Put the remote back in to pairing mode by holding Home and Select, then:-
connect <address>
Now it should work, then do:
scan off
exit
Here’s my complete bluetoothctl session for reference:-
osmc@osmc:~$ bluetoothctl
Agent registered
[bluetooth]# scan on
Discovery started
[CHG] Controller 10:D0:7A:B2:6E:C1 Discovering: yes
[NEW] Device C0:28:8D:DA:12:42 C0-28-8D-DA-12-42
[NEW] Device B0:FC:0D:05:A7:C5 AR
[CHG] Device 58:BC:5A:F3:18:D4 RSSI: -65
[CHG] Device 40:CB:C0:E2:20:2A RSSI: -57
[bluetooth]# devices
Device 0D:B1:69:10:B0:F5 0D-B1-69-10-B0-F5
Device 40:CB:C0:E2:20:2A 40-CB-C0-E2-20-2A
Device 58:BC:5A:F3:18:D4 58-BC-5A-F3-18-D4
Device C0:28:8D:DA:12:42 C0-28-8D-DA-12-42
Device B0:FC:0D:05:A7:C5 AR
[bluetooth]# pair B0:FC:0D:05:A7:C5
Attempting to pair with B0:FC:0D:05:A7:C5
[CHG] Device B0:FC:0D:05:A7:C5 Connected: yes
[CHG] Device B0:FC:0D:05:A7:C5 UUIDs: 00001800-0000-1000-8000-00805f9b34fb
[CHG] Device B0:FC:0D:05:A7:C5 UUIDs: 00001801-0000-1000-8000-00805f9b34fb
[CHG] Device B0:FC:0D:05:A7:C5 UUIDs: 0000180a-0000-1000-8000-00805f9b34fb
[CHG] Device B0:FC:0D:05:A7:C5 UUIDs: 0000180f-0000-1000-8000-00805f9b34fb
[CHG] Device B0:FC:0D:05:A7:C5 UUIDs: 00001812-0000-1000-8000-00805f9b34fb
[CHG] Device B0:FC:0D:05:A7:C5 UUIDs: 00001813-0000-1000-8000-00805f9b34fb
[CHG] Device B0:FC:0D:05:A7:C5 UUIDs: 5de20000-5e8d-11e6-8b77-86f30ca893d3
[CHG] Device B0:FC:0D:05:A7:C5 UUIDs: cfbfa000-762c-4912-a043-20e3ecde0a2d
[CHG] Device B0:FC:0D:05:A7:C5 UUIDs: fe151500-5e8d-11e6-8b77-86f30ca893d3
[CHG] Device B0:FC:0D:05:A7:C5 ServicesResolved: yes
[CHG] Device B0:FC:0D:05:A7:C5 Paired: yes
[NEW] Primary Service
/org/bluez/hci0/dev_B0_FC_0D_05_A7_C5/service0001
00001801-0000-1000-8000-00805f9b34fb
Generic Attribute Profile
[NEW] Characteristic
/org/bluez/hci0/dev_B0_FC_0D_05_A7_C5/servicefe02/charfe0b
cfbfa004-762c-4912-a043-20e3ecde0a2d
Vendor specific
Pairing successful
[CHG] Device B0:FC:0D:05:A7:C5 Appearance: 0x03c0
[CHG] Device B0:FC:0D:05:A7:C5 Modalias: usb:v0171p0413d0000
[CHG] Device C0:28:8D:DA:12:42 RSSI: -86
[CHG] Device 0D:B1:69:10:B0:F5 RSSI: -53
[AR]# trust B0:FC:0D:05:A7:C5
[CHG] Device B0:FC:0D:05:A7:C5 Trusted: yes
Changing B0:FC:0D:05:A7:C5 trust succeeded
[AR]# connect B0:FC:0D:05:A7:C5
Attempting to connect to B0:FC:0D:05:A7:C5
Connection successful
[AR]# scan off
Discovery stopped
[CHG] Controller 10:D0:7A:B2:6E:C1 Discovering: no
[CHG] Device B0:FC:0D:05:A7:C5 RSSI is nil
[CHG] Device C0:28:8D:DA:12:42 RSSI is nil
[CHG] Device 58:BC:5A:F3:18:D4 RSSI is nil
[CHG] Device 40:CB:C0:E2:20:2A RSSI is nil
[CHG] Device 0D:B1:69:10:B0:F5 RSSI is nil
[AR]# exitThanks Rich! will give this a try and report back
Worked a charm! Thanks for that
@spudy12 Glad to hear it worked for you.
@sam_nazarko Hey Sam could we get bluez-5.50 shipped as default in future builds?
This is something we can revisit after the next update.
Sam