FroniusWattpilotHandler tried updating the thing status although the handler was already disposed

Add-ons Bindings
1

Hi,
I have installed the Fronius Wattpilot binding and configures access to my wallbox. I was also able to successfully configure channels. But the binding is spamming my openhab log now with these messages:

2026-05-12 08:33:00.412 [WARN ] [.core.thing.binding.BaseThingHandler] - Handler FroniusWattpilotHandler tried updating the thing status although the handler was already disposed.

2026-05-12 08:33:00.413 [WARN ] [.core.thing.binding.BaseThingHandler] - Handler FroniusWattpilotHandler tried updating the thing status although the handler was already disposed.

2026-05-12 08:33:15.086 [WARN ] [.core.thing.binding.BaseThingHandler] - Handler FroniusWattpilotHandler tried updating the thing status although the handler was already disposed.

2026-05-12 08:33:15.086 [WARN ] [.core.thing.binding.BaseThingHandler] - Handler FroniusWattpilotHandler tried updating the thing status although the handler was already disposed.

2026-05-12 08:33:18.008 [WARN ] [.core.thing.binding.BaseThingHandler] - Handler FroniusWattpilotHandler tried updating the thing status although the handler was already disposed.

2026-05-12 08:33:18.008 [WARN ] [.core.thing.binding.BaseThingHandler] - Handler FroniusWattpilotHandler tried updating the thing status although the handler was already disposed.

I tried to set the log level of the binding to ERROR but this didn’t change anything.

I’m on openhab 5.1.4.

Anyone an idea?

2

Hi,

suppressing warnings by lowering the log level isn’t really a solution …

I’ll have a look at the disposal logic, seems it has a bug.

3

Aha, this (Shelly Binding - #5254 by ErikDB) is then probably bound to the same issue?

4

Not the information you wanted, but this will be a per-binding issue.

A OH core item in every binding is the ThingHandler. It does the initialization() and also the dispose() method. If something doesn’t get disposed this warning will appear. An example is if a polling job is initialized and not disposed (when the Thing status changes), the polling will continue after the handler is disposed and the warnings will keep coming. I haven’t stumbled on all the issues, but if the thing is reinitialized, I’ve seen duplicate polling from two schedulers and continued warnings. Just an example

5

So there indeed was a bug and I’ve created a fix for it: