Am I correct in thinking that this app is only of use if you also have the Connect module on your bike? Otherwise most of the data will only be updated when your smartphone is near the bike. For example charging data will not update “live”.
I have update the first post with all the information now to be more clear.
In a nutshell this uses Bosch APIs (Cloud), not local access to the bike as that is not possible/does not exit. While such information (battery, range Kms) is only provided from your bike to Bosch Cloud (Flow app) while having the Connect Module and/plus the Flow+ subscription this information will only be available if the 2 are existing, so yes it is a requirement.
Yes you need to do this process during maxium 60 seconds, retrieve the code and add the device/bike
Now the connect module is required the app has for me less value. My bike Kalkhoff Image (2026)is standard equiped with a gps tracker. So to install the connect module has no added value for me. ( except for your app of course).
You know some bikes do come with the connect module pre-installed already. I have 2 bikes (MTB and City) from 2022 and 2023 respectively had it and it was not advertised. The brands do sell those GPS services, yours and for example Riese und Müller are doing it but there are reports that it’s not reliable and does not work in all countries than the option from Bosch itself. Double check and if not I’m sorry to see you go.
Hi,
Maybe you could also update the driving modes? 
https://www.bosch-ebike.com/de/produkte/fahrmodi
There is now also a cloud-free option.
You can read the API directly from the bike using an ESP bridge:
Update:
Hello,
I don’t think it’s necessary to display all the driving modes.
That would just be too much and make things too cluttered.
Leave it as it is—that’s my opinion.
Thanks, the app is working for me.
Hello,
Unfortunately, the mileage doesn’t match the driving modes.
Perhaps due to update 1.36?
Is there any way I can help?
Best regards
Flow+ - App:
homey-App:
Update:
Hi Goncalo,
The statistics from the Bosch cloud are actually not that straightforward.
There is also an adapter in ioBroker that accesses the Bosch cloud and retrieves the data.
Each riding mode has its own identifier here.
For every trip, there is a “Trip” folder where a subfolder is created for each mode.
The most recent trip is always labeled “01”.
I have completed 9 trips so far.
Perhaps that helps.
Right now, the values in your Homey app are completely jumbled.
Here is the comparison from today:
Grüße
Hi Goncalo,
I’m working on BikeBridge, an open-source Android project focused on Bosch Smart System interoperability.
We’ve independently reverse engineered most of the BLE Live Data Interface (LDI) using HCI captures, Bosch’s official LDI specification and the Home Assistant implementation.
I noticed you’ve done extensive work on the Bosch cloud API for Homey.
I think our projects are highly complementary:
- you focus on the cloud side,
- we’re focusing on the local BLE side.
I’d love to exchange findings if you’re interested.
One question in particular:
During your reverse engineering, did you ever investigate the local BLE communication or the LDI subscription sequence?
Even if not, perhaps we can help each other.
There is a similar project here.
I registered the bridge in Homey using the ESPHome controller app:
I had previously installed this Bluetooth bridge (ESP32).
Unfortunately, Bosch only allows you to add a single device.
I am now using just the Sonoff charging limiter and the Bosch Flow+ app with the ConnectModule; Flow+ is free for the first year.
