roidy
24 April 2023 16:17
#1
I’ve purchased a cheap Xiaomi Mi BOX Bluetooth remote:-
However I’m having problems getting it to work. It connects fine via bluetooth but CoreELEC seems to think it’s a game controller:-
And when I try cat /proc/bus/input/devices
it’s not listed.
I: Bus=0010 Vendor=1b8e Product=0cec Version=0001
N: Name="cec_input"
P: Phys=
S: Sysfs=/devices/virtual/input/input0
U: Uniq=
H: Handlers=kbd event0
B: PROP=0
B: EV=3
B: KEY=1 0 0 0 0 100000 0 0 0
I: Bus=0019 Vendor=0000 Product=0000 Version=0000
N: Name="meson-ir"
P: Phys=meson-ir/input0
S: Sysfs=/devices/platform/ff808040.meson-ir/rc/rc0/input4
U: Uniq=
H: Handlers=kbd event4
B: PROP=0
B: EV=100013
B: KEY=fff 0 0 4200 108fc32e 2376051 0 0 0 7 158000 4192 40004801 9e96c0 0 0 10000ffc
B: MSC=10
Anybody have any ideas how to get this remote working? Thanks.
roidy
30 April 2023 11:32
#2
Does anybody have any ideas why this remote is detected as a game controller and not a remote?
You’ll need a udev rule like this stored under /storage/.config/udev.rules.d
:
SUBSYSTEM=="hid", ACTION=="add", ATTR{HID_ID}="0003:00000E8F:00002517", RUN+="/bin/sh -c 'echo 0005 2717 32B0 > /sys/bus/hid/drivers/hid-generic/new_id'"
The rule assigns the remote to the hid-generic
driver instead of the default controller driver.
This is for my the bundled remote for my mibox 3, however, and you’ll need to adapt the ATTR{HID_ID}
and the ID being echoed according to your actual device. You should be able to figure out yours by using udevadm monitor
.
roidy
3 May 2023 07:03
#4
Thanks for the reply.
I’ve run udevadm monitor
and when I connect the remote I get this response:-
UDEV [60999.434417] add /devices/platform/ff500000.dwc3/xhci-hcd.0.auto/usb1/1-1/1-1.3/1-1.3:1.0/bluetooth/hci0/hci0:65 (bluetooth)
Which part of that is the ID?
I can also run bluetoothctl
and it returns the following info for the remote:-
CoreELEC:~ # bluetoothctl
Agent registered
[CHG] Device B4:20:5B:A5:C2:5C RSSI: -84
[Xiaomi RC]# info
Device DC:E5:33:31:BB:40 (public)
Name: Xiaomi RC
Alias: Xiaomi RC
Class: 0x00000504
Icon: input-gaming
Paired: yes
Bonded: yes
Trusted: yes
Blocked: no
Connected: yes
LegacyPairing: no
ManufacturerData Key: 0x0000
RSSI: -46
TxPower: 0
But again I don’t know the ID.