Argon One Active Cooling and Active Linear Cooling Addon

Does anyone know’s how we can use the fan control after 2022.6 ?
After the upgrade the add-on is not working anymore, delete + reinstall is not possible anymore.

Mine is getting warm (no issues at this moment)

Hi, I’ve just installed this add-on on fresh installation of hassos. And after enabling i2c and couple of install/reinstall I still got this:

[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: Home Assistant OS 7.4 (aarch64 / raspberrypi4-64)
Home Assistant Core: 2022.3.0
Home Assistant Supervisor: 2022.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.
0 1 2 3 4 5 6 7 8 9 a b c d e f
00: – – – – – – – – – – – – – – – –
10: – – – – – – – – – – – – – – – –
20: – – – – – – – – – – – – – – – –
30: – – – – – – – – – – – – – – – –
40: – – – – – – – – – – – – – – – –
50: – – – – – – – – – – – – – – – –
60: – – – – – – – – – – – – – – – –
70: – – – – – – – – – – – – – – – –
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 43 Β°C
2022-03-03_20:21:26: 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!

Im also totally new to Rpi and HA. I installed yesterday and today Im trying to get this addon to work for my Argon One case. But I keep getting this:

22-03-12 17:43:44 WARNING (MainThread) [supervisor.misc.tasks] Watchdog found a problem with 7d06b5a0_argon_one_temp!
22-03-12 17:43:44 INFO (SyncWorker_5) [supervisor.docker.interface] Cleaning addon_7d06b5a0_argon_one_temp application
22-03-12 17:43:46 INFO (SyncWorker_5) [supervisor.docker.addon] Starting Docker add-on adamoutler/aarch64-hassosargonone with version 9.1.7
1 Like

@adamoutler1 I just want to say thank you for making this addon. I installed it (and set up the I2C) perfectly using the documentation, and it works really well. Thanks so much.

The add-on is still working well for me, and I see fan speed changes over time as temperature changes, according to my settings. But I saw something strange in the logs today:

2022-03-28_09:39:09: 34C - 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 34 Β°C

I double-checked and my I2C access is still valid/enabled (I re-added and started Adam’s I2C addon, which confirmed that I2C access was present). I’m unsure why the I2C write operation is failing. Looks like a few others have seen this before too. What can we do?

Looks like the main repo has not been updated for some months now.

hello i have some problem with 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: 24.1
 You are running the latest version of this add-on.
 System: Debian GNU/Linux 11 (bullseye)  (aarch64 / raspberrypi4-64)
 Home Assistant Core: 2022.3.8
 Home Assistant Supervisor: 2022.03.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.
     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 98 Β°F
2022-04-04_18:21:54: 98F - 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 have 4 i2c interfaces

i2c-3   i2c             bcm2835 (i2c@7e804000)                  I2C adapter
i2c-1   i2c             Broadcom STB :                          I2C adapter
i2c-2   i2c             bcm2835 (i2c@7e205000)                  I2C adapter
i2c-0   i2c             Broadcom STB :                          I2C adapter

addone use i2c-1
I think i need i2c-3

f@rpi4-20220121:~$ sudo i2cdetect -y 1
sudo: unable to resolve host rpi4-20220121: Name or service not known
     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

@rpi4-20220121:~$ sudo i2cdetect -y 3
sudo: unable to resolve host rpi4-20220121: Name or service not known
     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: -- -- -- -- -- -- -- --

how cane i change this?

Hi Guys!

I have edited my version of this addon

Now You can select which i2c bus should be used to scan for Argon One.

Link do download new version: Dropbox - argonOne_edited.zip - Simplify your life

Remember to add it as a local addon.

2 Likes

@olegvsf, don’t You think that in first step You should ask me do I agree to upload it to Your GitHub?
Please remove it, I am working to share it through my GitHub repo for future use…

And I dont agree that it is dificult to install it… it just requires to download .zip file, extract and copy folder to local at Home Assistant addons…

Officially edited version at GitHub from me: GitHub - znanywawa/HA_ArgonOne_set_i2c: Editet version of Argon One addon for Home Assistant to allow pick I2C bus

Hello, I am still very new with a test system at Home Asssiant. I also own an Argon M2 case and have been able to install the fan control add-on. What I unfortunately have not yet managed, that the Raspi after a shutdown can be switched on again via the power button. After shutdown, there is always a red LED in the back, which never goes out. Do you have a tip how I can turn on the Raspi again?

Oh, and one more thing. I have read the last posts about HA 2022.6 and the GPIO pins, but still don’t understand if there will be a problem or not? Might this also have something to do with the power button issue?

There is a jumper on the argon board that you can move to change the behaviour of the power button. It disables the button basically. So that it behaves more like a normal pi. It reboots instead of turning off. Core electronics there is an image halfway or so down the page.

I haven’t turned mine off for a while, but a single click on the button should turn it on in the standard jumper position.

The behavior of my Pi is such that it first stays off when freshly connected to power. It then turns on when you press the power button. The Argon add-on shows me the temperature and also audibly turns the fan on and off. However, when I then shut down the system, the button no longer responds. My PIN connection is default. Actually, I want to be able to switch it manually. But it should also be able to switch on again after switching off.

ok, sorry.

Thanks to you, I got rid of the annoying fan noise. :raised_hands:

Hi Guys,

Okay, I’m completely green to Home Assistant, and relatively new Raspberry Pi’s.

I’ve got myself a new RPi 4b 4gb along with a new Kingston A400 M.2 120gb and a new Argon One Enclosure. Just waiting on a M.2 to usb cable.

As this addon runs in a Docker Container, do I have to install HA using docker to be able to add and use this addon, or can I install HA through the RPi imager and then add this addon?

Sorry if this sounds a dumb question, but if you don’t know, ask.

Dizzwold.

Welcome to Home Assistant!

You may like to use search regarding your configuration. There are some threads that may help (example).

If you install with home assistant OS you will just install this addon using the details in the first post (you don’t need to install HA using docker, as the home assistant OS will manage the containers for you).

Hi Guys,
I seem to be having issues enabling the i2c.
Is there a complete guide to doing this with ssh from a mac terminal. When I say a complete guide, what I mean is exactly what to type to get to the correct files and to add the txt?
I’ve used ssh to [email protected], then pasted the following;

mkdir /tmp/mnt
mount /dev/sda1 /tmp/mnt
mkdir -p /tmp/mnt/CONFIG/modules
echo -ne i2c-dev>/tmp/mnt/CONFIG/modules/rpi-i2c.conf
echo dtparam=i2c_vc=on >> /tmp/mnt/CONFIG/config.txt
echo dtparam=i2c_arm=on >> /tmp/mnt/CONFIG/config.txt
sync
reboot

I’ve changed sda1 to sdb1 and mmcblk0p1 and get the responselike the following stating no directory;
mount: mounting /dev/mmcblk0p1 on /tmp/mnt failed: No such file or directory
etc, I’ve completely powered down, and unplugged many times.
Is this anything to do with the following img?


I’ve also taken the whole thing apart, and with the usb Alien connector and a usb-a to usb-a connected the ssd to my mac, but can’t get into it to change anything. This is also how I installed HA through Balena onto the drive.
I’d be grateful for some help, I’m a little clueless with this.

Dizz.

HI Guy’s,

I think i have it installed now, but how do I check this?

I’m not using this add-on anymore as I’ve moved back to a container based install, but just update the configuration and change the trigger temperature to be lower than your current pi temperature and it should start the cooling fan.

Newb question, @BlackRose67, how do I find the temperature of my Pi and Is there a nice addon for this?

In 64-bit Raspberry Pi OS I just use

/usr/bin/vcgencmd measure_temp

But HassOS uses a different version of Linux under the hood and I’m not sure if that command would work from a console.

I modified my configuration.yaml file and have this at the bottom of my file within the sensor: area.

  - platform: systemmonitor
    resources:
      - type: disk_use_percent
        arg: /config
      - type: disk_use
        arg: /
      - type: memory_free
      - type: processor_use
      - type: processor_temperature

Set the value to 30 or 35 and that should be low enough to test it.