Finally I got my Vero V (thank you!).
I’m using this WDTV Live remote:
It has “subtitle” and “audio” keys, which are mapped in the lirc config as:
KEY_SUBTITLE 0x30CF KEY_LANGUAGE 0xB04F
These were working properly on Vero 4k+ (cycling through available subtitle and audio streams), but doesn’t do anything on Vero V. These are (were…) somehow mapped to “CycleSubtitle” and “AudioNextLanguage” kodi functions.
Could anyone help me to get back these functions, please?
Thank you in advance!
What version of OSMC is 4K/4K+ running?
Have you checked Kodi debug log to see if the keys are 1) registered; 2) the same on 4K/4K+ and V?
Vero 4k+ version (according to the log):
Starting Kodi (21.1). Platform: Linux ARM 32-bit (version for Vero)
Using Release Kodi x32
Kodi compiled 2024-10-03 by GCC 10.2.1 for Linux ARM 32-bit version 5.10.158 (330398)
Running on OSMC Vero 4K / Vero 4K + with Open Source Media Center 2024.10-1, kernel: Linux ARM 32-bit version 4.9.269-62-osmc
Vero V version:
Starting Kodi (21.1). Platform: Linux ARM 32-bit (version for Vero)
Using Release Kodi x32
Kodi compiled 2024-10-03 by GCC 10.2.1 for Linux ARM 32-bit version 5.10.158 (330398)
Running on OSMC Vero V with Open Source Media Center 2024.10-1, kernel: Linux ARM 32-bit version 4.9.269-70-osmc
The KEY_SUBTITLE and the KEY_LANGUAGE events does appear in the Vero 4k+ debug log, but not in the Vero V log (see below). What do you think? What does it mean?
Unfortunately I don’t quite understand the IR process layers (kernel - lirc - kodi). 
2025-02-24 14:24:32.498 T:2811 info <general>: Enabled debug logging due to GUI setting. Level 2.
2025-02-24 14:24:32.501 T:2811 debug <general>: ------ Window Init () ------
2025-02-24 14:24:39.193 T:2875 debug <general>: LIRC: - NEW 6c 0 KEY_DOWN linux-input-layer (KEY_DOWN)
2025-02-24 14:24:39.248 T:2811 debug <general>: HandleKey: 167 (0xa7, obc88) pressed, window 10016, action is Down
2025-02-24 14:24:39.860 T:2875 debug <general>: LIRC: - NEW 6c 0 KEY_DOWN linux-input-layer (KEY_DOWN)
2025-02-24 14:24:39.915 T:2811 debug <general>: HandleKey: 167 (0xa7, obc88) pressed, window 10016, action is Down
2025-02-24 14:24:40.705 T:2875 debug <general>: LIRC: - NEW 6c 0 KEY_DOWN linux-input-layer (KEY_DOWN)
2025-02-24 14:24:40.766 T:2811 debug <general>: HandleKey: 167 (0xa7, obc88) pressed, window 10016, action is Down
2025-02-24 14:24:44.623 T:2875 debug <general>: LIRC: - NEW 172 0 KEY_SUBTITLE linux-input-layer (KEY_SUBTITLE)
2025-02-24 14:24:44.626 T:2811 debug <general>: HandleKey: comma (0x2c) pressed, window 10016, action is
2025-02-24 14:24:46.460 T:2875 debug <general>: LIRC: - NEW 170 0 KEY_LANGUAGE linux-input-layer (KEY_LANGUAGE)
2025-02-24 14:24:46.516 T:2811 debug <general>: HandleKey: minus (0x2d) pressed, window 10016, action is
2025-02-24 14:24:53.128 T:2875 debug <general>: LIRC: - NEW 67 0 KEY_UP linux-input-layer (KEY_UP)
2025-02-24 14:24:53.170 T:2811 debug <general>: HandleKey: 166 (0xa6, obc89) pressed, window 10016, action is Up
2025-02-24 14:24:53.484 T:2875 debug <general>: LIRC: - NEW 67 0 KEY_UP linux-input-layer (KEY_UP)
2025-02-24 14:24:53.532 T:2811 debug <general>: HandleKey: 166 (0xa6, obc89) pressed, window 10016, action is Up
2025-02-24 14:24:53.804 T:2875 debug <general>: LIRC: - NEW 67 0 KEY_UP linux-input-layer (KEY_UP)
2025-02-24 14:24:53.815 T:2811 debug <general>: HandleKey: 166 (0xa6, obc89) pressed, window 10016, action is Up
2025-02-24 14:24:55.798 T:2875 debug <general>: LIRC: - NEW 160 0 KEY_OK linux-input-layer (KEY_OK)
2025-02-24 14:24:55.848 T:2811 debug <general>: HandleKey: 11 (0xb, obc244) pressed, window 10016, action is Select
2025-02-24 14:24:55.849 T:2811 info <general>: Disabled debug logging due to GUI setting. Level 0.
2025-02-24 14:24:55.849 T:2811 info <general>: Log level changed to "info"
2025-02-24 14:29:33.552 T:2829 info <general>: Enabled debug logging due to GUI setting. Level 2.
2025-02-24 14:29:33.556 T:2829 debug <general>: ------ Window Init () ------
2025-02-24 14:29:35.456 T:2899 debug <general>: LIRC: - NEW 6c 0 KEY_DOWN linux-input-layer (KEY_DOWN)
2025-02-24 14:29:35.490 T:2829 debug <general>: HandleKey: 167 (0xa7, obc88) pressed, window 10016, action is Down
2025-02-24 14:29:36.651 T:2899 debug <general>: LIRC: - NEW 67 0 KEY_UP linux-input-layer (KEY_UP)
2025-02-24 14:29:36.668 T:2829 debug <general>: HandleKey: 166 (0xa6, obc89) pressed, window 10016, action is Up
2025-02-24 14:29:48.710 T:2899 debug <general>: LIRC: - NEW 160 0 KEY_OK linux-input-layer (KEY_OK)
2025-02-24 14:29:48.764 T:2829 debug <general>: HandleKey: 11 (0xb, obc244) pressed, window 10016, action is Select
2025-02-24 14:29:48.764 T:2829 info <general>: Disabled debug logging due to GUI setting. Level 0.
2025-02-24 14:29:48.764 T:2829 info <general>: Log level changed to "info"
Additonal logs on Vero 4K+ during video playing:
2025-02-24 15:31:40.636 T:2875 debug <general>: LIRC: - NEW 172 0 KEY_SUBTITLE linux-input-layer (KEY_SUBTITLE)
2025-02-24 15:31:40.642 T:2811 debug <general>: HandleKey: comma (0x2c) pressed, window 12005, action is NextSubtitle
2025-02-24 15:31:45.381 T:2875 debug <general>: LIRC: - NEW 170 0 KEY_LANGUAGE linux-input-layer (KEY_LANGUAGE)
2025-02-24 15:31:45.397 T:2811 debug <general>: HandleKey: minus (0x2d) pressed, window 12005, action is AudioNextLanguage
There is nothing similar in the Vero V log. No “key_” string between the start (key_go) and the stop (key_stop) command.
Can you look in the remote section of the My OSMC add-on on both devices and confirm the Vero V is set to the same remote profile as the 4K.
I’m really terribly sorry, it’s my fault.
You’re right, the Vero V was using the built-in WDTV remote profile, while the Vero 4k+ is running with my custom one. Probably I missed to click on the confirm button after selecting the right file.
Thank you for your answers, it’s resolved now.
No worries. Perhaps you could post here the contents of your custom conf file in case someone else happens to want these two buttons working as well.
Of course, here is the full story:
Actually, it’s not a real WDTV Live Remote, but an URC-7935 Universal Streaming Remote, sending IR codes of a WDTV remote.
Here is the config file for Lirc:
#
# brand: URC7935 emulating WDTV Live remote
# model no. of remote control: WDTV Live Remote
# devices being controlled by this remote: WDTV Live
#
begin remote
name URC7935_WDTV
bits 16
flags SPACE_ENC|CONST_LENGTH
eps 30
aeps 100
header 9024 4512
one 564 1692
zero 564 564
ptrail 564
repeat 9024 2256
pre_data_bits 16
pre_data 0x219E
gap 108000
toggle_bit_mask 0x0
begin codes
KEY_POWER 0x48B7
KEY_HOME 0x609F
KEY_UP 0xA05F
KEY_DOWN 0x00FF
KEY_LEFT 0xE01F
KEY_RIGHT 0x906F
KEY_OK 0x10EF
KEY_BACK 0xD827
KEY_STOP 0x20DF
KEY_INFO 0x58A7
KEY_REWIND 0xF807
KEY_PLAYPAUSE 0x50AF
KEY_FASTFORWARD 0x7887
KEY_PREVIOUS 0x40BF
KEY_NEXT 0x807F
KEY_SETUP 0x827D
KEY_MENU 0x08F7
KEY_SUBTITLE 0x30CF
KEY_LANGUAGE 0xB04F
KEY_PAGEUP 0xC03F
KEY_PAGEDOWN 0x32CD
end codes
end remote
And here is the related RMDU (Remote Master Device Upgrade) file. This file is to be used with the RemoteMaster program to modify the configuration of the JP1 Remotes. See details:
http://www.hifi-remote.com/wiki/index.php?title=Main_Page
http://www.hifi-remote.com/forums/index.php
https://controlremote.sourceforge.io/
The subtitle and language functions are mapped to the buttons “N” (Netflix) and “A” (Amazon). But of course these can be moved to any other buttons with the program above.
Description=Vero (WDTV mode)
Remote.name=URC-7935 OFA Streamer
Remote.signature=262403
SegmentFlags=255
DeviceType=Cable
DeviceIndex=2
SetupCode=3305
Protocol=00 5A
Protocol.name=NEC1
ProtocolParms=132 121 null 0 0
FixedData=20 DE 61
Function.0.name=Power
Function.0.hex=B7
Function.1.name=Home
Function.1.hex=9F
Function.2.name=Up
Function.2.hex=5F
Function.3.name=Down
Function.3.hex=FF
Function.4.name=Left
Function.4.hex=1F
Function.5.name=Right
Function.5.hex=6F
Function.6.name=OK
Function.6.hex=EF
Function.7.name=Back
Function.7.hex=27
Function.8.name=Stop
Function.8.hex=DF
Function.9.name=Info
Function.9.hex=A7
Function.10.name=Rewind
Function.10.hex=07
Function.11.name=Play/Pause
Function.11.hex=AF
Function.12.name=Fast Forward
Function.12.hex=87
Function.13.name=Previous
Function.13.hex=BF
Function.14.name=Next
Function.14.hex=7F
Function.15.name=Menu
Function.15.hex=F7
Function.16.name=Subtitle
Function.16.hex=CF
Function.17.name=Language
Function.17.hex=4F
Function.18.name=Channel Up
Function.18.hex=3F
Function.18.notes=PgUp
Function.19.name=Channel Down
Function.19.hex=CD
Function.19.notes=PgDn
Button.1c=Channel Up|null|null
Button.1d=Channel Down|null|null
Button.4=Back|null|null
Button.5=Home|null|null
Button.9=Up|null|null
Button.a=Down|null|null
Button.b=Left|null|null
Button.c=Right|null|null
Button.d=OK|null|null
Button.13=Rewind|null|null
Button.14=Play/Pause|null|null
Button.15=Fast Forward|null|null
Button.3=Power|null|null
Button.11=Menu|null|null
Button.12=Info|null|null
Button.21=Subtitle|null|null
Button.22=Language|null|null
I hope it will help others to use these functions…
BUMMER!
I was going to ask where you got that WDTV Live remote with dedicated Audio and Subtitles buttons.
I had a WDTV forever ago and my remote looked way simpler than that one.
I really like that remote shown in your first post.
It also has dedicated PLAY and STOP buttons which for some reason are rare on new remotes.
I also had about 3 or 4 different generations of WDTV players. I was a great fan of them before I met OSMC/Vero.
Its remote is still my favourite, it’s very easy to implement its functions on any universal remote, due to the strictly standard NEC protocol.
The “advanced” remote in my first post was bundled with the latest generations of WDTV (Live Streaming, and Live Hub). The earlier generations had this much simpler remote:
