NetworkMonitor / Presence Info trigger?

[gReatAutomation]

I have the networkmonitor driver installed to monitor various thinks, including if my camera's HTTP interface is accessible. Sometimes my cameras go offline for whatever reason. No triggers for these at all. I saw these triggered events in System->Monitor-Event Triggers

Not sure what these are for...

[Dean Roddey]

Those are the triggers for the camera going off line. They are presence triggers from the network monitor driver for Camera08, first with a type of exit and then with a type of enter (i.e. it exited the network and later re-entered.)

[gReatAutomation]

Thanks that is helpful to know and not readily apparent.

[Dean Roddey]

You can read about the standard event triggers and what they contain here:

https://www.charmedquark.com/Web2/CQCDoc...TriggerFmt

[gReatAutomation]

Thanks. I;ve read that before. Is there a matrix that lists what drivers support what triggers or would that be in each drivers' help file?

[Dean Roddey]

Well, the standard ones are mostly supported in conjunction with 'device classes'. Any device that supports the Security device class has to send any triggers defined by that class.

https://www.charmedquark.com/Web2/CQCDoc...=/Overview

Anything that supports the Lighting device class has to send the lighting load ones. Anything that supports the Locks device class has to send the locks ones. Anything that supports the Motion device class has to send motions ones.

The odd men out are User Action triggers, which are arbitrary and defined by each driver (though some device classes may require that drivers that implement it send out a user action.) For instance drivers that implement the Scene Controller device class should send out user action commands to report scenes being activated.

And there's no device class currently that encompasses presence type triggers. So that would be documented in the drivers that send them. I think the network monitor may be the only one.

Mostly though, when you look at a driver's docs and see it implements V2 device classes, that will tell you what standard triggers it will send.

In some cases, where the can be a lot of them, the class will require that the driver allow you to selectively enable them if there can be large numbers. V2 compliant devices like an Elk or Omni only will do that since they can have large numbers of potential fields that could send triggers (lights, security zones, and motion sensors) and you may not want to react to all of them.

[gReatAutomation]

I think the network monitor may be the only one.

I can see the NetworkMonitor sending out triggers. I have no triggers set to any driver fields and am only trying to relay on the pre-built triggers that you can see in System --> Monitor --> Event Triggers



But, I cannot get any of these to trigger in the action editor or have any indication of triggering in the logs:

[Dean Roddey]

Start simple. Just try the first filter and see if that works. If that works, try the second one and see if it works, then the third by itself. Let's try to divide and conquer and see where the problem is.

[gReatAutomation]

Start simple. Just try the first filter and see if that works. If that works, try the second one and see if it works, then the third by itself. Let's try to divide and conquer and see where the problem is.

I started that and could not get anything to work. I've tried each one individually.

[Dean Roddey]

OK, I'll see what I can figure out.