It looks like @marcel_verpaalen is already working on your problem No. 1.
The 2nd problem sounds really odd. Currently I have to admit that I do not have a clue what could be the cause of it. But I never heard about a relation between updating a configuration of a thing and refreshing / reloading rule files before. @dominicdesu Just to be clear: You are talking about reloading rule files? Do you? I am asking because in your linked issue you are talking about triggering startup rules which from my point of view is something different.
I am aware of a feasible issue related to configuration updates: It is possible to create an interminable loop - e.g if the ThingHandler calls updateConfiguration() from its initialize() method, because a configuration update leads to a new initialization of the thing.
I was assuming this reloads the rules and therefore also triggers the “System started” rules?
I hope I’ll find some time over the next few days to further debug this issue. Also note that I didn’t had this behaviour in OH 2.4…
Okay, after removing all MAX things in the PaperUI and rediscovering them, there seems to be no refreshing of rules anymore…
Maybe there was some internal incompatibility between the MAX things which have been added in OH 2.x and 2.5…
Anyways, thanks everybody for your support!
… but not for things, correct?
By any chance, could there be an (unwanted) link in the core such as a backpointer that results in changes to items, too, when the thing that an item is linked to gets changed as we have it here ?
So the reason for the strange behavior here was the (unnecessary, soon to be removed) update to the maxcube thing ? Then why did that not happen to everybody ?
Now I’m confused. After I’ve removed and readded the max things, the “System started” rules are not executed anymore, neither periodically (when the MAX binding updates the thing configuration) nor if I manually change the thing configuration in PaperUI.
So it doesn’t seem that updates to thing configurations trigger the “System started” rules, which would also match with the documentation.
I just experienced an all-rules-reload after I deleted an exec binding thing that was linked to by an item. Duh. I think we should file that as a bug, but how ? What’s the exact conditions this happens under ?
I have not yet seen it happen when I delete a thing. However, what I think happend in your case that deleting the thing caused an update to the item that triggered the reload.
I agree this is a bug. I think it was introduced in 2.5 m6.