I noticed this also. Why is it ‘by design’?
Hi there. Just wanted to say thanks for the addon! Really enjoying the sensor happily humming along in my dashboard.
However, I am running a Pi4 inside the case and enabling I2C was quite problematic for me. Hoping this helps someone else who is trying to get the addon + argon one + Pi4 working together in Home Assistant.
- I initially installed your other addon, unfortunately that didn’t work.
- Then tried the standard home assistant guide to enable I2C. That also didn’t work.
However, I eventually did manage to manually get I2C sorted by doing two things.
- Following @dankrill’s resolution Here
- Adding in @mattias resolution from here where he adds the config to /etc/modules-load.d/rpi-i2c.conf rather than the boot partition.
Strangely no amount of rebooting brought I2C online in /dev without that last line… I am at a loss to explain why, but that probably points to my lack of Pi and Linux skills. 
1 Like
You need to shutdown completely twice, not reboot, then any method will work, including I2C addon.
Tried that several times (pulled the cable out). Didn’t work. But thank you for the assistance here.
Hi,
i installed a fresh Pi4 2GB with HASS OS. I get the new Version v2 of the Argon Case. My jumper is in position 2 (always on).
For i2c access i use the easy way. Plugin gives me positive feedback, so i deinstalled it.
Next point is the configuration of the speed control:
CorF: C
LowRange: 40
MediumRange: 50
HighRange: 55
QuietProfile: true
Create a Fan Speed entity in Home Assistant: true
Log current temperature every 30 seconds: true
After saving and restarting, the protocol looks fine:
I can set the values like i want, the protocol shows the correct fan speed. But in fact, the fan is running at 100% all the time. I am not sure why, but there must be anything wrong in my config.
Thx for replying.
How can you tell that? Did you measured it?
The sound of the fan isn’t really different for 20% or 100%.
The lowest value seems to be the same to full speed for my ears. I hear no difference!
So how did you measured that it runs at 100%?
I changed the config values, so the Pi lays direct beside me. First config with Fan Level 1 and next with 100%. The log says, there were other Fan Levels, my ears say, the fan is as loud as before…
As I wrote: The fan has nearly the same sound regardless of the speed.
omg, so loud??? That makes me sad. But in my opinion there should be a difference between the Fan speeds. I think they are espacially because of the loudness.
Hi, I’ve just installed the addon and got the following errors in the log:
nc: socket(AF_INET,1,0): Permission denied
Failed 58: nc -i 1 hassio 80 > /dev/null <<< unix2dos <<EOF
I2C is seemed to be enabled (HassOS I2C Configurator says that). What next steps should I follow to troubleshoot the errors?
Few words about my environment: Pi4 + Ubuntu. I’ve also installed argononed, it works well however it doesn’t have integration with HA.
Thanks in advance.
Hello,
first of all, thank you for your add-on, that has helped me in any case.
My problem is that I don’t have an Argon ONE housing but the Argon One Fan Hat, which is just a Raspberry Pi Hat with a fan, button and 4 x LEDs to display the fan speed.
And this is exactly where the error lies.
On the HAT I have LEDs for 25%, 50%, 75% and 100% fan power.
With your addon there are 3 x levels, 33%, 66% and 100%.
If the fan runs at 33% according to the script, LED 1 (25%) lights up = correct!
If the fan runs at 66% according to the script, only LED 1 (25%) lights up and not LED 2 (50%) = wrong!
If the fan runs at 100% according to the script, then LED’s 1-3 (25 - 75%) light up but not LED 4 (100%) = wrong!
Why is this so?
Either the fan is controlled incorrectly by the script or the LEDs.
How can I fix this?
PS: Also, the power button does not work, although I have set it up as you indicated.
However, neither a single nor a double click is recognised.
Hi,
I love using HA and this addon seems to be useful but unfortunately I am experiencing issue:
[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: 24.1
You are running the latest version of this add-on.
System: Debian GNU/Linux 11 (bullseye) (armv7 / raspberrypi4)
Home Assistant Core: 2021.9.6
Home Assistant Supervisor: 2021.09.0
-----------------------------------------------------------
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.
0 1 2 3 4 5 6 7 8 9 a b c d e f
00: 00 01 02 03 04 05 06 07 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 78 79 7a 7b 7c 7d 7e 7f
Settings initialized. Argon One Detected. Beginning monitor..
Current Temperature 44 °C
2021-09-16_23:56:21: 44C - Level 1 - Fan 0% (OFF)
Error: Write failed
Failed 78: i2cset -y 1 0x01a "${fanPercentHex}"
Error: Write failed
Safe Mode Activated!
Failed 188: return ${returnValue}
Error: Write failed
Safe Mode Activated!
Current Temperature 43 °C
2021-09-16_23:56:51: 43C - Level 1 - Fan 0% (OFF)
Error: Write failed
Failed 78: i2cset -y 1 0x01a "${fanPercentHex}"
Error: Write failed
Safe Mode Activated!
Failed 188: return ${returnValue}
Error: Write failed
Safe Mode Activated!
And unfortunately, I cannot pass that or make any workaround 
Any idea what I can do to make it working?
It seems that you don’t have activated I2C. You have to do it before you use this Addon.
Thanks for answer
I tried to activate it through addon (HassOS I2C Configurator) but it fails with following error (protection mode is disabled):
crw--w---- 1 root tty 4, 1 Sep 16 23:42 tty1
crw--w---- 1 root tty 4, 10 Jul 13 19:29 tty10
crw--w---- 1 root tty 4, 11 Jul 13 19:29 tty11
crw--w---- 1 root tty 4, 12 Jul 13 19:29 tty12
crw--w---- 1 root tty 4, 13 Jul 13 19:29 tty13
crw--w---- 1 root tty 4, 14 Jul 13 19:29 tty14
crw--w---- 1 root tty 4, 15 Jul 13 19:29 tty15
crw--w---- 1 root tty 4, 16 Jul 13 19:29 tty16
crw--w---- 1 root tty 4, 17 Jul 13 19:29 tty17
crw--w---- 1 root tty 4, 18 Jul 13 19:29 tty18
crw--w---- 1 root tty 4, 19 Jul 13 19:29 tty19
crw--w---- 1 root tty 4, 2 Jul 13 19:29 tty2
crw--w---- 1 root tty 4, 20 Jul 13 19:29 tty20
crw--w---- 1 root tty 4, 21 Jul 13 19:29 tty21
crw--w---- 1 root tty 4, 22 Jul 13 19:29 tty22
crw--w---- 1 root tty 4, 23 Jul 13 19:29 tty23
crw--w---- 1 root tty 4, 24 Jul 13 19:29 tty24
crw--w---- 1 root tty 4, 25 Jul 13 19:29 tty25
crw--w---- 1 root tty 4, 26 Jul 13 19:29 tty26
crw--w---- 1 root tty 4, 27 Jul 13 19:29 tty27
crw--w---- 1 root tty 4, 28 Jul 13 19:29 tty28
crw--w---- 1 root tty 4, 29 Jul 13 19:29 tty29
crw--w---- 1 root tty 4, 3 Jul 13 19:29 tty3
crw--w---- 1 root tty 4, 30 Jul 13 19:29 tty30
crw--w---- 1 root tty 4, 31 Jul 13 19:29 tty31
crw--w---- 1 root tty 4, 32 Jul 13 19:29 tty32
crw--w---- 1 root tty 4, 33 Jul 13 19:29 tty33
crw--w---- 1 root tty 4, 34 Jul 13 19:29 tty34
crw--w---- 1 root tty 4, 35 Jul 13 19:29 tty35
crw--w---- 1 root tty 4, 36 Jul 13 19:29 tty36
crw--w---- 1 root tty 4, 37 Jul 13 19:29 tty37
crw--w---- 1 root tty 4, 38 Jul 13 19:29 tty38
crw--w---- 1 root tty 4, 39 Jul 13 19:29 tty39
crw--w---- 1 root tty 4, 4 Jul 13 19:29 tty4
crw--w---- 1 root tty 4, 40 Jul 13 19:29 tty40
crw--w---- 1 root tty 4, 41 Jul 13 19:29 tty41
crw--w---- 1 root tty 4, 42 Jul 13 19:29 tty42
crw--w---- 1 root tty 4, 43 Jul 13 19:29 tty43
crw--w---- 1 root tty 4, 44 Jul 13 19:29 tty44
crw--w---- 1 root tty 4, 45 Jul 13 19:29 tty45
crw--w---- 1 root tty 4, 46 Jul 13 19:29 tty46
crw--w---- 1 root tty 4, 47 Jul 13 19:29 tty47
crw--w---- 1 root tty 4, 48 Jul 13 19:29 tty48
crw--w---- 1 root tty 4, 49 Jul 13 19:29 tty49
crw--w---- 1 root tty 4, 5 Jul 13 19:29 tty5
crw--w---- 1 root tty 4, 50 Jul 13 19:29 tty50
crw--w---- 1 root tty 4, 51 Jul 13 19:29 tty51
crw--w---- 1 root tty 4, 52 Jul 13 19:29 tty52
crw--w---- 1 root tty 4, 53 Jul 13 19:29 tty53
crw--w---- 1 root tty 4, 54 Jul 13 19:29 tty54
crw--w---- 1 root tty 4, 55 Jul 13 19:29 tty55
crw--w---- 1 root tty 4, 56 Jul 13 19:29 tty56
crw--w---- 1 root tty 4, 57 Jul 13 19:29 tty57
crw--w---- 1 root tty 4, 58 Jul 13 19:29 tty58
crw--w---- 1 root tty 4, 59 Jul 13 19:29 tty59
crw--w---- 1 root tty 4, 6 Jul 13 19:29 tty6
crw--w---- 1 root tty 4, 60 Jul 13 19:29 tty60
crw--w---- 1 root tty 4, 61 Jul 13 19:29 tty61
crw--w---- 1 root tty 4, 62 Jul 13 19:29 tty62
crw--w---- 1 root tty 4, 63 Jul 13 19:29 tty63
crw--w---- 1 root tty 4, 7 Jul 13 19:29 tty7
crw--w---- 1 root tty 4, 8 Jul 13 19:29 tty8
crw--w---- 1 root tty 4, 9 Jul 13 19:29 tty9
crw-rw---- 1 root dialout 4, 64 Jul 13 19:29 ttyS0
crw--w---- 1 root tty 4, 65 Sep 16 23:42 ttyS1
crw-rw---- 1 root dialout 4, 66 Jul 13 19:29 ttyS2
crw-rw---- 1 root dialout 4, 67 Jul 13 19:29 ttyS3
crw------- 1 root root 10, 239 Jul 13 19:29 uhid
crw------- 1 root root 10, 223 Jul 13 19:29 uinput
crw-rw-rw- 1 root root 1, 9 Jul 13 19:29 urandom
crw------- 1 root root 241, 0 Jul 13 19:29 vchiq
crw-rw---- 1 root tty 7, 0 Jul 13 19:29 vcs
crw-rw---- 1 root tty 7, 1 Jul 13 19:29 vcs1
crw-rw---- 1 root tty 7, 2 Sep 16 23:42 vcs2
crw-rw---- 1 root tty 7, 3 Sep 16 23:42 vcs3
crw-rw---- 1 root tty 7, 4 Sep 16 23:42 vcs4
crw-rw---- 1 root tty 7, 5 Sep 16 23:42 vcs5
crw-rw---- 1 root tty 7, 6 Sep 16 23:42 vcs6
crw-rw---- 1 root tty 7, 128 Jul 13 19:29 vcsa
crw-rw---- 1 root tty 7, 129 Jul 13 19:29 vcsa1
crw-rw---- 1 root tty 7, 130 Sep 16 23:42 vcsa2
crw-rw---- 1 root tty 7, 131 Sep 16 23:42 vcsa3
crw-rw---- 1 root tty 7, 132 Sep 16 23:42 vcsa4
crw-rw---- 1 root tty 7, 133 Sep 16 23:42 vcsa5
crw-rw---- 1 root tty 7, 134 Sep 16 23:42 vcsa6
crw-rw---- 1 root tty 7, 64 Jul 13 19:29 vcsu
crw-rw---- 1 root tty 7, 65 Jul 13 19:29 vcsu1
crw-rw---- 1 root tty 7, 66 Sep 16 23:42 vcsu2
crw-rw---- 1 root tty 7, 67 Sep 16 23:42 vcsu3
crw-rw---- 1 root tty 7, 68 Sep 16 23:42 vcsu4
crw-rw---- 1 root tty 7, 69 Sep 16 23:42 vcsu5
crw-rw---- 1 root tty 7, 70 Sep 16 23:42 vcsu6
drwxr-xr-x 2 root root 60 Jul 13 19:29 vfio
crw------- 1 root root 10, 63 Jul 13 19:29 vga_arbiter
crw------- 1 root root 10, 238 Jul 13 19:29 vhost-net
crw------- 1 root root 10, 241 Jul 13 19:29 vhost-vsock
crw------- 1 root root 10, 130 Jul 13 19:29 watchdog
crw------- 1 root root 250, 0 Jul 13 19:29 watchdog0
crw-rw-rw- 1 root root 1, 5 Jul 13 19:29 zero
nothing to do. Is protection mode enabled? You can't run this without disabling protection mode
Also, I do have i2c files in /dev
My installation is Home Assistant Supervised at Docker on Raspi Debian (if it helps).
Oh, then I can not help you as I only knew Home Assistant operating system.
I’m having the same problem of the sensor.argon_one_addon_fan_speed entity disappearing after a HA core restart. Restarting the add-on fixes the issue, but it would be nice not to have to restart the add-on every time I restart HA.
I hope that there will be a fix for this. I moved to Debian bullseye to resolve another issue. I am now running into this problem.
Add-on version: 24.1
You are running the latest version of this add-on.
System: Debian GNU/Linux 11 (bullseye) (aarch64 / raspberrypi4-64)
Home Assistant Core: 2021.9.7
Home Assistant Supervisor: 2021.09.4
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.
0 1 2 3 4 5 6 7 8 9 a b c d e f
00: 00 01 02 03 04 05 06 07 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 78 79 7a 7b 7c 7d 7e 7f
Settings initialized. Argon One Detected. Beginning monitor…
Current Temperature 44 °C
2021-09-28_20:52:52: 44C - Level 1 - Fan 0% (OFF)
Error: Write failed
Failed 78: i2cset -y 1 0x01a “${fanPercentHex}”
Error: Write failed
Safe Mode Activated!
Failed 188: return ${returnValue}
Error: Write failed
Safe Mode Activated!
I think I found an workaround for it but dont know how to apply it as each time, add-on gets deployed from GitHub instead of locally downloaded files 
There must be change in run.sh file as there is hardcoded pointing to /dev/i2c-1 where probably, at our instanced it is: /dev/i2c-3
Unfortunately, when changing it locally (before first start of add-on) it is still not working as container image is pushed from GitHub
EDIT
I think I did it by adding as local and removing entries for GitHub as well as changed hardcoded i2c-1 to i2c-3
Maybe author could add ability to define i2c at configuration - this could solve such problems.
3 Likes