From a99f542fcd6faaf0c27822fa05090fb40e4af0d6 Mon Sep 17 00:00:00 2001 From: Jon Date: Mon, 22 Jun 2020 13:44:29 +0100 Subject: [PATCH] Added info re command line sensors being a breaking change (#13754) The fix for command line sensor was promoted as just a bugfix, whereas it is a breaking change. The workaround for the bug was to escape the quote with a backslash, and now the backslash is treated as a character and passed through. --- source/_posts/2020-06-10-release-111.markdown | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/source/_posts/2020-06-10-release-111.markdown b/source/_posts/2020-06-10-release-111.markdown index 6364bdcd0e9..3e52fb5a0df 100644 --- a/source/_posts/2020-06-10-release-111.markdown +++ b/source/_posts/2020-06-10-release-111.markdown @@ -322,6 +322,13 @@ Experiencing issues introduced by this release? Please report them in our [issue Previously it was set after the action that was part of the trigger was done. ([@basnijholt] - [#35671]) ([automation docs]) + + **Command Line Sensors** + + The fix for command line sensors removing quotes with template breaks any sensors where the quote has been escaped using a backslash. + E.g. to work around the previous bug a quote could be added using \" and this must now be replaced with simply " + + (@shenxn - #35559) (command_line docs) ## Farewell to the following