Custom Secondary Info for Entities Card

MizterB · February 20, 2019, 1:56pm

@finity - I don’t think it makes sense to add this to other types of cards. This card relies on the format / structure of the entity card to override the secondary_info element that already exists inside of it. The same approach could potentially be used to customize other standard HA cards, but it would be a completely separate effort. Anyone can use this card as a example of how to do it!

sendorm · February 20, 2019, 2:32pm

Version 0.1.1 is visible at the custom_updater. Thank you for the quick response and solution

Romquenin · February 21, 2019, 7:12am

Hi @cameron i’m using a custom component made by @renemarc, https://github.com/renemarc/home-assistant-config/tree/master/gtfs.

Holdestmade · February 21, 2019, 9:12am

Hi, this seems to be broken with v0.88, anyone else’s not working ?

ticranou · February 21, 2019, 10:52am

Yes, seems to be a problem since the 0.88 update.
The JS library has been updated:
https://raw.githubusercontent.com/MizterB/lovelace-secondaryinfo-entity-row/master/secondaryinfo-entity-row.js

Thx a lot for the update

Holdestmade · February 21, 2019, 11:15am

Thanks, I tried that update, (still says v0.1) and still not working

Vlavonvidden · February 21, 2019, 1:16pm

Same here … 0.88 broke all my stuff, be damned watchtower !

MizterB · February 21, 2019, 1:20pm

Looking into this now…seems to be a timing issue. I am able to see secondary info populate after update events are sent to to the entities (less than a minute after loading).

MizterB · February 21, 2019, 1:40pm

Version 0.2 released. This resolves the timing issue in HA 0.88

Make sure you are using the latest card-tools 0.3 commit (from Feb 19 - deb8e3). Otherwise this card will not load correctly (red error message).

Vlavonvidden · February 21, 2019, 1:55pm

I’ve made sure to update both, but the issue remains, I get the “Custom element doesn’t exist error” …

jono · February 21, 2019, 1:56pm

Thanks, working now for me!

Vlavonvidden · February 21, 2019, 1:58pm

Did you do something else besides update both components ? I cleared the cache from my brower(s) but the issue remains.

jono · February 21, 2019, 1:59pm

I had my custom card js files in a custom location (’/local/custom_ui/secondaryinfo-entity-row.js’ instead of ‘/local/secondaryinfo-entity-row.js’), and it wouldn’t work for me with that config.

I changed it to the default and now works for me. Might be worth checking?

Vlavonvidden · February 21, 2019, 2:00pm

Thanks for your answer . Mine is already at this place (/local/secondaryinfo-entity-row.js) … strange indeed.

jono · February 21, 2019, 3:09pm

Ah, right. Yeah, strange.

Holdestmade · February 21, 2019, 3:29pm

All working again now, many thanks

Vlavonvidden · February 21, 2019, 3:43pm

With the help of the mighty chrome inspector, I’ve made sure that the plugin location is correct:

And that the correct version is loaded:

Still, the error remains:

I’m pretty sure something must be right in front of my eyes and I don’t see it.

edit:

Made sure card-tools is ok too:

finity · February 21, 2019, 8:44pm

where did you find that information?

MizterB · February 21, 2019, 9:22pm

@Vlavonvidden - card-tools needs to be at the latest commit to prevent that error. If you are still seeing it despite being on the latest code, you might be running a cached version of card-tools. Try clearing your cache, or ensuring that the code you see contains this:

  static litElement() {
    return Object.getPrototypeOf(customElements.get('home-assistant-main'));
  }

Vlavonvidden · February 22, 2019, 8:23am

That was it … I think something went wrong with the custom updater, it was showing the correct commit number but the file did not contain the line you quoted.

COpy/pasting from github solved the issue. Thanks a lot !

@finity, I found that information using chrome inspector.