Do you have an Android Wear watch? Did you connect it to WiFi and wonder why it won’t stay connected? There’s good reason for that and it has to do with the tiny batteries inside these watches.
Android Wear is designed to be battery efficient. It takes a lot of power to run these things. They use many of the same components as the smartphone in your pocket. Smartphones have nearly ten times the battery power as an Android Wear watch. The screen, the processor, all of the sensors inside – these consume a lot of power. It also turns out that WiFi uses a lot more power than Bluetooth does. In fact, Bluetooth has become so efficient over the years that it uses almost no power when idle.
In order to capitalize on the low power consumption of Bluetooth, Android keeps the WiFi signal turned off until it’s needed. In other words, since your watch is already receiving information from your phone directly over Bluetooth, it doesn’t need the WiFi connection too. As a result, Android Wear turns the WiFi off to conserve battery power. When a connection to your phone is lost, the watch should scan for WiFi and connect to a network you’ve logged into previously.
For those that want to get straight to the point (TL;DR): It’s working as it should, don’t worry about it.