What is the easiest way to transfer a working MCE remote config from Libreelec to the Vero 4k.

I would like to migrate a working remote in libreelec to OSMC on the Vero 4k.

The devices below were easy to set up in Libreelec following this wiki:
Libreelec Wiki on Infra-Red Remotes

Receiver Device: 0471:0815 Philips (or NXP) eHome Infrared Receiver
Remote: Zotac

As you can see at the bottom, we have a treasure trove of keymaps we can “borrow” so I hope a wise soul can point me in the right direction or help make a wiki,

In summary, how do we:
Blacklist native Vero 4k IR receiver (Vero 4k is hidden from view)
Use MCE Receiver (its long cable is preferred)
Transfer working configs from ibreelec to Vero 4K

Thanks

 ls /usr/lib/udev/rc_keymaps/
adstech_dvb_t_pci.toml
af9005.toml
alink_dtu_m.toml
allwinner_ba10_tv_box.toml
allwinner_i12_a20_tv_box.toml
anysee.toml
apac_viewcomp.toml
astrometa_t2hybrid.toml
asus_pc39.toml
asus_ps3_100.toml
ati_tv_wonder_hd_600.toml
ati_x10.toml
avermedia.toml
avermedia_a16d.toml
avermedia_cardbus.toml
avermedia_dvbt.toml
avermedia_m135a.toml
avermedia_m733a_rm_k6.toml
avermedia_rm_ks.toml
avertv_303.toml
az6027.toml
azurewave_ad_tu700.toml
beelink.toml
beelink_gs1.toml
behold.toml
behold_columbus.toml
budget_ci_old.toml
cec.toml
cinergy.toml
cinergy_1400.toml
cinergyt2.toml
cubox_i.toml
d680_dmb.toml
delock_61959.toml
dib0700_nec.toml
dib0700_rc5.toml
dibusb.toml
digitalnow_tinytwin.toml
digittrade.toml
digitv.toml
dish_network.toml
dm1105_nec.toml
dntv_live_dvb_t.toml
dntv_live_dvbt_pro.toml
dtt200u.toml
dvbsky.toml
dvico_mce.toml
dvico_portable.toml
em_terratec.toml
encore_enltv.toml
encore_enltv2.toml
encore_enltv_fm53.toml
evga_indtube.toml
eztv.toml
flydvb.toml
flyvideo.toml
fusionhdtv_mce.toml
gadmei_rm008z.toml
geekbox.toml
genius_tvgo_a11mce.toml
gotview7135.toml
haupp.toml
hauppauge.toml
hisi_poplar.toml
hisi_tv_demo.toml
imon_mce.toml
imon_pad.toml
imon_rsc.toml
iodata_bctv7e.toml
it913x_v1.toml
it913x_v2.toml
kaiomy.toml
khadas.toml
kii_pro.toml
kworld_315u.toml
kworld_pc150u.toml
kworld_plus_tv_analog.toml
leadtek_y04g0051.toml
libreelec_multi.toml
lme2510.toml
manli.toml
mce_keyboard.toml
medion_x10.toml
medion_x10_digitainer.toml
medion_x10_or2x.toml
megasky.toml
minix_neo.toml
msi_digivox_ii.toml
msi_digivox_iii.toml
msi_tvanywhere.toml
msi_tvanywhere_plus.toml
nebula.toml
nec_terratec_cinergy_xs.toml
norwood.toml
npgtech.toml
odroid.toml
opera1.toml
pctv_sedna.toml
pine64.toml
pinnacle310e.toml
pinnacle_color.toml
pinnacle_grey.toml
pinnacle_pctv_hd.toml
pixelview.toml
pixelview_002t.toml
pixelview_mk12.toml
pixelview_new.toml
powercolor_real_angel.toml
proteus_2309.toml
protocols
purpletv.toml
pv951.toml
rc6_mce.toml
real_audio_220_32_keys.toml
reddo.toml
snapstream_firefly.toml
streamzap.toml
su3000.toml
tango.toml
tanix_tx3mini.toml
tanix_tx5max.toml
tbs_nec.toml
technisat_ts35.toml
technisat_usb2.toml
terratec_cinergy_c_pci.toml
terratec_cinergy_s2_hd.toml
terratec_cinergy_xs.toml
terratec_slim.toml
terratec_slim_2.toml
tevii_nec.toml
tivo.toml
total_media_in_hand.toml
total_media_in_hand_02.toml
trekstor.toml
tt_1500.toml
tvwalkertwin.toml
twinhan_dtv_cab_ci.toml
twinhan_vp1027_dvbs.toml
vega_s9x.toml
videomate_k100.toml
videomate_s350.toml
videomate_tv_pvr.toml
vp702x.toml
wetek_hub.toml
wetek_play2.toml
winfast.toml
winfast_usbii_deluxe.toml
wobo_i5.toml
x96max.toml
xbox_360.toml
xbox_dvd.toml
xbox_one.toml
zotac.toml
zx_irdec.toml

You shouldn’t need to blacklist the internal receiver.

We had patches for the eHome receiver before in our kernel but I think I dropped them as they weren’t in demand / needed.

Have you tried plugging the receiver in and seeing if your remote works?

Hello Sam,

Yes I have the receiver connected to the Vero 4k running OSMC.
I saw you suggested in other threads enabling RC6 in the remotes section of the GUI which I have done, also disabled and enabled a few times after reboot with no response to key presses.

Could net even get a response with

 ir-keytable  -t

Which is why I want to try the config import if possible.

I don’t think it’s a config issue but rather a missing kernel module.

Logs may give some clues.

Here they are:
My Very own Vero 4K Logs

No driver seems to be detected for the receiver, which is why it doesn’t work.
I don’t actually see the device detected on your system at all. Was it plugged in when you uploaded the logs?

Yes it was plugged in while the logs were generated and uploaded.
I have rebooted with a second MCE receiver plugged in and generated the logs here:
Vero4K reboot with 2 MCE Receivers

I can see the receiver is detected now and there is an attempt to load the rc6 module, but it then says:

[    2.622697] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[    2.622701] usb 1-1: Product: eHome Infrared Transceiver
[    2.622705] usb 1-1: Manufacturer: Philips
[    2.622708] usb 1-1: SerialNumber: PH00FiQf
[    2.623662] usb 1-1: Unsupported device

So I don’t think our kernel has support for this model at this time.

:man_shrugging:

This transceiver is very old hardware in 2021 so a little surprised it’s not supported.
Especially as an open source sister project has it working.

Is it possible to compile OSMC with the required module?

Otherwise I guess the next move would be to install Libreelec on the Vero 4k.
Is there a simple way to install libreelec on the Vero 4k?

I added support for this receiver some time ago but recall removing it because no one seemed to be using the module.

I believe it’s possible – but this isn’t something we could directly support.

I’ll take a look later to see if we can add support for this in the next update.

Thanks Sam,

I just found a third USB receiver device, perhaps 3rd time’s the charm:

$ lsusb\
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub\
Bus 001 Device 002: ID 0766:0204 Jess-Link Products Co., Ltd TopSpeed Cyberlink Remote Control\
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub\

The white USB port did not recognise the receiver so perhaps that’s the reason why I needed the second upload above.

In any case here are the logs:
Log with cyberlink USB Receiver

Could I just use the inbuilt receiver to at least test the Zotac?

[[protocols]]
name = "zotac"
protocol = "rc6"
variant = "rc6_mce"
[protocols.scancodes]
0x8034048e = "KEY_POWER"
0x8034043d = "KEY_SLEEP"
0x80340400 = "KEY_NUMERIC_0"
0x80340401 = "KEY_NUMERIC_1"
0x80340402 = "KEY_NUMERIC_2"
0x80340403 = "KEY_NUMERIC_3"
0x80340404 = "KEY_NUMERIC_4"
0x80340405 = "KEY_NUMERIC_5"
0x80340406 = "KEY_NUMERIC_6"
0x80340407 = "KEY_NUMERIC_7"
0x80340408 = "KEY_NUMERIC_8"
0x80340409 = "KEY_NUMERIC_9"
0x80340432 = "KEY_NUMERIC_POUND"
0x80340433 = "KEY_NUMERIC_STAR"
0x8034043a = "KEY_DELETE"
0x80340434 = "KEY_ENTER"
0x8034045d = "KEY_MEDIA"
0x8034040d = "KEY_MUTE"
0x803404cb = "KEY_INFO"
0x80340410 = "KEY_VOLUMEUP"
0x80340411 = "KEY_VOLUMEDOWN"
0x8034041e = "KEY_CHANNELUP"
0x8034041f = "KEY_CHANNELDOWN"
0x80340428 = "KEY_FASTFORWARD"
0x80340429 = "KEY_REWIND"
0x8034042c = "KEY_PLAY"
0x80340437 = "KEY_RECORD"
0x80340430 = "KEY_PAUSE"
0x80340431 = "KEY_STOP"
0x80340420 = "KEY_NEXT"
0x80340421 = "KEY_PREVIOUS"
0x80340458 = "KEY_UP"
0x80340459 = "KEY_DOWN"
0x8034045a = "KEY_LEFT"
0x8034045b = "KEY_RIGHT"
0x8034045c = "KEY_OK"
0x80340483 = "KEY_EXIT"
0x8034043e = "KEY_EPG"
0x8034042f = "KEY_TITLE"
0x8034046d = "KEY_RED"
0x8034046e = "KEY_GREEN"
0x8034046f = "KEY_YELLOW"
0x80340470 = "KEY_BLUE"

If you don’t mind spending ~$20 I would suggest that a FLIRC USB IR dongle and a USB extension cord is going to get you something that works better than the old school stuff running through lircd.

Thanks darwindesign
I have seen your recommendations in other posts and I will get one because I collect such things.

As you know, Open Source Media Center comes from Kodi which comes from XBMC which was hacked together for Microsoft’s XBox, there is a spirit of defiance and cooperation which has drawn many human hours of work and dedication and as a consequence we have a woven a heritage of interoperability between many disparate devices in the code base.

My 15 year old Dell precision M65 has the current 32 bit Debian running today and serves me well for minor tasks.

However my iPhone 6 cannot install Trello because my version of iOS is “too old”.
A simple text based app for sharing tasks.
The iPad 1 mocks me in the same way with little to offer today.

Yes I have the FireTV and Apple TV and Raspberry Pi and Vero4k and Roku because I like such things.
The MCE receiver does a very basic task very well and still has a place in this ecosystem.

So it would be great if we have it working here because the people got together and made something beautiful and in the process many devices have avoided the rubbish heap.

It means more to me than money, it’s about the story we continue to tell as human beings.
Let’s come together as one and make global peace!
The epic end :wink:

and cure corona too.

I get it. I have a couple old MCE receivers that dropped off the supported list quite some time back that I was probably suppose to check back in with Sam about during a slow period and forgot. I think that most people nowadays seem to be preferential to using CEC or something very small and simple like the OSMC remote so that’s going to get more attention generally speaking. Although I feel a bit like a shill pumping up a specific product, I don’t see a better option for someone who likes remotes with lots of buttons and doesn’t want to go Bluetooth. I bought one when someone posted that it worked with long-press. After a week of testing I bought four more for the rest of the TV’s in my house because it gave a better experience to the other solutions I was using at the time (CEC, USB IR dongles, and Vero built-in IR).

There are currently some people that reported a non working white USB port, so suggest to stick with all your testing to the black port.

Yes I understand that smaller is better in some cases. :stuck_out_tongue_closed_eyes:

We all have our favourites and there are many more . .

Thanks for the heads up.
My other Vero 4K seems to be doing just fine with both ports working (USB Hard Disk and IR receiver)

This has now been fixed and will be in a near future update very shortly.

That’s great news! Thanks for resolving it quickly Sam.