-
Notifications
You must be signed in to change notification settings - Fork 16
Repository exists in store (but it doesn't) #34
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
Comments
I cannot explain that. Have you tried restarting your Home Assistant instance and trying again ? |
I did actually try that. Its odd, b/c I've never had this repo added. Was really hoping to use yours as the main one is out of commission. Thanks! |
Same issue on my end as well. Definitely wasn't there prior and it isn't there now. Can't add it to HACS. Countless restarts, removal of others, addition of others, all worked - still can't add yours sadly. Never seen this bug before! |
Could you please try using this link : https://my.home-assistant.io/redirect/hacs_repository/?owner=bastgau&repository=ha-pi-hole-v6&category=Integration ? |
Getting the same errors using the custom repository in hacs as well as the above direct link. I enabled debug logging in hacs and see this line:
|
What HA version do yo use ? |
2.0.5 on my end |
HA 2025.3.1 |
On reboot, I do see these log items: Then in my {
"id": "938616079",
"new": true,
"full_name": "bastgau/ha-pi-hole-v6"
}, This repo object is the only item with the |
Don't know the reasons. I'm not an expert of HACS. And if you try to Add a device directly : Settings > Devices & Services > Add Integration > Search "Pi-hole V6 Integration" ? |
Does not appear in the integration list. I also do not see it downloaded in the |
Sorry I cannot help you. Maybe someone knows the solution. Another solution will be to download manually the files into the |
The issue is still relevant ? |
For me, yes. Still issues. I installed via local and will use this for the time being. It's working great - thank you! |
I was able to install by copying the files into custom components folder, and rebooting, then installing through normal add devices. I think, this is just a hunch, that the this custom hacs integration and the original pi-hole components share some elements and is the reason it thinks it’s already in the store. |
Nope. No component is shared between this integration et the core integration. |
I have been having the same problem with adding through HACS, I had to install manually. Once installed the integration works great. (I manually installed 1.7.0b0, about a month ago) Unfortunately I've not had the time since to dig into this but there are holidays coming up so maybe then. Just wanted to bump this as it was marked as stale and wondered if anyone else who had the same issue already found a fix? |
This issue is occurring on my instance as well, cannot add by a custom repository link in HACS nor the provided link to home-asssistant.io. |
I haven't found a solution to this problem yet. |
What HA version are you in? I faced a similar problem and updating to the latest solved it. |
Not for me. I am on the latest, and the problem continues. |
Same as @jl-678, can't get any newer.
|
hacs/integration#4246 and hacs/integration#4518 seem to be related issues in HACS. |
These tickets were closed. One appeared to be a user error problem and the other was less clear. Regardless, I am not sure if these relate. |
I don't know. On my side, I don't know how I can improve that. |
Same; Problem AFAIK is that we're in a position where the user doesn't have a work around. As a test; I forked the repository and tried adding it to HACS and received the same error. I think there's something in a configuration file or something HACS is reading that makes us unable to add this as a custom repo. |
Hey @misterjmw Yes it's a possibility. if you find the reason, please share with us the solution. |
Sorry, maybe I'm missing something... but trying to add this repo to HACS, it seems to think it's already exists. It doesnt and I can't find it in the store by name.
The text was updated successfully, but these errors were encountered: