Sending/Receiving Data via Bluetooth with Mobile Apps (Kinomap)

[rywell]

Hello!

I've been using ORM for a couple months now on an Xterra ERG 600w. First, a huge thank you to everyone who's worked on this project. For context, I'm a front-end developer and haven't worked with a Raspberry Pi before so most of this is new to me. I decided to try it for fun. I've been able to get everything set up and working but have been unable to get any mobile apps working (side note: I am able to use the "send to Strava" functionality successfully).

I know other people have used Kinomap, so I've been working mostly with that one. I am able to connect my iPhone over BLE successfully. I have the setting on "FTMS Rowing" (although, I've tried every other value for this with no luck). When setting up equipment in the Kinomap app, it's able to recognize/locate the service and connect successfully after selecting the "FTMS" type from the list. At this point the app asks the user to start rowing as a test --and this is where it fails to receive any data. Should ORM be able to send real-time data like this or am I misunderstanding? Any assistance is appreciated and/or ideas for troubleshooting.

[JaapvanEkris]

You are welcome!

First of all, please consider upgrading to https://github.com/JaapvanEkris/openrowingmonitor/tree/v1beta_updates as it has offers a lot of added functionality and improved stability (and a slightly improved frontend, although both Peter and I are absolutely no frontend dev's). It will require changing the configuration for your rower, but it deals with metrics a lot better, and thus offers a lot more metrics to receiving apps at times they expect them.

ORM offers real-time data via all Bluetooth (and ANT+) channels. I personally use it to row in EXR (see https://exrgame.com/) almost daily using ORM via the BLE FTMS and BLE C2-PM5 protocols. So if Kinomap isn't receiving, something might be wrong. Do you get an error message in the syslog (on Raspberry Pi OS BullsEye it can be found in /var/log/syslog, all marked with npm)?

[rywell]

Thanks for your response, and sorry for the delay. I wanted time to install the v1beta_updates as you suggest on a new OS installation. I have done that and am still unable to get data to Kinomap (or a couple other apps I've tried).

I checked the syslog and don't see any obvious errors for items marked with npm. I've attached a file with the relevant log entries. The rowing session in this log was performed while attempting to send data to Kinomap.
syslog-npm-items-02-10-24.txt

One other thing I noticed when running through the installation doc this time is that when running sudo systemctl status webbrowserkiosk in the terminal I get Unit webbrowserkiosk.service could not be found.

As an aside, would you prefer I move this post over to the other discussion under v1beta_updates?

[Gordon-Shumway2]

Hi rywell,

not sure how you are able to get dmesg output without ssh access - are you using a shell via bluetooth?
Anyway - to enable ssh on the pi create an empty file at the root of your SD card and call it "ssh" (no file extension). After a pi reboot you should at least be able to reach the sshd on the pi. If you can connect but do not have a username/password (quite likely) then please follow
https://github.com/raspberrypi/documentation/blob/develop/documentation/asciidoc/computers/configuration/headless.adoc#configure-a-user-manually

The encrypted value for password "redgrave" is
$6$dxI8UnOvBv8Bzun/$0LA8TxL5c5tpryqYZ5y/hrXa5mLui4GjVW8tfqpFs/C8ivefmEPm5lW8xRtLRVAJd/JGAAwPwWnZF5/f6VO10/

back to topic: the first bluetooth error showed up 240 seconds / four minutes after boot. I would assume that this is when you tested the Kinomap connectivity. That would be a first hint where the problem might lie. Will need to do some read-up on bluetooth libraries within ORM and will be back soon.

kind regards,
Michael

[Abasz]

not sure how you are able to get dmesg output without ssh access - are you using a shell via bluetooth?

You can attach a screen and a keyboard and you can log in via local terminal.

Also it is possible to set up the ssh when you flash to the SD card via the imager. There is a setting option before you flash and then it's enabled by default.

@rywell can you install something like efr connect (android: https://play.google.com/store/apps/details?id=com.siliconlabs.bledemo) and check if the pi actually shows up at all?

I suspect that the Bluetooth is not properly enabled (though it is interesting that fresh install does not solved this)

[Gordon-Shumway2]

Kinomap IS able to connect to ORM, but the subsequent connection to exchange data fails. The Iphone is also able to connect to the pi via bluetooth.
Some days ago there were changes to the bluetooth libraries on the v1beta_updates branch (they broke HRM functionality) that may be the cause for this issue. As these changes were specific to that branch I would recommend to continue with troubleshooting within the discussions section at
JaapvanEkris#39

[rywell]

Just to follow up on a couple points:

• Yes, I have a screen and keyboard attached directly to the PI
• The embarrassment of the typo was motivation enough to get SSH working before my last reply
  • I simply needed to remove the keys on my other computer and allow them to be generated again with the new OS installation
• Yes, I have always been able to connect my iPhone to the PI, and, at various points, have connected a bluetooth keyboard and mouse successfully.
• I just installed a desktop on the PI, so that I can troubleshoot a little easier (I'm not great with the CLI) --not sure if this will conflict with ORM.
  • I was able to connect Airpods and get audio through them after installing the desktop.
  • Kinomap is still not receiving data
• Also, not to complicate things further, but this issue was originally on v1beta and I've only just updated to v1beta_updates in an attempt to resolve it --however unsuccessfully.
• I have not done the next steps in the post created under the forked repo. I will reply there with what was requested.

Thanks, again!

[Abasz]

I understand that it's able to connect. I recommend erf as it is able to show the data that is being broadcasted. We need to see where things go wrong. Ftms is at spec so it should work.

As you said I am not able to reproduce this either which is utterly strange