I just installed fresh on a system to ensure it works.
Looks like you’re having problems reaching the “main” docker repository for Home Assistant Add-ons from your internet connection. It says it’s a temporary error and you should try again later. Not sure what could be causing it, maybe bad internet, fire wall, or something else.
I will try it out. And thank you for the advice regarding read/echo and cat! I copied this piece of code from this forum.
@adamoutler Thank you for creating this addon. I failed to install the latest version. It seems that the latest commit causes that.
Function mkfloat is used before definition. I tried to fix it in my fork, but with no luck.
Logs below:
[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.
/run.sh: line 7: mkfloat: command not found
[cmd] /run.sh exited 127
[cont-finish.d] executing container finish scripts...
[cont-finish.d] done.
[s6-finish] waiting for services.
[s6-finish] sending all processes the TERM signal.
[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.
/run.sh: line 7: mkfloat: command not found
[cmd] /run.sh exited 127
[cont-finish.d] executing container finish scripts…
[cont-finish.d] done.
[s6-finish] waiting for services.
[s6-finish] sending all processes the TERM signal.
I am also unable to run this, How do I check I enabled i2c properly? I put ssd into computer and followed instructions but don’t know where to look for…
The I2C devices should now be present under /dev.
@Tim_Knowlden
I did some refactoring and caused an error. Everything is operational and this will not happen again.
Okay no worries, will attempt reinstall now and see if it works for me 
Yes it is working now for me, thank you.
Do you know how I can see the state of the fan as an entity so I can add it to my pi info entities?
There is no way to pull that information from the i2c bus, as far as I know. The best I could do is report it. Reporting can be done from Terminal/bash without any dependencies as follows
sensorid=input_number.fan_speed
name="Fan Speed"
state=3
unit="%"
reqBody='{"state": "'${state}'", "attributes": {"unit_of_measurement": "%","mode":"slider", "min":"0", "max":"100", "step":"1", "icon": "mdi:clock-start", "friendly_name": "'${name}'"}}'
nc -i 1 hassio 80 <<<unix2dos<<EOF
POST /homeassistant/api/states/$sensorid HTTP/1.1
Authorization: Bearer ${SUPERVISOR_TOKEN}
Content-Length: $( busybox echo -n ${reqBody} | wc -c )
${reqBody}
EOF
This produces the following in Lovelace:
As you can see, the UI complains because the ID is not properly registered with HA. From reading on the forums, I can see that it requires python to properly register a sensor. I think that python may be outside the scope of this addon.
If you can figure out how to properly register a sensor via API without reboot, then I’d be willing to make the change. If this meets your needs, then I’d be willing to make the change as well.
Many thanks for this great add on. It would be great if there is a sensor in HA. If you can, yes please
Tip:
At the I2C configurator page there is the step to reboot you’re Home Assistant. I did twice but didn’t work, I realised the HOST must shut down twice. Makes sense because of the modification in the file system. Just a tip for small update on this page to mention this.
Again, thanks for this great add on. My HA is running smoothly in the Argon one M2 with a SSD
I set the default temperatues to the same stock defaults from the manual
I feel these are kinda high, so I recommend using my suggested values, in the first post, instead. However, they are default.
This looks handy - will it work on a supervised installation on Debian?
If you’re running a Raspberry Pi with add-on capabilities, it will work. If it doesn’t work, then we can make it work.
Super - I used raspi-config to switch on I2C then tried installing the add-on but got the same error message reported by schumi1337 above
The command '/bin/ash -o pipefail -c apk add i2c-tools --no-cache' returned a non-zero code: 1
Kind thoughts,
Andrew
Looks like debian used debian-based containers instead of alpine Linux which was expected. I guess I need to support both. I don’t have a debian-based Home Assistant, but I think I know how to handle it. Try upgrading to v0.12a
Installed ok.
Error on startup in log:
[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.
Current Temperature 53 °C
Level 1 - Fan 0% (OFF)
/run.sh: line 83: i2cset: command not found
I should add that i2cset is available from the pi command line.
Bother - I have misled you. I am not running Debian (that is my main HA installation) I am running Raspberry Pi OS (aka Raspbian.)
ok. Try 0.12b.
Sorry about misleading you on the OS version. Brain failure.
I’ve installed 0.12b (and rebooted) and get the same error in the log.
My log is
[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.
Current Temperature 52 °C
Quiet Level 2 - Fan 1% (Low)
/run.sh: line 92: i2cset: command not found
Current Temperature 50 °C
Level 1 - Fan 0% (OFF)
/run.sh: line 83: i2cset: command not found
Current Temperature 51 °C
Quiet Level 2 - Fan 1% (Low)
/run.sh: line 92: i2cset: command not found
Current Temperature 50 °C
/run.sh: line 83: i2cset: command not found
Level 1 - Fan 0% (OFF)
Current Temperature 50 °C
Current Temperature 51 °C
Quiet Level 2 - Fan 1% (Low)
/run.sh: line 92: i2cset: command not found
Current Temperature 50 °C
Level 1 - Fan 0% (OFF)
/run.sh: line 83: i2cset: command not found
My config is
CorF: C
LowRange: 50
MediumRange: 60
HighRange: 70
QuietProfile: true