You could always jump into the container. Disable Protection Mode on ssh then run
docker container ls
docker exec -it <container ID> bash
The container stays running for 99999 seconds for this reason.
But if you don’t see the devices, i2c tools won’t operate.
I’m off to bed now. I will check this again for proper operation tomorrow.
I started fresh and re flashed my SD card to the Hassio 64 Bit Raspberry Pi 4 image and ran this add on. Everything looked good but even after 2 reboots and 1 shutdown I still don’t see any i2c in /dev. I know the hardware is good as I can see their IDs using i2cdetect when booting under Raspberry Pi OS. I so wanted this to work but I don’t even know what questions to ask at this point.
Thanks for the developing this. I’ve followed the excellent guide Raspberry Pi 4, Home Assistant OS (5.5, dev version) on a SSD, and the Argon One M.2 Case (In Progress) by @FreelancerJ to the point of activating the fan. I’ve run the I2C Configurator and after a full shutdown and restart (a 1st reboot didn’t seem to be sufficient) it looks like that worked:
…
adding dtparam=i2c_vc=on to sda1 config.txt
adding dtparam=i2c_arm=on to sda1 config.txt
no sdb1 config found
no mmcblk0p1 config found
This Configurator did it’s job. You can uninstall and reboot now. This configurator only works once.
As I’m no Pi or Linux expert so this was an easy way to get I2C.
As for the Active Cooling addon, that’s working, the fan is on 
. I was using the default temperature settings where the low is 90F, however I couldn’t get below 95F-98F so the fan was running continuously. I’m not familiar with Pi4 temperatures so just wondering if you have deliberately set a low threshold. The HassOS is only running at just over 1% CPU so not exactly taxed. Anyway after looking at the Pi forums I’ve upped the low (100F) and medium values and it works great with the fan coming on occasionally.
Really happy to be running HA from SSD on a Pi4 device in a professional looking case, all with active cooling.
Disable Protection Mode on the SSH Addon and it should show up. That looks like a docker container with Protection Mode enabled. Addons must explicitly request a device, or have Protection Mode disabled to see devices in /dev/
I saw the problem and I thought to myself, “Self, since you already have access to the files, why not just show them the files?”, then I thought to myself, “Hey, self, that’s a great idea”, then I though to myself, “Yeah, I know, self, you came up with it!”. This went on for a while. Long story short, you can now see the output of the ls command and a “Found i2c access!” message when successful.
Please update.
You no longer need to disable protection mode. I changed some settings and disabled App Armor. We went from this:
Is this correct?
Shouldn‘t it be the I2C Configurator that has to be installed?
Correct! I had a malfunction in the copy-pasta subsystem.
That is great. Where can I get it?
Not working on my RPi4 with Home Assistant OS 5.10. More than 10 reboots and still getting these logs:
[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] done.
[services.d] starting services
[services.d] done.
ls: /dev/i2c-1: No such file or directory
I don’t see I2C.
i2c already configured on sda1
i2c already configured on sda1
no sdb1 config found
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.
Hardware:
Rpi4
Argon ONE M.2
WD Green 120gb
Confirmed. It’s working on mine and I’m seeing the same logs. Let me check into it.
Nice, it’s working perfectly with “ArgonOne Active Cooling”
thanks a lot for this utility. Unfortunately no luck on my rpi 4 - could this be because I’m booting from an SSD?
Please check the logs and place them here. A common problem is that you need to reboot twice. Full, power-off, pull-the-plug, reboot.
thanks - here it is: https://paste.ubuntu.com/p/nJ6VMKQn9s/ and here https://paste.ubuntu.com/p/x95M2Jgfnj/ is the log from the host
Ok. Now, hard-power-off the unit and power it back on. I need the log from after the power cycle. This shows the addon was run for a second time during the same boot. Restarting HA or the supervisor isn’t enough. It has to be a hard power down or “reboot host”.
ok will do, but in the mean time i have power cycled about 6 times already trying different things, editing the files manually etc. You need the host log or the add-on log?
Addon log is required from after the 2nd hard power-off-reboot.
