diff --git a/source/_dashboards/history-graph.markdown b/source/_dashboards/history-graph.markdown index 1a21bca39d7..b1f6bdf0ef8 100644 --- a/source/_dashboards/history-graph.markdown +++ b/source/_dashboards/history-graph.markdown @@ -71,6 +71,11 @@ fit_y_data: description: If true, configured Y-axis bounds would automatically extend (but not shrink) to fit the data. type: boolean default: false +expand_legend: + required: false + description: If true, the legend will show all items initially + type: boolean + default: false {% endconfiguration %} ### Options for entities diff --git a/source/_dashboards/statistics-graph.markdown b/source/_dashboards/statistics-graph.markdown index 8a1cec23152..2860351b433 100644 --- a/source/_dashboards/statistics-graph.markdown +++ b/source/_dashboards/statistics-graph.markdown @@ -87,6 +87,11 @@ fit_y_data: description: If true, configured Y-axis bounds would automatically extend (but not shrink) to fit the data. type: boolean default: false +expand_legend: + required: false + description: If true, the legend will show all items initially + type: boolean + default: false energy_date_selection: required: false description: If true, chart date range will follow the date selected on an `energy-date-selection` card on the same view, similar to energy cards. @@ -94,8 +99,8 @@ energy_date_selection: default: false collection_key: required: false - description: If using `energy_date_selection`, you can set a custom key to match the optional key of an `energy-date-selection` card. This is not typically required, but can be useful if multiple date selection cards are used on the same view. See [energy documentation](/dashboards/energy/#using-multiple-collections). - type: string + description: If using `energy_date_selection`, you can set a custom key to match the optional key of an `energy-date-selection` card. This is not typically required, but can be useful if multiple date selection cards are used on the same view. + type: string {% endconfiguration %} ### Options for entities