Zwave Controller goes offline and can't recovery after night

It’s definetly not the heal time - the nodes disappeared again …
The only thing i remember doing was decreasing the temperature at one thermostat manually (might have caused 10 update messages …) though it wasn’t node 10…

2021-03-04 08:01:54.666 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing 'zwave:device:57dc600655:node10' changed from ONLINE to OFFLINE (COMMUNICATION_ERROR): Node is not communicating with controller
2021-03-04 08:01:54.985 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing 'zwave:device:57dc600655:node8' changed from ONLINE to OFFLINE (COMMUNICATION_ERROR): Node is not communicating with controller
2021-03-04 08:01:54.985 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing 'zwave:device:57dc600655:node4' changed from ONLINE to OFFLINE (COMMUNICATION_ERROR): Node is not communicating with controller
2021-03-04 08:01:55.714 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing 'zwave:device:57dc600655:node6' changed from ONLINE to OFFLINE (COMMUNICATION_ERROR): Node is not communicating with controller
2021-03-04 08:01:55.922 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing 'zwave:device:57dc600655:node7' changed from ONLINE to OFFLINE (COMMUNICATION_ERROR): Node is not communicating with controller
2021-03-04 08:02:13.686 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing 'zwave:device:57dc600655:node2' changed from ONLINE to OFFLINE (COMMUNICATION_ERROR): Node is not communicating with controller
2021-03-04 08:09:00.405 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing 'zwave:device:57dc600655:node5' changed from ONLINE to OFFLINE (COMMUNICATION_ERROR): Node is not communicating with controller

I’ve looked up the other forum post:

the logging option was

log:set DEBUG org.openhab.core.io.transport.serial 

and i previously got the same result. I’ll enable it now with an OH restart in order to check if other log entrys appear once the error occurs.

Reading the post further i also checked permissions of the LCK file in the docker image.
It seems that the permissions of the lock file might be ok …

root@openhab-3:/openhab# ls -l /var/lock/                                                                             
total 4                                                                                                               
-rw-r--r-- 1 openhab openhab 11 Mar  4 09:21 LCK..ttyACM0