Bluettoth connection issues with MyHomeFit

[Gordon-Shumway2]

Hi,

can anyone confirm that the current version of openrowingmonitor works with MyHomeFit v1.2.4 (264)? I am unable to connect via bluetooth. MyHomeFit hangs at "Geräteinitialisierung" (initializing device) while openrowingmonitor reports

Dec 22 12:20:18 pirow npm[698]: ble central connected: 54:2e:14:XX:XX:XX
Dec 22 12:20:18 pirow npm[698]: rssiUpdate 127

This happens on a Pi Zero 2. I tried it with two android phones: xiaomi Poco M3 running MIUI Global 12.0.9 and a yoga tablet running LOS 18.1.

Any hints on how to debug this further are very welcome :)

Kind regards,
Michael

[laberning]

Hi Michael,

possible that we broke the support somehow.

MyHomeFit does not yet implement the full BLE FTMS Rower profile, instead Holger from MyHomeFit did a custom implementation based on some Sampledata from OpenRowingMonitor.

I'll have a look at it in about a week.

If you want to debug the BLE specific parts nRF Connect for Android is a good tool to analyze the BLE implementation.

Cheers, Lars

[laberning]

First of all, thanks for reporting this.

What happened here was, that there has been a sub-dependency update for the module @abandonware/bluetooth-hci-socket that currently has a compatibility issue with the bluetooth module @abandonware/bleno which we use (see here: abandonware/node-bluetooth-hci-socket#31).

Pretty nasty to figure out. I've now explicitly pinned node-bluetooth-hci-socket to the working version until there is a fix.

Can you check if BLE now works as expected on your device?

You can update your device by running updateopenrowingmonitor.sh

[Gordon-Shumway2]

Hi there,

I can confirm that after running 'updateopenrowingmonitor.sh' openrowingmonitor is now able to connect via BLE to MyHomeFit!
I am now also able to connect to ergometer-space when using openrowingmonitor's C2 emulation.

This is cool stuff and a good start to the new year!
Thank you for your work, it is much appreciated.

Ta,
Michael