Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

.setName for Bluetooth service seems picky #12

Open
tamccauley opened this issue Apr 20, 2022 · 1 comment
Open

.setName for Bluetooth service seems picky #12

tamccauley opened this issue Apr 20, 2022 · 1 comment

Comments

@tamccauley
Copy link

In main routine, if I have the following, Zwift works fine: Bluefruit.setName("K");

However, if I put Bluefruit.setName("KbikeBLE"); in there, the cadence part seems to work fine and lists the service as KbikeBLE, however, the Power Source connection in Zwift show the service as K36. It does connect, but immediately I get a No Signal alert on that service. Speed shows up but Power does not. I didn't pick up the latest release that allow FTMS to be disabled but I believe I have FTMS disabled on my own.
I guess I must have something messed up as I sense that other folks have this working without a problem.

@tamccauley tamccauley changed the title Name of Bluetooth service .setName for Bluetooth service seems picky Apr 20, 2022
@ajs123
Copy link
Owner

ajs123 commented Apr 21, 2022

Zwift seems to work fine for others with FTMS disabled, but it's not clear that it's working with FTMS. Are you using V1.1, or a download from the main repository? There was a post-V1.1 fix to remove reporting of resistance with FTMS, to be consistent with the fact that resistance can't be changed.

I did notice when I tested with Zwift that it abbreviated the name. I do wonder whether Zwift tries to do things that are dependent upon the name. Some stationary bikes that provide inflated power estimates have apparently been a problem.

I'm presently using Wahoo SYSTM and let my free Zwift trial period expire, so my ability to test is limited! Any systematic testing is appreciated!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants