I can see temperature of my Pi4, but the add-on log tells me Error: Write failed when it tries to write values to Fan speed. Am I missing something here? Your help would be greatly appreciated.
THANKS!!
-----------------------------------------------------------
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: 2021.12.7
Home Assistant Supervisor: 2021.12.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.
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 39 °C
2022-01-02_11:17:34: 39C - 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 39 °C
2022-01-02_11:18:04: 39C - Level 1 - Fan 0% (OFF)
Error: Write failed
Failed 78: i2cset -y 1 0x01a "${fanPercentHex}"
Error: Write failed
Maybe this issue is linked with This entity does not have a unique ID?
Please note the picture below is an example because my HA interface is in french so I took a picture showing the same warning on This entity does not have a unique ID? - Home Assistant
Can anyone one help with this issue?
@ adamoutler Are you still working on your add-on?
Amazing! I just installed your Add-on as a Local Add-on and what a relief when my Argon One Fan finally stopped!! I’m so thankful Znany! Very thankful!! So I guess @adamoutler1 should look into it for a future update. Thanks again!!!
EDIT: I just realized @adamoutler1 profile has been suspended… I hope he can get back to this forum soon and update his add-on. This add-on is just amazing and it needs to be updated with yours @Znany
Happy to hear that it helped
Unfortunately, I am not pro, I just found workaround for issue so if there is somebody who is more experienced in building add-ons - it just requires to add ability to pick i2c device on configuration panel and everythinkg should work for everyone
I believe the Argon One Active Cooling Addon doesn’t use the GPIO integration. It is running in it’s own docker container and drives the GPIOs directly (well directly via I2C).
@adamoutler (the writer of this addon) has a suspended account so it may be hard to ask him, if you are unable to confirm this by checking the code on Github.
I took a backup of the rpo_gpio integration just in case but I didn’t put it in the custom components folder. I upgraded to 2022.2 and the addon and fan seems to still be working fine for me. I was under the impression that the gpio functionality in HA core was going to be removed so that would mean add-ons like this should not be affected (this seems to be true at least for now)
I bit the bullet and upgraded to 2022.02 and this has so far been a non-issue.
I’m using this addon on an Rpi4 with an Argon Fan hat.
As @zoogara noted, this addon is communicating with the fan hat using I2C communication even though the fan hat is mounted on the GPIO header.
I altered my configuration to change the lowrange value so the fan would come on, and it did.
The fan stopped running once the lowrange value was reached.
I appreciate ya’ll testing the upgrade and seemingly confirm it did NOT break this addon. I too am running an Argon One which has a GPIO fan and it is confusing what the impact may or might not be. I’m gonna sit a bit and see if any more issues arise or not.
This is expected behaviour.
If you read my message again, you would see that it will be deprecated beginning from the release of 2022.6 and not 2022.2!
But what will happen to the code for the Button of the Argon One case:
binary_sensor:
- platform: rpi_gpio
pull_mode: DOWN
ports:
4: Argon One Power Button
Hello @Znany,
I have upgraded my setup to run from SSD instead of SD card on HassOS on my Raspberry Pi 4, and while this add on worked perfectly fine on SD card, it is no longer correctly detecting the Argon case on I2C, so I suspect there is a need to change this in the code. Would you be able to point me to the potential fix, please?
Thank you!
Cc @adamoutler1
ARGON ONE M.2
i try intgration ArgonOne Active Cooling but its not work
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.
Cannot find I2C port. You must enable I2C for this add-on to operate properly
Failed 1: source “$@”
Error: Could not open file /dev/i2c-1' or /dev/i2c/1’: No such file or directory
Failed 1: source “$@”
Error: Could not open file /dev/i2c-1' or /dev/i2c/1’: No such file or directory
[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.
HassOS I2C ConfiguratorHassOS I2C Configurator
Current version: 0.13
but its not work
help
I don’t see I2C.
mount: permission denied (are you root?)
Detected Protection Mode is enabled. Disable Protection Mode in Info Screen.
no sda1 config found
no sdb1 available
mount: permission denied (are you root?)
Detected Protection Mode is enabled. Disable Protection Mode in Info Screen.
no mmcblk0p1 config found
This Configurator did it’s job. Perform a hard-power-off reboot now.
You will need to reboot twice total, once to place the files, and again to activate the I2C.
Disable Protection Mode in Info Screen?Apologies in advance I’m new-from where
Perform a hard-power-off reboot now?Apologies in advance I’m new-from where from the Host?
In the information screen of the I2C Addon there should be four switches, the lowest should be switched off.
You should perform a shutdown of the Pi and then switch it off completeley, eg. pull out the USB-C cable. Then switch it on again, wait until it is started and switch it back off.
Then you are ready.
