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

[BUG] manually adjusting the resistance, incorrect behavior! #3145

Open
zunfire opened this issue Feb 4, 2025 · 13 comments
Open

[BUG] manually adjusting the resistance, incorrect behavior! #3145

zunfire opened this issue Feb 4, 2025 · 13 comments
Assignees
Labels
bug Something isn't working

Comments

@zunfire
Copy link

zunfire commented Feb 4, 2025

Describe the bug
When manually adjusting the resistance using the app on both Android and iPhone, the behavior is incorrect.

On iPhone, the plus (+) button increases the value from 50 to 150, then to 260.
On Android, the plus (+) button causes similar incorrect jumps in value.
The bike switches resistance levels to 15 and 26.

Open the QZ app.
Connect to bike ID: 10571.
Manually adjust resistance using the plus (+) button.
Observe incorrect behavior in resistance values.

Expected behavior
The resistance should increase as expected when using the manual adjustment buttons.

Device (iPhone & Android models): Debug from iPhone (Android same behavior)
OS (iOS & Android versions): iOS 15.8.3
App Version: 2.17.0

Append a debug log:
debug-tis_feb__4_15_26_34_2025.log

@zunfire zunfire added the bug Something isn't working label Feb 4, 2025
@cagnulein
Copy link
Owner

you told me that the resistance values shows in qz are *10 is it right? is it true to all the resistance levels?

@zunfire
Copy link
Author

zunfire commented Feb 4, 2025

Yes, changing the bike resistance on the bike from 1 to 32 results in values ranging from 10 to 320 in QZ, with increments of 10 steps.

Apps like MyWhoosh seem to be able to increment in 10-step intervals as expected, suggesting that the issue might be related to the user interface (UI) behavior in the QZ app maybe..

@cagnulein
Copy link
Owner

cagnulein commented Feb 4, 2025 via email

@cagnulein
Copy link
Owner

cagnulein commented Feb 4, 2025 via email

@zunfire
Copy link
Author

zunfire commented Feb 4, 2025

Hi,

The resistance values now correctly display from 1 to 32, which is good.

However, there is still an issue with how the levels change when pressing plus (+) or minus (-):
The app does not differentiate between plus (+) and minus (-) the behavior is exactly the same.

When a resistance change button is pressed, the new value jumps towards a specific level X, which seems to be influenced by the ResistOffset setting.

If the bike's resistance value (R) is high, it decreases toward Level X.
If the bike's resistance value (R) is low, it increases toward Level X.
Once it reaches Level X, it remains stuck at that level.

The adjustment steps are not single increments. Instead, the new resistance value appears to behave something like this formula:
NewResistValue = (CurrentResistValue * 0.5) + ResistOffset

I also tried enabling debug logging, but no file was created. Let me know if there’s another way to collect logs for troubleshooting.

Did try "enable the resistance instead of the inclination in the bike options" then i couldent change level at all with the user interface.

@cagnulein
Copy link
Owner

I need the debug to understand it. Which is the issue with it?

@zunfire
Copy link
Author

zunfire commented Feb 4, 2025

I couldn't find the folder like the first time, but after restarting the iPhone, it appeared.
Here is the log from the latest test:

ResistOffset set to 5
Bike at resistance 1

Started QZ.
Pressed the Plus button → no change.
Changed bike resistance to 10 on bike.
Pressed the Plus button → resistance drops to 3 on bike.
Pressed the Plus button → resistance drops to 1 on bike.
Pressed the Plus button → no change.

If ResistOffset is set example to 20, the behavior differs.

debug-tis_feb__4_22_08_11_2025.log

@cagnulein
Copy link
Owner

cagnulein commented Feb 5, 2025 via email

@cagnulein
Copy link
Owner

ok i guess i found the issue. I would like to try to explain it.

By deafult QZ, for FTMS devices like yours, when you press the resistance plus and minus buttons, it's sending a inclination command because, usually, the FTMS devices are not handling at all a resistance values.

Your device, is sending the actual resistance value, but it doesn't accept the command to set a resistance value (i'm not fully sure about this but since you told me "Did try "enable the resistance instead of the inclination in the bike options" then i couldent change level at all with the user interface." i guess it's so, in case with a log I can check this)

So the only solution is to set an inclination value that could match better an increment of the resistance level.

Could I ask you why you would like to use the resistance tile? Would you like to use QZ standalone for your training sessions?

@zunfire
Copy link
Author

zunfire commented Feb 5, 2025

I never use QZ as a standalone app but rather as a link between my bike and MyWhoosh to enable automatic resistance adjustments. I think it worked, but I will have to double-check it again now.

Pressing the plus (+) and minus (-) buttons in QZ was just to check if I could manually change the resistance during a session to see if it was possible to adjust the offset value. That’s when I noticed this strange behavior.

@cagnulein
Copy link
Owner

hah ok so you shouldn't worry about this. using the gears tile with also mywhoosh you can have also virtual gearing on mywhoosh!
let me know!

@zunfire
Copy link
Author

zunfire commented Feb 5, 2025

It's been a long time since I used QZ, and when I selected it on the iPhone 7 with a small screen, I didn’t notice the gear tile, which was positioned far down by default. It’s working perfectly as intended. Big thanks!

@cagnulein
Copy link
Owner

thanks for the coffees!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants