See the README for more information, including information on moving from PG2.

The Release Notes are also available.

If you have issues are requests please check Camect PG3 GitHub Issues to see it has already been listed.

Please confirm you are on the latest version of PG3 which is 3.0.40 right now.

- Work system: eisy / IoX 6.0.4 / PG3x 3.4.13

- Home system: PG3x 3.4.11 works correctly

- Camect plugin version: 3.1.0

- Status in PG3x: Connected

Problem:

Camect alerts are visible in the Camect UI and the PG3x log shows successful updates to IoX, but ISY/IoX programs are not triggering on the work system.

What I already tested:

- Removed and reinstalled the Camect plugin

- Confirmed alerts appear in Camect

- Confirmed PG3x shows node updates such as GPV and ST changing

- PG3x log shows “Successfully set ...” for Camect nodes

- This same setup works at home on PG3x 3.4.11

Why I suspect PG3x:

The main difference I can see is PG3x version:

- Home: 3.4.11 works

- Work: 3.4.13 does not trigger programs

Question:

Has anything changed in PG3x 3.4.13 that could affect Camect node event/status handling in IoX programs after reinstall?

Also, should Camect programs be triggered using STATUS, CONTROL, GPV, or another driver on current versions?

Examples from log:

- Host:update_status: cams=True report=True

- Successfully set 01_004 :: GPV to 1

- Successfully set 01_004 :: GPV to 0

- Successfully set 01_003 :: GPV to 1

- Successfully set 01_003 :: GPV to 0

Thanks.

Kind Regards,

Mike2545

I've currently have Arlo cameras set up and receive notifications via Arlo.  Unfortunately, those notifications are frequently delayed (up to several minutes) which impacts their usefulness.

I can think of several triggers I'd like to set up via cameras - turning on walkway lights based on a person, NOT a branch blowing; automower running in the back yard; etc. - but the timeliness of the triggers would be critical to their usefulness.

Can anyone share the time responses they are seeing with Camect in the wild?

Thanks!

If I use STATUS I get this:

Squirrel Detect - [ID 0154][Parent 0001]

If
        'Camect / Feeder Camera / Feeder Camera animal' Squirrel is True
 
Then
        Resource 'Squirrel Blaster(14)'
        Set 'Notifications / Notification Controller / UD Mobile' Send Message Content 10 Notification ID (ID=10)

 If I use CONTROL the closest I can get is this:

Squirrel Detect - [ID 0154][Parent 0001]

If
        'Camect / Feeder Camera / Feeder Camera animal' is switched Squirrel
 
Then
        Resource 'Squirrel Blaster(14)'
        Set 'Notifications / Notification Controller / UD Mobile' Send Message Content 10 Notification ID (ID=10)
 
This program triggers twice, False>True and True>False

How did you program that?

I believe the alerts are received immediately, what does the short/long polls control?

Thank you

Squirrel Detect - [ID 0154][Parent 0001]

If
        'Camect / Deck / Deck animal' Squirrel is True
     Or 'Camect / Deck / Deck human' Person is True
 
Then
        Set 'Squirrel Blast / Virtual Buttons Controller / Virtual Button 01' Push Button
 
Today I enabled "unknown animal" on the Camect app for this camera.  Shortly there after Camect detected an unknown animal and the above program triggered.  The screen shot of the node is attached. 

Here is the log file entry:

2023-05-04 10:05:53,665 Thread-14  udi_interface      DEBUG    Host:callback: {'type': 'alert', 'desc': 'Deck just saw an unknown animal

I'll PM you the log file

Thank you.

I am running Polygot v3.0.63, and am unable to upgrade the Camect node server from v3.0.8 to v3.0.9 ... When I restart the node server (in an attempt to apply the upgrade), when it first comes back online, v3.0.9 is shown at the top, under current version, then literally a few seconds later it goes back to v3.0.8.

Any insight would be appreciated! Thank you!

Jordan