BT Sensor Connection issue

Ulrich Kiermayr shared this problem 1 year ago
Solved

Hi,


I have Wahoo Speed and Cadence BT Sensors. Since the last version (where the seperate ones are supportet) I have a connection porblem: The sensors are often (not always) not detected by Locus and therefore no speed readings are avaliable. I can fix this by manually starting the Wahoo management App. When the Sensors are detected by the wahoo app, they are also immediately recognized by locus.

Before the seperation I never had this issue.

Greetings, Ulrich.

Comments (20)

photo
2

Good day Ulrich,


I've noticed issue with connection to BLE sensors for longer time. In current existing Beta version, this system was already improved. Unfortunately I was forced to create small hack that tries to reconnect to device completely from scratch, so in the end, connection takes about 1-2 seconds longer. This I hope won't be a problem.


Feel free to try latest Beta version of wait on next Locus Map published on Google Play ( it will probably come quite soon ). Thank you for a report and sorry for a complications.

photo
1

Thanks, I'll check the beta in the next days.


Greetings, Ulrich.

photo
photo
1

Hello Menion,


since last update i have similar problem with BLE devices (hr sensor, speed& cad sensor) with locus. Before last update everything was perfect.


Cheers.

photo
1

Good day Przemek,

issue with reconnecting happen to you since new 3.23 app version? Even if you give it a while (minute), Locus does not (re)connect?

photo
1

Menion,


I had this problem with previous version, but then it was 1 on 20 (or less) track recorded so i cannot reproduce error. With this version (3.23) issue with conecction is every time when i try to record track.

Even if you give it a while (minute), Locus does not (re)connect?

Sometimes locus get connection with sensor after some time. Yesterday locus establish connection after 9min of ride, today it was 15min.

photo
1

Hello, that's bad. Thanks for a feedback anyway. I'll try to do third solution as combination of original and this new improved. We will see ...

photo
1

Last path work for me. Thanks.

photo
photo
1

With the latest 3.23.1 update, every time Locus disconnects from my HRM (whenever I walk too far from my bike) I need to unlock the screen and select it from a list manually. I think reconnection worked just fine with 3.23.

photo
1

Stupid never ending BT story. Thanks Tomáši, I'll check it more precisely and fix. Hope this will be last iteration ... sorry for a complications.

photo
1

Hello,


I have the same Problem with my Speed and Cadence Sensors. Sometimes the connection is lost, then the dialoge to select a sensor pops up. Same happens if i start the BT Sensors before i come into the range of the Sensors.


With the two of them it is especially confusing, since the PopUp does not say, for which sensor it has found a new device: Soooo (see screenshot) should I select the speed or the cadence Sensor .... hmmm .... ;-)


Greetings, Ulrich.

photo
1

I'm really sorry Ulrich. One reported problem, and fixed, cause issue somewhere else and I was too lazy to do some more intensive field testing and here is result.

Anyway with latest Beta version, I have quite good results and during last week it never happen to me that sensor did not connect during first few (max. 10) seconds.

So if you will have time, try to use for your rides latest Beta. Thanks

photo
1

Hello Menion,


I tried the Beta, and the annoying/confusing Dialogues are gone and auto (re)connect works .... BUT:


When connecting both speed and cadence are connected to the same sensor, which does not make sense. I have the feeling that there is kind of "crosstalk" between the settings of the speed and the candence sensors.


Cheers, Ulrich.

photo
1

Hello,

both main issue solved, I'm glad to hear it.


Any connection to same sensor ... and why you connect to this sensor separately and not using above "Bicycle speed & cadence" sensor only?

photo
1

Hello,


Sorry for beeing unclear: I have to seperate Sensors: a dedicated BT Speed Sensor and a dedicated BT Cadence Sensor (http://amzn.to/2pWEnFU). Therefore I cannot use "Bicycle speed & cadence". What I need is Speed connecting to the BT Speed Sensor and Cadence connecting to the BT Cadence Sensor.

But somehow Locus only remembers the last one connected to and then both Locus Speed and locus Cadence are connected to the same sensor (either speed or cadence) and not to the correct seperate ones.


Want:

Locus Speed -> BT Speed

Locus Cadence -> BT Cadence


Have (Bug):

Locus Speed -> BT Speed

Locus Cadence -> BT Speed


*or*


Locus Speed -> BT Cadence

Locus Cadence -> BT Cadence

photo
1

Thanks Ulrich,

I believe I've got it. Will be fixed in next version.

photo
1

Hello,


Looks good now. I'll keep testing it, but I would say, now it works correctly.


Thanks a lot, Ulrich

photo
1

Hello all,


i have similar problem like Tomas described two weeks ago. I am on version 3.23.2. In addition sometimes reconnection is not working for various reasons:

- device selection is empty

- Locus stuck on "connecting" message

- BT has to be enabled, then stuck on "enabling BT"

- few times I had to restart the phone because it look like whole BT stack was broken


I am not using exact wording because do not remember it.

I have also say that reconnection sometimes works like a charm, not visible for the user.


thanks

i

photo
1

Good day Ivan,

this is really unfortunate. During last days/week I had tested current implementation quite a lot and it seems to work quite well. From comment of Ulrich, it seems I'm not alone.


Hmm what to do here. Restart device, remove association for certain device, if even after issue remains, I should prepare some special version that will print out some information.

Btw. are we talking here about BT 4.0 (BLE) devices?

photo
1

Hello Menion,


it is strange, but issues mentioned month ago never happened again.


thank you

i

photo
1

This sounds to me like a good news, thank you!

photo