Loading repository data…
gadgetchnnel / repository
A custom Lovelace card for displaying a combination of persistent notifications, calendar events, and entities in the style of a feed.
A transparent discovery signal based on current public GitHub metadata.
This score does not audit code, security, maintainers, documentation quality, or suitability. Verify the repository and its current documentation before adoption.
A custom Lovelace card for displaying a combination of persistent notifications, calendar events, and entities in the style of a feed.
You can install this manually or via HACS if you want easy updating,
Download all files and place them in the folder www/custom-lovelace/home-feed-card under your Home Assistant config folder.
Reference the file under resources like this:
resources:
- url: /local/custom-lovelace/home-feed-card/lovelace-home-feed-card.js?v=0.0.0
type: js
Search for "Lovelace Home Feed Card" in the store and follow the instructions
Alternatively, you can add https://raw.githubusercontent.com/gadgetchnnel/lovelace-home-feed-card/master/custom_card.json to the card_urls in custom_updater if you want to do it that way.
Version 0.2.4 uses dynamic module imports to import the Moment module. Firefox versions < 66 don't support these by default and you may need to set the javascript.options.dynamicImport option in about:config for it to work.
type: 'custom:home-feed-card'
title: Home Feed
card_id: main_feed
show_empty: false
calendars:
- calendar.home_calendar
- calendar.work_calendar
id_filter: ^home_feed_.*
more_info_on_tap: true
state_color: true
entities:
- sensor.next_alarm_time
- entity: sensor.bin_collection
name: Next Bin Collection
more_info_on_tap: false
- entity: sensor.reddit_help
multiple_items: true
list_attribute: posts
timestamp_property: created_
max_items: 5
content_template: '[{{title}}]({{url}})'
If this is set, it is used as the key for cacheing the feed in Local Storage, otherwise a key based on URL and card title is used.
This is a list of calendar entities you want events to display for in your feed.
How the calendar event timestamp should be formatted. Valid values are: relative, date, time and datetime.
The number of days before the current day to include calendar events for in the feed
The number of days after the current day to include calendar events for in the feed. This will include events up to the end of that day so, if you only want the current day, this should be set to 0
The number of days before the current day to include event history for in the feed
This is a regular expression for filtering persistent notifications by notification id. In the example above, "^home_feed_.*" will result in only notifications with ids starting with home_feed_ from being displayed.
Display the title for persistent notifications in the feed
A list of entities to display on the feed. These can be displayed as single items, or multiple items from a sensor attribute (see the section on multi-item entities). Single item entities are displayed as follows:
Each entity can be just an entity id or an entity object, allowing more customisation.
Whether to show the card if there are no items to show
This controls whether the feed is scrollable. If this is set to false then, by default, all items will be displayed unless the max_height or max_item_count option is used.
The maximum height of the feed in CSS format (e.g. "100px", "20em", etc.). When scrollbars are disabled, the content will be cut off at this height, otherwise it will control the scrollable height.
The maximum number of items to show in the feed, useful if scrollbars are disabled.
When this is true, tapping/clicking and entity will display the more-info dialogue. This can be overridden for individual entities (see later). From version 0.3.0 this also supports notifications, calendar events and multi-item entities. Multi-item entities require the new detail_template option (see later).
When this is true, a more compact layout is used where the time is displayed on the same line as the item content. Note: Due to layout constraints this also removes the dismiss button from notifications and so notifications will always be clickable in compact mode even if more_info_on_tap is disabled.
Setting this to false removes the icons from the left of the feed, can be used together with compact_mode to get a very compact feed.
By default, durations of less than a minute are displayed as "<1 minute ago" or "in <1 minute". Setting this option to true disables this, and displays the exact duration. Note: Doing this will make the time difference display refresh every second until the duration is 1 minute
Setting this to true will change the icon colour based on the state (the same as the option in the standard Entities card)
For single-item entities the following options are supported, see the section on multi-item entities for the options available for those.
This allows overriding the display name of the entity, otherwise the friendly name is used
Allows overriding the icon of the entity
Define an attribute to use instead of the state for the entity in the list
e.g. entities: - entity: sensor.my_sensor name: Sensor Time attribute: time
This allows the display format for that entity to be customised. The format is {{propertyname}}. The available properties are:
In addition any attribute of the entity can be used (do not prefix with attributes.).
This allows the history of an entity to be displayed, rather than just its current state (states of "unknown" are automatically filtered out). This currently uses the history for the last day.
The maximum history of the entity to display, this defaults to 3
This controls whether to remove repeated states from the history (e.g. the current state is the same as the previous state). Since "unknown" states are filtered out, this will avoid an entity appearing twice because it changed from "on" to "unknown" and back again following a restart. This can be disabled by setting this to false.
This allows custom mappings of states to display names, to override the device_class based mappings. In the example below this is used to map the "not_home" state to "Unknown Destination" instead of the default "Away".
A list of states to exclude. By default this is just "unknown". For example: entities: - entity: sensor.front_door name: Front Door exclude_states: - "off" - "unknown"
How the timestamp should be formatted. Valid values are: relative, total, date, time and datetime.
This is the same as the option of the same name at the top level. This allows for this setting to be overridden at the entity level.
Example:
type: 'custom:home-feed-card'
title: Home Feed
show_empty: false
id_filter: ^home_feed_.*
entities:
- entity: device_tracker.my_phone
name: Me
content_template: '{{display_name}} arrived at {{state}} ({{latitude}},{{longitude}})'
include_history: true
max_history: 5
remove_repeats: false
state_map:
not_home: Unknown Destination
Starting from 0.3.5b1, automations are handled slightly differently from other entities. The differences are as follows:
Entities can made to appear as multiple items in your feed if they contain a list of objects as an attribute. For example, the Reddit sensor has attributes like this:
{
"posts": [
{
"title": "Post title",
"created": 0000000000,
"body": "Post body!",
"score": 00,
"comms_num": 00,
"url": "https://www.reddit.com/r/*****",
"id": "******"
},
{
"title": "Another Post title",
"created": 0000000000,
"body": "Another Post body!",
"score": 00,
"comms_num": 00,
"url": "https://www.reddit.com/r/*****",
"id": "******"
}]
}
To add multi-item entities for this the following format would be used:
type: 'custom:home-feed-card'
title: Home Feed
show_empty: false
calendars:
- calendar.home_calendar
- calendar.work_calendar
id_filter: ^home_feed_.*
entities:
- entity: sensor.reddit_<name>
multiple_items: true
list_attribute: posts
timestamp_property: created
max_items: 5
content_template: '{{title}}'
This must be true to identify the entity as a multi-item entity
The attribute on the entity which holds the list of items which should be included in the feed
The property on the object which has the posted time. The property can be either a string in ISO format or a Unix timestamp. If this is not supplied, the modified timestamp of the entity is used.
The maximum number of items to display for this entity
This controls the message text which is displayed for each item. Any property on the object can be included as part of the text by using the format {{propertyname}}
Basic example, template generating text:
'{{title}}' -> 'Post title'
Advanced example, template generating Markdown:
'[{{title}}]({{url}})' -> "[Post title](https://www.reddit.com/r/...)" This would be rendered as Post title
Selected from shared topics, language and repository description—not editorial ratings.
djdevil /
A custom Lovelace card to display alerts and notifications based on entity states.
86/100 healthstudiobts /
The Device Pulse Table Card is a custom Lovelace card designed to work with the Device Pulse integration. It provides a table view of devices monitored through the integration.
77/100 healthstudiobts /
The Device Pulse Timeline Card is a custom Lovelace card designed to work with the Device Pulse integration. It provides a clear, visual timeline of connection and disconnection events for each monitored device, offering both horizontal and vertical layouts to fit any dashboard design.
76/100 healthfixtse /
A custom card for Home Assistant to show your Inbox, To Do and Teams Last Message from Office365
70/100 healthmath0ne /
:busstop: This Lovelace custom card displays Translink data from the public api for a given stop and route
35/100 healthPrivate-Storm /
A highly customizable, animated sidebar navigation card for Home Assistant Lovelace dashboards.
64/100 health