Ring Doorbell not verry stable

I've just reworked the flow to use the semaphore node, and added a gif animation below.
In real time it all happens pretty quickly, so I've added a delay node just so that you can see how the flow works.
To trigger the flow, I've reached around the doorway and pressed the doorbell, triggering a motion alert first, followed less than a second later by a ding.
As can be seen, the google home node shows the IP of the device beneath it, so first it sends a motion alert to 192.168.1.11, followed by motion alert to 102.168.1.5, then a ring alert to 192.168.1.5, and finally a ring alert to 192.168.1.11.

Without the queue, all four msg's would arrive at the google home node almost together, which creates chaos!

There is an example flow of node-red-contrib-semaphore in this post, courtesy of @Colin