🖼 Camera Gallery Card - NEED TESTERS

[alexh3o]

Hi, thanks for your anwer.

The value of seeing the filename is that i have 2 cameras that don’t have an embedded timestamp, so I can get the date and time with the filename only. My filenames are also indicative, with a suffix mentionning the context (snapshot triggered by motion sensor detection, camera activity detection or timed).
Edit: i just tried the name format recognition and it works well, it does address my main need which was to get the date & time, so well, nevermind, filename is not that important !

Yes, for the title i was just thinking of a static one. My snapshots are regularly deleted/cleaned, and it can happen that there is no more snapshot in the folder, hence the title to still identify which camera the card relates to.

[TheScubadiver (Ramon)]

Hey!

Glad to hear the recognitions works as intented!

Were you looking for something like this:

Let me know!

[TheScubadiver (Ramon)]

This is my current config!

type: custom:camera-gallery-card
source_mode: sensor
max_media: 50
preview_position: top
bar_position: top
thumb_size: 140
bar_opacity: 73
preview_click_to_open: false
color_mode: auto
delete_service: shell_command.gallery_delete
thumb_bar_position: top
preview_height: 340
live_cameras:
  - camera.lily
  - camera.muis
  - camera.deurbel_duidelijk
live_default_camera: camera.deurbel_duidelijk
thumb_layout: vertical
object_filters:
  - person
  - car
  - visitor
  - dog
live_enabled: true
live_default: true
style_variables: |-
  --cgc-live-active-bg: #ff0003;
  --cgc-pill-size: 15px;
autoplay: true
auto_muted: true
object_colors:
  fsdfdsf: "#c34141"
entities:
  - sensor.gallery_deurbel
object_fit: cover
live_auto_muted: false
max_files:
  sensor.test: 1
filename_datetime_format: DDMMYYYY
live_camera_entities:
  - camera.deurbel_duidelijk
  - camera.lily
  - camera.muis1
  - camera.lilycam_hd_stream
start_mode: live
persistent_controls: false
media_sources:
  - media-source://frigate/frigate/event-search/clips
live_camera_entity: camera.lily

[TheStigh]

Great, thanx @TheScubadiver

But I have following issue (running your 2.2.0 and HA 2026.4.0), after adding integration for FileTrack, I do not get any dialog, and I can’t use mode: sensor

PS; I’m old-school so use straight YAML and not any UI setup tools …

[TheScubadiver (Ramon)]

Welcome!

I should add a full YAML config to the readme, for the old (school) people Thanks for the reminder!

Had that issue before on GitHub and saw you commented that.

Currently it’s on v2.3.1. If you could update and let me know if it’s still missing?

Thanks!

[TheStigh]

2.3.0 was the latest on HACS - did an update.
Then uninstalled FileTrack, rebooted, installed FileTrack again.

Hehe, I’m only 57 next Sunday - still young! Com’on!
I guess there is more explanations in the UI tool than what I get from git - don’t get what all values do…

Btw; it says video is live but it ain’t (I see the clock is not ‘ticking’.

And, Chrome & Vivaldi responds quite different.

This is what I get and see ref FileTrack:

[alexh3o]

Hey, yes that’s i was thinking about !

[TheScubadiver (Ramon)]

57 is still young. I stand corrected, sir!

Let me test some things with Frigate on my own setup. I’ll let you know if I need some more details/info about yours. I’ve had one other user having this issue.

I’ll report to you later, sir.

Edit: You only way to make a sensor is using the UI. Are you still not able to see the Create new file sensor part?

[TheScubadiver (Ramon)]

It’s just a simple header/title card

type: heading
icon: phu:reolink-doorbell
heading: Doorbell
heading_style: title

[TheStigh]

Hi Ramon,

57 is young, indeed

As my entire Dashboard is built manually through YAML, I cannot combine manual and UI (what I can do is create another dashboard and use UI, perhaps I can do the sensor from there).

You should offer the possibility to use your card without relying on UI to fully configure it.

[TheScubadiver (Ramon)]

You are right. I should also serve the old school people. The people that are still living in the Stone Age

In the next update (card & FileTrack) I added the option to add a sensor through YAML. Will release that later tonight. So you have to update the card and FileTrack.

The -how to add a YAML file sensor- will be disclosed in the release notes.

Hope that helps you!

[TheStigh]

You’re so “kind” to me…

Thanks for the update, though HA nags when trying to add the FileTrack integration to configuration.yamlso that is not a good option for anybody.

Do I understand it correctly that FileTrack requires the files to be located in /config/www/ ? In that case, for me using Frigate this is not an option.

I use (in YAML):

    media_sources:
      - media-source://frigate/frigate/event-search/clips
      - media-source://frigate/frigate/recordings

[HerrLux]

Hi,
I just stumbled upon this great card.
Want to use it to simply browse through camera snapshots stored in /config/www/camera_snapshots/somename_YYYYMMDD-HHmmss.jpg

How do I set up the card to do so?
Entering /config/www/camera_snapshots/ in the source field when selecting Media folders doesn’t do the trick.

[TheScubadiver (Ramon)]

Hi,

Yes, FileTrack is only used when you have files saves in the /local storage.

Got the files from frigate already showing and playing?

[TheStigh]

Yeap I do.

[TheScubadiver (Ramon)]

Hey!

In that case you’ll need a file sensor to show the files. Did you by any chance read the ReadMe file on GitHub? FileTrack (for sensor mode)

All you have to do is install FileTrack and you can add the sensor and folder in the editor as you can see in the example below. ‘hoepla’ is just an example.

You could replace bothe ‘hoepla’ with ‘camera_snapshots’.

Folder would be /config/www/camera_snapshots
Sensor would be sensor.camera_snapshots

After you press ‘Create sensor’ you fill in the sensor at File Sensor at you’re all set!

[TheScubadiver (Ramon)]

Good to hear! What was the issue? If there was any.

[TheStigh]

Was never anything wrong with the Frigate part - just your docs who’s a bit unclear about FileTrack vs sensor mode vs gallery mode…

So when pointing directly to Frigate, use Gallery Mode and FileTrack is not needed at all.

[eltonline]

Hi. I’m a long time user of the original Files integration (in YAML mode) and Gallery Card. Great to see the new Camera Gallery Card and you’re keeping the really useful Files (now FileTrack) alive! I’ll refer to FileTrack from now on.

For years, every time I deleted an entity it left a trail of orphaned entities which were difficult to clean up. It also means you can’t configure the entity or delete them in the Home Assistant GUI. The solution is of course the unique_id attribute so that entities are stored in the entity-registry. This is the new default.

But I noticed that FileTrack still doesn’t support unique_id. So I decided to fix it so everyone can benefit from a more stable integration.

I’ve sent you a PR for changes to implement my enhancement for unique_id in FileTrack. I also updated the help. Let me know if you spot any issues but it works perfectly on my system.

[eltonline]

In the meantime I have a question. After a lot of experimenting the last few years, I found that Unix Timestamp offers the most flexible timestamp for Home Assistant and automations. It also supports timezones and daylight savings properly.

Have you considered adding unix timestamp as a filename option? For example I use <unix-timestamp>_cam1.jpg

If its not high on your list, I’m happy to do it

EDIT: escape the arrows.