MyWhoosh provides resistance data Incyclist does not #6
|
I have instrumented a dumb training using esp32s and it works great with MyWhoosh. Incyclist accepts power and cadence from my training bike but it does not send resistance data even though it is showing that Resistance is connected on the Paired Devices screen. Any ideas why this might be. I would really rather ride in the real world than in the MyWhoosh game. |
Replies: 11 comments 4 replies
|
please send me your UUID (From Settings->Support) via email or as a private message in Slack. Then I can have a look. Does sound like a messaging issue |
|
Thanks for the quick response.
Attached is a screenshot of the settings page showing the UUID.
If it is of interest to you here are the UUIDs that are used in the ble connection to the client:
#define FTMSDEVICE_FTMS_UUID "00001826-0000-1000-8000-00805F9B34FB"
#define FTMSDEVICE_INDOOR_BIKE_CHAR_UUID "00002AD2-0000-1000-8000-00805F9B34FB"
#define FTMSDEVICE_FTMS_FEATURE_CHAR_UUID "00002ACC-0000-1000-8000-00805F9B34FB"
#define FTMSDEVICE_FTMS_CONTROL_POINT_CHAR_UUID "00002AD9-0000-1000-8000-00805F9B34FB"
#define FTMSDEVICE_FTMS_STATUS_CHAR_UUID "00002ADA-0000-1000-8000-00805F9B34FB"
Thanks,
Fred
From: Guido Doumen ***@***.***>
Sent: September 5, 2026 9:20 AM
To: incyclist/.github ***@***.***>
Cc: FredPesp32 ***@***.***>; Author ***@***.***>
Subject: Re: [incyclist/.github] MyWhoosh provides resistance data Incyclist does not (Discussion #6)
please send me your UUID (From Settings->Support) via email or as a private message in Slack. Then I can have a look. Does sound like a messaging issue
—
Reply to this email directly, view it on GitHub <#6?email_source=notifications&email_token=CNPSZH4P3LNMROX4SARDGMT5NQ4MJA5CNFSNUABIM5UWIORPF5TWS5BNNB2WEL2ENFZWG5LTONUW63SDN5WW2ZLOOQXTCOBTGA3DENZWUZZGKYLTN5XKMYLVORUG64VFMV3GK3TUVRTG633UMVZF6Y3MNFRWW#discussioncomment-18306276> , or unsubscribe <https://github.com/notifications/unsubscribe-auth/CNPSZHYDXGBT7CGGJIEZJVT5NQ4MJAVCNFSNUABIKJSXA33TNF2G64TZHM4TMOJZHA2TOOJSHNCGS43DOVZXG2LPNY5TCMBXGUYTIOBQUF3AE> .
Triage notifications, keep track of coding agent tasks and review pull requests on the go with GitHub Mobile for iOS <https://github.com/notifications/mobile/ios/CNPSZH334TEMZVIDGFGYF535NQ4MJA5CNFSNUABIM5UWIORPF5TWS5BNNB2WEL2ENFZWG5LTONUW63SDN5WW2ZLOOQXTCOBTGA3DENZWUZZGKYLTN5XKMYLVORUG64VFMV3GK3TUVJTG633UMVZF62LPOM> and Android <https://github.com/notifications/mobile/android/CNPSZH2V347DXN2X2S54CPL5NQ4MJA5CNFSNUABIM5UWIORPF5TWS5BNNB2WEL2ENFZWG5LTONUW63SDN5WW2ZLOOQXTCOBTGA3DENZWUZZGKYLTN5XKMYLVORUG64VFMV3GK3TUVZTG633UMVZF6YLOMRZG62LE> . Download it today!
You are receiving this because you authored the thread. <https://github.com/notifications/beacon/CNPSZH6LIF6NAADAMZLML6T5NQ4MJBFCNFSM6AAAAAC65NV4FKWGG33NNVSW45C7OR4XAZNRIRUXGY3VONZWS33OINXW23LFNZ2KUY3PNVWWK3TUL5UWJTQBC5KOJJTSMVQXG33OUZQXK5DIN5ZA.gif> Message ID: ***@***.*** ***@***.***> >
|
|
Hi
I sent you a picture of the UUID but perhaps it didn’t get to you. Here is the info on the Support tab
App Version 0.9.1.2
UI version 26.9.1
uuid 18d44b94-a20a-4f33-925b-2e6fdb020a4c
Fred
From: ***@***.*** ***@***.***>
Sent: September 5, 2026 2:13 PM
To: 'incyclist/.github' ***@***.***>
Subject: RE: [incyclist/.github] MyWhoosh provides resistance data Incyclist does not (Discussion #6)
Thanks for the quick response.
Attached is a screenshot of the settings page showing the UUID.
If it is of interest to you here are the UUIDs that are used in the ble connection to the client:
#define FTMSDEVICE_FTMS_UUID "00001826-0000-1000-8000-00805F9B34FB"
#define FTMSDEVICE_INDOOR_BIKE_CHAR_UUID "00002AD2-0000-1000-8000-00805F9B34FB"
#define FTMSDEVICE_FTMS_FEATURE_CHAR_UUID "00002ACC-0000-1000-8000-00805F9B34FB"
#define FTMSDEVICE_FTMS_CONTROL_POINT_CHAR_UUID "00002AD9-0000-1000-8000-00805F9B34FB"
#define FTMSDEVICE_FTMS_STATUS_CHAR_UUID "00002ADA-0000-1000-8000-00805F9B34FB"
Thanks,
Fred
From: Guido Doumen ***@***.*** ***@***.***> >
Sent: September 5, 2026 9:20 AM
To: incyclist/.github ***@***.*** ***@***.***> >
Cc: FredPesp32 ***@***.*** ***@***.***> >; Author ***@***.*** ***@***.***> >
Subject: Re: [incyclist/.github] MyWhoosh provides resistance data Incyclist does not (Discussion #6)
please send me your UUID (From Settings->Support) via email or as a private message in Slack. Then I can have a look. Does sound like a messaging issue
—
Reply to this email directly, view it on GitHub <#6?email_source=notifications&email_token=CNPSZH4P3LNMROX4SARDGMT5NQ4MJA5CNFSNUABIM5UWIORPF5TWS5BNNB2WEL2ENFZWG5LTONUW63SDN5WW2ZLOOQXTCOBTGA3DENZWUZZGKYLTN5XKMYLVORUG64VFMV3GK3TUVRTG633UMVZF6Y3MNFRWW#discussioncomment-18306276> , or unsubscribe <https://github.com/notifications/unsubscribe-auth/CNPSZHYDXGBT7CGGJIEZJVT5NQ4MJAVCNFSNUABIKJSXA33TNF2G64TZHM4TMOJZHA2TOOJSHNCGS43DOVZXG2LPNY5TCMBXGUYTIOBQUF3AE> .
Triage notifications, keep track of coding agent tasks and review pull requests on the go with GitHub Mobile for iOS <https://github.com/notifications/mobile/ios/CNPSZH334TEMZVIDGFGYF535NQ4MJA5CNFSNUABIM5UWIORPF5TWS5BNNB2WEL2ENFZWG5LTONUW63SDN5WW2ZLOOQXTCOBTGA3DENZWUZZGKYLTN5XKMYLVORUG64VFMV3GK3TUVJTG633UMVZF62LPOM> and Android <https://github.com/notifications/mobile/android/CNPSZH2V347DXN2X2S54CPL5NQ4MJA5CNFSNUABIM5UWIORPF5TWS5BNNB2WEL2ENFZWG5LTONUW63SDN5WW2ZLOOQXTCOBTGA3DENZWUZZGKYLTN5XKMYLVORUG64VFMV3GK3TUVZTG633UMVZF6YLOMRZG62LE> . Download it today!
You are receiving this because you authored the thread. <https://github.com/notifications/beacon/CNPSZH6LIF6NAADAMZLML6T5NQ4MJBFCNFSM6AAAAAC65NV4FKWGG33NNVSW45C7OR4XAZNRIRUXGY3VONZWS33OINXW23LFNZ2KUY3PNVWWK3TUL5UWJTQBC5KOJJTSMVQXG33OUZQXK5DIN5ZA.gif> Message ID: ***@***.*** ***@***.***> >
|
|
Sorry for the late response. I had missed that you already shared your UUID. I have looked at the logs and am a bit clueless. I see that the devices support the BLE FTMS mode (service uuid 1826) and supports Bit 13 (Indoor Bike Simulation Parameters Supported), i.e. it allows the app to send Slope aks Gradient (and others) The app uses this and regularily sends the slope to the device. I don't see any errors, so the trainer seems to accept the values that the app sends. However, I also see that the restance is not increased ( e.g. 6.1% with 77W is highly unrealistic). As you mentioned that your have "instrumented " the trainer. Do you have access to any logs on your side? |
|
Hi Guido
Just thought I would let you know that I have Incyclist working better. I refactor my class that handles the Bluetooth interface based on some code I found in github. The slope data comes in fine at the beginning of the ride but it starts to lag the slope shown in Incyclist. After riding for 20 minutes the slope data was arriving over Bluetooth was a good minute late. I though it might be getting delayed in the bike computer’s operating system’s Bluetooth handling. So I went for a ride using MyWhoosh and the slope data coming into my bike computer was consistently no more than 1 second behind what was shown on the screen. I will continue to investigate but if you have any thoughts about why the slope data starts lagging on the Bluetooth inference, please let me know.
Thanks
Fred
From: Guido Doumen ***@***.***>
Sent: September 26, 2026 10:00 AM
To: incyclist/.github ***@***.***>
Cc: FredPesp32 ***@***.***>; Author ***@***.***>
Subject: Re: [incyclist/.github] MyWhoosh provides resistance data Incyclist does not (Discussion #6)
Sorry for the late response. I had missed that you already shared your UUID.
I have looked at the logs and am a bit clueless.
I see that the devices support the BLE FTMS mode (service uuid 1826) and supports Bit 13 (Indoor Bike Simulation Parameters Supported), i.e. it allows the app to send Slope aks Gradient (and others)
The app uses this and regularily sends the slope to the device. I don't see any errors, so the trainer seems to accept the values that the app sends. However, I also see that the restance is not increased ( e.g. 6.1% with 77W is highly unrealistic).
—
Reply to this email directly, view it on GitHub <#6?email_source=notifications&email_token=CNPSZHYWGPCKYKWLBEMC5HL5Q7YY5A5CNFSNUABIM5UWIORPF5TWS5BNNB2WEL2ENFZWG5LTONUW63SDN5WW2ZLOOQXTCOBWGE2TEMRQUZZGKYLTN5XKMYLVORUG64VFMV3GK3TUVRTG633UMVZF6Y3MNFRWW#discussioncomment-18615220> , or unsubscribe <https://github.com/notifications/unsubscribe-auth/CNPSZHZS5WJ2SD5YVZQY7DT5Q7YY5AVCNFSNUABIKJSXA33TNF2G64TZHM4TMOJZHA2TOOJSHNCGS43DOVZXG2LPNY5TCMBXGUYTIOBQUF3AE> .
Triage notifications, keep track of coding agent tasks and review pull requests on the go with GitHub Mobile for iOS <https://github.com/notifications/mobile/ios/CNPSZH62O2BS74NWPNU6QWL5Q7YY7A5CNFSNUABIM5UWIORPF5TWS5BNNB2WEL2ENFZWG5LTONUW63SDN5WW2ZLOOQXTCOBWGE2TEMRQUZZGKYLTN5XKMYLVORUG64VFMV3GK3TUVJTG633UMVZF62LPOM> and Android <https://github.com/notifications/mobile/android/CNPSZH43DFITXXUKDYWMBUD5Q7YY7A5CNFSNUABIM5UWIORPF5TWS5BNNB2WEL2ENFZWG5LTONUW63SDN5WW2ZLOOQXTCOBWGE2TEMRQUZZGKYLTN5XKMYLVORUG64VFMV3GK3TUVZTG633UMVZF6YLOMRZG62LE> . Download it today!
You are receiving this because you authored the thread. <https://github.com/notifications/beacon/CNPSZHY6DXFA65KMQRB6IN35Q7YY7BFCNFSM6AAAAAC65NV4FKWGG33NNVSW45C7OR4XAZNRIRUXGY3VONZWS33OINXW23LFNZ2KUY3PNVWWK3TUL5UWJTQBDQF3JJTSMVQXG33OUZQXK5DIN5ZA.gif> Message ID: ***@***.*** ***@***.***> >
|
|
Thanks for the log. I see over 500 timeouts in the log. I wonder if Windows is queuing the messages after a time out, so they get behind. I don’t know the internal working of the Windows Bluetooth stack so it hard to know what happens after the OS call to send.
Is there a way for me to get the log file after I do a ride. It might help me understand a bit more what is happening if I can correlate the Incyclist log with my bike computer’s log.
Thanks,
Fred
From: Guido Doumen ***@***.***>
Sent: October 1, 2026 2:51 AM
To: incyclist/.github ***@***.***>
Cc: FredPesp32 ***@***.***>; Author ***@***.***>
Subject: Re: [incyclist/.github] MyWhoosh provides resistance data Incyclist does not (Discussion #6)
fmts.log <https://github.com/user-attachments/files/32900565/fmts.log>
It's for me a bit hard to analyse as I don't see your side of the picture. From what I can see in the logs (see attached), I'm sending the mesages immediately and typically get a response within ~500ms
—
Reply to this email directly, view it on GitHub <#6?email_source=notifications&email_token=CNPSZH4JXSMVPI4SFPQBAW35RYSGNA5CNFSNUABIM5UWIORPF5TWS5BNNB2WEL2ENFZWG5LTONUW63SDN5WW2ZLOOQXTCOBWHE2TSNRTUZZGKYLTN5XKMYLVORUG64VFMV3GK3TUVRTG633UMVZF6Y3MNFRWW#discussioncomment-18695963> , or unsubscribe <https://github.com/notifications/unsubscribe-auth/CNPSZH4XTR4SUZIPAH3FH435RYSGNAVCNFSNUABIKJSXA33TNF2G64TZHM4TMOJZHA2TOOJSHNCGS43DOVZXG2LPNY5TCMBXGUYTIOBQUF3AE> .
Triage notifications, keep track of coding agent tasks and review pull requests on the go with GitHub Mobile for iOS <https://github.com/notifications/mobile/ios/CNPSZHY4LD53ILIH622NEOT5RYSGNA5CNFSNUABIM5UWIORPF5TWS5BNNB2WEL2ENFZWG5LTONUW63SDN5WW2ZLOOQXTCOBWHE2TSNRTUZZGKYLTN5XKMYLVORUG64VFMV3GK3TUVJTG633UMVZF62LPOM> and Android <https://github.com/notifications/mobile/android/CNPSZH3M23LUXU35XOZT6SD5RYSGNA5CNFSNUABIM5UWIORPF5TWS5BNNB2WEL2ENFZWG5LTONUW63SDN5WW2ZLOOQXTCOBWHE2TSNRTUZZGKYLTN5XKMYLVORUG64VFMV3GK3TUVZTG633UMVZF6YLOMRZG62LE> . Download it today!
You are receiving this because you authored the thread. <https://github.com/notifications/beacon/CNPSZH5XMLXQOGOBAUEJUKD5RYSGNBFCNFSM6AAAAAC65NV4FKWGG33NNVSW45C7OR4XAZNRIRUXGY3VONZWS33OINXW23LFNZ2KUY3PNVWWK3TUL5UWJTQBDVDRXJTSMVQXG33OUZQXK5DIN5ZA.gif> Message ID: ***@***.*** ***@***.***> >
|
|
The logfile is written in your Incyclist Home directory ( File: C:\Users$USER_NAME\AppData\Roaming\Incyclist\logs\logfile.json) The writes are only queued until the timeout is expired. But you'll see that subsequent messages are sent (and have responded). So I guess, queuing should not be an issue |
|
Thanks for the link. I should be able correlate the log files and it might give me a clue as to where the delay is happening.
…________________________________
From: Guido Doumen ***@***.***>
Sent: Friday, 02 October 2026 06:53:42
To: incyclist/.github ***@***.***>
Cc: FredPesp32 ***@***.***>; Author ***@***.***>
Subject: Re: [incyclist/.github] MyWhoosh provides resistance data Incyclist does not (Discussion #6)
The logfile is written in your Incyclist Home directory ( File: C:\Users$USER_NAME\AppData\Roaming\Incyclist\logs\logfile.json)
It is overwritten every time you start of the app.
The writes are only queued until the timeout is expired. But you'll see that subsequent messages are sent (and have responded). So I guess, queuing should not be an issue
—
Reply to this email directly, view it on GitHub<#6?email_source=notifications&email_token=CNPSZHYWUWPZF7QB76NBAX35R6XONA5CNFSNUABIM5UWIORPF5TWS5BNNB2WEL2ENFZWG5LTONUW63SDN5WW2ZLOOQXTCOBXGE3DGMRZUZZGKYLTN5XKMYLVORUG64VFMV3GK3TUVRTG633UMVZF6Y3MNFRWW#discussioncomment-18716329>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/CNPSZH37XLKD2JHQWQ5KODD5R6XONAVCNFSNUABIKJSXA33TNF2G64TZHM4TMOJZHA2TOOJSHNCGS43DOVZXG2LPNY5TCMBXGUYTIOBQUF3AE>.
Triage notifications, keep track of coding agent tasks and review pull requests on the go with GitHub Mobile for iOS<https://github.com/notifications/mobile/ios/CNPSZH4IJF3IQRTXRU6ZPAT5R6XONA5CNFSNUABIM5UWIORPF5TWS5BNNB2WEL2ENFZWG5LTONUW63SDN5WW2ZLOOQXTCOBXGE3DGMRZUZZGKYLTN5XKMYLVORUG64VFMV3GK3TUVJTG633UMVZF62LPOM> and Android<https://github.com/notifications/mobile/android/CNPSZHZMSKBZP4MFDBICDX35R6XONA5CNFSNUABIM5UWIORPF5TWS5BNNB2WEL2ENFZWG5LTONUW63SDN5WW2ZLOOQXTCOBXGE3DGMRZUZZGKYLTN5XKMYLVORUG64VFMV3GK3TUVZTG633UMVZF6YLOMRZG62LE>. Download it today!
You are receiving this because you authored the thread.Message ID: ***@***.***>
|
|
Hi Guido
I analyzed the log files and compared with the one from my bike. The time
of the “BLEServer out” message with cmd =” write” and the “BLEserver write”
come out at almost one second intervals (average of 996ms over 6 minutes of
data) The “BLEserver in” messages with type “response” which includes bike
simulation data came out at intervals of an average of 1.087 seconds over 6
minutes of data and slowly fall behind. My bike is receiving the messages at
the same rate as the BLEserver in messages. After about every 12 messages
the grade is a further 1 second behind. From my observation it appears that
the BLEserver out data matches what I see on the Incyclist screen but the
data coming to my bike matches BLEserver in messages.
Perhaps you understand the reason for this or if there something else I can
do help resolve my problem please let me know.
I attached the analysis spreadsheet if you are interested in looking at it.
For the BLEserver in messages and the XT450 Bike data I inserted blank cells
when there was not a message in a particular second to align the times
between the out and in messages.
Thanks,
Fred
From: Guido Doumen ***@***.***>
Sent: October 2, 2026 6:54 AM
To: incyclist/.github ***@***.***>
Cc: FredPesp32 ***@***.***>; Author
***@***.***>
Subject: Re: [incyclist/.github] MyWhoosh provides resistance data
Incyclist does not (Discussion #6)
The logfile is written in your Incyclist Home directory ( File:
C:\Users$USER_NAME\AppData\Roaming\Incyclist\logs\logfile.json)
It is overwritten every time you start of the app.
The writes are only queued until the timeout is expired. But you'll see
that subsequent messages are sent (and have responded). So I guess, queuing
should not be an issue
—
Reply to this email directly, view it on GitHub
<#6?email_source=notifications&
email_token=CNPSZHYWUWPZF7QB76NBAX35R6XONA5CNFSNUABIM5UWIORPF5TWS5BNNB2WEL2E
NFZWG5LTONUW63SDN5WW2ZLOOQXTCOBXGE3DGMRZUZZGKYLTN5XKMYLVORUG64VFMV3GK3TUVRTG
633UMVZF6Y3MNFRWW#discussioncomment-18716329> , or unsubscribe
<https://github.com/notifications/unsubscribe-auth/CNPSZH37XLKD2JHQWQ5KODD5R
6XONAVCNFSNUABIKJSXA33TNF2G64TZHM4TMOJZHA2TOOJSHNCGS43DOVZXG2LPNY5TCMBXGUYTI
OBQUF3AE> .
Triage notifications, keep track of coding agent tasks and review pull
requests on the go with GitHub Mobile for iOS
<https://github.com/notifications/mobile/ios/CNPSZH4IJF3IQRTXRU6ZPAT5R6XONA5
CNFSNUABIM5UWIORPF5TWS5BNNB2WEL2ENFZWG5LTONUW63SDN5WW2ZLOOQXTCOBXGE3DGMRZUZZ
GKYLTN5XKMYLVORUG64VFMV3GK3TUVJTG633UMVZF62LPOM> and Android
<https://github.com/notifications/mobile/android/CNPSZHZMSKBZP4MFDBICDX35R6X
ONA5CNFSNUABIM5UWIORPF5TWS5BNNB2WEL2ENFZWG5LTONUW63SDN5WW2ZLOOQXTCOBXGE3DGMR
ZUZZGKYLTN5XKMYLVORUG64VFMV3GK3TUVZTG633UMVZF6YLOMRZG62LE> . Download it
today!
You are receiving this because you authored the thread.
<https://github.com/notifications/beacon/CNPSZH2GKFLOY4WTA26KSFL5R6XONBFCNFS
M6AAAAAC65NV4FKWGG33NNVSW45C7OR4XAZNRIRUXGY3VONZWS33OINXW23LFNZ2KUY3PNVWWK3T
UL5UWJTQBDWLKTJTSMVQXG33OUZQXK5DIN5ZA.gif> Message ID: <
***@***.***>
***@***.***>
|
|
Hi Guido
I analyzed the log files and compared with the one from my bike. The time of the “BLEServer out” message with cmd =” write” and the “BLEserver write” come out at almost one second intervals (average of 996ms over 6 minutes of data) The “BLEserver in” messages with type “response” which includes bike simulation data came out at intervals of an average of 1.087 seconds over 6 minutes of data and slowly fall behind. My bike is receiving the messages at the same rate as the BLEserver in messages. After about every 12 messages the grade is a further 1 second behind. From my observation it appears that the BLEserver out data matches what I see on the Incyclist screen but the data coming to my bike matches BLEserver in messages.
Perhaps you understand the reason for this or if there something else I can do help resolve my problem please let me know.
I attached the analysis spreadsheet if you are interested in looking at it. For the BLEserver in messages and the XT450 Bike data I inserted blank cells when there was not a message in a particular second to align the times between the out and in messages.
Thanks,
Fred
From: Guido Doumen ***@***.***>
Sent: October 2, 2026 6:54 AM
To: incyclist/.github ***@***.***>
Cc: FredPesp32 ***@***.***>; Author ***@***.***>
Subject: Re: [incyclist/.github] MyWhoosh provides resistance data Incyclist does not (Discussion #6)
The logfile is written in your Incyclist Home directory ( File: C:\Users$USER_NAME\AppData\Roaming\Incyclist\logs\logfile.json)
It is overwritten every time you start of the app.
The writes are only queued until the timeout is expired. But you'll see that subsequent messages are sent (and have responded). So I guess, queuing should not be an issue
—
Reply to this email directly, view it on GitHub <#6?email_source=notifications&email_token=CNPSZHYWUWPZF7QB76NBAX35R6XONA5CNFSNUABIM5UWIORPF5TWS5BNNB2WEL2ENFZWG5LTONUW63SDN5WW2ZLOOQXTCOBXGE3DGMRZUZZGKYLTN5XKMYLVORUG64VFMV3GK3TUVRTG633UMVZF6Y3MNFRWW#discussioncomment-18716329> , or unsubscribe <https://github.com/notifications/unsubscribe-auth/CNPSZH37XLKD2JHQWQ5KODD5R6XONAVCNFSNUABIKJSXA33TNF2G64TZHM4TMOJZHA2TOOJSHNCGS43DOVZXG2LPNY5TCMBXGUYTIOBQUF3AE> .
Triage notifications, keep track of coding agent tasks and review pull requests on the go with GitHub Mobile for iOS <https://github.com/notifications/mobile/ios/CNPSZH4IJF3IQRTXRU6ZPAT5R6XONA5CNFSNUABIM5UWIORPF5TWS5BNNB2WEL2ENFZWG5LTONUW63SDN5WW2ZLOOQXTCOBXGE3DGMRZUZZGKYLTN5XKMYLVORUG64VFMV3GK3TUVJTG633UMVZF62LPOM> and Android <https://github.com/notifications/mobile/android/CNPSZHZMSKBZP4MFDBICDX35R6XONA5CNFSNUABIM5UWIORPF5TWS5BNNB2WEL2ENFZWG5LTONUW63SDN5WW2ZLOOQXTCOBXGE3DGMRZUZZGKYLTN5XKMYLVORUG64VFMV3GK3TUVZTG633UMVZF6YLOMRZG62LE> . Download it today!
You are receiving this because you authored the thread. <https://github.com/notifications/beacon/CNPSZH2GKFLOY4WTA26KSFL5R6XONBFCNFSM6AAAAAC65NV4FKWGG33NNVSW45C7OR4XAZNRIRUXGY3VONZWS33OINXW23LFNZ2KUY3PNVWWK3TUL5UWJTQBDWLKTJTSMVQXG33OUZQXK5DIN5ZA.gif> Message ID: ***@***.*** ***@***.***> >
|
|
I can't see your attachment. I guess this is because you were sending your comments via email. Could you log into GitHub in your browser and attach the Excel? Also: Could you repeat your test with Incyclist running on a Phone or Tablet (IOS or Android). That would exclude the BLE Server process, which is a bridge I only use on Windows (allowing the Incyclist App to communiate with the BLE stack). IOS/Android/Mac/Linux are not using that process |
please send me your UUID (From Settings->Support) via email or as a private message in Slack. Then I can have a look. Does sound like a messaging issue