Skip to content
Discussion options

You must be logged in to vote

I ran into this one myself as well. Not sure where it originates yet, but it is annoying.

Check rfkill via

sudo rfkill

You probably get a response like

ID TYPE      DEVICE      SOFT      HARD
 0 bluetooth hci0     blocked unblocked
 1 wlan      phy0   unblocked unblocked

To clear this, do a

sudo rfkill unblock bluetooth

This will enable the hardware again. Next, do a

sudo systemctl restart bluetooth

To restart the Bluetooth service. Then you can restart the OpenRowingMonitor app via

sudo systemctl restart openrowingmonitor.service

and everything should keep working, even after restarts.

Replies: 2 comments

Comment options

You must be logged in to vote
0 replies
Answer selected by LGallis
Comment options

You must be logged in to vote
0 replies
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Q&A
Labels
configuration issue An issue in configuring OpenRowingMonitor Main production branch Concerns the main production branch potential bug
2 participants