Ok, thanks, I’ll make a seperate token, I guess I could hit rate limits otherwise. 
It will count towards the same account.
By using multiple tokens, you can revoke one and only the system using that token will stop, not all.
I added a condition to my automation, because after a restart I always get a wrong “update available”-notification.
With this - hopefully - this issue should be gone.
add this condition:
condition:
- condition: numeric_state
entity_id: sensor.uptime
above: 0.2
and add this to your sensor.yaml:
- platform: uptime
unit_of_measurement: hours
Probably better to use a template condition to see if the state is None/Unknown
1 Like
yes thats better!
condition:
- condition: template
value_template: "{{ not is_state('sensor.hacs', 'none') }}"
- condition: template
value_template: "{{ not is_state('sensor.hacs', 'unknown') }}"
2 Likes
The first one will never be valid "none".
But the second one should be a good condition for this.
2 Likes
@h4nc Thanks for the Automation, it worked great this morning for me. I have not seen the false positive states you mentioned but I am going to try adding the condition.
@ludeeus the new update went really smooth! I got two more of my plugins moved from the legacy installation model to HACS! I am only missing a couple plugins that I use regularly, hopefully the Devs will add their work to HACS.
1 Like
Are there any plans to embed HACS in core home assistant?
1 Like
Currently no.
Was getting the exact same problem.
running docker version of HA (currently on v0.93.x - need some time to updgrade to v0.94/5 because of the potential impact of device tracker changes).
Restarting from the configuration panel… after actually fully restarting the container it worked.
Hi
Thanks for this component! It’s really fantastic.
I’ve installed few hours ago on an Intel Nuc i3 and I still have the message “Background task running, refresh the page in a little while.”.
Is it normal?
I also have an issue that I’ve reported n the Gauge card thread, because installing from HACS does not work, while installing manually with the old method it works.
The “background tasks…” thing is normal after a restart of Hass as it reloads all the components and discovers what you have installed. Also be aware that not all CCs will work with HACS as their GitHub repository must be in the correct format. (not sure exactly what that is, but I’m sure someone else can explain if needed)
2 Likes
Got this installed and loving it so far.
Question about its intended usage:
For Lovelace cards that aren’t included by default, is the desired thing to do to copy the repo address and manually add it via settings?
I’ve tried this and it seems to work for some repos (gives error on some). Just wanted to ensure this was the intended workflow.
yes, that’s correct.
yes, that’s normal because of this…
see here for the requirements for plugins:
https://custom-components.github.io/hacs/developer/plugin/
and here for integrations:
https://custom-components.github.io/hacs/developer/integration/
Hi, i just downloaded and tried to install HACS, but i have a couple of doubts.
First of all you write if i am using custom_updater i need to delete the entire directory but about custom_updater i have only one custom_updater.py file inside custom_components.
Do i need to delete only that file?
Second: i am using inside ui-lovelace.yaml this kind of entries:
resources:
- url: /customcards/custom_ui/weather-card.js
type: module
How to change it or what to do to have those entries workable with HACS?
Thanks in advance for your kind reply…
if that is true you have an old version, and yes remove that.
that is described here https://custom-components.github.io/hacs/installation/manual/#moving-from-custom_updater
Ok thanks, i read about moving from custom_updater, but for me it’s not so clear what to do…
Can you send me an example about how to modify that entry? Is this related only to plugin and for hass-io? I am using hassbian.
Use the editor of your choice.
Yes.
Home Assistant is Home Assistant, it does not matter how you installed it.