Integratinon failing

[E-K-I]

Good morning. I woke up to a very hot bathroom this morning. Checked HA and saw that the Xcomfort integration was not working. Found this in the logs any idea what is wrong? 08:15:14] INFO: Starting xcomfortd version 0.43 [08:15:14] INFO: xcomfortd --client-id xcomfort --server tcp://*****@core-mosquitto:1883 --hadiscoveryprefix homeassistant --eprom --file /config/comstick.dpl --hadiscovery --host 192.168.50.194 2021/10/31 08:15:14 Opened USB device 'vid=188a,pid=1101,bus=1,addr=3', packet size 32/32 2021/10/31 08:15:14 Connected to ECI (192.168.50.194:7153) 2021/10/31 08:15:14 Connecting to MQTT broker 'tcp://core-mosquitto:1883' with id 'xcomfort' 2021/10/31 08:15:14 Connecting to MQTT broker 'tcp://core-mosquitto:1883' with id 'xcomfort-1' 2021/10/31 08:15:14 read failed: EOF github.com/karloygard/xcomfortd-go/pkg/xc.(*Interface).Run.func1 /xcomfortd-go/pkg/xc/loop.go:31 runtime.goexit /usr/local/go/src/runtime/asm_arm64.s:1133 2021/10/31 08:15:14 Exiting [WARN] [client] Disconnect() called but not connected (disconnected/reconnecting) 2021/10/31 08:15:14 Terminal error github.com/karloygard/xcomfortd-go/pkg/xc.(*Interface).sendConfigCommand /xcomfortd-go/pkg/xc/loop.go:245 github.com/karloygard/xcomfortd-go/pkg/xc.(*Interface).Revision /xcomfortd-go/pkg/xc/config_messages.go:57 main.run.func1 /xcomfortd-go/main.go:177 runtime.goexit /usr/local/go/src/runtime/asm_arm64.s:1133 [cmd] /run.sh exited 1 [cont-finish.d] executing container finish scripts... [cont-finish.d] done. [s6-finish] waiting for services. [s6-finish] sending all processes the TERM signal.`

[karloygard]

It looks like the ECI disconnected, and the add-on terminated when the connection was dropped, I guess that could be undesirable.

However, it looks like the add-on restarted just before that, any idea why? This is just guesswork on my part, but it's possible that the ECI has a lingering connection from before, and declines new connections. Please turn on verbose mode, then we might see what's going on.

Is this the first time this has happened?

A quick fix is to turn on watchdog for the add-on, then it will automatically restart the add-on when it terminates.