LE13 - TV CEC Remote loses control of Kodi, when TV switched OFF and back ON.

    Current LibreELEC 13 Nightly installed on Rpi5 i.e. LibreELEC-RPi5.aarch64-13.0-nightly-20260711-3a340a8

    Following issue noted since switching from LibreELEC 12 to 13 Piers Beta 1 "Note a clean LibreELEC installation on Rpi5, no update from LibreELEC 12"

    I am having a particular issue I have never seen before when using LibreELEC 12 on my Rpi5, where the TV remote via CEC loses control of Kodi when the TV is switched OFF and then back ON again. This issue happens consistently i.e. When I reboot the Rpi5 (TV and AVR remain switched on) CEC via TV Remote works perfectly, however if I switch off the TV (which switches off the AVR) when I switch the TV back on (with AVR switched on by TV wake-up etc) I have no control of Kodi via CEC remote. (Until I perform a reboot of LibreELEC Rpi5)

    I have checked the CEC settings, re-setting to the defaults, after testing varied changes with no improvement observed etc.

    I used ssh and "getedid create" command to save working HDMI settings when CEC is correctly operational, (Custom HDMI settings) but doing this makes things perhaps worse as CEC then doesn’t work at ALL when under the Custom HDMI settings. (CEC consistently NOT working)

    Here is standard Kodi log (when CEC operational) using log capture method available in LibreELEC settings https://paste.libreelec.tv/bionomic-raven.log

    For more detailed Kodi debug log its unclear what to switch on in debug and what action to perform when, in order to capture any meaningful EDID/CEC data surrounding fact that CEC is working, then not working (after TV switched off and back on again) in same Kodi debug log etc.

    Note Rpi5 is connected to HDMI IN of AVR via HDMI port closest to power connection on Rpi5. TV is connected to HDMI OUT (ARC or eARC) of AVR

    Issue was not present in LibreELEC 12 with same physical connection set-up between Rpi5, AVR and TV

    ---Update---

    Switching TV from HDMI1 to another TV HDMI connection (with nothing connected to it) and then back to HDMI1, utilising the TV remote, wakes up the CEC connection in LibreELEC after TV has been switched off and back on. (Rather than having to re-boot Rpi5 in order to wake-up the CEC Connection)

    I am still investigating route cause to the loss of TV Remote CEC connection, but assume this finding will probably indicate that issue is not being caused by LibreELEC 13 (But something else in my HDMI handshake between the TV, AVR and Rpi5)

    Edited once, last by MikeKL (July 13, 2026 at 1:57 PM).

    It's worthwhile powering everything down, disconnecting cables, leaving everything for 20 mins (have a cup of tea/coffee) and then reconnect and power things on again. As dumb as that might sound, it frequently seems to work for CEC problems.

    Some of this behaviour could be intended. The underlying libCEC isn't 100 percent free of bugs. You should have a look with 'cec-ctl -M' via CLI whats happen on CEC bus during TV power off/ power on scenario. Maybe the TV is "old school" and requires the <MENU STATUS> message was sent, to route the remote keys through the HDMI port. With newer CEC versions this is not mandatory and the TV should everytime route the keys (One Remote idea). So it depends on th TV firmware as well.

    Since the TV sends the remote key commands to the active source only, the RPi5 must be identified as active source in beforehand of remote key routing. Do you have checked that this option is enabled wtihin your KODI CEC adapter settings?

    When you switch the HDMI ports at TV away from the current port and back again, the TV must send a <SET STREAM PATH> command as a routing information. The latter one will trigger the CEC follower (RPi5) to reinitiate some states, depending on the libCEC implementation.

    As the routing information must be right, it's very important that the port settings within the CEC adapter setting are correct and reliable. Only beginning with the nightly images nightly-20260420-bbf964a the libCEC 7.1.1 fix was implemented. Now it seems to be able to set correctly that an AVR is in use and the setting wasn't dropped after a reboot. But to get it working, my observation was as follows:

    • Don't use saved EDID information (remove via 'getedid delete'). That sounds logical to me as the CEC physical address negotiation depends on recent EDID information and should be not static.
    • Don't set "video=HDMI-A-1:1920x1080M@60D" via kernel boot line (cmdline.txt)

    Edited 3 times, last by HarryH (July 13, 2026 at 7:08 PM).

    Thank you both for your suggestions. I am going to look more carefully at the sequence of powering everything down and then bringing items powered up and online

    I've read that sequence of power up should be focused on TV first followed by the AVR and then finally the device(s) connected to the AVR.

    I've already kept hdmi connected elements in chain to a minimum until issue is hopefully fully resolved (TV - AVR - Rpi5) before connecting any other playback devices to AVR via HDMI.

    Will update thread with my findings..