This piston is triggered via web request from Blue Iris. It triggers via local endpoint, but it does not perform the same way it does when tested using the "test' button below the piston. The logs show the same information when triggered via endpoint or when testing the piston via "test" button. What isn't working is that the http request isn't being seen by Blue Iris. The rest of the piston works just fine.
I also tried using a timer to run the piston every few minutes... just as a test. It works perfectly.
What am I missing? Why won't this piston run properly via local endpoint?
UPDATE: This issue was with the triggers in Blue Iris. Blue Iris was seeing the external trigger from webCoRE while the motion trigger was still active, so it considered it a re-trigger and did not send it. Setting the camera to alert on re-triggers solved the issue.
It's triggered via local endpoint. It's an http request that triggers it.
I have a bunch of similar pistons that work perfectly. There's one for the mailbox, one for the shed, and one for the gate. They all work essentially the same and I have no issues with any of those. It's just this one that's giving me problems.
To the OP, can I assume that the web request on line 28 is a blue iris URL?
Do the other similar pistons you have also make a similar web request?
Without seeing logs, I’m wondering if you add a 1 or 2 second delay prior to turning on switch 24. Although it appears the piston is written to run synchronously, I’m wondering if the turn on command is negating the first condition under certain conditions. Quite unlikely, but something I would try anyway.
Also, do you need automatic piston state disabled? I don’t believe I’ve ever disabled that - are you trying to set piston states manually?
Finally, if line 38 is running, but line 28 is not, I would also try moving the web request into the same action list as line 38. You should be able to make a web request under Unknown Device 27’s action list.
I've actually abandoned the web request in this piston after finding a resolution in Blue Iris. The new piston just receives a web request from BI and triggers Echo Speaks. That all works perfectly.
To answer you questions... yes, the web request is to Blue Iris. Yes, I have other pistons that are almost identical that work perfectly. There's one that alerts if the gate or shed door open. There's one when mail arrives. They all use web requests to BI. I even trigger profile changes in BI using web request.
The only real difference with this piston is the type of camera it triggers. All of the others are Amcrest, and this one is a Reolink. Matter of fact, if I change the URL to trigger an Amcrest camera, it works perfectly.
The issue that prompted this strange piston is that the Reolink doorbell camera is using ONVIF events to tell Blue Iris that the doorbell was pressed. It uses "changed" as a state to trigger the ONVIF event. The problem is that it sees pressed and unpressed as changes, so the alert is being sent twice. I managed to set a timer in Blue Iris that ignores alerts sent within the same interval.
Anyhow, thanks for the help. I'd still be interested to know why it's not working, and I might rewrite the piston the way it was and post the logs simoly out of curiosity.
