Handler lifecycle changed from 2.4 to 2.5?

I recently switched over from 2.4 to 2.5 and I noticed a change in how the lifecycle of the ThingHandler is working. For a specific binding (RME), I noticed that - even as the Thing is ONLINE - initialise() of the handler is called every 2 minutes:

2020-10-15 12:47:08.928 [DEBUG] [rme.internal.handler.RMEThingHandler] - Initializing RME handler.

2020-10-15 12:53:08.636 [DEBUG] [rme.internal.handler.RMEThingHandler] - Initializing RME handler.

2020-10-15 12:55:08.841 [DEBUG] [rme.internal.handler.RMEThingHandler] - Initializing RME handler.

2020-10-15 12:57:08.855 [DEBUG] [rme.internal.handler.RMEThingHandler] - Initializing RME handler.

2020-10-15 12:58:08.529 [DEBUG] [rme.internal.handler.RMEThingHandler] - Initializing RME handler.

2020-10-15 13:00:08.913 [DEBUG] [rme.internal.handler.RMEThingHandler] - Initializing RME handler.

2020-10-15 13:02:08.884 [DEBUG] [rme.internal.handler.RMEThingHandler] - Initializing RME handler.

2020-10-15 13:03:08.674 [DEBUG] [rme.internal.handler.RMEThingHandler] - Initializing RME handler.

2020-10-15 13:04:08.725 [DEBUG] [rme.internal.handler.RMEThingHandler] - Initializing RME handler.

2020-10-15 13:05:08.759 [DEBUG] [rme.internal.handler.RMEThingHandler] - Initializing RME handler.

2020-10-15 13:07:08.735 [DEBUG] [rme.internal.handler.RMEThingHandler] - Initializing RME handler.

Is there something that has changed in between releases? Why is initialize() called on a Thing that is in the ONLINE state? And exactly every 2 minutes ?

Tx

That sort of symptom is usually about the installer failing to install an add-on (and retrying every 2 mins).
In the 2.4 -> 2.5 case, that is often about REST API docs addon, which moved.

Ok, I can relate to that. But with an ordinary binding? and what would be cause of such a failure?

You misunderstand me I think, some other binding or service failing to be installed cause all sorts of other stuff to reinitialize repeatedly. This caught a great many people out for 2.4 -> 2.5 migration, due to inclusions in their addons.cfg file

Right. I am now reading up on some of these discussion (on addons.cfg), but I don’t see a clear path/methodology to find the root cause of this or how to solve it…

Actually usually in the addons.config file in the userdata tree used by OH. For many people addons.cfg file is all comments.