Hi Alan! the blueprint was made with the goal of controlling each individual appliance, so sorry, but no, I have no plans for that. The blueprint itself is already very articulated but modular. Such an addition would be cool but perhaps āunnecessaryā to most users.
You can still achieve what you want by combining the two automations together: one for the washer and one for the drier.
Instead of announcing that the job was completed straight away when an appliance is done, you could play with the customizable āAction(s) when a job cycle is finishedā section of my blueprint, so that you check if the washer / the dryer is still performing a cycle, and then choose when to announce what, for both.
This could be a raw implementation of your request:
- āAction(s) when a job cycle is finishedā on the dryer automation (YAML code).
Note: Change the entities accordingly as they might have a different name.
actions_job_cycle_ends: # <- This is a custom action. After you've set up the blueprint (follow the documentation), you'll see the "Action(s) when a job cycle is finished" section. This is its corresponding yaml configuration
- if:
- condition: state
entity_id: input_boolean.washing_machine_job_cycle # Your wahing machine job cycle indicator (coming from the other blueprint)
state: 'off'
then:
# Do something. I'll send a notification. This is just an example
- service: notify.mobile_app_<someone's_phone> # For example: send a notification to a phone
data:
title: Washing & Drying Job completed
message: The job was completed on both the dryer and the washing machine
else: []
- āAction(s) when a job cycle is finishedā of the washing machine automation (YAML code).
Note: Change the entities accordingly as they might have a different name.
actions_job_cycle_ends: # <- This is a custom action. After you've set up the blueprint (follow the documentation), you'll see the "Action(s) when a job cycle is finished" section. This is its corresponding yaml configuration
- if:
- condition: state
entity_id: input_boolean.dryer_job_cycle # Your dryer job cycle indicator (coming from the other blueprint)
state: 'off'
then:
# Do something. I'll send a notification. This is just an example.
# Note that this part is the same on both
- service: notify.mobile_app_<someone's_phone> # For example: send a notification to a phone
data:
title: Washing & Drying Job completed
message: The job was completed on both the dryer and the washing machine
else: []
A few notes about this:
I made this example to show you how you could achieve that. Itās actually very straightforward and definitely possible. Please note that there are limitations. The biggest one in my opinion is that you may not have the washer running at all but the notification would mislead you into thinking the opposite. Also, the notification isnāt aware of the past.
Why to add the logic to both, you might ask. Well, what happens if the washer finishes before the dryer? The above conditions would have to be placed on both the automations so that the appliance that ends first is the one that sends the notification.
Please let me know if you need more help. Have a great day 
! I did consider including the creation of helpers through the GUI in the documentation, but that would take longer to explain. Copying and pasting my configuration seemed the more appropriate solution back then. Iāll definitely add that now that I see interest.
NEW BUG DISCOVERED - 07/15/2022 
, sorry for the delay
