Filter on Empty Values or Any Values

[SolusCado]

I would like to setup two separate cards, one that shows all items where a specific attribute (Studio) is empty, and one where that attribute has any value at all. I cannot seem to get this to work.
I can use 'sort_by' on the 'studio' attribute to group the items, but I need to put them in separate cards so I can restrict who can see a specific grouping.
Is there any way to specify something like "filter: studio=''" or "filter: studio=empty"? (And conversely, "filter: studio!=''" or "filter: studio!=empty"...)

[mkanet]

Hi @SolusCado please try version 0.6.1. I just updated this repo a few minutes ago with this enhancement. Please note that when upgrading Upcoming Media Card, sometimes, it requires deleting your web browser cache to remove lingering old upcoming media card javascript code after upgrading to the new version.

Let me know how it works for you!

[SolusCado]

Thanks for the quick response! But… it doesn’t seem to work at all. I opened a new browser in incognito mode just to be completely sure I was getting a new version of the script. It’s loading in my browser as upcoming-media-card.js?hacstag=146783593061. From: MKANET ***@***.***> Date: Tuesday, December 3, 2024 at 4:14 PM To: custom-cards/upcoming-media-card ***@***.***> Cc: Michael Bailey ***@***.***>, Mention ***@***.***> Subject: Re: [custom-cards/upcoming-media-card] Filter on Empty Values or Any Values (Issue #103) Hi @SolusCado<https://github.com/SolusCado> please try version 0.6.1. I just updated this repo a few minutes ago with this enhancement. Please note that when upgrading Upcoming Media Card, sometimes, it requires deleting your web browser cache to remove lingering old upcoming media card javascript code after upgrading to the new version. Let me know how it works for you! — Reply to this email directly, view it on GitHub<#103 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AEKBIR4VJFGH4WNAGTDYHED2DYNK5AVCNFSM6AAAAABS6KRLI6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKMJVGU3DGNBTGE>. You are receiving this because you were mentioned.Message ID: ***@***.***>

[mkanet]

Honestly, I didnt test this yesterday since I thought I was a pretty straight-forward fix. Can you post the full EXACT card code you're using? Ill see if I can reproduce the issue.

[SolusCado]

There isn't much to it:

type: custom:upcoming-media-card
title: Recently Added
entity: sensor.media_library_plex_recently_added
image_style: fanart
enable_tooltips: true
enable_transparency: true
hide_unflagged: false
flag: false
filter: studio=""
max: 20

[mkanet]

@SolusCado I tried to test this on my setup before uploading version 0.6.2. However, I had no Sonarr shows to test against that currently have no studio defined. Please try it let me know if it works

[SolusCado]

I would think any blank filter would be testable, but I'll check it shortly and let you know.

…

________________________________ From: MKANET ***@***.***> Sent: Thursday, December 5, 2024 11:27:03 PM To: custom-cards/upcoming-media-card ***@***.***> Cc: Michael Bailey ***@***.***>; Mention ***@***.***> Subject: Re: [custom-cards/upcoming-media-card] Filter on Empty Values or Any Values (Issue #103) @SolusCado<https://github.com/SolusCado> I tried to test this on my setup before uploading version 0.6.2. However, I had no Sonarr shows to test against that currently have no studio defined. Please try it let me know if it works — Reply to this email directly, view it on GitHub<#103 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AEKBIRYRIEBSMJ5EX6BV47D2EDHLPAVCNFSM6AAAAABS6KRLI6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKMRRGU4TIOJYGQ>. You are receiving this because you were mentioned.Message ID: ***@***.***>

[mkanet]

I dont know why I didnt think of that before. I just tested it. The following works: filter: studio="" or filter: studio=''

[SolusCado]

Ok; those still don't work for me - BUT this does:
filter: studio=

So, if I just leave it blank to the right of studio, it filters out any records with any value at all. So, that's good enough.

NOW... is there any way to reverse that? To show a wildcard or something, so that I only get records WITH a studio?

[mkanet]

Ok; those still don't work for me - BUT this does: filter: studio=

So, if I just leave it blank to the right of studio, it filters out any records with any value at all. So, that's good enough.

NOW... is there any way to reverse that? To show a wildcard or something, so that I only get records WITH a studio?

Glad its working for you. If you have a suggestion on how to reverse this using filter setting, let me know.

[gfay63]

You're right, I apologize. Let me write a clean version of the comment without any markdown formatting so you can easily copy/paste it to GitHub:

I'm experiencing similar filtering issues, but it appears the problem may be more fundamental. The filter functionality doesn't seem to work at all, regardless of the value or operator used.

Examples of filters I've tried (none work):

- filter: runtime=2 (to filter trailers)
- filter: runtime=97 (to match a specific movie)
- filter: rating='' (to match empty ratings)
- filter: title=Drop (to match a specific title)

Browser console shows repeated errors:

TypeError: this._config.filter.exclude is not iterable
  at Wt.update_entities (/local/auto-entries.js:182:7500)
  at async Wt.update_all (/local/auto-entries.js:182:3552)

This error suggests the filter implementation expects a different structure than what's documented in the README. I've tried alternative formats like:

filter:
  exclude: title=Drop

and

filter:
  include: title=Drop

but these produce the same error.

Looking at a trailer example in my data:

airdate: '2025-01-25T18:01:33Z'
aired: '2025-04-10'
release: $day, $date $time
flag: true
title: Drop
episode: ''
runtime: 2
studio: Blumhouse Productions
genres: Thriller, Drama
rating: ''

None of the documented filter approaches work to filter these items, suggesting this might be a broader issue with the filter implementation itself rather than just handling of empty values.

[mkanet]

@gfay63 Thats now how the general filter was designed to work. First of all, the filter currently only excludes the defined filter value, not include. Secondly, you can only have 1 filter per card. The only new enhancement I added here was to allow excluding items with null values. such as:

filter: studio='' or
filter: studio=

If you would like to see new features such as include filter or adding multiple filters, feel free to open a new issue for these feature requests.

[gfay63]

@mkanet Gotcha. Thanks for the confirmation...and quick reply! I can work with that as well, but still cannot get it to work. E.g., for this movie:

- airdate: '2025-01-27T07:21:57Z'
  aired: '2024-08-28'
  release: $day, $date $time
  flag: false
  title: Night Call
  episode: ''
  runtime: 97
  studio: Daylight Films
  genres: Thriller, Action
  rating: ★ 7.7
  poster: /local/upcoming-media-card-images/plex/Recently_Added_Plex_Movies/p81426.jpg
  fanart: /local/upcoming-media-card-images/plex/Recently_Added_Plex_Movies/f81426.jpg

none of these filters exclude it:

filter: episode=''
filter: episode=
filter: runtime=97
filter: title=Night Call
filter: flag=true

FYI, the other parts of the YAML are:

title: Plex Recently Released Movies
type: custom:upcoming-media-card
entity: sensor.recently_added_plex_movies
image_style: fanart
sort_by: number
enable_tooltips: true
filter: episode=''

In fact, I can't get the filter to do anything. I've tried everything and have never seen it exclude any. I am on the latest version. I just installed it a few days ago for the first time.

Thank you!
Greg