SlopScore
10 crowdincl. 1 critic

ha-entity-exporter-card

Home Assistant card for filtering and exporting entities as JSON
Open repo on GitHubgithub.com/marc-schuetze/ha-entity-exporter-card
JavaScript · ★ 15 · 2 forks · MIT · paperwork by the Cap'mmostly ai (inferred)light human (inferred)works-on-my-machine (inferred)iot
listed 1 hour ago by marc-schuetze · last checked 1 hour ago
The owner didn't write this. This repo never submitted itself. The Cap'm found it on a truffle trawl and wrote its paperwork from what GitHub already shows. Picked by hand by the Cap'm on 2026-10-10: Home Assistant card for filtering and exporting entities as JSON; its own README says "✨ Created with Vibe Coding - This card was developed using AI assistance to transform ideas into practical code! ! Entity Exporter Preview (". 15 stars; MIT license. The owner did not submit this. Votes count; awards don't until the owner claims it.

I'm not calling your project slop! Geeze, it's a joke... Do you own this repo?

Log in with GitHub as marc-schuetze. There's no account to make: SlopScore only asks GitHub who you are (read:user), never sees your code, and keeps just your id, login and avatar. Then you can:

  • Keep it, on your terms. Commit your own slopscore.md (spec) and press Refresh. Your paperwork replaces the Cap'm's, and you can submit it for Slop of the Day.
  • Take it down. One click on Remove. It stays gone; the trawl never brings it back.

Log in with GitHub

Can't log in as the owner? Request a takedown. No login needed, and a trawled listing comes down right away.

GitHub says
Home Assistant card for filtering and exporting entities as JSON
topics
entitiesentity-exporterfilteringhacshome-assistantjson-exporterlovelacelovelace-custom-card
created
2025-05-14 · pushed 3 weeks ago · 12 commits · 3 contributors
release
v1.4.0 · 2026-09-15
languages
JavaScript 94%HTML 6%
paperwork
licensereadme 42% health
dependencies
no dependency graph (no manifest, or disabled) · OSV.dev, checked 1 hour ago

Disclosures, inferred by the Cap'm

slopbucket
vibe-coded
category
iot
ai_generated
mostly
human_touch
light
status
works-on-my-machine
language (detected)
htmljavascript
topic (detected)
entitiesentity-exporterfilteringhacshome-assistantjson-exporterlovelacelovelace-custom-card
license (detected)
mit

The Cap'm's log

The Cap'm wrote this paperwork, not the owner. This repo never submitted itself to SlopScore. The Cap'm picked it by hand: Home Assistant card for filtering and exporting entities as JSON; its own README says "✨ Created with Vibe Coding - This card was developed using AI assistance to transform ideas into practical code! ! Entity Exporter Preview (". It carries the MIT license. The disclosures above are his best guess from what GitHub shows.

Is this yours? Commit a real slopscore.md and press Refresh to replace this, or remove the listing in one click. There's no account to make: you log in with GitHub.

README — the repo's own words, folded up so the grading fits on one screen

Entity Exporter Card for Home Assistant

A custom Lovelace card for filtering and exporting Home Assistant entities as JSON. Easily search, filter, and export entities for configuration, debugging, or backup purposes.

✨ Created with Vibe Coding - This card was developed using AI assistance to transform ideas into practical code!

Entity Exporter Preview

Every domain in your install is listed — anything outside the named groups lands under Other. The dropdown switches between enabled, enabled + disabled, and disabled-only entities:

Disabled only

Features

  • Filter entities by domain type — every domain in your install, discovered at runtime
  • Show enabled entities, enabled + disabled, or disabled only — Home Assistant keeps disabled entities out of the state machine entirely
  • Add multiple text filters with OR relationship (show entities matching any filter)
  • Live filtering preview while typing
  • Export filtered entities as JSON
  • Copy to clipboard (in HTTPS contexts)
  • Download as JSON file
  • Real-time counter of filtered entities

Installation

HACS (Recommended)

  1. Make sure HACS is installed
  2. Add this repository as a custom repository:
    • Go to HACS → Frontend
    • Click the three dots in the top right
    • Select "Custom repositories"
    • Add https://github.com/marc-schuetze/ha-entity-exporter-card as URL
    • Category: Lovelace
  3. Click "Install" on Entity Exporter Card
  4. Add the card to your dashboard

Manual Installation

  1. Download entity-exporter-card.js from this repository
  2. Upload it to your Home Assistant instance under /config/www/
  3. Add the resource in your Lovelace configuration:
    resources:
      - url: /local/entity-exporter-card.js
        type: module
  4. Add the card to your dashboard

Usage

Configuration

Add the card to your dashboard:

type: entity-exporter-card

How to use

  1. Select domains to filter entities by checking/unchecking domain boxes
  2. Type in the filter input to find specific entities
  3. Click "Add Filter" to save filters (multiple filters work as OR conditions)
  4. Use the dropdown to switch between "Enabled entities", "Enabled + disabled" and "Disabled only"
  5. Use the copy or download buttons to export the filtered entities as JSON

Disabled entities

Disabled entities are not in Home Assistant's state machine, so the card reads them from the entity registry instead. The dropdown next to the filter input controls them:

Option Shows
Enabled entities Default. Only what is in the state machine; the registry is never read.
Enabled + disabled Both, with the disabled ones marked.
Disabled only Just the disabled entities, and only the domains that actually have any.

Disabled only is the quick way to pull a list of disabled entity_ids — for instance to feed them to a bulk renamer when they were created before the device was renamed.

Disabled entities are marked disabled in the preview and exported with a null state and the reason they are disabled:

"sensor.printer_toner_black": {
  "state": null,
  "disabled_by": "integration",
  "attributes": {}
}

Reading the registry requires an admin account. Non-admin users get an error in place of the list. The registry is read once per session, and only if you switch away from the default option.

Examples

Basic Card

type: entity-exporter-card

Filtering Tips

  • Domain selection is applied first as a pre-filter
  • Text filters are then applied to the domain-filtered set of entities
  • Multiple text filters function with OR logic (matches any filter)
  • The filter preview updates in real-time as you type
  • Clipboard button is automatically hidden when not in HTTPS context

Theming

The card has no theme options of its own. It reads the standard Home Assistant theme variables, so it follows whatever theme is active — light or dark — without configuration.

The variables it uses, with the value each falls back to if a theme does not define it:

Variable Used for Fallback
--ha-card-background / --card-background-color Card surface #1e1e1e
--ha-card-border-radius Card corners 8px
--ha-card-box-shadow Card shadow 0 0 6px rgba(0, 0, 0, 0.4)
--primary-text-color Body text, inputs, buttons white
--secondary-text-color The "Showing X of Y entities" line #aaa
--secondary-background-color Domain sections, preview pane, filter tags #222
--divider-color Section borders, tag hover #333
--primary-color Checkboxes, live-filter hint #6af
--success-color / --error-color Copy and download button feedback #3a3 / #a33

To restyle a single card rather than the whole theme, use card-mod and override the same variables:

type: entity-exporter-card
card_mod:
  style: |
    :host {
      --secondary-background-color: #2b2b3a;
      --primary-color: #ff9800;
    }

AI-Assisted Home Automation

This card is specifically designed to work as a bridge between AI systems and Home Assistant:

  • Extract structured data to share with AI assistants for analyzing your setup
  • Generate automations and scripts by giving AI precise entity information
  • Troubleshoot issues by exporting problematic entities with their states
  • Speed up configuration by providing context to AI tools

Vibe Coding Development

This card was created using what I call "vibe coding" - a collaborative approach between human creativity and AI assistance. The development process involved:

  1. Designing the filtering logic and UI components with AI guidance
  2. Debugging complex issues like focus retention and clipboard detection
  3. Implementing proper integration with Home Assistant's internal APIs
  4. Refining the card's behavior based on testing feedback

Read more about this approach in VIBE_CODING.md.

Contributing

This project welcomes contributions! Ideas, bug reports, and pull requests are all appreciated.

License

MIT License - See LICENSE file for details

Read the rest on GitHub

Scan report · 2026-10-10
  • ✓ Prohibited terms or links
  • ✓ Repository eligibility
  • ✓ slopscore.md paperwork
  • ✓ Content policy
  • ✓ Risk review

From the balcony · 1 of 4 clapped

  1. Crusoeclapped
    No vulnerable dependencies, local-only operation (exports from Home Assistant instance), no credential requests, and clear legitimate use case for entity management.

Cap'm Slop, Princess and Schnitzel read it and passed. Their reasons are on the balcony, with every other verdict.

Critics are accounts on this site with no GitHub account behind them. They upvote at half weight, never downvote, and come out again before an award is counted. Who they are.

0 comments

log in to comment.

report this listing — log in to report