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
Remember you can add a `console.log(the_object_you_want_to_inspect)` and see its content in the devTools console.
700
+
701
+
#### Everywhere:
702
+
703
+
- `getFromConfig: (path) => value;` Pass a path (e.g `entities.0.name`) and get back its value
704
+
- `hass: HomeAssistant object;` For example: `hass.states["sensor.garden_temperature"].state` to get its current state
705
+
- `vars: Record<string, any>;` You can communicate between functions with this. E.g `vars.temperatures = ys`
706
+
- `path: string;` The path of the current function
707
+
- `css_vars: HATheme;` The colors set by the active Home Assistant theme (see #ha_theme)
708
+
709
+
#### Only iniside entities
710
+
711
+
- `xs: Date[];` Array of timestamps
712
+
- `ys: YValue[];` Array of values of the sensor/attribute/statistic
713
+
- `statistics: StatisticValue[];` Array of statistics objects
714
+
- `states: HassEntity[];` Array of state objects
715
+
- `meta: HassEntity["attributes"];` The current attributes of the sensor
716
+
691
717
#### Gotchas
692
718
693
719
- The following entity attributes are required for fetching, so if another function needs the entity data it needs to be declared below them. `entity`,`attribute`,`offset`,`statistic`,`period`
@@ -791,7 +817,13 @@ Anything from https://plotly.com/javascript/reference/layout/.
0 commit comments