I got it, thank you
i have argon miniFan
how do i get started in HASS
gpiopin=18
Help needed.
Tried your configurator in HA OS and worked like a charm. But needed to run HA in Docker, so reinstalled to Debian 11 and installed HA supervised as docker.
But now I am stuck. Running your program with protection disable just says
nothing to do. Is protection mode enabled? You can’t run this without disabling protection mode
I have installed a SSH add on and disabled protection in it. I have stoped debian built in ssh so that HA SSH addon can listen on port 22 so I am sure that the configurator is using that one. But still no go. Same error.
Any ide?
RPI 4 sdcard.
Is docker running as root?
Yes it was. But I gave up (had a few hours awake during night with nothing to do), tried a HA docker supervised installation on “unsuported” rasberry OS and it work fine. Super easy to activate i2c. So will run it now and see if there is any problem. Thank you for quick reply!
Just wanted to add that I was stuck on the “Disable Protection Mode” step. The reason was that, although the FAQ mentions that you need to disable it, I came across this post when scrolling just a bit and assumed that both the FAQ and logs were outdated.
After being stuck for a bit I looked more in the thread and found this post. Disabled protection mode and success.
I think it would be worth marking the 1st post with an edit at the top just in case others see it and make incorrect assumptions like I did.
1 Like
I think this might be beyond the scope of this add-on, but just in case it’s not: I’m having trouble actually interacting with i2c, but it looks like it might be detected correctly.
Specifically, I’m trying to run this command to auto-boot the pi (Argon-ONE-i2c-Codes/README.md at dc887d686f989b2e144488995d76413c561e2d96 · Argon40Tech/Argon-ONE-i2c-Codes · GitHub), but I’m getting “operation not permitted”, and it seems like very few people online have run into similar problems.
I’m running HAOS on an SD card, latest stable version of everything.
When I run ls /dev, the i2c devices (0,1, 10, 22) all show up.
However, when I run i2cdetect -l, I get unknown and NA in the output next to those devices. If i run i2cdetect -y 1 or i2cset -y 1, I get Error: Could not open file dev/i2c-1': Operation not permitted.
Any ideas? I tried re-running this script but I get the success message, and hard rebooting by physically pulling the power didn’t change anything either. I also tried prepending (and not) all of these commands with sudo, and explicitly changing to root with sudo su (interesting side note: by default, echo $USER returned nothing; I wonder whether a docker user misconfiguration in HAOS has led to some of the other problems I’ve seen online while digging into this).
hi, since yesterday I changed the temperature of argon one and now I get this again
` " 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 49°C
2023-06-25_08:00:40: 49C - Level 2 - Fan 1% (Quiet Low)
Error: Could not open file /dev/i2c-255' or /dev/i2c/255’: No such file or directory
Failed 98: 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 209: return ${returnValue}
Error: Could not open file /dev/i2c-255' or /dev/i2c/255’: No such file or directory
Safe Mode Activated! " `
I tried to redo the procedure with HassOS I2C restarting it twice and it gives me this
" brw-rw---- 1 root disk 254, 2 Apr 4 12:55 zram2 /dev/i2c-1 /dev/i2c-0 /dev/i2c-1 /dev/i2c-10 /dev/i2c-22 Found i2c access! Nothing to do! You can remove this add-on. "
How can I fix it??
Enable i2c
sorry can you help me understand how?
The other day after updating the HA OS kernel, the fan stopped working. Reinstalling and resetting didn’t help, nor did reusing HassOS I2C Configurator.
The following helped me:
I connected my ssd to the computer, found the config.txt file. and uncommented the lines containing ‘i2c’. Then I put it back in place and it worked.
P.S. I hope that this information will be useful to someone.
Tasked failed successfully. Im quiet unexperienced. Already tried to reboot and I’m still waiting. Any idea
I have the same issue, I only see the “HassOS Configurator” headline but no card to click on.
RPI4 HassOS 11.1 running from internal SSD drive.
Can’t do anything without logs.
I went into Settings/System/logs and only found what you see below. Is that the logs you were looking for? (I am quite new to Hass):
2023-11-29 22:21:50.363 WARNING (MainThread) [homeassistant.components.zha.core.cluster_handlers] [0x954B:1:0x0006]: async_initialize: all attempts have failed: [DeliveryError(‘Failed to deliver message: <EmberStatus.DELIVERY_FAILED: 102>’), DeliveryError(‘Failed to deliver message: <EmberStatus.DELIVERY_FAILED: 102>’), DeliveryError(‘Failed to deliver message: <EmberStatus.DELIVERY_FAILED: 102>’), DeliveryError(‘Failed to deliver message: <EmberStatus.DELIVERY_FAILED: 102>’)]
2023-11-29 22:21:50.615 WARNING (MainThread) [homeassistant.components.zha.core.cluster_handlers] [0x6AFB:1:0x0006]: async_initialize: all attempts have failed: [DeliveryError(‘Failed to deliver message: <EmberStatus.DELIVERY_FAILED: 102>’), DeliveryError(‘Failed to deliver message: <EmberStatus.DELIVERY_FAILED: 102>’), DeliveryError(‘Failed to deliver message: <EmberStatus.DELIVERY_FAILED: 102>’), DeliveryError(‘Failed to deliver message: <EmberStatus.DELIVERY_FAILED: 102>’)]
2023-11-29 22:21:51.003 WARNING (MainThread) [homeassistant.components.zha.core.cluster_handlers] [0x954B:1:0x0008]: async_initialize: all attempts have failed: [DeliveryError(‘Failed to deliver message: <EmberStatus.DELIVERY_FAILED: 102>’), DeliveryError(‘Failed to deliver message: <EmberStatus.DELIVERY_FAILED: 102>’), DeliveryError(‘Failed to deliver message: <EmberStatus.DELIVERY_FAILED: 102>’), DeliveryError(‘Failed to deliver message: <EmberStatus.DELIVERY_FAILED: 102>’)]
2023-11-29 22:21:51.390 WARNING (MainThread) [homeassistant.components.zha.core.cluster_handlers] [0x4586:1:0x0001]: async_initialize: all attempts have failed: [DeliveryError(‘Failed to deliver message: <EmberStatus.DELIVERY_FAILED: 102>’), DeliveryError(‘Failed to deliver message: <EmberStatus.DELIVERY_FAILED: 102>’), DeliveryError(‘Failed to deliver message: <EmberStatus.DELIVERY_FAILED: 102>’), DeliveryError(‘Failed to deliver message: <EmberStatus.DELIVERY_FAILED: 102>’)]
2023-11-29 22:21:51.431 WARNING (MainThread) [homeassistant.components.zha.core.cluster_handlers] [0x6AFB:1:0x0008]: async_initialize: all attempts have failed: [DeliveryError(‘Failed to deliver message: <EmberStatus.DELIVERY_FAILED: 102>’), DeliveryError(‘Failed to deliver message: <EmberStatus.DELIVERY_FAILED: 102>’), DeliveryError(‘Failed to deliver message: <EmberStatus.DELIVERY_FAILED: 102>’), DeliveryError(‘Failed to deliver message: <EmberStatus.DELIVERY_FAILED: 102>’)]
Logs from this addon, not your zigbee home Assistant error messages.
The problem is that I can’t download the HassOS configuration add on, only the headline shows but no install link. I need this to configure the i2c bus so I can start using your other add one for my Argon enclosure.
You need to enable Advanced Mode in HA. I had this issue too until I spotted this:
Have Raspberry Pi 5 8GB with Argon One V3 M2 NVMe case getting log Nothing to do Is protection mode enabled when it is disabled - restarted multiple times same issue ? Advanced mode also enabled …
Thank you for specifying V3. I searched and it apparently uses a PWM output instead of i2c. This is a significant deviation from v1/v2 which are supported. I don’t have a V3 unit so I cannot create a version which will work for that unit. However I will accept a patch and/or a donation to purchase a unit.