I do not see that option in the I2C Add-on either.
I have already Advanced mode enabled.
I will continue in the Add-on thread.
I now feel very very silly and am compelled to apologise and eat humble pie.
I honestly did not see the Disable Protection mode, I don’t know why but I feel very grateful to you all for helping.
It all seems to be working now.
Again, sincere apologies.
Hi guys, I failed in making work an Argon MINI fan on an RPI with HASSOS.
Home Assistant 2023.3.1
Supervisor 2023.04.1
Operating System 10.2
Frontend 20230302.0 - latest
I installed i2c and HassOSArgonOneAddon and I put the switch of the fan on PWR mode. In the HA interface, the fan status is changing but in fact, when I check the fan is not. More precisely, even though
entity_id form HA shows that the fan should start, in fact, it is off.
I2C protection mode is disabled
When I start the add-on I receive this message.
/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.
On the other hand, I receive the following error message when I start the Argon add-on
[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 123 °F
2023-05-29_14:46:30: 123F - Level 1 - Fan 0% (OFF)
Error: Could not open file `/dev/i2c-255' or `/dev/i2c/255': No such file or directory
Failed 98: 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 209: return ${returnValue}
Error: Could not open file `/dev/i2c-255' or `/dev/i2c/255': No such file or directory
Safe Mode Activated!
I made 2 or 3 hard resets of the RPI but it was useless!
I verified in the terminal and I saw the i2c files are present in /dev/
Do you have any suggestions?!
You don’t have an Argon One connected
I am not sure that I understand. It is not physically connected?
There is nothing on your i2c. It’s not communicating. It’s empty. No device is present. The diagnostic says your i2c is empty. Электронное устройство не общается. 电子设备无法通信.
1 Like
Ok. I got your point. Thanks a lot.
Hi there,
I had the same isue, what worked for me was to shut down my Argon one ( so not reboot)
and then start up the argon one.
The cooling addon seems to be working just fine, but I can’t hear the fan running in the case. I do not have QuietProfile active.
I’ve opened the case and can’t identify any missing or broken connections.
This worked when I first got the case about two years ago, but it hasn’t been working for the past year (I’ve just not gotten around to addressing it until now).
puh - what a long thred. I dont care about sophisticated temperatur models but just want that fan running because this thing gets hot after some time.
I installed i2c first and then Active linear coolin addon.
[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 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 10.3 (aarch64 / raspberrypi4-64)
Home Assistant Core: 2023.6.3
Home Assistant Supervisor: 2023.06.2
-----------------------------------------------------------
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.
ls: /dev/i2c-*: No such file or directory
Cannot find I2C port. You must enable I2C for this add-on to operate properly
[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 what went wrong?
also i cant open the Addons from the sideline - it is spinning endless
any suggestions? thanks
At least read the first post. Enable i2c. I don’t care to answer with any more detail as you don’t care to read.
1 Like
sorry but i used to enable i2c by your addon “The easy way”
I’m guessing this is in reply to satsatt, since I do have i2c enabled. At least it gives the impression that I do.
Great work @adamoutler !
Awaiting the delivery of my Argon case, prepping my system.
I2C enabled, thanks to your great tool, and by just following instructions … 
Question I have: the temperature being used for the fan regulation scheme, is it ambient temperature inside the casing being used ? Or is it actual CPU temp, derived from OpSys ?
Just wondering, since the cpu temp (available through HA systemmonitor, once enabled in sensor.yaml) is something I am monitoring right now. And can then use my historic data to compare and decide on thresholds.
Tnx, and keep up the good work,
John
Hi @adamoutler,
Seems that it’s not working with Debian Bookworm 
Today I have updated Debian and I have following messages at logs:
[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...
curl: (7) Couldn't connect to server
[20:05:48] ERROR: Something went wrong contacting the API
[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: 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-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: 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-1
checking i2c port 2 at /dev/i2c-2
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-2
checking i2c port 3 at /dev/i2c-3
0 1 2 3 4 5 6 7 8 9 a b c d e f
00: -- -- -- -- -- -- -- --
10: -- -- -- -- -- -- -- -- -- -- 1a -- -- -- -- --
20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
70: -- -- -- -- -- -- -- --
found at /dev/i2c-3
I2C Port 3
Settings initialized. Argon One Detected. Beginning monitor..
Current Temperature 39 °C
2023-06-30_20:05:49: 39C - Level 1 - Fan 0% (OFF)
nc: socket(AF_INET,1,0): Permission denied
nc: socket(AF_INET,1,0): Permission denied
Failed 78: nc -i 1 hassio 80 > /dev/null <<< unix2dos <<EOF
POST /homeassistant/api/states/sensor.argon_one_addon_fan_speed HTTP/1.1
Authorization: Bearer ${SUPERVISOR_TOKEN}
Content-Length: $( echo -ne "${reqBody}" | wc -c )
${reqBody}
EOF
Failed 78: nc -i 1 hassio 80 > /dev/null <<< unix2dos <<EOF
POST /homeassistant/api/states/sensor.argon_one_addon_fan_speed HTTP/1.1
Authorization: Bearer ${SUPERVISOR_TOKEN}
Content-Length: $( echo -ne "${reqBody}" | wc -c )
${reqBody}
EOF
Safe Mode Activated!
Failed 101: nc -i 1 hassio 80 > /dev/null <<< unix2dos <<EOF
POST /homeassistant/api/states/sensor.argon_one_addon_fan_speed HTTP/1.1
Authorization: Bearer ${SUPERVISOR_TOKEN}
Content-Length: $( echo -ne "${reqBody}" | wc -c )
${reqBody}
EOF
Safe Mode Activated!
Safe Mode Activated!
Failed 214: nc -i 1 hassio 80 > /dev/null <<< unix2dos <<EOF
POST /homeassistant/api/states/sensor.argon_one_addon_fan_speed HTTP/1.1
Authorization: Bearer ${SUPERVISOR_TOKEN}
Content-Length: $( echo -ne "${reqBody}" | wc -c )
${reqBody}
EOF
Safe Mode Activated!
Fan seems to be working on 100% where it should start with lowest power at 55 °C.
Can You take a look on it?
I do use Home Assistant 2023.6.3 Supervised on Debian 12 (Bookworm)
So after some of investigation, seems like there is issue with communication with Supervisor while option: “Create a Fan Speed entity in Home Assistant” is enabled?
23-07-04 20:23:19 WARNING (SyncWorker_5) [supervisor.docker.interface] Can't grep logs from adamoutler/aarch64-hassosargonone: 409 Client Error for http+docker://localhost/v1.43/containers/8d78012c7cbb0838a956176f74b9ef1bc2327a504a0e64eaf232e056cd4d875b/logs?stderr=1&stdout=1×tamps=0&follow=0&tail=100: Conflict ("can not get logs from container which is dead or marked for removal")'
Probably it is related to this part from previous log:
curl: (7) Couldn't connect to server
[20:05:48] ERROR: Something went wrong contacting the API
So Your addon goes to safe mod and set fan to 100% due to that, but if option: “Create a Fan Speed entity in Home Assistant” is disabled - everything seems to work correctly (but of course fan entity does not exist).
This doesn’t look like HAOS. This is def using the wrong i2c. What is your setup?
Looks like it says your container for the addon is scheduled to be removed. I think you have something with a bad install/uninstall going on.
You are right, following error:
23-07-04 20:23:19 WARNING (SyncWorker_5) [supervisor.docker.interface] Can't grep logs from adamoutler/aarch64-hassosargonone: 409 Client Error for http+docker://localhost/v1.43/containers/8d78012c7cbb0838a956176f74b9ef1bc2327a504a0e64eaf232e056cd4d875b/logs?stderr=1&stdout=1×tamps=0&follow=0&tail=100: Conflict ("can not get logs from container which is dead or marked for removal")'
Seems like it isnt suitable for this issue.
My setup:
Home Assistant: 2023.6.3
Supervisor: 2023.06.4
Frontend 20230608.0 - latest
OS: Debian 12 (Bookworm)
[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...
curl: (7) Couldn't connect to server
[15:28:08] ERROR: Something went wrong contacting the API
[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: 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-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: 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-1
checking i2c port 2 at /dev/i2c-2
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-2
checking i2c port 3 at /dev/i2c-3
0 1 2 3 4 5 6 7 8 9 a b c d e f
00: -- -- -- -- -- -- -- --
10: -- -- -- -- -- -- -- -- -- -- 1a -- -- -- -- --
20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
70: -- -- -- -- -- -- -- --
found at /dev/i2c-3
I2C Port 3
Settings initialized. Argon One Detected. Beginning monitor..
Current Temperature 43 °C
2023-07-05_15:28:10: 43C - Level 1 - Fan 0% (OFF)
nc: socket(AF_INET,1,0): Permission denied
nc: socket(AF_INET,1,0): Permission denied
Failed 78: nc -i 1 hassio 80 > /dev/null <<< unix2dos <<EOF
POST /homeassistant/api/states/sensor.argon_one_addon_fan_speed HTTP/1.1
Authorization: Bearer ${SUPERVISOR_TOKEN}
Content-Length: $( echo -ne "${reqBody}" | wc -c )
${reqBody}
EOF
Failed 78: nc -i 1 hassio 80 > /dev/null <<< unix2dos <<EOF
POST /homeassistant/api/states/sensor.argon_one_addon_fan_speed HTTP/1.1
Authorization: Bearer ${SUPERVISOR_TOKEN}
Content-Length: $( echo -ne "${reqBody}" | wc -c )
${reqBody}
EOF
Safe Mode Activated!
Safe Mode Activated!
Failed 101: nc -i 1 hassio 80 > /dev/null <<< unix2dos <<EOF
POST /homeassistant/api/states/sensor.argon_one_addon_fan_speed HTTP/1.1
Authorization: Bearer ${SUPERVISOR_TOKEN}
Content-Length: $( echo -ne "${reqBody}" | wc -c )
${reqBody}
EOF
Addon does correctly identifies which I2C should be used.