Posts by HarryH

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.

<?xml version="1.0" ?>
<settings version="1">
	<section id="service.test">
		<category id="generic" label="Generic" help="Help!">
			<group id="1" label="">
				<setting id="file" type="video" label="File" help="Select the video file">
				</setting>
			</group>
		</category>
	</section>
</settings>

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:

  Code

  DEBUG:   [          189968]     SetCurrentButton right (4) D:0ms cur:17f
  DEBUG:   [          189968]     key pressed: right (4) current(ff) duration(0)

• 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.

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:

Post

RE: 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…

HiassofT

May 2, 2024 at 11:10 AM

Version 1.1.0 released:

• add-on icon changed to follow LE style (thanks chewitt for providing this)
• issue #5: fan art modified to be more generic
• issue #4: localization for Italian added
• localization for German added

Edit:

Version 1.1.1 released:

• some typos and translation errors fixed

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-device

ArgonForty Device Configuration Add-On for LibreELEC - HungerHa/libreelec_package_argonforty-device

github.com

Hi Baallrog,

please use the updated scripts from here:

Post

RE: 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.

HarryH

April 15, 2024 at 8:24 PM

I think something like that should work for you:

curl -X POST -H "content-type:application/json" --data '{"command":"componentstate","componentstate":{"component":"ALL","state":false}}' http://192.168.133.114:8090/json-rpc

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.

Quote from firefox

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):

Post

[RPi] Argon ONE Control Add-on (Release Notes)

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/05/24 Version 1.1.12 (recommended): Please note the updated documentation.

What it does:

Provides a GUI and installs a service to manage Argon ONE case features including the power button, fan speed, and the Argon IR remote.

• supports LibreELEC 10 / 11 / 12 / 13
• supports Argon ONE V1/2 (RPi4)
• supports Argon ONE V3

…

HarryH

August 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?

Version 0.0.14 beta 2 released:

• avoid overwriting the existing rc_maps configuration, just add Argon REMOTE
• automatically switch between Celsius/Fahrenheit, depending on regional/temperature setting
• language file refactored
• regression: fan always-on setting and emergency fan (90°) doesn't worked
• switched to official add-on versioning

With this version in the most cases it shouldn't needed anymore to create the lock file to protect the own remote control configuration.
But for the worst case, for example if someone is using a lircd.conf file, the lock file support remains.

You are welcome. By the way, for the fan control of that case you can install this Addon: RE: [RPi4B] Argon One Case Shutdown

But please do place the lock file there before the Addon installation, to ensure that your current remote control configuration is not affected:
touch /storage/.config/argon40_rc.lock

The positioning of usb_max_current_enable=1 within the config.txt is not really important, but its good placed below the exiting lines in the [all] scope. It should be case sensitive, so you should use lower case for parameters in the config.txt, but UPPER CASE for parameters of the bootloader config.

You can check the current bootloader config with:
rpi-eeprom-config
or
vcgencmd bootloader_config

and edit with:
rpi-eeprom-config -e

That information is very important, because you need this:

bootloader config / EEPROM:
PSU_MAX_CURRENT=5000

config.txt
usb_max_current_enable=1

Explanation here: RE: LibreELEC 12.0 on Raspberry Pi5

Please keep in mind, that the RPi5 itself needs more power, than previous generations. If the system is very CPU agile and not in the idle state, then attaching of USB devices could be the worst case for the power supply and/or the PMIC.

If your USB HUB is really a powered one, you should try to only attach 1 tuner to the RPI5 directly and 2 tuners at the powered HUB.

Only to be sure, you attached the RPi5 power supply directly to the RPi5 pcb, right? You doesn't use a additional case or gadget like RemotePi board ?