We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Describe the bug I can't add custom repository to HACS
To Reproduce Go to HACS -> Integrations -> 3dots -> Custom repositories -> Paste repository URL, choose category and click ADD
Expected behaviour Repository added to HACS
Desktop/Server (please complete the following information):
Additional context HACS version: Integration version: | 1.26.2 Frontend version: | 20220714083628
error: <Integration lolouk44/xiaomi_mi_scale> Repository structure for 0.2.4 is not compliant
Home Assistant 2022.8.6 Supervisor 2022.08.3 Operating System 8.4 Frontend 20220802.0 - latest
The text was updated successfully, but these errors were encountered:
Which URL are you trying to add?
Sorry, something went wrong.
a wrong URL. I was adding https://github.com/lolouk44/xiaomi_mi_scale
I was having some issue with mi scale (wasn't updating my weight) and I was looking in the wrong place.
Xiaomi Mi Scale addon just wasn't started after some update. Manually starting it fixed the issue. Thank you.
No branches or pull requests
Describe the bug
I can't add custom repository to HACS
To Reproduce
Go to HACS -> Integrations -> 3dots -> Custom repositories -> Paste repository URL, choose category and click ADD
Expected behaviour
Repository added to HACS
Desktop/Server (please complete the following information):
Additional context
HACS version:
Integration version: | 1.26.2
Frontend version: | 20220714083628
error:
<Integration lolouk44/xiaomi_mi_scale> Repository structure for 0.2.4 is not compliant
Home Assistant 2022.8.6
Supervisor 2022.08.3
Operating System 8.4
Frontend 20220802.0 - latest
The text was updated successfully, but these errors were encountered: