Why the heck: do automations completely fail if one google home can't be contacted via node red?

Archive Month of "What the heck?!" (2020)
1

If you have a google home that goes out of commission, then the entire automation node is stopped

For example: if you send a volume adjustment to all speakers (say for an alert), and one speaker has an issue, that entire automation fails and the alert is not sent to the rest of the speakers and that automation node is stopped. This has forced me to write all of my automations to separately address each speaker with instructions so that if one speaker fails only that automation path stops. When I add a speaker I need to update all my automations to include that speaker. An option to ignore failed calls and still send to rest of speakers and continue the automation would be wonderful.

As an added bonus - why the heck can’t we mark an automation as synchronous? I have delays all over in my automations to wait for the speaker to adjust its volume or finish speaking a message. Would be wonderful to have a call and wait option so I can make sure that the message is finished before the automation continues.

2

This forum and “What the heck?!” is about Home Assistant, not Node-RED.

Please raise an issue and your concerns with those projects :+1:

3

I tried to raise it with node red and they said this was because of HA and closed it, which is why I saw this as an opportunity to raise it here.

4

Home Assistant has no control over the nodes and automations running in Node-RED. Node-RED is a client to Home Assistant.

I’m sorry, but there is nothing Home Assistant can do about this. The only resources you can go is:

Nothing in our code-base is has anything to do with Node-RED.