HomeKit Problems I had after 16.4 updates

[CyberDavis]

I was one of the ones who updated to the new architecture with 16.2 before the option was pulled.
Since then I'd had various problems such as...

1. Automations intermittently failing
2. Netatmo Carbon Monoxide sensor constantly being unavailable in Homekit but ok in own app

So I was hoping that 16.4 would resolve my issues and restore the pretty good reliability I had previously.
However, the journey to better operation has not been straightforward.

1. Automations still seemed unreliable for two areas. Only way to resolve was to delete automations and recreate them.
2. One Nanoleaf Essentials light was especially problematic with very slow response, it had previously worked well with no delays or errors.
   Tried removing it and re-adding but HomeKit could not find it even after waiting some time.
   Fortunately I had a spare Nanoleaf bulb I was going to use elsewhere, I added this and it all seems ok now.
   Autromations work as expected and no delays present in operation.
3. Aqara camera and blind visible and working from iPad but not iPhone. All devices at home are at latest version so it is a bit odd.
   I guess I'll try removing them and re-adding them when I have some time to spare.
4. Netatmo sensor has been added back and so far seems stable and responsive.

So whilst after the above issues things do seem better it has not been a smooth and trouble free journey.
Hopefully Homekit can now get on with improving and providing stable operation.

 

[iStorm]

For the slow response time in #2, you could have checked the Nanoleaf app to see if the bulb was using Thread. If it wasn't, it'd be using Bluetooth and would explain the slow response time. Just a tip to remember next time.

Also, did you reset the Nanoleaf bulb before trying to add it back? Removing it is not enough. It needs to be reset before it can be paired with your Home again (as with most HomeKit devices).

 

[CyberDavis]

For the slow response time in #2, you could have checked the Nanoleaf app to see if the bulb was using Thread. If it wasn't, it'd be using Bluetooth and would explain the slow response time. Just a tip to remember next time.

Also, did you reset the Nanoleaf bulb before trying to add it back? Removing it is not enough. It needs to be reset before it can be paired with your Home again (as with most HomeKit devices).

Before the 16.4 update the Nanoleaf bulb was using Thread, afterwards it was hard to tell as it was unresponsive in HomeKit and the Nanoleaf app, bizarrely when it would respond in Nanoleaf it would not show transport type at all.
I also use Eve app as that gives a good overview of Thread network.

I did try resetting it, but for expediency tried a new bulb as I had one available.
When I go to fit it in another location I’ll try resetting and reusing it and see how I get on.

For some reason the 16.4 update really did a number on this bulb.

 

[Mercenary]

I have 5 HomePods and since 16.4 they all just stop playing at random moments.

Before, one would drop off and stop. But now they all just stop. Asking Siri to resume and she just starts off from scratch.

This can be with music playing or ambient sounds at night

 

[CyberDavis]

The most bizarre ongoing issue is with my Aqara camera and blind controller.
They work fine and are accessible from my iPad, MacBook Pro and Mac Studio.
And indeed via the aqara app they are fine.
But via my iPhone the camera very rarely updates and the blind is very slow to respond.
It is very odd, I have checked, checked again checked yet again that all devices are on latest OS and/or have latest firmware.
Why a problem with iPhone but no other devices.

Apart from that every other issue seems to be resolved and HomeKit working as expected.

 

[Mercenary]

The most bizarre ongoing issue is with my Aqara camera and blind controller.
They work fine and are accessible from my iPad, MacBook Pro and Mac Studio.
And indeed via the aqara app they are fine.
But via my iPhone the camera very rarely updates and the blind is very slow to respond.
It is very odd, I have checked, checked again checked yet again that all devices are on latest OS and/or have latest firmware.
Why a problem with iPhone but no other devices.

Apart from that every other issue seems to be resolved and HomeKit working as expected.

Slow to respond I’ve had and my issue was I was using 3rd party dns on that device and forgot. In this cake quad9.

For some reason the smart devices app was instant. But home was slow. Changed dns back on the device and all fine.

 

[CyberDavis]

Slow to respond I’ve had and my issue was I was using 3rd party dns on that device and forgot. In this cake quad9.

For some reason the smart devices app was instant. But home was slow. Changed dns back on the device and all fine.

Thanks for the suggestion, but no unusual or out of the ordinary DNS or IP settings.
And would that explain why iPad and Macs work fine but not iPhone?

 

[rayward]

I was one of the ones who updated to the new architecture with 16.2 before the option was pulled.
Since then I'd had various problems such as...

1. Automations intermittently failing

Same here. I had just got everything working again - after converting to the new architecture under 16.3 before it was pulled - and 16.4 has broken it again. My location-sensitive automations (e.g. 15 mins before sunrise) don't run while fixed-time automations (e.g. 9am) do.

This just gets tiresome.

 

[CyberDavis]

Interesting, mine was the reverse.😂
Location sensitive was fine, fixed were unreliable.

So far after deleting some automations and adding them back, and replacing the bulb everything seems to have settled down and be working.
With the very odd situation with my Aqara devices which work fine from everywhere except my iPhone.

I find that as with previous updates I had to restart all Apple TVs and HomePods once they had updated.
That’s in addition to any restarts following upgrade.
That action seems to help with improving reliability.

 

[Shanghaichica]

eArc is no longer working for me since the update. I don’t know if it‘s the Apple TV update or the homepod update that broke it.