Just installed the update. My stereo pair started playing together immediately for the first time in a long time. One HomePod has been kicking in on a delayed basis since a few updates ago. Hopefully this is fixed permanently.
I have 7, all with unique names, and they kept their names. But, it does NOT surprise me that the update has introduced yet another bug. Try wiping them and re-adding to Home perhaps. See if they then stick for the next update.Strangely this update erases the names of your HomePods. They revert to just being called "HomePod".
Yup I noticed this, never had this issue previously.Stereo pair does not start playing together since the previous 2 updates. How sad is this ****.
Alright, unpairing and repairing the affected HomePod triggered the update. 😮💨Did they pull the update?
3 of my 4 OG HomePods updated from 16.3.1 to 16.3.2, but the update check says everything is up to date.
This isn't correct. Filtering capacitors just go bad, it happens, they weren't part of a faulty batch as we know. It's the diode that was part of the faulty batches with serial 1746K and 1748k but this created no power and would instantly stop working randomly, no warning.Popping happens because some capacitors on the board are failing. Nic's Fix (nicsfix.com) repairs it for ya quick... Mine did that, and then became the death fart and made my OG HomePod unusable and Apple won't do anything for ya. It was a bad batch of chips and every repair Nic does falls in that batch.
My new "issue" now is how slow my OG HomePod is compared to the few Mini's I have around the house.
Studio,Phone,Two Apple TV's,Two HomPod Mini's all updated and working. (watch still installing)
My hub switched from bedroom Mini to downstairs Apple TV but everything is working as it should.
last week HP started saying I had nothing set up, but I forced a hub change and it started working. Snappier I thought.
1) Unplug the power cable for the HomePod from the outletThe popping sound is the real problem of OG homepod. Apple does not want to admit that.
Haven't had a popping sound since OS 16 on my 4 OGsThe popping sound is the real problem of OG homepod. Apple does not want to admit that.
Resetting the HomePods to factory setting and setting up again fixes this issue.View attachment 2158196
I cannot for the life of me get my HomePods to stay signed in to my Apple ID. Anyone else experience this? I even updated to 13.3.2 and still get this error.
Tip, turn off listen for hey Siri on your phone. It's always in your hand anyway, so just use the button.Me, talking to my HomePod: "Hey Siri, play some music."
HomePod: [silence]
My iPhone in my pocket:
View attachment 2158263
It's handy having "Hey Siri" turned on in the car, though. At least Siri could have started playing music on my phone, I'd say! My Siri responses have become crazier and crazier the past month... it worked much better for me 4 years ago or so ago.Tip, turn off listen for hey Siri on your phone. It's always in your hand anyway, so just use the button.
Be careful. Once you hear it, you can't unhear it. Sort of like the red pill.I have four OG HomePods, and never had popping sounds. What is this?
I read about it. None of my HomePods experience this.Be careful. Once you hear it, you can't unhear it. Sort of like the red pill.
Now, are you sure you want to know what it is?
![]()
If you have any type of warranty left for those, run your ass to get replacements! It will only get worse over time and AirPlay communications will get severely degraded.Hopefully everyone gets to download it as I’ve started getting the popping noise
Anybody got a fix for this? ThanksIs anybody else getting this issue when it’s just looking for the update
Do you have the updated HomeKit architecture? I also have this issue and I guess it’s caused by this.Anybody got a fix for this? Thanks
I deleted my home/reset HomePods and then was able to updateDo you have the updated HomeKit architecture? I also have this issue and I guess it’s caused by this.
Yes I do actuallyDo you have the updated HomeKit architecture? I also have this issue and I guess it’s caused by this.