thanks - here it is: https://paste.ubuntu.com/p/nJ6VMKQn9s/ and here https://paste.ubuntu.com/p/x95M2Jgfnj/ is the log from the host
1 Like
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?
1 Like
Addon log is required from after the 2nd hard power-off-reboot.
i had to start the add-on, I did not have it start automatically on boot - is that an issue?
No. Itās not an issue at all. There is no start at boot option. The log shows you restarted the addon without rebooting.
Sorry but Iām not sure I understand. I ran the add-on, checked the log. then stopped HA and unplugged it. Did that twice. Started up again. Started the add-on. Copied the log. Am I misunderstanding something ? tx for your help!
By the way I also keep getting the ff message on the CLI: /dev/sda1: Canāt open blockdev. Not sure if thatās related and I donāt know when it was triggeredā¦
It says itās already configured on sda1. It says it couldnāt access sdb1. Youāve run the addon before without rebooting. This means a reboot is required.
The CLI log messages are normal and can be ignored.
okā¦sorry for my ignorance but how do I boot in that case? I have rebooted so often - but I shut down HA first in the configuration/server controls/server management option before pulling the power and powering back up. Is that not the right way? Or is it related to the fact that I have a Raspbee II HAT installedā¦some conflict? Just guessing now.
Can you think of a reason HA isnāt using sda1 for your config values? Are you using HassOS?
sorry Iām not familiar with that - just trying to get a fan to work. I donāt know what sda1 is - is that where my SSD is mounted? Yes I am using HassOS
The host log shows this:
2.709093] i2c i2c-11: Added multiplexed i2c bus 0
2.710704] i2c i2c-11: Added multiplexed i2c bus 10
I see that, but Iām expecting i2c-1.
What is the use case you have for i2c? Do you have the device hooked up? What errors do you see during CLI startup? Can you share the output of dmesg from a no-protection-mode ssh terminal?
Apparently, HassOS isnāt consuming the ā/boot/CONFIG/ā files we expected it to consume. This suggests the system wasnāt rebooted, or HassOS has a problem and needs a bug report.
Thereās always the official instructions to try before filing a bug report with Home Assistant. https://www.home-assistant.io/hassio/enable_i2c/
Use case is this fan. I have followed the official guide, both directly connecting the SSD to another computer and through CLI. The files are there, the contents is ok, as you say it looks like somehow that configuration is not taken into account. Will look for the logs.
It works now: I used hassos-overlay\etc\modules-load.d\rpi-i2c.conf and somehow that workedā¦
Can you explain how it was used?
I have no idea to be perfectly honest, even though I would love to understand. Most instructions only change config.txt in the boot partition root and rpi-i2c.conf in CONFIG/modules. This post mentioned the hassos-overlay partition. I tried and was lucky. Sorry I canāt be of more help.
hi does I2c also work on mcp23017 and bme680? or is it pure integration to connect only SSD HDD?
Iām working on it. Please check back over the weekend.