I upgraded to the new architecture for my original HomePod and mini last year, yet never happened upon the ‘configuring’ issue. I’m still yet to encounter it on either, though I don’t do (and have never done) any stereo pairing.
Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Apple Releases HomePod 16.4 Software
- Thread starter MacRumors
- Start date
- Sort by reaction score
Well, you are lucky. I’ve had 2 minis stuck on configuring for multiple OS updates, and every time I factory restore them and set them up, and even today they are still doing that.
They’ve had an error every time I try to set them up as a stereo pair as well.
Fingers crossed that something will change now that the new architecture is live.
I have one old regular Homepod saw same message on Home on Mac with 13.3. Then looked at iphone home and it said my Homepod was being updated their just does not show on Mac I guess?
Remote access to alarms is still broken with the "new HomeKit architecture", been that way since introduction with 16.2...
For ****s sake Apple, fix it or just go ahead and remove recurring alarms from the HomePods entirely, without being able to disable alarms remotely it is an entirety useless feature that will only result in pissed off neighbours when I inevitably go on a business trip or vacation without remembering to disable my recurring alarm.
For ****s sake Apple, fix it or just go ahead and remove recurring alarms from the HomePods entirely, without being able to disable alarms remotely it is an entirety useless feature that will only result in pissed off neighbours when I inevitably go on a business trip or vacation without remembering to disable my recurring alarm.
Which Home app you using? I found on my iphone that there it said it was being installed but on Mac 13.3 it was up to date I find the home app works better on iphone than my mac.
If you are looking on Mac go to your iphone and check home there I found it was updating via that device but Mac knew nothing.
i am so sick of “i couldn’t find that in your apple music library” that i don’t even bother asking any more, i just choose music via my iphone. when my 1st gen homepods die (which they will, given the design flaw apple has never publicly acknowledged but quietly fixed with the 2nd gen) i’ll move to sonos. it’s a shame because i still absolutely love their sound.
Ok working on my phone but I only have one Homepod thought maybe that was issue.
I got a little functionality back by factory resetting the HomePods, but because the HomePod updater blows @$$ only one updated despite both showing they were updated and now nothing works again because one is still on 16.3. This is utterly infuriating.
Did they finally fix the continual ‘there was a problem with Apple Music’ error when using a stereo pair of Minis as default output for an Apple TV?
Same here @csalm87 : 3 of 4 OG HomePods updated, fourth stuck on 16.32.
UPDATE — The following tactic worked to update the HP stuck on 16.3.2:
1. Open Home app and Remove HP stuck on 16.3.2
2. Reset stuck HomePod (https://support.apple.com/en-us/HT208244)
3. Hold phone near HomePod and follow instructions to reset and re-pair
4. Keep phone near HomePod and wait for software update to be detected
5. Use device settings to initiate HomePod software update
This worked for me. I hope this helps someone.
Last edited:
Normally I don’t update my 2 OG’s immediately, but today I did as my significant other would REALLY like to be able to control our HomeKit lights…like the one next to her side of the bed!
I’ll try to re-add her after her series 8 watch updates overnight; as I recall Apple stating everything had to be running .3 before the HomeKit fiasco blew up most everyone’s network. 🤬
I always update one HomePod at a time people. Just to minimize glitches, if you for some reason don’t see the manual option to update one at a time, just unplug one, update the other…💡
I’ll try to re-add her after her series 8 watch updates overnight; as I recall Apple stating everything had to be running .3 before the HomeKit fiasco blew up most everyone’s network. 🤬
I always update one HomePod at a time people. Just to minimize glitches, if you for some reason don’t see the manual option to update one at a time, just unplug one, update the other…💡
Plugin to your computer, and using Finder in Mac or iTunes, choose "Restore and Update".
Yeah, I had to buy a wifi extender and put it next to my regular router to basically clone the home wifi and that worked for me. Not exactly the best user experience. Funny that original Homepod, the big one, had a chip from iPad, not Apple Watch and had no issues like this. Even funnier that the new big one has Watch chip again, so people can experience the joys we did. Tim keeps delivering.
I think one of the others (Alexa?) has a politeness mode for (training) children that does that.
The problem is user confidence that the assistant is not listening (for anything other than the wakeup phrase) after an interaction. Right now, the only time Siri expects followup is if it needs to ask a question, such as when I ask for the hours of a local (regional chain) restaurant without giving the location; in that case, it picks the nearest, gives that information, and then asks if I want more (no, it got it right). Because the followup is a question, you know it's still listening. Courtesy phrases would make that harder to get right, and harder for the user to have confidence that Siri isn't eavesdropping. It would have to for example stop listening for followup after ten seconds or so if you didn't say "thank you". The light on top can help tell whether it's listening, except in a lot of locations (seated, in the shower, etc; yes, I have a Mini in the bathroom, to time my beard dye as well as answer random questions) one can't see the activity light.
Trust is important to Apple; they have a good case that they don't have much motivation to market your info (they sell actual products, they don't really push products of others that they sell, and the only processing they do with your information is for orders or services that you know about), so they build on that to claim that they're very careful about what they even collect. That's sort of true, not perfectly so (voice recognition requires samples of borderline raw voice for human adjustments to be made, but even Apple (let alone the others) kept some of those longer than they should have); but it definitely differentiates between them and anything run by say Google or Amazon, both of which have far more motivation to monetize users rather than respect their privacy as valued customers.
Here's what I do:
always do the updates manually
always update them from a device running the latest iOS/iPadOS/macOS (updated before updating the HomePods, if necessary; I would give best odds on updating from iOS or at any rate not macOS, since that's usually what's needed for original setup)
unpair any stereo pair(s) before updating
update one at a time, and test it after updating by playing something
re-pair the stereo pair(s) and test them again
No problems that way. There IS one oddity: since the update that enabled the HomePod Mini temperature and humidity sensors, Monterey (or any macOS prior to Ventura) only shows the Minis as "configuring", but that isn't breaking anything other than control or updating of them from those older macOS versions. I only have originals (3) and Minis (2), but I assume the new full size HomePods would be similar (or worse) with older macOS (or probably iOS/iPadOS) versions.
I did enable the Matter support and use a Beta of the Eve app to update my Eve smartplug to Matter, following all instructions. That worked and still works after 16.4.
Aside from being slow and relatively labor intensive compared to an automatic update, one minor annoyance is that any update (probably an automatic one too) causes them to forget the last song they played. That becomes obvious with the test playing in the procedure I described.
Occasionally I've had it require me to re-enter my AppleID password for updates. That's happened a couple of times lately, but not this time. I don't think it was REALLY necessary, more like a timing issue with the HomePod vs the device controlling the updates.
My WiFi setup is boring, a DLINK router/base station that I own, no mesh or relays (but separately named 2.4GHz and 5GHz SSIDs, so I know at a glance which one something is on). In a few cases, if I do something with the phone and a HomePod not long after coming home, the iPhone may be on the 2.4GHz because that has longer range and reconnected from the driveway, while the HomePod may be on the 5GHz (preferable for speed). For a few functions it complains that they're not on the same one, and the HomePod may "follow" the iPhone onto 2.4GHz. So if I'm careful, I make sure the iPhone is on 5GHz before using it to fiddle with HomePod settings.
My main laptop is still on Monterey because of the PITA of updating MacPorts (packaged open source software, has to be reinstalled after each major OS update) and breakage...but I do have a Ventura (or whatever is latest) VM for checking what works vs what breaks. And I have something still on Mojave because vpnd is said not to work right after that. (and a Snow Leopard VM with original Rosetta for a few PowerPC executables that are useful but were never updated) So I see things that break because of version mismatch issues (and device support not being backported)
I once had one of the original HomePods brick itself, but that was NOT associated with updating; it may have been a power bump, or just one of those random cosmic ray things (IoT devices and devices without a recovery mode REALLY need ECC CPUs, RAM, and flash, which might greatly reduce random problems; if my recollection is right, blame Intel for going cheap on consumer computers, even though bulk adoption would have minimized the cost difference; otherwise ECC might have been more widely adopted). Fortunately it still had a few months left on the AppleCare+; I procrastinated but did take it in still under coverage, so they just verified that the recommended procedures didn't help, and accepted it for swap; a few days later they had a new one to replace it for me to pick up. (I gather the inventory of spares is sparse enough that it had to be shipped from elsewhere.)
That's pretty much my entire experience with HomePod updates. Being a retired IT guy, I tend to do things manually because I want control and a plan for how to have the best outcome, or at any rate discover failures before they're any more widespread than necessary; and doing things too automatically is riskier, except in certain cases where one has done one's own extensive pre-testing on duplicate hardware. There are advantages to professional paranoia.
And to noticing details, which allows documenting a known safest (nothing is perfect) procedure.
Last edited:
I managed to get my second HomePod to update but again, nothing works. The HomePods literally can't be plugged in or they bring the entire network down. As soon as they're unplugged everything works fine. It's not the network (I've had two network technicians check out all my router settings), it only started with iOS 16.
I essentially have two paperweights.
I essentially have two paperweights.