Custom_updater and tracker-card not reporting correctly

Configuration
81

It won’t work until 0.88.0 is released according to Ludeeus…

82

Looks like its working now…its reporting a new version 4.0.3 versus my current 4.0.1.

83

It won’t work until 0.88.0 is released according to Ludeeus…

That is for the buttons, and platforms that have moved to the new embedded structure.

For showing the custom_updater “in itself” I wanted to wait until I got finished with this GitHub - custom-components/custom_updater: [DEPRECATED]📦 A component which allows you to track and update custom cards/components and python_scripts

Note to anyone having issues with it, open an issue at the repo if you want me to look into it, posts here fly by to fast for me to keep up

84

Am i forced to use mode: storage also if i use yaml mode in configuration?

85

No, I am using mode: yaml and everything is fine.

86

Sorry… you use mode: yaml in configuration.yaml regarding custom_updater in place of mode: storage?
If i use mode: yaml in configuration.yaml can i use mode: storage regarding custom_updater… i am confused.

87

You don’t have to use mode: storage in custom updater if you are using yaml mode for the configuration.
Here is my config for reference:

custom_updater:
  show_installable: False
  track:
    - cards
    - components
  card_urls: 
    - blabla
  component_urls:
    - blabla

lovelace:
  mode: yaml

You only need to specify custom_updater mode: storage if you are using the storage mode for configuration.

88

Ok, now it’s clear… thanks…

89

Just only one more doubt… If i don’t use mode: storage i must always cut off the tag release of the cards?

90

i just installed this and only devicetracker.life360 and custom_updater show up, my alexa media player component does not and none of my cards show up… do they ahve to be in a custom_cards folder? right now they are in /local/lovelace/

91

That isn’t an actual folder. The actual folder is /www/lovelace no?
/local/ and /customcards/ are just end points.
You need to change to /customcards/ in the lovelace file and remove versions. In the custom_updater config you need to specify mode: storage or yaml then your cards should show up.

yaml or storage and new custom_updater don’t need the version

92

so I installed this card afresh, along with the latest component on HA 0.87.1.

59

seems to do alright, apart from the 2 buttons Check and Update All and all the custom cards having an incorrect version number…

Im not using mode: yaml, since that was causing an error, and seems to be default? Lovelace mode is yaml.

what am I doing wrong here?
this is my file:

# https://github.com/custom-components/custom_updater/wiki/Installation

track:
  - components
  - cards
  - python_scripts

component_urls:
  - https://raw.githubusercontent.com/robmarkcole/Hue-sensors-HASS/master/custom_updater.json
  - https://raw.githubusercontent.com/pnbruckner/homeassistant-config/master/custom_components.json
  - https://raw.githubusercontent.com/xirixiz/home-assistant-config/master/custom_updater.json

card_urls:
  - https://raw.githubusercontent.com/kalkih/mini-media-player/master/tracker.json
  - https://raw.githubusercontent.com/kuuji/button-card/0.0.2/tracker.json
  - https://raw.githubusercontent.com/matisaul/vertical-style-card/master/tracker.json
  - https://raw.githubusercontent.com/kalkih/mini-media-player/master/tracker.json
  - https://raw.githubusercontent.com/kalkih/mini-graph-card/master/tracker.json
  - https://raw.githubusercontent.com/gurbyz/custom-cards-lovelace/master/custom_updater.json
  - https://raw.githubusercontent.com/ljmerza/waze-card/master/updater.json
  - https://raw.githubusercontent.com/sgttrs/lovelace-weather-card-chart/master/custom-updater.json

python_script_urls:
  - https://raw.githubusercontent.com/pnbruckner/homeassistant-config/master/python_scripts.json

show_installable: false

and my resources below, my true files are in /config/www/lovelace/resources/ so that translates to /customcards/lovelace/resources/ for the card?:

resources: #!include /config/lovelace/resources/resources.yaml
# https://github.com/thomasloven/lovelace-card-tools
  - url: /customcards/lovelace/resources/card-tools.js
    type: js
# Ha Cards : https://www.home-assistant.io/lovelace/gauge
# https://github.com/ciotlosm/custom-lovelace/tree/master/gauge-card
  - url: /customcards/lovelace/resources/gauge-card.js
    type: js
#https://github.com/custom-components/custom_updater
#https://github.com/custom-cards/tracker-card

  - url: /customcards/lovelace/resources/tracker-card.js
    type: module
# https://github.com/rodrigofragadf/lovelace-cards/tree/master/tiles-card
  - url: /customcards/lovelace/resources/tiles-card.js
    type: js
  - url: /customcards/lovelace/resources/useful-markdown-card.js
    type: js
# https://github.com/ciotlosm/custom-lovelace/tree/master/monster-card
  - url: /customcards/lovelace/resources/monster-card.js
    type: js
```

etc
etc,
93

I have the same issue with the buttons not being clickable for some reason.

94

yep, tried all possible combinations today, but only way to get my buttons back is with a version 3. of the tracker-card.
And yes, i did follow all instructions to change paths etc in combination with the custom component. Seems to cause a lot of system stress this set of features, the Hue lights are more unavailable than available again…

Also tested todays release allowing for individual updates.

Had the same results on 84.3/6 HA where I stopped upgrading the tracker card and component. Now I have one system on 87.1 thought to be safe, and upgraded them again, but no such luck. SO, HA 87.1 and tracker cards 3. again returning my buttons…;-(

11

95

I can actually see the buttons (lightly, maybe a different color would be better?)
image

One thing I have noticed today, is that after intalling a python script and it’s custom_updater conf

  python_script_urls:
    - https://raw.githubusercontent.com/pnbruckner/homeassistant-config/master/python_scripts.json

It doesn’t show up in the list (screenshot above).

Did I miss something?
The script is loaded in within HA
image

Not sure it is a bug or it is just me doing something wrong due that is the first time I am adding a python script

Thanks
Andrea

96

not sure about your setup, but in my issue, i could not only not see buttons, but nothing was clickable either.

97

Before latest version I could see the text but it was not clear it was a button and there was nothing that intended to show that was “clicked” (even tho it was working), exactly like screenshot you sent two post above.

As I said, beside the fact that didn’t show any action on click, the action was actually performed (noticed using logs in debug mode).

One thing I noticed from your screenshot is that on the first one (no button) you were using tracker-card 1.0.0 while on the second 0.1.5.

I am using 1.1.0, you might want to update to that version and check again (making sure to clean the browser cache with Dev Tools and CTRL+F5).

Hope this helps :slight_smile:

Andrea

98

The reason there is an issue with the buttons is that I have already made this card compliant with version 0.88.0 that should drop today.

99

thanks for letting us know, though that forces people to update no matter what… never a good strategy imho… some backward compatibility and warning would have been appreciated. Apparently I now have clicked the buttons and have updated all cards, while I didn’t want to because of other issues with other cards.

100

No? If you are holding off on updating HA you can hold off on updating custom elements too.

There are also options to disable certain cards for upgrading.

1 Like