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

set the correct URL for the next autodiscovery image #164

Merged
merged 7 commits into from
Oct 27, 2023

Conversation

benklop
Copy link
Contributor

@benklop benklop commented Oct 27, 2023

Summary

The path to the 'next' version of the rtl_433_mqtt_autodiscovery add-on is incorrect, and so when trying to install home assistant actually installs a copy of the main / release version instead. The path should contain 'next-' from what I can tell based on the container names.

Alternatives Considered

I've created my own copy of the repo to work on another feature, and discovered this in the meantime. I can use my own copy of the image there only by making this change.

Testing Steps

  1. forked the repo
  2. changed all the paths / actions / repo names to point to my copies of these things
  3. disabled building of the non-next versions of the images
  4. Built the images
  5. was not able to install (home assistant gave an error about the image not being available)
  6. Applied this fix
  7. was able to install

@catduckgnaf
Copy link

@benklop I have dont have as much interest in developing the add-on and I want to focus on the integration. I have done some work previously, and am hosting a repo mostly dedicated to just the script. Lets chat over discord, (and if anyone else is interested. Per RTL_433 the goal of the project is to produce raw output, things like Intergrations are merely suggestions to build on. Let me know if we can connect, https://discord.gg/FFdJMPeP

@deviantintegral
Copy link
Collaborator

Wow, nice digging! I double checked as well against the Actions logs and this should be good. Thank you!

@deviantintegral deviantintegral changed the base branch from main to next October 27, 2023 13:01
@deviantintegral
Copy link
Collaborator

I think for this to actually be fixed we'll have to roll a release, or at least merge to the main branch.

@deviantintegral
Copy link
Collaborator

Looks like this is going to fail until #165 is fixed.

@deviantintegral deviantintegral merged commit 5ac648c into pbkhrv:next Oct 27, 2023
20 checks passed
@deviantintegral
Copy link
Collaborator

Thanks!

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

Successfully merging this pull request may close these issues.

None yet

3 participants