Cannot install the addon from repo

[marst444]

Cannot install the addon from repo

[davidusb-geek]

If you are using an ARM architecture (RPi's), then just wait a few more seconds for the images to build.

[neil-ennis]

I try to add this repo:
https://github.com/davidusb-geek/emhass-add-on

I get this error:
https://github.com/davidusb-geek/emhass is not a valid add-on repository

Note the error message has a different URI from the repo.

It could just be me - I'm a bit of a gumby, but if I'm doing something wrong, please point me in the right direction.

[GeoDerp]

Just tried with https://github.com/davidusb-geek/emhass-add-on.git. Seems to work for me. Let us know if your still having issues.

I have noticed it can be finicky. Maybe restarting HA (or updating) and trying again may resolve some issues.

[marst444]

Running on a "homeassistant green"
Waiting out did not help.
Tried the above mentioned https instead, no luck:

2024-03-12 12:38:06.999 ERROR (MainThread) [homeassistant.components.hassio.handler] /store/repositories return code 400
2024-03-12 12:38:06.999 ERROR (MainThread) [homeassistant.components.hassio] Failed to to call /store/repositories -

Have updated to latest version and restarted.
No success.

[GeoDerp]

Running on a "homeassistant green" Waiting out did not help. Tried the above mentioned https instead, no luck:

2024-03-12 12:38:06.999 ERROR (MainThread) [homeassistant.components.hassio.handler] /store/repositories return code 400 2024-03-12 12:38:06.999 ERROR (MainThread) [homeassistant.components.hassio] Failed to to call /store/repositories -

Have updated to latest version and restarted. No success.

Thanks @marst444 , the error Failed to to call /store/repositories - is interesting.
Is it possible you could get to the terminal and run ping github.com ? could be a time or DNS issue.

[GeoDerp]

Could you also run uname -a (to check architecture and kernel version, should be aarch64). the ssh addon should allow you to do both commands.

[davidusb-geek]

Actually I just realized now that the images for ARM build failed!

This is intriguing because the build for docker testing passed correctly here on the emhass core tests:

[GeoDerp]

Actually I just realized now that the images for ARM build failed!

This is intriguing because the build for docker testing passed correctly here on the emhass core tests:

Interesting. Ill have a look at the workflow and see if I can find anything. I wonder if its a publish issue and not a build issue.

[davidusb-geek]

Oh boy with more than 5k of lines that's some logging there.
But it seems that for example Publish-armv7 is trying to pull the ghcr.io/home-assistant/amd64-builder:latest image to build this. Probably the cause of the late failure when building?

I wonder if its a publish issue and not a build issue.

Definitely blocked on build

[GeoDerp]

Oh boy with more than 5k of lines that's some logging there. But it seems that for example Publish-armv7 is trying to pull the ghcr.io/home-assistant/amd64-builder:latest image to build this. Probably the cause of the late failure when building?

Probably. im sure its the smallest issue. I think I might know what it is. I like how 0.8.2 worked without and issue as well ahaha

Im wondering if its another piwheel timeout issue.

[GeoDerp]

The arm builds should take like 15m not 4hrs. So its almost like piwheel wasn't running propperly. Re running the action again could be enough to fix that. Might be good to put in a measure to make sure piwheels is running correctly.

[davidusb-geek]

Ok re-running...

[marst444]

github ping.pdf

[GeoDerp]

its also having a lot of setuptools issues. maybe a pip install or apt-get may help. but why would it only brake once?

[GeoDerp]

github ping.pdf

thanks @marst444, my version seems to be different from yours. Mine being 6.1.73-haos-raspi. Since your running arch64 it should be good to go, you can also ping github fine I see. So i'm wondering if there is a difference with haos-raspi and haos. This may require some time to look into. (if time or a patch doesn't resolve issues)

[GeoDerp]

Meanwhile the action worked. @davidusb-geek 🤦
My guess, a pi wheel timeout issue.
@marst444 , you could give it a bit and try again and see if the new Docker image fixes the problem.

@davidusb-geek maybe there is a way to throw an error or retry, on pip install if it cant talk to piwheels. We can also set fail-fast: true. and so the whole publish action fails if one arch fails.

[davidusb-geek]

Yes it worked now.
Yes that parameter can be a nice option to not wait 4hrs because of a timeout problem

[GeoDerp]

We could also add packages like setup tools in so if it needs to compile the packages it can without error.

[marst444]

Still no go for me though. Trying both suggested https:
https://github.com/davidusb-geek/emhass-add-on
https://github.com/davidusb-geek/emhass-add-on.git

2024-03-12 19:50:28.598 ERROR (MainThread) [homeassistant.components.hassio.handler] /store/repositories return code 400
2024-03-12 19:50:28.598 ERROR (MainThread) [homeassistant.components.hassio] Failed to to call /store/repositories -
2024-03-12 19:50:37.436 ERROR (MainThread) [homeassistant.components.hassio.handler] /store/repositories return code 400

2024-03-12 19:50:37.437 ERROR (MainThread) [homeassistant.components.hassio] Failed to to call /store/repositories -

[davidusb-geek]

Well that seems like a problem with your HA instance. Are you able to add any other repository at all?

[marst444]

Yes I can. And also add addons from repo. But cannot add the "https://github.com/davidusb-geek/emhass-add-on"
Errors as above....

[marst444]

But now it showed up! This time i only had to wait it out a little longer it seems :) Will try to install now! :)

[marst444]

Yes. Now its installed. Just the configure part to get it up and running i guess :) Thanx for your help!

[davidusb-geek]

Glad to hear. Closing then.