Bosch connect KIOX integration

Hey Menion,

thanks for your quick reply.

Well is not really special It's very wide spreaded like garmin and polar that you support.

Therefore I'm wondering why it's not support because is leading the eBike scene as Pedelec supplier.

I think a bt connect interface would be just enough to query a few information like speed, heart rate, cadence and transfer the GPS date of the route to Locus.

https://www.bosch-ebike.com/us/produkte/kiox/

cheers

Hello,

I'm trying to find out if this is really possible and I see that direct connection from Android device is currently used only with their own Android application. I see here a big difference compare to existing POLAR etc support. These various sensors are directly made as a source of data for other apps, so they use the standard BT interface. WIth Bosch Kiox it is different. It is already a final product that consume data from other sensors and I'm not sure that any 3rd party app may simply connect and read it's data.

So sorry, for now, I do not think it will be done in the near future. Thanks for understanding.

Menion

Hey Menion,

sorry for my late response.

For clarification: with KIOX you can't navigate.

It's about to connect both apps Locus Map and Bosch eBike Connect to transfer routing (track) information to LocusMap. I.e Komoot does this already.

But It seems you understood it already. Maybe it's needed to get in contact with Bosch.

Cheers

Hi Menion,

I reopen this topic as I have bought a brand new VAE using the latest KIOX system which is now able to display navigation on it.

Currently, Bosch eBike Connect (the application provided by Bosch for their systems) can be connected via bluetooth with a smartphone containing a navigation system (Locus Maps for us) and displays the navigation instructions directly on the KIOX screen.

They are currently providing the connection to the 'Komoot' application.

Maybe they have developped an API which allows to get navigation instructions from navigation systems to display it on their screen, and it will be nice to have this kind of feature so we can connect our Locus Maps application directly.

Can you get in touch with Bosch to be able to connect to Locus Maps in their Bosch eBike Connect application?

So maybe it will be possible to connect also Locus Maps and not only 'Komoot' to their application.

Regards,

Laurent

Hello Laurent,

thanks for extra information. We plan to invest a time to a lot better support for sensors & e-bikes next year 2021.

Menion

Hi Menion,

Thanks for your answer.

I think that the connection used by the Bosch Kiox is both ways, that means that you can retrieve information from the Bosch Kiox as speed, cadence, and input some data to it as the navigation information.

If you have a look at the Bosch displays here, if you put your mouse on the 'i' icon next to 'Third-party apps' you can see that there are already many smartphone applications.

So hopefully next year we can get something intersting with Locus Map and Bosch e-bikes and probably other e-bikes systems.

Seconding this. Any news?

Hi Menion,

Any news about le Boch eBike connection ?

I have seen that you have released a new version of the App which is version 4, but the eBike connection is still missing.

This is more than 8 months that I do not use Locus Map anymore as I have conflicts with the GPS sharing between Locus Map Pro and the Bosch eBike app with Bluetooth connection.

I have downloaded instead Komoot as it is fully compatible with Bosch eBike App. I use it everytime I go out for a ride and have event paid the 29€ for the world map.

I would really like to go back to Locus Map, v4 and even pay for the gold member to get access to every functionnality, but the Bosch eBike is still missing.

Do you have any plans ? Any date when the application will be compatible with Bosch eBike App ?

Thanks

Hello Laurent,

I do not like promises so I won't do that. Anyway right now I'm working on completely new system for work with sensors. Once, all current sensors will work, next step is support for Power meter and improvements in dashboard. Support for additional sensors, eBikes etc may comes later. It will anyway depends on few factors, also complexity of implementation. This anyway needs to be examined first.

Menion

Hello Menion,

I come back to you regarding this thread.

Have you been able to implement the new system for sensors?

Do you have a plan for eBike sensors too? And when?

Hope to hear good news soon from you.

Thanks,

Laurent

Hello Laurent,

unfortunately, Dashboard & e-bike tasks have to be moved to the next year 2023 because of more important tasks (problems with the Wear platform, geocaching, LoPoints support, ..).

I hope you solve this soon. Because we need this and we have been waiting for it for a long time. Thank you

Hm, I have had my phone and Flow app paired with my bike for four months. Are steps 1 and 2 still necessary? I do not see a "smartphone" option in step 1 (see screenshot). And then Locus Map does not find anything.

I have Kiosk 300, which should be the same as Kiosk 500, just smaller display.

By the way, I guess I misunderstood. For me the main application was to be to use Locus Maps to push routes and navigation to the display. But now looking at it more closely, this is not really possible in principle, or is it?

Hi Tomas, yes, this is currently not about connecting to Bosch servers. This part heavily depends on Bosch itself and they still ignore our attempts for email communication.

What this change brings is a direct connection of Locus Map running on Android device over Bluetooth to the bike itself. Then app may read mentioned data and allows to display them on the Locus Map dashboard.

Hm, and any idea why it will not connect? I installed the Beta? I cannot get past step 1, there is no "smartphone component"

Hello Tomáš,

maybe the description in my post is incorrect. Key is to have bike and smartphone paired. If you have it, give a try to connect Locus Map to the bike.

Hm, Locus just does not see it then:

Understand, thanks. Seems we will have to brought a bike for testing ... 😶

Here, Bosch Smart System v19.54.0 connected via BT and Flow app can access the bike, but Locus v4.35.0 does not find the bike. I have unlocking via BT active, maybe this is important.

Maybe you have a bike rental around you or a friend owning one?

I unlock the bike with the Kiosk device, not with the phone via BT, so I do not think tha5 is important.

Great to see progress here, it's such a pity it Locus does not find the bike. What's curious is that the Bosch Smart System EBike appears under GPS Bluetooth 3.

Bei mir funktioniert es auch nicht

Data transfer via the Flow app isn't working for me either.
It would be great to have a detailed guide for this.
In any case, the instructions mentioned earlier don't work for me...

Hi Larry,

I had a small vacation so the 4.35.0.5 is not yet published, sorry. Check a Beta version folder at the end of this week for sure.

Unfortunately 4.35.0.5 doesn't do the job. It finds the Bosch Smart ebike when the bike is put in bluetooth pairing mode and connects. However it captures no data. If Locus is closed and restarted it fails to connect.

Habe die Beta Version heute auch getestet, aber funktioniert leider nicht. Neu ist, daß das Bike jetzt gefunden wird, aber dann nichts mehr passiert.

Bei mir funktioniert es, aber leider nur mit 3 Werten, Tempo, Akku und Trittfrequenz, eingestellt im Overlay vom Dashboard.

Bosch Smart ebike

Kathmandu Pro 800 2025

Hi all 👋

@Menion: The spec is good news because you can now work much more targeted – of course it's sad that you need to implement from scratch the "inverse" connection direction, but that's definitely less effort than getting Bosch eBike integration running with the previous try-error-approach using the "wrong" direction 🙂

I did look at this spec pdf

• I'm quite happy because the API offers most of the data I'm strongly interested in (cadence, rider power, battery SOC) which do allow several interesting computations in the future (e.g. battery drain related to rider power & slope & speed, increased accuracy of Locus' kcal consumption computation)
• Speed is IMHO only interesting in times of bad or no GNSS signals (e.g. in narrow valleys or bad weather) to increase precision of Locus' speed data.
• I don't have any idea what bike's ambient brightness, time or odometer might be useful for because smartphone has this data natively.
• I'm missing motor power (to know proportion between motor & human power) and assist mode (Eco/Tour/eMTB/Turbo to see mode distribution during the trip and to learn better which mode offers which range under which conditions). As the spec explicitly tells Live Data Interface is experimental and v1.0.0, to me, it makes the impression Bosch is open for feedback. @all Would you also like both motor power & assist mode? What do you think could most motivate Bosch to add them? Maybe if several users ask Bosch to add them, so repeatedly over a longer time the same request? Or is it better if Locus team asks because it's probably one of the first professional teams to make use of the API, so a welcome multiplier & mental sparring partner? Or a combination of both? Or will the combination be "too much"?
• I think it's not really sad that remaining range is not offered because if Locus does track recording as well as navigation, it can provide a much more useful/precise remaining range estimation: It knows the elevation profile, surface type & smoothness of the route ahead (future) and can compare to similar slopes & surfaces in the recorded track (past), while the bike does know nothing about the future so it does not know what to compare with – resulting in very bad range estimations when you have a big ascent/descent ahead.

Best regards, Georg

I forgot: Does anyone besides me want a possibility to use the Kiox display for navigation like Bosch Flow app does? Do you see a way to implement it? In my experience, Flow app is far inferior in bike routing than BRouter + LoRouter, e.g. it cannot recalculate when offline, it cannot use coordinates as input, it does not offer customization of routing profile, at crossings I repeatedly did not understand where to go,... If Locus used Kiox as display, battery of the mobile would be drained less and the mobile could rest within a bag, so well protected from the elements.

Yeah, I would be interested. I tried the Flow app, but it just stops updating as soon as my mobile turns the screen off. Maybe I need to do some fiddling with battery settings htat I needed to do for Locus so that it was able to record GPS tracks, but it would be cool. But I am not sure if this can offer navigation, does Bosch expose that?

This is a long time that I am waiting for this to be implemented and for sure I am waiting for this to work with my Bosch eBike MTB.

I own a bike with the correct engine but the interface I have is the original Kiox and not the latest version, so I'd love to have backward compatibility as Komoot is doing for the Bosch eBike connection.

I own a QuadLock system to have my phone on the handlebar and use it as display to display the track I am following.

If LocusMap can do the same thing without to having to change all the display system to Nyon that will make me invest in +300€ to be compatible, that would be the best solution for me, but i think I am not the only one to have this backward compatibility.

So please, Menion and others at LocusMap, try to find a way to be compatible with the older systems like Kiox to connect to the Bosch eBike system

I did try with Locus v4.35.0.8 beta with default configuration and without connecting to my account – so it's tested in free mode / without subscription. For the test, I customized the track recording side panel display like this, and these values I am referring to in the further text:

Feedback: You're on a good way! 🙂

1. For final release, we shall rework the setup explanation. For example, step 2 is completely unclear to me; in my Flow app interface, in components, I did not find anything that could translate to "Smartphone". I've the impression (!) 2+3 are already done if Flow app works fine – so before 2, we might tell something like "If Flow app is already fully operational (i.e. shows bike data), following 2 steps can be skipped"
2. Values were coming, updating with low latency, all seemed correct only battery SOC was shown 1% higher than in bike computer (which is IMHO not worth any fixing effort). When switching modes, they were correct just one mode was shown without the tailing "+". I changed mode list in Bosch Flow app, saved, changed modes back as the were before, then the mode name came correct with tailing "+".
3. I don't recall what exactly happened, but suddenly no values came any more – i.e. the display was as in the screenshot. I tried several approaches, e.g. stop track recording & restarted, I terminated Locus and Flow app, I switched off the bike, switched off Bluetooth in phone, etc. Nothing caused to get values again 🤷‍♂ Interestingly, after the bike ride, Locus map content button opened the side bar but it stayed blank until I terminated Locus and started it again – not usual.
4. The wording "Fahrradausrüstung" is very unspecific. I don't recall what was shown in the short time when data was coming. Maybe we can find a wording that's more clear, intuitive 🙂 What exactly shall it mean? From the icon I'd guess it is lights on/off but I cannot remember to have seen a value on/off or the like.
5. The wording "Leistung (3sek)" and "Power" are unclear – is it bike's or rider's or total power? By comparing to bike display I learned it's rider's power, i.e. how strongly I move the pedals. Maybe you could change the wording (e.g. "Your power" or "Human Power" or "Rider power" or the like) and/or icon (e.g. adding a human to the lightning).
6. When values were coming, IIRC (but maybe vice versa) "Assistierter Modus" did show Eco, eMTB etc. while "Assist profile" stayed as "–". What is "Assist profile" expected to show?
7. Track's multiple charts display do not show any sensor data, and track exported as GPX contains no sensor data. I hoped to see sensor data in both – but maybe this is related to the values not showing any more.

Attached log files.

Best regards, Georg

Hi, today I did another test with v4.35.8 during a longer ride, duration 2h15, divided into 2 segments with a break in between. Bottom line is same as in above's post: Current state is already usable 👍 and mainly joy & usability would benefit if some details get some care.

As in 2. of above post, values were correct & quickly updated with 2 exceptions:

1. This time, battery SoC in Locus was 2% higher than on bike display whenever I compared. As written, IMHO issue worth a fix because 2% is probably within error margin of SoC measurement precision, and as long as the difference is constant, the value is still easy to interpret.
2. Assist mode Tour+ was shown as Tour so + was missing. Again, after changing modes list in Bosch Flow App and afterwards changing the list back to previous state, the + appeared in Locus (see screenshot), so the value can be processed. I now programmed my bike such that Tour and Tour+ are not in my modes list, so we can see whether just the + sign is omitted or a completely wrong modes list is used.

Concerning 3. in above post: Bike connection was stable for over 1h 🙂 with one exception (after I took a break) for which I assume I now understood the precondition:

• After stopping recording, shutting off bike, having a break, starting the bike, starting recording – values not recorded. Phone's BT was not turned off but it lost connection to bike because bike was off. IIRC Locus was still showing sensor as connected.
• After stopping recording, shutting off bike, having a break, starting the bike, disconnecting the bike in sensor manager and connecting it again, starting recording – values are recorded

@Locus team: Are values also not coming from other sensors if sensor is switched off and connection is not switched off in Locus? Or is it specific to Bosch smart system because its "different" way of Bluetooth connection? In any case, would be much more convenient if Locus did not get any values for e.g. 1 minute, it would take actions. At least battery SoC shall always come, even when standing still, so no values at all are a strong indicator for broken connection. Action could be e.g. that Locus displayed a popup "BT connection to sensor <name> active but no values for over 1min. Disconnect and reconnect? <no> <yes with countdown of e.g. 10secs>" so if desired, user can cancel automatic reconnect by tapping <no>, but if user does nothing, system "tries to heal itself" and values are likely coming again.

Concerning 4. in above post: "Fahrradausrüstung" never showed a value. Also when light was on. As the wording is very unspecific: What is expected to be shown there?

Concerning 6. in above post: "Assistierter Modus" did show Eco, eMTB etc. while "Assist profile" stayed as "–". What is "Assist profile" expected to show?

Concerning 7. in above post:

• Track charts did now show sensor data 🙂 I do miss 3 values:
  motor's power (to see distribution between motor & human power)
  battery SoC (to see how much it drains depending on situation)
  assist mode (strongly affects power and battery drain).
• GPX export did now contain sensor data 🙂 but only power and cadence. It would be very nice if all recorded sensor values were in the GPX because that allows to freely analyse – also in ways Locus does not provide.
  Example GPX snippet:
  
  

  <trkpt lat="48.0264057" lon="7.7820930">
  	<ele>220.47</ele>
  	<time>2026-09-18T19:59:23.999Z</time>
  	<hdop>2.00</hdop>
  	<extensions>
  		<power>158.0</power>
  		<gpxtpx:TrackPointExtension>
  			<gpxtpx:cad>79</gpxtpx:cad>
  			<gpxtpx:speed>6.7611113</gpxtpx:speed>
  			<gpxtpx:course>53.072662</gpxtpx:course>
  		</gpxtpx:TrackPointExtension>
  	</extensions>
  </trkpt>

  
  
  
  

In track statistics, sensor values appear – I'd like to see also

• average power of motor
  and
  power distribution human + motor, e.g. <icon human> 73%, <pie chart> <motor or gears icon> 27% (so similar to Bosch display, see screenshot)
  It's a good feeling to see that I do most power myself 🙂
• battery SoC at start and end, and SoC drain, e.g. 85% → 70% (-15%)
  For example, this helps to understand later on why I used weak assist mode despite strong slope – because of low SoC
• theoretical range, i.e. if my tour had 25km and battery drain was 15%, I could drive 25*100/15=166.7km with the mix of modes and the power of motor support.
  This is "just" for convenience, i.e. users do not have to do the maths every time but the computer computes
• modes distribution as pie chart (see screenshot)

Referred screenshot of Bosch bike display Kiox 300:

Best regards,
Georg

Which Locus version did you use? For my setup, in v4.35.8 cadence is as on bike display.
Forget my question, as in your post further down, you write cadence is now correct with newer Locus version

For me, it was a workaround to change the modes list in Bosch Flow app, than change it back to what it was. Does it also work for you?
I don't mean the workaround for use in the long run, just to know whether behavior across devices is identical 🙂