Can't get filter work
See original GitHub issueDescribe the bug I have several sensor that id ends with ‘_battery’ but they don’t auto add in the card using the filter feature
How to reproduce Just add the configuration to the card through HA Lovelace UI
Expected behavior At least ten sensor would be integrated in the card
YAML configuration
type: 'custom:battery-state-card'
title: Battery levels
entities:
- sensor.button_table_battery
filter:
include:
- name: entity_id
value: '*battery'
Screenshots
Version 1.3.4
Issue Analytics
- State:
- Created 3 years ago
- Comments:9 (7 by maintainers)
Top Results From Across the Web
Best 5 Ways to Open and 2 Ways to Prevent STUCK Water ...
Turn your water supply off. · Relieve the water pressure on the lines before you attempt to unscrew the housing that holds the...
Read more >How Do I Get My Water Filter Unstuck
Sometimes, the filter can get wholly or partly unscrewed but yet still stays stuck to the unit. This is where using a pair...
Read more >Changing a Whole House Water Filter That's Stuck? Here's How!
The most common reason for a whole house filter to get stuck is the buildup of minerals from contaminated water. At times just...
Read more >Removing a Stuck Water Filter - Product Help | Whirlpool
If the water filter is stuck · Press and hold the button while the water filter is ejected. · Push on the filter...
Read more >Removing a Stuck Water Filter - Product Help - JennAir
Quarter Turn Filter · To remove filter turn the water filter a quarter turn to the left. Normally, the cap will be aligned...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Fixed in v1.3.5
No the fault is on my side! The doc states that in case of wildcard it should be “matches” by default. Sorry about that