Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Wildcards not replaced inside notification "data" field #915

Open
f18m opened this issue Mar 25, 2024 · 3 comments
Open

Wildcards not replaced inside notification "data" field #915

f18m opened this issue Mar 25, 2024 · 3 comments
Labels
bug Something isn't working work-in-progress

Comments

@f18m
Copy link

f18m commented Mar 25, 2024

Alarmo Version

v1.9.15

HA Version

2024.3.3

Bug description

When creating a notification in Alarmo, I noticed that the following YAML code does not produce the intended message:

service: notify.myemail
data:
  message: Alarm has been triggered
  title: Alarm has been triggered
  target: myemail@gmail.com
  data:
    html: |
      <h1>Alarm was triggered!!!</h1>
      <p>Caused by {{open_sensors}}</p>

The "notify.myemail" service is a simple SMTP notifier that I setup using the standard home assistant SMTP component (https://www.home-assistant.io/integrations/smtp/).
Indeed what happens is that the email I receive contains the literal "{{open_sensors}}" un-expanded in the email body.
The reason seems to be that the wildcards are expanded inside the "message" and "title" but not in the "data" field.

Can you confirm that?

Steps to reproduce

  1. setup SMTP integration
  2. create a notification in Alarmo with a custom "data.html" body including an Alarmo wildcard
  3. hit the "try" button in Alarmo to trigger the notification or, just trigger the condition that will trigger the notification to be sent (in my case: when the alarm fires)

Relevant log output

No response

@f18m f18m added the bug Something isn't working label Mar 25, 2024
Copy link

This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 7 days

@github-actions github-actions bot added the Stale label Apr 25, 2024
@f18m
Copy link
Author

f18m commented Apr 30, 2024

adding comment to avoid closure

@github-actions github-actions bot removed the Stale label May 1, 2024
@nielsfaber
Copy link
Owner

This should be fixed in the v1.10.1 release.
Please update your Alarmo installation and try it out.
You can close the issue if it works OK for you now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working work-in-progress
Projects
None yet
Development

No branches or pull requests

2 participants