Wahoo RFLKT support

I always like to read such responses :). If you will need anything, feel free to write me, I'll gladly help with some tasks or help to improve existing Locus API. Anyway for such add-on, I think that all should already be there.

Hi Tomáš,

you are fast. Unfortunately I personally don't have this device, so I wish you many many users/testers :).

Seems the weather won't clear up fast, so I will try indoors as much as I can!

Well it should work the same, but don't expect the ANT sensors to work. Getting that to work would be quite tricky.

Hi, I'm really glad that it works for you, I was honestly scared that there would be an issue I haven't though of and it would crash horribly. :-)

Yes, barometric pressure/temperature would be a similar problem as the ANT sensors, mostly because I don't think there's a way to send the data to Locus. Of course if we just wanted to show the numbers on a RFLKT, that could work, but it won't get into Locus track recording. And, most importantly, as I don't own a RFLKT+ or any additional sensors, there's no way I can code and test it. But I guess if you really wanted, at least the temperature could be doable without having the device and I would give you an apk to test or something.

Loading pages takes a really long time because of all those navigation icons. Without the navigation page, loading takes a few seconds. So I think it's actually more annoying for me than for normal users who load pages just once. :-)

Speaking of which, adding pages is actually quite easy, this is the configuration: https://github.com/liskin/locus-rflkt-addon/blob/master/src/main/res/raw/display_cfg_rflkt_default.json

There's some explanation of that format in the iPhone API kit (the one you obtain after filling out a form here: http://eu.wahoofitness.com/development-api), but it's easy to understand even without that, so unless you're curious, don't bother. Letting the users select which pages they want is something I'd like to do, letting them design the pages from scratch is too difficult, I think.

As far as Android development is concerned, scala isn't all that different from Java. If you just want to add a page and some fields, that should be easy. The hardest part, I'm afraid, will be obtaining all the libraries (https://github.com/liskin/locus-rflkt-addon/blob/master/src/main/libs/README.markdown), setting up the android sdk and sbt and getting it to build. If you'd like to try it and need help, I think it would be best to use gitter: https://gitter.im/liskin/locus-rflkt-addon

Thanks again for the feedback.

Are you on Android 6? There's been some changes in permissions and some people have reported that this may cause problems with discovery. One user wrote:

"First, I somehow get the version on Play Store to work yesterday. I basically went into setting and gave the app permission to everything."

Can you please try that? At least give it permission to use location, as that seems to be necessary for BT discovery to work.

(I only got Android 6 since yesterday, did not have any problems with it, but I'm running a slightly newer version that's on the Play store. I should make a release, soon. :-))

Tomas thank you for your prompt reply! Yes I'm running Android 7 I believe. I manually gave the addon app permission and now all seems to be working!

Thank you!!

I think it will.

I have tested it on mtb singletrails. It worked well for me. Great addon. With navigation based on saved track would be perfect for me and it would help to keep my phone in my backpack;-)

Thanks for your great work.

Ohh.. I was dumb. I figured out how i can switch on the navigation (based on saved track).

I see that "navigate" shows me turn by turn navigation on both screens. Will have a go with that, thanks!

I think 1.2.28 was one of the defective firmwares

Hi Tomas!

Thank you for the tip. I've just upgraded the RFLKT firmware to the latest (1.2.29), and everything works fine with this.

Oh, they still release firmware updates? I thought they called it a day on RFLKT. :-)

Anyway, glad you got it to work.

I informed about the wahoo support, and they offered a method to upgrade the RFLKT firmware (see below):

Android Steps

"1. Open the Wahoo Utilities app.

2. Make sure the Wahoo device is powered on.

3. Click on the Wahoo device when it pops up.

4. Wait for the Wahoo Device to connect, once connected tap the grey icon of the device with the Bluetooth emblem in it 10 times to bring up the firmware update list. It will show what firmware is current, choose the latest firmware next to that update in the listor the one that is (recommended).

5. Allow the update to finish and try and reconnect the device to the Wahoo Fitness app when done.

6. Return to the Wahoo Fitness app, repair the sensor in the sensor settings and save the sensor to the proper workout profiles.

7. Return to the main wahoo fitness screen, select the proper workout profile and start your workout!"

Oh, that's a weird trick, tapping the icon 10 times. Anyway, it tells me there are no updates even though my firmware is 1.2.18. But I guess I wouldn't tell the difference anyway. :-)

I wish that was possible, but it isn't. RFLKT hardly keeps up with the texts I'm sending to it (actually with the latest wahoo library updates, even that works very very badly, to the point I'm considering just buying a Garmin and ditching this whole project). There's no way we'll be able to send a bitmap to display. :-(

Did you try the Ride with GPS app for iOS? They say it supports the RFLKT.

Hi Tomas,

Yes I did but ridewithgps does not allow to export/use route without paying...

Yeah, but it's probably going to be cheaper than hiring a coder to make an app just for you. :-)

Yeah! I get that :)

It was just in case you know...

mapping.txt is for decoding error reports, unlikely you'll ever need it. :-)

That's good to know - Thank you!

The notification screen doesn't seem to be working for me, but maybe that is because of Oreo?

You may need to tweak the permissions manually in your phone's Settings → Applications (it needs access to SMS/calls and also Contacts to resolve phone mumbers to names). This helped in the past with BT permissions on Android 6. Unfortunately I don't have a phone with Oreo that I can test this on.

(And I must admit that it's been quite a while since I did anything with this. It sort of works, but it's not perfect, and Wahoo has been very slow to respond to my e-mails about problems with their API, and the product has long been discontinued, so it's only a matter of time until I finally snap and buy something else. I really loved the idea of using Locus for everything, and the battery life of RFLKT is just superb, but the communication with it is so slow it's impossible to display a map, and without a map it's not as useful as I'd like. And the communication is flaky in a few other ways and I really doubt there's any chance of Wahoo ever fixing the code.)

The permissions change worked - Thank you!

Of course all messages are via WhatsApp these days, but good to have phone notifications.

Really pleased to have found this add-on. Thank you for writing it. Working well for me on Oreo.

Hi Mathew,

It's been quite a while since I last worked on this, so I suspect it might be somewhat tricky to get up and running, as things in the Android world change fast.

Anyway, I'd start here: https://github.com/liskin/locus-rflkt-addon#building and you might need to consult this as well: https://github.com/scala-android/sbt-android#usage, especially the part about ANDROID_HOME. You will need the exact version of android SDK that locus-rflkt-addons uses, and I hope sbt-android tells you which one it is and perhaps even gets it for you, but I don't remember exactly. You'll also need the wahoo api library, which is somewhat hard to get as you need to accept their ToC and then you'll be able to download only a very recent version without any documentation. This goes here: https://github.com/liskin/locus-rflkt-addon/tree/master/src/main/libs. As you won't be able to get the old library version that locus-rflkt-addon needs, I think the only option is that I send them to you, which I guess is against the ToC, but what can we do... ;-) (contact me via e-mail or IRC or whatever if you want the files)

If you manage to get it building, then (1) should be easy, (2) should be doable and (3) quite a bit harder, perhaps even impossible (especially if you want to feed the sensor data back to Locus; there's no API for that).

To be honest with you, it's a lot of work and isn't really worth it unless your goal is to learn about Android development (that was one of my goals back then).

Hi guys,

just quick two cents ... sending data back to Locus Map is doable. API already support sending heart rate values. Other values may be added on request.

Menion

@Menion Thanks for the clarification!

BTW, I did check https://github.com/asamm/locus-api before writing my answer because I remembered that the Android Wear addon probably does need to feed the HRM data back, but I couldn't find it. What did I miss? :-)

It's based on so-called "Broadcast actions", but instead of "action to do", is send "data to handle". And exactly, add-on for Android Wear needs this but because we needed it only internally, it is not officially in the docs. So when (someone) will need this, let me know.