# Ring Doorbell not verry stable

**URL:** <https://discourse.nodered.org/t/ring-doorbell-not-verry-stable/4394>\
**Category:** General\
**Created:** [29 October 2018 19:33 UTC](https://discourse.nodered.org/t/ring-doorbell-not-verry-stable/4394 "2018-10-29T19:33:38Z")\
**Posts on this page:** 1\
**Showing post:** 10

<div class="post-metadata">

**Author:** ![Paul-Reed](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/paul-reed/32/66906_2.png) [@Paul-Reed](https://discourse.nodered.org/u/Paul-Reed)\
**Post date:** [30 October 2018 21:55 UTC](https://discourse.nodered.org/t/ring-doorbell-not-verry-stable/4394/10 "2018-10-30T21:55:05Z")

</div>

> [@NickB](#):
>
> @Paul-Reed: How do you exactly implement this queue?

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!

 ![ring3](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/2X/4/4e55c21634304334129dce9ae6ba3805c572c1c8.gif)

There is an example flow of `node-red-contrib-semaphore` [in this post](https://discourse.nodered.org/t/using-node-red-contrib-semaphore/4398/4), courtesy of @Colin

---

_[View the full topic](https://discourse.nodered.org/t/ring-doorbell-not-verry-stable/4394)._