@DaleOne Did you ever find a solution to this?

I am experiencing the same issue but haven't found a solution as of yet. Is there any movement on this issue?

After discussion with DTS, it seems this cannot be reverted. I believe it should be revertible as I did not convert it myself. Seems odd to force it without warning but then be unable to revert it.

Thanks for the information. I'm awaiting a callback from DTS today regarding this. I'm not sure how this occurred. I only realised it had occurred after users started to report issues to me.

Hi, I had Xcode 12 GM change this setting on me without realising. I uploaded a build of my app and released it not knowing my prior setting had been changed by Xcode. Now I cannot revert it. This seems counter intuitive when I did not intend for this setting to be changed. I relied on the iOS app and Watch app being both installed as I am using HomeKit identifiers which are shared if the app is dependent. Is it still not possible to revert? I did not do this myself. Xcode 12 changed the default without warning from prior setting I explicitly made in 11.

No public API for this is available. Some devices implement custom services/characteristics for this though.

This is all dependent on the device implementing it correctly. Hue devices for example return reachable when they are in fact not. The Home app works around this by checking using a characteristic read call then checking the error.

It is an issue when trying to debug our own apps though. Logs from HK should not be shown in our consoles as app developers unless relevant.

For the other HK developers out there, you will need to use the "add a UUID to your developer profile" method and export a development build.

Created FB7779724 regarding this issue.

FB5672565 for active boolean and FB5399040 for notification.

This is 100% needed. Currently we need to read every characteristic of a device to compare it to the HMActionSet to see if it is active. A simple boolean would be great. Along with a way to notify us of it changing like HMAccessory has for characteristic values would be superb.

WatchKit shared identifiers change sometimes when an OS update occurs. Requiring users to re-setup their apps, reboot devices or reinstall the apps entirely to get them back in sync. I cannot provide guaranteed circumstances but an OS update is a regular common reason for this. In terms of the overall request, syncable identifiers are very much required to make anything valuable to customers. Customers expect apps to be able to sync their decisions over multiple devices. Most apps now have to fake a unique identifier using serial number which is deprecated or a mix of name, room and home names etc. This is really not the best solution. I understand they were removed originally for privacy but a identifier could be generated per app + actual Home user to compromise.