So the output looks that CEC is working at hardware and driver level. You can test some CEC commands to switch your connected TV On/Standby/Off like described here: https://pimylifeup.com/raspberrypi-hdmi-cec/
To test if your TV passthrough the remote control keys to the RPi, simple start cec-client without any switches and look for key_press events. If that works, you only have some issues with your KODI installation/settings. That kind of issues can isolated with debug logging enabled and additional components logging is enabled for libCEC.
Posts by HarryH
-
-
WarpLover ,
these settings should only needed, if the Power Delivery negotiation between RPi5 and the power supply isn't possible or disturbed. Do you use a case like the Argon ONE or another gadget like RemotePi board for your RPi5? -
If chewitt serious recommendation don‘t ends in a success, you can stop KODI and afterwards check CEC directly.
- stop KODI
systemctl stop kodi - scan CEC bus
echo 'scan' | cec-client -s -d 1
Because I have seen, that you also tested something regarding the 4K/60 issue in combination with your Denon AVR: Maybe you have a outdated copy of EDID data locally?
- stop KODI
-
Hi tomstephens89 ,
some questions…
- Are you using a case for your RPi4?
- Do you have tried also another micro HDMI to HDMI adapter, if you use one?
- This could be ambiguous: HDMI 1 of „HDMI 0 + HDMI 1“ or „HDMI 1 + HDMI 2“ ?
- Perhaps you can provide a debug log?
-
By the way, the period key on the left of the number pad is assigned to the context menu by default.
-
Are you sure that you edit in the right directory ?
Your add-on with the settings.xml file for defining the GUI items should be located here: /storage/.kodi/addons/script.test
Add-on structure - Official Kodi Wiki
In the directory /storage/.kodi/userdata/addon_data/script.test , there should only be the corresponding settings.xml file for saving values and will be generated automatically. -
I think the missing part is <group></group> as a wrapper for setting. Its mandatory also if you doesn‘t have more than 1 group.
-
The linked thread is correct because the TV is the receiver of the IR signals and sends a button code (the duration info seems not parsed or reliable) to the RPi5 via CEC.
Technically possible, but I don't expect this behavior on a TV:
If the TV interprets the buttons based on how long they were held down, it may be sending a different CEC button code.
The important part regarding the breaking change seems the Android/Google TV generation. Previous generations of SONY TVs are able to passthrough the tuning and menu keys to CEC, if you configure this in the Bravia Sync settings for external inputs.
After switching to a newer TV of the same brand, I'm facing for the issue, that the menu keys and some other keys aren't passthrough anymore. Before it was possible to use the channel-up/down keys to navigate page wise through long listings. Now it's possible to open an additional menu for HDMI via info key and send a CEC command in behalf of the TV, but this key was also usable before directly.
My workaround is currently to move one step to right in the movie list to focus the scroll bar and move then with the cursor keys to jump to the next page(s) faster.
If this, that you meant with slow scrolling, perhaps you should map one of the color keys to the channel-up/down function. If not, you can only try to play a little bit with the CEC settings at System -> Input -> Peripherals.
To check which keys are going passthrough via CEC with your TV, you can stop KODI and use the cec-client command.- Stop KODI
systemctl stop kodi - Start the CEC-client
cec-client Press the keys on your remote control step by step and write down a list of all available keys. Here an example for cursor right:
- Stop the cec-client process with CTRL-C
- Start KODI again
systemctl start kodi
With that information you can make then the changes like you want to the keymap file.
EDIT:
I played a little bit with the settings (System -> Input -> Peripherals -> CEC Adapter) and could clarify 2 things:- Set „Remote button press repeat rate (ms)“ to 100ms fixes the „slow“ repeat rate compared to a IR remote control.
Reducing "Remote button press delay before repeating (ms)" to 200 makes it even faster to switch in repeat mode (scrolling), but could be make some trouble if there is "longpress" support in the future. - It‘s important to switch the TV to the HDMI sub input/device -> "Kodi HDMI 1 Player" not only "HDMI 1" to get the tuning and number keys to work.
- Stop KODI
-
Currently I have no plans to support RaspiOS too. There are many reasons that speak against it:
- with a normal OS the fan control should be enabled system-wide, power button too
- system-wide solutions are already available: argon1.sh, Argon One Daemon …
- no spare system to test
- available time
- …
-
Maybe the root cause of your 4.0 channel issue is the same like this issue:
PostRE: Only 6.1 LPCM for 7.1 sources with Raspberry Pi
When you open a HDMI audio device on the RPi the kernel automatically chooses a channel map based on the number of channels (eg 8 in this case) and the speaker allocation from the EDID.
The hdmi-codec driver has an ordered list, sorted by preference, and will choose the first entry that's supported by HDMI for the given number of channels and is supported by the AVR as well (all channels of that entry must also be present in the EDID speaker allocation block).
In this table the 6.1 entry with RC…HiassofTMay 2, 2024 at 11:10 AM -
-
Please don't use the outdated version 0.0.1 from Argon40. Instead use a recent version like 1.0.0:
Install instructions
Download Link at GitHub
Discussion thread -
chewitt ,
I'm appreciate your offer and hasn't forgot this Thread
Until now I was focused to make the technical part right. I wasn't unhappy with the original add-on icon, but it makes sense to follow a unified style.
Shortly after I enabled the issues option at the GitHub repo yesterday, it seems there is an interest to make some cosmetic changes... -
Version 1.0.0 released:
- renumbering to better follow semantic versioning
- menu structure reorganized
- added fan curve for GPU and PMIC temperature
New versions are now being published on GitHub
Releases · HungerHa/libreelec_package_argonforty-deviceArgonForty Device Configuration Add-On for LibreELEC - HungerHa/libreelec_package_argonforty-devicegithub.com -
Hi Baallrog,
please use the updated scripts from here:
PostRE: Problem with autostart.sh on RPI-4 Libreelec 11.95.1 Omega
In the meanwhile I have played a little bit with pinctrl. But it's now your part to test if it works.
(Code, 35 lines)
(Code, 41 lines)
[…]
To make it complete, please check every listed chip:
(Code, 2 lines)
The correct one has 58 on the RPi4 (but the pin count could be split/vary on RPi5) as the return value for ngpio and I'm assuming the label is "pinctrl-bcm2712" or something similar.
EDIT:
Benoitone I have added pull-down for the input pin, to be ensure the pin isn't floating.HarryHApril 15, 2024 at 8:24 PM -
-
That's nice.
Also if you got the outdated add-on download not from my repository, you are right that "issues" is disabled. I'm currently undecided, if I should enable this opportunity or not. From the workflow view it would be the right way if someone like you can use it, but I have not the time to moderate this. -
Downloaded from github right now , but latest libreelec version gives installing error.
Until now I only provided ready to install add-on packages here (attachments are at the end of the text):
PostRE: [RPi4] Argon One Case Shutdown
Please be aware:
I'm not a developer of KODI Add-ons. This is only a result of someone who had the wish to get the add-on work again with LibreELEC 10 and later.
Argon ONE Control
2025/04/11 Version 1.1.10 (recommended): Please note the updated documentation.
Provides a GUI and installs a service to manage Argon ONE case features including the power button, fan speed, and the Argon IR remote.
What it does:- supports LibreELEC 10 / 11 / 12 / 13
- supports Argon ONE V1/2 (RPi4)
- supports Argon ONE V3
HarryHAugust 2, 2023 at 9:57 PM
So I don't really know what you are talking about and need more details with an exact version and, if necessary, a link to the debug log.
Perhaps you tried the original version 0.0.1 from Argon, which is known that it not working with versions, which are newer than LibreELEC 9?