Case in point. They just released Core 2024.11.2 and I had to add ‘allow net,’ to the apparmor profile…
Hi Adam, Can You help me about one issue?
System: Home Assistant OS 13.2 (aarch64 / raspberrypi4-64)
Home Assistant Core: 2024.11.3
Home Assistant Supervisor: 2024.11.4
[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: – – – – – – – – – – 1a – – – – –
20: – – – – – – – – – – – – – – – –
30: – – – – – – – – – – – – – – – –
40: – – – – – – – – – – – – – – – –
50: – – – – – – – – – – – – – – – –
60: – – – – – – – – – – – – – – – –
70: – – – – – – – –
found at /dev/i2c-1
I2C Port 1
Settings initialized. Argon One Detected. Beginning monitor…
Current Temperature = 33 °C
2024-11-23_14:39:45: 33C - Fan 0% | hex:(0x00)
Current Temperature = 29 °C
2024-11-23_14:40:15: 29C - Fan 0% | hex:(0x00)
Current Temperature = 29 °C
2024-11-23_14:40:45: 29C - Fan 0% | hex:(0x00)
Current Temperature = 27 °C
2024-11-23_14:41:15: 27C - Fan 0% | hex:(0x00)
Current Temperature = 29 °C
2024-11-23_14:41:45: 29C - Fan 0% | hex:(0x00)
Current Temperature = 28 °C
2024-11-23_14:42:15: 28C - Fan 0% | hex:(0x00)
Current Temperature = 30 °C
2024-11-23_14:42:45: 30C - Fan 0% | hex:(0x00)
Current Temperature = 29 °C
2024-11-23_14:43:15: 29C - Fan 0% | hex:(0x00)
So, it seems, that the Your ADD ON works properly, but in some reason the temperatures don’t switch the Fan ON or OFF. What can I do?
I have set the parameters that the fan should stop when the temp is 35 Celsius, and start again until it will reached 45 decree Celsius.
Hi Olli,
did You ever solve this problem? I have same issue with that fan control. Everything seems to be ok, but the fan does not stop/start according to temperatures.
Your system shows the temp is lower than your setpoint and that would turn the fan off.
Thank You for the answer. Ok… that was the situation at that moment, when I take the log-capture to this site, but even though it is above the limits, it dosen’t change the status of fan. So, the software functioning right, but it dosen’t effect the real fan inside the raspberry case…
Argon One Active Cooling removed from HA Add-In repository. Where now? @adamoutler
It still works, so I’m keeping it installed for now.
Maybe you removed the repository?
It isn’t anything I’ve changed.
I’m running a Supervised installation. It all worked fine until I updated the core to:
- Core2024.12.0
- Supervisor2024.11.4
- Operating System
- Frontend20241127.7
(I’m currently running Core2024.12.2)
My repository configuration looks like this:
It won’t let me remove your repository because it is still in use but the Community Repository list has nothing beginning with ‘Argon’
(I wanted to include a screen clip here but I dont have sufficient privilege to include more than one .png per post)
Of interest - the EweLink (CoolKit-Technologies) add-on has also suffered the same fate.
My guess (and it is a guess) is that it has been deprecated from the Supervised installation but not the HassOS configuration. This surmise is based on the observation that you are not aware of any problem. What’s your opinion?
Mark
@adamoutler Hi Adam - thanks for your gentle prompting. I have now worked out what is happening. The issue was rooted in DNS. hassio_dns was unable to resolve github.com vie the DNS on my router. I re-configured it to use the google DNS resolver and everything has come back to life.
Now I need to work out WHY - but that is a story for another day. Thanks again.
Mark
I am also seeing the same message in:
Home Assistant - Raspberry Pi 4
- Core 2024.12.3
- Supervisor 2024.12.0
- Operating System 14.0
- Frontend 20241127.8
I can resolve github.com without error
The repo and apps are still there. They’re not going away.
I rebooted the entire Pi and now the message about it being removed is no longer present and it still appears in the list of add-ons
Thank you for your efforts.
I have been using this add-on successfully, but recently I have encountered an issue where it is not functioning properly.
While the i2c add-on indicates no issues, the Argon add-on reports that it cannot detect i2c.
What should I check to resolve this issue?
The relevant logs are as follows:
[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 V3 Active Linear Cooling
Actively keeping your ArgonOne V3 cool.
Add-on version: 30a
You are running the latest version of this add-on.
System: Home Assistant OS 14.1 (aarch64 / raspberrypi4-64)
Home Assistant Core: 2024.12.4
Home Assistant Supervisor: 2024.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: – – – – – – – –
/run.sh: line 117: thePort: unbound variable
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.
@MallocArray It isn’t enough to be able to resolve (or ping) github.com - check the DNS logs (dropdown at top right) in Settings/System/Logs to see if there are errors logged there. These went away when I updated the host resolver to use google dns - this only applies for the Supervised installation, yours may differ.
Interestingly enough, I haven’t had any recurrence of this since upgrading the Core to 2024.12.5 - even while using my router as DNS resolver. I didn’t see anything in the Release Notes to say anything had been changed in this area, but you never know; fingers crossed, this issue has been resolved.
I have a similar issue and similar error in the logs. The add-on does not start but I2C configurator indicates no issues.
Any ideas?
I face an issue where all of a sudden the ventilator starts to run at 100%
When looking at the log, it states
Current Temperature = 45 °C
2025-01-04_13:54:48: 45C - Fan 0% | hex:(0x00)
Current Temperature = 44 °C
2025-01-04_13:55:18: 44C - Fan 0% | hex:(0x00)
Error: Write failed
Failed 96: i2cset -y "${port}" "0x01a" "0x80" "${fanPercentHex}"
Safe Mode Activated!
Failed 160: return "${returnValue}"
Safe Mode Activated!
Current Temperature = 44 °C
2025-01-04_13:55:49: 44C - Fan 0% | hex:(0x00)
Current Temperature = 44 °C
2025-01-04_13:56:19: 44C - Fan 0% | hex:(0x00)
I interpret this as some “fallback” mode with 100% fan. unfortunately it never recovers from that 100% fan unless I completely reboot.
I am using ArgonOne V3 Active Linear Cooling with an ArgonOne V2 housing.
Any idea ?