Lovelace: Upcoming Media Card

Disable your adblocker when on your home assistant page

Thanks man - for some reason I overlooked that part of it. Appreciate it.

For the radarr upcoming card.
" This fix will only work if you do not use fanart view. I would be interested in knowing what movie is causing this issue as it would help me track it down. If you could share the results from a direct connection to the radarr api and the sensor’s data it would be helpful. If you’re more comfortable sending this to me via PM on the HA forums, don’t hesitate to do so."

I am using fanart and it is working properly. The only movie in the list is Legally Blonde 3. I can get the api data when I get home if needed.

Yeah, looks like that movie just doesn’t have a backdrop (fanart) image file yet. Try the other fix I put on the github issue and let me know if that works alright.

Disabling addblocker did the trick. Thanks for that and the great card.
Addblock plus and Ghostery, in fact.
But why would the pictures track as adds?

data: >-
  [{"title_default": "$title", "line1_default": "$episode", "line2_default":
  "$release", "line3_default": "$rating - $runtime", "line4_default": "$number -
  $studio", "icon": "mdi:arrow-down-bold"}, {"airdate": "2020-02-13T03:00:00Z",
  "release": "$day, $time", "flag": true, "title": "The Magicians (2015)",
  "episode": "Apocalypse? Now?!", "number": "S05E05", "runtime": 45, "studio":
  "Syfy", "rating": "\u2605 8.5", "genres": "Drama, Fantasy", "poster":
  "https://artworks.thetvdb.com/banners/posters/299139-1_t.jpg", "fanart":
  "https://artworks.thetvdb.com/banners/fanart/original/299139-1_t.jpg"}, ...

I have no isues on thetvdb.com itself

One of the lists used in your adblocker is too aggressive and is blocking anything with “banner” in the URL that isn’t hosted on the site you’re currently using (HA site). It wouldn’t block them on thetvdb.com because that is the originating URL.

1 Like

Is there a way to resize the display cards so one can see more data without needing to scroll?

Not yet, there is currently a PR for it but I haven’t had a chance to check it out.

Ok thanks!

little lost here as my cards show nothing but the title I gave them.

I have:

upcoming-media-card.js in /config/www/custom-lovelace/upcoming-media-card

ui-lovelace.yaml in /config

resources: 
  - url: /local/custom-lovelace/upcoming-media-card/upcoming-media-card.js?v=0.1.1
    type: js

title: Vermillion Home
views:
  - title: Overview
  
  - title: Home Media
    cards:
      #Plex
      - type: custom:upcoming-media-card
        entity: sensor.plex_recently_added
        title: Plex Recently Added
      - type: custom:upcoming-media-card
        entity: sensor.radarr_upcoming_media
        title: Upcoming Movies

proper files in custom_components/plex_recently_added/

sensors in sensor.yaml

- platform: plex_recently_added
    name: Recently Added Movies # will create sensor.recently_added_movies
    token: !secret token
    host: !secret host
    port: 32400
    section_types:
    - movie

verified the created sensors are producing output. also a few images have been pulled into
/config/www/custom-lovelace/upcoming-media-card/images/plex

You’ve used the name config for the sensor (copy and pasted from the docs). Check out the comment next to it

So that would be the name you add to the cards config: entity: sensor.recently_added_movies

making progress, but images arent loading consistently

I’m trying to use this with Plex.
Installed both cards as described.
This link works (I see xml text):

http://192.168.1.2:32400/library/recentlyAdded?X-Plex-Token=yOuRPLexT0keng03sheRE

All blockers are turned off. I even use a browser that never had any blockers and I still can’t see anything. All I see is the title of the card. Running latest AH 106.2
Any ideas?

EDIT: I do get an error:
2020-02-29 17:03:49 WARNING (SyncWorker_12) [custom_components.plex_recently_added.sensor] No Metadata field for “Documentaries”

But in my states, I can see everything. Forgot to say that.

What’s your config for the component and card look like?

Well in terms of Plex my config is grayed out. I discovered Plex through HA integrations.

#Plex Server
#plex:
#  host: !secret plex_host
#  port: 32400
#  token: !secret plex_token
#  ssl: true
#  verify_ssl: false

As for your card (in config UI):

  • type: js
    url: /community_plugin/upcoming-media-card/upcoming-media-card.js?v=0.1.1

I have both upcoming media card 0.4.0 and plex recently added 0.2.9 installed through the HACS.

The card itself is:

cards:
- entity: sensor.plex_recently_added
title: Recently Added to Plex
type: ‘custom:upcoming-media-card’

Have you added config for the Plex Recently Added component to your configuration.yaml file? Does the sensor plex_recently_added show up in Developer >> States?

The plex config you shared above has nothing to do with this component or card.

Yes sorry, I have it as a sensor:

- platform: plex_recently_added
  token: !secret plex_token
  host: 192.168.1.xx
  port: 32400
  name: Recently Added to Plex

And yes it shows in my states and has values

Yes I now realize it has nothing to do… The one I shared… I got confused. Sorry

No worries and thank you. This is a bug and I’ll get it fixed in the next release.

Actually, it’s not a bug. You’ve just got the card setup wrong.

Your sensor config renames the sensor name: Recently Added to Plex

So your sensor’s name would be sensor.recently_added_to_plex
Meaning your cards config should be:

cards:
- entity: sensor.recently_added_to_plex
  title: Recently Added to Plex
  type: ‘custom:upcoming-media-card’

The error you’re getting means that you have a section in your library named “documentaries” that contains no metadata or no items, but otherwise everything should work fine.

1 Like