Yea,
I’m stuck 
I reinstalled the Argon app. It shows green on as working, but soon after to turns red off.
Here is my log from the Argon App:
Deleted
Here is my log from the HassOS I2C Configurator (which is still installed):
Deleted
Okay, I think I fixed it 
I turned off Protection Mode for HassOS I2C Configurator
I did a full reboot twice.
Now the Argon seems to be working and I can see the fan on the overview page.
I will post both logs below. If there is anything wrong, please let me know.
Argon Log:
Deleted
HassOS I2C Configurator Log:
Deleted
Dont post that much log out of a codebox. You need to disable protection mode on the i2c addon.
Sorry, I deleted all that code.
Disabling protection mode did fix it.
Thank you.
I’m having some errors that I think are coming from this add-on. Did I miss something in the settings? I also get the feeling my fan still runs fast (it’s still noisy) even though my config says it’s running at 1%.
WARNING (SyncWorker_2) [supervisor.addons.validate] Add-on have full device access, and selective device access in the configuration. Please report this to the maintainer of DeskPi Pro Active Cooling
First of all, thank you for the addons.
I use the Linear Cooling and my fan always runs at 100% when it is in the temperature range.
I am using Celsius and the log says for example the fan should run at 12%. I tried to change the temperature range but it is always the same speed, regardless of whether the log says 10% or 80%.
Could it be that my fan simply does not allow speed control?
Is it possible that you have some other app controlling your fans?
I use your ArgonOne Active Linear Cooling Addon only, or is another program installed on HA OS that can control the fan?
There are custom integrations in and scripts people have used in the past. I dont know what the cause is, but i suggested something.
You might try swapping back to raspian and using the official script to see if theres a change.
I tried it with the official script and it is the same, I think my fan is broken because I can’t control the speed and it also whirs all the time.
This worked alright for me for a week or so but since a few days it stops a few seconds after it starts. See below for what’s showing in the logs.
I’m unable to make sense of it so any help would be much appreciated.
[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.5 (aarch64 / raspberrypi4-64)
Home Assistant Core: 2023.2.5
Home Assistant Supervisor: 2023.01.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: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
/run.sh: line 111: thePort: unbound variable
30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
70: -- -- -- -- -- -- -- --
not found on /dev/i2c-22
[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.
Not sure if it’s allowed, but I thought I’d try anyways to bump this. Any thoughts on this? I’m assuming it’s this add-on, since I don’t have any others running.
You have I2C but your device is missing. There is no Argon One device on your i2c.
You might try cleaning your fan. As for the message, last year the devs made a change that triggers that message. It’s unimportant and will be addressed in some future release.
1 Like
Thanks, I’ll have a look, and good to know about the future release. Thanks again for the add-on!
How can I fix that? I ran I2C again but it says something along the lines: all good, you can uninstall this add-on now.
Looks like your hardware is disconnected or you have some other problem going on. I’m not sure. I’d say try raspian and the original scripts and contact Argon Support.
Running HA on a Raspi 4 with my new Argon One M.2 I get the following log:
'[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 9.5 (aarch64 / raspberrypi4-64)
Home Assistant Core: 2023.3.2
Home Assistant Supervisor: 2023.03.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.
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.’
Fan is running on full speed all the time
Enable i2c