Other way to automatically signal for custom-cards updates than HACS?

right now I am periodically running over my resource list to check if any of the cards has been updated. Of course, next to following several topics here, where some of the authors post their updates.

I was wondering if I can somehow create a template sensor, and use that in an automation, to automate the process of signaling an available update, just like we can do with hassio versions.

I don’t use HACS, and because of the many issues I read about that, am not tempted yet to do so.

If anyone of you has found a way to find the updates I’d be appreciative to learn how. Maybe via the GitHub notification (starring) ? or a scrape of the webpage…

Hope there is a way, thanks for having a look!

I’m not sure where you are reading about “many issues” but I’ve been using HACS pretty much since it was released and I’ve almost never had any issues with it.

It’s pretty much the easiest way out there for not only initial installation of custom integrations/lovelace plugins/appdaemon apps/etc but it makes keeping up with changes dirt simple.

And you can create a sensor that will list any pending updates so you don’t have to keep checking HACS for update notification updates. But even that is easy since they are always right at the top of the list in a different color than the rest of your installed stuff.

1 Like

Check a few cards and check if they have actually updated. I am finding that HACS keeps pulling old versions instead of the right updated one. I am now in the habit of running winmerge on the old/new download to make sure they are different (ie updated). I find I need to restart HA and then reinstall. Also seen reports of integrations similarly not updating. There is an open issue.

I just went thru my list of installed items and they all seem to be up to date. That is if I can believe the “green” icon indicator and the “installed version (available version)” indication to the right side of each item.

I have had a couple times when I noticed it didn’t update to the newest version after I clicked to update. But I noticed it right away because it stayed with the yellow icon and it was still in the “update available section”.

usually a restart or an update of HACS itself fixed it tho.

Those were included in the “almost never” part of the post. :wink:

It’s still the way easiest method to install/update custom stuff, IMHO.

You can’t believe it.

OK, then I’ll have to dig a bit deeper…

I agree… but like I said, even though visually it looks updated, only way to be sure is to compare the current code with previous code. As I backup on my HD I can do this pretty easily.

When HACS first came out and there was stuff not in there I wrote some Template sensors… it was a bit kludgey but maybe I can find it for you is you are interested… but despite the HACS ‘issues’ I would recommend using it…

mini-media card today did it; button-card, custom-header does it… even my BOM weather card does it… Pretty much everything I check isn’t updating. (Integrations seem ok as does themes & appdaemon. It’s just plugins.)

I only discovered this over the weekend - working out where i’m running the old version is going to be fun!

1 Like

Just download raw file into a text file and use winmerge on the HA version you have installed…

The issue in HACS i see is that you have to select the newest version before the update.

It had the version with (latest) selected…

Please do :wink: I’d be most interested.

to the issue of not using HACS: I have tried it, in several of its iterations, some while ago I must confess. After that, I decided to not use it (didn’t like the way it interfered with system settings and imposed file locations also), but mainly because it seems to cause serious system performance issues on this side.

I have a small list of custom components that would be nice to use, since they offer functionality I really appreciate, but add to the issues with system issues (timing, endless unidentified errors in the logs,) which the HUE setup never fails to uncover.

HACS is on that list, as is Breaking Changes, and Authenticated to name a few. The native Websocket integration or the sensor based on that, for the connected clients, are/where sensitive also, but not sure exactly which was causing the experienced issues .

Added to that, most of these are simply try and restart CC’s, but HACS takes a bit more than that, and really roots into the system. Not so easy to turn-on/off.

So, long story short: Id love t try your templates @DavidFW1960 :wink:

1 Like

I’ll see if I can dig them out for you tomorrow when at the computer.
I use authenticated as well. No issues for me…

cool, no hurries.

Fyi, Ive tried this for starters:

  - platform: github
    access_token: !secret github_token
      - path: 'home-assistant/home-assistant'
      - path: 'maykar/custom-header'
      - path: custom-cards/button-card

which creates sensors for custom-header and button card:

so that’s something to go on. Unfortunately no last_changed in the repo, but a latest_release_url attribute. the sensor could trigger an automation based on that probably.

we’ll see…
adding the following card errors out though:

GitHub error for custom-cards/config-template-card: 401 {'message': 'Bad credentials', 'documentation_url': 'https://developer.github.com/v3'}

This only happens if you revert a card. The dropdown will no-longer auto choose the most recent version.

I’ve never seen this out of date. I develop apps for hacs and it’s always spot on and detects changes. Not sure what you’re referring to.

The only way this could be wrong is if people have piss poor revisioning on their apps. In that case, I wouldn’t blame hacs.

Are there new releases for these cards? I’m looking at all 3 and they are up to the current revision for all cards.

I just checked about two-thirds of my plug-ins and they are all up to date.

button card for me had not updated, but all the others had (mini graph, custom header, bar card).

What system settings are you referring to?

I’m not aware of any except for the basic installation of HACS itself.

It does necessarily “impose” any file locations. It just puts all the files it downloads into known locations. And except for the plugins you would have to put those files in exactly the same locations any way - custom components into /custom_components/, python scripts into /python_scripts, etc.

plugins get put where they are because it’s a non-cached location so you don’t have to keep clearing your cache constantly for updates to take effect.

I’ve never seen that either.