HomeKit not working with iOS 16.2

I published a test version of the app: HomeyKit | Homey

Please let me know if it works (also before updating to the new Home architecture, if you still haven’t updated).

Don’t know but I still download 4.1.10, has it been published correctly?

The test page is showing 4.2.0?

Also when I install it:

Ah ok, still in test page, I was thinking it has been release in public.

I’ve ran into an issue which may require pushing a new test version of the app that will reset the internal storage (which means having to set up all your devices in Home again).

There’s also an additional issue that prevents me from making 4.2.X stable soon (and it may also mean that once it is upgraded to stable, you have to again set up Home again).

Test version 4.2.1 has been published: HomeyKit | Homey

I just pushed a version to Github that should perform a migration from the old storage to the new storage, which means that (at least in theory) it should be possible to go from the stable version of the app to the test version of the app and back again, while retaining the current device setup.

Anyone interested in testing this?

You need to have a working command line setup for Homey apps to be able to do this, which I explained in this post. However, the download link for the code (and also the directory in the ZIP file) is now different than the one mentioned there:
https://github.com/swttt/com.swttt.homekit/archive/refs/heads/master.zip

Eventually, everyone running the current test version will still be required to do another HomeKit reset.

Only the devices added by our Homey (acting as HomeKit bridge)?

Or all (native/Homebridge) HomeKit devices?

Only the devices added through Homey.

I just tried the following with my own Homey:

  • installed the current stable
  • set up HomeKit on iOS (moved some devices to separate rooms, etc)
  • updated to the new test version (4.3.0, not released to the app store yet)
  • the setup was migrated properly (all the devices were still in the correct room)
  • went back to the current stable (4.1.10)
  • the setup was still working as expected

So I’m going to push this as a test version. For current test users, this may cause a reset of the internal storage and require a re-setup for devices imported from Homey. Hopefully for the last time, because my intention is to make this new test version stable.

Hi Robert,

Have used the app with no issues for sone years now. Thank you for youre work.

Upgraded My iOS devices to 16.1 and then the no response issue whas a fact.

Read along this thread an decided to install the test version of homeykit. I then resett the storage but still have the no response issue…

Do i need to delete the bridge in HomeKit and add it again to get things working again?

Thank you in advance.

If you have reset the storage you should take the following steps:

  • remove Homey from HomeKit
  • restart the HomeyKit app
  • add Homey to HomeKit again (with pairing code 20020200)

Thanks,

All devices now are populated and responses are back.

Do i need to do the same when you upgrade the official app?

Should i wait untill that is in place before i start configuring HomeKit again?

It’s my intention to make the current test version the stable version, so you shouldn’t have to reconfigure again (famous last words :wink:).

I don’t know when that switch will take place, because I’d like to check first if the current test version also still works with iOS 15.

What’s the current status?

Apple released the release candidate of iOS 16.2 earlier today, so the final will probably be available next week…

AFAIK the test version works, but I’d rather wait with promoting it to stable until I get a bit more feedback.

In any case, this might be a good time to consider switching to HomeKitty :wink:

I guess you refer to this?

And not this?

I was not aware of either; how do I migrate without breaking all iOS automations that use devices offered by HomeyKit?

What’s the status of the new (iOS 16.2) HomeKit architecture support for HomeKitty?

Might have to wait:

That sensor is the main reason I use this…

You can’t, HomeKit doesn’t offer such a thing.

It should work (but I haven’t tested this myself, I don’t run iOS pre-releases).

That sensor is supported and confirmed working by others, @Ryan’s issue is likely local.

1 Like

Excellent!

In test only or also in stable?

Both, but the current stable has some other issues that are solved by the test version, so if you want to test it either wait for the new stable to go live (hopefully today or tomorrow) or install the test version.

1 Like