UPDATED: Program Logic Timer Switch Plugin

I seem to be unable to change the interval for a trigger. I enter a time in the “Interval” box at the top of the “Conditions” tab. I have conditions entered in the “Trigger” box.

Closing and reopening the device, or even going to a different tab within the device, causes the interval to return to 0.

Did you apply the patch? [url=http://forum.micasaverde.com/index.php/topic,14155.0.html]http://forum.micasaverde.com/index.php/topic,14155.0.html[/url]

I have now. That seems to have done the trick. Thanks!

Hi RexBeckett

And thx so much for your great plugin.
I don’t understand why but i have a strange behaviour, as if PLTS has created some scenes from a previous configuration and cannot delete them. Where are they stored?

Thx for your help.

@milillicuti
Can you post some more details about what you are experiencing …
PLTS does not create any scenes … It has actions (Each action is similar to a scene). When you delete the PLTS devices … the actions should get deleted as well.

What are you seeing ?
Can you do provide a report for your PLTS device(s) ?

Hi RexBeckett

And thx so much for your great plugin.


I would be a proud man if I had created the PLxx plugins but the credit belongs entirely to @RichardTSchaefer.

[quote=“RichardTSchaefer, post:85, topic:173258”]@milillicuti
Can you post some more details about what you are experiencing …
PLTS does not create any scenes … It has actions (Each action is similar to a scene). When you delete the PLTS devices … the actions should get deleted as well.

What are you seeing ?
Can you do provide a report for your PLTS device(s) ?[/quote]

I had strange behaviours but i found the origin.
PLTS does not create any scenes but it creates triggers, whose list i found in scenes > triggers. I delete all the ones related to PLTS and everything i fine now!

Thx for your fast reply and great plugin!

[quote=“apt, post:74, topic:173258”]I was trying to replace some scenes with so PLTS and PLEG devices, but I have run into a lot of trouble.
First my actions would run regardless wether the device (PLTS) was armed or disarmed. I want to define a schedule within the PLTS to arm and disarm itself in order to avoid running the actions. I have upgraded from 2.0 to 2.1 and now this seems to work out.[/quote]

Hello all,

I have the same behaviour… I created two PLTS to use with my house fan system and it seems when I create the triggers inside the PLTS, the plugin adds them as scene triggers. The problem the is that Vera is evaluating regularly these triggers and firing the actions related (those I set in the PLTS). For instance, I have a very simple PLTS that set a low speed on fan when humidity goes below 55%. The command is sent randomly about 5 times an hour, although the sensor remained under 55%.
My other PLTS fired actions when Bypassed with as condition a trigger used to set the bypass mode…

I was using version 1.9, and upgraded to 4.2 yesterday, but this strange things keep on going… should I destroy my previous PLTS (created with version 1.9) and rebuild them ?

Do I miss something in the way things are handled by vera / PLTS ? As you will see on the left, I am a beginner…

Config :

PLTS1 - Low speed

o Inputs :

  • Triggers:
    SdBHum_inf58 : humidity sensor bathroom goes below 58%

o Conditions:

  • Trigger :
    SdBHum_inf58

o Actions:

  • On :
    Set blind actuator tu ‘Down’
    Prowl notification

—> this PLTS runs regularly several times an hour, even when the humidity is and remains under 58%

PLTS2 - High speed

o Inputs :

  • Triggers:
    SdBHum_sup62 : humidity sensor bathroom goes over 62%
    ExtHum_inf63 : humidity sensor outside goes under 63%
    ExtHum_Sup65 : humidity sensor outside goes over 65%

o Conditions:

  • Trigger :
    SdBHum_sup62
  • Bypass :
    ExtHum_Sup65
  • Arm :
    ExtHum_inf63

o Actions:

  • On :
    Set blind actuator tu ‘Up’
    Prowl notification

—> this PLTS seems to runs each time one of the 3 triggers is true (and maybe regularly)

When I get a notification, I go in Automation / triggers and see they have run. It seems the PLTS logic is put apart by vera and the box just considers one trigger and fires the actions set in the corresponding PLTS set.

My vera firmware is 1.5.622, I have PLC and PLTS, but not PLEG installed.

Here is the log of one of the events :
08 05/22/13 0:31:09.702 JobHandler_LuaUPnP::HandleActionRequest device: 47 service: urn:rts-services-com:serviceId:ProgramLogicC action: TriggerAction <0x2fc85680>
08 05/22/13 0:31:09.703 JobHandler_LuaUPnP::HandleActionRequest argument triggerName=ExtHum_sup65 <0x2fc85680>
06 05/22/13 0:31:09.705 Device_Variable::m_szValue_set device: 47 service: urn:rts-services-com:serviceId:ProgramLogicTS variable: Armed was: 0 now: 0 #hooks: 0 upnp: 0 v:0xa623a0/NONE duplicate:1 <0x2fc85680>
06 05/22/13 0:31:09.707 Device_Variable::m_szValue_set device: 47 service: urn:rts-services-com:serviceId:ProgramLogicC variable: ObjectStatusMap was: {{name =‘Arm’, state = false, seq = 0},{name =‘Bypass’, state = true, seq = 1369174598},{name =‘Reset’, state = nil, seq = 0},{name =‘Trigger’, state = false, seq = 0},{name =‘Trigger2’, state = nil, seq = 0},{name =‘Restart’, state = nil, seq = 0},{name =‘Restart2’, state = nil, seq = 0},{name =‘On’, state = nil, seq = 0},{name =‘Off’, state = nil, seq = 0},{name =‘SdbHum_sup60’, state = false, seq = 0},{name =‘ExtHum_sup65’, state = true, seq = 1369174598},{name =‘ExtHum_inf63’, state = false, seq = 0},} now: {{name =‘Arm’, state = false, seq = 0},{name =‘Bypass’, state = true, seq = 1369175469},{name =‘Reset’, state = nil, seq = 0},{name =‘Trigger’, state = false, seq = 0},{name =‘Trigger2’, state = nil, seq = 0},{name =‘Restart’, state = nil, seq = 0},{name =‘Restart2’, state = nil, seq = 0},{name =‘On’, state = nil, seq = 0},{name =‘Off’, state = nil, seq = 0},{name =‘SdbHum_sup60’, state = false, seq = 0},{name =‘ExtHum_sup65’, state = true, seq = 1369175469},{name =‘ExtHum_inf63’, state = false, seq = 0},} #hooks: 0 upnp: 0 v:0xa86248/NONE duplicate:0 <0x2fc85680>
07 05/22/13 0:31:09.709 Event::Evaluate 5 ExtHum_sup65 scene ProgramLogic_47 is true users:(null) allow:1 <0x2fc85680>
08 05/22/13 0:31:09.709 Scene::RunScene running 11 ProgramLogic_47 <0x2fc85680>
08 05/22/13 0:31:09.710 JobHandler_LuaUPnP::HandleActionRequest device: 16 service: urn:upnp-org:serviceId:IOSPush1 action: SendProwlNotification <0x2fc85680>
08 05/22/13 0:31:09.710 JobHandler_LuaUPnP::HandleActionRequest argument Event=PLTS-VMC <0x2fc85680>
08 05/22/13 0:31:09.710 JobHandler_LuaUPnP::HandleActionRequest argument Description=Passage en grande vitesse <0x2fc85680>
08 05/22/13 0:31:09.710 JobHandler_LuaUPnP::HandleActionRequest argument Priority= <0x2fc85680>
08 05/22/13 0:31:09.712 JobHandler_LuaUPnP::HandleActionRequest argument URL= <0x2fc85680>

See:
http://forum.micasaverde.com/index.php/topic,14732.msg113537.html#msg113537

Hello Richard,

Indeed this solution fixed some of my problems (ie ghost actions from deleted PLTS)…

But I have another issue with my PLTS : I am trying to use “weather” sensors (ie that are regularly updated) as triggers.
Richard, stop me if I am wrong (as I am not so good at decrypting javascript language) : your PL plugin deals with binary triggers : “is right” or “is wrong”… this means that the evaluation of any PL device is fired when the value of one of its triggers has changed at update (?)

In my case the humidity is regularly updated by Rfxtrx plugin :

  • if none of the sensors I use as trigger in my PL device logic has changed value, nothing happens…
  • if any value of them has changed, then the PL logic is called and evaluates directly the input conditions : is each sensor (trigger) below or over value xx : true or false. With no concern if the previous state was already in the trigger range (ie already triggered before).
    ==> this fires the actions systematically when the triggering conditions are met and one sensor’s value slightly changes (for example , I need humidity below 59% and it goes from 55 to 54…)

The vera scenes work exactly the same way… I would have thought (my personal logic) that saying “Trigger = Sensor value goes under xx” means the trigger fires when the sensor crosses xx+ to xx- and then nothing happens until it go back over xx and crosses again under… it seems MCV did not implemented it that way.

As I suppose I am not the first one to run into this issue, I would appreciate some users samples of how you handle “simple” scene where a device is controlled by a ‘continuous’ sensor (I mean regularly updated value) and you don’t want the command to be issued all the time…

@Richard,
Would it be possible to implement in the PL that when it is called for evaluation it gets the triggers previous states and makes sure they were not already in the triggering range ? If yes → evaluated trigger considered as null.
Or do users want triggers that fire the actions at each update, even if condition already met before ???

In the PL plugins … Conditions only trigger actions when they go from false to true.
If a condition is repeatedly evaluated as true … it will NOT call the associated actions for subsequent evaluations. I suspect that one of your sensors is reporting bad data occasionally causing the associated condition to turn false momentarily.

I think it is not the case :
I checked the logs and found that sensors updates where value does not change has no effect on actions, and all the updates where value changes trigger the actions if value is in ‘trigger range’…

In the attached file (readable format this time :wink: ) you’ll have an example with device 41 (my 4in1 humidity sensor) and PLTS device 49 :
05/23/13 22:24:59.586 Device 41 updated for same value => no effect…
(some log, no update of device 41)
05/23/13 22:36:59.686 Device 41 updated, for a different value (both initial and final far from trigger value but in “triggering zone”)
05/23/13 22:36:59.687 PLTS (device 49) starts evaluation and triggers actions

=> in this case, PLTS has sent a notification for humidity below 59 although the humidity was updated from 50 to 49 (it is not in the log but PLTS had already triggered previously several times with humidity values far under 59)

The triggers I use for Arming and bypassing the PLTS seem to work weel, but I didn’t check if the effect was applied repetitively or once.
My two PLTS are exclusive on the same sensor, so when one is firing plenty of notifications (when I take a shower for example… humidity changing quickly) the other one is still.

Do you have any type of ‘weather’ sensor you could use to build a PLTS config like mine and see if you have same behaviour ?

On my side I will test with a temperature sensor to see if I have the same behaviour.

Hi Richard,

As I was suspecting, if I set another sensor as trigger, it is the same behaviour.
I set an Oregon temperature sensor as trigger yesterday and since I had 160 notifications (12 hours) of running actions from PLTS. The condition was External Temperature goes below 15degC. The temperature never went over 15 since yesterday, and the Oregon sensor has a 0,1degC accuracy which explains the number of notifications : each time there is a variation of 0,1degC, the actions are triggered.

There’s a software issue behind this. Firmware, plugins code, something else… I don’t know.

The question now is : is it my specific to my Vera and configuration or is it the same for everybody running 1.5.622 with PLTS ?
That’s why it would be nice if someone could try to set a PLTS with one trigger plugged on a temperature or humidity sensor…

That must be a Vera behavior for those types of events.

Get rid of the trigger … use a device variable … and program the condition as:

   TriggerCondition      DeviceVariable < SomeValue

This will only fire when the DeviceVariable goes below the SomeValue the 1st time.

[quote=“RichardTSchaefer, post:94, topic:173258”]That must be a Vera behavior for those types of events.

Get rid of the trigger … use a device variable … and program the condition as:

   TriggerCondition      DeviceVariable < SomeValue

This will only fire when the DeviceVariable goes below the SomeValue the 1st time.[/quote]

AAAARGGGHH !!! Same issue !!! >:( >:( >:( :cry:

06 05/25/13 21:53:43.205 Device_Variable::m_szValue_set device: 41 service: urn:micasaverde-com:serviceId:HumiditySensor1 variable: CurrentLevel was: 48 now: 49 #hooks: 2 upnp: 0 v:0xabd070/NONE duplicate:0 <0x2c09d680> 06 05/25/13 21:53:43.210 Device_Variable::m_szValue_set device: 48 service: urn:rts-services-com:serviceId:ProgramLogicC variable: ObjectStatusMap was: {{name ='Arm', state = false, seq = 1369499887},{name ='Bypass', state = true, seq = 1369511345},{name ='Reset', state = nil, seq = 0},{name ='Trigger', state = false, seq = 1369384698},{name ='Trigger2', state = nil, seq = 0},{name ='Restart', state = nil, seq = 0},{name ='Restart2', state = nil, seq = 0},{name ='On', state = nil, seq = 0},{name ='Off', state = nil, seq = 0},{name ='ExtHum_Sup65', state = true, seq = 1369511345},{name ='ExtHum_inf63', state = false, seq = 1369499887},{name ='SdBHum', state = '48', seq = 1369510903},} now: {{name ='Arm', state = false, seq = 1369499887},{name ='Bypass', state = true, seq = 1369511345},{name ='Reset', state = nil, seq = 0},{name ='Trigger', state = false, seq = 1369384698},{name ='Trigger2', state = nil, seq = 0},{name ='Restart', state = nil, seq = 0},{name ='Restart2', state = nil, seq = 0},{name ='On', state = nil, seq = 0},{name ='Off', state = nil, seq = 0},{name ='ExtHum_Sup65', state = true, seq = 1369511345},{name ='ExtHum_inf63', state = false, seq = 1369499887},{name ='SdBHum', state = '49', seq = 1369511623},} #hooks: 0 upnp: 0 v:0xaff0b0/NONE duplicate:0 <0x2c09d680> 06 05/25/13 21:53:43.212 Device_Variable::m_szValue_set device: 49 service: urn:rts-services-com:serviceId:ProgramLogicTS variable: ToggleTime was: 1369510908 now: 1369511628 #hooks: 0 upnp: 0 v:0xadb828/NONE duplicate:0 <0x2c09d680> 08 05/25/13 21:53:43.214 JobHandler_LuaUPnP::HandleActionRequest device: 16 service: urn:upnp-org:serviceId:IOSPush1 action: SendProwlNotification <0x2c09d680> 08 05/25/13 21:53:43.214 JobHandler_LuaUPnP::HandleActionRequest argument Description= <0x2c09d680> 08 05/25/13 21:53:43.215 JobHandler_LuaUPnP::HandleActionRequest argument Priority= <0x2c09d680> 08 05/25/13 21:53:43.215 JobHandler_LuaUPnP::HandleActionRequest argument Event=PLTS VMC tripped - PV <0x2c09d680> 08 05/25/13 21:53:43.215 JobHandler_LuaUPnP::HandleActionRequest argument URL= <0x2c09d680> 06 05/25/13 21:53:44.275 Device_Variable::m_szValue_set device: 16 service: urn:upnp-org:serviceId:IOSPush1 variable: TimeSend was: 1369510904 now: 1369511624 #hooks: 0 upnp: 0 v:(nil)/NONE duplicate:0 <0x2c09d680> 06 05/25/13 21:53:44.276 Device_Variable::m_szValue_set device: 16 service: urn:upnp-org:serviceId:IOSPush1 variable: ProwlCount was: 480 now: 481 #hooks: 0 upnp: 0 v:(nil)/NONE duplicate:0 <0x2c09d680> 06 05/25/13 21:53:44.277 Device_Variable::m_szValue_set device: 16 service: urn:upnp-org:serviceId:IOSPush1 variable: LastError was: Ok - 21:41 - (Prowl) now: Ok - 21:53 - (Prowl) #hooks: 0 upnp: 0 v:(nil)/NONE duplicate:0 <0x2c09d680> 06 05/25/13 21:53:49.493 Device_Variable::m_szValue_set device: 16 service: urn:upnp-org:serviceId:IOSPush1 variable: ProwlRemaining was: 999 now: 998 #hooks: 0 upnp: 0 v:(nil)/NONE duplicate:0 <0x2c09d680> 06 05/25/13 21:53:49.504 Device_Variable::m_szValue_set device: 16 service: urn:upnp-org:serviceId:IOSPush1 variable: ProwlResetDate was: 1369514504 now: 1369514505 #hooks: 0 upnp: 0 v:(nil)/NONE duplicate:0 <0x2c09d680> 06 05/25/13 21:53:49.506 Device_Variable::m_szValue_set device: 49 service: urn:rts-services-com:serviceId:ProgramLogicTS variable: Status was: 0 now: 1 #hooks: 0 upnp: 0 v:0xae4460/NONE duplicate:0 <0x2c09d680> 06 05/25/13 21:53:49.506 Device_Variable::m_szValue_set device: 49 service: urn:rts-services-com:serviceId:ProgramLogicTS variable: State was: 0 now: 3 #hooks: 0 upnp: 0 v:0xae4b00/NONE duplicate:0 <0x2c09d680> 06 05/25/13 21:53:49.507 Device_Variable::m_szValue_set device: 49 service: urn:rts-services-com:serviceId:ProgramLogicTS variable: LastStateChange was: 1369510908 now: 1369511629 #hooks: 0 upnp: 0 v:(nil)/NONE duplicate:0 <0x2c09d680> 06 05/25/13 21:53:49.509 Device_Variable::m_szValue_set device: 49 service: urn:rts-services-com:serviceId:ProgramLogicC variable: ObjectStatusMap was: {{name ='Arm', state = nil, seq = 0},{name ='Bypass', state = nil, seq = 0},{name ='Reset', state = nil, seq = 0},{name ='Trigger', state = true, seq = 1369510905},{name ='Trigger2', state = nil, seq = 0},{name ='Restart', state = nil, seq = 0},{name ='Restart2', state = nil, seq = 0},{name ='On', state = nil, seq = 0},{name ='Off', state = nil, seq = 0},{name ='SdBHum', state = '48', seq = 1369510903},} now: {{name ='Arm', state = nil, seq = 0},{name ='Bypass', state = nil, seq = 0},{name ='Reset', state = nil, seq = 0},{name ='Trigger', state = true, seq = 1369511629},{name ='Trigger2', state = nil, seq = 0},{name ='Restart', state = nil, seq = 0},{name ='Restart2', state = nil, seq = 0},{name ='On', state = nil, seq = 0},{name ='Off', state = nil, seq = 0},{name ='SdBHum', state = '49', seq = 1369511623},} #hooks: 0 upnp: 0 v:0xaff0b0/NONE duplicate:0 <0x2c09d680> 01 05/25/13 21:53:49.510 AlarmManager::Run callback for alarm 0x8af378 entry 0x1127548 type 15 id 330 param=(nil) entry->when: 1369511625 time: 1369511629 tnum: 1 slow 0 tardy 4 <0x2c09d680> 01 05/25/13 21:53:49.511 AlarmManager::Run callback for alarm 0x8af378 entry 0x119b518 type 14 id 331 param=(nil) entry->when: 1369511625 time: 1369511629 tnum: 1 slow 0 tardy 4 <0x2c09d680> 06 05/25/13 21:53:49.512 Device_Variable::m_szValue_set device: 49 service: urn:rts-services-com:serviceId:ProgramLogicTS variable: Status was: 1 now: 0 #hooks: 0 upnp: 0 v:0xae4460/NONE duplicate:0 <0x2de9d680> 06 05/25/13 21:53:49.513 Device_Variable::m_szValue_set device: 49 service: urn:rts-services-com:serviceId:ProgramLogicTS variable: State was: 3 now: 0 #hooks: 0 upnp: 0 v:0xae4b00/NONE duplicate:0 <0x2de9d680> 06 05/25/13 21:53:49.513 Device_Variable::m_szValue_set device: 49 service: urn:rts-services-com:serviceId:ProgramLogicTS variable: LastStateChange was: 1369511629 now: 1369511629 #hooks: 0 upnp: 0 v:(nil)/NONE duplicate:1 <0x2de9d680> 06 05/25/13 21:53:49.514 Device_Variable::m_szValue_set device: 49 service: urn:rts-services-com:serviceId:ProgramLogicTS variable: TimeRemaining was: now: #hooks: 0 upnp: 0 v:(nil)/NONE duplicate:1 <0x2de9d680>

I must really have a big problem in my Vera…
I opened a ticket to MCV support.

Would Verbose mode help to understand ?

Otherwise, I will try to uninstall all PL devices and re-install…

Turn on debug … UnInstall/ReInstall is not really necessary.

Done… here is the log.
PLTS is Device 49
Humidity sensor is combined 4in1 device #41
I am surprised to see arm and bypass evaluations as for device 49 there is only a trigger condition with SdBHum<60. The device is armed all the time.

06 05/26/13 11:06:54.739 Device_Variable::m_szValue_set device: 41 service: urn:micasaverde-com:serviceId:HumiditySensor1 variable: CurrentLevel was: 55 now: 56 #hooks: 3 upnp: 0 v:0xf75e70/NONE duplicate:0 <0x2bc15680> 06 05/26/13 11:06:54.740 Device_Variable::m_szValue_set device: 19 service: urn:futzle-com:serviceId:CombinationSwitch1 variable: Label was: 1/2 now: 1/2 #hooks: 0 upnp: 0 v:0xeadfc8/NONE duplicate:1 <0x2bc15680> 06 05/26/13 11:06:54.740 Device_Variable::m_szValue_set device: 19 service: urn:futzle-com:serviceId:CombinationSwitch1 variable: Status was: 0 now: 0 #hooks: 1 upnp: 0 v:0xead398/NONE duplicate:1 <0x2bc15680> 06 05/26/13 11:06:54.741 Device_Variable::m_szValue_set device: 19 service: urn:upnp-org:serviceId:SwitchPower1 variable: Status was: 0 now: 0 #hooks: 1 upnp: 0 v:0xe716a8/NONE duplicate:1 <0x2bc15680> 06 05/26/13 11:06:54.745 Device_Variable::m_szValue_set device: 48 service: urn:rts-services-com:serviceId:ProgramLogicC variable: ObjectStatusMap was: {{name ='Arm', state = nil, seq = 1369499887},{name ='Bypass', state = false, seq = 1369553421},{name ='Reset', state = nil, seq = 0},{name ='Trigger', state = false, seq = 1369541930},{name ='Trigger2', state = nil, seq = 0},{name ='Restart', state = nil, seq = 0},{name ='Restart2', state = nil, seq = 0},{name ='On', state = nil, seq = 0},{name ='Off', state = nil, seq = 0},{name ='ExtHum_Sup65', state = false, seq = 1369553421},{name ='ExtHum_inf63', state = true, seq = 1369559050},{name ='SdBHum', state = '55', seq = 1369555613},} now: {{name ='Arm', state = nil, seq = 1369499887},{name ='Bypass', state = false, seq = 1369553421},{name ='Reset', state = nil, seq = 0},{name ='Trigger', state = false, seq = 1369541930},{name ='Trigger2', state = nil, seq = 0},{name ='Restart', state = nil, seq = 0},{name ='Restart2', state = nil, seq = 0},{name ='On', state = nil, seq = 0},{name ='Off', state = nil, seq = 0},{name ='ExtHum_Sup65', state = false, seq = 1369553421},{name ='ExtHum_inf63', state = true, seq = 1369559050},{name ='SdBHum', state = '56', seq = 1369559214},} #hooks: 0 upnp: 0 v:0xfb83a0/NONE duplicate:0 <0x2bc15680> 50 05/26/13 11:06:54.746 luup_log:49: PLTS:49:PropertyUpdate:SdBHum: from:55 to:56 <0x2bc15680> 50 05/26/13 11:06:54.747 luup_log:49: PLTS:49:EvalConditions:Condition:Arm Trigger:SdBHum Result:false <0x2bc15680> 50 05/26/13 11:06:54.747 luup_log:49: PLTS:49:EvalConditions:Condition:Bypass Trigger:SdBHum Result:false <0x2bc15680> 50 05/26/13 11:06:54.748 luup_log:49: PLTS:49:EvalConditions:Condition:Reset Trigger:SdBHum Result:false <0x2bc15680> 50 05/26/13 11:06:54.749 luup_log:49: PLTS:49:EvalConditions:Condition:Trigger Trigger:SdBHum Result:true <0x2bc15680> 50 05/26/13 11:06:54.750 luup_log:49: PLTS:49:TriggerCondition:Trigger <0x2bc15680> 50 05/26/13 11:06:54.750 luup_log:49: PLTS:49:Interval:5:1 <0x2bc15680> 50 05/26/13 11:06:54.751 luup_log:49: PLTS:49:SetState:From:0 To:3 Via:1 <0x2bc15680> 50 05/26/13 11:06:54.751 luup_log:49: PLTS:49:StateTriggerAction: <0x2bc15680> 50 05/26/13 11:06:54.751 luup_log:49: PLTS:49:FireAction:Nothing found for:Trigger <0x2bc15680> 06 05/26/13 11:06:54.752 Device_Variable::m_szValue_set device: 49 service: urn:rts-services-com:serviceId:ProgramLogicTS variable: ToggleTime was: 1369555618 now: 1369559219 #hooks: 0 upnp: 0 v:0xf94560/NONE duplicate:0 <0x2bc15680> 50 05/26/13 11:06:54.753 luup_log:49: PLTS:49:StateToggleAction: <0x2bc15680> 50 05/26/13 11:06:54.753 luup_log:49: PLTS:49:FireAction:On <0x2bc15680> 08 05/26/13 11:06:54.754 JobHandler_LuaUPnP::HandleActionRequest device: 16 service: urn:upnp-org:serviceId:IOSPush1 action: SendProwlNotification <0x2bc15680> 08 05/26/13 11:06:54.754 JobHandler_LuaUPnP::HandleActionRequest argument Description= <0x2bc15680> 08 05/26/13 11:06:54.754 JobHandler_LuaUPnP::HandleActionRequest argument Priority= <0x2bc15680> 08 05/26/13 11:06:54.754 JobHandler_LuaUPnP::HandleActionRequest argument Event=PLTS VMC tripped - PV <0x2bc15680> 08 05/26/13 11:06:54.755 JobHandler_LuaUPnP::HandleActionRequest argument URL= <0x2bc15680> 06 05/26/13 11:06:56.072 Device_Variable::m_szValue_set device: 16 service: urn:upnp-org:serviceId:IOSPush1 variable: TimeSend was: 1369555614 now: 1369559216 #hooks: 0 upnp: 0 v:(nil)/NONE duplicate:0 __LEAK__ this:16384 start:2629632 to 0x1472000 <0x2bc15680> 06 05/26/13 11:06:56.073 Device_Variable::m_szValue_set device: 16 service: urn:upnp-org:serviceId:IOSPush1 variable: ProwlCount was: 502 now: 503 #hooks: 0 upnp: 0 v:(nil)/NONE duplicate:0 <0x2bc15680> 06 05/26/13 11:06:56.074 Device_Variable::m_szValue_set device: 16 service: urn:upnp-org:serviceId:IOSPush1 variable: LastError was: RST - 10:42 now: Ok - 11:06 - (Prowl) #hooks: 0 upnp: 0 v:(nil)/NONE duplicate:0 <0x2bc15680> 06 05/26/13 11:07:01.292 Device_Variable::m_szValue_set device: 16 service: urn:upnp-org:serviceId:IOSPush1 variable: ProwlRemaining was: 998 now: 999 #hooks: 0 upnp: 0 v:(nil)/NONE duplicate:0 __LEAK__ this:32768 start:2662400 to 0x147a000 <0x2bc15680> 06 05/26/13 11:07:01.308 Device_Variable::m_szValue_set device: 16 service: urn:upnp-org:serviceId:IOSPush1 variable: ProwlResetDate was: 1369557774 now: 1369562814 #hooks: 0 upnp: 0 v:(nil)/NONE duplicate:0 <0x2bc15680> 06 05/26/13 11:07:01.309 Device_Variable::m_szValue_set device: 49 service: urn:rts-services-com:serviceId:ProgramLogicTS variable: Status was: 0 now: 1 #hooks: 0 upnp: 0 v:0xf9d7b0/NONE duplicate:0 <0x2bc15680> 06 05/26/13 11:07:01.310 Device_Variable::m_szValue_set device: 49 service: urn:rts-services-com:serviceId:ProgramLogicTS variable: State was: 0 now: 3 #hooks: 0 upnp: 0 v:0xf9d790/NONE duplicate:0 <0x2bc15680> 06 05/26/13 11:07:01.311 Device_Variable::m_szValue_set device: 49 service: urn:rts-services-com:serviceId:ProgramLogicTS variable: LastStateChange was: 1369555618 now: 1369559221 #hooks: 0 upnp: 0 v:(nil)/NONE duplicate:0 <0x2bc15680> 50 05/26/13 11:07:01.311 luup_log:49: PLTS:49:EvalConditions:Condition:Trigger2 Trigger:SdBHum Result:false <0x2bc15680> 50 05/26/13 11:07:01.312 luup_log:49: PLTS:49:EvalConditions:Condition:Restart Trigger:SdBHum Result:false <0x2bc15680> 50 05/26/13 11:07:01.313 luup_log:49: PLTS:49:EvalConditions:Condition:Restart2 Trigger:SdBHum Result:false <0x2bc15680> 50 05/26/13 11:07:01.313 luup_log:49: PLTS:49:EvalConditions:Condition:On Trigger:SdBHum Result:false <0x2bc15680> 50 05/26/13 11:07:01.314 luup_log:49: PLTS:49:EvalConditions:Condition:Off Trigger:SdBHum Result:false <0x2bc15680> 50 05/26/13 11:07:01.315 luup_log:49: PLTS:49:SaveDB:{{name ='Arm', state = nil, seq = 0},{name ='Bypass', state = nil, seq = 0},{name ='Reset', state = nil, seq = 0},{name ='Trigger', state = true, seq = 1369559221},{name ='Trigger2', state = nil, seq = 0},{name ='Restart', state = nil, seq = 0},{name ='Restart2', state = nil, seq = 0},{name ='On', state = nil, seq = 0},{name ='Off', state = nil, seq = 0},{name ='SdBHum', state = '56', seq = 1369559214},} <0x2bc15680> 06 05/26/13 11:07:01.315 Device_Variable::m_szValue_set device: 49 service: urn:rts-services-com:serviceId:ProgramLogicC variable: ObjectStatusMap was: {{name ='Arm', state = nil, seq = 0},{name ='Bypass', state = nil, seq = 0},{name ='Reset', state = nil, seq = 0},{name ='Trigger', state = true, seq = 1369555614},{name ='Trigger2', state = nil, seq = 0},{name ='Restart', state = nil, seq = 0},{name ='Restart2', state = nil, seq = 0},{name ='On', state = nil, seq = 0},{name ='Off', state = nil, seq = 0},{name ='SdBHum', state = '55', seq = 1369555613},} now: {{name ='Arm', state = nil, seq = 0},{name ='Bypass', state = nil, seq = 0},{name ='Reset', state = nil, seq = 0},{name ='Trigger', state = true, seq = 1369559221},{name ='Trigger2', state = nil, seq = 0},{name ='Restart', state = nil, seq = 0},{name ='Restart2', state = nil, seq = 0},{name ='On', state = nil, seq = 0},{name ='Off', state = nil, seq = 0},{name ='SdBHum', state = '56', seq = 1369559214},} #hooks: 0 upnp: 0 v:0xfb83a0/NONE duplicate:0 <0x2bc15680> 02 05/26/13 11:07:01.317 ZW_Send_Data node 8 NO ROUTE (nil) <0x2be15680> 02 05/26/13 11:07:01.318 LOG_CHECK_MEMORY_LEAK pMem start 0x1437000 now 0x147a000 last 0x146e000 leaked 274432 <0x2bc15680> 50 05/26/13 11:07:01.321 luup_log:49: PLTS:49:SetState:From:3 To:0 Via:0 <0x2da15680> 50 05/26/13 11:07:01.321 luup_log:49: PLTS:49:StateResetAction: <0x2da15680> 50 05/26/13 11:07:01.322 luup_log:49: PLTS:49:FireAction:Nothing found for:Reset <0x2da15680> 50 05/26/13 11:07:01.323 luup_log:49: PLTS:49:FireAction:Nothing found for:Off <0x2da15680> 06 05/26/13 11:07:01.323 Device_Variable::m_szValue_set device: 49 service: urn:rts-services-com:serviceId:ProgramLogicTS variable: Status was: 1 now: 0 #hooks: 0 upnp: 0 v:0xf9d7b0/NONE duplicate:0 <0x2da15680> 06 05/26/13 11:07:01.324 Device_Variable::m_szValue_set device: 49 service: urn:rts-services-com:serviceId:ProgramLogicTS variable: State was: 3 now: 0 #hooks: 0 upnp: 0 v:0xf9d790/NONE duplicate:0 <0x2da15680> 06 05/26/13 11:07:01.324 Device_Variable::m_szValue_set device: 49 service: urn:rts-services-com:serviceId:ProgramLogicTS variable: LastStateChange was: 1369559221 now: 1369559221 #hooks: 0 upnp: 0 v:(nil)/NONE duplicate:1 <0x2da15680> 06 05/26/13 11:07:01.325 Device_Variable::m_szValue_set device: 49 service: urn:rts-services-com:serviceId:ProgramLogicTS variable: TimeRemaining was: now: #hooks: 0 upnp: 0 v:(nil)/NONE duplicate:1 <0x2da15680> 50 05/26/13 11:07:08.611 luup_log:25: RFXtrx: Received message: 08 50 02 01 E0 01 00 D9 59 <0x2f6a5680> 06 05/26/13 11:07:08.611 Device_Variable::m_szValue_set device: 25 service: urn:rfxcom-com:serviceId:rfxtrx1 variable: LastReceivedMsg was: 0A 52 02 01 8C 05 00 C4 36 00 69 now: 08 50 02 01 E0 01 00 D9 59 #hooks: 0 upnp: 0 v:(nil)/NONE duplicate:0 <0x2f6a5680> 50 05/26/13 11:07:08.613 luup_log:25: RFXtrx: cmds: T2/57345 Temperature 21.7 T2/57345 BatteryLevel 100 <0x2f6a5680> 06 05/26/13 11:07:08.615 Device_Variable::m_szValue_set device: 33 service: urn:upnp-org:serviceId:TemperatureSensor1 variable: CurrentTemperature was: 21.7 now: 21.7 #hooks: 0 upnp: 0 v:0xf57c08/NONE duplicate:1 <0x2f6a5680> 06 05/26/13 11:07:08.615 Device_Variable::m_szValue_set device: 33 service: urn:micasaverde-com:serviceId:HaDevice1 variable: BatteryDate was: 1369559189 now: 1369559228 #hooks: 0 upnp: 0 v:(nil)/NONE duplicate:0 <0x2f6a5680> 06 05/26/13 11:07:08.616 Device_Variable::m_szValue_set device: 33 service: urn:micasaverde-com:serviceId:HaDevice1 variable: BatteryLevel was: 100 now: 100 #hooks: 0 upnp: 0 v:0xe66f40/NONE duplicate:1 <0x2f6a5680> 06 05/26/13 11:07:15.133 Device_Variable::m_szValue_set device: 46 service: urn:demo-ted-striker:serviceId:PingSensor1 variable: CurrentFailureCount was: 0 now: 0 #hooks: 0 upnp: 0 v:(nil)/NONE duplicate:1 <0x2d615680> 02 05/26/13 11:07:17.179 ZWaveSerial::GetFrame 0x2be14f58 timed out now 0 m_listGetFramePending 0 <0x2be15680> 02 05/26/13 11:07:17.179 ZWaveJobHandler::SendDataAbort got m_iFrameID 0 <0x2be15680> 01 05/26/13 11:07:17.180 ZWJob_PollNode::Run job job#56 :pollnode_wake #8 dev:38 (0x1451588) N:8 P:20 S:1 ZW_Send_Data to node 8 failed 1 req 0x14701d8/1 abort m_iFrameID 0 <0x2be15680> 02 05/26/13 11:07:17.180 ZWJob_PollNode::PollFailed job job#56 :pollnode_wake #8 dev:38 (0x1451588) N:8 P:20 S:1 node 8 battery 1 <0x2be15680> 04 05/26/13 11:07:17.181 <0x2be15680>

I hope you can deduce from this what is the problem…

[EDIT] Moreover my other PLTS is firing actions in Bypass mode… totally strange ! Are U sure I don’t need to reinstall PL plugin ?

Hello,
From other users tests it seems this issue is specific to my Vera.
Now this is in MCV technical support’s hands.

Thanks for your help and time on my issue.