-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Trouble connecting #1
Comments
Thanks for feedback. Unfortunately in my case application works in most cases, I see issues relatively rarely. Can you please provide full connection logs from both Clock (UART output) and App (browser console)? I think it will be very helpful to resolve this issue. |
Today I captured the serial log when a connection failed, and saw that the message was incomplete:
Retrying I received:
So I think the problem is on the watch, where I suspect the onWrite method is running concurrently with onConnect (which now deletes the message queue). Actually - the log before the above gives more insight:
It is reporting that it is connected twice!? |
Is it receiving onConnect() event twice in both cases, or only in case when part of message was lost? |
sorry about platform io not grabbing all the characters. i have no idea why, so i tried a couple times
it kinda worked the first few times i used it, but anymore i cant get anything but "An unhandled error has occurred. Reload" at the bottom of my screen |
That's strange.
May be this is the issue reason? Is https://my-ttgo-watch.co.uk BT pairing working in your case? |
so i almost said that page worked fine (since it did yesterday) but i decided to try again to verify: it connects briefly before disconnecting again. the first time was too quick to do anything so i restarted my bt and tried again, it connected long enough for me to click on and get the step counter data before losing the connection again. grabbed logs from that page:
|
So looks like issue isn't in WConfigurator application directly? |
since i have an iphone, i cant use gagetbridge and afaik cant do much else with bt atm, so it could be faulty hardware for all i know. it definately DID work previously, and now doesnt. not on my desktop in linux or windows 10, nor my brothers laptop which is win10. i didnt touch any bt related code, nor do i use any in anything ive written. im assuming you havnt changed anything, which leaves something upstream, are the 2 pages built on common framework? is it worth trying with a different browser, say firefox instead of chrome? |
Windows & Chrome
Looking at the console output, the times I get continued spinning dots is always after selecting the device to pair to, and when WConfigurator receives either no response, or a battery status update, but no list of buttons:
Sometimes that's all, other times I also receive:
Which is
{t:"status", bat:77}
surrounded by CR LF, with no \x03I have had it work too, when the console includes
[3,123,34,97,112,112,34,58,34,105,114,34,44,34,114,34,58,34,108,105]
({"app":"ir","r":"li
) etcThe text was updated successfully, but these errors were encountered: