homebridge/homebridge-config-ui-x

Homebridge v1.8.0 broke connectivity to homekit

Closed this issue · 3 comments

Describe The Bug

Similar to this issue: #2045

When I upgraded to homebridge v1.8.0 I immediately lost connectivity to homekit. Homebridge and homekit worked fine leading up to the update. I did not update on the host - I just upgraded homebridge via the UI.

Environment details:

  • All my accessories are still connected and work via homebridge
    • The issue is just between homebridge and homekit
  • I run homebridge in an ubuntu 22.04 VM on a VLAN, where my homekit devices are in the same subnet and VLAN, but mostly connected through a different WAP.
  • I have mdns reflection enabled using avahi on pfSense.

Troubleshooting steps:

  • Trying other mdns providers in homebridge all fail as well (bonjour, ciao, resolved)

Logs

Looking at my logs the following day I saw:
The selected advertiser, "avahi", isn't available on this platform. Reverting to "bonjour-hap"

This is strange, as it was working fine leading up to the update and that error wasn't there before the update.

I've installed avahi-daemon on the ubuntu host which cleared up that error, but no connectivity.

No other logs seem to stand out.

Config

{
    "bridge": {
        "name": "Homebridge 63E0",
        "username": "***",
        "port": 51808,
        "pin": "***",
        "advertiser": "avahi",
        "bind": [
            "ens18"
        ]
    },
    "platforms": [
        {
            "name": "Config",
            "port": 8581,
            "platform": "config"
        },
    ]
}

Homebridge UI Version

4.56.1

Homebridge Version

1.8.0

Node.js Version

20.12.2

Operating System

Ubuntu / Debian (or a variant)

Environment Info

Other (specify in description)

Raspberry Pi Model

None

Deleting homebridge in homekit and resetting the homebridge accessory under settings seems to have fixed it.

I had to re-add the homebridge and redo all my settings, but connectivity is restored.

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

This issue has been closed as no further activity has occurred.