That resolved the one ghost I still had…and found several others that I wasn’t aware of. This looks promising!
Fix works perfectly.
- Garrett
[quote=“RichardTSchaefer, post:38, topic:175277”]OK, I have found the way that folks are creating these ghost actions.
When editing the actions you are clicking the SAVE button and not the Finished button.[/quote]
Actually, I noticed this was causing problems early on, so I was very conscious not to do that. Typically on my setup, the ghost actions seemed to appear after deleting a condition.
Anyway, I hate to be a pain, but I regret this fix actually created new ghost actions on my setup. I have two PLEG devices (1. Lighting, 2. Occupancy) installed and I did get a pop-up saying the ghost actions had been deleted when entering the PL device for Occupancy. Oddly though, the Lighting PLEG started exhibiting ghost behavior (turning lights on and off).
I cleared them (i hope!) by deleting all the actions in the Lighting PLEG and recreating them again.
You will need to show a debug log and a report.
At this time I am pretty sure this is not a ghost issue.
You may be suffering from logic problems.
[quote=“RichardTSchaefer, post:44, topic:175277”]You will need to show a debug log and a report.
At this time I am pretty sure this is not a ghost issue.
You may be suffering from logic problems.[/quote]
I wouldn’t rule that out. Any advice would certainly be appreciated!
Here’s the partial log and report (saved as txt since board won’t let me upload *.htm extensions).
The interesting part in the log file starts at line 100 where an event is triggering: Scene::RunScene running 21 ProgramLogic_98 <0x2e55d680> (turning on device #96 garage light). As the report shows, the garage light is not associated with the hallway sensor (MainHallMotionUntripped), and never has been.
Unfortunately, I did not have PLEG debugging on when this ghost action happened so i don’t know if the log will even be helpful. I’ve since turned it on and will repost with the new log when i can capture the ghost actions again.
I’m also seeing an interesting behavior just now where clicking on report for one of the PLEG devices triggers the ghost action cleanup prompt again, even though I haven’t made any changes since the last time it was cleaned. Odd.
Please let me know if there is any additional information I can contribute besides the debugging logs.
Thanks!
Hello,
Sorry, but it seems not to have worked for me also… 
I still have at least one non existing scene triggering (linked to PLTS service)…
08 05/22/13 23:00:05.919 JobHandler_LuaUPnP::HandleActionRequest device: 48 service: urn:rts-services-com:serviceId:ProgramLogicC action: TriggerAction <0x2f7ff680>
08 05/22/13 23:00:05.919 JobHandler_LuaUPnP::HandleActionRequest argument triggerName=ExtHum_Sup65 <0x2f7ff680>
06 05/22/13 23:00:05.935 Device_Variable::m_szValue_set device: 48 service: urn:rts-services-com:serviceId:ProgramLogicC variable: ObjectStatusMap was: {{name ='Arm', state = false, seq = 0},{name ='Bypass', state = true, seq = 1369256338},{name ='Reset', state = nil, seq = 0},{name ='Trigger', state = false, seq = 1369243335},{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 = 1369256338},{name ='ExtHum_inf63', state = false, seq = 0},{name ='SdBHum_sup62', state = false, seq = 1369243333},} now: {{name ='Arm', state = false, seq = 0},{name ='Bypass', state = true, seq = 1369256405},{name ='Reset', state = nil, seq = 0},{name ='Trigger', state = false, seq = 1369243335},{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 = 1369256405},{name ='ExtHum_inf63', state = false, seq = 0},{name ='SdBHum_sup62', state = false, seq = 1369243333},} #hooks: 0 upnp: 0 v:0xc7b378/NONE duplicate:0 <0x2f7ff680>
07 05/22/13 23:00:05.937 Event::Evaluate 4 ExtHum_Sup65 scene ProgramLogic_48 is true users:(null) allow:1 <0x2f7ff680>
08 05/22/13 23:00:05.937 Scene::RunScene running 12 ProgramLogic_48 <0x2f7ff680>
08 05/22/13 23:00:05.937 JobHandler_LuaUPnP::HandleActionRequest device: 16 service: urn:upnp-org:serviceId:IOSPush1 action: SendProwlNotification <0x2f7ff680>
08 05/22/13 23:00:05.938 JobHandler_LuaUPnP::HandleActionRequest argument Event=PLTS2 tripped - GV <0x2f7ff680>
08 05/22/13 23:00:05.938 JobHandler_LuaUPnP::HandleActionRequest argument Description= <0x2f7ff680>
08 05/22/13 23:00:05.938 JobHandler_LuaUPnP::HandleActionRequest argument Priority= <0x2f7ff680>
08 05/22/13 23:00:05.938 JobHandler_LuaUPnP::HandleActionRequest argument URL= <0x2f7ff680>
06 05/22/13 23:00:07.021 Device_Variable::m_szValue_set device: 16 service: urn:upnp-org:serviceId:IOSPush1 variable: TimeSend was: 1369256340 now: 1369256407 #hooks: 0 upnp: 0 v:(nil)/NONE duplicate:0 __LEAK__ this:32768 start:2220032 to 0x1191000 <0x2f7ff680>
06 05/22/13 23:00:07.022 Device_Variable::m_szValue_set device: 16 service: urn:upnp-org:serviceId:IOSPush1 variable: ProwlCount was: 145 now: 146 #hooks: 0 upnp: 0 v:(nil)/NONE duplicate:0 <0x2f7ff680>
06 05/22/13 23:00:07.023 Device_Variable::m_szValue_set device: 16 service: urn:upnp-org:serviceId:IOSPush1 variable: LastError was: Ok - 22:59 - (Prowl) now: Ok - 23:00 - (Prowl) #hooks: 0 upnp: 0 v:(nil)/NONE duplicate:0 <0x2f7ff680>
06 05/22/13 23:00:07.160 Device_Variable::m_szValue_set device: 16 service: urn:upnp-org:serviceId:IOSPush1 variable: ProwlRemaining was: 994 now: 993 #hooks: 0 upnp: 0 v:(nil)/NONE duplicate:0 __LEAK__ this:36864 start:2256896 to 0x119a000 <0x2f7ff680>
06 05/22/13 23:00:07.161 Device_Variable::m_szValue_set device: 16 service: urn:upnp-org:serviceId:IOSPush1 variable: ProwlResetDate was: 1369257024 now: 1369257024 #hooks: 0 upnp: 0 v:(nil)/NONE duplicate:1 <0x2f7ff680>
07 05/22/13 23:00:07.162 Event::Evaluate 5 ExtHum_inf63 scene ProgramLogic_48 is false repeat 0/-1 <0x2f7ff680>
I uploaded file, with restart checked… reloaded again the luup. Opened and saved the action tabs on PLTS devices. Then I Compared the vera J_ProgramLogicC.js file with the one provided (same). I suppose I followed well the procedure. But still ghost actions if one trigger of my PLTS logic is true.
[EDIT] : I still have a running PLTS device created with the old version plugin (1.9), could it be the cause of the issue ? The one that triggered ghost action is the most recent, though…
[EDIT2]
I digged a little bit to find out the html command to get userdata and ‘hidden’ scenes… I found several ones that are not in my 'Automation / scenes" tab…
Some are related to PL.
Am I supposed to delete all that are not in the “Autom/Scenes” tab ? Can I delete scenes with nothing inside (no trigger, just a scene declaration) ?
Did you restart/reload your browser ?
Hello,
No… you’re right ! I had not read carefully enough your procedure.
I did it and got some scene deletion notifications when opening one PLTS action tab.
But… still some unwanted actions from ‘old’ PLTS’ → removed it.
Then I wanted to add a new one, and clicked on ‘Add a new program logic core’ → I deleted it through direct http command (I hope there was nothing else to remove except the device).
Then I reloaded the navigator several times, I had my removed PLTS scene purged, reconstructed a new one, did several refresh of navigator cache… all seemed OK.
But… I still have unwanted triggering actions… I had one when my external sensor was updated, although this one is used to Bypass the PLTS !
The running scene in the logs seem to be the ‘good one’ (only related to this PLTS)…
08 05/23/13 9:39:59.741 JobHandler_LuaUPnP::HandleActionRequest device: 48 service: urn:rts-services-com:serviceId:ProgramLogicC action: TriggerAction <0x2fb5d680>
08 05/23/13 9:39:59.741 JobHandler_LuaUPnP::HandleActionRequest argument triggerName=ExtHum_Sup65 <0x2fb5d680>
06 05/23/13 9:39:59.745 Device_Variable::m_szValue_set device: 48 service: urn:rts-services-com:serviceId:ProgramLogicC variable: ObjectStatusMap was: {{name ='Arm', state = false, seq = 0},{name ='Bypass', state = true, seq = 1369294062},{name ='Reset', state = nil, seq = 0},{name ='Trigger', state = false, seq = 1369282282},{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 = 1369294062},{name ='ExtHum_inf63', state = false, seq = 0},{name ='SdBHum_sup62', state = false, seq = 1369282281},} now: {{name ='Arm', state = false, seq = 0},{name ='Bypass', state = true, seq = 1369294799},{name ='Reset', state = nil, seq = 0},{name ='Trigger', state = false, seq = 1369282282},{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 = 1369294799},{name ='ExtHum_inf63', state = false, seq = 0},{name ='SdBHum_sup62', state = false, seq = 1369282281},} #hooks: 0 upnp: 0 v:0xe992e0/NONE duplicate:0 <0x2fb5d680>
07 05/23/13 9:39:59.747 Event::Evaluate 3 ExtHum_Sup65 scene ProgramLogic_48 is true users:(null) allow:1 <0x2fb5d680>
08 05/23/13 9:39:59.747 Scene::RunScene running 12 ProgramLogic_48 <0x2fb5d680>
08 05/23/13 9:39:59.747 JobHandler_LuaUPnP::HandleActionRequest device: 16 service: urn:upnp-org:serviceId:IOSPush1 action: SendProwlNotification <0x2fb5d680>
08 05/23/13 9:39:59.748 JobHandler_LuaUPnP::HandleActionRequest argument Event=PLTS2 tripped - GV <0x2fb5d680>
08 05/23/13 9:39:59.748 JobHandler_LuaUPnP::HandleActionRequest argument Description= <0x2fb5d680>
08 05/23/13 9:39:59.748 JobHandler_LuaUPnP::HandleActionRequest argument Priority= <0x2fb5d680>
08 05/23/13 9:39:59.748 JobHandler_LuaUPnP::HandleActionRequest argument URL= <0x2fb5d680>
06 05/23/13 9:40:01.589 Device_Variable::m_szValue_set device: 16 service: urn:upnp-org:serviceId:IOSPush1 variable: TimeSend was: 1369294063 now: 1369294801 #hooks: 0 upnp: 0 v:(nil)/NONE duplicate:0 __LEAK__ this:81920 start:2207744 to 0x12c6000 <0x2fb5d680>
06 05/23/13 9:40:01.590 Device_Variable::m_szValue_set device: 16 service: urn:upnp-org:serviceId:IOSPush1 variable: ProwlCount was: 246 now: 247 #hooks: 0 upnp: 0 v:(nil)/NONE duplicate:0 <0x2fb5d680>
06 05/23/13 9:40:01.591 Device_Variable::m_szValue_set device: 16 service: urn:upnp-org:serviceId:IOSPush1 variable: LastError was: Ok - 09:27 - (Prowl) now: Ok - 09:40 - (Prowl) #hooks: 0 upnp: 0 v:(nil)/NONE duplicate:0 <0x2fb5d680>
06 05/23/13 9:40:01.863 Device_Variable::m_szValue_set device: 16 service: urn:upnp-org:serviceId:IOSPush1 variable: ProwlRemaining was: 998 now: 997 #hooks: 0 upnp: 0 v:(nil)/NONE duplicate:0 __LEAK__ this:36864 start:2244608 to 0x12cf000 <0x2fb5d680>
06 05/23/13 9:40:01.864 Device_Variable::m_szValue_set device: 16 service: urn:upnp-org:serviceId:IOSPush1 variable: ProwlResetDate was: 1369297407 now: 1369297407 #hooks: 0 upnp: 0 v:(nil)/NONE duplicate:1 <0x2fb5d680>
07 05/23/13 9:40:01.865 Event::Evaluate 4 ExtHum_inf63 scene ProgramLogic_48 is false repeat 0/-1 <0x2fb5d680>
I have no more ideas… the whole PL behaves like if I had just entered several triggers in a vera scene with no logic associated.
Reminder on my PLTS config :
PLTS1 - Low speed
o Inputs :
- Triggers:
SdBHum_inf59 : humidity sensor bathroom goes below 59%
o Conditions:
- Trigger :
SdBHum_inf59
o Actions:
- On :
Set blind actuator to ‘Down’ → removed until problem solved
Prowl notification
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 to ‘Up’ → removed until problem solved
Prowl notification
Not sure if this is suppose to happen, but every few times when I access the PLEG device to create new triggers, conditions, or actions, I get the pop up stating about ghost devices and that I need to save and refresh. Is this suppose to happen all of the time or was it only a one time occurrence?
- Garrett
Hello,
I had the same problem… Was waiting to access my Vera to Check again…
I was wondering if the issue reoccurs when the PL device triggers ?
I had once a correct behaviour with trigger arming my PLTS, then it triggered (expected) and after that unwanted actions sometimes when a sensor is updated…
Is there a way to display ghost scenes ? To check when they appear in the vera.
I just combined two PLEG devices as they did similar things (get me to bed and wake me up). I refreshed the page, opened up an actions tab and was told PLEG was deleting ghost scenes. It also deleted a scene I manually created which was associated with the deleted PLEG device.
I did also have notification of deleted ghost scenes… but my PLTS has only one trigger, plugged on a humidity sensor : if humidity in bathroom is under 59%, then trigger a notification…
It did its work correctly at 19:40 tonight, but triggered 5 times since despite the humidity has fallen under 55% at 19:40 !!! Do PLTs have a problem with sensors ? I noted same behaviour of a scene made directly in the vera : triggers at correct time, and them triggers regularly despite sensor is well under the limit…
Should I use the device property instead of defining a trigger ???
Did Vera Restart ?
It could be caused by Vera being reloaded …
Also It could be caused by Sensor sending bogus data occasionally.
No physical restart… but Luup restart regularly as I play with devices to understand. But I left it running during all afternoon and evening ant I had the problem…
Here is an extract of my vera logs : at 22:24:54 device 41 is updated without any effect on the PLTS but another update at 22:36:52 generates an unwanted action as the same action had already been fired 22:01…
Updating device 38 (4in1 sensor reporting bathroom humidity) starts PLTS #49 despite it already triggered for this 36 minutes earlier…
06 05/23/13 22:36:52.365 Device_Variable::m_szValue_set device: 38 service: urn:micasaverde-com:serviceId:ZWaveDevice1 variable: LastWakeup was: 1369340692 now: 1369341412 #hooks: 0 upnp: 0 v:(nil)/NONE duplicate:0 <0x2b4bb680>
02 05/23/13 22:36:52.367 ZWJob_SendData UPDATE MANUAL ROUTE 8=(nil) <0x2b4bb680>
02 05/23/13 22:36:52.371 ZW_Send_Data node 8 NO ROUTE (nil) <0x2b8bb680>
06 05/23/13 22:36:54.226 Device_Variable::m_szValue_set device: 38 service: urn:upnp-org:serviceId:TemperatureSensor1 variable: CurrentTemperature was: 24 now: 24 #hooks: 0 upnp: 0 v:0xc3f628/NONE duplicate:1 <0x2b4bb680>
06 05/23/13 22:36:54.226 Device_Variable::m_szValue_set device: 39 service: urn:upnp-org:serviceId:TemperatureSensor1 variable: CurrentTemperature was: 24 now: 24 #hooks: 0 upnp: 0 v:0xc3f628/NONE duplicate:1 <0x2b4bb680>
02 05/23/13 22:36:54.227 ZW_Send_Data node 8 NO ROUTE (nil) <0x2b8bb680>
06 05/23/13 22:36:56.956 Device_Variable::m_szValue_set device: 38 service: urn:micasaverde-com:serviceId:LightSensor1 variable: CurrentLevel was: 7 now: 7 #hooks: 0 upnp: 0 v:0xc5e690/NONE duplicate:1 <0x2b4bb680>
06 05/23/13 22:36:56.956 Device_Variable::m_szValue_set device: 40 service: urn:micasaverde-com:serviceId:LightSensor1 variable: CurrentLevel was: 7 now: 7 #hooks: 0 upnp: 0 v:0xc5e690/NONE duplicate:1 <0x2b4bb680>
02 05/23/13 22:36:56.957 ZW_Send_Data node 8 NO ROUTE (nil) <0x2b8bb680>
06 05/23/13 22:36:59.686 Device_Variable::m_szValue_set device: 38 service: urn:micasaverde-com:serviceId:HumiditySensor1 variable: CurrentLevel was: 50 now: 49 #hooks: 0 upnp: 0 v:0xc5d200/NONE duplicate:0 <0x2b4bb680>
06 05/23/13 22:36:59.686 Device_Variable::m_szValue_set device: 41 service: urn:micasaverde-com:serviceId:HumiditySensor1 variable: CurrentLevel was: 50 now: 49 #hooks: 2 upnp: 0 v:0xc5d200/NONE duplicate:0 <0x2b4bb680>
07 05/23/13 22:36:59.687 Event::Evaluate 5 SdBHum_sup62 scene ProgramLogic_48 is false repeat 0/-1 <0x2b4bb680>
08 05/23/13 22:36:59.687 JobHandler_LuaUPnP::HandleActionRequest device: 49 service: urn:rts-services-com:serviceId:ProgramLogicC action: TriggerAction <0x2b4bb680>
08 05/23/13 22:36:59.688 JobHandler_LuaUPnP::HandleActionRequest argument triggerName=SdBHum_inf59 <0x2b4bb680>
06 05/23/13 22:36:59.690 Device_Variable::m_szValue_set device: 49 service: urn:rts-services-com:serviceId:ProgramLogicTS variable: ToggleTime was: 1369339264 now: 1369341424 #hooks: 0 upnp: 0 v:0xc7bf78/NONE duplicate:0 <0x2b4bb680>
08 05/23/13 22:36:59.691 JobHandler_LuaUPnP::HandleActionRequest device: 16 service: urn:upnp-org:serviceId:IOSPush1 action: SendProwlNotification <0x2b4bb680>
08 05/23/13 22:36:59.691 JobHandler_LuaUPnP::HandleActionRequest argument Description= <0x2b4bb680>
08 05/23/13 22:36:59.692 JobHandler_LuaUPnP::HandleActionRequest argument Priority= <0x2b4bb680>
08 05/23/13 22:36:59.692 JobHandler_LuaUPnP::HandleActionRequest argument Event=PLTS VMC tripped - PV <0x2b4bb680>
08 05/23/13 22:36:59.692 JobHandler_LuaUPnP::HandleActionRequest argument URL= <0x2b4bb680>
06 05/23/13 22:37:00.914 Device_Variable::m_szValue_set device: 16 service: urn:upnp-org:serviceId:IOSPush1 variable: TimeSend was: 1369339261 now: 1369341420 #hooks: 0 upnp: 0 v:(nil)/NONE duplicate:0 __LEAK__ this:86016 start:2334720 to 0x10df000 <0x2b4bb680>
06 05/23/13 22:37:00.915 Device_Variable::m_szValue_set device: 16 service: urn:upnp-org:serviceId:IOSPush1 variable: ProwlCount was: 271 now: 272 #hooks: 0 upnp: 0 v:(nil)/NONE duplicate:0 <0x2b4bb680>
06 05/23/13 22:37:00.926 Device_Variable::m_szValue_set device: 16 service: urn:upnp-org:serviceId:IOSPush1 variable: LastError was: RST - 22:18 now: Ok - 22:37 - (Prowl) #hooks: 0 upnp: 0 v:(nil)/NONE duplicate:0 <0x2b4bb680>
06 05/23/13 22:37:01.251 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 __LEAK__ this:32768 start:2367488 to 0x10e7000 <0x2b4bb680>
06 05/23/13 22:37:01.251 Device_Variable::m_szValue_set device: 16 service: urn:upnp-org:serviceId:IOSPush1 variable: ProwlResetDate was: 1369342861 now: 1369342862 #hooks: 0 upnp: 0 v:(nil)/NONE duplicate:0 <0x2b4bb680>
06 05/23/13 22:37:01.253 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:0xc84c90/NONE duplicate:0 <0x2b4bb680>
06 05/23/13 22:37:01.254 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:0xc851c8/NONE duplicate:0 <0x2b4bb680>
06 05/23/13 22:37:01.254 Device_Variable::m_szValue_set device: 49 service: urn:rts-services-com:serviceId:ProgramLogicTS variable: LastStateChange was: 1369339266 now: 1369341421 #hooks: 0 upnp: 0 v:(nil)/NONE duplicate:0 <0x2b4bb680>
06 05/23/13 22:37:01.256 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 = 1369339266},{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_inf59', state = true, seq = 1369339259},} now: {{name ='Arm', state = nil, seq = 0},{name ='Bypass', state = nil, seq = 0},{name ='Reset', state = nil, seq = 0},{name ='Trigger', state = true, seq = 1369341421},{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_inf59', state = true, seq = 1369341419},} #hooks: 0 upnp: 0 v:0xc93248/NONE duplicate:0 <0x2b4bb680>
07 05/23/13 22:37:01.258 Event::Evaluate 6 SdBHum_inf59 scene ProgramLogic_49 is true users:(null) allow:1 <0x2b4bb680>
08 05/23/13 22:37:01.258 Scene::RunScene running 13 ProgramLogic_49 <0x2b4bb680>
02 05/23/13 22:37:01.260 ZW_Send_Data node 8 NO ROUTE (nil) <0x2b8bb680>
06 05/23/13 22:37:01.267 Device_Variable::m_szValue_set device: 49 service: urn:rts-services-com:serviceId:ProgramLogicTS variable: TimeRemaining was: now: 03 #hooks: 0 upnp: 0 v:(nil)/NONE duplicate:0 <0x2d4bb680>
06 05/23/13 22:37:01.268 Device_Variable::m_szValue_set device: 49 service: urn:rts-services-com:serviceId:ProgramLogicTS variable: IconState was: 0 now: 175 #hooks: 0 upnp: 0 v:0xc85228/NONE duplicate:0 <0x2d4bb680>
04 05/23/13 22:37:01.397 <0x2b4bb680>
The update 10 minutes before last trigger had no effect with PLTS…
06 05/23/13 22:24:54.216 Device_Variable::m_szValue_set device: 38 service: urn:upnp-org:serviceId:TemperatureSensor1 variable: CurrentTemperature was: 24 now: 24 #hooks: 0 upnp: 0 v:0xc3f628/NONE duplicate:1 <0x2b4bb680>
06 05/23/13 22:24:54.216 Device_Variable::m_szValue_set device: 39 service: urn:upnp-org:serviceId:TemperatureSensor1 variable: CurrentTemperature was: 24 now: 24 #hooks: 0 upnp: 0 v:0xc3f628/NONE duplicate:1 <0x2b4bb680>
02 05/23/13 22:24:54.217 ZW_Send_Data node 8 NO ROUTE (nil) <0x2b8bb680>
06 05/23/13 22:24:56.897 Device_Variable::m_szValue_set device: 38 service: urn:micasaverde-com:serviceId:LightSensor1 variable: CurrentLevel was: 7 now: 7 #hooks: 0 upnp: 0 v:0xc5e690/NONE duplicate:1 <0x2b4bb680>
06 05/23/13 22:24:56.897 Device_Variable::m_szValue_set device: 40 service: urn:micasaverde-com:serviceId:LightSensor1 variable: CurrentLevel was: 7 now: 7 #hooks: 0 upnp: 0 v:0xc5e690/NONE duplicate:1 <0x2b4bb680>
02 05/23/13 22:24:56.898 ZW_Send_Data node 8 NO ROUTE (nil) <0x2b8bb680>
06 05/23/13 22:24:59.586 Device_Variable::m_szValue_set device: 38 service: urn:micasaverde-com:serviceId:HumiditySensor1 variable: CurrentLevel was: 50 now: 50 #hooks: 0 upnp: 0 v:0xc5d200/NONE duplicate:1 <0x2b4bb680>
06 05/23/13 22:24:59.586 Device_Variable::m_szValue_set device: 41 service: urn:micasaverde-com:serviceId:HumiditySensor1 variable: CurrentLevel was: 50 now: 50 #hooks: 2 upnp: 0 v:0xc5d200/NONE duplicate:1 <0x2b4bb680>
02 05/23/13 22:24:59.587 ZW_Send_Data node 8 NO ROUTE (nil) <0x2b8bb680>
02 05/23/13 22:24:59.736 ZW_Send_Data node 8 NO ROUTE (nil) <0x2b8bb680>
06 05/23/13 22:25:02.296 Device_Variable::m_szValue_set device: 38 service: urn:micasaverde-com:serviceId:HaDevice1 variable: BatteryDate was: 1369333501 now: 1369340702 #hooks: 0 upnp: 0 v:(nil)/NONE duplicate:0 <0x2b4bb680>
06 05/23/13 22:25:02.296 Device_Variable::m_szValue_set device: 38 service: urn:micasaverde-com:serviceId:HaDevice1 variable: BatteryLevel was: 99 now: 100 #hooks: 0 upnp: 0 v:0xb4ea80/NONE duplicate:0 <0x2b4bb680>
04 05/23/13 22:25:02.298 <0x2b4bb680>
02 05/23/13 22:25:02.299 JobHandler::Run job#16 :Wakeup done 8 dev:38 (0x10a5438) N:8 P:102 S:0 is 10.42113000 seconds old <0x2b8bb680>
02 05/23/13 22:25:02.300 UPDATE MANUAL ROUTE2 8=(nil) <0x2b8bb680>
02 05/23/13 22:25:02.300 ZW_Send_Data node 8 NO ROUTE (nil) <0x2b8bb680>
04 05/23/13 22:25:02.406 <0x2b4bb680>
06 05/23/13 22:25:09.627 Device_Variable::m_szValue_set device: 31 service: urn:micasaverde-com:serviceId:SecuritySensor1 variable: Tripped was: 0 now: 1 #hooks: 1 upnp: 0 v:0xb55eb0/NONE duplicate:0 <0x2dabb680>
06 05/23/13 22:25:09.628 Device_Variable::m_szValue_set device: 31 service: urn:micasaverde-com:serviceId:SecuritySensor1 variable: LastTrip was: 1369340617 now: 1369340709 #hooks: 0 upnp: 0 v:0xb40440/NONE duplicate:0 <0x2dabb680>
50 05/23/13 22:25:09.858 luup_log:25: RFXtrx: Received message: 08 50 02 01 E0 01 00 E3 69 <0x2e8bb680>
06 05/23/13 22:25:09.859 Device_Variable::m_szValue_set device: 25 service: urn:rfxcom-com:serviceId:rfxtrx1 variable: LastReceivedMsg was: 0A 52 02 01 27 04 00 4B 45 00 59 now: 08 50 02 01 E0 01 00 E3 69 #hooks: 0 upnp: 0 v:(nil)/NONE duplicate:0 <0x2e8bb680>
50 05/23/13 22:25:09.860 luup_log:25: RFXtrx: cmds: T2/57345 Temperature 22.7 T2/57345 BatteryLevel 100 <0x2e8bb680>
06 05/23/13 22:25:09.862 Device_Variable::m_szValue_set device: 33 service: urn:upnp-org:serviceId:TemperatureSensor1 variable: CurrentTemperature was: 22.7 now: 22.7 #hooks: 0 upnp: 0 v:0xc3f628/NONE duplicate:1 <0x2e8bb680>
06 05/23/13 22:25:09.863 Device_Variable::m_szValue_set device: 33 service: urn:micasaverde-com:serviceId:HaDevice1 variable: BatteryDate was: 1369340670 now: 1369340709 #hooks: 0 upnp: 0 v:(nil)/NONE duplicate:0 <0x2e8bb680>
06 05/23/13 22:25:09.863 Device_Variable::m_szValue_set device: 33 service: urn:micasaverde-com:serviceId:HaDevice1 variable: BatteryLevel was: 100 now: 100 #hooks: 0 upnp: 0 v:0xb4ea80/NONE duplicate:1 <0x2e8bb680>
50 05/23/13 22:25:11.120 luup_log:46: PingSensor Ping Enabled, executed <0x2d0bb680>
02 05/23/13 22:25:15.103 ZW_Send_Data node 10 NO ROUTE (nil) <0x2b8bb680>
04 05/23/13 22:25:15.236 <0x2b4bb680>
I could not find any ‘buggy’ update of device 41 between “the update that does nothing to PLTS” and “the update that generates unwanted action”… see attached file (because log is too long to include it in the post).
As I told you previously I am a beginner in the MCV world… so I 'm learning as fast as possible but I am surely missing plenty of clues…
Is there a possibility that vera resets some variables or timers that make PL believe there was no previous trigger, and thus conclude that the variable has just crossed trigger value ?
As I said in my previous post, I had same behaviour with a vera scene (only one trigger : humidity is below xx% and when it is true, Vera keeps firing the scene randomly even hours after the trigger has passed the limit value). I assumed this was normal and that vera was re-evaluating scenes periodically. Can this be part of the issue ?
[EDIT] : Device 41 is a 4in1 sensors set to sleep for 720s and be polled every 360s…
Looking at my Cosm records, it seems the unwanted action triggers each time the sensor value is updated and has changed… if it does not change (updated value equals previous one) → no pb. If it is updated with a value change and satisfying the trigger condition (ie hum<59%) the action is fired…
Sleep time… spending too much time on my Vera :
[quote=“garrettwp, post:49, topic:175277”]Not sure if this is suppose to happen, but every few times when I access the PLEG device to create new triggers, conditions, or actions, I get the pop up stating about ghost devices and that I need to save and refresh. Is this suppose to happen all of the time or was it only a one time occurrence?
- Garrett[/quote]
I don’t know how the designed behavior is supposed to work, but mine only pops up once (aside from the weird anomaly I described earlier in the thread).
[quote=“silencery, post:45, topic:175277”][quote=“RichardTSchaefer, post:44, topic:175277”]You will need to show a debug log and a report.
At this time I am pretty sure this is not a ghost issue.
You may be suffering from logic problems.[/quote]
I wouldn’t rule that out. Any advice would certainly be appreciated!
Here’s the partial log and report (saved as txt since board won’t let me upload *.htm extensions).
The interesting part in the log file starts at line 100 where an event is triggering: Scene::RunScene running 21 ProgramLogic_98 <0x2e55d680> (turning on device #96 garage light). As the report shows, the garage light is not associated with the hallway sensor (MainHallMotionUntripped), and never has been.
Unfortunately, I did not have PLEG debugging on when this ghost action happened so i don’t know if the log will even be helpful. I’ve since turned it on and will repost with the new log when i can capture the ghost actions again.
I’m also seeing an interesting behavior just now where clicking on report for one of the PLEG devices triggers the ghost action cleanup prompt again, even though I haven’t made any changes since the last time it was cleaned. Odd.
Please let me know if there is any additional information I can contribute besides the debugging logs.
Thanks![/quote]
Just wanted to report back some good news on this. After that one last incident where the ghost actions were cleaned (again), it seems everything is working properly for now. Still not clear why PLEG cleaned twice though (I should also mention I opened the PLEG device at least a half dozen times after the initial clean before the second cleaning prompt came up)? Hopefully the fix will stick.
I’ll add more feedback if anything else comes up.
Thanks again Richard!
Richard:
Try this on your setup. Open a PLEG, go to the Action tab, click on Edit for an action, don’t make any changes, click Finish, then click save. After the Reload and a browser refresh, open the PLEG again and click on the Action tab. On my setup, I get the “ghost found” dialog and it cleans it.
I can repeat this process over an over, each time it claims to have found a ghost. I’ve tried it on multiple different PLEGs. I’m not seeing any ghost behavior at this point, but the auto-clean feature seems to think there still are some.
Hello Richard,
After another look at my PLTS I think they work the expected way… but this raises another issue that I describe in the PLTS thread… as this one is solved from my point of view.
Arnaud
@ChrisAZ
The 4.2 version of the plugin corrects the issue you raised.
I hope this thread is now closed!