Power button not working at all and fan speed always at 100%?

Sure. This is the content:

pi@iobroker:/boot/firmware $ cat config.txt

# For more options and information see

# http://rptl.io/configtxt

# Some settings may impact device functionality. See link above for details

# Uncomment some or all of these to enable the optional hardware interfaces

dtparam=i2c_arm=on

#dtparam=i2s=on

#dtparam=spi=on

# Enable audio (loads snd_bcm2835)

dtparam=audio=on

# Additional overlays and parameters are documented

# /boot/firmware/overlays/README

# Automatically load overlays for detected cameras

camera_auto_detect=1

# Automatically load overlays for detected DSI displays

display_auto_detect=1

# Automatically load initramfs files, if found

auto_initramfs=1

# Enable DRM VC4 V3D driver

dtoverlay=vc4-kms-v3d

max_framebuffers=2

# Don't have the firmware create an initial video= setting in cmdline.txt.

# Use the kernel's default instead.

disable_fw_kms_setup=1

# Run in 64-bit mode

arm_64bit=1

# Disable compensation for displays with overscan

disable_overscan=1

# Run as fast as firmware / board allows

arm_boost=1

[cm4]

# Enable host mode on the 2711 built-in XHCI USB controller.

# This line should be removed if the legacy DWC2 controller is required

# (e.g. for USB device mode) or if USB support is not required.otg_mode=1

[all]

enable_uart=1

pi@iobroker:/boot/firmware $

The config.txt is looking good. Perhaps you really have a defective fan or case pcb. The only remaining chance is, that the argononed service initiate some trouble during boot. To exclude that, you should disable the service and try it after a cold boot again.

  • systemctl disable argononed
  • shutdown
  • important: remove the power supply from the case for 10 seconds or more
  • plug the power supply into the USB-C port
  • press the power button at the case
  • i2cdetect, to ensure the MCU is reachable
  • i2cset -y 1 0x1a 0x00 (no other command) to stop the fan

Hi,

Thanks for all informations provided here.

I have an issue with fan remaining at 100% after start (normally it stops after few seconds). It occurs sometimes, 1 time over 10 and i don’t understand what is failing.
I use Argon ONE V2 on PI4 and librelec distribution.

With your help i’m testing a workaround with an autostart script :
nano /storage/.config/autostart.sh

(

i2cset -y 1 0x1a 0x00

)&

chmod +x /storage/.config/autostart.sh

@stefil
if you have only a software issue and not a hardware related one wit LibreELEC:

Remove the current version 0.0.1 of the Add-on if you have installed (aka: ArgonRemote.zip). And try your luck with this Add-on version v0.0.12.

Attention: Independent of this Add-on there exist a MCU firmware related issue/limitation, that if you use the power button to signal “shutdown”, The operating system (LibreELEC) remains only ~10 seconds to shutdown properly. With LE12 it takes much longer to ending KODI, so it will never a graceful shutdown and can results in data corruption or some strange behavior regarding power off/on the device again.

@HarryH
I did some more tests today.
The service for argonone was disabled. Rebooted. Power unplugged for 30mins. Started with power on (no button needed - as jumper is set accorlingly to power on directly). Stopped iobroker to make sure no influence from this. And then did the following with Firmware V2 and V3 commands


pi@iobroker:~ $ i2cget -y 1 0x1a 0x80
0xe7
pi@iobroker:~ $ i2cget -y 1 0x1a
0xe7
pi@iobroker:~ $ i2cset -y 1 0x1a 0x16
pi@iobroker:~ $ i2cget -y 1 0x1a
0xe7
pi@iobroker:~ $ i2cset -y 1 0x1a 0x64
pi@iobroker:~ $ i2cset -y 1 0x1a 0x01
pi@iobroker:~ $ i2cget -y 1 0x1a 0x80
0xe7
pi@iobroker:~ $ i2cset -y 1 0x1a 0x80 0x64
pi@iobroker:~ $ i2cget -y 1 0x1a 0x80
0xe7
pi@iobroker:~ $ i2cset -y 1 0x1a 0x80 0x00
pi@iobroker:~ $ i2cset -y 1 0x1a 0x80 0x64
pi@iobroker:~ $ i2cset -y 1 0x1a 0x00
pi@iobroker:~ $ i2cget -y 1 0x1a
0xe7

The result: only the command

i2cset -y 1 0x1a 0x00

set the fan to stop.
Any other value like 0x01 or 0x08 or 0x16 or 0x64 set the fan to 100%

The first impression is that it looks normal. If you do not have a V3, the “old” command set must be used.

I don’t think that the fan use a 100% duty cycle every time if you set values less than 0x64. Are you familiar with PWM? Unfortunately, you can’t expect to get the factory installed fan silent without stopping the fan. There are various reasons for this:

  • fan size 30mm x 30mm requires high revolution per minutes to create an air flow
  • the installation position
  • the air flow is not free and creates streaming noises
  • the MCU internally assigns the I2C values 1 to 100 to the DutyCycle 30 to 100 percent (found somewhere in the forum, no official information)

Thank you @HarryH for all this information and the passion to support all of us. I really appreciate it much.
But does 1% fan sounds so close as 100% fan does? Unfortunately I have no meter to measure the electrical PWM signal at the fan.
But I have a Spectrum Analyser to listen more detail. And yes, you are right. There is a small differentiation.
This is 0% fan. Quite env:

This is 100% fan:

and this is 1% fan:

What I also realized is that when the Homeautomation iobroker is running on this host it immediately starts again the fan when it was stopped by 0x1a 0x00. For sure the argonone service was stopped before.
When the iobroker is stopped (iob stop command) the fan stay at 0%.
So this is next i need to check. I also have a n USB DECONZ conbeeII stick connected and a service running on this host.

Sum up: I still have side effect by iob and Deconz. Fan speed react on the commandos even you can hear it much between 1% and 100%. I will also check the button at the argon device too

It looks like you must find a way to prevent that iobroker is steering the I2C bus. Do you have some HATs installed or is the PIN header free ?

Pin header is free, nothing is connected. Also no I2C device connected and controlled at all. Therefore I wonder why this has an impact. I will check in Iobroker Forum about it. Thank you