Hey @arrows. I just noticed this is theholyrogerβs fork from adamoutler. Adamβs repo is usually pretty good at keeping it updated. I have both so I got confused at who was who. So @ TheHolyRoger may have broke his fork.
@adamoutler Is there any way you could scrape ole holyrogerβs to add a few sensors? Thatβs the only reason I have his lol. It would make urs more robust.
Iβm not willing to add any sensors. This is intended to be lightweight and not processor intensive so it saves power. I am trying to keep it minimal.
Ok I understand totally keeping it simplistic⦠Not sure what you mean by battery?
Power. I meant power.
lol I thought you had a portable setup or something. I get yah
@adamoutler I just setup my new Argon One M.2 and installed your fan control add-on. Works perfect!
Two questions though:
-
I donβt seem to find much difference between 1% or 3% and 100% fan speed. I 'didnβt measure the fan rpm but the fan sound remains unaffected whether 1% or 100%. It sounds always like full speed.
-
I noticed huge increase in backup size after installing this add on. There is one file in backup βlocal_argon_one_temp.tar.gzβ which is more than 10MB! Rest of backup files constitutes only about 2MB. Although file size is not at all a concern as there is far more than enough space on disk , but just to control a fan the whole backup file size increasing by 6 times kind of feels like overkill . Why is this file so huge?
#1 is hard. You should notice a major difference. To troubleshoot youβll need to check the logs during startup and then install RPi OS and use the official tool to see if thereβs a difference.
#2. Certain versions get built locally and would probably be fully backed up if youβre also backing up the contents.
Thanks @jimmyz51501. I canβt remember why I switched to theholyrogerβs fork. Iβve switched back now. Nice to have the I2C part work smoothly regardless of the repo.
Thanks @adamoutler for giving a couple of options now!
Hello,
i got this plugin βhalfworkingβ and i am not sure what i am doing wrong.
At start/restart of it im getting the following loglines:
[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...
curl: (7) Couldn't connect to server
[20:39:45] 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 1 at /dev/i2c-1
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-1
I2C Port 1
Settings initialized. Argon One Detected. Beginning monitor..
Current Temperature 35 Β°C
2023-11-09_20:39:46: 35C - Level 2 - Fan 1% (Quiet Low)
/run.sh: socket: Permission denied
/run.sh: line 79: /dev/tcp/hassio/80: Permission denied
/run.sh: socket: Permission denied
Failed 79: exec 3<> /dev/tcp/hassio/80
Failed 79: exec 3<> /dev/tcp/hassio/80
/run.sh: line 79: /dev/tcp/hassio/80: Permission denied
Safe Mode Activated!
/run.sh: line 80: 3: Bad file descriptor
Failed 80: echo -ne "POST /homeassistant/api/states/sensor.argon_one_addon_fan_speed HTTP/1.1\r\n" 1>&3
Safe Mode Activated!
/run.sh: line 80: 3: Bad file descriptor
Failed 80: echo -ne "POST /homeassistant/api/states/sensor.argon_one_addon_fan_speed HTTP/1.1\r\n" 1>&3
Safe Mode Activated!
Failed 81: echo -ne "Connection: close\r\n" 1>&3
/run.sh: line 81: 3: Bad file descriptor
Safe Mode Activated!
/run.sh: line 81: 3: Bad file descriptor
Failed 81: echo -ne "Connection: close\r\n" 1>&3
Safe Mode Activated!
/run.sh: line 82: 3: Bad file descriptor
Failed 82: echo -ne "Authorization: Bearer ${SUPERVISOR_TOKEN}\r\n" 1>&3
Safe Mode Activated!
/run.sh: line 82: 3: Bad file descriptor
Failed 82: echo -ne "Authorization: Bearer ${SUPERVISOR_TOKEN}\r\n" 1>&3
Safe Mode Activated!
Safe Mode Activated!
/run.sh: line 83: 3: Bad file descriptor
Failed 83: echo -ne "Content-Length: $(echo -ne "${reqBody}" | wc -c)\r\n" 1>&3
Safe Mode Activated!
Failed 84: echo -ne "\r\n" 1>&3
/run.sh: line 83: /run.sh: line 84: 3: Bad file descriptor
3: Bad file descriptor
Failed 83: echo -ne "Content-Length: $(echo -ne "${reqBody}" | wc -c)\r\n" 1>&3
Safe Mode Activated!
/run.sh: line 85: 3: Bad file descriptor
Failed 85: echo -ne "${reqBody}" 1>&3
Safe Mode Activated!
/run.sh: line 55: 3: Bad file descriptor
Failed 86: timeout=5
Safe Mode Activated!
Failed 84: echo -ne "\r\n" 1>&3
/run.sh: line 84: 3: Bad file descriptor
Safe Mode Activated!
Failed 85: echo -ne "${reqBody}" 1>&3
Safe Mode Activated!
/run.sh: line 85: 3: Bad file descriptor
Safe Mode Activated!
Failed 86: timeout=5
/run.sh: line 55: 3: Bad file descriptor
Safe Mode Activated!
And after a few seconds i am getting Temperature readings so far nicely.
Running:
ArgonOne Active Cooling Version 30a
- Core 2023.11.1
- Supervisor 2023.11.0
- Operating System Debian 12.2
- Frontend 20231030.1
Hardware Pi4/4GB
Any idea what i am doing wrong?
Isnβt this:
the problem?
But HA is running smoothly and observer says:
Home Assistant observer
|Supervisor:|Connected|
|Supported:|Supported|
|Healthy:|Healthy|
Also in the setting there is no hint of the safe mode activated.
A few times i had an issue when HA was really running in Safe Mode β but this was always a fault of a configuration. But actually it is running fine.
Works perfectly for me.
Add-on version: 30a
System: Home Assistant OS 11.1 (aarch64 / raspberrypi4-64)
Home Assistant Core: 2023.11.2
Home Assistant Supervisor: 2023.11.3
This i2c add-on is really handy btw, thanks.
I managed to resolve it through some combination of
- re-flash HA to the SD card, restore from backup while not using the Argon case
- enable I2C by modifying the SD card
- reboot many times
Fingers crossed it doesnβt regress again
Btw about the logs you posted - do they get logged to disk? If so, wdyt about a configuration flag to turn off those logs? (I can write the code)
Thanks for all your work!
Hi
Can not get fan to work see log
can you help please
[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: 30a
You are running the latest version of this add-on.
System: Home Assistant OS 11.2 (aarch64 / raspberrypi4-64)
Home Assistant Core: 2023.12.3
Home Assistant Supervisor: 2023.11.6
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.
Hallo,
I have the same problem, clean installation of Debian 12 and HA supervised.
Running:
ArgonOne Active Cooling Version 30a
- Core 2023.12.3
- Supervisor 2023.12.1.dev2001
- Operating System Debian 12
- Frontend 20231208.2
Hardware Pi4/4GB
Home Assistant observer
Supervisor: Connected
Supported: Supported
Healthy: Healthy
[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...
curl: (7) Couldn't connect to server
[14:23:55] 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.
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 = 43 Β°C
2023-12-21_14:23:56: 43C - Fan 0% | hex:(0x00)
Error: Write failed
Failed 74: i2cset -y 1 0x01a "${fanPercentHex}"
Error: Write failed
Safe Mode Activated!
Failed 140: return ${returnValue}
/run.sh: socket: Permission denied
/run.sh: line 37: /dev/tcp/hassio/80: Permission denied
Failed 37: exec 3<> /dev/tcp/hassio/80
Error: Write failed
Error: Write failed
/run.sh: line 38: 3: Bad file descriptor
/run.sh: socket: Permission denied
/run.sh: line 37: /dev/tcp/hassio/80: Permission denied
Safe Mode Activated!
Safe Mode Activated!
Failed 38: echo -ne "POST /homeassistant/api/states/sensor.argon_one_addon_fan_speed HTTP/1.1\r\n" 1>&3
Failed 37: exec 3<> /dev/tcp/hassio/80
Error: Write failed
Safe Mode Activated!
Failed 38: echo -ne "POST /homeassistant/api/states/sensor.argon_one_addon_fan_speed HTTP/1.1\r\n" 1>&3
Safe Mode Activated!
Failed 39: echo -ne "Connection: close\r\n" 1>&3
/run.sh: line 38: 3: Bad file descriptor
Error: Write failed
/run.sh: line 39: 3: Bad file descriptor
Error: Write failed
Error: Write failed
/run.sh: line 39: 3: Bad file descriptor
/run.sh: line 40: 3: Bad file descriptor
Safe Mode Activated!
Did you modify it? This doesnβt seem to be detecting the proper device.
No, Itβs original. Just some DVB-Ts tuners are plugged in now, but same result was before with absolutely clear installation.
I have the same problem, please help fix it.
The error log is the same as yours.
Works like a dream with HAOS. It used to work with Debian. Maybe someone could jump in a d try to troubleshoot. I donβt run Debian.
Argon One Active Cooling not working for me after the HomeAssisant update.
See logs:
-----------------------------------------------------------
** Add-on version: 30a**
** You are running the latest version of this add-on.**
** System: Home Assistant OS 11.3 (aarch64 / raspberrypi4-64)**
** Home Assistant Core: 2024.1.2**
** Home Assistant Supervisor: 2023.12.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.
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 35 Β°C
2024-01-08_12:24:11: 35C - Level 1 - Fan 0% (OFF)
Error: Could not open file /dev/i2c-255' or
/dev/i2c/255β: No such file or directory
Failed 105: 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 216: return ${returnValue}
Error: Could not open file /dev/i2c-255' or
/dev/i2c/255β: No such file or directory
Safe Mode Activated!