That’s likely a hardware issue.
Another year, another Core update, another battle with apparmor. This time around, I have simply renamed my /usr/share/hassio/apparmor/7d06b5a0_argon_one_temp file to effectively remove it. And the add-on is back up and running again after a reboot.
First time I faced the same issue 2-3 months ago. What helped me was completely disconnecting the device from the power supply. Simple device reboot didn’t help. Now I see the same errors in log, but I can’t disconnect device remotely being far from it.
@adamoutler hi, i have the argon neo model with the same hat. This will work with my model too?
I don’t have one of those. You can try it. I wouldn’t expect problems. Let me know if it works and which version you use. I need to create a table of operation
| Argon Version | Works With |
|---|---|
| Debian v1/v2 | linear classic |
| V1 | active cooling & linear |
| V2 | active cooling & linear |
| Neo | active cooling & linear |
| V3 | linear v3 |
| V5 |
Let me know which versions work. I expect it to work with linear and active cooling. Please check all you can.
the active cooling, linear seems to work correctly
Great. That means it will also work with the plain ol active cooling package.
I have disconnected power each time setting this up and get that same message. Is there any fixes for this?
Did you find a way to make this work?
Hi there,
The fan on my case turns ON/OFF almost every minute.
Can’t the fan just run continuously?
Do I need to adjust any setting or add some configuration?
Here the log:
And here my settings:
Hello,
Is it possible to create an automation to turn things on and off within a specific time range?
So Im having the same issue. Suddenly my fan went on and stayed on. I checked the logs in the addon and got:
-----------------------------------------------------------
Add-on: ArgonOne Active Cooling
Actively keeping your Argon One cool.
-----------------------------------------------------------
Add-on version: 30a
You are running the latest version of this add-on.
System: Home Assistant OS 15.2 (aarch64 / raspberrypi4-64)
Home Assistant Core: 2025.5.3
Home Assistant Supervisor: 2025.05.5
-----------------------------------------------------------
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
I2C Port 255
Argon One was not detected on i2c. Argon One will show a 1a on the i2c bus above. This add-on will not control temperature without a connection to Argon One.
Current Temperature 102 °F
2025-06-18_13:27:31: 102F - Level 1 - Fan 0% (OFF)
Error: Could not open file `/dev/i2c-255' or `/dev/i2c/255': No such file or directory
Failed 106: i2cset -y "${port}" "0x01a" "${fanPercentHex}"
Error: Could not open file `/dev/i2c-255' or `/dev/i2c/255': No such file or directory
Safe Mode Activated!
Failed 217: return ${returnValue}
Error: Could not open file `/dev/i2c-255' or `/dev/i2c/255': No such file or directory
Safe Mode Activated!
However, I can clearly see the buses:
And the I2c Configurator logs shows:
/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.
As I said, this suddenly happened. The case and fan worked fine up until yesterday. What do I do?
It looks like you have I²C Access. But I think there’s nothing on the i2c bus to communicate with. This may be a hardware failure. Or it could be something disconnected.
Hello, I have the V3 case, everything looks ok, but my fan is always on.
The logs show:
found at /dev/i2c-1
I2C Port 1
Settings initialized. Argon One Detected. Beginning monitor…
What should i do next to make it work?
What came before that and what came after? Wrap it all in a code box.
1 Like
Solved, i had not installed the ArgonOne V3 Active Linear Cooling, but the normal one, now it is working as expected. Many thanks for your answer.!
Current high temperatures and burning hot Raspberry forced me to look into the fan stuff for the Argon One case. I was under the assumption, that there is no fan, but luckily there is. Found this Addon: Thanks you!
It took me a while to get to config.txt (SATA boot) to enable i2c. Problem was: “normal SSH” didn’t get me to the boot partition. Solved this with the 22222 SSH Addon.
Now I’m wondering, why the temperature is written to the logfile, while the fan is forwarded to an Homeassistant entity.
Is there any specific reason not to forward the temperature to an entity?
Does this work with the v5 case at all?
1 Like
Wasn’t able to make it working with my argon one v5 case. When switching to raspbian and running original Argon one script, fan seems working
-----------------------------------------------------------
Add-on: ArgonOne Active Cooling
Actively keeping your Argon One cool.
-----------------------------------------------------------
Add-on version: 30a
You are running the latest version of this add-on.
System: Home Assistant OS 16.0 (aarch64 / raspberrypi5-64)
Home Assistant Core: 2025.7.2
Home Assistant Supervisor: 2025.07.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 13 at /dev/i2c-13
0 1 2 3 4 5 6 7 8 9 a b c d e f
00: 08 09 0a 0b 0c 0d 0e 0f
10: 10 11 12 13 14 15 16 17 18 19 1a 1b 1c 1d 1e 1f
20: 20 21 22 23 24 25 26 27 28 29 2a 2b 2c 2d 2e 2f
30: -- -- -- -- -- -- -- -- 38 39 3a 3b 3c 3d 3e 3f
40: 40 41 42 43 44 45 46 47 48 49 4a 4b 4c 4d 4e 4f
50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
60: 60 61 62 63 64 65 66 67 68 69 6a 6b 6c 6d 6e 6f
70: 70 71 72 73 74 75 76 77
not found on /dev/i2c-13
checking i2c port 14 at /dev/i2c-14
0 1 2 3 4 5 6 7 8 9 a b c d e f
00: 08 09 0a 0b 0c 0d 0e 0f
10: 10 11 12 13 14 15 16 17 18 19 1a 1b 1c 1d 1e 1f
20: 20 21 22 23 24 25 26 27 28 29 2a 2b 2c 2d 2e 2f
30: -- -- -- -- -- -- -- -- 38 39 3a 3b 3c 3d 3e 3f
40: 40 41 42 43 44 45 46 47 48 49 4a 4b 4c 4d 4e 4f
50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
60: 60 61 62 63 64 65 66 67 68 69 6a 6b 6c 6d 6e 6f
70: 70 71 72 73 74 75 76 77
not found on /dev/i2c-14
I2C Port 255
Argon One was not detected on i2c. Argon One will show a 1a on the i2c bus above. This add-on will not control temperature without a connection to Argon One.
Current Temperature 42 °C
2025-07-20_12:20:21: 42C - Level 3 - Fan 66% (Medium)
Error: Could not open file `/dev/i2c-255' or `/dev/i2c/255': No such file or directory
Failed 106: i2cset -y "${port}" "0x01a" "${fanPercentHex}"
Error: Could not open file `/dev/i2c-255' or `/dev/i2c/255': No such file or directory
Safe Mode Activated!
However it seems, that V5 case wont need argon script to control the fan. But maybe someone can confirm. From argon discussion - Argon One V5 - Fan not recognized - Argon 40 Forum & Community it seems, that FAN is connected directly to Raspi 4 in connector without any added need to control this.
Some documentation from raspi: https://www.raspberrypi.com/documentation/computers/raspberry-pi.html#raspberry-pi-5-fans