It would not bother me if I had not occasional communication problems to the ccu. Errors range from Jetty start failed or like now none at all. Thats the worst as it fails silently.
I can operate everything from the CCU but not from openhab.
Things in the Inbox are basically inert. Beyond the initial scan that caused them to be discovered in the first place they don’t do anything. They can’t be the cause of your communication problems because they don’t cause any communication in the first place.
If you ignore them it delete them from the inbox so they come back?
Your discovery issue is coming from the CCU bridge Thing.
In your file, you gave it the ID „ccu“ whereas it is discovered with a serial number.
This is an representation property issue within the binding and should not happen. You should file an issue on github.
Solution for you would be to change the ID of the CCU Thing, but you need to change that part in the channels of all items too. As you use textual config, it is a simple search and replace.
But as @rlkoshak already pointed out, this will not solve your communication issue and should be filed as a second issue. If doing so, please provide TRACE logs from when the problem occurred.
most things in the inbox did not re-appear after they have been deleted.
If you, like myself, do not get that right at the first attemt, each try will give you yet another set of Inbox items.
To delete them go to the openhab-cli: docker exec -ti openhab /openhab/runtime/bin/client
and execute inbox clear <<- that would be a useful button in the web interface
I narrowed down my communication issues to a Jetty start failed message that came from Caused by: java.io.IOException: Failed to bind to /0.0.0.0:9125
The issues could be triggered by re-starting the openhab container.
Odd enough that could be fixed by restarting piVCCU. Long story short, sudo apt-get update &upgrde apparently fixed it. For now.
A bind exception like that means something else is already listening on that port (9125 in this case). Maybe an old instance of the add-on didn’t shutdown properly or something like that?
