That’s already in the default log file. I only showed which line to change to adjust the log level of the existing events logger.
Maybe other recommendations? There are not more messages in TRACE log level.
I created a TRACE using:
openhab> log:set TRACE org.eclipse.smarthome
openhab> log:set TRACE smarthome.event
openhab.log (23.0 KB)
There is a removal of thing “shelly:shellyrgbw2-color:662526” at 2019-12-19 13:38:59.222
and ‘System started’ event at 2019-12-19 13:39:06.726 (execution of initialize.rules).
Well, the logs do show that the Rules are being refreshed. The refresh will trigger the System started event. You need to watch that log and see if you can find some sort of correlation between what happens immediately before those Refreshing log statements each time they occur.
I started to notice this behavior in 2.5M6. I have created a ticket on Git for the core, but given where OpenHAB is headed it is unlikely to get much attention. Since this issue is now appearing in 2.4, I wonder if it is a binding or add on change that is affecting both 2.4 and 2.5, and is causing a System start to trigger, and not changes to the core? For now I just made some changes to my rules so that lights and alarms don’t go crazy every time I make change to an item or thing.
I do not use text file for Things. OH just reloads my Items file when it is changed. I am on 2.5 Stable though.
I don’t use thing files for most of my devices either. I have hybrid approach to items. This issue occurs with PaperUI for me.
Aaah…forgot to mention - I’m on OH 2.5 stable since 2 days. But is the same behaviour. The trace log today was created on OH 2.5.
@rlkoshak Unfortunately I cannot see the reason for refreshing all rules in the log. In my opinion there is nothing interesting between Removed element and first Refreshing resource . But I can provide the full log if necessary.
I am also running 2.5 stable now and the issue persists but I just work around it.
I do not have too much devices but can reproduce it on two various bindings: Shelly and Sony.
My thought was that something changed across both 2.4 and 2.5 at about the same time. Only thing I could think of was addons. I don’t use either of those bindings. Do you have MQTT or other addon/actions enabled? This may just be a rabbit hole.
Any jar files in the addons folder?
Nope. None for me.
MQTT is not enabled.
Installed addons:
openHAB Add-ons :: Bundles :: Astro Binding
openHAB Add-ons :: Bundles :: Exec Binding
openHAB Add-ons :: Bundles :: Mail Binding
openHAB Add-ons :: Bundles :: Network Binding
openHAB Add-ons :: Bundles :: OpenWeatherMap Binding
openHAB Add-ons :: Bundles :: IO :: Java Sound Support
openHAB Add-ons :: Bundles :: IO :: openHAB Cloud Connector
openHAB Add-ons :: Bundles :: IO :: Web Audio Support
openHAB Add-ons :: Bundles :: Transformation Service :: Exec
openHAB Add-ons :: Bundles :: Transformation Service :: Map
openHAB Add-ons :: Bundles :: Transformation Service :: RegEx
openHAB Add-ons :: Bundles :: Shelly Binding
openHAB Add-ons :: Bundles :: Sony Binding
The mentioned Shelly and Sony Binding JAR and californium-core-2.0.0.jar + element-connector-2.0.0.jar as requirement for Shelly Binding.
The Shelly binding is a 2.5 binding and may have issuing 2.4. You should install on 2.5 rather than use the jar to be sure you have the proper build.
There are also official Sony audio bindings for 2.4 and 2,5. Why did you manually install it?
It is possible those manually installed bindings are causing an issue.
I’m the QA for Shelly Binding developer, so I’m using the SNAPSHOT.
Not the Sony Audio Binding but Sony Devices Binding which is still not included in stable OH build:
Just removed all JAR’s from addon folder and stopped/uninstalled the bindings/libs. Now only stable addons are installed.
I removed a Netwok Binding Thing (pingable network device) and the refresh of rules still happens.
My installed add-ons that overlap yours are:
openHAB Add-ons :: Bundles :: Astro Binding
openHAB Add-ons :: Bundles :: Exec Binding
openHAB Add-ons :: Bundles :: Network Binding
openHAB Add-ons :: Bundles :: IO :: openHAB Cloud Connector
openHAB Add-ons :: Bundles :: IO :: Web Audio Support
openHAB Add-ons :: Bundles :: Transformation Service :: Exec
openHAB Add-ons :: Bundles :: Transformation Service :: Map
openHAB Add-ons :: Bundles :: Transformation Service :: RegEx
I also have
openHAB Add-ons :: Bundles :: DarkSky Binding
which is very similar to OpenWeatherMap Binding
I also have several other add-ons installed, but if it is an add-on that is causing the System started trigger, then it has to be something we both have installed. You have ruled out the Network binding so it would leave one of the others listed above as the likely culprit, if any.
I meant I just removed one (of many) thing of type “Network Binding” - one pingable device. The Network Binding is still installed and active. And the issue is still present although the other both add-ons from addon folder are uninstalled.