Julien Roy

Can you provide the full history (without hidden states) and provide the history you want to be displayed based on your configuration? Is it working with non multiple card ?

Yes, to me the behaviour is correct and squashing the 2 open state will lead to a invalid state ... If OK for you, you can close the issue

@Kanecaine can we close the issue ?

Hello, i don't undestand what's wrong here. As I can see, the attributes configured for `sensor.asher_ace_last_pumping` and `sensor.asher_ace_last_change` are displayed. What is missing ?

Any updates?

Hello, thanks for reporting feature requests. Can you create another feature request for `adding a filter by date option` to have separate tickets. Can you please add some context for...

According to the [transmission integration documentation](https://www.home-assistant.io/integrations/transmission/#services)page: > It can either be a URL (HTTP, HTTPS or FTP), magnet link or a local file (make sure that the path is white...

Hello @trisweb, I didn't have the issue on my instance (HA 2024.4.4). Did you have the issue before ? The card use the first entity as entity to render the...

Try to add `custom_logs: true` in your entity ```yaml type: custom:multiple-logbook-card desc: true entities: - entity: switch.accesscontroller_relay_7 custom_logs: true hidden_state: - unavailable state_map: - label: aperto value: 'on' - label:...

Not sure about the fix but seems that this yaml configuration is valid ```yaml binary_sensor: - platform: gpio pin: number: GPIO19 inverted: true mode: input: true pullup: true name: Volume...