Posts by HarryH

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

    Version 1.2.0 released:

    added fan control support for ONE V5 with 2 different mechanism:

    • Activate RPi5 system fan detection for ONE V5/NEO 5/Raspberry Pi Active Cooler
      Works via sysfs PWM interface (default, if system fan could be detected on add-on startup):
      Should behave like the ONE V1/2/3 fan control with immediate changes after settings changed in GUI and supports different temperature sources.
    • Force support for ONE V5/NEO 5/Raspberry Pi Active Cooler via cooling_fan overlay
      If enabled, uses the generic RPi5 fan control at the kernel level with the parameters in the config.txt file. Disables the integrated fan control of the Argon ONE V1/2/3! Advantage: Works independently of Kodi. Disadvantage: With this method, a restart is required after each change to the fan/temperature settings in the GUI for the changes to take effect.

    Unfortunately, the Weblate service is currently not working as intended, so the new GUI menu strings are only available in English and German. If there is progress with Weblate (which could take some time) and/or users provide the updated translation file in their native language, some language updates for the add-on will follow.

  • Clarification of usage of PKG_VERSION / PKG_VER for add-ons

    Hi heitbaum

    because of your comment at https://github.com/LibreELEC/LibreELEC.tv/pull/10658 I'm a little confused. What is the intended usage of PKG_VERSION and PKG_REV?

    Currently the build process combine both informations like PKG_VERSION + PKG_REV:

    • PKG_VERSION="1.1.13" + PKG_REV="0" results to addon version="1.1.13.0".

    If both symbols are set, why do you want that the PKG_REV should be increased as well? I'm trying to understand, because in the past I started every time with "0" as long the add-on with the new PKG_VERSION was never build before and uploaded afterwards to the repo. if just the build process needs some changes (without changes of the source package), the PKG_REV can increased additional to force a new version in the add-on repo.

    I have seen that you have increased both symbols at the same time: https://github.com/LibreELEC/LibreELEC.tv/pull/10653/files
    , but currently couldn't recognise the reason for. For example the filebrowser would results in a version jump: 2.44.2.4 -> 2.45.0.5

    Usually increasing PKG_VERSION would be enough to trigger a new add-on version, because 2.45.0 is already a successor of 2.44.2. https://kodi.wiki/view/Addon.xml#Core_elements

    Do I missed some other ruleset?

    EDIT:

    Okay, I have now seen in the add-on repo that the creation process for most (but not all) add-ons behaves differently from the current one for argononecontrol and hides the source version behind a new add-on version that corresponds to the ADDON_VERSION symbol. So I think your assumption was that this is also the case with argononecontrol. Now I understand your objections/intention, but ends with some new questions:

    • Should I from now increase every time the last digit (PKG_REV) within the add-on repo of the corresponding LE version, also if it's technically not necessary?
    • May it be okay for the future to still have a speaking add-on version, other than the LE 12.x.x.x/13.x.x.x one? Or it's planned/necessary to make it sometimes equal? Reason: The current behaviour is welcome, because the current scheme generates no conflicts with the manually installed versions for testing from GitHub.

    Regards,

    Harry

  • [RPi] Argon ONE V5 Case

    I am currently working on version 1.2.0 of the Argon ONE Control add-on, which optionally supports the ONE V5 fan or any RPi5 with a fan installed on the official fan connector. I need a little feedback before the general release in the LE add-ons repo, if possible. If anyone is interested in testing this with an RPi5, please send me a message or leave a comment.

  • [RPi] Automatic Resolution and Refresh Rate Adjustments

    Usualy you should fill the mode whitelist with the resolutions/refresh rate combinations you want that KODI switches to if the media format matches. The available combinations depend on the EDID data provided. Maybe there are some limitations which combinations are supported by RPi4/5 hardware.

    It should be enough to set: "Settings \ Player \ Videos \ Adjust display refresh rate = Start/Stop". This prevents that KODI switches back to the default if OSD is open during playback and ensures the best match of your whitelist is used.

    EDIT:
    race condition, HiassofT was faster... ;)

  • [RPi4] Constant access on external drives

    Hi guys, please remain relaxed. There is no reason to curse the case itself, this time. ;)

    ajne
    I will look into this, but I need some time to simulate your configuration in order to find a more practical solution. In the meantime (untested), you can change line 432 in this file:

    nano /storage/.kodi/addons/service.argononecontrol/resources/lib/argon.py

    from val = argonsysinfo_getmaxhddtemp()

    to val = 0

    Restart KODI afterwards or disable/enable the addon to activate the changes.
    systemctl restart kodi

  • HDMI input switching

    Your TV set switches to the ‘active source’, which is normally intended. How it reacts on simultaneous "active sources" depends on your TV. As a rule, the active source that is reported last wins. This could lead to the situation that you have to wait until the satellite receiver reports itself as an active source after startup. You could also start this satellite receiver only and patiently wait until this activates the TV.
    With some TVs, you can set a specific external input as the standard for watching television.

    Maybe a mitigation is possible if you disable "Switch source to this device on startup" and/or "Wake devices when deactivating the screensaver" in the "CEC Adapter" settings of LibreELEC: Settings -> System -> Input -> Peripherals -> CEC Adapter

    However, this could also lead to some problems, e.g. that the remote control via CEC not working properly or partially only because another CEC device is being controlled or similar.

  • [RPi5] CEC not working

    Stuntel ,

    You should make sure that you use the HDMI port that is closest to the USB-C port. Then CEC will work again. 12.0.1 temporarily supported CEC on both ports, but there were too many unresolved issues, so support was limited to the first HDMI port.

  • [RPi] Argon ONE V5 Case

    It's not currently on the ToDo list as the V5 has nothing in common with the previous ONE enclosures other than the name and the manufacturer. In addition, I don't have an OLED device to test the function, and I would need capable testers with the ONE V5 case to get useful feedback in a timely manner during the development/debugging phase.

    As far as I can see in Argon40's implementation with their scripts, the OLED requires additional Python modules like Luma.OLED and some binaries provided by Argon40. The latter without licence information. This hinders an integration, not only the additional abundant effort.

    What expectations would you have regarding OLED support? Only the few cyclically repeated system information as with the argon1v5.sh script?

  • [RPi4, LE12.0.1] Autostart.sh with python script for fan control won't work

    Please keep in mind that LE is reduced to just the required components for KODI and hosted in a readonly root filesystem. All additional things (more than a simple script), which are not already available in the base image or as add-on, you want to install should be a package. This can be an add-on package or directly included in a self build image. Many things are documented in the Wiki, at GitHub and also in the code itself.

    As for your example with the Python background process, you can set it up manually as you have already done, or create an KODI add-on (script or service) that does the same. Adding new additional Python libraries can be significantly more difficult and depends heavily on how experienced you already are with compiling and packaging Linux packages.
    Maybe I'm just misunderstanding you. But your wishes/goals sound very ambitious and require a good understanding of hardware/specialised knowledge in some areas. There is no such thing as a simple all-in-one guide. You should also not ignore the fact that not everything can be realised or is necessary on every hardware platform.

    Some starting points:

  • [RPi4, LE12.0.1] Autostart.sh with python script for fan control won't work

    You are welcome. It was just a guess on my part that you also moved the fan_control.sh shell script to the subfolder called ‘scripts’. You are right that it makes no difference where it is located as long as the path in the autostart.sh script matches.

    If you set FAN_OFF = 0, the fan should be stopped until the CPU temp value cross the threshold of MIN_TEMP. So you could lower the value MIN_TEMP near to the idle temperature for testing purposes, to trigger ON/OFF earlier and check the functionality of the script.

  • [RPi4, LE12.0.1] Autostart.sh with python script for fan control won't work

    Because it relies on gpiozero you could be affected by this (RPi gpiozero): https://libreelec.tv/2025/01/22/libreelec-nexus-12-0-2/

    To find out where the problem comes from, what is the output of python3 /storage/scripts/fan_control.py ? Are there any exceptions/error messages? Or is this what you mean by?

    Quote

    I was able to control my fan just fine from the interactive python so I know I have everything hooked up correctly.

    If this works, the next step should be to test the wrapper script:
    sh /storage/scripts/fan_control.sh start and sh /storage/scripts/fan_control.sh stop