Receive "DST Detected" (and reload of sensors) on April 1

Hi,

Since the real adaption of the DST (aka “Summertime”) on March 28 days ago I’m greeted again this eventing (April 1 - no fools joke) with messages like :slight_smile:

02 04/01/20 21:16:00.102 luup_log:6374: Reactor: DST change detected! Re-evaluating all children. <0x7508a520>

This occured this evening (April 01) already several times, so I’m getting some oscillation with Reactor scene controlling some HUE & LED-wall lights while whatching TV.

02 04/01/20 21:16:00.102 luup_log:6374: Reactor: DST change detected! Re-evaluating all children. <0x7508a520>
02 04/01/20 21:17:00.165 luup_log:6374: Reactor: DST change detected! Re-evaluating all children. <0x7508a520>
02 04/01/20 21:46:00.102 luup_log:6374: Reactor: DST change detected! Re-evaluating all children. <0x7508a520>
02 04/01/20 21:47:08.434 luup_log:6374: Reactor: DST change detected! Re-evaluating all children. <0x7508a520>

On March 28 → 29 (the real DST-switchover here in Europe) I was faced with lamps going on in the middle of the night etc) and I rebooted the VeraPlus hoping things would clear.
No DST messages since then but this evening again…?

How the heck should I investigate this ?
Reactor info,

*************************************************** REACTOR LOGIC SUMMARY REPORT ***************************************************
Version: 3.5 config 20017 cdata 20045 ui 20045 pluginDevice 6374 LuaXP not loaded
System: Vera version 1.7.4453 (pre-7.30) on Sercomm G450 ID nil (unknown); loadtime 1585692019; systemReady 1585692033; Lua 5.1; JSON dkjson 1.2; UnsafeLua=nil
Local time: 2020-04-01T23:30:17+0200; DST=1; Rumst, Flanders Belgium; formats %m/%d/%Y %H:%M:%S
House mode: plugin 1; system 1; tracking on
Sun data: { “source”: “int”, “civdawn”: 1585716213, “nautdawn”: 1585713783, “sunset”: 1585764880, “nautdusk”: 1585769330, “stamp”: 2020092, “latitude”: 51.1, “astrodusk”: 1585771930, “longitude”: 4.417, “civdusk”: 1585766900, “astrodawn”: 1585711183, “sunrise”: 1585718233 }
Geofence: not running

Hi Patrick,

I suspect I’m seeing the same issue. I have some time conditions between 10am and 3pm, it’s showing as last being true at 4pm.

I’ll try and generate log files for you.

Thanks
Tonyreactor logic summary.zip (3.6 KB)