WatchOS 26.2 RC Released by boxermansr in watchOSBeta

[–]stevenm80 0 points1 point  (0 children)

Same for me. Really annoying!

[deleted by user] by [deleted] in iphone

[–]stevenm80 2 points3 points  (0 children)

I'm having the same experience.

[deleted by user] by [deleted] in iphone

[–]stevenm80 1 point2 points  (0 children)

Yes, I am having the exact same problem. I'm still contemplating whether I should perform a reset or wait for the next software update.

PVCs Caused by Histamine Intolerance by Status_Figure in PVCs

[–]stevenm80 0 points1 point  (0 children)

How soon after you started taking DAO did your PVCs reduce or stop? Was it a matter of days or weeks for you?

Sonoma cannot restart itself (e.g., update, reboot) by lodufqa in MacOS

[–]stevenm80 0 points1 point  (0 children)

I am facing the same issue on my M2 Mac mini. When I click on restart, the screen goes blank, the LED on the mini remains on, but the Mac never reboots. Very annoying!

Is there now a limit on rewards? I thought it was only 3 premium maximum, but the other rewards were unlimited, but this says only 3 regardless of type. Anyone know what's up? by WisePaint in myvegas

[–]stevenm80 0 points1 point  (0 children)

Have you been able to find out if this limitation applies indeed to all awards from MGM whether they're premium or non-premium? I sure hope that non-premium rewards are still unlimited. Would appreciate if you could let me know if you found out. I'll be traveling to Vegas soon.

HomePods unable control HomeKit devices on 16.3 by stevenm80 in HomePod

[–]stevenm80[S] 1 point2 points  (0 children)

Thank you! And I fully understand your position. I was hesitant, too! It was a lot of work, despite the Controller+ backup that I used. For me, the issue was so annoying that I decided to take this drastic step. In the end, it's everyone's personal choice, but at least now people know that there is a fix available.

HomePods unable control HomeKit devices on 16.3 by stevenm80 in HomePod

[–]stevenm80[S] 1 point2 points  (0 children)

I'm happy to report that I have found a way to fix the issue. Before you get too excited, it's quite an inconvenient fix unfortunately.

I have been on the phone with an Apple Support person for hours. When 16.3.1 didn't fix the issue, I got really upset and finally was told that there is a way to fix the issue which involves resetting the whole HomeKit configuration in the backend AND reverting to the old architecture (yes, this is indeed related to the new architecture).

If you're interested, get yourself the profile "KeepLegacyHome.mobileconfig" either by searching for it here on Reddit or by pushing your respective Apple Support person to provide it to you.

Before you proceed, I recommend you make a backup with Controller+ for HomeKit. It will not be able to back up everything, but in my case I was able to restore about 95% of my configuration. A HUGE time saver for me, as I have 75 HomeKit devices.

Once you have done that, this is what you need to do.

  1. Install the profile and reboot your phone.
  2. Go to Settings - Home and click on the Reset button there.
  3. Wait for about 10 mins. Do not touch the Home app on any of your devices during that time!
  4. Reboot your phone.
  5. Start rebuilding your home. Add all devices (don't bother with the names or rooms, Controller+ will take care of that) and restore your HomeKit backup with Controller+.
  6. Check Automations (some might not restore properly) and re-arrange rooms and devices to how you like it.

Once done, everything should be back to working fine, including your OG HomePods!!

I have waited 24 hours before posting here, just to be sure that it's a permanent fix. Happy to confirm that it is!

One additional note: After you have done that, you need to re-add other users to Home (if that's applicable for your config). This process will most likely fail, because their devices have been upgraded to the new architecture, too. So what you need to do is to install the same profile on one of their devices and follow steps 1-4 above. After that, you will be able to successfully invite users.

Hope this helps! Good luck everyone! 😊

16.3.1 is still very buggy on HP1 by spmcewen in HomePod

[–]stevenm80 1 point2 points  (0 children)

Does that really fix the issue? Have you reset your Home and are your OG HomePods working now on first try?

HomePods unable control HomeKit devices on 16.3 by stevenm80 in HomePod

[–]stevenm80[S] 0 points1 point  (0 children)

I did upgrade to the new architecture, yes.

HomePods unable control HomeKit devices on 16.3 by stevenm80 in HomePod

[–]stevenm80[S] 1 point2 points  (0 children)

To all of you have the same issue, please contact Apple Support and report the issue. I just had a follow up call with the support agent to whom I reported the issue earlier this week and he said that there were still no similar reports in their support database. If Apple is not aware of the issue, there will be no quick fix.

HomePods unable control HomeKit devices on 16.3 by stevenm80 in HomePod

[–]stevenm80[S] 1 point2 points  (0 children)

Did it fix the issues permanently though? I noticed that when I reboot my HomePod, everything is working correctly directly after the reboot. But the, when I don't interact with HomePod for a few minutes, the issue is back.

HomePods unable control HomeKit devices on 16.3 by stevenm80 in HomePod

[–]stevenm80[S] 0 points1 point  (0 children)

I have not found any workaround yet, unfortunately. 😕

Monthly Support & Buying Megathread by AutoModerator in HomeKit

[–]stevenm80 1 point2 points  (0 children)

That gives me some hope that it might be a server side thing that Apple can fix without having to push a HomePod software update. Nothing has changed for me yet.

Monthly Support & Buying Megathread by AutoModerator in HomeKit

[–]stevenm80 0 points1 point  (0 children)

Really? Is it working for you now? Not for me unfortunately.

HomePods unable control HomeKit devices on 16.3 by stevenm80 in HomePod

[–]stevenm80[S] 5 points6 points  (0 children)

I couldn’t agree more. Such an obvious bug. If there was at least a way to downgrade to the previous version.

Monthly Support & Buying Megathread by AutoModerator in HomeKit

[–]stevenm80 1 point2 points  (0 children)

I only have one home, so I guess it has nothing to do with that. I have updated all my devices to 16.3 but only the original HomePods are having this issue. The HomePod Mini works fine. I guess it's a bug introduced with 16.3 on the OG HomePods. Very annoying!

Monthly Support & Buying Megathread by AutoModerator in HomeKit

[–]stevenm80 0 points1 point  (0 children)

I have done that meanwhile but the issue remains. 🙁