We have moved at community.getvera.com

Author Topic: Timed scenes triggering more than once?  (Read 4165 times)

Offline akbooer

  • Moderator
  • Master Member
  • *****
  • Posts: 6387
  • Karma: +291/-70
  • "Less is more"
Re: Timed scenes triggering more than once?
« Reply #15 on: May 03, 2017, 04:51:18 pm »
OK, that's as it should be - thanks.
3x Vera Lite-UI5/Edge-UI7, 25x Fibaro, 23x TKB, 9x MiniMote, 2x NorthQ Power, 2x Netatmo, 1x Foscam FI9831P, 9x Philips Hue,
Razberry, MySensors Arduino, HomeWave, AltUI, AltHue, DataYours, Grafana, openLuup, ZWay, ZeroBrane Studio.

Offline akbooer

  • Moderator
  • Master Member
  • *****
  • Posts: 6387
  • Karma: +291/-70
  • "Less is more"
Re: Timed scenes triggering more than once?
« Reply #16 on: May 03, 2017, 04:58:31 pm »
Quote
When I think of the next step, I'll be asking...

...in fact, just another sanity check: could you confirm that the output of the console's Scheduler > Jobs menu selection shows only one timer running for each scheduled scene?  On one of my systems I get, for example:

Code: [Select]
Scheduled Jobs, Wed May  3 21:55:58 2017 
    #  date       time        device    status  info 
    1  2017-05-03 21:55:59    system       Run  job#1162 :HTTP request from 127.0.0.1 
    2  2017-05-03 21:55:59    system      Wait  job#1160 :HTTP request from 127.0.0.1 
    3  2017-05-03 21:56:02    system      Wait  job#1137 :HTTP new connection tcp{client}: 0x1980690 
    4  2017-05-03 21:56:03    system      Wait  job#1161 :HTTP new connection tcp{client}: 0x1a10970 
    5  2017-05-03 21:56:54         0      Wait  job#8 :timer 'minute tick' for scene [3] Timer Test 
    6  2017-05-03 21:56:54         0      Wait  job#18 :timer '1 min' for scene [14] Delayed Actions 
    7  2017-05-03 22:34:54         0      Wait  job#9 :timer 'hour tick' for scene [3] Timer Test 
    8  2017-05-04 05:25:44         0      Wait  job#16 :timer 'sunrise' for scene [12] Sunrise 
    9  2017-05-04 12:00:00         0      Wait  job#13 :timer 'weekday' for scene [9] Weekday 
   10  2017-05-04 20:27:49         0      Wait  job#15 :timer 'sunset' for scene [11] Sunset 
   11  2017-05-06 12:00:00         0      Wait  job#17 :timer 'weekend' for scene [13] Weekend 
   12  2017-05-08 12:00:00         0      Wait  job#11 :timer 'monday' for scene [7] Monday 
   13  2017-05-09 12:00:00         0      Wait  job#10 :timer 'tuesday' for scene [6] Tuesday 
   14  2017-05-10 12:00:00         0      Wait  job#12 :timer 'wednesday' for scene [8] Wednesday 
   15  2017-06-01 00:00:00         0      Wait  job#14 :timer 'december' for scene [10] December 

The openLuup plugin device Control tab has a direct link to the console, which is the fastest way to get there unless you have it open already.
3x Vera Lite-UI5/Edge-UI7, 25x Fibaro, 23x TKB, 9x MiniMote, 2x NorthQ Power, 2x Netatmo, 1x Foscam FI9831P, 9x Philips Hue,
Razberry, MySensors Arduino, HomeWave, AltUI, AltHue, DataYours, Grafana, openLuup, ZWay, ZeroBrane Studio.

Offline a-lurker

  • Hero Member
  • *****
  • Posts: 872
  • Karma: +66/-8
Re: Timed scenes triggering more than once?
« Reply #17 on: May 03, 2017, 05:33:32 pm »
Code: [Select]
Scheduled Jobs, Thu May  4 07:28:29 2017 
    #  date       time        device    status  info 
    1  2017-05-04 07:28:30    system       Run  job#53312 :HTTP request from 172.22.22.18 
    2  2017-05-04 07:28:30    system      Wait  job#53311 :HTTP request from 172.22.22.18 
    3  2017-05-04 07:28:33    system      Wait  job#52260 :HTTP new connection tcp{client}: 0x1a41a88 
    4  2017-05-04 07:28:33    system      Wait  job#52965 :HTTP new connection tcp{client}: 0x17652d8 
    5  2017-05-04 07:30:00         0      Wait  job#31 :timer 'It is 7.30 AM' for scene [7] It is 7.30 AM 
    6  2017-05-04 07:47:38         0      Wait  job#35 :timer 'Prod DALI' for scene [32] Prod DALI 
    7  2017-05-04 08:00:00         0      Wait  job#30 :timer '8.00 AM trigger' for scene [6] It is 8.00 AM 
    8  2017-05-04 11:30:00         0      Wait  job#36 :timer '11.30 AM trigger' for scene [49] It is 11.30 AM 
    9  2017-05-04 17:29:10         0      Wait  job#28 :timer 'new timer' for scene [2] Sunset trigger 
   10  2017-05-04 17:54:59         0      Wait  job#33 :timer 'It is 5.55 PM' for scene [9] It is 5.55 PM 
   11  2017-05-04 23:59:00         0      Wait  job#32 :timer 'It is 11.59 PM' for scene [8] It is 11.59 PM 
   12  2017-05-05 01:29:59         0      Wait  job#29 :timer '1.30 AM trigger' for scene [5] It is 1.30 AM 
   13  2017-05-05 06:30:00         0      Wait  job#34 :timer '6.30 AM trigger' for scene [31] It is 6.30 AM 
   14  2017-05-05 07:04:52         0      Wait  job#27 :timer 'new timer' for scene [1] Sunrise trigger

You can see the 5.55 PM and 1.30 AM timer are out by a small amount. I'm not likely to be up at 1.30 AM to check what happens.

The days are getting long in Greenwich.

Offline DesT

  • Sr. Member
  • ****
  • Posts: 364
  • Karma: +5/-1
Re: Timed scenes triggering more than once?
« Reply #18 on: May 03, 2017, 07:53:31 pm »
I got:

1493855591    1493855591.7287
Vera Edge-UI7/Plus-UI7 (2), DSC Partition (5 ) + Zones Sensors(31), Nest thermostat (1) & Protect Fire/CO (3), GE Sw (8 ), GE Dimr (14), FGMS-001 (2), ZW100 (2), RZCS4 (1), AL-DSC11 (1), Aeon HEM 2nd Edition (1), Aeon SSE (5), YRD220-ZW (1), SONOS (6), MyQ Chamberlain (1)
PINE64/openLuup/ALTUI/Rules

Offline DesT

  • Sr. Member
  • ****
  • Posts: 364
  • Karma: +5/-1
Re: Timed scenes triggering more than once?
« Reply #19 on: May 04, 2017, 06:34:42 am »
Looks like I'm OK also..

Code: [Select]
42  2017-05-04 07:59:54         0      Wait  job#33 :timer 'Winnie Reminder' for scene [46] Reminder - Winnie 
   43  2017-05-04 10:00:00         0      Wait  job#34 :timer 'Daily 10:00:00' for scene [60] Reset RulesEngine ON 
   44  2017-05-04 18:54:55         0      Wait  job#31 :timer '18h55' for scene [43] Reminder - Kids Sleeping - 18h45 
   45  2017-05-04 19:44:55         0      Wait  job#32 :timer '19h50' for scene [44] Reminder - Kids Sleeping - 19h50 
   46  2017-05-04 19:47:00         0      Wait  job#35 :timer 'Everyday @ 19:47' for scene [61] Smartswitch - Evening mode *V 
   47  2017-05-04 20:11:55         0      Wait  job#25 :timer 'timer20:12' for scene [1] Pre-Sleeping *V 
   48  2017-05-05 03:00:00         0      Wait  job#27 :timer 'inNight Sleeping' for scene [14] Post-Sleeping 
   49  2017-05-05 04:59:57         0      Wait  job#29 :timer 'Everyday @ 05:00' for scene [28] SmartSwitch - Reset ALL 
   50  2017-05-05 04:59:59         0      Wait  job#30 :timer 'Daily Backup' for scene [41] Daily backup 
   51  2017-05-05 05:00:00         0      Wait  job#28 :timer 'Daily' for scene [20] Summer Mode 
   52  2017-05-05 05:15:00         0      Wait  job#37 :timer 'working days - 05h15' for scene [69] Waking Up - Seb working days 
   53  2017-05-05 21:12:00         0      Wait  job#26 :timer 'timer21:12' for scene [1] Pre-Sleeping *V 
   54  2017-05-06 15:00:00         0      Wait  job#36 :timer '15h00' for scene [63] Reminder - Snack time - 15h00 
Vera Edge-UI7/Plus-UI7 (2), DSC Partition (5 ) + Zones Sensors(31), Nest thermostat (1) & Protect Fire/CO (3), GE Sw (8 ), GE Dimr (14), FGMS-001 (2), ZW100 (2), RZCS4 (1), AL-DSC11 (1), Aeon HEM 2nd Edition (1), Aeon SSE (5), YRD220-ZW (1), SONOS (6), MyQ Chamberlain (1)
PINE64/openLuup/ALTUI/Rules

Offline DesT

  • Sr. Member
  • ****
  • Posts: 364
  • Karma: +5/-1
Re: Timed scenes triggering more than once?
« Reply #20 on: May 04, 2017, 08:23:36 am »
Just rename all my trigger name and also reload openLuup and looks like now, all trigger are at the right time and not like before with some seconds before the right time...

Code: [Select]
5  2017-05-04 10:02:00         0      Wait  job#34 :timer 'Everyday @ 10:02' for scene [60] Reset RulesEngine ON 
    6  2017-05-04 18:55:00         0      Wait  job#31 :timer 'Sunday to Thursday @ 18:55' for scene [43] Reminder - Kids Sleeping - 18h55 
    7  2017-05-04 19:47:00         0      Wait  job#35 :timer 'Everyday @ 19:47' for scene [61] Smartswitch - Evening mode *V 
    8  2017-05-04 19:50:00         0      Wait  job#32 :timer 'Sunday to Thursday @ 19:50' for scene [44] Reminder - Kids Sleeping - 19h50 
    9  2017-05-04 20:12:00         0      Wait  job#25 :timer 'Sunday to Thursday @ 20:12' for scene [1] Pre-Sleeping *V 
   10  2017-05-05 03:00:00         0      Wait  job#27 :timer 'inNight Sleeping Everyday @ 03:00' for scene [14] Post-Sleeping 
   11  2017-05-05 05:00:00         0      Wait  job#28 :timer 'Daily Backup Everyday @ 05:00' for scene [20] Summer Mode 
   12  2017-05-05 05:00:00         0      Wait  job#29 :timer 'Smartswitch Everyday @ 05:00' for scene [28] SmartSwitch - Reset ALL 
   13  2017-05-05 05:00:00         0      Wait  job#30 :timer 'Daily Backup Everyday @ 05:00' for scene [41] Daily backup 
   14  2017-05-05 05:15:00         0      Wait  job#37 :timer 'Monday to Friday @ 05:15' for scene [69] Waking Up - Seb working days 
   15  2017-05-05 08:00:00         0      Wait  job#33 :timer 'Winnie Reminder' for scene [46] Reminder - Winnie 
   16  2017-05-05 21:12:00         0      Wait  job#26 :timer 'Friday to Saturday @ 21:12' for scene [1] Pre-Sleeping *V 
   17  2017-05-06 15:00:00         0      Wait  job#36 :timer 'Saturday to Sunday @ 15:00' for scene [63] Reminder - Snack time - 15h00 
Vera Edge-UI7/Plus-UI7 (2), DSC Partition (5 ) + Zones Sensors(31), Nest thermostat (1) & Protect Fire/CO (3), GE Sw (8 ), GE Dimr (14), FGMS-001 (2), ZW100 (2), RZCS4 (1), AL-DSC11 (1), Aeon HEM 2nd Edition (1), Aeon SSE (5), YRD220-ZW (1), SONOS (6), MyQ Chamberlain (1)
PINE64/openLuup/ALTUI/Rules

Offline akbooer

  • Moderator
  • Master Member
  • *****
  • Posts: 6387
  • Karma: +291/-70
  • "Less is more"
Re: Timed scenes triggering more than once?
« Reply #21 on: May 04, 2017, 08:31:12 am »
Just rename all my trigger name and also reload openLuup and looks like now, all trigger are at the right time and not like before with some seconds before the right time...

Yes, I am wondering if there is some clock 'drift' issue.  Not necessarily with the system itself, but with the ways that delays are calculated.  This gives me something to look for...

  • Does the multiple scene problem get worse with time?
  • Does the system clock drift and/or get resynched every so often?

Not sure what the RPi default behaviour regarding NIST syncs and the clock might be - I'm no Unix expert!  Any observations on the above welcomed.

3x Vera Lite-UI5/Edge-UI7, 25x Fibaro, 23x TKB, 9x MiniMote, 2x NorthQ Power, 2x Netatmo, 1x Foscam FI9831P, 9x Philips Hue,
Razberry, MySensors Arduino, HomeWave, AltUI, AltHue, DataYours, Grafana, openLuup, ZWay, ZeroBrane Studio.

Offline DesT

  • Sr. Member
  • ****
  • Posts: 364
  • Karma: +5/-1
Re: Timed scenes triggering more than once?
« Reply #22 on: May 04, 2017, 08:47:15 am »
AK,

I'm not running openLuup on a Raspberry Pi anymore since a while.  It's running on a small form factor i7!

AFAIK it's not getting worse with time..
Vera Edge-UI7/Plus-UI7 (2), DSC Partition (5 ) + Zones Sensors(31), Nest thermostat (1) & Protect Fire/CO (3), GE Sw (8 ), GE Dimr (14), FGMS-001 (2), ZW100 (2), RZCS4 (1), AL-DSC11 (1), Aeon HEM 2nd Edition (1), Aeon SSE (5), YRD220-ZW (1), SONOS (6), MyQ Chamberlain (1)
PINE64/openLuup/ALTUI/Rules

Offline akbooer

  • Moderator
  • Master Member
  • *****
  • Posts: 6387
  • Karma: +291/-70
  • "Less is more"
Re: Timed scenes triggering more than once?
« Reply #23 on: May 05, 2017, 01:55:38 am »
I checked the time stamps in the above json - shows 2 second delay on  "last_run". Also - in the log posted above you see the scene started early by about 2 seconds. And the second scene was late by two seconds. Is  "last_run"  every used to calculate anything in this case? Is the two second offset a problem? Just guessing - as I would have thought the scheduler just says it's 8 AM again - run the scene. "last_run" would not be considered or enter into the calculations.

I think this may be the vital clue which I have been slow to pick up on...

...is it always the case for multiple triggering that only the last one is at or after the scheduled time?
3x Vera Lite-UI5/Edge-UI7, 25x Fibaro, 23x TKB, 9x MiniMote, 2x NorthQ Power, 2x Netatmo, 1x Foscam FI9831P, 9x Philips Hue,
Razberry, MySensors Arduino, HomeWave, AltUI, AltHue, DataYours, Grafana, openLuup, ZWay, ZeroBrane Studio.

Offline a-lurker

  • Hero Member
  • *****
  • Posts: 872
  • Karma: +66/-8
Re: Timed scenes triggering more than once?
« Reply #24 on: May 05, 2017, 02:20:29 am »
Well this is two days later from the last log and it's earlier again by an extra 1.5 secs from the last log. Maybe rounding errors building up. Give me another couple of hours and I'll post the next log.

Code: [Select]
2017-05-03 17:54:55.468   openLuup.server:: request completed (177 bytes, 1 chunks, 6 ms) tcp{client}: 0x198ab28
2017-05-03 17:54:58.497   luup_log:0: My Lua ver 0.50 debug: executing scene 9: "It is 5.55 PM" in room: "Watchers"
2017-05-03 17:55:00.161   luup_log:0: My Lua ver 0.50 debug: rest of scene 9 was executed
2017-05-03 17:55:00.161   luup.scenes:: scene 9, It is 5.55 PM, initiated by It is 5.55 PM
2017-05-03 17:55:00.173   openLuup.server:: request completed (4130 bytes, 1 chunks, 5073 ms) tcp{client}: 0x197afb8
2017-05-03 17:55:00.224   openLuup.server:: GET /data_request?id=user_data&output_format=json&DataVersion=497072759&_=1493447211658 HTTP/1.1 tcp{client}: 0x197afb8
2017-05-03 17:55:00.226   luup_log:0: My Lua ver 0.50 debug: executing scene 9: "It is 5.55 PM" in room: "Watchers"
2017-05-03 17:55:01.651   luup_log:0: My Lua ver 0.50 debug: rest of scene 9 was executed
2017-05-03 17:55:01.651   luup.scenes:: scene 9, It is 5.55 PM, initiated by It is 5.55 PM
2017-05-03 17:55:02.512   openLuup.server:: request completed (1159333 bytes, 73 chunks, 2288 ms) tcp{client}: 0x197afb8

This is what the job queue says:

Code: [Select]
2017-05-05 17:54:58         0      Wait  job#33 :timer 'It is 5.55 PM' for scene [9] It is 5.55 PM
« Last Edit: May 05, 2017, 02:25:28 am by a-lurker »

Offline akbooer

  • Moderator
  • Master Member
  • *****
  • Posts: 6387
  • Karma: +291/-70
  • "Less is more"
Re: Timed scenes triggering more than once?
« Reply #25 on: May 05, 2017, 02:43:56 am »
I am convinced that the scheduler and timer modules themselves are not the cause...

Here's some specific lines extracted from a log of one of my systems which has been running for 64 days.  The openLuup plugin synchronises to clock time on startup and then starts a repeating timer which should run on the minute, every two minutes.

Code: [Select]
2017-05-05 04:02:00.356   :: openLuup LOG ROTATION :: (runtime 64.4 days)
2017-05-05 04:04:00.044   luup_log:0: 3 Mb, cpu 2.3%, 64.38 days
2017-05-05 04:06:00.350   luup_log:0: 4 Mb, cpu 2.3%, 64.38 days
2017-05-05 04:08:00.153   luup_log:0: 4 Mb, cpu 2.3%, 64.38 days
2017-05-05 04:10:00.467   luup_log:0: 5 Mb, cpu 2.3%, 64.38 days
2017-05-05 04:12:00.291   luup_log:0: 5 Mb, cpu 2.3%, 64.38 days
2017-05-05 04:14:00.040   luup_log:0: 4 Mb, cpu 2.3%, 64.39 days
2017-05-05 04:16:00.405   luup_log:0: 4 Mb, cpu 2.3%, 64.39 days
2017-05-05 04:18:00.185   luup_log:0: 5 Mb, cpu 2.3%, 64.39 days
2017-05-05 04:20:00.455   luup_log:0: 5 Mb, cpu 2.3%, 64.39 days
2017-05-05 04:22:00.330   luup_log:0: 5 Mb, cpu 2.3%, 64.39 days
2017-05-05 04:24:00.060   luup_log:0: 3 Mb, cpu 2.3%, 64.39 days
2017-05-05 04:26:00.381   luup_log:0: 4 Mb, cpu 2.3%, 64.39 days
2017-05-05 04:28:00.115   luup_log:0: 5 Mb, cpu 2.2%, 64.39 days
2017-05-05 04:30:00.218   luup_log:0: 5 Mb, cpu 2.2%, 64.4 days

I would expect some variation, since the scheduler may be busy with other jobs, but as you see there is no drift even after 64 days.

The problem, then, must be specifically with the scene handling.
3x Vera Lite-UI5/Edge-UI7, 25x Fibaro, 23x TKB, 9x MiniMote, 2x NorthQ Power, 2x Netatmo, 1x Foscam FI9831P, 9x Philips Hue,
Razberry, MySensors Arduino, HomeWave, AltUI, AltHue, DataYours, Grafana, openLuup, ZWay, ZeroBrane Studio.

Offline a-lurker

  • Hero Member
  • *****
  • Posts: 872
  • Karma: +66/-8
Re: Timed scenes triggering more than once?
« Reply #26 on: May 05, 2017, 04:04:08 am »
As of a few minutes ago:

Code: [Select]
2017-05-05 17:54:58.844   openLuup.server:: GET /port_3480/data_request?_dc=1493970900534&id=lr_dmCtrl&control=status&last=1493970853 HTTP/1.1 tcp{client}: 0x199f708
2017-05-05 17:54:58.846   luup_log:0: My Lua ver 0.50 debug: executing scene 9: "It is 5.55 PM" in room: "Watchers"
2017-05-05 17:55:01.103   luup_log:0: My Lua ver 0.50 debug: rest of scene 9 was executed
2017-05-05 17:55:01.104   luup.scenes:: scene 9, It is 5.55 PM, initiated by It is 5.55 PM
2017-05-05 17:55:01.115   openLuup.server:: request completed (4130 bytes, 1 chunks, 5297 ms) tcp{client}: 0x192adb0
2017-05-05 17:55:01.116   openLuup.server:: request completed (268 bytes, 1 chunks, 2271 ms) tcp{client}: 0x199f708
2017-05-05 17:55:01.250   luup_log:12: Paradox_IP150_wps debug: zoneStatus: 1
2017-05-05 17:55:01.250   luup_log:12: Paradox_IP150_wps debug: Zone_011: Entry Hallway PI is now open
2017-05-05 17:55:01.250   luup.variable_set:12: 12.urn:a-lurker-com:serviceId:Paradox_IP150_wps1.Zone_011 was: 0 now: 1 #hooks:0
2017-05-05 17:55:01.251   openLuup.server:: GET /data_request?id=user_data&output_format=json&DataVersion=497074416&_=1493447224535 HTTP/1.1 tcp{client}: 0x192adb0
2017-05-05 17:55:01.253   luup_log:0: My Lua ver 0.50 debug: executing scene 9: "It is 5.55 PM" in room: "Watchers"
2017-05-05 17:55:02.905   luup_log:0: My Lua ver 0.50 debug: rest of scene 9 was executed
2017-05-05 17:55:02.906   luup.scenes:: scene 9, It is 5.55 PM, initiated by It is 5.55 PM
2017-05-05 17:55:03.779   openLuup.server:: request completed (1159513 bytes, 73 chunks, 2526 ms) tcp{client}: 0x192adb0
2017-05-05 17:55:03.807   luup_log:12: Paradox_IP150_wps debug: zoneStatus: 0

And the next scheduled trigger:

Code: [Select]
  15  2017-05-06 17:54:58         0      Wait  job#33 :timer 'It is 5.55 PM' for scene [9] It is 5.55 PM

Offline jswim788

  • Hero Member
  • *****
  • Posts: 809
  • Karma: +58/-2
Re: Timed scenes triggering more than once?
« Reply #27 on: May 05, 2017, 11:49:05 am »
Here's some specific lines extracted from a log of one of my systems which has been running for 64 days.  The openLuup plugin synchronises to clock time on startup and then starts a repeating timer which should run on the minute, every two minutes.
I would expect some variation, since the scheduler may be busy with other jobs, but as you see there is no drift even after 64 days.
Is it possible you would see a difference with a single long term timer (say 24 hours or more) as opposed to a timer running every 2 minutes?  Just a thought.

Offline akbooer

  • Moderator
  • Master Member
  • *****
  • Posts: 6387
  • Karma: +291/-70
  • "Less is more"
Re: Timed scenes triggering more than once?
« Reply #28 on: May 05, 2017, 01:08:22 pm »
Is it possible you would see a difference with a single long term timer (say 24 hours or more) as opposed to a timer running every 2 minutes?  Just a thought.

Good thought, but in fact I have several daily and weekly timers also running (like clockwork!) This one, for example:

Code: [Select]
2017-05-05 16:00:00.265   openLuup.scenes:: Advent ON is currently paused

is scheduled for 16:00 daily, does so (although it's actually paused, it still get rescheduled) and has been doing so for 64 days.

I'm currently following the line of thought that it's a problem in scenes which have potentially time-consuming actions, in other words, ones which finish a significant time after they start.  Just running some tests on a fix at the moment, and it needs some further work, but seems like it may be promising.  This is related to your cumulative error suggestion.

Is it the case that these repeated scenes have significant processing associated with them?  It may not be many lines of code, but if it involves, for example, HTTP requests or other I/O, then that would count.
3x Vera Lite-UI5/Edge-UI7, 25x Fibaro, 23x TKB, 9x MiniMote, 2x NorthQ Power, 2x Netatmo, 1x Foscam FI9831P, 9x Philips Hue,
Razberry, MySensors Arduino, HomeWave, AltUI, AltHue, DataYours, Grafana, openLuup, ZWay, ZeroBrane Studio.

Offline DesT

  • Sr. Member
  • ****
  • Posts: 364
  • Karma: +5/-1
Re: Timed scenes triggering more than once?
« Reply #29 on: May 09, 2017, 07:21:31 am »
AK,

Maybe that can help, need to validate, but pretty sure that all my scene that run more than once, contain either a wget call or/and an external os.execute ...
Vera Edge-UI7/Plus-UI7 (2), DSC Partition (5 ) + Zones Sensors(31), Nest thermostat (1) & Protect Fire/CO (3), GE Sw (8 ), GE Dimr (14), FGMS-001 (2), ZW100 (2), RZCS4 (1), AL-DSC11 (1), Aeon HEM 2nd Edition (1), Aeon SSE (5), YRD220-ZW (1), SONOS (6), MyQ Chamberlain (1)
PINE64/openLuup/ALTUI/Rules