Posts by HarryH

PANiCnz ,

your are the second which reports this behavior with Argon One V3 in combination with 0.0.7. So there seems really to be an issue within the current code.
Currently I can't reproduce with my V2 case... it could takes longer to find the root cause.

As long the CPU temperatur is below the first threshold, the fan should be off. Pulsing is possible if the current temperature is around the threshold. 42c is far away from the 55c default value. I fear I have possibly insert this bug as I switched over to the Argon Register Helper methods, which has a mechanism included to differentiate the firmware versions.

From the testing with Argon V3 case exists a version 0.0.6d, but this version should only be used with LE12 + Argon One V3 cases, because the commands were changed for the new firmware. I don't know if there are also V2 cases with this type of firmware in the wild.

Edit: This bug was fixed beginning with v.0.0.8. Please update to a current version of the add-on.

Thank you guys for your research! Because of that I could successful update the ArgonForty Device Configuration Add-On.

Add-On was update to version 0.0.7.

• make it work with LE12 nightly builds after 2023/11/16.
  Raspberry Pi Tools - GPIOZERO - LE12 Issues
• supports the new firmware version of the Argon One V3 (RPi5) case

Hi chewitt ,

As you suggested, I opened a repo on GitHub. There are the changes for both versions (0.0.4 and 0.0.5). I actually didn't want to take this step until I could successfully build the plugin from scratch, without using the old ZIP as a basis...

HiassofT ,

thank you for the information and providing the updated rpi-tools add-on.

ghtester ,

thank you for the direction to gpiozero documentation. I have prepared a migrated version of the ArgonForty Device Configuration add-on . But I need feedback from a brave tester with an LE12 nightly build. Killom , do you will give version 0.0.5 a try?

@Guis,

If blueribb's hint doesn't work and the files aren't encrypted (unlike petediscrete feared), you might want to try TS-Doctor. This tool is not free, but you have a trial period. The files are only remuxed and not converted. The time required is not that great and the quality of the video and audio stream remains unaffected.

frankvw ,

do you have checked if it works if you limit the security settings in your router to WPA2? The important thing is to test it without PMF (Protected Managment Frames/802.11w). Is there an option to disable this at the Huawei AX3?

tomstephens89,

as far as you use LibreELEC 10+, you can use the add-on: ArgonForty Device Configuration add-on
There is the option for fan control included and you have a GUI for the settings. The only thing is, it takes a some seconds (first time it needs a reboot) until new fan settings are applied.

Maybe this is exactly what you expect...

myshit,

I am in the lucky situation that the combination Argon One + Pi4 worked flawless out-of-the box. According to the PiHut documentation it seems to make a difference which HDMI port is in use.

https://support.thepihut.com/hc/en-us/articles/360008687257-No-HDMI-output-on-my-Raspberry-Pi-4

With LibreELEC 11.0.3., I get vc4-hdmi-0 as primary audio device, but my cable chain is (Pi4)Argon One M2 -> AVR-> TV (1920x1080). I don't know if it's only because the auto-detection of your displays EDID is currently not working right, but it looks to me that your HDMI cable is connected to the second HDMI port.

HDMI can be erroneous, because of many pitfalls. VLouis and Da Flex comments are directing to the most well-known root causes of issues with EDID, handshake, maximum transfer speed (4K related) and so on.

- bad cabling (cheap manufactured cables, not certified, not 4K ready ...)

- buggy software/hardware at display device or AVR (TV, monitor, projector)

- production issue of circuit board in the Argon One case

- driver issue

- high frequency emitting devices in the near like USB3, WLAN

...

Additional I had made the experience that a powerless device which is connected at the same time to the AVR via HDMI can disturb CEC, because it seems to pulls down the +5V or the signal level at HDMI.

The Argon One casing seems not free of additional issues, some users had to force the EDID information. Do you have tested yet the 4 lines at the same time in your config.txt?

Thread

RPI4 No HDMI Sound using Argon One Case

Just got my RPI 8GB today and flashed LibreELEC on it and installed Argon One script on it. I have already set hdmi_drive=2 and there is still no sound. When I switch to Analogue and plug in a headphones and switch the Audio Output Device to HDMI / HDMI + Analog, I get sound only on the headphones . When I disassembled and used the RPI4 without the case, the audio seemed to work fine. This only happens when it is connected to the Argon One Case. Really appreciate any help

Kodi Log: …

prispither

June 1, 2020 at 4:22 PM

Raspberry Pi Documentation - The config.txt file

The official documentation for Raspberry Pi computers and microcontrollers

www.raspberrypi.com

hdmi_drive=2
hdmi_ignore_edid=0xa5000080
hdmi_mode=16
hdmi_group=1

I‘m not sure if it’s a good idea to start this discussion here and not in separate thread...

Do you have ensured that you has connected to the first HDMI 0 port? If yes, please check if the contacts at the plugs and the sockets looks good.

Did it work with LibreELEC 11.0.3 before or just an older version?

myshit,

You're welcome. Nice to read that it's working for you now.

Da Flex
I have reviewed the python scripts again. To be technical correct I should revise my posting (#28)

• the microcontroller supports Reboot (double-tab at power-on button) and not RESET
• the microcontroller signals 2 different requests (Reboot, Shutdown) at PIN7 of the Pi4 board
• during shutting down a script sends 2 messages at SMBus (i2C) back to the microcontroller
  - first message : stop fan
  - second message: initiate power off, cut when the serial pin goes 'down'
  More information about this are available here: https://github.com/Argon40Tech/Argon40case

These things are only working if a service is running in the background to make cycling checks at PIN7 for new message from the microcontroller. The shutdown script is a hook during the LibreELEC OS shutdown: https://wiki.libreelec.tv/configuration/startup-shutdown

Hi Da Flex ,

I hope I can remind me right, because these information are 2 years old...

There are at least 2-3 revisions of the Argon One case. The newer ones even have an infrared receiver on board. The power-on button is not directly connected to the Pi. In between is a circuit board with a microcontroller. This is responsible for switching off the power supply to the Raspberry after shutting down. The microcontroller recognizes the signal at the power-on button and can also trigger a RESET (different PIN on the Raspberry) by pressing the power-on button twice in quick succession. If you press this button longer than 3x seconds, the Raspberry will be shut down and the power will be switched off after a delay. It may be that this behavior depends on the firmware version of the microcontroller and could be different with the first batch of the casing.

If you shut down the Raspberry via OS, the microcontroller in the Argon One lacks the information that its allowed to cut the power supply. Therefore, after an orderly shutdown, the red LED at the front, behind the semi-transparent plastic cover, remains on. However, the microcontroller also knows a return channel via PIN on the UART interface. This PIN changes its logic level after shut down of the Pi and the microcontroller starts the process to cut the power of the Raspberry Pi. This has to be configured specifically on every OS and with every startup. It's part of the ArgonForty Device Configuration add-on, for example. Alternatively, there are some other scripts/daemons that do something similar.

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/05 Version 1.1.8 (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 (RPi5)
• 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 at least.

Important: The add-on download has been moved to GitHub: Download Please use the latest version of the add-on to ensure that the known bugs have been fixed.

For historical reasons only: If someone stays on LE10 and the last versions really don't work, they can try version v0.0.4. I have left the download of the outdated version as an attachment just for this case.

Known Issues:

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.

Solution:

To compensate that, the add-on has been repeatedly optimized to decrease the shutdown time to below 8 seconds. Depending whats currently installed and running in KODI it need sometimes longer, then the shutdown will not be graceful and data corruption is possible in the worst case.

This behaviour only occurs if you use the power button on the remote control or on the back of the case to switch off. If the KODI power menu is used to switch off, the power cut will triggered at the very end (+10 seconds).

Another workaround for the following scenario:

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

Breaking change:

Additional I have switched from lircd to rc_maps/keymaps (thanks to adam.h. for providing the files). If you use a self made remote control profile for your remote control, please make a backup of your remote control configuration and/or place a lock file before installation to prevent overwriting:
touch /storage/.config/argon40_rc.lock

Source:

The original sources are from there: GitHub Argon40Tech and here: Installation package version 0.0.1

I have forked (26.10.2023) the Argon40 add-on repository and pushed my changes to this repository: GitHub Argon ONE Control

Installation:

Quick installation (recommended for LE13)

Search for "Argon ONE control" within the LibreELEC add-ons 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.

Please have a look for more details at the linked documentation, especially if you have already an older version of the add-on in use.

Manual installation

The installation process will try to add 3 lines to the config.txt to enable the needed modules for I2C 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.

A few things to do:

• Upload one of the linked zip files (GitHub release asset: libreelec_argononecontrol_x.x.x.zip) 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 browse to the folder where you uploaded the zip
• select the ZIP file and press OK
• after installation: Ignore the "Device Configuration Error" teaser message and reboot, so that the modules for UART and I2C are activated

Within Add-ons list, the Argon ONE Control (fka: ArgonForty Device Configuration) add-on should be available now. There you can configure the fan settings and the shutdown should work properly now. Please be patient, it will take a few seconds for the LED to goes off.

Important: Recent versions are available at GitHub first, followed by publishing via LibreELEC add-ons repo: Download

myshit ,

You will need some additional scripts that are part of the Argon Pi addon. Since the add-on was no longer maintained after the initial commit on GitHub, I ported it myself to make it work with LibreElec 10+ two years ago. I haven't touched this since then, but it still works with LibreElec 11 and you can also configure the fan speed.

I'd have to look up the git repo and installation package. If my newly created user allows this at all, I could make it available here.