No devices responding with iOS 16.2

[Bergherjar]

Hi Robert.

Homeykit stopped working after installing iOS 16.2 beta and updating to the new architecture of HomeKit.

I have updated all home hubs with the latest betas as well (Apple TVs).

https://www.macrumors.com/2022/10/25/home-app-architecture-update-ios-16-2/

[robertklep]

I saw your post on the community forum about Homebridge still working, which could mean that an upgrade to the latest HAP libraries will hopefully get HomeyKit working again.

[robertklep]

The current test version of the app has updated hap-nodejs dependencies: https://homey.app/a/com.swttt.homekit/test/

[Bergherjar]

I installed version 4.20 and restarted my Homey. It does not seem to work. Still no response from all Homey devices i Apple Homekit.

[Bergherjar]

I installed version 4.2.0 and restarted my Homey. It does not seem to work. I still get no response from all my Homey devices in Apple Homekit. Can it help to completely unistall Homeykit and add it to Homekit again? Would rather not do this since I have many devices and automations.

[robertklep]

Uninstalling/reinstalling will probably not solve any issues. If you're using a Home hub (typically an iPad or Apple TV), try disabling it (on the device, in the Home settings, you can turn it off).

Otherwise, the only solution (other than just wait for a couple of hours in the hope that it will start working again) is to do a HomeyKit reset, which you can do from the HomeyKit app settings page. But that will certainly require setting up everything from scratch again 🙄

[Bergherjar]

Starting from scratch did the trick. It was working fine, except for deleted/hidden devices via homeykit coming back in homekit a couple minutes after being deleted/hidden or just staying in homekit with no response.

[Bergherjar]

Unfortunately after updating to 4.3 it all crashed again. No response from any device added through homeykit.

[robertklep]

@Bergherjar "crashed" or "no response"? Those are two very different things.

If it's "no response": that's to be expected with 4.3. You should do a HomeyKit reset again from the App Settings. Hopefully for the last time 🫣

[Bergherjar]

It was a message saying the app quit unexpectedly this morning. I restarted the app and it is now running, but I get no response from all devices added through homeykit. I did the reset and then started the app again, still no response.

You are referring to this, right:

[robertklep]

@Bergherjar yes, that's the one.

The correct sequence for a reset:

• remove Homey as a bridge/accessory from your home on iOS
• perform the "Clear HomeKit storage step"
• restart the HomeyKit app
• add Homey again as an accessory for your home on iOS (use code "20020200")

[Bergherjar]

Thanks for the info. So I need to start from scratch once again? Will this be the last time? It took me quite a while yesterday 😅

[Bergherjar]

Thanks for all your help, by the way!

[robertklep]

@Bergherjar I cannot guarantee that you don't have to start over again, but with the current test version (4.3.0) I'm trying to prevent that 😅

[OlivierZal]

Thank you very much @robertklep! Rebasing my fork on the 4.3.0 fixed it without having to reset any device.

[OlivierZal]

However I forgot to precise that I needed to upgrade the package-lock.json to make it work locally: https://github.com/OlivierZal/com.swttt.homekit/pull/1/files#diff-053150b640a7ce75eff69d1a22cae7f0f94ad64ce9a855db544dda0929316519R9 (https://github.com/OlivierZal/com.swttt.homekit/blob/44111ae7ed5102dba27eb9ace3782ed4b64393f7/package-lock.json#L9)

[robertklep]

@OlivierZal I stopped pushing node_modules to Github (seemed a bit pointless) so you may need to run npm install after each update (which should also update package-lock.json).

[robertklep]

@OlivierZal ah yes, I hadn't run npm i after updating the version. Shouldn't really be an issue since you need to run it anyway, but I just pushed an updated version anyway 😅