… and it will stop working the moment the developer fixes this malformed attribute (you don’t include literal string-delimiters in the attribute’s value).
If your template uses in instead of == it will work if the ssid attribute does or does not contain literal double-quotes.
The issue was evident 5 hours ago when I wrote this:
What I didn’t count on was that it was readily visible but your eyes were editing out the double-quotes surrounding the SSID value and only reporting the string between them.