New Vero V remote doesn’t always work

Help and Support Vero V
1

Got my new Vero V last week and finally setting it up today.
Is the remote line of sight now or something?
Doesn’t register clicks most of the time and not sure if it’s Pavlovian or not but when I point it more or less at the vero it works better.
Not sure if logs would help or not.

The blue light at the end of the remote does light every click.
Only about 12-15 feet away.

Have a usb hub (usb3) with multiple drives and enclosure attached, but this behaviour was happening right out of the box before connecting the drives.
Also updated it to the August 2024 update.

Thanks for any suggestions.

2

The remote is RF, not IR, although there is an IR receiver built in for use with those types of remotes. Having a USB 3 device plugged in can sometimes cause this type of behavior but if it is doing it without any USB devices attached you might look to see if you have any nearby devices that may be transmitting a strong signal in the 2.4ghz range. Is it maybe sitting really close to a router or WiFi access point?

3

Try putting that USB-3 hub in the USB 2 port and see if it improves. I know you said it happened before connecting but I am still curious.

Also see: Improving remote performance - Vero V - OSMC. We may need to ship you an external receiver if it’s still problematic

Sam

4

No, router is at opposite end of the house.
Have the tv cable box beside it and the usb hub and drives.
Everything is wireless these days so we of course have a lot of devices on wifi, both 2.4 and 5.
3 phones, couple laptops, the wireless tv gateways (they use 5ghz) , some Bluetooth devices and a handful of other ‘smart’ devices.
I used to have access to a wifi analyzer to see if some channels were overloaded but I no longer have that access.

5

Got it thanks, will try moving the hub to the other port and check out that article.

1 Like
6

Keep us posted.

7

Different port and moving the hub further away from the Vero hasn’t helped.
I’m going to try a longer usb cord for the hub to move it even further to see if that will help.

8

New dongle received and seemed like it was better.
A few days later it’s having problems again.
Often multiple presses do not register.
Seems like it comes and goes but clearly something isn’t right.

9

Have you paired the remote with the new dongle?

Can you upload some logs so we can check the new dongle is being used?

If you still have problems this would suggest some local interference that must be quite extreme.

10

I’ll grab some logs next few days.
I literally swapped out the 4K for the V in the entertainment unit. Same place.
Nothing else added. No issues with the vero 4K remote.

11

Thanks,

12

Sorry, work and home life have been less than ideal lately.
How can I tell if the dongle has been paired to the remote? Is there a specific lien int ehj log that shows us this?
I don’t have any prompts that show up, but i have tried the Home plus OK button to pair (if necessary).
Sorry if this is super basic.
Appreciate the help.

13

If you haven’t paired the remote to the new receiver you got, it won’t work. A log will show us if the replacement receiver is being detected and if the remote is working, then it has been paired to the new receiver.

14

Here’s the latest log, also had the missed remote presses.
What are the steps to pair the dongle?
https://xxxxx

15

The remote is paired by holding the Home and OK keys.

I can see that the external receiver is detected and working as expected:

usb_remote_manager.sh[2619]: External OSMC Remote USB receiver detected - internal receiver disabled.

The replacement dongle has fixed the issue for other users. If you have a problem still I would suspect a problem with your environment. The performance of these new receivers are actually improved over the ones that shipped with 4K/4K+ with regards to range.

Anything connected to the USB ports on the device?

16

Yes, just the powered TP-Link USB hub (model: UH720(UN) that connects to the 2 enclosures and 2 external drives.

17

Plug it in the USB2 port if it’s in the USB3 port. Does this fix the issue?