You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I own a Cardiostrong BX70i Ergometer bike, which uses like many other fitness device brands an iConsole+ computer. Mine is a SM5200E with Firmware rev. 05 from the developer Chang Yow.
This computer connects well with current versions of Kinomap and iConsole+ app on most current ipados.
Home Assistant does not see my bike via bluetooth (all my other bluetooth devices work well).
I have checked the bluetooth link with BT Inspector and I can see the iConsole+ computer claiming to adhere to the Fitness Machine 1.0 protocol. There are regular updates to several characteristics.
So in general the device should be able to work with your integration. Maybe my problem is helping you to expand the list of compatible fitness devices in a future version.
If needed, I can provide you with the information read by BT inspector.
Best Regards
Bernd
The text was updated successfully, but these errors were encountered:
Hi,
I appreciate your FTMS idea very much.
I own a Cardiostrong BX70i Ergometer bike, which uses like many other fitness device brands an iConsole+ computer. Mine is a SM5200E with Firmware rev. 05 from the developer Chang Yow.
This computer connects well with current versions of Kinomap and iConsole+ app on most current ipados.
Home Assistant does not see my bike via bluetooth (all my other bluetooth devices work well).
I have checked the bluetooth link with BT Inspector and I can see the iConsole+ computer claiming to adhere to the Fitness Machine 1.0 protocol. There are regular updates to several characteristics.
So in general the device should be able to work with your integration. Maybe my problem is helping you to expand the list of compatible fitness devices in a future version.
If needed, I can provide you with the information read by BT inspector.
Best Regards
Bernd
The text was updated successfully, but these errors were encountered: