homebridge: IOS 16.5 -> Homebridge 1.6.1 -> device can not add to HomeKit , there is not compatible

Current Situation

I have a new installation of homebridge - with a Homebridge-image , homebridge work, but I can not connect to HomeKit. the issue is: device can not add to HomeKit , there is not compatible.

thx2u

Logs

i have no error in the logs

Configuration

{
    "bridge": {
        "name": "Homebridge 1327",
        "username": "xx:xx:xx:xx:xx:xx",
        "port": 51899,
        "pin": "xxx-xx-xxx",
        "advertiser": "avahi"
    },
    "accessories": [],
    "platforms": [
        {
            "name": "Config",
            "port": 8581,
            "platform": "config"
        },
        {
            "name": "Hue",
            "anyOn": true,
            "effects": true,
            "hosts": [
                "xx.xx.xx.40",
                "127.0.0.1:4530"
            ],
            "hueMotionTemperatureHistory": true,
            "lights": true,
            "linkButton": false,
            "nativeHomeKitLights": true,
            "nativeHomeKitSensors": true,
            "resource": true,
            "sensors": true,
            "users": {
                "user": "pass"
            },
            "wallSwitch": false,
            "platform": "Hue"
        },
        {
            "host": "xx.xx.xx.250",
            "port": 80,
            "username": "xxxx",
            "password": "xxxxxxx",
            "options": {
                "stairwellSwitch": "pulse",
                "moodSwitches": "none",
                "radioSwitches": 1,
                "alarmSystem": "delayedon",
                "alarmTrigerLevel": 5,
                "autoLock": 1,
                "autoLockDelay": 5
            },
            "platform": "LoxoneWs"
        },
        {
            "name": "Camera FFmpeg",
            "cameras": [
                {
                    "name": "Home",
                    "videoConfig": {
                        "source": "-i rtsp://xx.xx.xx.xx:8554/mjpeg/1",
                        "stillImageSource": "none"
                    }
                }
            ],
            "platform": "Camera-ffmpeg"
        }
    ],
    "disabledPlugins": [
        "homebridge-loxone-ws-adv-cstm"
    ]
}

Environment

  • OS: Raspbian GNU/Linux Bullseye
  • Software: Homebridge
  • Node: v18.16.0
  • npm:

Process Supervisor

hb-service

Additional Context

No response

About this issue

  • Original URL
  • State: closed
  • Created a year ago
  • Reactions: 1
  • Comments: 38 (7 by maintainers)

Most upvoted comments

There are so many completely different issues here. Please help us to help you by not posting new issues in a GitHub thread that’s about a different issue. If you have a different issue, create a new GitHub issue. Otherwise it’s impossible to follow.

@JulyIghor - devices adding successfully then disappearing a couple of minutes later (when the phone does an iCloud sync) is an endpoint/iCloud cache coherency issue. If you are using iOS 16.5, there is a known bug whereby adding new devices if you are not the home ‘owner’ causes this. My 95% guess is this is your issue. Other 5%: sign out of iCloud on your iPhone and HomeKit hubs, then back in. This will rebuild the internal HomeKit state.

@homeautomationch - this is not a Homebridge (or Home Assistant) issue. If you can access the Homebridge machine (e.g. the UI) by IP but adding to HomeKit gives ‘unable to find accessory’, 100% of the time it means you have a multicast routing issue on your network. First step is to run Homebridge natively on your machine - not in Docker or a VM. If that doesn’t fix things (and 80% of the time it will not), it means your network isn’t set up to route multicast traffic properly. Home routers purchased in the last 5 years will do this automatically, and not require any setup. If you are using an enterprise router setup/VLANs/discrete APs/etc. you will need to set up multicast forwarding between the network segments. Look for settings called ‘multicast DNS’, ‘IGMP proxy’, ‘IGMP enhancement’ etc. and set those correctly. If this is beyond your ability, just get a good mesh network e.g. Eero or Google Wi-Fi and everything will ‘just work’ out of the box.

@badriram - you also have a multicast routing issue. After adding devices to HomeKit on your iPhone, if you are using the ‘new architecture’, as soon as an iCloud sync occurs (usually 1-2 minutes after adding), control will transfer from iPhone->device to active HomeKit hub->device. If your iPhone can reach your Homebridge machine via mDNS but your active HomeKit hub cannot reach your Homebridge machine via mDNS, then devices will add OK but after a minute or two, go to ‘No Response’. See my comment to @homeautomationch.

Finally, ‘out of compliance’ means that the device is initially setting characteristics outside the allowed range. For example a thermostat reporting a temperature of -9999 will produce this message. It is a plug-in issue. Find the responsible plug-in using any method of your choice (bisect, remove one by one, etc.) and reach out to the plug-in author. iOS releases tend to be more strict enforcing this as time goes on, and iOS 16.5 validates more comprehensively than iOS 16.4. It is not a Homebridge issue.

Brand new New homebridge setup today ios 16.5.1, Synology running homebridge 1.6.1 off docker… I cant add to Apple homekit manually or via QR code… each time after a long wait I get “Accessory not Found”. FYI… Interestingly also tried HomeAssistant and same experience.

On Homebridge discord I saw a reply from @.thelegend71 (#kudos) changing mDNS to “Ciao” resolved the issue and now homekit is recognising my Homebridge setup 😃

Brand new New homebridge setup today ios 16.5.1, Synology running homebridge 1.6.1 off docker… Apple home does not allow add accessory manually or via QR code same error message as https://github.com/homebridge/homebridge/issues/3373#issuecomment-1558438317 I think we urgently need a fix for this new ios / Home version we know Apple somewhat mandates updates > any chance an someone could please prioritise… i see several forums talking of this issue and not yet realising it is cuteness incompatible. 😢