Hi,
I have a Raspberry Pi 4 (running Home Assistant OS) with the Argon One Case. I use an SSD via USB and no Micro-SD-Card at all.
For months, the linear cooling addon worked fine for me: I never heard the fan, since the passive cooling was obviously enough to keep the Pi’s temperature below 50 Degrees Celsius.
But now I changed the jumper position to “always on”. The reason are occasional random Raspberry blackouts. I guess the blackouts happen because the regular Raspberry power cable does not provide enough power to the SSD via USB. Until I get an external power source for the SSD, I hope to circumvent the blackouts of the Raspberry with the “always on”-mode of the jumper.
When I am not at home and my Raspberry is not reachable anymore, I can switch a wifi plug off and on again and therefore reboot the Raspberry Pi.
But now, the fan runs always with a 100%, which is very loud.
Here are the logs.
[s6-init] making user provided files available at /var/run/s6/etc...exited 0.
[s6-init] ensuring user provided files have correct perms...exited 0.
[fix-attrs.d] applying ownership & permissions fixes...
[fix-attrs.d] done.
[cont-init.d] executing container initialization scripts...
[cont-init.d] 00-banner.sh: executing...
-----------------------------------------------------------
Add-on: ArgonOne Active Linear Cooling
Actively keeping your Argon One cool.
-----------------------------------------------------------
Add-on version: 29c
You are running the latest version of this add-on.
System: Home Assistant OS 9.4 (aarch64 / raspberrypi4-64)
Home Assistant Core: 2023.1.1
Home Assistant Supervisor: 2022.12.1
-----------------------------------------------------------
Please, share the above information when looking for help
or support in, e.g., GitHub, forums or the Discord chat.
-----------------------------------------------------------
[cont-init.d] 00-banner.sh: exited 0.
[cont-init.d] 01-log-level.sh: executing...
[cont-init.d] 01-log-level.sh: exited 0.
[cont-init.d] done.
[services.d] starting services
[services.d] done.
Detecting Layout of i2c, we expect to see "1a" here.
checking i2c port 0 at /dev/i2c-0
0 1 2 3 4 5 6 7 8 9 a b c d e f
00: -- -- -- -- -- -- -- --
10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
70: -- -- -- -- -- -- -- --
not found on /dev/i2c-0
checking i2c port 1 at /dev/i2c-1
0 1 2 3 4 5 6 7 8 9 a b c d e f
00: -- -- -- -- -- -- -- --
10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
70: -- -- -- -- -- -- -- --
not found on /dev/i2c-1
checking i2c port 10 at /dev/i2c-10
0 1 2 3 4 5 6 7 8 9 a b c d e f
00: -- -- -- -- -- -- -- --
10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
70: -- -- -- -- -- -- -- --
not found on /dev/i2c-10
checking i2c port 22 at /dev/i2c-22
0 1 2 3 4 5 6 7 8 9 a b c d e f
00: -- -- -- -- -- -- -- --
10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
70: -- -- -- -- -- -- -- --
not found on /dev/i2c-22
/run.sh: line 111: thePort: unbound variable
[cmd] /run.sh exited 1
[cont-finish.d] executing container finish scripts...
[cont-finish.d] 99-message.sh: executing...
-----------------------------------------------------------
Oops! Something went wrong.
We are so sorry, but something went terribly wrong when
starting or running this add-on.
Be sure to check the log above, line by line, for hints.
-----------------------------------------------------------
[cont-finish.d] 99-message.sh: exited 0.
[cont-finish.d] done.
[s6-finish] waiting for services.
[s6-finish] sending all processes the TERM signal.
So I thought I needed to install an run the HassOS I2C Configurator again. But those were the logs:
crw--w---- 1 root tty 4, 29 Jun 2 2022 tty29
crw--w---- 1 root tty 4, 3 Jun 2 2022 tty3
crw--w---- 1 root tty 4, 30 Jun 2 2022 tty30
crw--w---- 1 root tty 4, 31 Jun 2 2022 tty31
crw--w---- 1 root tty 4, 32 Jun 2 2022 tty32
crw--w---- 1 root tty 4, 33 Jun 2 2022 tty33
crw--w---- 1 root tty 4, 34 Jun 2 2022 tty34
crw--w---- 1 root tty 4, 35 Jun 2 2022 tty35
crw--w---- 1 root tty 4, 36 Jun 2 2022 tty36
crw--w---- 1 root tty 4, 37 Jun 2 2022 tty37
crw--w---- 1 root tty 4, 38 Jun 2 2022 tty38
crw--w---- 1 root tty 4, 39 Jun 2 2022 tty39
crw--w---- 1 root tty 4, 4 Jun 2 2022 tty4
crw--w---- 1 root tty 4, 40 Jun 2 2022 tty40
crw--w---- 1 root tty 4, 41 Jun 2 2022 tty41
crw--w---- 1 root tty 4, 42 Jun 2 2022 tty42
crw--w---- 1 root tty 4, 43 Jun 2 2022 tty43
crw--w---- 1 root tty 4, 44 Jun 2 2022 tty44
crw--w---- 1 root tty 4, 45 Jun 2 2022 tty45
crw--w---- 1 root tty 4, 46 Jun 2 2022 tty46
crw--w---- 1 root tty 4, 47 Jun 2 2022 tty47
crw--w---- 1 root tty 4, 48 Jun 2 2022 tty48
crw--w---- 1 root tty 4, 49 Jun 2 2022 tty49
crw--w---- 1 root tty 4, 5 Jun 2 2022 tty5
crw--w---- 1 root tty 4, 50 Jun 2 2022 tty50
crw--w---- 1 root tty 4, 51 Jun 2 2022 tty51
crw--w---- 1 root tty 4, 52 Jun 2 2022 tty52
crw--w---- 1 root tty 4, 53 Jun 2 2022 tty53
crw--w---- 1 root tty 4, 54 Jun 2 2022 tty54
crw--w---- 1 root tty 4, 55 Jun 2 2022 tty55
crw--w---- 1 root tty 4, 56 Jun 2 2022 tty56
crw--w---- 1 root tty 4, 57 Jun 2 2022 tty57
crw--w---- 1 root tty 4, 58 Jun 2 2022 tty58
crw--w---- 1 root tty 4, 59 Jun 2 2022 tty59
crw--w---- 1 root tty 4, 6 Jun 2 2022 tty6
crw--w---- 1 root tty 4, 60 Jun 2 2022 tty60
crw--w---- 1 root tty 4, 61 Jun 2 2022 tty61
crw--w---- 1 root tty 4, 62 Jun 2 2022 tty62
crw--w---- 1 root tty 4, 63 Jun 2 2022 tty63
crw--w---- 1 root tty 4, 7 Jun 2 2022 tty7
crw--w---- 1 root tty 4, 8 Jun 2 2022 tty8
crw--w---- 1 root tty 4, 9 Jun 2 2022 tty9
crw-rw---- 1 root audio 204, 64 Jun 2 2022 ttyAMA0
crw------- 1 root root 5, 3 Jun 2 2022 ttyprintk
crw------- 1 root root 10, 239 Jun 2 2022 uhid
crw------- 1 root root 10, 223 Jun 2 2022 uinput
crw-rw-rw- 1 root root 1, 9 Jun 2 2022 urandom
drwxr-xr-x 3 root root 60 Jun 2 2022 v4l
crw------- 1 root root 245, 0 Jun 2 2022 vc-mem
crw------- 1 root root 239, 0 Jun 2 2022 vchiq
crw------- 1 root root 10, 125 Jun 2 2022 vcio
crw-rw---- 1 root tty 7, 0 Jun 2 2022 vcs
crw-rw---- 1 root tty 7, 1 Jun 2 2022 vcs1
crw-rw---- 1 root tty 7, 2 Jun 2 2022 vcs2
crw-rw---- 1 root tty 7, 3 Jun 2 2022 vcs3
crw-rw---- 1 root tty 7, 4 Jun 2 2022 vcs4
crw-rw---- 1 root tty 7, 5 Jun 2 2022 vcs5
crw-rw---- 1 root tty 7, 6 Jun 2 2022 vcs6
crw-rw---- 1 root tty 7, 128 Jun 2 2022 vcsa
crw-rw---- 1 root tty 7, 129 Jun 2 2022 vcsa1
crw-rw---- 1 root tty 7, 130 Jun 2 2022 vcsa2
crw-rw---- 1 root tty 7, 131 Jun 2 2022 vcsa3
crw-rw---- 1 root tty 7, 132 Jun 2 2022 vcsa4
crw-rw---- 1 root tty 7, 133 Jun 2 2022 vcsa5
crw-rw---- 1 root tty 7, 134 Jun 2 2022 vcsa6
crw-rw-rw- 1 root root 10, 122 Jun 2 2022 vcsm-cma
crw-rw---- 1 root tty 7, 64 Jun 2 2022 vcsu
crw-rw---- 1 root tty 7, 65 Jun 2 2022 vcsu1
crw-rw---- 1 root tty 7, 66 Jun 2 2022 vcsu2
crw-rw---- 1 root tty 7, 67 Jun 2 2022 vcsu3
crw-rw---- 1 root tty 7, 68 Jun 2 2022 vcsu4
crw-rw---- 1 root tty 7, 69 Jun 2 2022 vcsu5
crw-rw---- 1 root tty 7, 70 Jun 2 2022 vcsu6
crw------- 1 root root 10, 127 Jun 2 2022 vga_arbiter
crw------- 1 root root 10, 137 Jun 2 2022 vhci
crw-rw-rw- 1 root 111 10, 238 Jun 2 2022 vhost-net
crw-rw-rw- 1 root 111 10, 241 Jun 2 2022 vhost-vsock
crw-rw---- 1 root netdev 81, 2 Jun 2 2022 video10
crw-rw---- 1 root netdev 81, 6 Jun 2 2022 video11
crw-rw---- 1 root netdev 81, 8 Jun 2 2022 video12
crw-rw---- 1 root netdev 81, 1 Jun 2 2022 video13
crw-rw---- 1 root netdev 81, 3 Jun 2 2022 video14
crw-rw---- 1 root netdev 81, 4 Jun 2 2022 video15
crw-rw---- 1 root netdev 81, 5 Jun 2 2022 video16
crw-rw---- 1 root netdev 81, 12 Jun 2 2022 video18
crw-rw---- 1 root netdev 81, 0 Jun 2 2022 video19
crw-rw---- 1 root netdev 81, 7 Jun 2 2022 video20
crw-rw---- 1 root netdev 81, 9 Jun 2 2022 video21
crw-rw---- 1 root netdev 81, 10 Jun 2 2022 video22
crw-rw---- 1 root netdev 81, 11 Jun 2 2022 video23
crw-rw---- 1 root netdev 81, 13 Jun 2 2022 video31
crw------- 1 root root 10, 130 Jun 2 2022 watchdog
crw------- 1 root root 247, 0 Jun 2 2022 watchdog0
crw-rw-rw- 1 root root 1, 5 Jun 2 2022 zero
brw-rw---- 1 root disk 254, 0 Jun 2 2022 zram0
brw-rw---- 1 root disk 254, 1 Jun 2 2022 zram1
brw-rw---- 1 root disk 254, 2 Jun 2 2022 zram2
/dev/i2c-1
/dev/i2c-0 /dev/i2c-1 /dev/i2c-10 /dev/i2c-22
Found i2c access! Nothing to do! You can remove this add-on.
So, is there really nothing to do? How can I get the addon to work again and setting the fan speed?