Yesterday I updated all my devices to 16.2 and then applied the new architecture. Initially all seemed ok, apart from one HomePod stereo pair that decided to separate and needed a reboot before they would pair again. I did not really check automations as I was tired and had other things t get on with.
Fast forward to this morning and I realised all my automations were not working, scenes were exceeding slow and overall response was slow. Frustrating to say the least as I have spent time convincing my wife of the benefits of the automations.
So I decided to reboot all possible hubs.I restarted all HomePods and apple TV's. I then checked all was back online and all HomePod to Apple TV links ok and home theatre links to TV's working.
Initially there was no change, then after a few more minutes things started to work.
The response to devices was back to normal speed and automations seem to be working again.
I'll keep an eye on things as the day progresses and check time based automations work and carry on checking event based automations work.
But it seems that after updating to 16.2 and then updating the architecture all possible hubs need a further reboot/restart to allow normal operation to proceed.
Seems a bit of a hassle, but I'll put it down to the new architecture, but I would have expected the restarts to be handled automatically or at least prompted.
Hopefully the above helps someone if they are struggling.
Fast forward to this morning and I realised all my automations were not working, scenes were exceeding slow and overall response was slow. Frustrating to say the least as I have spent time convincing my wife of the benefits of the automations.
So I decided to reboot all possible hubs.I restarted all HomePods and apple TV's. I then checked all was back online and all HomePod to Apple TV links ok and home theatre links to TV's working.
Initially there was no change, then after a few more minutes things started to work.
The response to devices was back to normal speed and automations seem to be working again.
I'll keep an eye on things as the day progresses and check time based automations work and carry on checking event based automations work.
But it seems that after updating to 16.2 and then updating the architecture all possible hubs need a further reboot/restart to allow normal operation to proceed.
Seems a bit of a hassle, but I'll put it down to the new architecture, but I would have expected the restarts to be handled automatically or at least prompted.
Hopefully the above helps someone if they are struggling.
