Startup rules are executed even though OH already running for hours

Hi,

just had the situation that my startup rules were executed even though OH2 was running since a few hours:

2016-09-17 14:57:00.628 [DEBUG] [sistence.rrd4j.internal.RRD4jService] - Stored 'WeatherTemperature' with state '20.40' in rrd4j database
2016-09-17 14:57:00.639 [DEBUG] [sistence.rrd4j.internal.RRD4jService] - Stored 'Aeon_CO_Temperature' with state '24' in rrd4j database
2016-09-17 14:57:00.649 [DEBUG] [sistence.rrd4j.internal.RRD4jService] - Stored 'Thermostat_BA_SetTemp' with state '4.5' in rrd4j database
2016-09-17 14:57:28.821 [INFO ] [thome.io.rest.core.item.ItemResource] - Received HTTP DELETE request at 'items/zwave_device_a367f17a_node9_meter_watts' for the unknown item 'zwave_device_a367f17a_node9_meter_watts'.
2016-09-17 14:57:49.252 [INFO ] [smarthome.model.script.Heating.rules] - Setting default values at startup
2016-09-17 14:57:49.279 [INFO ] [smarthome.model.script.Heating.rules] - Current month is 9
2016-09-17 14:57:49.295 [INFO ] [smarthome.model.script.Heating.rules] - Setting Heating summer mode to ON
2016-09-17 14:57:52.860 [INFO ] [marthome.model.script.Presence.rules] - Setting default values at startup
2016-09-17 14:58:08.127 [INFO ] [marthome.model.script.Lighting.rules] - Setting default values at startup

Last action I did was trying to delete an auto-generated item at 14:57:28. (which failed for some reason…)

I am running OH2 just one or two snapshots before the beta4 release.
Any idea what could have caused this?

This is one of the startup rules:

rule "Set default presence settings on startup"
when
    System started
then    
    logInfo("Presence.rules", "Setting default values at startup")
end

Any time that that something happens that causes rules to be reloaded the System started rules will execute. So if you edited that rules file or otherwise edited rules it may have triggered the reload.

Keep an eye on it. If it persists even when not editing rules or items then come back here with more details and open an issue. You might put your logging into trace mode to get more details immediately before the errant System started rules execution.

2 Likes