When the problem occurs GB debug just keeps saying "waiting for message".
I've verified that when I first pair (or delete and re-pair) my watch with phone it gives me expected JSON messages, but after some period of time (it took 5 hours this time, but I've had it fail within 10 minutes) there's zero communication, despite both watch and phone stating they are connected.
edit to add, I also did the "Rewrite settings", just in case there was some problem there. I thought maybe it had, but no, it just took longer this time than usual.
second edit: I just noticed that my step counter widget has been reset, and my "messages" list contains only the test email I sent myself after re-pairing with my phone, none of the dozens of messages I've been receiving throughout the day.
Is it possible the watch crashed causing the BLE to get into a weird state? Connected but not able to communicate?
Espruino is a JavaScript interpreter for low-power Microcontrollers. This site is both a support community for Espruino and a place to share what you are working on.
When the problem occurs GB debug just keeps saying "waiting for message".
I've verified that when I first pair (or delete and re-pair) my watch with phone it gives me expected JSON messages, but after some period of time (it took 5 hours this time, but I've had it fail within 10 minutes) there's zero communication, despite both watch and phone stating they are connected.
edit to add, I also did the "Rewrite settings", just in case there was some problem there. I thought maybe it had, but no, it just took longer this time than usual.
second edit: I just noticed that my step counter widget has been reset, and my "messages" list contains only the test email I sent myself after re-pairing with my phone, none of the dozens of messages I've been receiving throughout the day.
Is it possible the watch crashed causing the BLE to get into a weird state? Connected but not able to communicate?