cmqttd closing without error message, network related.

Hi,

Great work on the open source CBUS integration!

I am running the new Wiser 3 (5500SHAC/NAC) as a CNI, with all default settings eg Port 10001. This is a new CBUS test network so not much activity. After a few mins (3-5 mins) the program would exit without a message.

I ran across this issue in docker, then also in a new Ubuntu 18.04.5 VM. Still no error message when enabling DEBUG messages.

Using Wireshark I could see that the SHAC was closing the connection after about 260 seconds of no activity, eg no packets being sent either way.

After changing '--timesync' to 120s, to force packet activity, the connection would stay alive and has not crashed yet (5h so far).

Is there someway to force python to keep the connection open without the time sync? I am happy to run some test code if you don't have access to hardware for testing.

Also a couple of improvement ideas:

have you thought about bringing the verbosity/logging out as a docker environment variable?
an offical docker image, as this will make it easier for Synology docker users (also running docker home assistant, nodered and mosquitto).
A command line option, to not create MQTT topics if not defined in the project file. It gets messy if you create a new group in toolkit, then update cmqttd, HA then has duplicates that can only be cleaned up by deleting the MQTT integration and then reinstalling.

Really appreciate the effort you've put in.

Cheers, Chris

micolous / cbus

cmqttd closing without error message, network related. #24