Closed mikesalz closed 2 years ago
Make sure you have read the issue guidelines and that you filled out the entire template.
If you have an issue identical to this, do not add comments like "same here", "i have this too", instead add a :+1: reaction to the issue description. Thanks! :+1:
If it says that, then you have it already.
It can be you have set a country limitation in your HACS configuration, if that is the case remove that configuration, or leave HA running for 48h (no restarts).
@ludeeus Thank you for getting back to me. The issue absolutely was the country limitation setting in my HACS config.
I temporarily changed it to allow all and was able to install the integration. Question: If I now change it back to US, will I still be able to receive updates from this integration now that it has been installed?
Yes, once downloaded the cached data is overwritten by new which removed that key. (Same would also happen after HA has been running for 48h as that is when it fetches data for non-downloaded repositories)
System Health details
System Health
Home Assistant Community Store
GitHub API | ok -- | -- GitHub Content | ok GitHub Web | ok GitHub API Calls Remaining | 4956 Installed Version | 1.25.5 Stage | running Available Repositories | 1047 Downloaded Repositories | 6AccuWeather
can_reach_server | ok -- | -- remaining_requests | 35Home Assistant Cloud
logged_in | false -- | -- can_reach_cert_server | ok can_reach_cloud_auth | ok can_reach_cloud | okDashboards
dashboards | 6 -- | -- resources | 1 views | 11 mode | storageRecorder
oldest_recorder_run | June 3, 2022, 3:09 PM -- | -- current_recorder_run | June 8, 2022, 8:39 PM estimated_db_size | 106.80 MiB database_engine | sqlite database_version | 3.34.1Checklist
Describe the issue
When attempting to download the 'djtimca/haomnilogic' custom repository, I get the below error. I made sure to completely remove any previous versions of this integration and restart HA, but I still get this error.
Reproduction steps
Debug logs
Diagnostics dump
^ Note: Debug logs requirement was EVERYTHING from startup, but that exceeded the max size of the input field.