🪫 Low Battery Notifications & Actions

@dantist

Okay, what version of HA are you on? If you are on an old version if possible could you please update your HA and try again.

Blacky :grinning:

I’m on the latest version.

Core
2025.5.1
Supervisor
2025.04.1
Operating System
15.2
Frontend
20250509.0

@dantist

Okay, do you have this in your configuration.yaml file?

Check each letter and character. Is it at the top of the file?

If not move it to the top and restart HA.

default_config:

group: !include groups.yaml
automation: !include automations.yaml
script: !include scripts.yaml
scene: !include scenes.yaml

Blacky :grinning:

Yes, it’s all there and at the top.

@dantist

The last thing in this order, is to remove the blueprint, reboot (not restart) your HA, install the blueprint again and reboot (not restart) your HA. Try the same steps as above and this time when you save it this time change the file name to something different. If is still not working then something must be wrong with your HA or there is a bug in HA and you will have to report it to them.

Blacky :grinning:

I got it working now. So although the configuration.yaml states
automation: !include_dir_merge_list automation/
the automation is written to automations.yaml. After copying the output to the correct folder and file it’s working :+1:

Btw., is it possible to use Entity IDs for notify_device and excluded sensors? E.g. “device_tracker.smartphone_1” instead of “3b5c1f81c4df69424b1f91d09be1f9e5”

@dantist

Nice one glad you got it working now. You will need to make sure you look at groups, scripts and scenes like I shown above to.

It is best to just use the input selectors I have.

Blacky :grinning:

1 Like

Maybe recent update changed minimum HA version?
Running 2024.7 and get this error:

same error with no trigger selected, also with time trigger for 09:00.
YAML view


Right after installing the blueprint the watchman freaks out and alerts me about missing services and entites in the blueprint file. This is not a missing entity within an automation created by the blueprint, but the blueprint.yaml itself.

What to do?

HAOS Version 2025.05.1

@MarkusBiggus

This is because your on an old version of HA. In version 2.6 we updated the blueprint to follow HA coding practices to align with their roadmap. If you can update HA then it will work.

Blacky :grinning:

@vghgvbh

There is nothing wrong with the blueprint and you don’t need to do anything. It is just pointing out that it uses the mobile app to notify you and it also allows you to use the todo integration developed and managed by HA. You can simply ignore these watchmans reports… your all good.

Blacky :grinning: