ITD not trying to reconnect after PineTime re-enters range #44

Open
opened 2 months ago by hafl · 6 comments
hafl commented 2 months ago

Steps to reproduce:

  • launch itd
  • confirm pinetime is connected
  • wander out of range for a few minutes
  • re-enter range

Per bluetoothctl (bluetoothctl devices Connected) there no connected devices.
Per pinetime, no bt icon is displayed.

The actual steps to reproduce may require wandering in and out of range more than once before staying out of range for a few minutes.

Built from source, git log shows 73a679d10bf09a965b5afd3d0e81f51813325c67 as the latest commit.

Steps to reproduce: * launch itd * confirm pinetime is connected * wander out of range for a few minutes * re-enter range Per bluetoothctl (`bluetoothctl devices Connected`) there no connected devices. Per pinetime, no bt icon is displayed. The actual steps to reproduce may require wandering in and out of range more than once before staying out of range for a few minutes. Built from source, git log shows `73a679d10bf09a965b5afd3d0e81f51813325c67` as the latest commit.
hafl commented 2 months ago
Poster

Sorry, forgot to add, this was on Arch Linux Arm, Pine64 PinePhonePro.

Sorry, forgot to add, this was on Arch Linux Arm, Pine64 PinePhonePro.
hafl commented 2 months ago
Poster
pacman -Q | grep -i bluez
bluez 5.66-1
bluez-libs 5.66-1
bluez-plugins 5.66-1
bluez-qt 5.100.0-1
bluez-tools 0.2.0-5
bluez-utils 5.66-1
``` pacman -Q | grep -i bluez bluez 5.66-1 bluez-libs 5.66-1 bluez-plugins 5.66-1 bluez-qt 5.100.0-1 bluez-tools 0.2.0-5 bluez-utils 5.66-1 ```
hafl changed title from IIT not trying to reconnect after PineTime re-enters range to ITD not trying to reconnect after PineTime re-enters range 2 months ago
Owner

In your output, I can see these lines:

11:32PM DBG Device not connected, connecting
11:32PM DBG InfiniTime device found in list mac=D7:F3:C3:74:52:44
11:32PM DBG Device not connected, connecting
11:32PM DBG Reconnected to device, running OnReconnect callback
11:32PM DBG Checking characteristic status
11:32PM DBG InfiniTime device found in list mac=D7:F3:C3:74:52:44
11:32PM DBG Device not connected, connecting
11:32PM DBG Reconnected to device, running OnReconnect callback

Which tells me ITD actually did reconnect to the device

In your output, I can see these lines: ``` 11:32PM DBG Device not connected, connecting 11:32PM DBG InfiniTime device found in list mac=D7:F3:C3:74:52:44 11:32PM DBG Device not connected, connecting 11:32PM DBG Reconnected to device, running OnReconnect callback 11:32PM DBG Checking characteristic status ``` ``` 11:32PM DBG InfiniTime device found in list mac=D7:F3:C3:74:52:44 11:32PM DBG Device not connected, connecting 11:32PM DBG Reconnected to device, running OnReconnect callback ``` Which tells me ITD actually did reconnect to the device
hafl commented 2 months ago
Poster

After reporting this, it did not display the BT icon on the PineTime nor did any future notifications pop up. I'll see if I can capture any additional information in a future reply.

After reporting this, it did not display the BT icon on the PineTime nor did any future notifications pop up. I'll see if I can capture any additional information in a future reply.
hafl commented 2 months ago
Poster

Actually, I guess there isn't much more to capture.

$ ./itctl notify one two
10:00PM FTL Error while running app error="not connected"

And the output of itd has changed by one line:

10:00PM DBG Checking characteristic status   
Actually, I guess there isn't much more to capture. ``` $ ./itctl notify one two 10:00PM FTL Error while running app error="not connected" ``` And the output of itd has changed by one line: ``` 10:00PM DBG Checking characteristic status ```

I'm seeing the same problem on Arch Linux on AMD. I've attached a debug log where I've inserted a few blank lines each time I walked out of range for a few seconds. Each time I came back in range I sent a notification. Everything worked fine the first two times I returned, but the third time nothing at all was logged, the watch claimed to be disconnected, and sending a notification resulted in only the single "Checking characteristic status" line you see at the end.

I'm seeing the same problem on Arch Linux on AMD. I've attached a debug log where I've inserted a few blank lines each time I walked out of range for a few seconds. Each time I came back in range I sent a notification. Everything worked fine the first two times I returned, but the third time nothing at all was logged, the watch claimed to be disconnected, and sending a notification resulted in only the single "Checking characteristic status" line you see at the end.
6.6 KiB
Sign in to join this conversation.
Loading…
There is no content yet.