Delay/Issues with camera alert disablement via API

64 views
Skip to first unread message

Brian Wilson

unread,
Mar 8, 2021, 8:39:44 AM3/8/21
to Camect User Forum

I continue to experience an issue when disabling my cameras from alerting (via Hubitat camect integration: https://github.com/bdwilson/hubitat/tree/master/Camect).  As you can see below, I disabled alerts on both garage cameras prior to leaving the house.  The disablement worked fine on one camera, but didn't on the other.  It's not a fluke because it happens to the same camera each time.  Below you can see the time when the alert fired as well as the API call-backs from Camect showing when the disable and enable alerting API calls were made.  Any ideas? Perhaps a bug?

Garage Back (e10bd60be885e2c5xxxx) saw a car at 07:59:03.   But Garage Front Did not.  

2021-03-08 08:00:33.756 am Unhandled event: [type:alert_enabled, cam_id:14dd5793c43e59aexxxx, cam_name:Garage Front]

2021-03-08 08:00:33.622 am Unhandled event: [type:alert_enabled, cam_id:e10bd60be885e2c5xxxx, cam_name:Garage Back]

2021-03-08 07:58:10.384 am Unhandled event: [type:alert_disabled, cam_id:e10bd60be885e2c5xxxx, cam_name:Garage Back]

2021-03-08 07:58:10.247 am Unhandled event: [type:alert_disabled, cam_id:14dd5793c43e59aexxxx, cam_name:Garage Front]

2021-03-08 07:56:54.025 am Unhandled event: [type:alert_enabled, cam_id:14dd5793c43e59aexxxx, cam_name:Garage Front]

2021-03-08 07:56:53.566 am Unhandled event: [type:alert_enabled, cam_id:e10bd60be885e2c5xxxx, cam_name:Garage Back]

2021-03-08 07:54:51.098 am Unhandled event: [type:alert_disabled, cam_id:e10bd60be885e2c5xxxx, cam_name:Garage Back]

2021-03-08 07:54:50.879 am Unhandled event: [type:alert_disabled, cam_id:14dd5793c43e59aexxxx, cam_name:Garage Front]

FlyingDiver

unread,
Mar 8, 2021, 6:17:59 PM3/8/21
to Camect User Forum, Brian Wilson
Are you using the same reason code for both cameras?

Brian Wilson

unread,
Mar 9, 2021, 8:14:51 AM3/9/21
to Camect User Forum, Brian Wilson
My understanding was that the reason code only needed to be unique per camera (if they are being disabled by 2 different calls vs one).   In this case, the reason code for each camera was the same. 

Hoping Arup can confirm if the reason codes need to be unique per camera as I thought both the reason and camera needed to match to enable a disabled camera, and not just the reason.  

CamectChao

unread,
Mar 10, 2021, 3:58:36 AM3/10/21
to Camect User Forum, Brian Wilson
There is no need for the reason to be unique across cameras.
Based on what you said, I think it's likely caused by the current implementation only check the alert state (i.e whether it's disabled) when the motion starts.
For your case, I think "Garage Back" sees the motion before "Garage Front" and the alert is disabled in between.
I'll make some change to better handle such cases.

Brian Wilson

unread,
Mar 10, 2021, 8:47:43 AM3/10/21
to Camect User Forum, CamectChao, Brian Wilson
Thank you.  The back camera definitely is the first camera to see me when I leave, but given that a disable happened at 7:58:10 and the alert was triggered at 7:59:03 - almost a minute later, I was assuming the disable would have come before motion was detected, but I guess I'm not sure how long that process takes and, like you mention, if disable happens at the front end it may be missed.  Thanks for looking at this, Chao! 

Brian

Reply all
Reply to author
Forward
0 new messages