Searching for a PLEG "ghost"

Plugins & Plugin Development Program Logic (PLEG)
1

I don’t think I’m alone in the PLEG community in having an unexpected event to occur, in this case it’s always the same LED Hall light which could be triggered by either one of two AEON 3 in 1’s.
Wifie has been very supportive but it is starting to cause some anxiety now and I’d like to sort this out.

Our moggie is the chief suspect, but I’m not sure of how many times the LED is actually being triggered, so I’m trying to isolate the cause, what is bugging me is that all I want to do is to monitor only one LED over a 24 hour period, without resorting to data mining or searching through 24 hours of logs and the ever expanding amount of devices I now have.

I’m not sure how many times per night this LED is being triggered, so I want to monitor it over a 24 hour period, simply…

Has anyone any suggestions as to how I could achieve this simply before I go ghost hunting in the PLEG ???

2

That sounds to me as if you have a motion sensor which triggers unexpectedly ? Especially if you have a Aeon 4 in 1, they have atendency to have false triggers. So I think if it is a motion sensor there is a good chance it is actually the motion sensor itself causing the problem. There is a thread here about Aeon and the false trigger problem

3

Try putting a notification on the device itself, select “Device is turned on” and it will send you an email (or text) each time it was turned on.

@mikee123 is right, those sensors are twitchy. You will want to do the same thing with them, add a notification when “a sensor is tripped”

that should tell you how often and which of the sensors is firing. keep your cat in bed with you while testing!

4

There is also the LOG command where you can set the log for a PLEG device to it’s own log file.
You should have a USB stick to log this …
You can much more easily see what is happening with just this PLEG for tracking down problems.

5

Thanks guy’s, I’m fully aware of the problems AEON’s have, that is skirting around the issue.
I’m sure some conditional logic using other triggers and conditions would trap this.

The issue is how many times is it triggering and what time as we’re not convinced they are “twitchy”.

Bulldog, I’m not sure how to set this up, similarly Richard, I’m not sure how to setup logging, are either of these possible solutions documented anywhere?

6

Richard can help with the PLEG logs, but you can set your device to notify just like the attachment

7

Perhaps asks that LED settings get added to the EventWatcher project.

Service ID: urn:micasaverde-com:serviceId:SceneControllerLED1
Variable: LightSettings
Value: 13 (sample)

8

Thanks for the suggestions, I finally got around to using the Notifications Tab, never new it was there.

The sensors fire every 2 hours, oddly each has a 2 minute interval, between.

ie
motion1 0100
motion2 0102
motion3 0104

then
motion1 0300
motion2 0302
motion3 0304

and so on.

I’m guessing that it has something to do with the sensor wakeup, not sure how the 2 minute interval happens?
Why the sensors are firing every 2 hours has me beat, I have them set as Armed Sensors, would a change to tripped be a solution?

9

That’s one precise moggie!

The 2 minutes might be a result of a polling interval. I believe actual polling is a function of polling interval and # of devices to be polled …
It will not allow multiple devices to be polled at the exact same time.

10

the AEON sensors are somewhat infamous for this kind of behaviour, so you may want to turn off the wake-up.

Try changing their wakeup interval to zero. It still will fire back to Vera but you will no longer be able to update its configuration with vera unless you use the button on the device (you can set it back to wakeup automatically).

You will then need to physically wake it up for any configuration changes after this, so if they are not in a difficult place to access, you may be OK with that.

11

Thanks Richard/Bulldogwell, I’ll try changing config to no wakeup, there easily accessible so I don’t see a problem if I need to wake them up manually.

Motion2 and Motion3 are located on a waist high cupboard so the beam isn’t directed to the floor, so I knew it couldn’t be the cat.

One last question, should the sensors be set up to fire or just detect motion?

12

sorry, by “fire” i mean “signal tripped”

you have to disregard my now American colloquialisms i’ve picked up too

let us know how it works out with the wake up settings.

13

Just to clarify, when I add a AEON 4 in 1, I have the choice of adding it as the following triggers in PLEG:

  1. a sensor (door/window/motion) is tripped.
  2. a armed sensor is tripped.
  3. Battery level goes below.

Should the trigger be set to 1 or 2? Actually, I’ve always wondered about why the difference, perhaps there isn;t one?

14

[quote=“zedrally, post:13, topic:180283”]1. a sensor (door/window/motion) is tripped.
2. a armed sensor is tripped.[/quote]

Armed is a software setting in Vera.

You have the option to toggle the ‘armed’ status of sensors and include that in your logic. For example, you may only want to trigger motion events in the evening. You can create a scene that ‘arms’ all of the sensors you want to activate in the evening. Then you can trigger other scenes or notifications based on that armed status. When you disarm them (in the morning) they will not trigger those scenes or notifications.