Fitbit Air Won't Stay Connected
I realise this might be an issue that Google / Fitbit need to address, but maybe something can be done on the Hammerhead / Karoo side? Today's update had a comment that made me think they were trying to address it and it is better, in that my Karoo (Audio?!) now shows as a device, but when I reboot the Karoo, it repeatedly connects and instantly disconnects.
-
The first time I added the fitbit air hr sensor to my karoo 3 it kept connecting and disconnecting and I thought it was not going to work. Then I added it while a ride was in progress and it worked. It shows up as "Karoo BT audio" in the Google health app. But: during a 4 hour ride it lost connection twice and I had to delete and re-add the sensor in karoo. I also have to delete and re-add the sensor on the karoo after every reboot.
Haven't tried it since the recent 1.634.2440 update which as you say mentions BLE bonding and sensors not staying connected. I'm hoping maybe hammerhead dev team is already working on the issue.
Update: I tested the updated software today on another 4 hour ride. It feels like maybe it behaves even less stable than before the update. I had many dropouts, sometimes the HR would cycle on and off over and over until I clicked "reload" on the hr sensor and then it seemed to be more stable. But I still had dropouts after that too. I did not have to delete and re-add the sensor again yet, so maybe one step forward one step back.
Please sign in to leave a comment.
Comments
1 comment