Nope for websocket, it s the listener, so the third app, that contact the server, connect it, leave and rejoin, the server for websocket never close.
To be sure you can see the websocket connexion on deconz log.
I don’t know if it’s a personal problem but my logs have a time span of 15 minutes (more or less).
If the event happened hours before, logs are useless.
You can try to implement an UPTIME between Deconz and Conbee II to check if there is what I say.
No power issue. I saw System Uptime; Raspberry didn’t reboot.
If I enable log after the issue I cannot see that. Log didn’t record if you don’t enable it before. But I don’t want to destroy the SD card with an infinite log and useless because I lose the data afte 15 minutes.
And… I don’t live in front my screen. If I realize an issue after 8 hours I cannot see that in the log.
The number is a timestamp since last boot time, that can be translated in human readable format with -T (dmesg -T) but seems not always accurate for many reasons (lot a discussion about that in forums)