Polar H10 Connection issues

[HuskerHeel]

Hello! Thank you for creating the Polar2LSL streamer. I followed your instructions for the install and it looks like both the GUI approach and command line approach connect to the Polar but it does not seem to be streaming data. I attached some screenshots here. When using the GUI, it recognizes the band, and after connecting it seems to broadcast to LSL as I'm able to see the stream on the network, but no data are getting recorded and the GUI continues to say Wait... Using the command line approach it seems to connect but then returns to prompt after displaying the battery level. I'm running on Windows 11, Python 3.11.5. Do you have any suggestions on troubleshooting this issue? Thank you.

[markspan]

Hi Anthony, I can only guess. I know that sometimes the polar connects after two starts. Can you try that? This behaviour is seen once in a while. M.

…

On Thu, 30 Nov 2023, 22:05 Anthony Ries, ***@***.***> wrote: Hello! Thank you for creating the Polar2LSL streamer. I followed your instructions for the install and it looks like both the GUI approach and command line approach connect to the Polar but it does not seem to be streaming data. I attached some screenshots here. When using the GUI, it recognizes the band, and after connecting it seems to broadcast to LSL as I'm able to see the stream on the network, but no data are getting recorded and the GUI continues to say Wait... Using the command line approach it seems to connect but then returns to prompt after displaying the battery level. I'm running on Windows 11, Python 3.11.5. Do you have any suggestions on troubleshooting this issue? Thank you. AnacondaPrompt.png (view on web) <https://github.com/markspan/PolarBand2lsl/assets/25234327/59cb2948-3339-4caa-9a48-2d06992ee3f7> LabRecorder.png (view on web) <https://github.com/markspan/PolarBand2lsl/assets/25234327/26ff0e5f-ff5a-43f1-b27f-a89061844c59> PolarGUI.png (view on web) <https://github.com/markspan/PolarBand2lsl/assets/25234327/7a5fb039-db7b-4d9f-a03a-b591ba001c3b> — Reply to this email directly, view it on GitHub <#4>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AA7KHGE4EP2OYCBKASDND7LYHDYJJAVCNFSM6AAAAABAB2N44GVHI2DSMVQWIX3LMV43ASLTON2WKOZSGAYTSNJQHAYDGMI> . You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>

[HuskerHeel]

Thank you for your reply. I'll give it a try.

…

On Thu, Nov 30, 2023, 14:15 Mark M. Span ***@***.***> wrote: Hi Anthony, I can only guess. I know that sometimes the polar connects after two starts. Can you try that? This behaviour is seen once in a while. M. On Thu, 30 Nov 2023, 22:05 Anthony Ries, ***@***.***> wrote: > Hello! Thank you for creating the Polar2LSL streamer. I followed your > instructions for the install and it looks like both the GUI approach and > command line approach connect to the Polar but it does not seem to be > streaming data. I attached some screenshots here. When using the GUI, it > recognizes the band, and after connecting it seems to broadcast to LSL as > I'm able to see the stream on the network, but no data are getting recorded > and the GUI continues to say Wait... Using the command line approach it > seems to connect but then returns to prompt after displaying the battery > level. I'm running on Windows 11, Python 3.11.5. Do you have any > suggestions on troubleshooting this issue? Thank you. > AnacondaPrompt.png (view on web) > < https://github.com/markspan/PolarBand2lsl/assets/25234327/59cb2948-3339-4caa-9a48-2d06992ee3f7> > LabRecorder.png (view on web) > < https://github.com/markspan/PolarBand2lsl/assets/25234327/26ff0e5f-ff5a-43f1-b27f-a89061844c59> > PolarGUI.png (view on web) > < https://github.com/markspan/PolarBand2lsl/assets/25234327/7a5fb039-db7b-4d9f-a03a-b591ba001c3b> > > — > Reply to this email directly, view it on GitHub > <#4>, or unsubscribe > < https://github.com/notifications/unsubscribe-auth/AA7KHGE4EP2OYCBKASDND7LYHDYJJAVCNFSM6AAAAABAB2N44GVHI2DSMVQWIX3LMV43ASLTON2WKOZSGAYTSNJQHAYDGMI> > . > You are receiving this because you are subscribed to this thread.Message > ID: ***@***.***> > — Reply to this email directly, view it on GitHub <#4 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AGAQXF7E3FPQUH7CGAR35DDYHDZPPAVCNFSM6AAAAABAB2N44GVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQMZUGU3TCMRUGM> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[HuskerHeel]

Hi Mark, I'm getting the same issues on two different machines and virtual environments, Windows 10 and 11. What versions of python, bleak, pylsl, aioconsole, async-timeout do you use? Should I be using Polar2LSL.py or Polar2LSL2.py?

…

On Thu, Nov 30, 2023 at 2:54 PM Anthony Ries ***@***.***> wrote: Thank you for your reply. I'll give it a try. On Thu, Nov 30, 2023, 14:15 Mark M. Span ***@***.***> wrote: > Hi Anthony, > > I can only guess. I know that sometimes the polar connects after two > starts. Can you try that? This behaviour is seen once in a while. > > M. > > On Thu, 30 Nov 2023, 22:05 Anthony Ries, ***@***.***> wrote: > > > Hello! Thank you for creating the Polar2LSL streamer. I followed your > > instructions for the install and it looks like both the GUI approach > and > > command line approach connect to the Polar but it does not seem to be > > streaming data. I attached some screenshots here. When using the GUI, > it > > recognizes the band, and after connecting it seems to broadcast to LSL > as > > I'm able to see the stream on the network, but no data are getting > recorded > > and the GUI continues to say Wait... Using the command line approach it > > seems to connect but then returns to prompt after displaying the > battery > > level. I'm running on Windows 11, Python 3.11.5. Do you have any > > suggestions on troubleshooting this issue? Thank you. > > AnacondaPrompt.png (view on web) > > < > https://github.com/markspan/PolarBand2lsl/assets/25234327/59cb2948-3339-4caa-9a48-2d06992ee3f7> > > > LabRecorder.png (view on web) > > < > https://github.com/markspan/PolarBand2lsl/assets/25234327/26ff0e5f-ff5a-43f1-b27f-a89061844c59> > > > PolarGUI.png (view on web) > > < > https://github.com/markspan/PolarBand2lsl/assets/25234327/7a5fb039-db7b-4d9f-a03a-b591ba001c3b> > > > > > — > > Reply to this email directly, view it on GitHub > > <#4>, or unsubscribe > > < > https://github.com/notifications/unsubscribe-auth/AA7KHGE4EP2OYCBKASDND7LYHDYJJAVCNFSM6AAAAABAB2N44GVHI2DSMVQWIX3LMV43ASLTON2WKOZSGAYTSNJQHAYDGMI> > > > . > > You are receiving this because you are subscribed to this > thread.Message > > ID: ***@***.***> > > > > — > Reply to this email directly, view it on GitHub > <#4 (comment)>, > or unsubscribe > <https://github.com/notifications/unsubscribe-auth/AGAQXF7E3FPQUH7CGAR35DDYHDZPPAVCNFSM6AAAAABAB2N44GVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQMZUGU3TCMRUGM> > . > You are receiving this because you authored the thread.Message ID: > ***@***.***> >

[markspan]

What BLE dongle do you use?

…

On Fri, 1 Dec 2023, 02:39 Anthony Ries, ***@***.***> wrote: Hi Mark, I'm getting the same issues on two different machines and virtual environments, Windows 10 and 11. What versions of python, bleak, pylsl, aioconsole, async-timeout do you use? Should I be using Polar2LSL.py or Polar2LSL2.py? On Thu, Nov 30, 2023 at 2:54 PM Anthony Ries ***@***.***> wrote: > Thank you for your reply. I'll give it a try. > > On Thu, Nov 30, 2023, 14:15 Mark M. Span ***@***.***> wrote: > >> Hi Anthony, >> >> I can only guess. I know that sometimes the polar connects after two >> starts. Can you try that? This behaviour is seen once in a while. >> >> M. >> >> On Thu, 30 Nov 2023, 22:05 Anthony Ries, ***@***.***> wrote: >> >> > Hello! Thank you for creating the Polar2LSL streamer. I followed your >> > instructions for the install and it looks like both the GUI approach >> and >> > command line approach connect to the Polar but it does not seem to be >> > streaming data. I attached some screenshots here. When using the GUI, >> it >> > recognizes the band, and after connecting it seems to broadcast to LSL >> as >> > I'm able to see the stream on the network, but no data are getting >> recorded >> > and the GUI continues to say Wait... Using the command line approach it >> > seems to connect but then returns to prompt after displaying the >> battery >> > level. I'm running on Windows 11, Python 3.11.5. Do you have any >> > suggestions on troubleshooting this issue? Thank you. >> > AnacondaPrompt.png (view on web) >> > < >> https://github.com/markspan/PolarBand2lsl/assets/25234327/59cb2948-3339-4caa-9a48-2d06992ee3f7> >> >> > LabRecorder.png (view on web) >> > < >> https://github.com/markspan/PolarBand2lsl/assets/25234327/26ff0e5f-ff5a-43f1-b27f-a89061844c59> >> >> > PolarGUI.png (view on web) >> > < >> https://github.com/markspan/PolarBand2lsl/assets/25234327/7a5fb039-db7b-4d9f-a03a-b591ba001c3b> >> >> > >> > — >> > Reply to this email directly, view it on GitHub >> > <#4>, or unsubscribe >> > < >> https://github.com/notifications/unsubscribe-auth/AA7KHGE4EP2OYCBKASDND7LYHDYJJAVCNFSM6AAAAABAB2N44GVHI2DSMVQWIX3LMV43ASLTON2WKOZSGAYTSNJQHAYDGMI> >> >> > . >> > You are receiving this because you are subscribed to this >> thread.Message >> > ID: ***@***.***> >> > >> >> — >> Reply to this email directly, view it on GitHub >> < #4 (comment)>, >> or unsubscribe >> < https://github.com/notifications/unsubscribe-auth/AGAQXF7E3FPQUH7CGAR35DDYHDZPPAVCNFSM6AAAAABAB2N44GVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQMZUGU3TCMRUGM> >> . >> You are receiving this because you authored the thread.Message ID: >> ***@***.***> >> > — Reply to this email directly, view it on GitHub <#4 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AA7KHGASYUDURU4QGIJ2JYLYHEYNFAVCNFSM6AAAAABAB2N44GVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQMZVGI3DSMRQGI> . You are receiving this because you commented.Message ID: ***@***.***>

[markspan]

We are using the programs in our labs, on many different devices. I usually install the latest version of anaconda, but for the GUI executable, I install nothing....

…

On Fri, 1 Dec 2023, 02:39 Anthony Ries, ***@***.***> wrote: Hi Mark, I'm getting the same issues on two different machines and virtual environments, Windows 10 and 11. What versions of python, bleak, pylsl, aioconsole, async-timeout do you use? Should I be using Polar2LSL.py or Polar2LSL2.py? On Thu, Nov 30, 2023 at 2:54 PM Anthony Ries ***@***.***> wrote: > Thank you for your reply. I'll give it a try. > > On Thu, Nov 30, 2023, 14:15 Mark M. Span ***@***.***> wrote: > >> Hi Anthony, >> >> I can only guess. I know that sometimes the polar connects after two >> starts. Can you try that? This behaviour is seen once in a while. >> >> M. >> >> On Thu, 30 Nov 2023, 22:05 Anthony Ries, ***@***.***> wrote: >> >> > Hello! Thank you for creating the Polar2LSL streamer. I followed your >> > instructions for the install and it looks like both the GUI approach >> and >> > command line approach connect to the Polar but it does not seem to be >> > streaming data. I attached some screenshots here. When using the GUI, >> it >> > recognizes the band, and after connecting it seems to broadcast to LSL >> as >> > I'm able to see the stream on the network, but no data are getting >> recorded >> > and the GUI continues to say Wait... Using the command line approach it >> > seems to connect but then returns to prompt after displaying the >> battery >> > level. I'm running on Windows 11, Python 3.11.5. Do you have any >> > suggestions on troubleshooting this issue? Thank you. >> > AnacondaPrompt.png (view on web) >> > < >> https://github.com/markspan/PolarBand2lsl/assets/25234327/59cb2948-3339-4caa-9a48-2d06992ee3f7> >> >> > LabRecorder.png (view on web) >> > < >> https://github.com/markspan/PolarBand2lsl/assets/25234327/26ff0e5f-ff5a-43f1-b27f-a89061844c59> >> >> > PolarGUI.png (view on web) >> > < >> https://github.com/markspan/PolarBand2lsl/assets/25234327/7a5fb039-db7b-4d9f-a03a-b591ba001c3b> >> >> > >> > — >> > Reply to this email directly, view it on GitHub >> > <#4>, or unsubscribe >> > < >> https://github.com/notifications/unsubscribe-auth/AA7KHGE4EP2OYCBKASDND7LYHDYJJAVCNFSM6AAAAABAB2N44GVHI2DSMVQWIX3LMV43ASLTON2WKOZSGAYTSNJQHAYDGMI> >> >> > . >> > You are receiving this because you are subscribed to this >> thread.Message >> > ID: ***@***.***> >> > >> >> — >> Reply to this email directly, view it on GitHub >> < #4 (comment)>, >> or unsubscribe >> < https://github.com/notifications/unsubscribe-auth/AGAQXF7E3FPQUH7CGAR35DDYHDZPPAVCNFSM6AAAAABAB2N44GVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQMZUGU3TCMRUGM> >> . >> You are receiving this because you authored the thread.Message ID: >> ***@***.***> >> > — Reply to this email directly, view it on GitHub <#4 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AA7KHGASYUDURU4QGIJ2JYLYHEYNFAVCNFSM6AAAAABAB2N44GVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQMZVGI3DSMRQGI> . You are receiving this because you commented.Message ID: ***@***.***>

[HuskerHeel]

Hi Mark, Thank you again for your speedy response. I'm guessing the BLE dongle is my problem as I didn't realize I needed one lol :-) Best, Anthony On Fri, Dec 1, 2023 at 2:55 AM Mark M. Span ***@***.***> wrote:

…

We are using the programs in our labs, on many different devices. I usually install the latest version of anaconda, but for the GUI executable, I install nothing.... On Fri, 1 Dec 2023, 02:39 Anthony Ries, ***@***.***> wrote: > Hi Mark, > > I'm getting the same issues on two different machines and virtual > environments, Windows 10 and 11. What versions of python, bleak, pylsl, > aioconsole, async-timeout do you use? > > Should I be using Polar2LSL.py or Polar2LSL2.py? > > On Thu, Nov 30, 2023 at 2:54 PM Anthony Ries ***@***.***> wrote: > > > Thank you for your reply. I'll give it a try. > > > > On Thu, Nov 30, 2023, 14:15 Mark M. Span ***@***.***> wrote: > > > >> Hi Anthony, > >> > >> I can only guess. I know that sometimes the polar connects after two > >> starts. Can you try that? This behaviour is seen once in a while. > >> > >> M. > >> > >> On Thu, 30 Nov 2023, 22:05 Anthony Ries, ***@***.***> wrote: > >> > >> > Hello! Thank you for creating the Polar2LSL streamer. I followed your > >> > instructions for the install and it looks like both the GUI approach > >> and > >> > command line approach connect to the Polar but it does not seem to be > >> > streaming data. I attached some screenshots here. When using the GUI, > >> it > >> > recognizes the band, and after connecting it seems to broadcast to > LSL > >> as > >> > I'm able to see the stream on the network, but no data are getting > >> recorded > >> > and the GUI continues to say Wait... Using the command line approach > it > >> > seems to connect but then returns to prompt after displaying the > >> battery > >> > level. I'm running on Windows 11, Python 3.11.5. Do you have any > >> > suggestions on troubleshooting this issue? Thank you. > >> > AnacondaPrompt.png (view on web) > >> > < > >> > https://github.com/markspan/PolarBand2lsl/assets/25234327/59cb2948-3339-4caa-9a48-2d06992ee3f7> > > >> > >> > LabRecorder.png (view on web) > >> > < > >> > https://github.com/markspan/PolarBand2lsl/assets/25234327/26ff0e5f-ff5a-43f1-b27f-a89061844c59> > > >> > >> > PolarGUI.png (view on web) > >> > < > >> > https://github.com/markspan/PolarBand2lsl/assets/25234327/7a5fb039-db7b-4d9f-a03a-b591ba001c3b> > > >> > >> > > >> > — > >> > Reply to this email directly, view it on GitHub > >> > <#4>, or unsubscribe > >> > < > >> > https://github.com/notifications/unsubscribe-auth/AA7KHGE4EP2OYCBKASDND7LYHDYJJAVCNFSM6AAAAABAB2N44GVHI2DSMVQWIX3LMV43ASLTON2WKOZSGAYTSNJQHAYDGMI> > > >> > >> > . > >> > You are receiving this because you are subscribed to this > >> thread.Message > >> > ID: ***@***.***> > >> > > >> > >> — > >> Reply to this email directly, view it on GitHub > >> < > #4 (comment)>, > > >> or unsubscribe > >> < > https://github.com/notifications/unsubscribe-auth/AGAQXF7E3FPQUH7CGAR35DDYHDZPPAVCNFSM6AAAAABAB2N44GVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQMZUGU3TCMRUGM> > > >> . > >> You are receiving this because you authored the thread.Message ID: > >> ***@***.***> > >> > > > > — > Reply to this email directly, view it on GitHub > < #4 (comment)>, > or unsubscribe > < https://github.com/notifications/unsubscribe-auth/AA7KHGASYUDURU4QGIJ2JYLYHEYNFAVCNFSM6AAAAABAB2N44GVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQMZVGI3DSMRQGI> > . > You are receiving this because you commented.Message ID: > ***@***.***> > — Reply to this email directly, view it on GitHub <#4 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AGAQXF5JB4YWLMVR7K4DGR3YHGSPVAVCNFSM6AAAAABAB2N44GVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQMZVG44TOMJQGM> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[HuskerHeel]

Which one do you use?

…

On Fri, Dec 1, 2023, 06:46 Anthony Ries ***@***.***> wrote: Hi Mark, Thank you again for your speedy response. I'm guessing the BLE dongle is my problem as I didn't realize I needed one lol :-) Best, Anthony On Fri, Dec 1, 2023 at 2:55 AM Mark M. Span ***@***.***> wrote: > We are using the programs in our labs, on many different devices. I > usually > install the latest version of anaconda, but for the GUI executable, I > install nothing.... > > On Fri, 1 Dec 2023, 02:39 Anthony Ries, ***@***.***> wrote: > > > Hi Mark, > > > > I'm getting the same issues on two different machines and virtual > > environments, Windows 10 and 11. What versions of python, bleak, pylsl, > > aioconsole, async-timeout do you use? > > > > Should I be using Polar2LSL.py or Polar2LSL2.py? > > > > On Thu, Nov 30, 2023 at 2:54 PM Anthony Ries ***@***.***> wrote: > > > > > Thank you for your reply. I'll give it a try. > > > > > > On Thu, Nov 30, 2023, 14:15 Mark M. Span ***@***.***> wrote: > > > > > >> Hi Anthony, > > >> > > >> I can only guess. I know that sometimes the polar connects after two > > >> starts. Can you try that? This behaviour is seen once in a while. > > >> > > >> M. > > >> > > >> On Thu, 30 Nov 2023, 22:05 Anthony Ries, ***@***.***> wrote: > > >> > > >> > Hello! Thank you for creating the Polar2LSL streamer. I followed > your > > >> > instructions for the install and it looks like both the GUI > approach > > >> and > > >> > command line approach connect to the Polar but it does not seem to > be > > >> > streaming data. I attached some screenshots here. When using the > GUI, > > >> it > > >> > recognizes the band, and after connecting it seems to broadcast to > > LSL > > >> as > > >> > I'm able to see the stream on the network, but no data are getting > > >> recorded > > >> > and the GUI continues to say Wait... Using the command line > approach > > it > > >> > seems to connect but then returns to prompt after displaying the > > >> battery > > >> > level. I'm running on Windows 11, Python 3.11.5. Do you have any > > >> > suggestions on troubleshooting this issue? Thank you. > > >> > AnacondaPrompt.png (view on web) > > >> > < > > >> > > > https://github.com/markspan/PolarBand2lsl/assets/25234327/59cb2948-3339-4caa-9a48-2d06992ee3f7> > > > > > >> > > >> > LabRecorder.png (view on web) > > >> > < > > >> > > > https://github.com/markspan/PolarBand2lsl/assets/25234327/26ff0e5f-ff5a-43f1-b27f-a89061844c59> > > > > > >> > > >> > PolarGUI.png (view on web) > > >> > < > > >> > > > https://github.com/markspan/PolarBand2lsl/assets/25234327/7a5fb039-db7b-4d9f-a03a-b591ba001c3b> > > > > > >> > > >> > > > >> > — > > >> > Reply to this email directly, view it on GitHub > > >> > <#4>, or > unsubscribe > > >> > < > > >> > > > https://github.com/notifications/unsubscribe-auth/AA7KHGE4EP2OYCBKASDND7LYHDYJJAVCNFSM6AAAAABAB2N44GVHI2DSMVQWIX3LMV43ASLTON2WKOZSGAYTSNJQHAYDGMI> > > > > > >> > > >> > . > > >> > You are receiving this because you are subscribed to this > > >> thread.Message > > >> > ID: ***@***.***> > > >> > > > >> > > >> — > > >> Reply to this email directly, view it on GitHub > > >> < > > > #4 (comment)>, > > > > > >> or unsubscribe > > >> < > > > https://github.com/notifications/unsubscribe-auth/AGAQXF7E3FPQUH7CGAR35DDYHDZPPAVCNFSM6AAAAABAB2N44GVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQMZUGU3TCMRUGM> > > > > > >> . > > >> You are receiving this because you authored the thread.Message ID: > > >> ***@***.***> > > >> > > > > > > > — > > Reply to this email directly, view it on GitHub > > < > #4 (comment)>, > > > or unsubscribe > > < > https://github.com/notifications/unsubscribe-auth/AA7KHGASYUDURU4QGIJ2JYLYHEYNFAVCNFSM6AAAAABAB2N44GVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQMZVGI3DSMRQGI> > > > . > > You are receiving this because you commented.Message ID: > > ***@***.***> > > > > — > Reply to this email directly, view it on GitHub > <#4 (comment)>, > or unsubscribe > <https://github.com/notifications/unsubscribe-auth/AGAQXF5JB4YWLMVR7K4DGR3YHGSPVAVCNFSM6AAAAABAB2N44GVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQMZVG44TOMJQGM> > . > You are receiving this because you authored the thread.Message ID: > ***@***.***> >

[markspan]

Any that is compatible with bleak. Which are most I guess. It needs to support GATT.

[HuskerHeel]

Sounds good, thank you!

…

On Fri, Dec 1, 2023, 07:26 Mark M. Span ***@***.***> wrote: Any that is compatible with bleak. Which are most I guess. It needs to support GATT. — Reply to this email directly, view it on GitHub <#4 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AGAQXF4RI6EWF3H6W6EKH63YHHSJRAVCNFSM6AAAAABAB2N44GVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQMZWGIYDKNZZGI> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[HuskerHeel]

Hi Mark, I picked up a couple of BLE dongles and tried both command line and exe options getting the same behavior as before. I added some print and wait statements to try to diagnose the problem. I also added logging to bleak which all resulted in the following output below. It seems like its disconnecting after it tries to run: await client.read_gatt_char(PMD_CONTROL) Is there a way for me to confirm if the PMD_CONTROL is correct? Please let me know if you have any suggestions. Thank you. (base) C:\Software\PolarBand2lsl-main>python Polar2LSL.py MACADDRESS is e0:a6:f1:f6:fa:dd STREAMNAME is PolarBand 2023-12-03 21:22:38.592 ( 0.062s) [ 7B8C67D0] loguru.cpp:828 INFO| Logging to 'test.out', mode: 'a', verbosity: -3 2023-12-03 21:22:38,959 bleak.backends.winrt.scanner MainThread DEBUG: Received 29:0E:C0:62:AF:E5: . 2023-12-03 21:22:39,067 bleak.backends.winrt.scanner MainThread DEBUG: Received 29:0E:C0:62:AF:E5: . 2023-12-03 21:22:39,083 bleak.backends.winrt.scanner MainThread DEBUG: Received 75:C8:48:F6:A9:39: . 2023-12-03 21:22:39,193 bleak.backends.winrt.scanner MainThread DEBUG: Received 75:C8:48:F6:A9:39: . 2023-12-03 21:22:39,300 bleak.backends.winrt.scanner MainThread DEBUG: Received 75:C8:48:F6:A9:39: . 2023-12-03 21:22:39,926 bleak.backends.winrt.scanner MainThread DEBUG: Received 75:C8:48:F6:A9:39: . 2023-12-03 21:22:40,010 bleak.backends.winrt.scanner MainThread DEBUG: Received 29:0E:C0:62:AF:E5: . 2023-12-03 21:22:40,249 bleak.backends.winrt.scanner MainThread DEBUG: Received 75:C8:48:F6:A9:39: . 2023-12-03 21:22:40,959 bleak.backends.winrt.scanner MainThread DEBUG: Received 29:0E:C0:62:AF:E5: . 2023-12-03 21:22:41,193 bleak.backends.winrt.scanner MainThread DEBUG: Received 75:C8:48:F6:A9:39: . 2023-12-03 21:22:41,303 bleak.backends.winrt.scanner MainThread DEBUG: Received 75:C8:48:F6:A9:39: . 2023-12-03 21:22:41,538 bleak.backends.winrt.scanner MainThread DEBUG: Received E0:A6:F1:F6:FA:DD: . 2023-12-03 21:22:41,541 bleak.backends.winrt.scanner MainThread DEBUG: 3 devices found. Watcher status: <BluetoothLEAdvertisementWatcherStatus.STOPPED: 3>. 2023-12-03 21:22:41,542 bleak.backends.winrt.client MainThread DEBUG: Connecting to BLE device @ e0:a6:f1:f6:fa:dd 2023-12-03 21:22:41,564 bleak.backends.winrt.client MainThread DEBUG: getting services (service_cache_mode=None, cache_mode=None)... 2023-12-03 21:22:42,044 bleak.backends.winrt.client Dummy-1 DEBUG: session_status_changed_event_handler: id: BluetoothLE#BluetoothLE5c:f3:70:a6:4f:49-e0:a6:f1:f6:fa:dd, error: <BluetoothError.SUCCESS: 0>, status: <GattSessionStatus.ACTIVE: 1> 2023-12-03 21:22:42,174 bleak.backends.winrt.client Dummy-1 DEBUG: max_pdu_size_changed_handler: 132 2023-12-03 21:22:42,424 bleak.backends.winrt.client Dummy-2 DEBUG: e0:a6:f1:f6:fa:dd: services changed 2023-12-03 21:22:43,859 bleak.backends.winrt.client Dummy-3 DEBUG: e0:a6:f1:f6:fa:dd: services changed ---------Looking for Device------------ C:\Software\PolarBand2lsl-main\Polar2LSL.py:102: FutureWarning: is_connected has been changed to a property. Calling it as an async method will be removed in a future version await client.is_connected() ---------Device connected-------------- 2023-12-03 21:22:44,928 bleak.backends.winrt.client MainThread DEBUG: Read Characteristic 002D : bytearray(b'H10\x00') Model Number: H10 2023-12-03 21:22:44,966 bleak.backends.winrt.client MainThread DEBUG: Read Characteristic 002B : bytearray(b'Polar Electro Oy\x00') Manufacturer Name: Polar Electro Oy 2023-12-03 21:22:45,002 bleak.backends.winrt.client MainThread DEBUG: Read Characteristic 0040 : bytearray(b'F') Battery Level: 70% Getting ready to collect GATT data... 2023-12-03 21:23:00,005 bleak.backends.winrt.client MainThread DEBUG: Disconnecting from BLE device... 2023-12-03 21:23:03,237 bleak.backends.winrt.client Dummy-2 DEBUG: max_pdu_size_changed_handler: 23 2023-12-03 21:23:03,237 bleak.backends.winrt.client Dummy-4 DEBUG: session_status_changed_event_handler: id: BluetoothLE#BluetoothLE5c:f3:70:a6:4f:49-e0:a6:f1:f6:fa:dd, error: <BluetoothError.SUCCESS: 0>, status: <GattSessionStatus.CLOSED: 0> 2023-12-03 21:23:03,238 bleak.backends.winrt.client MainThread DEBUG: closing requester 2023-12-03 21:23:03,238 bleak.backends.winrt.client MainThread DEBUG: closing session

…

On Fri, Dec 1, 2023 at 8:31 AM Anthony Ries ***@***.***> wrote: Sounds good, thank you! On Fri, Dec 1, 2023, 07:26 Mark M. Span ***@***.***> wrote: > Any that is compatible with bleak. Which are most I guess. It needs to > support GATT. > > — > Reply to this email directly, view it on GitHub > <#4 (comment)>, > or unsubscribe > <https://github.com/notifications/unsubscribe-auth/AGAQXF4RI6EWF3H6W6EKH63YHHSJRAVCNFSM6AAAAABAB2N44GVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQMZWGIYDKNZZGI> > . > You are receiving this because you authored the thread.Message ID: > ***@***.***> >

[HuskerHeel]

Hi Mark, Just wanted to update you on a couple things I have tried. In Polar2LSL2.py my device would not connect; however it would in Polar2LSL.py. In Polar2LSL2.py line 61, I changed client.connect() to client.is_connected() and it seemed to work better. However it looks like it may not be reading the PMD_CONTROL correctly as I get the error:

…

---------Looking for Device------------ ---------Device connected-------------- Model Number: H10 Manufacturer Name: Polar Electro Oy Battery Level: 100% Error: Characteristic FB005C81-02E7-F387-1CAD-8ACD2D8DF0C8 was not found! Process finished with exit code 1

On Sun, Dec 3, 2023 at 9:34 PM Anthony Ries ***@***.***> wrote: Hi Mark, I picked up a couple of BLE dongles and tried both command line and exe options getting the same behavior as before. I added some print and wait statements to try to diagnose the problem. I also added logging to bleak which all resulted in the following output below. It seems like its disconnecting after it tries to run: await client.read_gatt_char(PMD_CONTROL) Is there a way for me to confirm if the PMD_CONTROL is correct? Please let me know if you have any suggestions. Thank you. (base) C:\Software\PolarBand2lsl-main>python Polar2LSL.py MACADDRESS is e0:a6:f1:f6:fa:dd STREAMNAME is PolarBand 2023-12-03 21:22:38.592 ( 0.062s) [ 7B8C67D0] loguru.cpp:828 INFO| Logging to 'test.out', mode: 'a', verbosity: -3 2023-12-03 21:22:38,959 bleak.backends.winrt.scanner MainThread DEBUG: Received 29:0E:C0:62:AF:E5: . 2023-12-03 21:22:39,067 bleak.backends.winrt.scanner MainThread DEBUG: Received 29:0E:C0:62:AF:E5: . 2023-12-03 21:22:39,083 bleak.backends.winrt.scanner MainThread DEBUG: Received 75:C8:48:F6:A9:39: . 2023-12-03 21:22:39,193 bleak.backends.winrt.scanner MainThread DEBUG: Received 75:C8:48:F6:A9:39: . 2023-12-03 21:22:39,300 bleak.backends.winrt.scanner MainThread DEBUG: Received 75:C8:48:F6:A9:39: . 2023-12-03 21:22:39,926 bleak.backends.winrt.scanner MainThread DEBUG: Received 75:C8:48:F6:A9:39: . 2023-12-03 21:22:40,010 bleak.backends.winrt.scanner MainThread DEBUG: Received 29:0E:C0:62:AF:E5: . 2023-12-03 21:22:40,249 bleak.backends.winrt.scanner MainThread DEBUG: Received 75:C8:48:F6:A9:39: . 2023-12-03 21:22:40,959 bleak.backends.winrt.scanner MainThread DEBUG: Received 29:0E:C0:62:AF:E5: . 2023-12-03 21:22:41,193 bleak.backends.winrt.scanner MainThread DEBUG: Received 75:C8:48:F6:A9:39: . 2023-12-03 21:22:41,303 bleak.backends.winrt.scanner MainThread DEBUG: Received 75:C8:48:F6:A9:39: . 2023-12-03 21:22:41,538 bleak.backends.winrt.scanner MainThread DEBUG: Received E0:A6:F1:F6:FA:DD: . 2023-12-03 21:22:41,541 bleak.backends.winrt.scanner MainThread DEBUG: 3 devices found. Watcher status: <BluetoothLEAdvertisementWatcherStatus.STOPPED: 3>. 2023-12-03 21:22:41,542 bleak.backends.winrt.client MainThread DEBUG: Connecting to BLE device @ e0:a6:f1:f6:fa:dd 2023-12-03 21:22:41,564 bleak.backends.winrt.client MainThread DEBUG: getting services (service_cache_mode=None, cache_mode=None)... 2023-12-03 21:22:42,044 bleak.backends.winrt.client Dummy-1 DEBUG: session_status_changed_event_handler: id: BluetoothLE#BluetoothLE5c:f3:70:a6:4f:49-e0:a6:f1:f6:fa:dd, error: <BluetoothError.SUCCESS: 0>, status: <GattSessionStatus.ACTIVE: 1> 2023-12-03 21:22:42,174 bleak.backends.winrt.client Dummy-1 DEBUG: max_pdu_size_changed_handler: 132 2023-12-03 21:22:42,424 bleak.backends.winrt.client Dummy-2 DEBUG: e0:a6:f1:f6:fa:dd: services changed 2023-12-03 21:22:43,859 bleak.backends.winrt.client Dummy-3 DEBUG: e0:a6:f1:f6:fa:dd: services changed ---------Looking for Device------------ C:\Software\PolarBand2lsl-main\Polar2LSL.py:102: FutureWarning: is_connected has been changed to a property. Calling it as an async method will be removed in a future version await client.is_connected() ---------Device connected-------------- 2023-12-03 21:22:44,928 bleak.backends.winrt.client MainThread DEBUG: Read Characteristic 002D : bytearray(b'H10\x00') Model Number: H10 2023-12-03 21:22:44,966 bleak.backends.winrt.client MainThread DEBUG: Read Characteristic 002B : bytearray(b'Polar Electro Oy\x00') Manufacturer Name: Polar Electro Oy 2023-12-03 21:22:45,002 bleak.backends.winrt.client MainThread DEBUG: Read Characteristic 0040 : bytearray(b'F') Battery Level: 70% Getting ready to collect GATT data... 2023-12-03 21:23:00,005 bleak.backends.winrt.client MainThread DEBUG: Disconnecting from BLE device... 2023-12-03 21:23:03,237 bleak.backends.winrt.client Dummy-2 DEBUG: max_pdu_size_changed_handler: 23 2023-12-03 21:23:03,237 bleak.backends.winrt.client Dummy-4 DEBUG: session_status_changed_event_handler: id: BluetoothLE#BluetoothLE5c:f3:70:a6:4f:49-e0:a6:f1:f6:fa:dd, error: <BluetoothError.SUCCESS: 0>, status: <GattSessionStatus.CLOSED: 0> 2023-12-03 21:23:03,238 bleak.backends.winrt.client MainThread DEBUG: closing requester 2023-12-03 21:23:03,238 bleak.backends.winrt.client MainThread DEBUG: closing session On Fri, Dec 1, 2023 at 8:31 AM Anthony Ries ***@***.***> wrote: > Sounds good, thank you! > > On Fri, Dec 1, 2023, 07:26 Mark M. Span ***@***.***> wrote: > >> Any that is compatible with bleak. Which are most I guess. It needs to >> support GATT. >> >> — >> Reply to this email directly, view it on GitHub >> <#4 (comment)>, >> or unsubscribe >> <https://github.com/notifications/unsubscribe-auth/AGAQXF4RI6EWF3H6W6EKH63YHHSJRAVCNFSM6AAAAABAB2N44GVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQMZWGIYDKNZZGI> >> . >> You are receiving this because you authored the thread.Message ID: >> ***@***.***> >> >

[markspan]

I can confirm that the PMD_Control UUID is the one we use with our 8 Polarbands. They work here. Our bands were bought in two seperate batches, more than one year ago. A new version of the band could have, but should not have different UUIDs. I know of more individuals working with this software, and have not heard this problem before. You could use the GATTBrowser app on android to look up the various UUIDs. For me, it is found as the first GATT service with READ/WRITE/INDICATE, and a seperate NOTIFY Property. Hope this helps.

But its hard to "debug" from here.. Sorry.

[HuskerHeel]

Thank you for the feedback and understand its hard to troubleshoot this way. I'll try the GATT service route and some other bands. I'm wondering if perhaps when ours were ordered, since I'm with the DoD, that maybe the read capabilities were shut off or altered.

…

On Tue, Dec 5, 2023 at 2:09 AM Mark M. Span ***@***.***> wrote: I can confirm that the PMD_Control UUID is the one we use with our 8 Polarbands. They work here. Our bands were bought in two seperate batches, more than one year ago. A new version of the band could have, but should not have different UUIDs. I know of more individuals working with this software, and have not heard this problem before. You could use the GATTBrowser app on android to look up the various UUIDs. For me, it is found as the first GATT service with READ/WRITE/INDICATE, and a seperate NOTIFY Property. Hope this helps. But its hard to "debug" from here.. Sorry. — Reply to this email directly, view it on GitHub <#4 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AGAQXF5OGMNXJRJJD72FILTYH3QDTAVCNFSM6AAAAABAB2N44GVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQNBQGMYTSNRVGM> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[HuskerHeel]

I can confirm that the old H10 bands we have have a different PMD_Control UUID ("FB005C52-02E7-F387-1CAD-8ACD2D8DF0C8") and they do not have READ/WRITE/INDICATE, which I think was my issue (weird). I bought a new Polar H10 today, and using the plugable Bluetooth 4.0 LE adapter, I got it to work using the PolarGUI! Thank you for your patience and help troubleshooting my issue.

…

On Tue, Dec 5, 2023 at 6:37 AM Anthony Ries ***@***.***> wrote: Thank you for the feedback and understand its hard to troubleshoot this way. I'll try the GATT service route and some other bands. I'm wondering if perhaps when ours were ordered, since I'm with the DoD, that maybe the read capabilities were shut off or altered. On Tue, Dec 5, 2023 at 2:09 AM Mark M. Span ***@***.***> wrote: > I can confirm that the PMD_Control UUID is the one we use with our 8 > Polarbands. They work here. Our bands were bought in two seperate batches, > more than one year ago. A new version of the band could have, but should > not have different UUIDs. I know of more individuals working with this > software, and have not heard this problem before. You could use the > GATTBrowser app on android to look up the various UUIDs. For me, it is > found as the first GATT service with READ/WRITE/INDICATE, and a seperate > NOTIFY Property. Hope this helps. > > But its hard to "debug" from here.. Sorry. > > — > Reply to this email directly, view it on GitHub > <#4 (comment)>, > or unsubscribe > <https://github.com/notifications/unsubscribe-auth/AGAQXF5OGMNXJRJJD72FILTYH3QDTAVCNFSM6AAAAABAB2N44GVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQNBQGMYTSNRVGM> > . > You are receiving this because you authored the thread.Message ID: > ***@***.***> >

[markspan]

Great that you got it to work. I am amazed that the uuid values have changed. I'll try to find a way to detect the issue and make the code work regardless. If you have pointers let me know!