@tmchow You can do this using the customize section in your config YAML, or in the UI (Configuration > Customization). In the YAML wit would be something like this:
homeassistant:
...
customize:
sensor.my_sensor:
icon: mdi:home
You can use the standard Material Design icons in the format mdi:iconname
I donât think this is something that I would be able to implement in the card, since it can only see the current state of the entity and not the history. The best way of doing this would probably be to have automations creating persistent notifications when the doors open and close, which would appear on the feed. If you use one notification id for door open and another for door close, then you would always see when it last opened or closed (unless you dismiss the notification).
You need to define device class. https://www.home-assistant.io/components/binary_sensor/#device-class
You need to define device class. Binary sensor - Home Assistant
It seems these are already set with the proper device classes. For example, if I go into looking at my Foyer Motion binary sensor, youâll see device class is already set to motion and yet the home feed card just says off and on. What am I missing?
Due to the way my card displayâs the entities, it canât use the standard entity rows. These do translation between the internal state and the display state based on the device class. My card is only picking up the internal state (âonâ or âoffâ). Iâm currently investigating ways to leverage this same logic in my card.
This will possibly involve having a default mapping built into the card, which you can also override in the configuration (e.g. you may want a door sensor to show the state as âopenedâ in the card instead of just âopenâ to be more âfeed-likeâ).
Iâve worked out how to implement the standard device class logic and have release a beta version (0.2.8b1) which is now available on HACS. This doesnât implement any way to override the mapping (e.g. use âOpenedâ instead of âOpenâ) as Iâm not sure how useful this would actually be. However, I have implemented a way to customise the text displayed so that it doesnât just show âname @ stateâ. This uses the content_template option (which was previously only used for multi-item entities), like this:
type: 'custom:home-feed-card'
title: Home Feed
show_empty: false
id_filter: ^home_feed_.*
entities:
- entity: device_tracker.person1_phone
name: Person 1
content_template: '{{display_name}} arrived at {{state}} ({{latitude}},{{longitude}})'
- entity: device_tracker.person2_phone
name: Person 2
content_template: '{{display_name}} arrived at {{state}} ({{latitude}},{{longitude}})'
The template can use display_name and state, plus any attributes from the entity.
Thank you Steven, iâll try.
Thanks for your work on this, itâs super useful.
Are the entityâs icons supposed to automatically show in the feed (mine all show as the bell), or do they all have to be manually defined in the config?
Few issues/questions Iâm not figuring out yet:
This isnât currently possible, but Iâll defintely consider it as, if possible, it would be a great feature.
I may consider adding an option for this, but you can do this now by wrapping my card in the auto-entities card as I mentioned in my earlier post.
Do you definitely have the beta version installed (this was added in 0.2.8b1)?
If you use HACS you will need to click on the âhamburgerâ menu when on the details for my card and select âShow Betaâ, otherwise you can manually download the beta versions from the Releases tab on the GitHub page.
Not currently, but Iâll look into adding an option to disable the scroll bar and set a maximum number of items.
Beta version 0.2.8b3 has now been published.
This includes new options to:
The additional options for entities are:
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 In addition any attribute of the entity can be used (do not prefix with attributes. ).
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â.
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
The top level config also has the following three options:
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.
If you are using HACS and donât see the new version, check that you have enabled Beta versions (âShow Betaâ on the âhamburgerâ menu) and also try using the âReloadâ option to reload the data.
If you are not using HACS, you can download this release from here.
0.2.8 has now been published as a non-beta release. This also includes an additional fix for calendar events. The card should have been sending the time as UTC when querying the events for the feed, but was actually sending it as the local time. This has been fixed now, so the correct events should now appear in the feed.
Hi, thanks for this card; itâs a very nice addition.
One question:
I am trying to use the new state_map to map on/off for some groups of doors to open/closed. It doesnât seem to be working. Config is below.
- type: 'custom:home-feed-card'
title: Home Feed
show_empty: false
id_filter: ^home_feed_.*
entities:
- entity: group.household
- entity: group.exit_doors
state_map:
Off: Closed
On: Open
- entity: group.garage_doors
state_map:
Off: Closed
On: Open
- entity: alarm_control_panel.ha_alarm
@jwelter I believe the internal state is âonâ and âoffâ rather than âOnâ and âOffâ and, since the map is a dictionary, it is case sensitive.
I had tried that as well; but same issue. Wondering if the âgroupâ represents state differently.
This worked fine for me with a group containing two binary sensors with a device_class of âdoorâ, which should be the same as with actual door sensors:
- type: 'custom:home-feed-card'
title: Home Feed
show_empty: false
id_filter: ^home_feed_.*
entities:
- entity: group.doors
content_template: '{{state}}'
state_map:
'on': 'Some doors are open'
'off': 'All doors are closed'
The content_template shouldnât actually be needed there, I was just experimenting with how a combination of the content_template and state_map can be used to have something more interesting than just âEntity is at stateâ.
Edit: If this is still not working for you, make sure you are on the latest version or try reinstalling it from HACS (if you use it).
Ahhh!!! I was missing the âxxxxâ around the states; added that and working well. Thanks!
please make state filtering function without using auto-entity
Is there an example of max_height I have tried to implement it, but canât get it to work
Is it not available through HACS anymore? Canât find it⊠Even tried to reinstall HACS.