I am using the Collapsable-card config to clean up multiple lights in my rooms.
I was using the hue like card for the lights to rename etc.
I have found that when i use the code under the collapsable card it doesn’t change the title and icons.
type: custom:collapsable-cards
title: Office
cards:
- type: custom:hue-like-light-card
entities:
- entity: light.bedroom_light
title: Ceiling Light
Icon: null
show_header_toggle: true
type: custom:hue-like-light-card
entity: light.bedroom_light
title: Ceiling Light
icon: mdi:lightbulb
WallyR
(Wally)
May 13, 2025, 8:01am
2
it says custom: in your YAML, so it is a custom third party card.
You need to find the GitHub page for that card and then post the issue there or if the author of the card have made a thread on the forum, then find that particular thread and reply to that.
The GitHub repo does not have an issues or wiki section - and there is no thread on the forum.
A custom Lovelace card that hides other cards behind a dropdown toggle
The card is broken, e. g.
offen 12:25PM - 08 Aug 25 UTC
geschlossen 01:15PM - 08 Aug 25 UTC
### Checklist
- [x] I have updated to the latest available Home Assistant versi… on.
- [x] I have cleared the cache of my browser.
- [x] I have tried a different browser to see if it is related to my browser.
- [ ] I have tried reproducing the issue in [safe mode](https://www.home-assistant.io/blog/2023/11/01/release-202311/#restarting-into-safe-mode) to rule out problems with unsupported custom resources.
### Describe the issue you are experiencing
Since likely 2025.7 a history stats graph is first shown wrong or not at all. It is shown correctly
- in dashboard edit mode
- once a sensor legend is clicked (disabled) and enabled again
### Describe the behavior you expected
Shown as usual
### Steps to reproduce the issue
1. Update to 2025.7
2. Check history-stats graphs
### What version of Home Assistant Core has the issue?
core-2025.7.4
### What was the last working version of Home Assistant Core?
_No response_
### In which browser are you experiencing the issue?
All browsers and apps
### Which operating system are you using to run this browser?
_No response_
### State of relevant entities
```txt
```
### Problem-relevant frontend configuration
```yaml
```
### JavaScript errors shown in your browser console/inspector
```txt
```
### Additional information
Example

Default view

Disabled

Re-enabled

More crazy examples of default views

I tried to PM @rossmcmillan92 here but never got a reply.
There is no active fork.
Dead. Right?
dcapslock
(Darryn Capes-Davis)
August 20, 2025, 10:38pm
4
e-raser:
There is no active fork.
Dead. Right?
Yes. Suggest you migrate to lovelace-expander-card (MelleD fork) which is active and deals with the issue. The core issue is that some history card does not deal with zero width (which a card with display: none has) so the workaround required is that the custom card uses home assistant conditional card which adds/removes elements from DOM rather than just hiding them.
1 Like
I had a look at that card once some while ago. Not sure if it is a pretty close to “drop-in replacement” or needs a lot of migration work.
First thought is if it can be
a) configured to only expand per default for desktop screens only (or never or always)
b) styled like collapsable-card can (even natively) as I mainly use collapsable cards for main/outer cards like
type: custom:collapsable-cards
title: ⚙️ HA & Hardware
defaultOpen: desktop-only
buttonStyle: "font-size: 26px; background-color: var(--divider-color);"
cards:
...
type: custom:collapsable-cards
title: 🆕 Updates
defaultOpen: desktop-only
buttonStyle: "font-size: x-large;"
cards:
...
dcapslock
(Darryn Capes-Davis)
August 22, 2025, 11:01am
6
Up to you I guess. You can put in FR on the maintained expander-card. If the FR are included then that would be a good outcome for the community. For me I did not use those features of collapsable card so it was an easy migration.
Migrated to expander-card. Actively maintained, besides few optical glitches/differences almost same output.
1 Like