How to make continuous lines for missing values?

[Photelegy]

I have a cover and want to plot the position. But when the cover is not used for some time it goes into sleep mode and doesn't send any values.
How can I tell your plotly-graph-card to connect the line where there are missing values?

Somewhat like in Excel (handling missing data) https://www.nurturetechacademy.in/how-to-handle-missing-data-in-excel-charts/

type: custom:plotly-graph
entities:
  - entity: sensor.rollo_w_sensor_position
    name: West
    line:
      color: yellow
      width: 2
  - entity: sensor.rollo_o_sensor_position
    name: Ost
    line:
      color: cyan
      dash: dot
      width: 2
hours_to_show: 24
refresh_interval: 10
title: Rollo-Position
layout:
  height: 310
  margin:
    t: 70
    l: 50
    r: 5
  dragmode: pan
  showlegend: true
  legend:
    x: 0
    'y': -0.25
    bgcolor: rgba(0,0,0,.7)
    orientation: h
    itemsizing: constant
    font:
      size: 10
  xaxis:
    rangeselector:
      'y': 1.05
      buttons:
        - count: 1
          step: hour
        - count: 2
          step: hour
        - count: 6
          step: hour
        - count: 12
          step: hour
        - count: 1
          step: day
        - count: 2
          step: day
        - count: 7
          step: day
  yaxis:
    fixedrange: true
    range:
      - -0.5
      - 100.5
    title: Position [%]

[dbuezas]

filter the unknown/unavailable with a lambda:

entities:
   - entity: sensor.mysensor
     lambda: |-
        ys => ys.map(y => +y)

The way this works is that when your cover goes to sleep, HomeAssistant will store a datapoint with "unavailable" as its value. Then the + (plus symbol) in the lambda will make javascript try to cast (convert) it to a number, and the javascript will treat the string "unavailable" as "not a number" or NaN. Finally, Plotly should discard those NaNs.

If this doesn't work, let me know and I'll help you filter those more explicitly

[Photelegy]

Wow, thank you!
This works!

[macbih]

David @dbuezas, can you please provide an example of how to achieve the same with the filters function as the lambda function is deprecated since version 3.0.0? Thank you!

[dbuezas]

Please search in the readme. There is the fn filter which is almost like a lambda, and that specific code should be the force_numeric filter

[macbih]

Thank you for your fast response!

In fact I did read the readme but unfortunately I did not succeed in the first run. After playing around with the syntax a bit (honestly, I didn't really know what to do), I did have some success. For reference, the following 2 examples will both do the trick:

1. Uses fn (reusing the lambda function from above):

defaults:
  entity:
    filters:
      - fn: |-
          ({xs, ys}) => {
            return {
              ys: ys.filter(ys=>!Number.isNaN(parseFloat(ys))),
              xs: xs.filter((xs,i)=>!Number.isNaN(parseFloat(ys[i]))),
            };
          }

2. Uses force_numeric (much shorter and therefore more elegant):

defaults:
  entity:
    filters:
      - force_numeric

Thank you yery much for the new filters!

[dbuezas]

🎉 sorry I saw code and thought you were a programmer just being lazy :😂
Happy to hear you like them! If you are missing a specific filter functionality let me know, these are easy to implement