Ring Doorbell piston not working

#1

1) Give a description of the problem
Almost any event from my Ring Doorbell causes my piston to execute as if the button was pressed. It’s not any motion but many motions that are fired. Pushing the button works too but not solely.

2) What is the expected behavior?
When someone pushes the button to ring the doorbell, it lets us know that the button was pressed using Alexa (Amazon Echo).

3) What is happening/not happening?
The ring doorbell is causing this piston to run when there is motion and not only when someone pushes the button to ring the doorbell.

4) Post a Green Snapshot of the piston!

image
image.png796×233 5.66 KB

5) Attach any logs (From ST IDE and by turning logging level to Full)
[2019-01-05 5:13:45.709 PM EST
DEVICE motion active Doorbell detected motion.

#2

Make sure you have the correct device type in ST. I run virtually the same piston and it works fine. Not sure why yours shows button #1. is there more than one button on your device? Here is my piston:

Doorbell
Doorbell.png1178×689 99.8 KB

#3

Any chance you created another piston or a custom alert in smart home monitor?

#4

I looked again. There is an option for button number but I just left it on ‘Any’

#5

I defaulted to “any” but changed it to try to get it working correctly.

Thanks for looking at it.

#6

It’s interesting you ask that. I have it set up in the alexa app but have now deleted it from there as I don’t need it in alexa. I just want alexa to speak when someone rings the doorbell. I am using Echo Speaks which is working in this and other pistons but my event is the problem here.

I will try some other tweaks.

Thanks

#7

Ok, I looked at the Alexa app and it had a routine to announce from the doorbell that I thought I disabled. The reason I wanted to use a piston is that Alexa only detects motion and won’t recognize the push of the button.

I have now deleted the doorbell and routine from alexa and it is working expected.

Thank you for confirming my code should work and for suggesting looking at other locations.

#8

Glad you figured it out. Sometimes is those sideways hints that help us debug. :smiley: