Open brookslively opened 9 years ago
Do you have installed the latest version of NightWatch? Do you have the problem just if one of the watches gets out of range or always?
I did have the idea that the data was put on the data layer once per node and everytime it is put out gets synced with every watch, could cause the problem. But with my 1-Watch setup I couldn't cause any problem by putting it on the data layer 20times. :/
Here is a screenshot of my LG G Watch and nightwatch from the connected phone when both watches are connected. The watch is in range of the phone. I'm running nightwatch v1.0.2.
Im not exactly sure what triggers the watch to begin missing information. Last night when I connected both watches, it took an hour or two before this started happening. Then, the only solution I've found is to manually disconnect the watch I'm not using in the Android Wear companion app.
@brookslively Out of curiosity, have you tried seeing if closing the app (using the recents interface) and then restarting it helps?
I had an issue last night where my Moto 360 (single-watch configuration, no dual-watch stuff) stopped receiving updates while out running errands (phone was in my pocket the entire time) Attempting to reboot the watch did nothing, but restarting the app did fix the issue here. I'm not sure if my issue is in any way related to yours though, it probably is not.
If it happens again I'll try to get a logcat.
When I have two watches connected at the same time, an LG G Watch and a Moto 360, eventually the watches or one of the watchfaces stop updating. The Nightwatch app updates fine. My solution has been to manually disconnect whatever watch I'm not using within the Android Wear app. I just connected both watches to my phone so that I can share some images. Please let me know if something else would be helpful to resolving the issues like a logcat or something. Or if you have any questions. Thanks!