Deconz binding shows error after OH (3.3) restart

[Wolfgang_S]

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

deConz with OH3 offline after Raspi restart

hi all Following configuration: OH3 runs on Win 10 (VM) ConBee 2 USB on Raspberry 4b (RaspBee image) deConz binding Issue After restarting Raspberry the thing on OH3 goes offline (communication error) …as long as good. After all is up again the thing stays offline (with this error message). Only action that helps is to disable and enable the thing using paper ui. Question Is there something to configure that tells OH3 to poll for the thing to bring it online after everything started up? …

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?