iClint_, you mean you're getting the red "disconnected from phone" icon whenever you switch off bluetooth? In that case, there's some other problem, i.e., your iPhone's wifi settings are not being correctly shared with the watch. In theory, and it works great for me, whenever you're on a wifi network and you are not moving (i.e., just sitting at home or work and using the same network for a while), your watch should be connected to the same wifi network as your phone. Then, if you turn off bluetooth (or walk into another part of the house so that you go out of range for bluetooth), the watch is supposed to continue to communicate with the iPhone over wifi. It sounds like for some reason, that's just not happening for you .. which is a different issue, but still something to maybe troubleshoot (separately). Not sure how to help you there.
But assuming you can actually get it to work so the watch is connected to the phone via wifi -- at that point, turning off bluetooth should resolve the latency issue with getting notifications on your watch. Though obviously it's not a great solution, but while you're still learning what's what, it could be useful to factor out bluetooth connectivity issues while troubleshooting other stuff.
Also, many people seem to misunderstand the notification model for the watch -- which is understandable, it's not comprehensible to begin with. But, there are many cases where you will never get notified on the watch, and this is "working as intended." People have posted about that either here or in other threads.
In short, there are two fundamental issues you should be aware of:
(1) Each iPhone notification mirrored to the watch is "all-or-nothing".
That means, either the notification does display on the watch, or it doesn't and never will. (This is by design.) In other words, there's no "sync" mechanism for missed notifications to show up as a red dot. (Delays are the result of communication issues between the iPhone and the watch, not somehow inherent in the model that there's some sync happening in the background. Sure, a notification that is attempted to be sent from the phone to the watch will be retried until it succeeds, but that's a lower level than what I'm talking about. I'm saying this "all-or-nothing" modality has to do with whether it even tries to send the notification to begin with.)
The red dot only shows up when you missed a notification that *was* delivered to the watch, but you didn't see it before the screen blanked (or you didn't dismiss it somehow; noting that there are multiple ways to dismiss.) But, if for the reason below, your phone decides not to send a notification to the watch, it will never go to the watch (that one notification, I mean, not future notifications from the same source). And in specific, I'm talking about notifications that are mirrored to the watch from your phone via "bluetooth" (in fact, they will go without bluetooth, but to parallel the notifications you would get to other bluetooth devices such as Pebble).
Note: notifications from apps running on the watch itself do not work the same way (so ignore this point and the next one for those types).
(2) For the notifications described in (1) above, notifications will only be sent to the watch if your iPhone thinks they should be!
The iPhone makes that determination itself, based on a few things such as whether or not the watch is connected, whether or not the iPhone is in use, etc.
Most importantly, if your iPhone is unlocked (or, I think even if the screen is lit up but it's still locked), notifications will not go to the watch. It's a "power-saving" (and user-confusing) feature designed by Apple. :-) They figure, if you are looking at your phone, you don't need to hear or feel a notification on your watch .. you can just consume it on your phone.
So a LOT of people who troubleshoot slow or broken notifications get really confused by this -- in 100% of the cases, if they're unaware of this requirement, they will be looking at their phone when a notification comes in, see it relayed to the Pebble or other devices instantly, and then while the phone is on and unlocked and they're staring at it, wonder why the notifications never also went to the watch! But this is exactly how it's designed. They simply won't go to the watch in this case.
In brief, you must hit the side button on your iPhone (to lock it and put its display to sleep) before a notification arrives, or else your iPhone won't relay it to the watch! (See "all-or-nothing" above. :-) ) And because of the all-or-nothing property, you won't ever see it, even later .. so if you lock your iPhone one millisecond after the notification starts to be received, it's too late, and you'll never see the notification. Your iPhone must be locked and asleep before you even have a chance to see notifications go to your watch.
Of course, when you're not troubleshooting, this is what you want. Because you want to rest assured that you'll be notified when you're out and about. But .. I think of this just like the refigerator door dilemma. :-) You don't know if it's working while you're testing it, you just have to hope.
Hope this is helpful.
Steve
