Deconz binding shows error after OH (3.3) restart

After restarting my OH (3.3) installation faced an error with the deCONZ bridge which showed an error message (destroyed container cannot be restarted…)
There’s already a bug on github on that topic Link
Restarting the deCONZ bridge item using the UI inside OH fixes everything.
Any ideas how do deal with that …any way to restart the bridge item automatically?

Greets,
Matt

PS: under OH 3.2 never faced this issue, so it has to be something which came with the latest release

I have the same problem.
Any progress on this?

Regards,

Herman

Just updated to 3.3 from 3.2 and faced the same issue

Same here. After Updating from 3.2 to 3.3, the deCONZ bridge showed this error message.

Same error message was reported earlier for other versions of OH.
One of these threads is this one:

In that case it was reported that the clock was not synchronized.

Besides that in that thread @J-N-K mentioned:

I have only seen this “destroyed container could not be restarted” error on my test or production system once. That was when I had two openHAB instances running with the same API key. Could that be the case?

Thank you Wolfgang
…the first mentioned case was one I’ve created. It was slightly different from this one …but the hint with the time is something I need to watch for, but now on the side of OH (win) not Pi.
Last time I’ve restarted OH there was no issue at all …will have an eye on that.
The second mentioned case is impossible in this config because OH will get restarted with the VM where it lives …but good to know that there could be issues with two instances of OH. Is there a case where somebody wants to run two instances of OH (except for testing)?