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 
I’m on the latest version.
Core
2025.5.1
Supervisor
2025.04.1
Operating System
15.2
Frontend
20250509.0
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
Yes, it’s all there and at the top.
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
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 
Btw., is it possible to use Entity IDs for notify_device and excluded sensors? E.g. “device_tracker.smartphone_1” instead of “3b5c1f81c4df69424b1f91d09be1f9e5”
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
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
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
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
HI, thanks for your great blue print.
I have two questions.
Is there a way to add Messages to telegram addional to HA notifications?
and is there a way to exluce a whole integration? I’m using battery+ and all devices get double notifications
@Blacky I have added the ability to exclude Hidden entities, this is useful when using the integration Battery Notes which has the option to hide the default battery entities and only show Battery+ one. See below
Hidden Entities Included
Hidden Entities Excluded
you can find my forked gitst here: low-battery-notifications-and-actions.yaml · GitHub
If you could add this support to your version it would be really appreciated.
Andy
Thanks Andy, I will think about it. I have recently added the ability to exclude entities using labels. You can apply a label to all you hidden batteries and then exclude them all. This was done for Battery+ as it duplicates the entities.
Blacky
@Blacky Thanks, yeah, I Know, but it requires you to remember to add the label each time you add a new device :), Using the builtin Hide option works automatically, plus when you have loads of batteries to deal with it becomes an annoyance.
I don’t use battery+ but do they get hidden automatically? Or do you have to hide them?
Blacky
What option?
using in configuration.yaml
battery_notes:
hide_battery: true
O okay. Let me think about this.
Thanks
Blacky
1 Like