$fn inside fn in filter (syntax - don't know how)

[luissimoes]

I know (thanks to David) how to have indicators.... but now I have in a filter section the following:

   filters:
    - filter: i < xs.length - 1
      - delta
      - fn: |
          ({ys,xs,hass}) => ({
            xs: [...xs, new Date().setHours(0,0,0)],
            ys: [...ys, hass.states['sensor.from_netz_daily'].state],
          })

To have the indicator I need to have a line like this for the last value i.e. the now that is in the -fn in the filter

     fn: $fn ({ys, vars}) => {vars.solar = ys.at(-1);}

How do I put this in the section?

      - fn: |
          ({ys,xs,hass, vars}) => ({
            xs: [...xs, new Date().setHours(0,0,0)],
            ys: [...ys, hass.states['sensor.from_netz_daily'].state],
            **_vars: [??????  ]_**
          })

---

I have a workaround, which is to create an entity that is internal only and then use the fn for the value... ie I am basically duplicating the input stream....
but may be there is a more elegant or better solution

thanks

[dbuezas]

Hi again!
Try this:

- fn: |
          ({ys,xs,hass, vars}) => {
              vars.solar = ys.at(-1);
              return {
                xs: [...xs, new Date().setHours(0,0,0)],
                ys: [...ys, hass.states['sensor.from_netz_daily'].state],
              }
          })

Although if you need the hass.states['sensor.from_netz_daily'].state just use it wherever you were about to use the var.
Beware that if you have refresh_interval: auto, the plot won't auto update unless you use entity: sensor.from_netz_daily somewhere.

[luissimoes]

Hi David,
many thanks again.
I had tried something similar and it didn't work (see the screenshots...) - that's why I asked if there is a solution to have it inside the block where we have the new added point calculated

1. with the "internal" sensors that just collect the info for the sole purpose of displayed the indicator (the values are correct i.e.

• 32.53 and 35.11)

2. with the alternative proposed (btw: I removed the last ')' ... )

• the indicator (for the pink value "consumed" shows the at(-1) i.e. from previous week (74...) ... not the last point of the graph --> that's why I thought about bringing it "inside" the calculation.... but don't know how\

S-Shot1

S-Shot2

[dbuezas]

Right, I think you missed my comment at the end of the last answer:

Although if you need the hass.states['sensor.from_netz_daily'].state just use it wherever you were about to use the var.
Beware that if you have refresh_interval: auto, the plot won't auto update unless you use entity: sensor.from_netz_daily somewhere.

That means: don't use a var inside the indicator. Instead, set entity: sensor.from_netz_daily and usevalue: $ex ys.at(-1).

If this doesn't solve it, please post your full yaml inside a code block

```yaml
type: custom:plotly-graph
entities:
  - entity: blah
```

[luissimoes]

Right!!!!!
and then there was light! :-)

So... I did read but "read" something completely different.... (I was using hass.states['sensor.from_netz_daily'].state)...

Just to be sure - here is what I did:

• I still do use an additional entity, which is also called sensor.from_netz_daily..
• it is still type Indicator -
• the value is set with $ex

=> this worked.... is this why you meant? (It was only clear to me when you spelled it all in the last post :-)... sorry!)

Last Q:
is this better than to create this?
In the sense, that is more efficient? I suppose so, because now I have only 2 entities (one the "real one) and the other the "indicator", as in the alternative I have 3....

Or its the same?

- entity: sensor.to_netz_weekly internal: true fn: $fn ({ys, vars}) => {vars.sold = ys.at(-1);}

thanks!!!!

[dbuezas]

Haha, no problem. It often happens that text only makes sense on the second read :)

=> this worked.... is this why you meant? (setting value directly using $ex ys.at(-1)

yes!

is this better than to create this? (another internal entity)

Oh, a perfectionist! 🚀 Yes, that's better. Performance wise you won't be able to measure the difference, but it makes sense to have an entity and use it directly, it makes little sense to fetch it in an internal one just to use it in another one (except if you are composing multiple entities into one trace).

Feel free to post your entire yaml and I can tell you if there's any extra trick to clean it up even more

[luissimoes]

man you are really good! thanks for the offer.... :-)
here is what I have
(the graph looks like this, but I am looking for making the "sold" values (blue) as negative values stacked to the other ones
--> thought about adding a filter that multiplies the y-values by -1)... again wondering if this efficient or of there is a better way)

[dbuezas]

Sure, no problem. I'll take a look after work.
btw, please fix the code block using the format I wrote down here #368 (reply in thread)

[netweaver1970]

Yey! I know who to ping if I ever get into solar 😂

I think >90% of all people using plotly on HA use it for environment (temp/hum etc) or for energy related stuff. THE major usecases ...
It almost deserves a real masterclass video on it, if someone is video inclined...