ComfoConnect LAN C end of sale. Compatibility with successor ComfoConnect Pro?

[helgeklein]

Zehnder apparently stopped selling the ComfoConnect LAN C with library has been developed for. Zehnder's successor is the ComfoConnect Pro. The Pro works with the same app (ComfoControl), so I'm hoping that this library is compatible with the Pro, too.

Can anyone share their experience?

[helgeklein]

I just realized that the ComfoConnect Pro offers Modbus access, so this library might not even be needed...

[peterfication]

I only got timeouts with the ComfoConnect Pro :/ But I haven't investigated deeper yet.

[NStrijbosch]

I have the ComfoConnect Pro just installed and performed the following tests using the CLI:

1. try to discover

 python -m aiocomfoconnect discover

result:

Discovered bridges:
<Bridge 192.168.X.XX, UID=XXXXXXXXXXXXXXXXXXXX>

2. try to register

python -m aiocomfoconnect register --host 192.168.X.XX

result:

WARNING:aiocomfoconnect.bridge:Timeout while waiting for response from bridge
ERROR:asyncio:Task exception was never retrieved
future: <Task finished name='Task-3' coro=<Bridge._connect.<locals>._read_messages() done, defined at /folder/python3.12/site-packages/aiocomfoconnect/bridge.py:109> exception=AioComfoConnectNotConnected('We have been disconnected') created at /folder/python3.12/site-packages/aiocomfoconnect/bridge.py:123>
source_traceback: Object created at (most recent call last):
  File "<frozen runpy>", line 198, in _run_module_as_main
  File "<frozen runpy>", line 88, in _run_code
  File "/folder/python3.12/site-packages/aiocomfoconnect/__main__.py", line 472, in <module>
    asyncio.run(main(arguments), debug=True)
  File "/usr/lib/python3.12/asyncio/runners.py", line 194, in run
    return runner.run(main)
  File "/usr/lib/python3.12/asyncio/runners.py", line 118, in run
    return self._loop.run_until_complete(task)
  File "/usr/lib/python3.12/asyncio/base_events.py", line 674, in run_until_complete
    self.run_forever()
  File "/usr/lib/python3.12/asyncio/base_events.py", line 641, in run_forever
    self._run_once()
  File "/usr/lib/python3.12/asyncio/base_events.py", line 1979, in _run_once
    handle._run()
  File "/usr/lib/python3.12/asyncio/events.py", line 88, in _run
    self._context.run(self._callback, *self._args)
  File "/folder/python3.12/site-packages/aiocomfoconnect/comfoconnect.py", line 82, in _reconnect_loop
    read_task = await self._connect(uuid)
  File "/folder/python3.12/site-packages/aiocomfoconnect/bridge.py", line 123, in _connect
    read_task = self._loop.create_task(_read_messages())
Traceback (most recent call last):
  File "/folder/python3.12/site-packages/aiocomfoconnect/bridge.py", line 218, in _process_message
    message = await self._read()
              ^^^^^^^^^^^^^^^^^^
  File "/folder/python3.12/site-packages/aiocomfoconnect/bridge.py", line 181, in _read
    msg_len_buf = await self._reader.readexactly(4)
                  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/lib/python3.12/asyncio/streams.py", line 750, in readexactly
    raise exceptions.IncompleteReadError(incomplete, n)
asyncio.exceptions.IncompleteReadError: 0 bytes read on a total of 4 expected bytes

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
  File "/folder/python3.12/site-packages/aiocomfoconnect/bridge.py", line 113, in _read_messages
    await self._process_message()
  File "/folder/python3.12/site-packages/aiocomfoconnect/bridge.py", line 252, in _process_message
    raise AioComfoConnectNotConnected("The connection was closed.") from exc
aiocomfoconnect.exceptions.AioComfoConnectNotConnected: The connection was closed.

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
  File "/folder/python3.12/site-packages/aiocomfoconnect/bridge.py", line 121, in _read_messages
    raise AioComfoConnectNotConnected("We have been disconnected") from exc
aiocomfoconnect.exceptions.AioComfoConnectNotConnected: We have been disconnected
WARNING:aiocomfoconnect.bridge:Timeout while waiting for response from bridge
ERROR:asyncio:Task exception was never retrieved

If there are suggestions to try: let me know!

[waverider93]

Hi everyone,

I’ve been experimenting with integrating the ComfoConnect Pro into Home Assistant using its Modbus interface, and while it works for the basics, I’ve run into some limitations:

• Fan values are not available – Modbus only reports a single total airflow value, so you can’t monitor the individual fans.
• Bypass damper status is missing – there’s no way to see if it’s open or closed.

With the current Modbus setup I can still get some useful data into Home Assistant, but the lack of these extra points makes it less powerful for detailed monitoring or troubleshooting or fancy visualizations.

For now, I might either switch back to the old LAN C model (which works great with aiocomfoconnect) or hope that someone with deeper knowledge of the Pro bridge will be able to add full support to aiocomfoconnect / Home Assistant.

Here is a tcp modbus configuration for homeassistant. The addresses are documented in the installer manuel of the comfoconnect pro in section 9.

comfoair_modbus.yaml.txt

Best regards
adrian

[jvanhees]

I did some digging and I figured that the new device works with the same protocol, but the connection / authorization flow is slightly different. I opened a PR with some changes that should fix this, I was able to read all sensor data from my ComfoConnect Pro. #74

The Modbus integration is useful as well, but doesn't expose every variable that we can get in this integration.