Author Topic: Run scene no action  (Read 246 times)

Offline PrincessCleavage

  • Sr. Member
  • ****
  • Posts: 315
  • Karma: +4/-1
Run scene no action
« on: January 11, 2019, 09:59:10 pm »
Hi Rigpapa,
I have attempted to use run scene activity to run a Vera scene (end code is return true) but upon trip and in trip no actions take place. I notice there is a small icon import to activities that doesn?t seem to do anything, am I missing something or should the scene just run once selected and reactor changes states? Also notice that when selecting multiple scenes they get a red box around them and can not select save until their positions are swapped twice
(https://uploads.tapatalk-cdn.com/20190112/610cb2f84ee4d8378f892f8f3dd44f57.jpg)
Scenes run fine when I add the reactor state as a trigger for the Vera scene
« Last Edit: January 11, 2019, 11:05:46 pm by PrincessCleavage »

Offline rigpapa

  • Moderator
  • Hero Member
  • *****
  • Posts: 904
  • Karma: +144/-1
Re: Run scene no action
« Reply #1 on: January 11, 2019, 10:07:43 pm »
Hi Rigpapa,
I have attempted to use run scene activity to run a Vera scene (end code is return true) but upon trip and in trip no actions take place. I notice there is a small icon import to activities that doesn?t seem to do anything, am I missing something or should the scene just run once selected? Also notice that when selecting multiple scenes they get a red box around them and can not select save until their positions are swapped twice
(https://uploads.tapatalk-cdn.com/20190112/610cb2f84ee4d8378f892f8f3dd44f57.jpg)
Scenes run fine when I add the reactor state as a trigger for the Vera scene

The import button brings the scene's actions into the activity (makes it a local copy of what the scene does). Others have used this successfully. But "am I missing something or should the scene just run once selected" is a bit confusing. Selecting the scene will not run it. Clicking the import button on the scene will also not run it. I'm not sure what you're getting at there.

Based on these and your other comments, you just generally seem to not be successful with this interface on a mobile device. I'm not really into spending a lot of time figuring that out, because this is a very complex interface that requires the resources (width/resolution, speed, capability) of a desktop browser. I suggest you take your work there.

But based on your screen shot, it should run the two scenes when the ReactorSensor is tripped. If it doesn't, please go the to the Tools page and hit the Logic Summary link at the bottom of the page, and post the output here.
Author of Reactor, DelayLight, SiteSensor, Rachio, Deus Ex Machina II, Intesis WMP Gateway, Auto Virtual Thermostat and VirtualSensor plugins. Vera Plus w/100+ Z-wave devices. Vera3 sandbox.

Offline PrincessCleavage

  • Sr. Member
  • ****
  • Posts: 315
  • Karma: +4/-1
Re: Run scene no action
« Reply #2 on: January 11, 2019, 10:51:51 pm »
Hi Rigpapa,
I have attempted to use run scene activity to run a Vera scene (end code is return true) but upon trip and in trip no actions take place. I notice there is a small icon import to activities that doesn?t seem to do anything, am I missing something or should the scene just run once selected? Also notice that when selecting multiple scenes they get a red box around them and can not select save until their positions are swapped twice
(https://uploads.tapatalk-cdn.com/20190112/610cb2f84ee4d8378f892f8f3dd44f57.jpg)
Scenes run fine when I add the reactor state as a trigger for the Vera scene

The import button brings the scene's actions into the activity (makes it a local copy of what the scene does). Others have used this successfully. But "am I missing something or should the scene just run once selected" is a bit confusing. Selecting the scene will not run it. Clicking the import button on the scene will also not run it. I'm not sure what you're getting at there.

Based on these and your other comments, you just generally seem to not be successful with this interface on a mobile device. I'm not really into spending a lot of time figuring that out, because this is a very complex interface that requires the resources (width/resolution, speed, capability) of a desktop browser. I suggest you take your work there.

But based on your screen shot, it should run the two scenes when the ReactorSensor is tripped. If it doesn't, please go the to the Tools page and hit the Logic Summary link at the bottom of the page, and post the output here.
The previous screenshot is from a win 10 desktop running Firefox browser and all the actions were performed on it.
Should there be a notification or anything when click on the import? I get no response:
Output from logic:
***************************** LOGIC SUMMARY REPORT *****************************
   Version: 2.0 config 202
Local time: 2019-01-12T13:49:29+1000, DST=0
House mode: 1
  Sun data: { "stamp": 20190112, "civdawn": 1547231851, "nautdawn": 1547229969, "sunset": 1547282862, "nautdusk": 1547286310, "astrodusk": 1547288290, "civdusk": 1547284428, "astrodawn": 1547227988, "sunrise": 1547233417 }
====================================================================================================================================
Camera Management (#781)
    Message/status: Not tripped
    Group #1 <grp1683d15a834>
        (housemode) in 2,3,4 <cond1683d15a835>
    Trip Actions
        Run scene 34 Arm HD Foscam
        Run scene 122 Dinning Camera Home
    Untrip Actions
        Run scene 35 Disarm HD Foscam
        Run scene 121 Dinning Camera Topmost
    Events
        01/12/19 12:50:00 start:
        01/12/19 12:50:11 action: action=Trip,
        01/12/19 12:50:16 sensorstate: state=true,
        01/12/19 12:50:23 action: action=Reset,
        01/12/19 12:50:23 sensorstate: state=false,

Offline PrincessCleavage

  • Sr. Member
  • ****
  • Posts: 315
  • Karma: +4/-1
Re: Run scene no action
« Reply #3 on: January 11, 2019, 11:11:09 pm »
Red box around scene when adding multiple scenes and save button not avaialble until swap scene positions twice then red box goes away and save button becomes functional again:
(https://uploads.tapatalk-cdn.com/20190112/537416bbdde884066b12857bf406d158.jpg)

Offline rigpapa

  • Moderator
  • Hero Member
  • *****
  • Posts: 904
  • Karma: +144/-1
Re: Run scene no action
« Reply #4 on: January 12, 2019, 12:51:28 pm »
Red box around scene when adding multiple scenes and save button not avaialble until swap scene positions twice then red box goes away and save button becomes functional again:
(https://uploads.tapatalk-cdn.com/20190112/537416bbdde884066b12857bf406d158.jpg)

OK. Found that. Will have that fix up in the stable branch later today.

For your other issue(s), I need you to do two things (multiple steps each):

1) Trip your ReactorSensor, wait a moment (10-15 seconds), then open your Vera log file (http://your-vera-ip/cgi-bin/cmh/log.sh?Device=LuaUPnP), use in-page search (ctrl-F) to find the string "Camera Management (#781) now tripped". You may find several if you've been experimenting with tripping and untripping, and we need only the last/most-recent one, with the timestamp that matches your then-current time of day. Grab that line and 50-100 lines of log that follow and post it here or to me via email.

2) For each scene named above (34,35,121,122), run the following URL, and paste the output for all four in an email to me or post it here: http://your-vera-ip/port_3480/data_request?id=lr_Reactor&action=preloadscene&scene=nnn (supply your Vera's local IP address and change nnn to the scene number, one at a time).
Author of Reactor, DelayLight, SiteSensor, Rachio, Deus Ex Machina II, Intesis WMP Gateway, Auto Virtual Thermostat and VirtualSensor plugins. Vera Plus w/100+ Z-wave devices. Vera3 sandbox.

Offline PrincessCleavage

  • Sr. Member
  • ****
  • Posts: 315
  • Karma: +4/-1
Run scene no action
« Reply #5 on: January 12, 2019, 08:56:38 pm »
Red box around scene when adding multiple scenes and save button not avaialble until swap scene positions twice then red box goes away and save button becomes functional again:
(https://uploads.tapatalk-cdn.com/20190112/537416bbdde884066b12857bf406d158.jpg)

OK. Found that. Will have that fix up in the stable branch later today.

For your other issue(s), I need you to do two things (multiple steps each):

1) Trip your ReactorSensor, wait a moment (10-15 seconds), then open your Vera log file (http://your-vera-ip/cgi-bin/cmh/log.sh?Device=LuaUPnP), use in-page search (ctrl-F) to find the string "Camera Management (#781) now tripped". You may find several if you've been experimenting with tripping and untripping, and we need only the last/most-recent one, with the timestamp that matches your then-current time of day. Grab that line and 50-100 lines of log that follow and post it here or to me via email.

2) For each scene named above (34,35,121,122), run the following URL, and paste the output for all four in an email to me or post it here: http://your-vera-ip/port_3480/data_request?id=lr_Reactor&action=preloadscene&scene=nnn (supply your Vera's local IP address and change nnn to the scene number, one at a time).
Thanks Rigpapa, love your work. (Will I get the reactor update via auto update option or manual update?)
I think I have found my cause or my random scene working/not working issue where my return nil value stops the Kia engine from successfully starting:
LuaInterface::StartEngine failed run: 0 attempt to call a string value
http://forum.micasaverde.com/index.php?topic=17426.0
I think my system needs a purge of unused scenes and apps at the command line level as they don?t show in the GUI.
Tested reactor with run scene and is now working after manual power cycle of unit and the a soft restart of Vera edge but issue will most likely reoccur at some random interval, at least I know the symptoms and identification in logs(sorry to be a pain)
« Last Edit: January 12, 2019, 09:09:13 pm by PrincessCleavage »

Offline rigpapa

  • Moderator
  • Hero Member
  • *****
  • Posts: 904
  • Karma: +144/-1
Re: Run scene no action
« Reply #6 on: January 12, 2019, 09:34:42 pm »
Red box around scene when adding multiple scenes and save button not avaialble until swap scene positions twice then red box goes away and save button becomes functional again:
(https://uploads.tapatalk-cdn.com/20190112/537416bbdde884066b12857bf406d158.jpg)

OK. Found that. Will have that fix up in the stable branch later today.

For your other issue(s), I need you to do two things (multiple steps each):

1) Trip your ReactorSensor, wait a moment (10-15 seconds), then open your Vera log file (http://your-vera-ip/cgi-bin/cmh/log.sh?Device=LuaUPnP), use in-page search (ctrl-F) to find the string "Camera Management (#781) now tripped". You may find several if you've been experimenting with tripping and untripping, and we need only the last/most-recent one, with the timestamp that matches your then-current time of day. Grab that line and 50-100 lines of log that follow and post it here or to me via email.

2) For each scene named above (34,35,121,122), run the following URL, and paste the output for all four in an email to me or post it here: http://your-vera-ip/port_3480/data_request?id=lr_Reactor&action=preloadscene&scene=nnn (supply your Vera's local IP address and change nnn to the scene number, one at a time).
Thanks Rigpapa, love your work. (Will I get the reactor update via auto update option or manual update?)
I think I have found my cause or my random scene working/not working issue where my return nil value stops the Kia engine from successfully starting:
LuaInterface::StartEngine failed run: 0 attempt to call a string value
http://forum.micasaverde.com/index.php?topic=17426.0
I think my system needs a purge of unused scenes and apps at the command line level as they don?t show in the GUI.
Tested reactor with run scene and is now working after manual power cycle of unit and the a soft restart of Vera edge but issue will most likely reoccur at some random interval, at least I know the symptoms and identification in logs(sorry to be a pain)

Really? Ugh. That thread you linked goes back to 2013. I guess it hasn't improved since. That's... disappointing. Kind of suggests that if you've seen it once, you can see it again.  :(

So, I guess you spotted that in the logs? Unfortunately, Vera's logs are like sipping from a fire hose, but if you're patient, you can find gems that take you far. Always look at the logs when things are going pear-shaped. When I asked that you get them, I had noticed/confirmed (in the logic summary) that the scene wasn't running, so I was hoping the logs would reveal something about why (very unusual for it to not even log a scene start), and the second part, the request with the 4 scenes, was to pull the scene data out in JSON form (better than screen-shotting Vera's scene builder or "advanced editor"), so I could see what those were doing. If you're now up and running, I of course don't need those now, but if you discover down the road it's still not quite meeting expectations, that's the process (logic summary first, to review the basics, and if that's not fully revealing, log file and associated data).

I'm happy you found something, and I hope that's truly it. At this point, I would also back up my Vera (with a fresh Z-Wave backup) and tuck that file someplace, before you launch into any purging of scenes or other cleanups. My habit is to take a backup any time I'm about to start any serious wool-pulling, and immediately after things have returned to sanity after (and then again periodically as things continue to improve/evolve).

Still undecided on how I will deliver the update. Everything fixed is in the JavaScript UI, so just the one file as before.
« Last Edit: January 12, 2019, 09:45:40 pm by rigpapa »
Author of Reactor, DelayLight, SiteSensor, Rachio, Deus Ex Machina II, Intesis WMP Gateway, Auto Virtual Thermostat and VirtualSensor plugins. Vera Plus w/100+ Z-wave devices. Vera3 sandbox.

Offline PrincessCleavage

  • Sr. Member
  • ****
  • Posts: 315
  • Karma: +4/-1
Run scene no action
« Reply #7 on: January 12, 2019, 09:40:21 pm »
Thanks for the guidance. I also read a log developer thread who also had in log returning nil value which for one of the thread contributors turned out to be value led in a device which stopped lua engine from loading thus stopping scenes from executing. Hopefully it might be just all the modifications with the new reactor version and may not reoccur when I iron things out and stop or slow modifications to the system.
P.s I am now up to reactor no 22

Offline rigpapa

  • Moderator
  • Hero Member
  • *****
  • Posts: 904
  • Karma: +144/-1
Re: Run scene no action
« Reply #8 on: January 12, 2019, 11:06:34 pm »
OK. Patched JavaScript file is up. The instructions and link are in this earlier, now updated, post.
Author of Reactor, DelayLight, SiteSensor, Rachio, Deus Ex Machina II, Intesis WMP Gateway, Auto Virtual Thermostat and VirtualSensor plugins. Vera Plus w/100+ Z-wave devices. Vera3 sandbox.

Offline ledavidou

  • Sr. Newbie
  • *
  • Posts: 23
  • Karma: +0/-0
Re: Run scene no action
« Reply #9 on: January 14, 2019, 10:50:33 am »
Hi Rigpapa

First, Thanks for your works, pretty cool ! (V2.1 there)

But, I don't know why, since yesterday, my two reactors do no run the scene they are dedicated to.

The reactor change its state (from untripped to tripped to untripped and so on) but that's all...

Any idea ? Or something you want me to post in order to investigate ?

Thanks

Offline rigpapa

  • Moderator
  • Hero Member
  • *****
  • Posts: 904
  • Karma: +144/-1
Re: Run scene no action
« Reply #10 on: January 14, 2019, 10:59:41 am »
Hi Rigpapa

First, Thanks for your works, pretty cool ! (V2.1 there)

But, I don't know why, since yesterday, my two reactors do no run the scene they are dedicated to.

The reactor change its state (from untripped to tripped to untripped and so on) but that's all...

Any idea ? Or something you want me to post in order to investigate ?

Thanks

Let's start with the Logic Summary on the Tools tab (at the very bottom, in the footer).
Author of Reactor, DelayLight, SiteSensor, Rachio, Deus Ex Machina II, Intesis WMP Gateway, Auto Virtual Thermostat and VirtualSensor plugins. Vera Plus w/100+ Z-wave devices. Vera3 sandbox.

Offline ledavidou

  • Sr. Newbie
  • *
  • Posts: 23
  • Karma: +0/-0
Re: Run scene no action
« Reply #11 on: January 14, 2019, 11:59:37 am »
Wow, that's what I call a quick reply !!!

So, this is for the first reactor :

*************************************************** REACTOR LOGIC SUMMARY REPORT ***************************************************
   Version: 2.1 config 204
Local time: 2019-01-14T17:57:34+0100, DST=0
House mode: 1
  Sun data:
====================================================================================================================================
Cool / Heat Off (#335) armed
    Version 2.1547481489 01/14/19 16:58:09
    Message/status: Not tripped
    Group #1 <grp1684c7b7e76> false as of 17:46:14
        =T (trange) bet ,10,16,0,0,,4,15,0,0 [true/true as of 14:11:14/14:11:14; 1547484375 at 17:46:15] <cond1684c7b7e77>
        =f (service) Fibaro Tpt Sud (200) urn:upnp-org:serviceId:TemperatureSensor1/CurrentTemperature > 22 [false/false as of 17:46:14/17:46:14; 21.90 at 17:46:14] <cond1684c7bf908>
    Group #2 <grp1684c7d0483> false as of 14:12:22
        =f (trange) bet ,4,16,0,0,,10,15,0,0 [false/false as of 14:12:22/14:12:22; 1547484375 at 17:46:15] <cond1684c7d0484>
        =T (service) Fibaro Tpt Sud (200) urn:upnp-org:serviceId:TemperatureSensor1/CurrentTemperature < 27 [true/true as of 14:12:22/14:12:22; 21.90 at 17:46:14] <cond1684c7d8187>
    Trip Actions
        Run scene 169 Clim Off
    Untrip Actions (none)
    Events
        01/14/19 16:29:13 start:
        01/14/19 16:30:53 action: action=Restart,
        01/14/19 16:30:53 start:
        01/14/19 16:31:03 devicewatch: var=urn:upnp-org:serviceId:TemperatureSensor1/CurrentTemperature, device=200, old=22.10, new=21.10,
        01/14/19 16:31:03 condchange: newState=false, cond=cond1684c7bf908, oldState=true,
        01/14/19 16:31:03 evalchange: newState=false, cond=cond1684c7bf908, oldState=true,
        01/14/19 16:31:03 groupchange: newState=false, cond=grp1684c7b7e76, oldState=true,
        01/14/19 16:31:03 sensorstate: state=false,
        01/14/19 16:31:03 devicewatch: var=urn:upnp-org:serviceId:TemperatureSensor1/CurrentTemperature, device=200, old=22.10, new=21.10,
        01/14/19 16:46:05 devicewatch: var=urn:upnp-org:serviceId:TemperatureSensor1/CurrentTemperature, device=200, old=21.10, new=22.50,
        01/14/19 16:46:05 condchange: newState=true, cond=cond1684c7bf908, oldState=false,
        01/14/19 16:46:05 evalchange: newState=true, cond=cond1684c7bf908, oldState=false,
        01/14/19 16:46:05 groupchange: newState=true, cond=grp1684c7b7e76, oldState=false,
        01/14/19 16:46:05 sensorstate: state=true,
        01/14/19 16:46:05 devicewatch: var=urn:upnp-org:serviceId:TemperatureSensor1/CurrentTemperature, device=200, old=21.10, new=22.50,
        01/14/19 16:54:11 action: action=SetArmed, state=1,
        01/14/19 17:16:08 devicewatch: var=urn:upnp-org:serviceId:TemperatureSensor1/CurrentTemperature, device=200, old=22.50, new=21.40,
        01/14/19 17:16:08 condchange: newState=false, cond=cond1684c7bf908, oldState=true,
        01/14/19 17:16:08 evalchange: newState=false, cond=cond1684c7bf908, oldState=true,
        01/14/19 17:16:08 groupchange: newState=false, cond=grp1684c7b7e76, oldState=true,
        01/14/19 17:16:08 sensorstate: state=false,
        01/14/19 17:16:10 devicewatch: var=urn:upnp-org:serviceId:TemperatureSensor1/CurrentTemperature, device=200, old=22.50, new=21.40,
        01/14/19 17:31:10 devicewatch: var=urn:upnp-org:serviceId:TemperatureSensor1/CurrentTemperature, device=200, old=21.40, new=22.90,
        01/14/19 17:31:10 condchange: newState=true, cond=cond1684c7bf908, oldState=false,
        01/14/19 17:31:10 evalchange: newState=true, cond=cond1684c7bf908, oldState=false,
        01/14/19 17:31:10 groupchange: newState=true, cond=grp1684c7b7e76, oldState=false,
        01/14/19 17:31:10 sensorstate: state=true,
        01/14/19 17:31:10 startscene: scene=__trip, sceneName=__trip,
        01/14/19 17:31:10 startscene: scene=169, sceneName=Clim Off,
        01/14/19 17:31:11 endscene: scene=__trip, sceneName=__trip,
        01/14/19 17:31:11 devicewatch: var=urn:upnp-org:serviceId:TemperatureSensor1/CurrentTemperature, device=200, old=21.40, new=22.90,
        01/14/19 17:31:12 endscene: scene=169, sceneName=Clim Off,
        01/14/19 17:46:14 devicewatch: var=urn:upnp-org:serviceId:TemperatureSensor1/CurrentTemperature, device=200, old=22.90, new=21.90,
        01/14/19 17:46:14 condchange: newState=false, cond=cond1684c7bf908, oldState=true,
        01/14/19 17:46:14 evalchange: newState=false, cond=cond1684c7bf908, oldState=true,
        01/14/19 17:46:14 groupchange: newState=false, cond=grp1684c7b7e76, oldState=true,
        01/14/19 17:46:14 sensorstate: state=false,
        01/14/19 17:46:15 devicewatch: var=urn:upnp-org:serviceId:TemperatureSensor1/CurrentTemperature, device=200, old=22.90, new=21.90,


And for the second

*************************************************** REACTOR LOGIC SUMMARY REPORT ***************************************************
   Version: 2.1 config 204
Local time: 2019-01-14T17:58:53+0100, DST=0
House mode: 1
  Sun data:
====================================================================================================================================
Heat On (#336) armed tripped
    Version 2.1547481518 01/14/19 16:58:38
    Message/status: Tripped
    Group #1 <grp1684c899ca3> true as of 17:46:14
        =T (trange) bet ,10,16,0,0,,4,15,0,0 [true/true as of 14:27:00/14:27:00; 1547484375 at 17:46:15] <cond1684c899ca4>
        =T (service) Fibaro Tpt Sud (200) urn:upnp-org:serviceId:TemperatureSensor1/CurrentTemperature < 22 [true/true as of 17:46:14/17:46:14; 21.90 at 17:46:14] <cond1684c8a1d62>
        =T (trange) bet ,,,5,40,,,,0,30 [true/true as of 14:27:00/14:27:00; 1547484375 at 17:46:15] <cond1684c8a81c5>
    Trip Actions
        Run scene 170 Chauffe 23 degrés
    Untrip Actions (none)
    Events
        01/14/19 16:29:13 start:
        01/14/19 16:30:05 action: action=Trip,
        01/14/19 16:30:05 sensorstate: state=true,
        01/14/19 16:30:35 action: action=Restart,
        01/14/19 16:30:35 start:
        01/14/19 16:30:40 sensorstate: state=false,
        01/14/19 16:31:03 devicewatch: var=urn:upnp-org:serviceId:TemperatureSensor1/CurrentTemperature, device=200, old=22.10, new=21.10,
        01/14/19 16:31:03 condchange: newState=true, cond=cond1684c8a1d62, oldState=false,
        01/14/19 16:31:03 evalchange: newState=true, cond=cond1684c8a1d62, oldState=false,
        01/14/19 16:31:03 groupchange: newState=true, cond=grp1684c899ca3, oldState=false,
        01/14/19 16:31:03 sensorstate: state=true,
        01/14/19 16:31:03 devicewatch: var=urn:upnp-org:serviceId:TemperatureSensor1/CurrentTemperature, device=200, old=22.10, new=21.10,
        01/14/19 16:46:05 devicewatch: var=urn:upnp-org:serviceId:TemperatureSensor1/CurrentTemperature, device=200, old=21.10, new=22.50,
        01/14/19 16:46:05 condchange: newState=false, cond=cond1684c8a1d62, oldState=true,
        01/14/19 16:46:05 evalchange: newState=false, cond=cond1684c8a1d62, oldState=true,
        01/14/19 16:46:05 groupchange: newState=false, cond=grp1684c899ca3, oldState=true,
        01/14/19 16:46:05 sensorstate: state=false,
        01/14/19 16:46:05 devicewatch: var=urn:upnp-org:serviceId:TemperatureSensor1/CurrentTemperature, device=200, old=21.10, new=22.50,
        01/14/19 16:54:16 action: action=SetArmed, state=1,
        01/14/19 17:16:08 devicewatch: var=urn:upnp-org:serviceId:TemperatureSensor1/CurrentTemperature, device=200, old=22.50, new=21.40,
        01/14/19 17:16:08 condchange: newState=true, cond=cond1684c8a1d62, oldState=false,
        01/14/19 17:16:08 evalchange: newState=true, cond=cond1684c8a1d62, oldState=false,
        01/14/19 17:16:08 groupchange: newState=true, cond=grp1684c899ca3, oldState=false,
        01/14/19 17:16:09 sensorstate: state=true,
        01/14/19 17:16:09 startscene: scene=__trip, sceneName=__trip,
        01/14/19 17:16:09 startscene: scene=170, sceneName=Chauffe 23 degrés,
        01/14/19 17:16:10 endscene: scene=170, sceneName=Chauffe 23 degrés,
        01/14/19 17:16:10 endscene: scene=__trip, sceneName=__trip,
        01/14/19 17:16:10 devicewatch: var=urn:upnp-org:serviceId:TemperatureSensor1/CurrentTemperature, device=200, old=22.50, new=21.40,
        01/14/19 17:31:11 devicewatch: var=urn:upnp-org:serviceId:TemperatureSensor1/CurrentTemperature, device=200, old=21.40, new=22.90,
        01/14/19 17:31:11 condchange: newState=false, cond=cond1684c8a1d62, oldState=true,
        01/14/19 17:31:11 evalchange: newState=false, cond=cond1684c8a1d62, oldState=true,
        01/14/19 17:31:11 groupchange: newState=false, cond=grp1684c899ca3, oldState=true,
        01/14/19 17:31:11 sensorstate: state=false,
        01/14/19 17:31:11 devicewatch: var=urn:upnp-org:serviceId:TemperatureSensor1/CurrentTemperature, device=200, old=21.40, new=22.90,
        01/14/19 17:46:14 devicewatch: var=urn:upnp-org:serviceId:TemperatureSensor1/CurrentTemperature, device=200, old=22.90, new=21.90,
        01/14/19 17:46:14 condchange: newState=true, cond=cond1684c8a1d62, oldState=false,
        01/14/19 17:46:14 evalchange: newState=true, cond=cond1684c8a1d62, oldState=false,
        01/14/19 17:46:14 groupchange: newState=true, cond=grp1684c899ca3, oldState=false,
        01/14/19 17:46:14 sensorstate: state=true,
        01/14/19 17:46:14 startscene: scene=__trip, sceneName=__trip,
        01/14/19 17:46:14 startscene: scene=170, sceneName=Chauffe 23 degrés,
        01/14/19 17:46:15 endscene: scene=170, sceneName=Chauffe 23 degrés,
        01/14/19 17:46:15 endscene: scene=__trip, sceneName=__trip,
        01/14/19 17:46:15 devicewatch: var=urn:upnp-org:serviceId:TemperatureSensor1/CurrentTemperature, device=200, old=22.90, new=21.90,


Hope you'll find something...

Offline rigpapa

  • Moderator
  • Hero Member
  • *****
  • Posts: 904
  • Karma: +144/-1
Re: Run scene no action
« Reply #12 on: January 14, 2019, 12:15:36 pm »
OK. That's not giving me what I need to know. Please do this:

1) Go to the Tools tab in the ReactorSensor, and click the "Toggle Debug" link in the same footer where you found the Logic Summary link. You should get a new tab/page with a message saying that debug is now ON. You can close that tab/page.

2) Go back to the ReactorSensor's Status tab and click the Restart button. Wait until it goes through "Starting..." and to "Tripped" or "Untripped".

3) Click the Trip or Untrip button (opposite whatever state it's curerntly in). Do two full trip/untrip cycles.

4) Display the log file by going to http://your-vera-ip/cgi-bin/cmh/log.sh?Device=LuaUPnP (put in your Vera's local IP address).

5) Use the in-page search feature (CTRL-F usually) to search for the string "debug set true by request" and send me that line and everything after. Since it's going to be long and verbose, best is to PM me or email it to me (if you look in the left margin of this reply you'll see email and PM icons to use).
Author of Reactor, DelayLight, SiteSensor, Rachio, Deus Ex Machina II, Intesis WMP Gateway, Auto Virtual Thermostat and VirtualSensor plugins. Vera Plus w/100+ Z-wave devices. Vera3 sandbox.

Offline rigpapa

  • Moderator
  • Hero Member
  • *****
  • Posts: 904
  • Karma: +144/-1
Re: Run scene no action
« Reply #13 on: January 14, 2019, 08:15:20 pm »
OK. Got the logs. They show only the "Clim Off" scene running (only that Reactor being tripped/untripped), but it does show the scene running. Two IR commands going out.

It appears there may be a scene trigger still on that scene. Not sure if that's interfering or not, but when the ReactorSensor trips, I can see Vera's own event logic examining the scene triggers (it also looks like there's a house mode restriction? That would not affect Reactor).

There are no errors logged, and Reactor is running the two commands in the scene. When sending IR commands, timing can often be quite finicky. As a quick test, try changing the 2 second delay in your scene to 3 seconds. See if that makes a difference.
Author of Reactor, DelayLight, SiteSensor, Rachio, Deus Ex Machina II, Intesis WMP Gateway, Auto Virtual Thermostat and VirtualSensor plugins. Vera Plus w/100+ Z-wave devices. Vera3 sandbox.