Me too, and that's part of why I signed up for Mac Rumors. (And I, too, own an SE.)
I just bought my first Apple watch toward the end of October and after going through a lot of troubleshooting with Apple, I returned it (one of the chat reps suggested I take it back). I got another Series 5 GPS thinking the first one was just a lemon. Unfortunately, Siri is just as unreliable and placing calls on the watch almost always results in "I can't complete that request".
Once the watch gets in its electronic brain that it can't complete a request, like place a call, it tends to keep on behaving that way until I do multiple on/off toggles of the Bluetooth, WiFi and reboot the watch and the phone multiple times (if not also force-restart the watch). Then it works okay for awhile until I don't interact with my phone in any way. It seems like when the watch/phone are idle it goes back to having connectivity problems. Eventually Siri completes a connection/request but it is SUPER annoying to have Siri preface everything with "working on that", "let me try that again" or "please try again later".
I am seeing a modest improvement — might just be my imagination though! — with the latest watchOS update but still nowhere near what I would expect based on my experience with how Siri works on the phone.
My take on it is that the Bluetooth and WiFi aren't playing nice with each other and if Bluetooth doesn't have a good connection to the phone it's not "deciding" quickly enough to use the WiFi connection vs. Bluetooth. That would explain why Siri eventually completes a response but there is a LOT of lag time while it keeps trying the Bluetooth. Sometimes I even go into WiFi on the watch and see that my network has moved down into the list of local networks (neighborhood). So that would seem to suggest the watch is logging off the WiFi — maybe to conserve battery? — and not reconnecting fast enough. That's my theory anyway…
I just bought my first Apple watch toward the end of October and after going through a lot of troubleshooting with Apple, I returned it (one of the chat reps suggested I take it back). I got another Series 5 GPS thinking the first one was just a lemon. Unfortunately, Siri is just as unreliable and placing calls on the watch almost always results in "I can't complete that request".
Once the watch gets in its electronic brain that it can't complete a request, like place a call, it tends to keep on behaving that way until I do multiple on/off toggles of the Bluetooth, WiFi and reboot the watch and the phone multiple times (if not also force-restart the watch). Then it works okay for awhile until I don't interact with my phone in any way. It seems like when the watch/phone are idle it goes back to having connectivity problems. Eventually Siri completes a connection/request but it is SUPER annoying to have Siri preface everything with "working on that", "let me try that again" or "please try again later".
I am seeing a modest improvement — might just be my imagination though! — with the latest watchOS update but still nowhere near what I would expect based on my experience with how Siri works on the phone.
My take on it is that the Bluetooth and WiFi aren't playing nice with each other and if Bluetooth doesn't have a good connection to the phone it's not "deciding" quickly enough to use the WiFi connection vs. Bluetooth. That would explain why Siri eventually completes a response but there is a LOT of lag time while it keeps trying the Bluetooth. Sometimes I even go into WiFi on the watch and see that my network has moved down into the list of local networks (neighborhood). So that would seem to suggest the watch is logging off the WiFi — maybe to conserve battery? — and not reconnecting fast enough. That's my theory anyway…