Alerts working for all camera except one - stymied

Post Reply
bluenoob
Posts: 2
Joined: Fri Jun 25, 2021 3:43 pm

Alerts working for all camera except one - stymied

Post by bluenoob »

I'm hoping someone can help with some things to try / investigate.

I have a few cameras, and using them to send a curl command to my Pushover account. The alerts work perfectly, and really fast.

I added a new camera (a doorbell camera from Amcrest). I have it all set up in Blue Iris, and can see the video perfectly.

Here's the problem. The camera will trigger, and send the pictures to DeepStack. DS will return with a hit, and record a short clip of the motion (buffered and all). I can see in the alerts filter from BI that the camera tripped, found a person, and recorded it. It also shows the icons saying it found a person, and a percentage of certainty.

There is where the problem is. For all other cameras, I have a curl command in the alert and it sends a Pushover notice. This camera does not, and I'm at my wits end with things to try or investigate.

Here is the alert curl command (again, this works in 5 other cameras, just not the last one):

https://api.pushover.net/1/messages.json -s --form-string "token=YOUR_TOKEN_HERE" --form-string "user=YOUR_USER_KEY_HERE" --form-string "message=<b>&CAM</b> &MEMO" --form-string "html=1" --form-string "device=YOUR_PUSHOVER_DEVICE_NAME(S)_HERE" --form-string "sound=YOUR_PUSHOVER_SOUND_HERE" --form-string "url_title=Stream Alert via UI3" --form-string "url=&WAN/ui3.htm?rec=&ALERT_DB&maximize=1" -F "attachment=@D:\Blue Iris\Alerts\&ALERT_PATH"

Hoping for some help....
User avatar
YrbkMgr
Posts: 587
Joined: Sun Nov 24, 2019 12:56 am
Location: Chicagoland

Re: Alerts working for all camera except one - stymied

Post by YrbkMgr »

I don't know squat about curl commands, and you clearly have competency, but this caught my eye:
DS will return with a hit, and record a short clip of the motion
DS manages whether or not a motion trigger produces the alert. DS is there as a cop to determine if motion that occurs after the triggering event, satisfies the criteria in AI settings. Then it's a "go / no go" decision - confirmed or cancelled. It has nothing to do with what is recorded.

I know it doesn't address your main issue, I'm just pointing it out. That said, the json link/string you provided shows the error:
secret "invalid"
errors
0 "secret must be supplied; did you mean to do a POST?"
status 0
request "6856d0d7-db20-44c6-a030-86b545eee0d1"
It means nothing to me, but maybe it's a clue on what's going wrong.
  • "Whenever I take something apart to fix it and put it back together again, I end up with like six really important looking pieces left over" -Tim Allen
  • If you know what your after, you'll recognize it when you see it.
Post Reply