Lovelace - Markdown card - sensor won't show its state

Configuration Frontend
1

HI,

trying to migrate this regular HA card with sensor:

  hassio_log_tail:
    name: Logtail
    icon: mdi:library-books
    entities:
      - sensor.log_tail

to Lovelace

  - type: entities
    title: Logtail
    entities:
      - sensor.log_tail

and/or

  - type: custom:useful-markdown-card
    content: >
       [[ sensor.log_tail ]]

or:

  - type: markdown
    content: >
       [[ sensor.log_tail ]]

the entities card shows correctly but the markdown card errors:

07

using:

  - type: custom:useful-markdown-card
    content: >
       [[ states.sensor.log_tail.state ]]

gives:

02

while dev-state is showing as it should:

59
59843Ă—206 31.1 KB

what should I change to get this showing correctly?

this is the sensor definition:

# https://home-assistant.io/components/sensor.file/
  - platform: file
    file_path: /config/home-assistant.log
    name: Log tail
2

From the other thread about this, shouldn’t it be:

  - type: custom:useful-markdown-card
    content: >
       [[ sensor.log_tail.state ]]

Notice the word state after your entity_id and the lack of the word states before.

Exact same issue you had here:

The key being

3

No, that’s what I tried of course, but it shows:

58

should have mentioned that, sorry

4

in the custom:useful-markdown-card? That doesn’t make sense.

5

it doesn’t, and it didn’t… I tried all combinations both with the custom card or the regular markdown. Except for this:

  - type: custom:useful-markdown-card
    title: Logtail
    content: >
       [[ sensor.log_tail.state ]]

et voilĂ :
24

thank you…

6

weather coordinates? That’s odd… You may have found an issue with the custom card.

EDIT: Nevermind, you’re saying it works.

7

the card now shows my log. that works.

the OWM component doesn’t :wink:

8

not familiar with that.

9

Hi,
with the built in Markdown card the following worked for me:

type: markdown
content: |
  {{ states('sensor.log_tail') }}

Ispired by this post.

2 Likes
10

This whole thread was using the custom:markdown card prior to the existence of Jinja templates in the built in markdown card.

11

What’s your point?

12

That you revived an old outdated thread.

1 Like
13

Old != Outdated.

14

it is when the main topic at hand is about the useful-markdown-card which is deprecated

15

Which it wasnt (exclusively). Discussion Done.

17

Deleting the post doesn’t mean I agree with you.