From c4ee09ef464f3cd30ddefd8609cb3a81b2db00fb Mon Sep 17 00:00:00 2001 From: Troon Date: Mon, 13 Jul 2020 13:22:08 +0100 Subject: [PATCH] Reworded section on pulling attributes from JSON (#13972) Improved English; original probably written by someone using second language which is far more impressive than me slightly tweaking it in my first language! --- source/_integrations/rest.markdown | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/source/_integrations/rest.markdown b/source/_integrations/rest.markdown index c5e130b79a8..361f81dfb06 100644 --- a/source/_integrations/rest.markdown +++ b/source/_integrations/rest.markdown @@ -320,7 +320,7 @@ sensor: ``` {% endraw %} -This configuration shows how to extract multiple values from a dictionary with `json_attributes` and `template`. It helps you to avoid flooding the REST service and only ask once the results and separate them in multiple templates referring to it. (No need for a specific state on the REST sensor and it's default state will be the full JSON value which will be longer than the 255 max length. It's why we'll used a static value) +This configuration shows how to extract multiple values from a dictionary with `json_attributes` and `template`. This avoids flooding the REST service by only requesting the result once, then creating multiple attributes from that single result using templates. By default, the sensor state would be set to the full JSON — here, that would exceed the 255-character maximum allowed length for the state, so we override that default by using `value_template` to set a static value of `OK`. {% raw %} ```json