LordMike/MBW.BlueRiiot2MQTT

Failed to install addon

gitprova0 opened this issue · 27 comments

Try installing the repository from the add-on store, after updating to "core-2021.1.4" and "supervisor-2021.01.4" I receive this error:

404 Client Error for http+docker://localhost/v1.41/images/create?tag=0.9.2&fromImage=lordmike%2Fblueriiot2mqtt: Not Found ("manifest for lordmike/blueriiot2mqtt:0.9.2 not found: manifest unknown: manifest unknown")

I'm not sure where you get 0.9.2 from.. The hass-addons repo says v0.9.2 .. so you should be getting that.

I've just checked, and tag v0.9.2 does exist.. :|

Hi,

I am also getting an error (previously working install) when trying to start.

Failed to start addon 404 Client Error for http+docker://localhost/v1.40/containers/create?name=addon_dff6e9be_blueriiot2mqtt: Not Found ("No such image: lordmike/blueriiot2mqtt:0.9.2")

Yeah me too. I restored back to over a week ago when it was working and its still the same error :/

Is it possible to get some details from the HASS store about what is about to be installed?

.. Anywhere the version / tag can be shown?

  • Hub.docker.com shows the v0.9.2, which is shown to be last pulled 3h-1month ago.. I'm only using amd64, so others must be using the arm versions
  • The hass-addons config file specifies v0.9.2 ... could it be possible HASS changed something that would strip the v ?

I don't run HASSIO myself, so I can't immediately test it :|

If this goes on much longer, I'll just push to 0.9.2 as well -.-'

I get the same error and it shows 0.9.2

I've pushed a 0.9.2 tag. It should work out now :|

I'm still at a loss as to why.

blue
Sorry no luck :(

Now I'm able to install it but still have problem running it:
404 Client Error for http+docker://localhost/v1.41/containers/create?name=addon_e141bb7c_blueriiot2mqtt: Not Found ("No such image: lordmike/blueriiot2mqtt:0.9.2")

lordmike/blueriiot2mqtt:0.9.2 does exist now. Are you sure that f.ex. network isn't an issue?

So I managed to install hassio myself in a VM, and I'm getting the same issue as you .. On start, it reports that issue. On the internet, some people are saying this could be a disk freespace issue, which it wasn't for me. To test, I opened the CLI on the system, logged on as root, and ran docker run --rm lordmike/blueriiot2mqtt:v0.9.2 - which ran. So docker works.

I next tried ha addons start dff6e9be_blueriiot2mqtt, which seems to have worked.. I do not know why.

Now I can stop, and start the addon in the UI - with no issue. I can even reinstall it, and start it again..

I'm at a loss :|

image

In the logs above, the errors are when I tried it first from the UI. Then later, I started it using the console, after which the UI works.

  • This page has the same sudden 404's on things that use to work - referencing the supervisor / docker issue below, and also touches on DNS issues.
  • This page reports on the disk issues, and potential corruptions in the install
  • This page reports incompatibilities of docker 20.10 with the supervisor version HASS runs.

IMG_20210119_192130
I get this error when trying to run "docker run --rm lordmike/blueriiot2mqtt:v0.9.2"

That's expected (as it's not configured). This proves the image was downloaded and can run..

Try ha addons start dff6e9be_blueriiot2mqtt .. the value there should be in your browsers address bar, when you visit the add-ons page for BlueRiiot2MQTT. I think it will be the same.

Hi,
I tried some things, but still can't get it working. I don't have the 'v' anymore, which should be right? Any Idea's? The e141bb7c_blueriiot2mqtt is what is in my address bar, in the addon store.
image

It states this on installation:
image

Then after you start it, and it fails it changes to:

image

Just some info..

It's totally weird they would remove the v - but I'm quite certain they still reference the correct image.

As I found earlier, this is likely an issue with HASSIO, where something broke.

You could try to find out which versions you're running:

  • Docker, if it's 20.10 - it might be failing with incompatibility with supervisord

This post mentions how to downgrade docker, to 19.03. Which might fix stuff.. Note that I don't take any responsibility for anything that may come of this.

I found that Hass has an alerts page, which at some point listed this incompatibility. The alert is gone, and I now found why: home-assistant/alerts.home-assistant.io#256. They mentioned that Docker 20.10.1 and Supervisor 2020.12.7 fixed the issue.

You could therefore also try updating to get the newer versions.

Here is the original alert from HASS.

This is my configuration:
Capture
and this is the CLI output (e141bb7c_blueriiot2mqtt):
IMG_20210120_153755

Same problem for me :(

Would it be possible for one or more of you to open a thread on the Hassio forums?

I'm quite certain the issue isn't with this project.

Hi,
I have the exact same problem as mentionned earlier, not I can install the add-on. I even remove and re-added the add-on repository to start from scratch.
Note that I do not have the same problem with other custom repos for other add-ons.

Could it be that there is now a discrepancy between the version naming v0.9.2 and 0.9.2 for the reference in the add-on config.json here ?:
https://github.com/LordMike/hass-addons/blob/02739c0e8ce501b1caad9c438e0a812db5b7385e/blueriiot2mqtt/config.json#L3

Would that line not have to be "version": "0.9.2", instead of "version": "v0.9.2", ?

When simply listing the add-ons with ha addons i get this:
image

I can try changing that to 0.9.2. In reality, I was surprised to find that the version was expected to also be the tag of a docker image. So I went with the "v" prefix to indicate versions.

I've changed it to 0.9.2 .. so you could try that. If it works, I'll just rename future versions to a non-prefixed kind.

Great !! That did the trick. It works fine.
I deinstalled and deleted the repository. Restarted the core, and re-added the repository and installed.
Re-pasted my config data, and started no problem. All is published on MQTT as expected !

Thanks!

Fine. I'll mark new versions without a prefix..

Wow that's stupid.

@youngy00 @colesealeaf @gitprova0 @Nicklas86 could you try again ? I've removed the prefix which should resolve the issue

I've also pushed version 0.10.0 - which includes a new command to do wifi readings.

@youngy00 @colesealeaf @gitprova0 @Nicklas86 could you try again ? I've removed the prefix which should resolve the issue

I've also pushed version 0.10.0 - which includes a new command to do wifi readings.

It works for me now! I will do the config later :) Thanx