Comfoconnect integration is using a deprecated library to talk to the Zehnder

[ams2990]

The problem

pycomfoconnect has been deprecated since 2022. The replacement is aiocomfoconnect, from the same author.

I wasn't able to find a bug tracking the upgrade -- is this change of interest to the integration maintainers?

The reason I noticed this I wanted to control non-fan aspects of the Zehnder from automations. This is technically possible via pycomfoconnect today, but is far nicer with the updated library. For instance, I wanted to control the bypass state. I found someone else who wanted to do the same thing (michaelarnauts/comfoconnect#30), and the solution is much cleaner in aiocomfoconnect -- you just call set_bypass.

What version of Home Assistant Core has the issue?

core-2025.3.4

What was the last working version of Home Assistant Core?

No response

What type of installation are you running?

Home Assistant OS

Integration causing the issue

comfoconnect

Link to integration documentation on our website

https://www.home-assistant.io/integrations/comfoconnect/

Diagnostics information

No response

Example YAML snippet

Anything in the logs that might be useful for us?

Additional information

No response

[home-assistant]

Hey there @michaelarnauts, mind taking a look at this issue as it has been labeled with an integration (comfoconnect) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of comfoconnect can trigger bot actions by commenting:

• @home-assistant close Closes the issue.
• @home-assistant rename Awesome new title Renames the issue.
• @home-assistant reopen Reopen the issue.
• @home-assistant unassign comfoconnect Removes the current integration label and assignees on the issue, add the integration domain after the command.
• @home-assistant add-label needs-more-information Add a label (needs-more-information, problem in dependency, problem in custom component) to the issue.
• @home-assistant remove-label needs-more-information Remove a label (needs-more-information, problem in dependency, problem in custom component) on the issue.

_{^{(message by CodeOwnersMention)}}

---

comfoconnect documentation
comfoconnect source
_{^{(message by IssueLinks)}}

[ams2990]

Ah, @michaelarnauts, I didn't notice that you owned the Home Assistant integration. I feel certain you're quite familiar with the situation with the two libraries considering you wrote both of them 🙂

[michaelarnauts]

Indeed. There is also a HACS integration I wrote to replace the one in home assistant, but I don't have the energy and time to handle all the steps that are necessary to replace the integration in core.

If someone is interested in helping with this, please do so :)

[ams2990]

Ah, I see: https://github.com/michaelarnauts/home-assistant-comfoconnect. You would just want to replace what's in the repo with that (as-is, to the extent that's possible)?

I've never worked with Home Assistant before, but that's doesn't sound terribly difficult. The config migration seems like it's got the most challenging bits. What other issues do you foresee?

[michaelarnauts]

I'm not sure what's best to do here. I think it's best to just replace it, but that requires tests, and I don't have those. It will also be a breaking change, and I don't think the entities are migrated correctly, so you'll loose history of your sensors.