gadgetchnnel / lovelace-home-feed-card

A custom Lovelace card for displaying a combination of persistent notifications, calendar events, and entities in the style of a feed.
275 stars 24 forks source link

Display broke on latest core-2021.6.0b0 #70

Closed bschatzow closed 3 years ago

bschatzow commented 3 years ago

With the home-feed-card my display is blank. No changes in any of my configuration. I can see my display loading and then it goes to a blank screen. Tried the latest chrome as well as edge. The same on three different computers as well as phone and tablets.

my card code is:

type: "custom:home-feed-card"
calendars:
  - 
    calendar.bschatzow_gmail_com
id_filter: ^home_feed_.*
more_info_on_tap: true
entities:

  - 
    content_template: '{{display_name}} arrived at {{state}} ({{latitude}},{{longitude}})'
    entity: device_tracker.bill_pixel_gps
    name: Bill
    include_history: true
    keep_latest: true
  - 
    entity: cover.west
    include_history: true
    keep_latest: true
    remove_repeats: true
  - 
    entity: cover.middle
    exclude_states: 'off'
    include_history: true
    keep_latest: true
title: Activity

Loading any of these fail on my test lovelace display.

gadgetchnnel commented 3 years ago

I've published a new beta of this, 0.6.0b1, which uses an embedded lit-element to avoid this issue. Can you please give that a go and let me know if it works for you?

bschatzow commented 3 years ago

Tried it. No difference.

gadgetchnnel commented 3 years ago

I was able to reproduce your issue in version 0.5.0 of the card but not in the 0.6.0b1 beta version. Are you definitely on the beta version? Maybe try clearing the browser cache, in case the old version is hanging around.

bschatzow commented 3 years ago

It is working now. I was on .5 but had a HA update on the beta. Not sure if this is what fixed it or your code. I thought I cleared the cache, but maybe not.

verstrepeng commented 3 years ago

I had the same issue after upgrade to latest Home Assistant. Upgrade of home-feed-card to beta 0.6.0b1 and cache clear solved it.

gadgetchnnel commented 3 years ago

Closing as I have now promoted 0.6.0 containing this fix from beta to release.