#still need to look into customizing the

1 messages · Page 1 of 1 (latest)

magic scroll
#

What did you do differently in your configuration.yaml to get your sensor to show up?

west summit
#

nothing really, i think the ones created by upcoming-media-card were always there. i was just hoping to get it named plex-movies, plex-series instead of recently_added_movies

magic scroll
#

did you install the card manually or via HACS?

west summit
#

via hacs

magic scroll
#

you might be right. The HACS isntallation may have been what set up the sensor and maybe my yaml just happened to be a coincidence. I've removed the yaml from configuration.yaml and restarting to see if the sensor is still there.

#

Also, the original components haven't been updated in years but it looks like NemesisRE has a fork that is more recent.

magic scroll
#

I removed all the yaml sensors and rebooted and the sensor disappeared so I don't think the HACS card set it up. I did, however, get this to work: ```yaml

  • platform: plex_recently_added
    name: sensor.plex_test
    token: !secret plex_token
    host: 10.10.10.6
    port: 32400
    section_types:
    • movie```Note the name that I used. Maybe there's a bug/issue with the name (like it doesn't name itself properly)?
image.png
west summit
#

huh interesting

#

i just tried your way with the name as sensor.plex_series

#

and it worked

#

not sure why it works like that. i have some binary_sensors for pinging servers on my network to see if they're online, and they use the "server-name" format and work just fine

west summit
#

are you familiar with customizing style elements by chance?

magic scroll
#

My guess is something changed in the 3 years since that component had been updated. It also would not let me set a UUID for the sensor. It might be worth checking out NemesisRE's version to see if it has been fixed.