@oferbar, @LtraVulgaris, you both need to enable i2c. There are other threads to help with this.
A hard reset dit the job! Thanks
Hi @adamoutler,
I encountered an issue and not sure how to proceed. I installed the addon on a fresh new setup recently (about a month ago) it seamed fine but today when fiddling with the UI, I tried to create a entity card with the Argon One fan speed, and realised the addon stopped working. I am quite sure it worked previously as I tested it with a lower temperature threshold and the fan started. Funny enough the fan is not on at the moment but the addon stopped. Please see bellow:
[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.4 (aarch64 / raspberrypi4-64)
Home Assistant Core: 2022.12.8
Home Assistant Supervisor: 2022.11.2
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
/run.sh: line 111: thePort: unbound variable
[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.
Any idea what could have caused this? or how to try and fix it?
Best regards,
Valentin
Looks like the hardware is not connected. The ports are enabled, but there’s no 1a/1b.
Everything is in the same setup from day one, in the Argon One case.
Any other explanation? PS: Recently updated the HA Core.
Well, Im running the latest HAOS and everything is working well. I had a problem updating but resolved it two nights ago so everything is running the latest version. I’d say this is likely a problem with your hardware. You can test by using an SDCard with Raspberry Pi OS and installing the Argon script to see how it compares.
After a restart the 1a appeared. now working and fan speed entity appeared.
1 Like
Are there any known issues or config-gotcha’s to prevent the fan from turning on then off every 30 seconds?
For example, the log shows repeats of -
2022-12-30_22:35:03: 44C - Level 2 - Fan 33% (Low)
2022-12-30_22:35:41: 40C - Level 1 - Fan 0% (OFF)
2022-12-30_22:36:11: 42C - Level 2 - Fan 33% (Low)
This is with the ‘Active Cooling’ Addon, with low set to 45c, medium set to 50c, high set to 60c.
I see similar with the linear, with the temp bouncing causing frequent spin up’s and downs.
I should also preface somewhat, this is with an argon fan hat, which uses the same script (I think) as a ArgonOne iirc…may be wrong about that though.
As a short term workaround, are we able to set a constant speed with any version of this addon?
Try Quiet Profile. It does 0,1,3,100%. Theres also the linear addon which will scale less dramatically. The option you’re using emulates the stock Argon One script.
Hi,
I tried with the Linear too, same issue.
RE: Quiet Profile, 1% & 3%?
Is there a reasoning for those being as they are?
Hi
Is this only for HA installed on the argon itself?
My HA is installed on another server but would like to control the remote argons fan from HA, is this possible with this?
Also, is this compatible with the argon eon?
Thanks
Quick question.
Does the Argon One M2 interfer with the raspberry pi4 Bluetooth?
Slightly out of topic here I know, but just trying to narrow down a long time Bluetooth issues. Running the latest HA OS and always used Agon One cases, was looking forward to HA Bluetooth implementation early in the year but never worked for me.
Tya
And happy new year 
On quiet profile -
2022-12-31_15:51:59: 39C - Level 1 - Fan 0% (OFF)
2022-12-31_15:52:29: 42C - Level 2 - Fan 1% (Quiet Low)
2022-12-31_15:53:07: 39C - Level 1 - Fan 0% (OFF)
2022-12-31_15:53:37: 42C - Level 2 - Fan 1% (Quiet Low)
2022-12-31_15:54:37: 40C - Level 1 - Fan 0% (OFF)
2022-12-31_15:55:07: 42C - Level 2 - Fan 1% (Quiet Low)
2022-12-31_15:56:07: 40C - Level 1 - Fan 0% (OFF)
2022-12-31_15:56:37: 42C - Level 2 - Fan 1% (Quiet Low)
2022-12-31_15:57:07: 40C - Level 1 - Fan 0% (OFF)
2022-12-31_15:57:37: 42C - Level 2 - Fan 1% (Quiet Low)
2022-12-31_15:58:37: 39C - Level 1 - Fan 0% (OFF)
2022-12-31_15:59:07: 42C - Level 2 - Fan 1% (Quiet Low)
2022-12-31_16:00:07: 38C - Level 1 - Fan 0% (OFF)
2022-12-31_16:00:37: 41C - Level 2 - Fan 1% (Quiet Low)
2022-12-31_16:01:37: 40C - Level 1 - Fan 0% (OFF)
2022-12-31_16:02:07: 41C - Level 2 - Fan 1% (Quiet Low)
2022-12-31_16:02:37: 40C - Level 1 - Fan 0% (OFF)
2022-12-31_16:03:15: 42C - Level 2 - Fan 1% (Quiet Low)
2022-12-31_16:04:15: 39C - Level 1 - Fan 0% (OFF)
Can’t be good for the fan’s motor…
You’d be better off asking this on an Argon based forum, this addon is specifically for controlling the fan on an Argon case/HAT.
Its based on sound profile for more even ramping. The 33% is practically 100% airflow due to restrictions, and there’s a huge cooling difference between 0,1, and 3.
Its Active cooling meaning it’s monitoring and adjusting. If its not, then its not active.
Fair enough.
The same issue appears with the Linear addon too. Worth trying the linear classic?
It’s a metal case. RF isn’t the best behind metal.
1 Like
Thanks for the swift reply!
Yes, not the ideal case for it, but what I meant to ask is if it uses any resources like I2C that may otherwise be reserved for the Bluetooth. Only asking because I get an error when turning passive scanning off in Homeassistant.
16725875976945544985066220877521|375x500
Logger: homeassistant.config_entries
Source: config_entries.py:1113
First occurred: 15:39:22 (2 occurrences)
Last logged: 15:41:24
Config entry 'DC:A6:32:2F:3C:D6' for bluetooth integration not ready yet: hci0 (DC:A6:32:2F:3C:D6): Failed to start Bluetooth: [org.bluez.Error.NotReady] Resource Not Ready; Retrying in background
Logger: bluetooth_auto_recovery.recover
Source: components/bluetooth/util.py:43
First occurred: 00:13:38 (473 occurrences)
Last logged: 15:42:59
Bluetooth adapter hci0 [DC:A6:32:2F:3C:D6] could not be reset due to timeout
Many thanks
Jorge
Nope. Not a thing from this addon. Mine works fine… although, low signal.
1 Like
Had to resort to a clean install, all working fine here too now. many thanks 