Troubleshooting & FAQ

This page lists common issues and their solutions. Before creating a new issue, please check if your problem is described here.

Common Problems

Card does not appear / "Custom element doesn't exist"

This is the most common issue and is almost always caused by an incorrect resource path in your Lovelace configuration.

1. Verify Resource Path:
   • HACS Installation: The path must be /hacsfiles/fast-search-card/fast-search-card.js.
   • Manual Installation: The path must be /local/fast-search-card.js.
2. Clear Browser Cache: After installation or an update, your browser might still be using an old version of the file. Clear your browser's cache completely. A simple refresh (F5) is often not enough; use Ctrl + Shift + R (or Cmd + Shift + R on Mac) for a hard refresh.
3. Check Logs: Go to Settings > System > Logs in Home Assistant to see if there are any specific errors related to loading the card.

Auto-Discovery finds no devices

If auto_discover: true is set but the card remains empty:

• Check Supported Domains: By default, the card discovers entities from domains like light, switch, climate, cover, media_player, fan, script, automation, and scene. Make sure you have devices in these domains.
• Check Area Assignments: The card heavily relies on areas. Ensure your devices and entities are assigned to an area in Home Assistant (Settings > Areas & Zones). Entities without an area might not be displayed as expected.
• Review include_/exclude_ filters: If you have used options like exclude_domains or exclude_areas in your card configuration, double-check that you are not accidentally filtering out all of your devices.

Icons are not showing up correctly

• Standard Icons: The card uses emoji for most standard icons. These should work on all modern browsers.
• Custom Icons: In custom_mode, you can define your own icons. If they don't appear, ensure the emoji or character is correctly entered in your configuration.

Custom Mode is not working

• Check enabled: true: Make sure you have set enabled: true under the custom_mode key.
• Validate JSON: If you are using a template_sensor or mqtt data source, the content of the sensor's attribute must be valid JSON. You can use an online JSON validator to check your data structure.
• Check Attribute Name: Ensure the content_attribute in your configuration matches the actual attribute name in your sensor that contains the item list.

Frequently Asked Questions (FAQ)

Q: Can I change the color scheme?

A: Currently, the card's color scheme is hard-coded to match the Spatial UI aesthetic. Advanced theming is not yet supported, but you can use a tool like card-mod for minor CSS adjustments.

Q: Why are my schedules from the card not running?

A: The timer and schedule functionality depends on the Scheduler Component integration. Please make sure you have installed and configured it correctly from HACS.

Q: Can I search through the content of my custom items?

A: Yes! The search engine automatically indexes the content field of your custom items. This allows for a powerful full-text search through your notes, recipes, or other custom data.