Trigger stopped after update

Plugins & Plugin Development Program Logic (PLEG)
#1

My motion sensor triggers have stopped responding after the latest update.Reinstalled PLEG and Core.
Log shows “WatchTriggerProperties : InvalidTrigger :tOM1”. A device property for the tripped variable works fine.
I tried reentering them several times.

Edit: Also Device Properties from a multistring variable are not getting updated.
VeraPlus Firmaware 1.7.1975

#2

Can you go to the Advanced Tab for the PLEG that you are having problems with.
Then copy the contents of the Triggers property and post it .

This looks like trigger was not completely defined …

#3

I created a new PLEG device for testing with only one trigger.

From the advanced tab,triggers. [{‘device’:‘877’,‘name’:‘t1’,‘service’:‘’,‘template’:‘1’}]

#4

Just for the heck of it I pasted this from an older PLEG into the triggers.

[{‘name’:‘tOM’,‘device’:‘453’,‘template’:‘1’,‘service’:‘urn:micasaverde-com:serviceId:SecuritySensor1’,‘args’:[{‘name’:‘Armed’,‘op’:‘=’,‘value’:‘1’},{‘name’:‘Tripped’,‘op’:‘=’,‘value’:‘1’}]}]

After changing the device # to the correct one it works!
So, it looks like the editor is not populating the triggers correctly.?

#5

As I set it looks like the trigger was not fully defined …
Did you select all the options ?

#6

Yes. I will attach screen shots of the 2 triggers I just did. This is the trigger info.

[{‘device’:‘877’,‘name’:‘Test1’,‘service’:‘’,‘template’:‘1’},{‘device’:‘873’,‘name’:‘Test2’,‘service’:‘urn:upnp-org:serviceId:SwitchPower1’,‘template’:‘1’,‘args’:[{‘op’:‘=’,‘name’:‘Status’,‘value’:‘1’}]}]

The switch added fine but the motion did not.
I really hope this is not me doing something stupid, but I have worked on it for hours trying everything!

#7

I tried triggers from other devices and they work. It seems to only affect Motion sensors.
I have tried changing the EVENT TYPE and it still does not work.
Parameters for motion devices do work.

#8

Thanks, I will look into it.

#9

I found the problem with this. Fix will be released soon.

#10

If only Vera had someone like you on staff Richard!
Top marks!

#11

Great! I have a couple of other small issues, but I am going ti investigate further before I get with you about them.

Thanks!!!

#12

RTS, You are the best! Motion triggers are now working.
I was going to write this earlier and tell you it was still not working, but after a couple of reboots it started working correctly!

#13

The fix for newly defined motion triggers did not make it into the release … although I did release the change. Still investigating.

#14

Newly defined motion triggers ARE working for me! I just tested it again.

#15

Maybe I should have stayed in bed … They are working for me now … they were not working a few mintutes ago. It was like and old version was running then.

#16

Thats funny! I had to do a hard reboot. Thanks again.

#17

Bill, Richard,

Can you tell me if the fix regarding new motion sensors is already in place?
As i mentioned before i also experienced the issue that no information was coming to the PLEG
After some updates my existing motion sensors start working again, so i thought all issues are solved. But today i added two new motion sensors and here i’m having the same issues.
They work perfect in the standard Vera software, but not in PLEG. (again no last true or false data is received).

Kind regards,

Jeroen

#18

Did you reload LUA after creating your new triggers ?

#19

Hi Richard,
That did the trick, thanks for your quick reply.