Jérôme W.

No, `entity.state` contains the state of the entity associated to the button. No need to reference it by name.

For that, the solution is in this [comment](https://github.com/custom-cards/button-card/issues/389#issuecomment-717125073). Use a template also for the nested card and it will work.

I won't make an exception only for state, sorry.

That is with `state_display` and it works similarly to `label` and `name`. I don't know what you want more.

Ok, `state_display` is not available to override in the `state` array. I'll add this. But you can always do this instead: ```yaml button_card_templates: err_handling: state_display: '[[[ return entity.state === "unavailable"...

Actually, `state_display` is supported in `state` if you download the latest beta version of button-card. I forgot that :D

Use `show_state: true`and you'll get what you want. No need for javascript templates.

Ok, I see. The timer is not the main entity. One easy way to do this is to embed a button-card with the timer as entity in a custom_field on...

You should find a way to do this in this comment: https://github.com/custom-cards/button-card/issues/314#issuecomment-616258963

Yes, use navigate as the action and call your service like in the example linked in any other yaml key.