Chargers created from templates with a password *starting* with '#' fail creation both in UI and YAML

[johannrichard]

Description

I failed to create a Zaptec Go charger in the UI (and via YAML). Whatever tried, I got a message that username and password were missing when checking / validating the configuration. Even when adding the password with single quotes, I got the same failure.

Then I realised the password of that account started with a hash (#), changed it to something different and - boom - everything started to work as expected. Did take me quite a bit of time to notice consciously that I had a password stating with a hash and that this could be the culprit. 🤣

Did some tests and can confirm the following:

• Whatever the password and independent if it’s entered in single quotes or not: the configuration check (only) fails if the first character of the password is a '#'
• If the hash is preceded by one or more other characters the error goes away and auth happens as expected

Steps to Reproduce

• add a charger (UI or YAML)
• select a model with username/password (pick Zaptec Go)
• enter 'demo@evcc.io' as username
• enter '#password' as password
• press "validate" or run evcc charger
• UI/CLI throw an error 'cannot create charger type
  'template:zaptec": cannot create charger type 'zaptec': missing user/password credentials‘
• change the password to 'password#' or 'p#assword' and you get the (expected) auth error from Zaptec or successful auth if valid credentials are used

Version

v0.300.2

System

linux/amd64, CET +01:00

[naltatis]

Verified that our input processing works correctly (ui, yaml). The issue here is an error in the Zaptec template. See #26521