HomeKit HomeKit Disabling Automations?

[JWreck]

HomeKit keeps disabling automations, and I’ve narrowed it down to only happening when the iPad has Home enabled for iCloud. Some of my devices don’t have the same name on the iPad as it does on my iPhone, or my wife’s iPad Air 2.

I’ve gone so far as to reset and erase the iPad and still no luck.

Apple TV 4K, iPad Pro 9.7”, and iPhone X all running latest 11.2.1 update.

Any thoughts?

Video link to the disabling of the automation without my interaction:

 

[robnbill]

HomeKit keeps disabling automations, and I’ve narrowed it down to only happening when the iPad has Home enabled for iCloud. Some of my devices don’t have the same name on the iPad as it does on my iPhone, or my wife’s iPad Air 2.

I’ve gone so far as to reset and erase the iPad and still no luck.

Apple TV 4K, iPad Pro 9.7”, and iPhone X all running latest 11.2.1 update.

Any thoughts?

Video link to the disabling of the automation without my interaction:

We have HK enabled on multiple devices - and it always works fine - all rooms and devices are the same - and named the same - across all devices.

I thought all devices using HK automatically use iCloud - I didn't think there is a setting for it.

Are all your iOS devices, incl. your ATV 4K, using the same Apple ID with 2FA enabled? They would have to in order to have the same HK devices, names and automations.

Other than that, I have no idea why your automations simply turn off. Curious as to what you find out - we use an ATV 4K as our primary hub too.

Added: And is iOS Keychain on for all devices?

 

[cynics]

While I never seen that happen for me are your sunset automations conflicting with each other?

Could be device specific with the HomeKit framework that if a device is told to come on twice the second is disabled.

 

[wesley96]

There’s also a possibility of synchronization gone awry. All the devices under the same account automatically gets the settings and automations sync’ed, but certain devices may be slow to do so and decide to enforce an older state, resulting in deletion of new data. I’ve seen this happen a few times, so I had to configure an automation a couple of times for it to stick.

 

[JWreck]

Finally got it working. Wiped my iPad and set it up new, rather than restoring from backup or using the quick setup. Good opportunity to clean up a bunch of stuff I didn’t use anyway, but annoying that I was forced to do so.

 

[JWreck]

Well surprise surprise...I’m having this issue again. Randomly some exterior automations are disabling. Last time I had to wipe my iPad to get it to stop.

I’m tempted to open a case with Apple but I fear they’ll likely be useless and tell me to restore my devices first anyway.

Is no one else having this problem?

 

[blastum]

I know its late, but I've been having the same problem. I see what's going on and how to fix it:

If you look at the automation with Home 3 app (search for Matthias Hochgatterer in the iOS App Store), there is a "Disable after execution" flag. I don't see this in the apple home app. Sometimes, this flag gets set. I don't know why, perhaps it happened when I upgraded to Catalina or iOS 13 betas, but can't guarantee that. Anyway, turning that flag off and reenabling the automation has done the trick for me. As far as I know, this can only be done from the Home 3 app.

I don't believe you can do this from either the Apple Home app for iOS or for Mac. I don't know why Apple would not expose so important a flag. You may have to go pay for the other app.