I’m trying to setup some automations to send a Telegram notification on camera motion.
When I try to use the automation editor to define the data section for the service call, it fails to store the secret correctly in automations.yaml.
Example:
Automation editor:
caption: Motion Detected - Garage Back
password: !secret cam_password
url: 'http://example/Streaming/channels/1/picture'
username: admin
what gets saved in automations.yaml (notice the password is empty now)
data:
caption: Motion Detected - Garage Back
password:
url: http://example/Streaming/channels/1/picture
username: admin
service: telegram_bot.send_photo
If I then edit the automations.yaml and add the secret manually it works.
Example:
data:
caption: Motion Detected - Garage Back
password: !secret cam_password
url: http://example/Streaming/channels/1/picture
username: admin
service: telegram_bot.send_photo
But then if I go back to the automations editor and edit any automation using the front end, it will replace/ expose all my secrets with actual passwords in automations.yaml.
Example:
data:
caption: Motion Detected - Garage Back
password: actualPassword
url: http://example/Streaming/channels/1/picture
username: admin
service: telegram_bot.send_photo
Is this a bug? Has anyone else come across this?
Cheers.