Raspberry Pi Errors

[janstadt]

Describe the bug Unable to get the binary to run. Keep getting a segmentation fault. Im using this bluetooth dongle: https://www.amazon.com/dp/B06XRLF8B5?psc=1&ref=ppx_yo2ov_dt_b_product_details and after following some other steps i've gotten the service to run as i was worried that it was why qz wasnt able to run. I see you recommend a tp-link one that i was going to buy but read the reviews on amazon and thought it wasnt going to work outta the box on the pi. Definitely can return the one i bought if people think that it might be the issue.

Bluetooth service output:

pi@raspberrypi:~/qdomyos-zwift/src $ /etc/init.d/bluetooth status
● bluetooth.service - Bluetooth service
     Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor preset: enabled)
     Active: active (running) since Thu 2022-08-11 18:58:50 BST; 1h 2min ago
       Docs: man:bluetoothd(8)
   Main PID: 852 (bluetoothd)
     Status: "Running"
      Tasks: 1 (limit: 415)
        CPU: 10.089s
     CGroup: /system.slice/bluetooth.service
             └─852 /usr/libexec/bluetooth/bluetoothd --noplugin=sap //<--this is what i had to add

Aug 11 18:58:50 raspberrypi systemd[1]: Starting Bluetooth service...
Aug 11 18:58:50 raspberrypi bluetoothd[852]: Bluetooth daemon 5.55
Aug 11 18:58:50 raspberrypi systemd[1]: Started Bluetooth service.
Aug 11 18:58:50 raspberrypi bluetoothd[852]: Starting SDP server
Aug 11 18:58:50 raspberrypi bluetoothd[852]: Excluding (cli) sap
Aug 11 18:58:50 raspberrypi bluetoothd[852]: Bluetooth management interface 1.21 initialized

GDB output:

pi@raspberrypi:~/qdomyos-zwift/src $ gdb --args ./qdomyos-zwift -qml
GNU gdb (Raspbian 10.1-1.7) 10.1.90.20210103-git
Copyright (C) 2021 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Type "show copying" and "show warranty" for details.
This GDB was configured as "arm-linux-gnueabihf".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<https://www.gnu.org/software/gdb/bugs/>.
Find the GDB manual and other documentation resources online at:
    <http://www.gnu.org/software/gdb/documentation/>.

For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from ./qdomyos-zwift...
(No debugging symbols found in ./qdomyos-zwift)
(gdb) run
Starting program: /home/pi/qdomyos-zwift/src/qdomyos-zwift -qml
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/arm-linux-gnueabihf/libthread_db.so.1".
qt.qpa.xcb: could not connect to display 
qt.qpa.plugin: Could not load the Qt platform plugin "xcb" in "" even though it was found.
This application failed to start because no Qt platform plugin could be initialized. Reinstalling the application may fix this problem.

Available platform plugins are: eglfs, linuxfb, minimal, minimalegl, offscreen, vnc, wayland-egl, wayland, wayland-xcomposite-egl, xcb.

Program received signal SIGABRT, Aborted.
__GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50
50  ../sysdeps/unix/sysv/linux/raise.c: No such file or directory.

Just running the service directly:

pi@raspberrypi:~/qdomyos-zwift/src $ sudo ./qdomyos-zwift 
qt.qpa.xcb: could not connect to display 
qt.qpa.plugin: Could not load the Qt platform plugin "xcb" in "" even though it was found.
This application failed to start because no Qt platform plugin could be initialized. Reinstalling the application may fix this problem.

Available platform plugins are: eglfs, linuxfb, minimal, minimalegl, offscreen, vnc, wayland-egl, wayland, wayland-xcomposite-egl, xcb.

Aborted
pi@raspberrypi:~/qdomyos-zwift/src $ sudo ./qdomyos-zwift -no-gui -heartrate-monitor
OK, you are root.
Segmentation fault

GDB for the above calls:

pi@raspberrypi:~/qdomyos-zwift/src $ gdb --args ./qdomyos-zwift -no-gui -heartrate-monitor
GNU gdb (Raspbian 10.1-1.7) 10.1.90.20210103-git
Copyright (C) 2021 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Type "show copying" and "show warranty" for details.
This GDB was configured as "arm-linux-gnueabihf".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<https://www.gnu.org/software/gdb/bugs/>.
Find the GDB manual and other documentation resources online at:
    <http://www.gnu.org/software/gdb/documentation/>.

For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from ./qdomyos-zwift...
(No debugging symbols found in ./qdomyos-zwift)
(gdb) run
Starting program: /home/pi/qdomyos-zwift/src/qdomyos-zwift -no-gui -heartrate-monitor
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/arm-linux-gnueabihf/libthread_db.so.1".
Runme as root!
[Inferior 1 (process 2660) exited with code 0377]
(gdb) q
pi@raspberrypi:~/qdomyos-zwift/src $ gdb --args sudo ./qdomyos-zwift -no-gui -heartrate-monitor
GNU gdb (Raspbian 10.1-1.7) 10.1.90.20210103-git
Copyright (C) 2021 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Type "show copying" and "show warranty" for details.
This GDB was configured as "arm-linux-gnueabihf".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<https://www.gnu.org/software/gdb/bugs/>.
Find the GDB manual and other documentation resources online at:
    <http://www.gnu.org/software/gdb/documentation/>.

For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from sudo...
(No debugging symbols found in sudo)
(gdb) run
Starting program: /usr/bin/sudo ./qdomyos-zwift -no-gui -heartrate-monitor
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/arm-linux-gnueabihf/libthread_db.so.1".
sudo: effective uid is not 0, is /usr/bin/sudo on a file system with the 'nosuid' option set or an NFS file system without root privileges?
[Inferior 1 (process 2673) exited with code 01]
(gdb) 

To Reproduce Followed the installation process for Raspberry Pi. Set up a service for starting the service immediately and noticed it was showing a SE

Expected behavior The service starts.

Screenshots If applicable, add screenshots to help explain your problem.

Desktop (please complete the following information):

• OS: raspberrypi OS
• Version Jellyfin

[cagnulein]

hi @janstadt type "bt" on gdb to get the stack trace thanks

[janstadt]

@cagnulein Here you go. This is just running the binary directly in gdb without any arguments:

pi@raspberrypi:~/qdomyos-zwift/src $ gdb --args ./qdomyos-zwift
GNU gdb (Raspbian 10.1-1.7) 10.1.90.20210103-git
Copyright (C) 2021 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Type "show copying" and "show warranty" for details.
This GDB was configured as "arm-linux-gnueabihf".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<https://www.gnu.org/software/gdb/bugs/>.
Find the GDB manual and other documentation resources online at:
    <http://www.gnu.org/software/gdb/documentation/>.

For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from ./qdomyos-zwift...
(No debugging symbols found in ./qdomyos-zwift)
(gdb) run
Starting program: /home/pi/qdomyos-zwift/src/qdomyos-zwift 
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/arm-linux-gnueabihf/libthread_db.so.1".
qt.qpa.xcb: could not connect to display 
qt.qpa.plugin: Could not load the Qt platform plugin "xcb" in "" even though it was found.
This application failed to start because no Qt platform plugin could be initialized. Reinstalling the application may fix this problem.

Available platform plugins are: eglfs, linuxfb, minimal, minimalegl, offscreen, vnc, wayland-egl, wayland, wayland-xcomposite-egl, xcb.

Program received signal SIGABRT, Aborted.
__GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50
50  ../sysdeps/unix/sysv/linux/raise.c: No such file or directory.
(gdb) bt
#0  __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50
#1  0xb4dd9804 in __GI_abort () at abort.c:79
#2  0xb51b710c in QMessageLogger::fatal(char const*, ...) const () from /lib/arm-linux-gnueabihf/libQt5Core.so.5
#3  0xb5f2229c in QGuiApplicationPrivate::createPlatformIntegration() () from /lib/arm-linux-gnueabihf/libQt5Gui.so.5
#4  0xb63c6000 in ?? () from /lib/arm-linux-gnueabihf/libQt5Gui.so.5
Backtrace stopped: previous frame identical to this frame (corrupt stack?)
(gdb) 

[cagnulein]

unfortunately there aren't any useful information there

the only way to understand something is to put a breakpoint into the first line of the main and go step by step

for sure it's a binary corruption or something similar anyway

[janstadt]

Is this one more helpful:

pi@raspberrypi:~/qdomyos-zwift/src $ sudo gdb --args ./qdomyos-zwift -no-gui -heart-service
GNU gdb (Raspbian 10.1-1.7) 10.1.90.20210103-git
Copyright (C) 2021 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Type "show copying" and "show warranty" for details.
This GDB was configured as "arm-linux-gnueabihf".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<https://www.gnu.org/software/gdb/bugs/>.
Find the GDB manual and other documentation resources online at:
    <http://www.gnu.org/software/gdb/documentation/>.

For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from ./qdomyos-zwift...
(No debugging symbols found in ./qdomyos-zwift)
(gdb) run
Starting program: /home/pi/qdomyos-zwift/src/qdomyos-zwift -no-gui -heart-service
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/arm-linux-gnueabihf/libthread_db.so.1".
OK, you are root.
[New Thread 0xb0985380 (LWP 2854)]
[New Thread 0xaffff380 (LWP 2855)]

Thread 3 "QQmlThread" received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0xaffff380 (LWP 2855)]
0xb6023944 in ?? () from /lib/arm-linux-gnueabihf/libQt5Gui.so.5
(gdb) bt
#0  0xb6023944 in ?? () from /lib/arm-linux-gnueabihf/libQt5Gui.so.5
#1  0xb602a1ec in QFontDatabase::findFont(QFontDef const&, int) () from /lib/arm-linux-gnueabihf/libQt5Gui.so.5
#2  0xb63c88d4 in QTextCursorPrivate::setBlockFormat(QTextBlockFormat const&, QTextDocumentPrivate::FormatChangeMode)@got.plt () from /lib/arm-linux-gnueabihf/libQt5Gui.so.5
Backtrace stopped: previous frame identical to this frame (corrupt stack?)
(gdb) 

[cagnulein]

did you try also the -no-gui switch?

[janstadt]

@cagnulein yeah i tried the -no-gui -heart-service as well which is right above your post. Wondering if thats showing more info that would be helpful. Right now im running make again as i kept having issues with my ssh client disconnecting from the pi after timing out or the screen going to sleep. I disabled that on my mac and was able to finish the build but now im trying to do it directly on the pi instead of via ssh to see if that A) goes faster B) doesnt fail.

[cagnulein]

check also the ram, maybe there isn't enough?

[janstadt]

Its got 512mb of ram.

[cagnulein]

should be enough if no other services are running i was using dietpi for this scope

Il giorno gio 11 ago 2022 alle 21:37 Jake Anstadt @.***> ha scritto:

Its got 512mb of ram.

— Reply to this email directly, view it on GitHub https://github.com/cagnulein/qdomyos-zwift/issues/894#issuecomment-1212410192, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAALYWCXW4BV6FJ43KBFGJ3VYVJA7ANCNFSM56JH3JQA . You are receiving this because you were mentioned.Message ID: @.***>

-- Roberto Viola Software engineer and open source enthusiast http://robertoviola.cloud

[janstadt]

Yeah this pi is going to be dedicated to just qdomyos-zwift so i dont believe any other services are running on it. Im unfamiliar with dietpi. Is that something i should try or should the raspberrypi-os lite be alright?

[janstadt]

Is it possible to run the make file with arguments that target specific treadmills/cycles instead of compiling all of the bikes? I would presume that would speed up the build process but im unsure how the app is written/organized.

[cagnulein]

no it's not possible:)

[janstadt]

I'll see how this build goes and if it fails i'll give dietpi a try.

[janstadt]

Dietpi was a no go. Rebuilt from scratch and i dont have any errors. Had to enable bluetooth scanning manually so that my phone could discover the pi. Is this normal or does QZ handle all the pairing? Since ill be running headless on a pi, does that mean i have to manually pair (with the code and all) the devices ill be using first? Also, once my phone is paired to the pi and i go to zwift, the bluetooth portion there doesnt seem to find the pi even though im paired. Ill look at the api a bit closer tomorrow but we have made some progress at least!

[cagnulein]

no pairing is required on bluetooth 4.0

maybe the bluetooth was just off on the pi?

[janstadt]

Do you mean "no manual pairing is required" or none whatsoever? I must be misunderstanding how this bridge works. Was under the impression that it is a bluetooth bridge between your fitness devices and zwift or other applications running on other devices to keep track of workouts and whatnot? Do i need an android/ios qdomyos-zwift app on a different device as well? I was thinking that the headless pi version was an alternative to running this whole setup without the application on the 'receiving' end of the bridge?

[cagnulein]

bluetooth 2.0 requires the paring process bluetooth 4.0 (qz bridge to zwift) doesn't yes you need two devices if you want to stream the bike metrics to zwift. one device for qz (raspberry, phone...) and one device for zwift otherwise you can use one device only with dircon setting that use tcp instead of bluetooth to stream metrics to zwift

[janstadt]

I have this: https://www.amazon.com/dp/B06XRLF8B5?psc=1&ref=ppx_yo2ov_dt_b_product_details which is bluetooth 4.0. I have an echelon bike and a sole F80 treadmill. I'd like to do bike|treadmill -> qz bridge running on pi -> zwift on either i fire stick or old fire tablet (specifically this one: https://www.gsmarena.com/amazon_fire_hd_10_(2017)-8872.php) which has bluetooth 4.1 according to the specs. Do i need to download the qz app on the fire tablet as well or just have zwift running on it? Also, will the headless qz app pair automatically to the bike/treadmill or do i need a UI and shell access to ssh and see the device to pair with?

[cagnulein]

I have this: https://www.amazon.com/dp/B06XRLF8B5?psc=1&ref=ppx_yo2ov_dt_b_product_details which is bluetooth 4.0.

yeah so no pairing is needed

I have an echelon bike and a sole F80 treadmill. I'd like to do bike|treadmill -> qz bridge running on pi -> zwift on either i fire stick or old fire tablet (specifically this one: https://www.gsmarena.com/amazon_fire_hd_10_(2017)-8872.php) which has bluetooth 4.1 according to the specs. Do i need to download the qz app on the fire tablet as well or just have zwift running on it?

nope, qz must be only on the raspberry

Also, will the headless qz app pair automatically to the bike/treadmill or do i need a UI and shell access to ssh and see the device to pair with?

if you the have 2 devices (bike and treadmill ) up at the same time, you need the UI to choose the device that you want to use. otherwise it will connect directly to the only device online.

[janstadt]

Thanks @cagnulein and apologize for all the questions. When you say 'online' do you mean just the power of the device is on or do they have to be connected to the internet somehow? I must be missing something here. I have the echelon sport bike which only has bluetooth and if i open the echelon app it pairs with my tablet. Is that required? How does the qz app on the pi automatically know when to connect to a device and how does zwift know to automatically pair with the qz bridge?

[janstadt]

For what its worth, i havent brought the pi down to my workout area to try and pair it with the other devices as i thought i would try and debug the connectivity between the tablet and the bridge first. Maybe when i bring it down there, everything will just automatically connect?

[cagnulein]

Thanks @cagnulein and apologize for all the questions.

no problem at all

When you say 'online' do you mean just the power of the device is on or do they have to be connected to the internet somehow?

just the power

I must be missing something here. I have the echelon sport bike which only has bluetooth and if i open the echelon app it pairs with my tablet. Is that required?

no. echelon app MUST BE turned off. your bike led must be blinking

How does the qz app on the pi automatically know when to connect to a device and how does zwift know to automatically pair with the qz bridge?

when it saws the advertising bluetooth packet from the bike

[cagnulein]

For what its worth, i havent brought the pi down to my workout area to try and pair it with the other devices as i thought i would try and debug the connectivity between the tablet and the bridge first. Maybe when i bring it down there, everything will just automatically connect?

yes absolutely, you can't test it without the fitness machines

[janstadt]

@cagnulein good news. I was able to pair qz with my treadmill (Sole F63) super fast. Unfortunately i havent been able to successfully pair with my bike (Echelon Sport). I will try and get some logs here but i feel like i remember seeing an issue on here where passing in the -name argument would potentially help things. Is there any preference for the name value or can i just do -name qz or something simple? Im naming the qz instance running on the pi right?

[cagnulein]

the -name option is about the echelon. So you need to put the bluetooth name of your echelon device there something like ECHEX-33444 @janstadt

[janstadt]

@cagnulein great thanks i'll test that out. Curious about the name argument with multiple devices. Will the -name property need to be empty if i want to pair it with my treadmill or is qz smart enough to differentiate between the two devices when one or the other is turned on and ready to pair?

[cagnulein]

the name argument is required only if you have multiple devices powered on and compatible with qz. with this argument you can specify which device you want to connect with qz otherwise is useless and qz will connect automatically to they only available device

Il giorno mer 17 ago 2022 alle 18:28 Jake Anstadt @.***> ha scritto:

@cagnulein https://github.com/cagnulein great thanks i'll test that out. Curious about the name argument with multiple devices. Will the -name property need to be empty if i want to pair it with my treadmill or is qz smart enough to differentiate between the two devices when one or the other is turned on and ready to pair?

— Reply to this email directly, view it on GitHub https://github.com/cagnulein/qdomyos-zwift/issues/894#issuecomment-1218244545, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAALYWAETA4MFBJ4X5HUJXTVZUHLFANCNFSM56JH3JQA . You are receiving this because you were mentioned.Message ID: @.***>

-- Roberto Viola Software engineer and open source enthusiast http://robertoviola.cloud

[janstadt]

qdomyos-zwift -no-gui -no-log -heart-service -name ECH-SPORT-030716 or qdomyos-zwift -no-gui -no-log -heart-service -name=ECH-SPORT-030716

I've tried both (reloaded the daemon and restarted the service) and it doesnt seem to find the bike. Also with this set, it doesnt seem to find my treadmill any longer either.

[janstadt]

Edit: My bad. The treadmill is still found after i press the Bluetooth button on the treadmill so thats still good to go.

[janstadt]

This worked i think: -name "ECH-SPORT-030716" I heard my bike beep meaning it paired with qz (i think) but now it doesnt show up in zwift.

[cagnulein]

i need a debug log to understand why. maybe you just need to clear the bluetooth cache of the zwift device also did you try nrfconnect on the zwift device?

Il giorno mer 17 ago 2022 alle 20:29 Jake Anstadt @.***> ha scritto:

This worked i think: -name "ECH-SPORT-030716" I heard my bike beep meaning it paired with qz (i think) but now it doesnt show up in zwift.

— Reply to this email directly, view it on GitHub https://github.com/cagnulein/qdomyos-zwift/issues/894#issuecomment-1218357849, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAALYWAAVE3TDZI4LUCROY3VZUVRBANCNFSM56JH3JQA . You are receiving this because you were mentioned.Message ID: @.***>

-- Roberto Viola Software engineer and open source enthusiast http://robertoviola.cloud

[janstadt]

I'll see if i can get the logs for you. Im using an Iphone 13 for zwift so there isnt a way to clear bluetooth cache. I might end up trying a different android device for swift. Also, do i just remove -no-log to generate logs? Is there a logs folder or where would i get the logs? Whats super weird is it seems like qz pairs instantaneously with the echelon sport bike (at least the bike thinks so) but then it doesnt show up on the zwift list as a power source.

[janstadt]

One other nugget. When i provide a -name argument, it somehow thinks that my treadmill is a cycle and shows it as a device i can connect to while on the riding tab vs the running tab in swift.

[janstadt]

Alright, im returning this bluetooth adapter and am going to test it out with the tp-link one you had recommended at one point to someone. bluetoothctl just kept cycling through devices and scanning constantly so i wonder if that was an issue? I also noticed that when it did pair to the echelon, when i was in the bluetootcl, the cmd prompt name (the left most portion of the cli in brackets) would be the echelon name. Is that expected?

[cagnulein]

I'll see if i can get the logs for you. Im using an Iphone 13 for zwift so there isnt a way to clear bluetooth cache.

you can do it resetting the network in the phone settings

I might end up trying a different android device for swift. Also, do i just remove -no-log to generate logs?

yes

Is there a logs folder or where would i get the logs?

in the qz binary folder

Whats super weird is it seems like qz pairs instantaneously with the echelon sport bike (at least the bike thinks so) but then it doesnt show up on the zwift list as a power source.

that's because of the bluetooth cache of the iphone for sure

[cagnulein]

One other nugget. When i provide a -name argument, it somehow thinks that my treadmill is a cycle and shows it as a device i can connect to while on the riding tab vs the running tab in swift.

that's because qz is showing a treadmill as a bike and a treadmill to zwift in order to enable the auto incline feature

[cagnulein]

Alright, im returning this bluetooth adapter and am going to test it out with the tp-link one you had recommended at one point to someone. bluetoothctl just kept cycling through devices and scanning constantly so i wonder if that was an issue?

no, i don't think so. i guess it's the standard behavior

I also noticed that when it did pair to the echelon, when i was in the bluetootcl, the cmd prompt name (the left most portion of the cli in brackets) would be the echelon name. Is that expected?

yes

[janstadt]

Got the tp-link dongle installed but still having issues. I also dont see any log files in the binary directory. Is there an argument i need to pass in for verbose logging or anything? Currently running this command /home/pi/qdomyos-zwift/src/qdomyos-zwift -no-gui -heart-service -miles without the -name argument and the echelon pairs immediately but the zwift app on my iphone doesnt show it in the devices even after resetting my network/bluetooth stuff.

[janstadt]

Could someone with a pi confirm the bluetoothctl settings they have for their devices? scan on/off? unpair/pair? the only way i can make my echelon disconnect is to stop the bluetooth service and restart it. Otherwise it keeps repairing even after i've removed the mac address and set the device to not be trusted. Unsure what the heck is going on. Might end up trying to rebuild yet again in hopes it helps things?

[cagnulein]

Got the tp-link dongle installed but still having issues. I also dont see any log files in the binary directory. Is there an argument i need to pass in for verbose logging or anything?

don't you see the log directly on the stdout? you can copy and paste in this case

Currently running this command /home/pi/qdomyos-zwift/src/qdomyos-zwift -no-gui -heart-service -miles without the -name argument and the echelon pairs immediately but the zwift app on my iphone doesnt show it in the devices even after resetting my network/bluetooth stuff.

did you try with nrfconnect @janstadt ?

[cagnulein]

Could someone with a pi confirm the bluetoothctl settings they have for their devices? scan on/off? unpair/pair? the only way i can make my echelon disconnect is to stop the bluetooth service and restart it. Otherwise it keeps repairing even after i've removed the mac address and set the device to not be trusted. Unsure what the heck is going on. Might end up trying to rebuild yet again in hopes it helps things?

it's not a build issue for sure. If you see the metrics on QZ the bluetooth stuff is ok, we should only try to understand with nrfconnect which is the issue on zwift. Let me know

[stale[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[cagnulein]

@janstadt any news?

[janstadt]

Seems to be working fine with just one workout device but pairing a second doesnt work and i still dont see any logs in the binary folder.

[cagnulein]

@janstadt the binary itself doesn't produce logs directly on stdout?

[stale[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[cagnulein]

bump

[janstadt]

Sorry @cagnulein i havent had a chance to look into this more closely. I'll close this for now but when i get a chance to i'll post here any additional info i can dig up. Thanks again for the help!

[cagnulein]

os lite should be alright but keep an eye also to dmesg to check if there is any ooem that means a memory issue

Il giorno gio 11 ago 2022 alle 21:43 Jake Anstadt @.***> ha scritto:

Yeah this pi is going to be dedicated to just qdomyos-zwift so i dont believe any other services are running on it. Im unfamiliar with dietpi. Is that something i should try or should the raspberrypi-os lite be alright?

— Reply to this email directly, view it on GitHub https://github.com/cagnulein/qdomyos-zwift/issues/894#issuecomment-1212415847, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAALYWFL6OCJDKT5DOVW5ETVYVJV7ANCNFSM56JH3JQA . You are receiving this because you were mentioned.Message ID: @.***>

-- Roberto Viola Software engineer and open source enthusiast http://robertoviola.cloud