Reports Neo Smarthub as already controlled another controller but this does not appear to be the case

[deepcontent]

The problem

I am trying to give HA control over a Neo Smarthub UFH controller. However despite all steps taken, when I attempt to add the controller to HA, I repeatedly get the message:

"The device is already pairing with another co... [Truncated but presumably "controller"] Abort pairing on all controllers, or try restarting the device, then continue to resume pairing."

Steps taken:

1. Removed Smarthub from Home (/Homekit) via Apple Home app.
2. Reset Home settings in ios app.
3. Factory reset the Neo Smarthub.
4. Turned Smarthub off then on.

Other possible factors:

The Neo Smarthub's Homekit code is in the format 12345678, I am inputting this in the format 123-45-678.

Please advise how to rectify.

What version of Home Assistant Core has the issue?

2024.10.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

No response

Link to integration documentation on our website

No response

Diagnostics information

No response

Example YAML snippet

No response

Anything in the logs that might be useful for us?

No response

Additional information

This problem is similar to #114759 marked as complete but no resolution steps given. Running this on a Home Assistant Green

[joostlek]

What integration do you have this problem with?

[deepcontent]

Hi Joost, This is for the Polypipe SmartHub (Bridge) HomeKit Device

[home-assistant[bot]]

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

Code owner commands

Code owners of `homekit_controller` 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 homekit_controller` 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)}}

---

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

[deepcontent]

Thank you. Here's the remaining dialogue's that I get, even though the bridge has been removed from Home(Kit).

[deepcontent]

Any joy with this?

[ianhinder]

Are you sure you are using the right 8-digit code? On my NeoHub, there are two 8-digit codes near each other on the device label. One starting HC- didn’t work. There is another 8 digit code written on the homekit barcode (without dashes). That one is what worked for me. You need to add the dashes. The “already pairing” error seems spurious; my guess is that if ANYTHING goes wrong, it reports that error. I also found that in order to get asked for the code again, I needed to restart HA.

So try:

• Restart HA
• Put in the right code, in case it was the wrong one

I enjoyed a full hour of homekit integration, then when I woke up the next day, it reported all neohub homekit devices as unavailable in HA. 🤦‍♂️

[deepcontent]

Hi Ian, Many thanks for your perpective and tips. I'll try those today. These hubs seem to be very solid as regards the connection between the thermostat and the hub itself but very, very flakey with Homekit! I am wondering whether it's worth having them in Homekit at all. I might look at somehow just controlling them in Home Assistant. (Though how I would do that, I'm as yet unsure!)