integration: Can't update HACS 0.24.4
I can’t update HACS on my HASS
Getting this error:
this is the log on HASS: `Logger: hacs Source: deps/lib/python3.8/site-packages/integrationhelper/logger.py:25 First occurred: 0:04:20 (3 occurrences) Last logged: 23:52:37
Could not use repository with ID 172733314`
About this issue
- Original URL
- State: closed
- Created 4 years ago
- Comments: 34 (9 by maintainers)
Can I log a ‘me too’?
Every time HACS wants to update itself I just end up with a big red bar saying
An error occurred while processing Could not use repository with ID 172733314
Or such. So I go and remove HACS. I oh so carefully step through the instructions getting a lovely shiny new git hub token, which of course I don’t need then as I have just done a whole new unzipped custom_components/hacs folder. So there I am thinking "this time I am sure I read every word, dotted every i and crossed every t. It must work this time and shortly after it smoothly updates one or more of my integrations and my confidence rises. However, after a week or so, they push some more changes, HACS wants to update, I click the UPDATE and we’re back to the big red bar.
The log just says 2020-05-09 13:11:59 ERROR (MainThread) [hacs] Could not use repository with ID 172733314
I have a git account. I have a lot of C++ stashed there but I’m a poor old retired embedded systems programmer and python reads funny to my senile old brain. Is there some way to determine what I’m doing wrong? It’s a nice system running on a Pi3 in simple vend mode that looks after my lights and plugs.
Yes, I have removed all the previous tokens and I checked the token I feed into the install is right. I did try the yaml configuration option but that was the same.
Change permission on hacs folder and upgrade to version 1.0.0. Upgrading works now!
I’ll give it a shot. I don’t know if I can contribute any code though.
Glad that helped some people. A couple thoughts:
I think it’s common to have a user account for normal system interaction, and a separate one for running HA.
I also think that the HACS error message was not particularly helpful.
A few ideas:
Have the code that does the downloading/extraction check for correct permissions, and throw a (descriptive) error if they’re wrong.
Have a generic permission check somewhere in HACS. Maybe this issue could be detected during installation. Or maybe the same code that checks during installation can be called again to check before any downloading/extracting happens.
Add a note to the installation directions to make sure the necessary directories are writable by the user running HA.
Just throwing that out there.
My owner was the basic pi:pi account as I was unpacking the hacs.zip on the PC and moving it over via samba. Using sudo chown -R homeassistant …hacs and then chgrp the same seems to have done it as it just did a reinstall OK. I shall await the next push of updates with trepidation. So it was, basically, my unfamiliarity it linux? I rather expected that.
Thanks for your time guys.