You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: readme.md
+3-1Lines changed: 3 additions & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -798,7 +798,7 @@ Remember you can add a `console.log(the_object_you_want_to_inspect)` and see its
798
798
- `path: string;` The path of the current function
799
799
- `css_vars: HATheme;` The colors set by the active Home Assistant theme (see #ha_theme)
800
800
801
-
#### Only iniside entities
801
+
#### Only inside entities
802
802
803
803
- `xs: Date[];` Array of timestamps
804
804
- `ys: YValue[];` Array of values of the sensor/attribute/statistic
@@ -813,6 +813,8 @@ Remember you can add a `console.log(the_object_you_want_to_inspect)` and see its
813
813
- Functions cannot return functions for performance reasons. (feature request if you need this)
814
814
- Defaults are not applied to the subelements returned by a function. (feature request if you need this)
815
815
- You can get other values from the yaml with the `getFromConfig` parameter, but if they are functions they need to be defined before.
816
+
- Any function which uses the result of a filter, needs to be placed in the YAML below the filter. For instance, `name: $ex ys.at(-1)` where the filter is modifying `ys`.
817
+
- The same is true of consecutive filters - order matters. This is due to the fact that filters are translated internally to function calls, executed in the order they are parsed.
0 commit comments