Activities dont always run ;-(

I have an reactor set up to turn on the HW and set the CH to 21 degrees every morning and evening, this has been working ok but I noticed yesterday evening the HW did not turn on, but it worked this morning and tonight it hasnt turned on again

Can I get some help please trying to understand whats wrong, just one thing when the HW turns on it also turns on binary switch that pumps the water around, here is the logic summary report if anyone can help, thank you

*************************************************** REACTOR LOGIC SUMMARY REPORT ***************************************************
   Version: 3.7-20190 config 20190 cdata 20045 ui 20190 pluginDevice 526 LuaXP 1.0.2enh
    System: Vera version 1.7.5186 (7.31) on Sercomm G450 ID 36 (Vera Plus); loadtime 1600708254/1600708269; systemReady 1600708274
       Env: Lua 5.1; JSON dkjson 1.2; UnsafeLua=nil/true
Local time: 2020-09-21T18:17:55+0100; DST=1; Leicester, England United Kingdom; formats %d/%m/%Y %H:%M:%S
House mode: plugin 1; system 1; tracking off
  Sun data: { "source": "int", "civdawn": 1600665298, "nautdawn": 1600662861, "sunset": 1600711552, "nautdusk": 1600716044, "stamp": 2020265, "latitude": 52.6386, "astrodusk": 1600718600, "longitude": -1.13169, "civdusk": 1600713607, "astrodawn": 1600660305, "sunrise": 1600667353 }
  Geofence: not running
        RS: 1600626852,1600628338,1600630105,1600631821,1600631891,1600680007,1600696819,1600696843,1600696868,1600708269
        NS: 0:X,1590927660:U,1591331580:D,1591331645:U
************************************************************************************************************************************
CH HW (#539) tripped
    Version 20045.17 09/20/20 18:11:45
    Message/status: Tripped
    Condition group "CH HW" (OR)  TRUE as of 18:00:00 <root>
      |-F-trange bet ,,,5,30,,,,7,15 [1600707600 => 1600708270 at 18:11:10; F/F as of 07:15:00/07:15:00] <cond0>
      |-T-trange bet ,,,18,0,,,,22,0 [1600707600 => 1600708270 at 18:11:10; T/T as of 18:00:00/18:00:00] <condsemwy5g>
    Activity root.false
        Device Thermostat (469) action urn:upnp-org:serviceId:TemperatureSetpoint1/SetCurrentSetpoint( NewCurrentSetpoint="16.0" )
        Device Water (472) action urn:upnp-org:serviceId:HVAC_UserOperatingMode1/SetModeTarget( NewModeTarget="Off" )
        Delay 180 inline
        Device HW Pump (34) action urn:upnp-org:serviceId:SwitchPower1/SetTarget( newTargetValue="0" )
        Reset latched conditions in all groups
    Activity root.true
        Device HW Pump (34) action urn:upnp-org:serviceId:SwitchPower1/SetTarget( newTargetValue="1" )
        Device Thermostat (469) action urn:upnp-org:serviceId:TemperatureSetpoint1/SetCurrentSetpoint( NewCurrentSetpoint="21.00" )
        Device Water (472) action urn:upnp-org:serviceId:HVAC_UserOperatingMode1/SetModeTarget( NewModeTarget="HeatOn" )
    Events
        2020-09-21 18:11:09: Reactor startup (Luup reload)
        2020-09-21 18:11:09: Starting (Luup Startup/Reload)
        2020-09-21 18:11:10: Sensor update starting
        2020-09-21 18:11:10: Sensor update completed; 0.009s
        2020-09-21 18:14:03: Reset action invoked
        2020-09-21 18:14:03: Changing RS tripped state to false
        2020-09-21 18:14:09: Trip action invoked
        2020-09-21 18:14:09: Changing RS tripped state to true
    Devices
        ZWave (1) urn:schemas-micasaverde-com:device:ZWaveNetwork:1 (19/0); parent 0; plugin -; mfg  model ; dev D_ZWaveNetwork.xml impl 
        Thermostat (469) urn:schemas-upnp-org:device:Heater:1 (5/2); parent 1; plugin -; mfg Secure model SRT321; dev D_Heater1.xml impl 
        Water (472) urn:schemas-upnp-org:device:HVAC_ZoneThermostat:1 (5/1); parent 470; plugin -; mfg  model ; dev D_HVAC_ZoneThermostat1.xml impl 
        Relay (470) urn:schemas-upnp-org:device:Heater:1 (5/2); parent 1; plugin -; mfg Secure model SSR303; dev D_Heater1.xml impl 
        HW Pump (34) urn:schemas-upnp-org:device:BinaryLight:1 (3/0); parent 1; plugin -; mfg  model ; dev D_BinaryLight1.xml impl 
    Watches
        Device #539 CH HW service urn:toggledbits-com:serviceId:ReactorSensor variable TestHouseMode
        Device #539 CH HW service urn:toggledbits-com:serviceId:ReactorSensor variable cdata
        Device #539 CH HW service urn:toggledbits-com:serviceId:ReactorSensor variable TestTime

Could you capture the logic summary after the condition has gone true so we can see exactly what is happening. Currently there is no good info in the events section

ok thank you, the logic summary I posted is after the condition has gone true, did I miss something?

Hm in the event log if I’m looking at it correctly the conditions didn’t go true. Were you trying to manually making the conditions go true by just setting the RS to tripped?

ah yes, I think I did try to do that, my mistake, I’ll wait till it fails again then repost, thanks

Ok so this morning at 7:15 the HW and pump should turn off and thermostat set to 16, when I checked HW and pump ok but thermostat still at 21

*************************************************** REACTOR LOGIC SUMMARY REPORT ***************************************************
   Version: 3.8-20262 config 20190 cdata 20045 ui 20190 pluginDevice 526 LuaXP 1.0.2enh
    System: Vera version 1.7.5186 (7.31) on Sercomm G450 ID 36 (Vera Plus); loadtime 1600929689/1600929705; systemReady 1600929710
       Env: Lua 5.1; JSON dkjson 1.2; UnsafeLua=nil/true
Local time: 2020-09-24T07:58:59+0100; DST=1; Leicester, England United Kingdom; formats %d/%m/%Y %H:%M:%S
House mode: plugin 1; system 1; tracking off
  Sun data: { "source": "int", "civdawn": 1600924805, "nautdawn": 1600922386, "sunset": 1600970319, "nautdusk": 1600974788, "stamp": 2020268, "latitude": 52.6386, "astrodusk": 1600977308, "longitude": -1.13169, "civdusk": 1600972369, "astrodawn": 1600919866, "sunrise": 1600926854 }
  Geofence: not running
        RS: 1600886565,1600886638,1600887004,1600887133,1600887839,1600889142,1600889263,1600889703,1600898177,1600929705
        NS: 0:X,1590927660:U,1591331580:D,1591331645:U
************************************************************************************************************************************
CH HW (#539)
    Version 20045.17 09/20/20 18:11:45
    Message/status: Not tripped
    Condition group "CH HW" (OR)  false as of 07:15:00 <root>
      |-F-trange bet ,,,5,30,,,,7,15 [1600928100 => 1600929706 at 07:41:46; F/F as of 07:15:00/07:15:00] <cond0>
      |-F-trange bet ,,,18,0,,,,22,0 [1600928100 => 1600929706 at 07:41:46; F/F as of 22:00:00/22:00:00] <condsemwy5g>
    Activity root.false
        Device Thermostat (469) action urn:upnp-org:serviceId:TemperatureSetpoint1/SetCurrentSetpoint( NewCurrentSetpoint="16.0" )
        Device Water (472) action urn:upnp-org:serviceId:HVAC_UserOperatingMode1/SetModeTarget( NewModeTarget="Off" )
        Delay 180 inline
        Device HW Pump (34) action urn:upnp-org:serviceId:SwitchPower1/SetTarget( newTargetValue="0" )
        Reset latched conditions in all groups
    Activity root.true
        Device HW Pump (34) action urn:upnp-org:serviceId:SwitchPower1/SetTarget( newTargetValue="1" )
        Device Thermostat (469) action urn:upnp-org:serviceId:TemperatureSetpoint1/SetCurrentSetpoint( NewCurrentSetpoint="21.00" )
        Device Water (472) action urn:upnp-org:serviceId:HVAC_UserOperatingMode1/SetModeTarget( NewModeTarget="HeatOn" )
    Events
        2020-09-24 07:41:45: Reactor startup (Luup reload)
        2020-09-24 07:41:45: Starting (Luup Startup/Reload)
        2020-09-24 07:41:46: Sensor update starting
        2020-09-24 07:41:46: Sensor update completed; 0.008s
    Devices
        ZWave (1) urn:schemas-micasaverde-com:device:ZWaveNetwork:1 (19/0); parent 0; plugin -; mfg  model ; dev D_ZWaveNetwork.xml impl 
        Thermostat (469) urn:schemas-upnp-org:device:Heater:1 (5/2); parent 1; plugin -; mfg Secure model SRT321; dev D_Heater1.xml impl 
        Water (472) urn:schemas-upnp-org:device:HVAC_ZoneThermostat:1 (5/1); parent 470; plugin -; mfg  model ; dev D_HVAC_ZoneThermostat1.xml impl 
        Relay (470) urn:schemas-upnp-org:device:Heater:1 (5/2); parent 1; plugin -; mfg Secure model SSR303; dev D_Heater1.xml impl 
        HW Pump (34) urn:schemas-upnp-org:device:BinaryLight:1 (3/0); parent 1; plugin -; mfg  model ; dev D_BinaryLight1.xml impl 
    Watches
        Device #539 CH HW service urn:toggledbits-com:serviceId:ReactorSensor variable TestHouseMode
        Device #539 CH HW service urn:toggledbits-com:serviceId:ReactorSensor variable cdata
        Device #539 CH HW service urn:toggledbits-com:serviceId:ReactorSensor variable TestTime

Did you do a reload after 7:15? The events still don’t show the group going true, they only show a reload at 7:41 which clears the events

Hello Pabla, no I didn’t, I was still in bed :grinning:

sorry I’m a little unsure about what you need to help, I produced this report after 7:15 when HW and Pumps switch to off which they did but the thermostat hadnt set back to 16 from 21
thank you

Luup restarted at 7:41 and wiped the event history. Unless that was a planned reload, and given your other post about devices randomly not responding, I’d say you’re having a system problem, not a Reactor problem. You need to get to a stable system.

Still, we can likely prove Reactor is doing what you ask: you can turn on file logging for the ReactorSensor by setting its LogEventsToFile to 1 and doing a Luup reload. It will create a file called /etc/cmh-ludl/ReactorSensor539-events.log; the next time you think it isn’t working, grab that file (you can’t use the Luup files page, you have to use scp or similar tool) and email it to the email address in the Troubleshooting section of the Tools tab (and ping me here to let me know you’ve emailed it).

With the event log it shows exactly what happens leading up to the trigger of the activities and after that too. It allows us to see if this is a Reactor error or a Vera error. Following @rigpapa suggestions above will get the event log and then we can better help troubleshoot.

1 Like

Ha! It’s almost certainly a system problem and not Reactor, now and again I get a device that wont respond that is not controlled by a Reactor, then I do a manual reload and it responds straight away! , not sure why Luup reloaded, thanks I’ll try what you suggested

Ok so now the lights have not come on tonight, does this log help?

*************************************************** REACTOR LOGIC SUMMARY REPORT ***************************************************
   Version: 3.8-20262 config 20190 cdata 20045 ui 20190 pluginDevice 526 LuaXP 1.0.2enh
    System: Vera version 1.7.5186 (7.31) on Sercomm G450 ID 36 (Vera Plus); loadtime 1600971943/1600971959; systemReady 1600971964
       Env: Lua 5.1; JSON dkjson 1.2; UnsafeLua=nil/true
Local time: 2020-09-24T19:27:16+0100; DST=1; Leicester, England United Kingdom; formats %d/%m/%Y %H:%M:%S
House mode: plugin 1; system 1; tracking off
  Sun data: { "source": "int", "civdawn": 1600924805, "nautdawn": 1600922386, "sunset": 1600970319, "nautdusk": 1600974788, "stamp": 2020268, "latitude": 52.6386, "astrodusk": 1600977308, "longitude": -1.13169, "civdusk": 1600972369, "astrodawn": 1600919866, "sunrise": 1600926854 }
  Geofence: not running
        RS: 1600887133,1600887839,1600889142,1600889263,1600889703,1600898177,1600929705,1600970430,1600970902,1600971959
        NS: 0:X,1590927660:U,1591331580:D,1591331645:U
************************************************************************************************************************************
Lights (#536) tripped
    Version 20045.75 09/08/20 20:02:08
    Message/status: Tripped
    Condition group "Lights" (AND)  TRUE as of 19:18:00 <root>
      &-T-sun after sunset+20, [1600971480 => 1600971962 at 19:26:02; T/T as of 19:18:00/19:18:00] <condsd5fjyo>
      &-T-trange bet ,,,16,0,,,,23,30 [1600971480 => 1600971962 at 19:26:02; T/T as of 16:00:00/16:00:00] <condsd5hbns>
    Activity root.false
        Device Bathroom Light (71) action urn:upnp-org:serviceId:SwitchPower1/SetTarget( newTargetValue="0" )
        Device .Bedroom Lamp 1 (594) action urn:upnp-org:serviceId:SwitchPower1/SetTarget( newTargetValue="0" )
        Device .Bedroom Lamp 2 (593) action urn:upnp-org:serviceId:SwitchPower1/SetTarget( newTargetValue="0" )
        Device .Standard Lamp (624) action urn:upnp-org:serviceId:SwitchPower1/SetTarget( newTargetValue="0" )
        Device Borys Room Lamp (187) action urn:upnp-org:serviceId:SwitchPower1/SetTarget( newTargetValue="0" )
        Device Hall Lights (65) action urn:upnp-org:serviceId:SwitchPower1/SetTarget( newTargetValue="0" )
        Device Landing Lights (156) action urn:upnp-org:serviceId:SwitchPower1/SetTarget( newTargetValue="0" )
        Device Garden Lights (242) action urn:upnp-org:serviceId:SwitchPower1/SetTarget( newTargetValue="0" )
        Device Guest Toilet (300) action urn:upnp-org:serviceId:Dimming1/SetLoadLevelTarget( newLoadlevelTarget="0" )
        Device Hall Lamp (317) action urn:upnp-org:serviceId:Dimming1/SetLoadLevelTarget( newLoadlevelTarget="0" )
        Device Light (216) action urn:upnp-org:serviceId:SwitchPower1/SetTarget( newTargetValue="0" )
        Device Down Lights (292) action urn:upnp-org:serviceId:SwitchPower1/SetTarget( newTargetValue="0" )
        Delay 16200 inline
        Device .sensor 1 (590) action urn:micasaverde-com:serviceId:SecuritySensor1/SetArmed( newArmedValue="0" )
        Device Sensor Side (185) action urn:micasaverde-com:serviceId:SecuritySensor1/SetArmed( newArmedValue="0" )
        Device Neo Sensor Shed (610) action urn:micasaverde-com:serviceId:SecuritySensor1/SetArmed( newArmedValue="0" )
        Device Coach Lights (290) action urn:upnp-org:serviceId:SwitchPower1/SetTarget( newTargetValue="0" )
        Device Drive Motion Sensor (572) action urn:micasaverde-com:serviceId:SecuritySensor1/SetArmed( newArmedValue="0" )
        Device LED Strip Light (498) action urn:upnp-org:serviceId:SwitchPower1/SetTarget( newTargetValue="0" )
        Device Multisensor 6 in 1 (557) action urn:micasaverde-com:serviceId:SecuritySensor1/SetArmed( newArmedValue="0" )
    Activity root.true
        Device .Bedroom Lamp 1 (594) action urn:upnp-org:serviceId:Dimming1/SetLoadLevelTarget( newLoadlevelTarget="50" )
        Device .Bedroom Lamp 2 (593) action urn:upnp-org:serviceId:Dimming1/SetLoadLevelTarget( newLoadlevelTarget="50" )
        Device Coach Lights (290) action urn:upnp-org:serviceId:SwitchPower1/SetTarget( newTargetValue="1" )
        Device Hall Lamp (317) action urn:upnp-org:serviceId:Dimming1/SetLoadLevelTarget( newLoadlevelTarget="50" )
        Device Garden Lights (242) action urn:upnp-org:serviceId:SwitchPower1/SetTarget( newTargetValue="1" )
        Device Sensor Side (185) action urn:micasaverde-com:serviceId:SecuritySensor1/SetArmed( newArmedValue="1" )
        Device .sensor 1 (590) action urn:micasaverde-com:serviceId:SecuritySensor1/SetArmed( newArmedValue="1" )
        Device Neo Sensor Shed (610) action urn:micasaverde-com:serviceId:SecuritySensor1/SetArmed( newArmedValue="1" )
        Device Drive Motion Sensor (572) action urn:micasaverde-com:serviceId:SecuritySensor1/SetArmed( newArmedValue="1" )
        Device Multisensor 6 in 1 (557) action urn:micasaverde-com:serviceId:SecuritySensor1/SetArmed( newArmedValue="1" )
    Events
        2020-09-24 19:25:59: Reactor startup (Luup reload)
        2020-09-24 19:25:59: Starting (Luup Startup/Reload)
        2020-09-24 19:26:02: Sensor update starting
        2020-09-24 19:26:02: Sensor update completed; 0.010s
    Devices
        Bathroom Light (71) urn:schemas-upnp-org:device:DimmableLight:1 (2/0); parent 64; plugin -; mfg  model ; dev D_DimmableLight1.xml impl 
        Down Lights (292) urn:schemas-upnp-org:device:DimmableLight:1 (2/0); parent 64; plugin -; mfg  model ; dev D_DimmableLight1.xml impl 
        Landing Lights (156) urn:schemas-upnp-org:device:BinaryLight:1 (3/0); parent 64; plugin -; mfg  model ; dev D_BinaryLight1.xml impl 
        Hall Lights (65) urn:schemas-upnp-org:device:BinaryLight:1 (3/0); parent 64; plugin -; mfg  model ; dev D_BinaryLight1.xml impl 
        .Bedroom Lamp 2 (593) urn:schemas-upnp-org:device:DimmableLight:1 (2/0); parent 586; plugin -; mfg innr model BF 263; dev D_DimmableALTHue1.xml impl 
        Multisensor 6 in 1 (557) urn:schemas-micasaverde-com:device:MotionSensor:1 (4/3); parent 1; plugin -; mfg Aeotec model ZW100; dev D_MotionSensor1.xml impl 
        Philips hue (586) urn:schemas-upnp-org:device:althue:1 (26/-1); parent 0; plugin -; mfg Philips hue model BSB002; dev D_ALTHUE.xml impl I_ALTHUE.xml
        Light (216) urn:schemas-upnp-org:device:BinaryLight:1 (3/0); parent 214; plugin -; mfg  model ; dev D_BinaryLight1.xml impl 
        Borys Room Lamp (187) urn:schemas-upnp-org:device:BinaryLight:1 (3/0); parent 1; plugin -; mfg Everspring model ; dev D_BinaryLight1.xml impl 
        .sensor 1 (590) urn:schemas-micasaverde-com:device:MotionSensor:1 (4/3); parent 586; plugin -; mfg Signify Netherlands B.V. model SML002; dev D_MotionSensor1.xml impl 
        ZWave (1) urn:schemas-micasaverde-com:device:ZWaveNetwork:1 (19/0); parent 0; plugin -; mfg  model ; dev D_ZWaveNetwork.xml impl 
        Coach Lights (290) urn:schemas-upnp-org:device:BinaryLight:1 (3/0); parent 64; plugin -; mfg  model ; dev D_BinaryLight1.xml impl 
        LED Strip Light (498) urn:schemas-upnp-org:device:BinaryLight:1 (3/3); parent 1; plugin -; mfg Qubino model ZMNHBD1; dev D_BinaryLight1.xml impl 
        Virtual Sensor (571) urn:schemas-toggledbits-com:device:VirtualSensor:1 (4/1); parent 0; plugin 9031; mfg  model ; dev D_VirtualSensor1.xml impl I_VirtualSensor1.xml
        .Bedroom Lamp 1 (594) urn:schemas-upnp-org:device:DimmableLight:1 (2/0); parent 586; plugin -; mfg innr model BF 263; dev D_DimmableALTHue1.xml impl 
        Drive Motion Sensor (572) urn:schemas-micasaverde-com:device:MotionSensor:1 (4/3); parent 571; plugin -; mfg  model ; dev D_MotionSensor1.xml impl 
        Sensor Side (185) urn:schemas-micasaverde-com:device:MotionSensor:1 (4/3); parent 1; plugin -; mfg Philio model PSP05; dev D_MotionSensor1.xml impl 
        Neo Sensor Shed (610) urn:schemas-micasaverde-com:device:MotionSensor:1 (4/3); parent 1; plugin -; mfg  model ; dev D_MotionSensor1.xml impl 
        Hall Lamp (317) urn:schemas-upnp-org:device:DimmableLight:1 (2/0); parent 1; plugin -; mfg  model ; dev D_DimmableLight1.xml impl 
        Guest Toilet (300) urn:schemas-upnp-org:device:DimmableLight:1 (2/0); parent 64; plugin -; mfg  model ; dev D_DimmableLight1.xml impl 
        RFXtrx controller de (64) urn:schemas-rfxcom-com:device:rfxtrx:1 (666/-1); parent 0; plugin -; mfg  model ; dev D_RFXtrx.xml impl I_RFXtrx.xml
        Neo 2 Gang Switch (214) urn:schemas-upnp-org:device:BinaryLight:1 (3/0); parent 1; plugin -; mfg  model ; dev D_BinaryLight1.xml impl 
        .Standard Lamp (624) urn:schemas-upnp-org:device:DimmableLight:1 (2/0); parent 586; plugin -; mfg innr model BF 263; dev D_DimmableALTHue1.xml impl 
        Garden Lights (242) urn:schemas-upnp-org:device:BinaryLight:1 (3/0); parent 1; plugin -; mfg  model ; dev D_BinaryLight1.xml impl 
    Watches
        Device #536 Lights service urn:toggledbits-com:serviceId:ReactorSensor variable TestHouseMode
        Device #536 Lights service urn:toggledbits-com:serviceId:ReactorSensor variable TestTime
        Device #536 Lights service urn:toggledbits-com:serviceId:ReactorSensor variable cdata

Nope. You are in restart hell. You need to figure out why your system is restarting so much. Reactor can send the commands to luup to control the devices, but it cannot directly know if those commands succeed or not. What I suspect has happened is that one of these devices has caused a deadlock, which then resulted in a restart; when the restart happened, all pending Luup jobs were flush/dropped. So Reactor thinks it did the work, but Luup actually didn’t do it. Reactor doesn’t manage each device to make sure it ends up in the desired state; that would be a herculean task to get right for all of the various device types. At some point, we have to assume Luup is going to do what is asked of it. When there’s a mesh problem that makes luup crash/restart, all bets are off.

You’ve got at least one problem device in your mesh.

Ok thank you for the reply, all I need to do know is figure out why my system keeps restarting that would explain the randomness of different device AAAAAAAARRRRRRRRRGHHHHHHHH :wink: guess I’ll try to log a ticket with support, thanks

Ok so I spent all rebuilding my zwave hue and rf network
came home tonight and CH HW thermostat still at 16 should be 21 HW heat on but pump not switched on, am I right in thinking from the logic report that Luup reloaded again…

*************************************************** REACTOR LOGIC SUMMARY REPORT ***************************************************
   Version: 3.8-20262 config 20190 cdata 20045 ui 20190 pluginDevice 15 LuaXP 1.0.2enh
    System: Vera version 1.7.5186 (7.31) on Sercomm G450 ID 36 (Vera Plus); loadtime 1601312747/1601312758; systemReady 1601312763
       Env: Lua 5.1; JSON dkjson 2.5+LPeg; UnsafeLua=nil/true
Local time: 2020-09-28T19:22:14+0100; DST=1; Lutterworth, England United Kingdom; formats %d/%m/%Y %H:%M:%S
House mode: plugin 1; system 1; tracking off
  Sun data: {"source":"int","civdawn":1601270835,"nautdawn":1601268446,"sunset":1601315365,"nautdusk":1601319792,"stamp":2020272,"latitude":52.4563,"astrodusk":1601322260,"longitude":-1.20218,"civdusk":1601317402,"astrodawn":1601265978,"sunrise":1601272873}
  Geofence: not running
        RS: 1601234510,1601235653,1601237620,1601238692,1601238928,1601238993,1601275059,1601283320,1601292466,1601312758
        NS: 0:X,1601118480:U
************************************************************************************************************************************
CH HW (#40) tripped
    Version 20045.7 09/26/20 13:52:24
    Message/status: Tripped
    Condition group "CH HW" (OR)  TRUE as of 18:00:00 <root>
      |-F-trange bet ,,,5,30,,,,7,0 [1601312400 => 1601312762 at 18:06:02; F/F as of 07:00:00/07:00:00] <cond0>
      |-T-trange bet ,,,18,0,,,,22,0 [1601312400 => 1601312762 at 18:06:02; T/T as of 18:00:00/18:00:00] <condwzvau22>
    Activity root.false
        Device Wall Thermostat (11) action urn:upnp-org:serviceId:TemperatureSetpoint1/SetCurrentSetpoint( NewCurrentSetpoint="16" )
        Delay 180 inline
        Device HW (14) action urn:upnp-org:serviceId:HVAC_UserOperatingMode1/SetModeTarget( NewModeTarget="Off" )
        Device HW Pump (20) action urn:upnp-org:serviceId:SwitchPower1/SetTarget( newTargetValue="0" )
    Activity root.true
        Device Wall Thermostat (11) action urn:upnp-org:serviceId:TemperatureSetpoint1/SetCurrentSetpoint( NewCurrentSetpoint="21" )
        Device HW (14) action urn:upnp-org:serviceId:HVAC_UserOperatingMode1/SetModeTarget( NewModeTarget="HeatOn" )
        Device HW Pump (20) action urn:upnp-org:serviceId:SwitchPower1/SetTarget( newTargetValue="1" )
    Events
        2020-09-28 18:05:58: Reactor startup (Luup reload)
        2020-09-28 18:05:59: Starting (Luup Startup/Reload)
        2020-09-28 18:06:02: Sensor update starting
        2020-09-28 18:06:02: Sensor update completed; 0.009s
    Devices
        HW (14) urn:schemas-upnp-org:device:HVAC_ZoneThermostat:1 (5/1); parent 12; plugin -; mfg  model ; dev D_HVAC_ZoneThermostat1.xml impl 
        HW Pump (20) urn:schemas-upnp-org:device:BinaryLight:1 (3/0); parent 1; plugin -; mfg  model ; dev D_BinaryLight1.xml impl 
        Relay (12) urn:schemas-upnp-org:device:Heater:1 (5/2); parent 1; plugin -; mfg Secure model SSR303; dev D_Heater1.xml impl 
        Wall Thermostat (11) urn:schemas-upnp-org:device:Heater:1 (5/2); parent 1; plugin -; mfg Secure model SRT321; dev D_Heater1.xml impl 
        ZWave (1) urn:schemas-micasaverde-com:device:ZWaveNetwork:1 (19/0); parent 0; plugin -; mfg  model ; dev D_ZWaveNetwork.xml impl 
    Watches
        Device #40 CH HW service urn:toggledbits-com:serviceId:ReactorSensor variable TestHouseMode
        Device #40 CH HW service urn:toggledbits-com:serviceId:ReactorSensor variable cdata
        Device #40 CH HW service urn:toggledbits-com:serviceId:ReactorSensor variable TestTime

Yes it reloaded again before you could grab the event log, try to set a notification in the activities so that when the event goes true you can quickly get the logic summary before the LUUP reloads

vera log 1800 to 1805.pdf (196.4 KB)

Does this help?
Thanks

Please reread the instructions in this post: Activities dont always run ;-(

This will let us capture the event log in a file so that the reboots/reloads don’t matter.

Ok will do, problem is its random but I guess if I turn on a few of the reactors that have not run then I should get one sooner or later,thanks

I’m not sure what this means. Can you explain?

Best Home Automation shopping experience. Shop at getvera!

© 2020 Vera Control Ltd., All Rights Reserved. Terms of Use | Privacy Policy | Forum Rules