[add-on] HassOS I2C Configurator

Burkard · January 14, 2023, 2:36pm

Now I did a complete reinstallation of HassOS I2C Configurator with disabled protected mode and rebooted the device via power cord pull twice. I still get this protocol message from HassOS I2C Configurator:

brw-rw----    1 root     disk      254,   1 Jun  2  2022 zram1
brw-rw----    1 root     disk      254,   2 Jun  2  2022 zram2
ls: /dev/i2c-1: No such file or directory
I don't see I2C.
dtparam=i2c_vc=on
i2c already configured on sda1. Reboot required.
dtparam=i2c_arm=on
dtparam=i2c_arm=on
i2c already configured on sda1. This addon was already run during this boot and no reboot occurred. 
mount: mounting /dev/sdb1 on /tmp/sdb1 failed: No such file or directory
no sdb1 config found
no mmcblk0p1 available
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.

Any further idea?

adamoutler · January 14, 2023, 4:38pm

Lets see the log directly after a pull-the-plug reboot.

Burkard · January 14, 2023, 6:13pm

Directly after a pull-the-plug reboot the HassOS I2C Configurator did not start automatically, although the start switch is on; I had to start it by hand. Then the protocol looks like this:

crw-------    1 root     root      247,   0 Jun  2  2022 watchdog0
crw-rw-rw-    1 root     root        1,   5 Jun  2  2022 zero
brw-rw----    1 root     disk      254,   0 Jun  2  2022 zram0
brw-rw----    1 root     disk      254,   1 Jun  2  2022 zram1
brw-rw----    1 root     disk      254,   2 Jun  2  2022 zram2
ls: /dev/i2c-1: No such file or directory
I don't see I2C.
dtparam=i2c_vc=on
i2c already configured on sda1. Reboot required.
dtparam=i2c_arm=on
dtparam=i2c_arm=on
i2c already configured on sda1. This addon was already run during this boot and no reboot occurred. 
mount: mounting /dev/sdb1 on /tmp/sdb1 failed: No such file or directory
no sdb1 config found
no mmcblk0p1 available
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.

adamoutler · January 14, 2023, 8:29pm

I’m not sure what’s going on here, but its saying this is the second time the addon was run during this boot. It’s detected this by looking for a file it places that is automatically removed by Home Assistant during HAOS boot up. For some reason your machine is not booting from the SDA or it’s not using this file, or it isnt able to write or delete that file.

Burkard · January 14, 2023, 10:20pm

Oh, my system boots from SSD. Maybe that causes the problem?

adamoutler · January 14, 2023, 10:31pm

Is the SSD the sda drive?

Burkard · January 14, 2023, 11:26pm

Yes, it is.

adamoutler · January 15, 2023, 12:53am

That wouldn’t be the problem then. If its booting from sda, not microsd, and those files on are on sda1, they should be acted upon and removed by the OS at startup.

Burkard · January 15, 2023, 7:44am

In /config.txt of my /dev/sda1 I find:

dtparam=i2c1=on
dtparam=i2c_arm=on
dtparam=i2c_vc=on
dtparam=i2s=on

and lsmod | grep i2c shows:

i2c_mux_pinctrl        16384  0
i2c_mux                16384  1 i2c_mux_pinctrl
i2c_bcm2835            16384  0

but there is still no i2c device:

# ls /dev/i2*
ls: /dev/i2*: No such file or directory

Maybe a hardware issue?

Burkard · January 15, 2023, 10:32am

I added file named ‘rpi-i2c.conf’ to the directory /etc/modules-load.d/ with following lines in it:

i2c-dev
i2c-bcm2835

Now I see i2c devices:

# ls -l /dev/i2*
crw-------    1 root     root       89,   0 Jun  2  2022 /dev/i2c-0
crw-------    1 root     root       89,   1 Jun  2  2022 /dev/i2c-1
crw-------    1 root     root       89,  10 Jun  2  2022 /dev/i2c-10
crw-------    1 root     root       89,  22 Jun  2  2022 /dev/i2c-22
#

And everything works fine

Thanks a lot for your support, Adam!

adamoutler · January 16, 2023, 10:35pm

Did you try something else prior to this? It seems it was 1/2 installed before you ran the app.

Burkard · January 17, 2023, 6:36am

Yes, I tried to activate i2c by hand and uncommented the i2c related entries in my /config.txt before I found your tool. But I didn’n succeed . . .

adamoutler · January 17, 2023, 12:06pm

This tool uses the commented entries to determine the need to apply the other files. If you had run it with the entries commented it would have worked fine.

Burkard · January 17, 2023, 4:38pm

Ok, I see. Next time I use your tool I leave the i2c entries commented. It would have been helpful if I had this information before… Thank you for your advice, Adam!

adamoutler · January 17, 2023, 5:56pm

Updated faq. This is a new one.

Burkard · January 17, 2023, 6:15pm

Perfect, thanks!

portalras · February 22, 2023, 1:14am

Hello

My system appears only this log and does not change. I’ve restarted twice and I don’t know what’s wrong. My Argoone has a 256GB SSD
log:
ls: /dev/i2c-1: No such file or directory
I don’t see I2C.
mount: permission denied (are you root?)
Detected Protection Mode is enabled. Disable Protection Mode in Info Screen.
in sda1 config found
no sdb1 available
no mmcblk0p1 available
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.

adamoutler · February 22, 2023, 1:28am

Check the FAQ in the first post.

portalras · February 22, 2023, 1:40am

Sorry I’m new to home assistant and I started a week ago. I’m still getting familiar with everything. I informed you above that I use an SSD, but I was wrong. I use an M.2 as HD in Argoone.

portalras · February 22, 2023, 1:41am

I read all the posts and it didn’t help me.