Provides a GUI and installs a service to manage Argon ONE V1/2/3 case features including the power button, fan speed, and the Argon IR remote.
Please note: The Argon ONE V5 and NEO 5 are cases without an additional microcontroller for fan control or power switch events. Therefore, this add-on is optional here, for example, if a graphical user interface for the kernel fan control settings (cooling_fan overlay) or an alternative fan control is desired.

This will also enable I2C, IR receiver and UART.

Important: Starting with version 1.1.6 the add-on has been renamed to "Argon ONE Control". The add-on ID has been changed as well. This was a prerequisite for the integration of this add-on into the LibreELEC add-ons repo. For better user experience if beginning from scratch, its now possible to install it from there directly, please see "Quick installation" below. To distinguish my fork of the add-on from the official, currently outdated version 0.0.1 of Argon40, I have also changed the name of the add-on. Unfortunately, as a one-off event, this change requires the removal of an existing version with the old add-on ID in advance so as not to collide with running background processes.

• supports LibreELEC 10 / 11 / 12 / 13
• supports Argon ONE V1/2 (RPi4)
• supports Argon ONE V3 (RPi5)
• supports optional Argon ONE V5 / NEO 5 / Active Cooler (RPi5 fan control only)
• probably also supports Argon Fan HAT, Argon ONE (RPi3) but untested (feedback is welcome)
• enables IR receiver (V2/V3, or if self added to V1 pcb)
• enables Argon REMOTE support (rc_maps + keymap)
• fan control with fan curves CPU, SSD/NVMe, GPU and PMIC
• graceful shutdown (power button commands: Reboot, Shutdown ...)

For full support of the power button commands with a RPi5, please use LE12.

If someone is using LE10 and it really doesn't work, they can try the outdated version v0.0.4: LibreELEC Thread

There is a limitation in the Argon ONE V1/2/3 case firmware.

After the power button at remote control or the button (held for > 3 seconds, but < 5 seconds) on the back of the case was pressed, KODI including all OS processes only has ~10 seconds to shutdown properly! Once initiated, the 10 seconds power cut timeout can't be interrupted and is perhaps only with another case firmware correctable.

To compensate that, I have optimized v0.0.10+ as far I currently could to decrease the shutdown time to below 8 seconds. Since LibreELEC 12 it taked much more time to shutdown the KODI process. The cause of the delay seems the switch to lgpio / gpiozero as the default python modules to interact with the GPIO chip. A KODI add-on thread with lgpio / gpiozero imported can't be terminated within 5 seconds. KODI tries to kill this thread and afterwards stucks until a timeout of 30 seconds.

Starting with v1.1.4 the add-on supports gpiod as an alternative way to interact with the GPIO pins. This may it possible to stop KODI within 5-6 seconds and properly shutdown via power button of the remote control again!

During the review phase of the integration of this library into the official LibreELEC add-ons, it was decided to integrate the Python bindings (gpiod) into the system-tools add-on instead of the rpi-tools add-on to make it available for all platforms, not just the RPi. As of v1.1.5, both variants are supported.

NOTE: The change will only take effect if KODI has already been started with the updated rpi-tools/system-tools. Restart LibreELEC after updating the rpi-tools/system-tools.

The PRs for system tools have been applied and manual installation is no longer required. Only for historical reason you can find an update version of rpi-tools in the release area of version 1.1.4. which already contains gpiod.

• virtual.rpi-tools-12.0.0.1.zip for LE12
• virtual.rpi-tools-12.80.1.1.zip for LE13 nightly builds

Note: Depending on what is currently installed and running in KODI, it sometimes takes longer than 10 seconds (including the final processes of the underlying operating system), then the shutdown will not be graceful and in the worst case data corruption is possible.

The safety way: If the power menu of KODI is used to shutdown, the power cut is initiated just at the end (+10 seconds).

There are some reports on the Argon40 forum that the fan control scripts they provide no longer work with the Argon ONE V1 cases since the new command set with register support was added for the Argon ONE V3 cases. I cannot verify this, and there is no feedback on whether this is really the case and switching off the register detection definitely helps. A compatibility mode was therefore added in version 1.1.9, which explicitly deactivates the detection of register support. If you are one of the early adopters with a V1 case (with micro HDMI outputs at the back of the case) and the fan control or the shutdown process already isn't working right:

• Enable "Activate compatibility mode for ONE V1"
• Shutdown KODI/LibreELEC
• Make sure that the case is powerless (unplug PSU) for some seconds
• Start LibreELEC with compatibility mode enabled

Situation: Remote control power button pressed → 10 seconds timer starts -> shutdown is initiated → red LED turns off, but it seems that it doesn't respond to the power button on the remote to get it on again.

Please try in this situation (unsuccessful shutdown):

• The red LED must be off
• Press the power button on the remote control
• Wait 10 seconds (MCU cuts off power internally)
• Press the power button on the remote control again to boot

I have switched from lircd to rc_maps/keymaps (thanks to adam.h. for providing the files) to use the modern way with ir-keytable. If you use a custom lircd.conf for your remote control, please make a backup of your remote control configuration and/or place a lock file before installation of the add-on to prevent overwriting.

If there is already a rc_maps.cfg file in the /storage/.config directory, the add-on checks if the needed line to include the argon40.toml file exists. If necessary, an attempt is made to append the needed line.

In the worst case scenario, to prevent the add-on from changing the IR configuration, all you need to do is place an empty lock file in the /storage/.config directory.

touch /storage/.config/argon40_rc.lock

• Do I need this add-on for an ONE V5 case? In short: No.
• If this add-on is not needed with ONE V5, why is it supported as an option? Over the course of this add-on's history, it was renamed “Argon ONE Control,” which implied to some that it was compatible with any Argon case named ONE and was unnecessarily installed on the V5. Originally, I wanted to decline support for V5, as newer kernel versions support its fan control by default because it uses the official RPi5 fan connector. To give the add-on with the ONE V5 a purpose, version 1.2.0 and higher offers a graphical user interface for the kernel fan overlay and, in addition, a replacement for it that behaves identically to the ONE V1/2/3.
• Are additional features of ONE V5 such as OLED etc. supported? Currently not. Fan control only.
• Can I use this add-on with an RPi5 without using an Argon40 case? Yes, if the RPi5 fan connector is populated with a working fan. However, keep in mind that if you are already satisfied with the fan control provided by the kernel, you will be installing additional software and its associated footprint without any additional benefit to you.
• If I don't have ONE V1/2/3, is there anything I need to be aware of? Not really, but you could disable monitoring of the power button to minimize the CPU usage of the background service.
• I played around a bit with the “Force support for ONE V5...” setting, but I have a ONE V3 and now I feel like the fan control is no longer working. Please check the config.txt file and remove all lines in the “cooling_fan” section, as these lines cause the fan to be expected at the RPi5 fan connector and not connected to the MCU of the ONE V3. Alternatively disable both "V5" switches and restart KODI.
• I have "ArgonForty Device Configuration" add-on already installed. Should I remove all installed versions of that before switching to "Argon ONE Control" add-on? Yes, that is the recommended procedure.
• Can I damage the LE installation if I switch back to an version before 1.1.6? No, but don't forget to remove "Argon ONE Control" first.
• Will I permanently damage my system if I accidentally install both add-on versions at the same time / or forget to remove them beforehand? No, but it could result in non-functional fan control or some other misbehaviour. Solution: After one of the add-ons has been removed, followed by a reboot, all things should be fine again.
• Are the versions from GitHub and from the LibreELEC add-ons repo exchangeable? Yes.
• What are the difference between the GitHub version and from LE repo? Only the version metadata, nothing else. Functionality is the same, as long the first 3 digits are identical. Same source code.
• Are there restrictions if I install the version from GitHub manually? Yes, but not a deal breaker. The add-on will not automatically updated/changed to the version from LibreELEC repo. But the add-on update will be anounced there as well and you can switch to the repo version if you chose there "Install all updates" and not only use "Install auto updates only".
• Will the add-on updated to latest version automatically? Yes, if the current installed add-on version is one of the versions from LE add-ons repo.
• Will future versions be available on GitHub and in the LE repository at the same time? No, or only approximately, because of the required workflow. With LE's approval workflow and subsequent build process, the GitHub package will always be available first.
• How can I determine whether I am using the version from the LE repository? Look at the add-on information via the context menu in the KODI Add-ons section, where ‘LibreELEC Add-ons’ should be displayed as ‘Origin’. The LE add-ons version also contains the fourth digit with the LE package revision.
• Where can I find the add-on version information? Navigate to the KODI Add-ons section and select the add-on, but don't press OK. Use the context menu and go to "Information". There you can find the current installed version and also the switch to available versions in the LE add-ons repository is possible there.
• Will I lose my customised settings if I update/downgrade the add-on? Normally not. But if you switch between versions with different add-on IDs, yes.

Search for "Argon ONE control" within the LibreELEC add-on section below "Program add-ons" and install the add-on. All requirements will be downloaded and installed automatically. If you install this add-on the first time, a reboot is required afterwards to activate all interfaces like I2C, UART and IR. Due to the versioning of the automatically created LibreELEC add-ons, a LE package revision number starting with 0 is also added - for example 1.1.6.0. The first 3 digits correspond to the version of the add-on.

ATTENTION: If you have already installed a version older than 1.1.6, it is necessary to remove the older version first. If you have customised the settings to your personal requirements, these will unfortunately be lost in this way. This is a one time event and neccessary because of the required change of the add-on ID. The technically possible simultaneous installation of both add-on versions (due to the different IDs) will otherwise lead to malfunctions or non-functioning add-ons! Versions equal or newer than 1.1.6 can be installed via LibreELEC repo or from the GitHub release packages.

In the following installation instructions, the term "ZIP file" is used for simplicity. Because there seems to be room for misinterpretation and to avoid future confusion: It doesn't mean the code download button from GitHub, to download the whole source code repository content!

Please use one of the ready to install add-on archives with the name pattern libreelec_argononecontrol_x.x.x.zip from the releases.

The installation process will try to add 3 configuration lines to the config.txt to enable the needed modules for I2C, IR and UART. This part is not bullet proofed, because it looks only for the first line. It skips the needed modification if the line "dtparam=i2c=on" is already there. Therefore it could be better to make a backup of /flash/config.txt before to see the different.

A few things to do. The first 3 steps in square brackets are optional and are only required if the dependencies cannot be resolved automatically and can usually be skipped. If they are needed they can be done manually within the add-ons menu section of the KODI GUI.:

• [ install RPi Tools (LibreELEC Repo -> Program Add-ons) ]
• [ install System Tools (LibreELEC Repo -> Program Add-ons) ]
• [ Reboot (necessary before installing the Argon Add-on so that the system tools work properly) ]
• Upload the ZIP file to /tmp, /storage or another place where you have access via KODI
• Allow installation of Add-ons from external sources: Enable "Settings->System->Addons->Unknown sources".
• In the main menu within Add-ons select "Install from ZIP file", confirm the security question and switch to the folder where you uploaded the ZIP file
• Select the ZIP file and press OK
• After the first installation: Ignore the “Device Configuration Error” teaser message and reboot to enable the UART, IR and I2C modules

Within Add-ons list, the Argon ONE Control add-on should be available now. There you can configure the fan control. The shutdown and reboot (double tab) should work now too. Please be patient, it will take a few seconds for the LED to turn off.

• Clone the LibreELEC.tv repo

  git clone [email protected]:LibreELEC/LibreELEC.tv.git

• Change into the LibreELEC.tv directory

  cd LibreELEC.tv

• Create the add-on package directory

  mkdir -p packages/addons/service/argononecontrol

• Copy the package.mk into the add-on directory

  wget -O packages/addons/service/argononecontrol/package.mk https://raw.githubusercontent.com/HungerHa/libreelec_addon_argononecontrol/refs/heads/master/package.mk

• Start the build process

  PROJECT=ARM ARCH=aarch64 DEVICE=ARMv8 scripts/create_addon argononecontrol