Per the title, I’ve found an issue where the Timers function of HomePods running 14.7 are not working as designed.  Specifically whether you set the Timer on an iOS device OR attempt directly on the HomePod they fail in different yet similar ways Setting on iPhone You will either not see the New Timer button in the Home app or you will and it will allow you to set one BUT when it gets to 00:00 the sound never goes off and when you click the x to cancel, the timer never goes away.  Setting on HomePod Directly You say ‘hey Siri set an x second time’ and then get presented with a couple of responses based on this issue. I’m classing them as below: Worst Case - ‘Somethings gone wrong’ - doesn't even appear to attempt setting timer Middle Case - ‘x second timer starting now’ - but then doesn't sound at the end of the timer, doesn’t register in Home App and if you ask ‘hey Siri how long’s left on my timer’ it will respond ‘there are no timers set’ Best Case - ‘x second timer starting now’ then sounds the timer alarm whether set by the Home App to the HomePod in question OR whether set by voice on the HomePod directly and you can view the timer counting down in the Apple Home App Full resets of network infrastructure and even HomePod resets do NOT resolve issue. With that said I have 1 HomePod out of a few that is working without issue. Therefore I believe that 1 could assist in fault isolation and ultimate resolution but haven't found anything different about that one yet.  For clarity, all Siri requests that involve Internet are working fine and even setting an Alarm or controlling HomeKit works fine. In other words everything else is good EXCEPT the Timers function. Is there a particular port/service that is required for this specific functionality ? I've tested this on both iOS 15 beta (for iPhone testing) and against standard iOS 14 (release version) and the same issue occurs. HomePods like I said are running release version 14.7. I've filed a bug too but mentioning here in case others have seen this. Thanks

AllPer the subject line, I tried to turn on Messages in iCloud but get the above error. I am using the same account for both. The only difference is that as this is an old @me.com Apple account that iCloud is somehow reverting the new @iCloud.com version to @me.com for that login whereas messages is using the new version of the same account @iCLoud.com. For Example:iCloud login shows: name@me.comiMessage shows: name@icloud.comAgain same address jsut for whatever reason when I enter the @icloud.com in the icloud login it reverts it to the older @me.com domain. Thats the only possible issue I see that could be causing this.Anyone else seeing this and have a workaround ? If not I'll file a bugThanks

Per the title, 14.7 was running on an original 4K ATV (not the latest one) and I was watching content on it yesterday then all of a sudden screen goes blank, and ATV is fast flashing the LED. Its been doing this ever since. How do I resolve this and what caused it as this literally happened while just consuming content ? Thanks

After many betas not being able to convert my SSD to APFS, I booted from a 10.13 USB drive today, went into Disk Utility and was 'seemingly' succesful in converting to APFS. Rebooted and now won't boot. This is an encrypted volume. Booted back off the USB image, went into Disk Utility again, sure enough mounts with the PW without issue. Run First Aid and fails immediately with exit code 8. Click on the Info icon in Disk Utility and evrything shows ok, APFS Encrypted etc except when I scroll down to bootable and it shows NO.If I go to Image Verify in DIsk Utility menu (just to see if I can browse to the APFS volume) sure enough it works fine, shows the file structure etc, just wont boot. Boots the bar to the no entry logo only. Doesnt prompt me to enter password and unencrypt on regular boot.If I try and change Startup Disk to the APFS volume it say 'You can't change the startup disk to the selected disk.' 'Running bless to place boot files failed'Anyone else seen this issue and know how to resolve ? It looks like the drive is still good with data on it, not sure why when APFS conversion exited successfully that it will not not allow it to boot.Any help is greatly appreciated.Thanks