Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

I2C installed but Argon device is missing #49

Open
YanisKyr opened this issue Mar 7, 2023 · 17 comments
Open

I2C installed but Argon device is missing #49

YanisKyr opened this issue Mar 7, 2023 · 17 comments

Comments

@YanisKyr
Copy link

YanisKyr commented Mar 7, 2023

This worked alright for me for a week or so but now it stops a few seconds after it starts. See below for what’s showing in the logs.

Any help to get it back on track would be much appreciated.

[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] 00-banner.sh: executing... 
-----------------------------------------------------------
 Add-on: ArgonOne Active Linear Cooling
 Actively keeping your Argon One cool.
-----------------------------------------------------------
 Add-on version: 29c
 You are running the latest version of this add-on.
 System: Home Assistant OS 9.5  (aarch64 / raspberrypi4-64)
 Home Assistant Core: 2023.2.5
 Home Assistant Supervisor: 2023.01.1
-----------------------------------------------------------
 Please, share the above information when looking for help
 or support in, e.g., GitHub, forums or the Discord chat.
-----------------------------------------------------------
[cont-init.d] 00-banner.sh: exited 0.
[cont-init.d] 01-log-level.sh: executing... 
[cont-init.d] 01-log-level.sh: exited 0.
[cont-init.d] done.
[services.d] starting services
[services.d] done.
Detecting Layout of i2c, we expect to see "1a" here.
checking i2c port 0 at /dev/i2c-0
     0  1  2  3  4  5  6  7  8  9  a  b  c  d  e  f
00:                         -- -- -- -- -- -- -- -- 
10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
70: -- -- -- -- -- -- -- --                         
not found on /dev/i2c-0
checking i2c port 1 at /dev/i2c-1
     0  1  2  3  4  5  6  7  8  9  a  b  c  d  e  f
00:                         -- -- -- -- -- -- -- -- 
10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
70: -- -- -- -- -- -- -- --                         
not found on /dev/i2c-1
checking i2c port 10 at /dev/i2c-10
     0  1  2  3  4  5  6  7  8  9  a  b  c  d  e  f
00:                         -- -- -- -- -- -- -- -- 
10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
70: -- -- -- -- -- -- -- --                         
not found on /dev/i2c-10
checking i2c port 22 at /dev/i2c-22
     0  1  2  3  4  5  6  7  8  9  a  b  c  d  e  f
00:                         -- -- -- -- -- -- -- -- 
10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
/run.sh: line 111: thePort: unbound variable
30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
70: -- -- -- -- -- -- -- --                         
not found on /dev/i2c-22
[cmd] /run.sh exited 1
[cont-finish.d] executing container finish scripts...
[cont-finish.d] 99-message.sh: executing... 
-----------------------------------------------------------
                Oops! Something went wrong.

 We are so sorry, but something went terribly wrong when
 starting or running this add-on.
 
 Be sure to check the log above, line by line, for hints.
-----------------------------------------------------------
[cont-finish.d] 99-message.sh: exited 0.
[cont-finish.d] done.
[s6-finish] waiting for services.
[s6-finish] sending all processes the TERM signal.
@javierpal
Copy link

javierpal commented Mar 7, 2023

same here, worked like 1 month and then the next error show up.

[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] 00-banner.sh: executing... 
-----------------------------------------------------------
 Add-on: ArgonOne Active Linear Cooling
 Actively keeping your Argon One cool.
-----------------------------------------------------------
 Add-on version: 29c
 You are running the latest version of this add-on.
 System: Home Assistant OS 9.5  (aarch64 / raspberrypi4-64)
 Home Assistant Core: 2023.3.1
 Home Assistant Supervisor: 2023.03.1
-----------------------------------------------------------
 Please, share the above information when looking for help
 or support in, e.g., GitHub, forums or the Discord chat.
-----------------------------------------------------------
[cont-init.d] 00-banner.sh: exited 0.
[cont-init.d] 01-log-level.sh: executing... 
[cont-init.d] 01-log-level.sh: exited 0.
[cont-init.d] done.
[services.d] starting services
[services.d] done.
Detecting Layout of i2c, we expect to see "1a" here.
checking i2c port 0 at /dev/i2c-0
     0  1  2  3  4  5  6  7  8  9  a  b  c  d  e  f
00:                         -- -- -- -- -- -- -- -- 
10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
70: -- -- -- -- -- -- -- --                         
not found on /dev/i2c-0
checking i2c port 1 at /dev/i2c-1
     0  1  2  3  4  5  6  7  8  9  a  b  c  d  e  f
00:                         -- -- -- -- -- -- -- -- 
10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
70: -- -- -- -- -- -- -- --                         
not found on /dev/i2c-1
checking i2c port 10 at /dev/i2c-10
     0  1  2  3  4  5  6  7  8  9  a  b  c  d  e  f
00:                         -- -- -- -- -- -- -- -- 
10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
70: -- -- -- -- -- -- -- --                         
not found on /dev/i2c-10
checking i2c port 22 at /dev/i2c-22
     0  1  2  3  4  5  6  7  8  9  a  b  c  d  e  f
00:                         -- -- -- -- -- -- -- -- 
10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
70: -- -- -- -- -- -- -- --                         
not found on /dev/i2c-22
/run.sh: line 111: thePort: unbound variable
[cmd] /run.sh exited 1
[cont-finish.d] executing container finish scripts...
[cont-finish.d] 99-message.sh: executing... 
-----------------------------------------------------------
                Oops! Something went wrong.

 We are so sorry, but something went terribly wrong when
 starting or running this add-on.
 
 Be sure to check the log above, line by line, for hints.
-----------------------------------------------------------
[cont-finish.d] 99-message.sh: exited 0.
[cont-finish.d] done.
[s6-finish] waiting for services.
[s6-finish] sending all processes the TERM signal.

@javierpal
Copy link

any updates?

@adamoutler
Copy link
Owner

Looks like hardware failure. You should try the Argon One official script and see if it works. If not, contact Argon Support. If it does work then I have no ideas. You should be seeing 1a. There is no 1a. The hardware i2c appears to be disconnected.

@YanisKyr
Copy link
Author

Is it possible to try the official script while Home Assistant is running on the same system?

@adamoutler
Copy link
Owner

Yes. Just insert a different sdcard

@javierpal
Copy link

weird that this error show up to both of us at almost the same time, don't you think?

@adamoutler
Copy link
Owner

Its been happening a lot lately. It's not something I can address with software. You have i2c port, and you have a device connected to the i2c port or you don't. In this case you have a port and no device connected. You should see a 1a or 1b there.

@javierpal
Copy link

Its been happening a lot lately. It's not something I can address with software. You have i2c port, and you have a device connected to the i2c port or you don't. In this case you have a port and no device connected. You should see a 1a or 1b there.

maybe a design flaw in the raspberry PI hardware?

@adamoutler
Copy link
Owner

adamoutler commented Mar 14, 2023

Probably Argon hardware. The Pi is a chip and a wire that goes to the chip. If it breaks your i2c port would probably be gone. The Argon is an additional system attached to it. That's why you should contact them.

@adamoutler
Copy link
Owner

I've never heard back on this issue, although this is like the 10th time. Please report back whatever you find. It would be nice to know if it's something disconnected, EEPROM setting, or something like the wrong power supply... I'd like to know so I don't keep getting these drawn out threads here and on the forums.

@YanisKyr
Copy link
Author

My Argon's internal fan has stopped running since a couple of days actually. Not sure if it's broken completely though as the addon is still giving me the error and therefore not managing it.

The ultimate goal was to have the fan start above 45C while keeping it cool inside a cupboard with a couple of Noctuas.

That said, if I find the time, I will investigate further and keep you posted.

@unCleanCode
Copy link

Having the same problem. Appeared just recently, I believe after OS update

@adamoutler
Copy link
Owner

What do the logs say?

@Lapias
Copy link

Lapias commented Jul 6, 2023

Add-on version: 29c
You are running the latest version of this add-on.
System: Home Assistant OS 10.3 (aarch64 / raspberrypi4-64)
Home Assistant Core: 2023.7.0
Home Assistant Supervisor: 2023.07.1

Hi, I faced a similar issue after a kernel update. Restoring and reinstalling repositories and programs did not help.

But the following worked for me:
I connected the ssd m.2 to my computer via usb, then found the configuration file, and uncommented all the lines containing 'i2c'.
After that the problem disappeared!

Привет, я столкнулся с аналогичной проблемой после обновления ядра. Восстановление, и переустановка репозиториев и программ не помогли.

Но мне помогло следующее:
Я подключил ssd m.2 к своему компьютеру через usb, после нашёл файл конфигурации, и разкомментировал все строки содержащие в себе "i2c".
После этого проблема исчезла!

@mxr
Copy link
Contributor

mxr commented Nov 26, 2023

I have dealt with the same issue (sudden regression after an unknown update). I managed to resolve it through some combination of

  • re-flash HA to the SD card, restore from backup while not using the Argon case
  • enable I2C by modifying the SD card
  • reboot many times

@javierpal
Copy link

javierpal commented Dec 3, 2023

Recently I lost electricity on my building, I had to power off my raspberry pi, and keep it without power for at least 2 hours, what happened? well, the addon started working fine after home assistant booted up, and as you can see, I had the problem for a looong time, so then, it seems that maybe is not a hardware problem as @adamoutler said, maybe is a software problem, the fan didn't stopped working in all this time, just the software implementation.

image
image
image

@adamoutler
Copy link
Owner

The biggest problem I've had is people installing the wrong version from somebody else and expecting support from me. It's really easy

  1. Argon One
  2. HAOS
  3. Enable i2c
  4. Start this addon.
    Nothing follows

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

6 participants