@ian.robson, check if you have the right home assistance URL on the page that opens when you click Import Blueprint. The URL address is located at the bottom of the windows and you can edit by clicking the pencil icon at the right.
Everything works perfect but the telegram notification does not start. If I simply delete the word {{entities}} the notification is sent (obviously without the entity names)
Any idea on the possible solution?
The blueprint works perfectly since the results (above in the image) are what I expected, but the telegram notification doesnāt start. The notification starts if I delete the word {{entities}} so the problem is not in the notifiy service either. What should I check for?
After doing some research at the forum I found someone with a problem with the telegram bot similar to the one you are having, and it was related to the fact that the variables in the message had underscore, here is the link to it: Telegram message with variables - #2 by anon43302295
Looking at what you have inside the entities variable I see you have some sensors that have _ in the name, given that you need to replace them with something else, try this {{ entities|replace('_', ' ') }}
Any chance you could add an include list as well as the exclude?
Iād like to track specific entities that fall offline, and I have many many entities that are āunavailableā for other reasons, due to custom components considering that to be a valid state for ānot activeā (e g Google home timers).
No worries if not, just thought it might be a nice addition of easy enough.
If you know how to edit the blueprint:
In the unavailable_entities_notification.yaml file edit the following:
Line 91:
Change {% if state.state == āunavailableā and not state.entity_id in exclude.entity_id %}
To {% if state.state == āunavailableā and state.entity_id in exclude.entity_id %}
You can also replace every word āExcludeā (or āexcludeā¦ā) with the word āIncludeā for less confusion .
The Blueprint now works only with every Included entity!
Is there any way to avoid triggering the automation when thereās no unavailable entity? Iāve tested with unavailable ones and work like a charm, a persistent notification is sent. But when all entities are available the notificaiton got triggered as well.
I have integrated the battery blueprint and works like a charm, not triggered when threshold is not under.
Iāve found the issue: It was introduced with latest commit. I just copied the previous version were entities were shown using commas instead of /n. Hope it helps.
Been using this for a while and itās very helpful, thank you!
I have this in an auto entities dropdown in an admin dashboard, but is there a way to just show devices which have any unavailable entities instead of the entities themselves? Some of these devices have like 10 entities and I donāt need to see them individually because when they go offline itās always all of them.