Same issue here. I have two sets of OGs on 16.3 + new architecture. What a pain!Same here. First fails, second succeeds. Two OG’s with 16.3 on the new architecture.
I have submitted a bug report with a link to this thread so hopefully they will read it!Just another data point in case Apple is perusing this thread.
Yep, seeing this about 30-50% of my requests on OG HomePods. Second request works immediately. I do have HP minis but TBH I haven't noticed if they're also doing the same thing or not.
New architecture here as well.
That’s a significant downgrade, sonically. Don’t do it.Same experience. New architecture and OG homepods (not tried minis). Might consider moving a mini if this is going to be a long standing issue.
More than likely Apple are performing limited testing against the OG HomePods compared to current models than some nefarious Dr Evil reasonNot a fan of conspiracy theories, but bizarre this started happening as new models are released
Same here with me. All 3 of my OG HomePods have a first attempt issue whereas my minis are fine. I’m also on the new architectureI updated all my devices to iOS 16.3 when it came out, and for the most part things are pretty stable. At first, the FindMy feature to ask about your family members' locations wasn't working, but after rebooting all the home hubs, that seems to have cleared out. The one problem I still have is that when asking a HomePod to turn on lights or a scene, it will fail. It says something like "I can't do this right now, try again in a minute". I immediately try again and it works right away. Then I can ask it to turn on any light in the house and it works fine. It's just that first request that fails. If I move to another HomePod, it's the same thing, first time fail, then works fine.
Anyone else seeing this behavior? Before I go any further with troubleshooting, I wanted to see if it's a system-wide Homekit thing, or something specific to my network.
Are you sure it's fixed? I've had a few times where the first command works and I get excited....then I ask that same Homepod to do something an hour later and it's back to the same old message.....16.3.1 has fixed it for me
Yeah. I celebrated when I installed 16.3.1 when the first 10 commands seemed to be great. Then the HomePod had some time to itself and decided that it’d be hilarious and start the old behaviour again.Are you sure it's fixed? I've had a few times where the first command works and I get excited....then I ask that same Homepod to do something an hour later and it's back to the same old message.....
Yep, same here. Come on, Apple! This can't be that hard to fix!Yeah. I celebrated when I installed 16.3.1 when the first 10 commands seemed to be great. Then the HomePod had some time to itself and decided that it’d be hilarious and start the old behaviour again.
Pmsl!!! Yeah once I installed it I tried it first go I had… one sec… that’s done! I was like woooooooo ‘it just works’ then in haste I gave another command… on it… there was a problem completing your request please try again in a bit…Yeah. I celebrated when I installed 16.3.1 when the first 10 commands seemed to be great. Then the HomePod had some time to itself and decided that it’d be hilarious and start the old behaviour again.