CEC TV Remote stopped working

[Giovanni_Garcea]

Hi, suddenly I cannot control the Vero 4k with my TV remote anymore.
Coincidentally my TV received a firmware update while I was at work and when I got home I noticed this problem.
I did a factory reset of the TV, but that didn’t help. The TV remote is still able to change the receiver volume and the CEC on off functions work, but no arrow or ok functions.
To test further I disconnected the HDMI cable from the Vero and connected back to my Shield TV and in that case the remote can control the Shield without any issue, so CEC commands from the TV seem ok.

I rebooted the Vero box about 10 times and on one of these times, the CEC control worked…

I even set back the CEC settings in kodi to default, but no luck.

Hopefully you guys can help me figure out what’s wrong.

Here’s a log:
http://paste.osmc.tv/uzekamabun

[sam_nazarko]

Try powering down everything at the mains for five minutes.

[Giovanni_Garcea]

Thanks Sam, unfortunately it didn’t help…
I tried many power up sequences (receiver last, tv last, vero last) and even connecting the TV directly to the Vero without receiver. I just can’t get it to work anymore. It worked perfectly out of the box until today…

[Giovanni_Garcea]

Any ideas?

• Some more info: The TV sees “Kodi” (Kodi is listed in the list of CEC devices connected)

• Connected the Vero directly to the TV using a different (trusted) HDMI cable. no change.

• I searched through the forum and I issued this command (twice, because I got an error the first time):

  osmc@osmc:~$ echo scan | cec-client -s -d 1
  opening a connection to the CEC adapter…
  requesting CEC bus information …
  ERROR: [ 21160] failed to request the physical address
  CEC bus information

  device #0: TV
  address: 0.0.0.0
  active source: no
  vendor: Unknown
  osd string: TV
  CEC version: unknown
  power status: on
  language: eng

  device #1: Recorder 1
  address: 1.7.0.0
  active source: no
  vendor: Pulse Eight
  osd string: CECTester
  CEC version: 1.4
  power status: on
  language: eng

  device #5: Audio
  address: f.f.f.f
  active source: no
  vendor: Denon
  osd string: AVR-X3400H
  CEC version: unknown
  power status: on
  language: ???

  currently active source: unknown (-1)
  osmc@osmc:~$ echo scan | cec-client -s -d 1
  opening a connection to the CEC adapter…
  requesting CEC bus information …
  CEC bus information

  device #0: TV
  address: 0.0.0.0
  active source: no
  vendor: Unknown
  osd string: TV
  CEC version: 1.4
  power status: on
  language: ???

  device #1: Recorder 1
  address: 1.7.0.0
  active source: no
  vendor: Pulse Eight
  osd string: CECTester
  CEC version: 1.4
  power status: on
  language: eng

  device #5: Audio
  address: 1.0.0.0
  active source: no
  vendor: Unknown
  osd string: AVR-X3400H
  CEC version: unknown
  power status: on
  language: ???

  currently active source: unknown (-1)

[sam_nazarko]

Okay – let’s think about what might have changed.

Have recent devices been added / powered recently?
Does CEC work if HDMI is temporarily ran to the TV directly?

[Giovanni_Garcea]

Thanks Sam.
Devices are the same, but VIZIO updated the firmware of the TV yesterday. The problems started at the same time. This is suspicious because they mention some CEC changes in their release notes:

Update the Cast Shell to 1.27
HDR Certification for 2016 P and 2017 M and P series
Fix for casting DirecTV now app 30 second loop problem
Alexa Performance improvements
p65-e1 white line issue fix
CEC Auto Naming
Correction to blue screen when casting Spotify
General/overall system improvements.

Having said that, Denon and Shield TV continued to be CEC controlled without issues after the firmware update. Maybe some subtle changes that affect only some hardware…

No, I can’t make CEC control to work at all, excluding the receiver from the chain, using different shorter cables, etc… Nothing seem to work. Only once yesterday after a reboot it worked, but I wasn’t able to reproduce that again.

I’m new to OSMC, so I’m not sure when updates are released. Was there anything updated in the last 48 hours?

[sam_nazarko]

@Giovanni_Garcea

Was there anything updated in the last 48 hours?

No changes.

I wonder if we need to change the role of the Vero 4K for you. Some information:

My Panasonic Viera Remote all of a sudden stopped working with my Raspberry Pi 2

There are limitations in CEC re. # of players, recorders etc. You can only have two Recorders, and three Players by default I believe. Then you have to change the LA manually (which Kodi allows for example) to a free address. However I think if you do this, some functions may not work as expected because some devices on the bus will expect a different role depending on the address. Address Device 0 TV 1 Recording Device 1 2 Recording Device 2 3 Tuner 1 4 Playback Device 1 5 Audio System 6 Tun…

See

HDMI-CEC some buttons not working on Vero2 that do work on Pi2

Interesting. Vero 2 is configured as a Player by the bootloader but it behaves as a Recorder on Pi. You can try editing this file and see if it fixes things: Edit /usr/share/kodi/system/peripherals.xml. Change <setting key="device_type" type="int" value="4" configurable="0" /> to <setting key="device_type" type="int" value="1" configurable="0" /> This change will be overwritten by future updates, but the plan here is to see if this works for you.

Changing the device type via peripherals.xml might work for you.

[Giovanni_Garcea]

It’s alive! Thanks for the suggestions. Actually, changing values in this file:

/usr/share/kodi/system/peripherals.xml

didn’t do anything. So I went ahead and make a change to:

.kodi/userdata/peripheral_data/cec_CEC_Adapter.xml

I changed device type from “1” to “4” and the remote started working immediately.
Hopefully this is a stable fix!

[sam_nazarko]

Yes – this adjustment will be persistent. If you ever reinstall OSMC however you’ll need to make these changes again.

Sam