[closed - Dongle broken] Pairing remote does not work

Help and Support
1

Hi there,

have not yet been able to pair the remote.
In principle this is not problem as the remote of my TV works on the Vero4k+ via CEC
However there is one big drawback.

When I have switched off my TV I am not able to get back to my vero…
Hence each time I want to use it I need to reboot as my tv remote does not wake up the vero…

I tried to pair it a couple of times via the force pair (dongle off/ force pair/ dongle back in usb) but it does not work.

a) is there a way how to restart the vero without pulling the plug ?
did not find a switch ;-))

b) is there a CEC override - i.e. if the vero is connected HDMI to my TV (Samsung Qseries - it actually first goes into the Q90R soundbar and then into the TV) only the “Master” remote works

c) is the dongle faultiy ?
Put it into the USB of a PC (Win10) - as per the wiki its detecec as a USB keyboard mouse but no movement in the notepad (am using notepad++ - does it need to be the standard one ?)

NB - exchanged the batteries a couple of times and the only thing I see working on the remote is the blues light which stays on

Appreciated if you could provide some guidance on what could be the issue.
Would a log on the vero show me that at least the dongle works ?
Can I see sth on my Win10 machine ?

Tx

2

Yes.

3

Hi again,

I did not really manage to use the pastebin version (or there are now some logs which I cannot pickup)

Also I do not really want to post the full log here as a) too big and b) quite a lot of other stuff in there (almost my full libary)

From the logs I created it seems that the dongle is at least detected?
What are the buzzwords that would show me that its pairing or not ?

Aug 09 22:51:12 4kbox kernel: usb 1-2: New USB device found, idVendor=2017, idProduct=1688
Aug 09 22:51:12 4kbox kernel: usb 1-2: New USB device strings: Mfr=1, Product=2, SerialNumber=0
Aug 09 22:51:12 4kbox kernel: usb 1-2: Product: USB Keyboard Mouse
Aug 09 22:51:12 4kbox kernel: usb 1-2: Manufacturer: OSMC Remote Controller
Aug 09 22:51:12 4kbox kernel: input: OSMC Remote Controller USB Keyboard Mouse as /devices/c9000000.dwc3/xhci-hcd.0.auto/usb1/1-2/1-2:1.0/0003:2017:1688.0001/input/input2
Aug 09 22:51:12 4kbox kernel: hid-generic 0003:2017:1688.0001: input,hidraw0: USB HID v1.10 Keyboard [OSMC Remote Controller USB Keyboard Mouse] on usb-xhci-hcd.0.auto-2/input0
Aug 09 22:51:12 4kbox kernel: input: OSMC Remote Controller USB Keyboard Mouse as /devices/c9000000.dwc3/xhci-hcd.0.auto/usb1/1-2/1-2:1.1/0003:2017:1688.0002/input/input3
Aug 09 22:51:12 4kbox kernel: hid-generic 0003:2017:1688.0002: input,hidraw1: USB HID v1.10 Mouse [OSMC Remote Controller USB Keyboard Mouse] on usb-xhci-hcd.0.auto-2/input1

2019-08-10 15:52:54.320 T:3841975008 NOTICE: Register - new cec device registered on cec->AOCEC: CEC Adapter (0000:0000)
2019-08-10 15:52:54.351 T:4066263040 NOTICE: Register - new keyboard device registered on application->keyboard: Keyboard (0000:0000)
2019-08-10 15:52:54.352 T:4066263040 NOTICE: Register - new mouse device registered on application->mouse: Mouse (0000:0000)
2019-08-10 15:58:38.416 T:4037010144 DEBUG: CLibInputHandler::DeviceRemoved - keyboard type device removed: OSMC Remote Controller USB Keyboard Mouse (event2)
2019-08-10 15:58:38.576 T:4037010144 DEBUG: CLibInputHandler::DeviceRemoved - pointer type device removed: OSMC Remote Controller USB Keyboard Mouse (event3)
2019-08-10 15:58:38.576 T:4037010144 DEBUG: CLibInputHandler::DeviceRemoved - keyboard type device removed: OSMC Remote Controller USB Keyboard Mouse (event3)
2019-08-10 15:58:38.656 T:4037010144 DEBUG: CLibInputHandler::DeviceRemoved - pointer type device removed: eventlircd (event6)

2019-08-10 15:58:44.686 T:4037010144 DEBUG: CLibInputHandler::DeviceAdded - pointer type device added: OSMC Remote Controller USB Keyboard Mouse (event3)
2019-08-10 15:58:44.686 T:4037010144 DEBUG: CLibInputHandler::DeviceAdded - keyboard type device added: OSMC Remote Controller USB Keyboard Mouse (event3)
2019-08-10 15:58:44.686 T:4037010144 DEBUG: CLibInputKeyboard::GetRepeat - could not get key repeat for event3 (Function not implemented)
2019-08-10 15:58:44.686 T:4037010144 DEBUG: CLibInputKeyboard::GetRepeat - delay: 400ms repeat: 80ms for OSMC Remote Controller USB Keyboard Mouse (event3)
2019-08-10 15:58:44.768 T:4037010144 DEBUG: CLibInputHandler::DeviceAdded - keyboard type device added: OSMC Remote Controller USB Keyboard Mouse (event2)
2019-08-10 15:58:44.768 T:4037010144 DEBUG: CLibInputKeyboard::GetRepeat - delay: 500ms repeat: 50ms for OSMC Remote Controller USB Keyboard Mouse (event2)

tx anyhow for ideas

4

Are you using the standby functionality of the Vero? If so try turning that off (it really doesn’t save much power).

By ‘Master’ remote do you mean the TV remote or the Vero remote?

When you try to pair the Vero remote, does the blue light blink?

5

no the blue light stays straight and then dims out & Yes the master remote is the one from my TV

6

Sound like a low battery. Did you try a new ‘non counterfeit’ battery out of a packet, or a battery from another device?

7

new battery out of the blister & dim out is not right - it switches off

8

Just to be sure, have you exactly tried the steps described here: Pairing the Original Black OSMC RF Remote Control with a Pi/Vero2/4k/4k+

9

yup thats the one I followed BUT

  1. Hold Home and OK button for around 5 seconds until the blue LED starts flashing.
    It is lit constantly - no flashing in the way like on off on off

  2. Plug in the USB receiver to the Pi/Vero and the LED should flash 3 times within some seconds,
    It just goes dark…

10

That’s ok, but the rest sounds odd. Any chance that this is the wrong USB dongle? Tbh some time ago I exchanged the dongle with the one from an Rii mini keyboard and spent an hour wondering why the OSMC remote does not want to pair.
If it is the right dongle, something seems to be broken …

Addition: Just rechecked the behaviour with my current OSMC remote from a Vero 4k. The blue remote LED starts glowing after 5 seconds press+hold the OK- and HOME-button but the
LED immediatelly goes dark when I release the buttons … but it is still in pairing mode. After inserting the RF receiver USB dongle the remote LED flashes 3 times.

13

It’s definitely the right dongle & I am really curious how to identify the route cause.
Will retry with a log later this week

14

Hope that the log now worked - could sbdy have a look in here
http://paste.osmc.io/eqoriqubof.vhdl

When the log got recorded I pluged and unplugged a couple of times the dongle.
Before plugging back into a diff usd I started the pairing process again from the remote so that I get the blue light…

still not working :rage: and wonder where I fail

15

Please start a support ticket so we can send a new receiver

16

ok - have done so - tx for the support and quick feedback
(have amended the title - threat can be closed)