Closed vikohub closed 11 months ago
I tested with the older version that does not include the \n newlines. It renders without errors in the Template checker. I am still on 2023.10.5 - perhaps that is the cause?
Still, the automations based on the blueprint fail to trigger
Hmm, for whatever reason, when I imported the new versions of the blueprints (the newline versions), they looked like this:
I suppose that this was not intended?
Re-importing them after upgrading to 2013.11.2 yielded this (no backslashes):
"... trigger:
Seemed to pass the template checker, but did not trigger correctly at first try.
After toggling the allowed rank above AND below the current rank a few times, the automation finally started to work.
Seems like the problem was created by copying the code manually from the browser window, and somehow the \n tags got incorporated into the code. The blueprints work fine after re-importing. Closing the issue.
Imported the blueprint and based a couple of test automations on it. None will trigger. If triggered manually, they always go to "else" (i.e. turn off the device), and never choose the "on" option.
When I pasted the blueprint code to the Template checker in HA, I get the error mentioned in the title.
A bit of googling suggests that the \ characters are not escaped correctly in the trigger: section; more specifically at
"- platform: template value_template: "{% if on_attribute == \ "
(the first backslash there is the character number 1930)
Any ideas?