HRM not working on fresh installation on a Pi Zero 2 #35
Replies: 4 comments 1 reply
-
|
Hi Michael, Thanks for catching this and reporting it! I can reproduce this as well. I am going to downgrade the bluethooth libraries again. This is weird, as I have tested it earlier in the process. Odd thing is, when I downgrade the libraries manually, it still won't work. I'm now seeing what happens when I revert to the complete original setup. Jaap |
Beta Was this translation helpful? Give feedback.
-
|
I've got HRM working again on BullsEye with Node18. I'l test further with BullsEye on Node 20, and Bookworm on Node20. |
Beta Was this translation helpful? Give feedback.
-
|
After some initial tests, it all seems to work. You can now install on bullseye and bookworm. HRM works, as does EXR. |
Beta Was this translation helpful? Give feedback.
-
|
I can confirm that ORM and HRM with a TickrX 2 now works on my Pi Zero 2 after running "/opt/openrowingmonitor/bin/updateopenrowingmonitor.sh". Thank you for the quick fix! |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
I'm afraid I am seeing the same error stack that I mentioned in the Pi Zero (1) discussion with a fresh OS installation on the latest v1beta_updates branch using a Pi Zero 2. Heart rate monitor (TickrX 2) is not recognized and clicking on the BLE icon throws this error stack:
Clicking on the ANT icon (without any ANT hardware being present) leads to ORM exiting:
Is this a known issue?
I used parts of my old config (rower-specific things, not BLE or ANT related) in both installations so this might well be a misconfiguration issue but so far I could not find anything obviously wrong.
Kind regards,
Michael
Beta Was this translation helpful? Give feedback.
All reactions