HoneywellHome/Resideo homekit integration PROA7Plus

Third party integrations
1

Hi HA community,

I am trying to integrate a HoneywellHome/Resideo security alarm panel PROA7Plus using the homekit device integration. I’ve tried this with HA running on a RPI5 and in VMware and am arriving at pretty much the same result. I am able to discover the device in HA, but as soon as I try to add it after putting in the pairing code, I get an error stating “Invalid flow specified”. Strangely, the panel itself shows “Success. ProSeries Controler successfully added as an accessory in Apple Home”

Some data from the logs:

Log details (ERROR)
Logger: aiohomekit.utils
Source: /usr/local/lib/python3.13/site-packages/aiohomekit/utils.py:45
First occurred: 4:13:24 PM (6 occurrences)
Last logged: 4:21:18 PM

Failure running background task: Task-341
Failure running background task: Task-474
Failure running background task: Task-476
Failure running background task: Task-479
Failure running background task: Task-651
Traceback (most recent call last):
  File "/usr/local/lib/python3.13/site-packages/aiohomekit/utils.py", line 40, in _handle_task_result
    task.result()
    ~~~~~~~~~~~^^
  File "/usr/local/lib/python3.13/site-packages/aiohomekit/controller/ip/pairing.py", line 409, in _process_config_changed
    await self.list_accessories_and_characteristics()
  File "/usr/local/lib/python3.13/site-packages/aiohomekit/controller/ip/pairing.py", line 175, in list_accessories_and_characteristics
    await self._ensure_connected()
  File "/usr/local/lib/python3.13/site-packages/aiohomekit/controller/ip/pairing.py", line 155, in _ensure_connected
    raise AccessoryDisconnectedError(
        f"Ensure connection returned but still not connected: {connection.hosts}:{connection.port}"
    )
aiohomekit.exceptions.AccessoryDisconnectedError: Ensure connection returned but still not connected: ['192.168.0.206']:50200

Appreciate any help on this!

2

In case someone comes across this issue and burns hours (or days) in frustration, this is what I observed:

  1. For some odd reason, the PROA7Plus cannot be the first homekit device in HA
  2. I added a Vizio TV that supports Homekit and it created a device in HA
  3. I put the PROA7Plus in the mode to be discovered; after discovery by HA, I attempt to pair it and I have the same issue

HomeKitAddFromDiscovery
HomeKitAddFromDiscovery2240×1464 155 KB

HomeKitAddFromDiscovery2
HomeKitAddFromDiscovery22216×1310 163 KB

5. I choose to click on “ADD ENTRY” and follow the same procedure of entering the homekit pairing code and it works like a charm:

WhatWorked_1
WhatWorked_12170×1058 85.6 KB

WhatWorked_2
WhatWorked_21524×1094 73.2 KB

WhatWorked_3
WhatWorked_32094×1390 153 KB

I’m not sure what causes this, but hopefully this helps someone.

Hope this helps.

3 Likes
3

Fabulus work Rohit. For those of us who do not live in the apple world, how do we integrate the ProA7Plus?

I wonder what if we dont use ProA7Plus at all. Can we bring the Z-Wave sensors from Honeywell/Resideo directly into HA?

Any pointers?

Anil

4

Really can’t thank you enough @rohit!!! I spent hours trying to figure this out and your little “trick” worked first time. So deeply appreciate you posting this! (Had the same problem with the Brilliant light switch system and this solved it)

5

Does this work even if we dont have apple devices? I mean go to ha directly as a homekit device and from there on android using port 8123?

6

Thank you for sharing, @rohit! Question. Did you do the HomeKit Device bridge AND the Total Connect HA Integration? If so was it worth it?

7

This PR fixes this issue Prevent zeroconf service removal from aborting HomeKit pairing flows by odlund · Pull Request #162262 · home-assistant/core · GitHub