Trouble with PLEG

Developer's Corner General Dev Discussions
1

So I realize this must be user error, but for the life of me I cannot get the functionality I’m looking for. I’ve had PLEG working before, but this scenario is giving me trouble. Basically, I want to send a text notification if either garage door is left open for more than 15 minutes after dark. I have used the Day or Night pluggin, and it is giving me the correct status, as well as the tripped variable of either garage door sensor.

These have been entered into the input tab of PLEG. WHen I look at the variable states in the window, they seem to be what I would expect (i.e. it seems like the inputs are correctly defined). However the following conditions are either not evaluating correctly or the notifications arent working correctly (other motion sensors are firing, so the base functionality is there).

Here is what I have as conditions:
GarageOpen |||| ((GarageS or GarageD) and (not IsDay))
GarageOpenLong |||| GarageOpen; Now > 15:00

The notifications are temporary set up to fire on either condition to aid in debugging, and I dont see anything on the myAlterts tab or sent as an email/text.

Thanks!

Brian

2

Have you looked at the Status command to make sense of what is happening ?

Also:
GarageOpenLong |||| GarageOpen; Now > 15:00

Will always fire 15 minutes after the garage door is open … even if you closed it.
If you want it to only trigger if the garage is still open you should have:

GarageOpenLong |||| GarageOpen and (GarageOpen; Now > 15:00)

3

Thanks for that correction, makes more sense.

Interestingly I was using the tripped variable instead of the status variable for the Garage door sensor. That could be it perhaps, as this morning my wife opened the garage early in the morning and the conditions fired. The last few nights i’d been trying to test it by leaving the door open and nothing was happening despite the fact that the variables seemed to be configured correctly and showing the right values in the input tab.

Perhaps using the tripped variable doesnt generate an event for PLEG to evaluate? Hard to explain but you cant take anything for granted on this platform. =)

bk

4

For the best responses … include a Status or Report with your post so we can see how the PLEG is configured. When we only see fragments … we have to guess how you are using it.

5

Thanks,

Is this what you were asking for? I noticed I can use a USB drive to capture a log, but I dont see any specific Status or Report function for PLEG specifically.

6

If you go to the Control tab you should see the Report and the Status command.

If you do not have the Status command you may want to upgrade to the latest version.

I see you are using device properties and not triggers.
Triggers have a boolean value true or false.
Device properties can have boolean values … but as you see from the current value the ones you are using have numeric values, or strings whose values are numbers.

You should write your first condition:
GarageOpen ((GarageS == 1) or (GarageD == 1)) and (NOT IsDay)

7

Thanks for tracking down two problems for me, I think I switched things over to device properties at some point while I was debugging things… I think I convinced myself that those would only fire when something changed state, and I wanted to make sure the PLEG code was evaluated constantly and not just when one input triggers (I think I read that it evaluates every minute elsewhere).

Anyway, it turns out that these apps were the only ones where they cannot be set to autoupdate, and I was somehow only running v1.7. So now I can see the report and status elements and I must say that is massively helpful for me to figure this out.

Excellent work, its much appreciated. I wish your insight into this was incorporated into the base vera functionality but I’m glad you are here to contribute so much.

Thanks again.

bk