Meshtastic

Bluetooth connection

i got my 2 T beams in flashed them and got one to pair but it wont stay connected for the app to see the device. is there something i missed ?

hmm. Do your tbeams have batteries installed? Can you elaborate a bit on what you mean by won’t stay connected? What is the behavior you see. You connect, pair, use the app and then what happens? (how long and what does the problem look like to you?)

I have a battery installed, tbeam paired to phone. when i open the app it does not see the tbeam.

I have two TTGO Boards with one outputting(putty) plus displaying(display), the OnPassKey, and the second one only occasionally outputting an OnPassKey. The OnPassKey changes from day to day…for both. The problem follows one board.

Please ask for any other info.

(I did order two HiTech boards but they insisted on additional non-duty/taxes charges while the boards were in transit, so I will no longer by their boards. But I had fun with them…)

The TTGO Boards are both.

T22_V1.1
20191212

Both on firmware-tbeam-US-0.7.10.bin

They both act differently.

No battery in either one.

They both have displays now. They both worked the same via putty, with and without a display. The displays just add info.

I have reflashed the one that works less, twice, and the one that works once. The problem stays with one board.

I have swapped usb cables and power sources and the problem follows the same board.

The required Bluetooth pairing code seems to be changing and is not static.

They are acting differently on the boot-up and how they connect via bluetooth.

The “fdc8” board does not always provide an OnPassKey while the “cea0” one does. The cea0 one does not always change its pairing code. If it does, it is displayed it on the screen, the fdc8 has not displayed the OnPassKey on the display as of yet.

After power off, the fdc8 board lost its name (“two”) whereas the cea0 retained its name “ed”.

The cea0 displays

ed
?km
signal: 100%
13 minutes ago

The fdc8 board displays

Unknown fdc8
?km
signal: 100%
7 minutes ago

They both worked last night as I caught the fdc8 board sending a OnPassKey. This morning after being off all night (unplugged-no battery) the fdc8 board lost its name…and has yet to generate a OnPassKey.

Below is some output from the two boards.

+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

LORA init result 0
sending owner !f008d1c7fdc8/Unknown fdc8/?C8
Update DB node 0xd1c7fdc8, rx_time=0
Node status update: 1 online, 1 total
Screen got status update 3
showing standard frames
old user !f008d1c7fdc8/Unknown fdc8/?C8
updating changed=0 user !f008d1c7fdc8/Unknown fdc8/?C8
Adding packet record (id=0x5da22018 Fr0xc8 To0xff, WantAck0, HopLim3 Payload:User)
enqueuing for send (id=0x5da22018 Fr0xc8 To0xff, WantAck0, HopLim3 encrypted)
txGood=0,rxGood=0,rxBad=0
Screen: Started…
Battery 0mV 0%
Screen got status update 1
GPS fix type 0
Ignoring invalid GPS time
New GPS pos lat=0.000000, lon=0.000000, alt=0, pdop=0.000000
Screen got status update 2
showing standard frames
Starting low level send (id=0x5da22018 Fr0xc8 To0xff, WantAck0, HopLim3 encrypted)
Transition powerFSM transition=boot timeout, from=BOOT to=ON
Setting bluetooth enable=1
Pre BT: 200988 heap size
Starting bluetooth
*** Mesh service:
onPassKeyNotify 329280
Trigger powerFSM 7
Transition powerFSM transition=Bluetooth pairing, from=ON to=ON
showing bluetooth screen
Completed sending (id=0x5da22018 Fr0xc8 To0xff, WantAck0, HopLim3 encrypted)

++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

old user !f008d1c7fdc8/Unknown fdc8/?C8
updating changed=0 user !f008d1c7fdc8/Unknown fdc8/?C8
Adding packet record (id=0x4becbfcc Fr0xc8 To0xff, WantAck0, HopLim3 Payload:Use r)
enqueuing for send (id=0x4becbfcc Fr0xc8 To0xff, WantAck0, HopLim3 encrypted)
txGood=0,rxGood=0,rxBad=0
Screen: Started…
Battery 0mV 0%
Screen got status update 1
Starting low level send (id=0x4becbfcc Fr0xc8 To0xff, WantAck0, HopLim3 encrypte d)
GPS fix type 0
Ignoring invalid GPS time
New GPS pos lat=0.000000, lon=0.000000, alt=0, pdop=0.000000
Screen got status update 2
showing standard frames
Transition powerFSM transition=boot timeout, from=BOOT to=ON
Setting bluetooth en able=1
Pre BT: 201128 heap size
Starting bluetooth
*** Mesh service:
Completed sending (id=0x4becbfcc Fr0xc8 To0xff, WantAck0, HopLim3 encrypted)
GPS fix type 0
Ignoring invalid GPS time
GPS fix type 0
Ignoring invalid GPS time
GPS fix type 0

+++++++++++++++++++++++++++++++++++++++++++
Emitting reboot packet for serial shell
▒▒Hbooted, wake cause 0 (boot count 1), reset_reason=reset
I2C device found at address 0x34
axp192 PMU found
I2C device found at address 0x3c
ssd1306 display found
done
Meshtastic swver=0.7.10, hwver=1.0-US
Setting random seed 1046331456
Total heap: 265260
Free heap: 215952
Total PSRAM: 4194252
Free PSRAM: 4194252
chip id detect 0x3
Detect CHIP :AXP192
OUTPUT Register 0x5f
AXP192 Begin PASS
DCDC1: ENABLE
DCDC2: ENABLE
LDO2: ENABLE
LDO3: ENABLE
DCDC3: ENABLE
Exten: ENABLE

DCDC1: ENABLE
DCDC2: ENABLE
LDO2: ENABLE
LDO3: ENABLE
DCDC3: ENABLE
Exten: ENABLE
SRC REG:0xcf
Charging enable is enable
Charging target-voltage : 0x2
end when the charge current is lower than 10% of the set value
Charge current : 1000.00 mA
enab le [0x40]val:0xdc
enable [0x41]val:0xff
enable [0x42]val:0x3b
Turning on screen
Read RTC time as 1 (cur millis 1535) valid=0
Connected to UBLOX GPS successfully
RadioConfig reset!
Installing AES128 key!
Initial packet id 1345760880, numPacketId 4294967295
Loading saved preferences
Warn: devicestate is old, discarding
RadioConfig reset!
Installing AES128 key!
Installing AES128 key!
NODENUM=0xd1c7cea0, dbsize=1
JOINING WIFI: ssid=geeksville
Starting meshradio init…
Set radio: name=Default, config=3, ch=6, power=23
LORA init result 0
sending owner !f008d1c7cea0/Unknown cea0/?A0
Update DB node 0xd1c7cea0, rx_time=0
Node status update: 1 online, 1 total
Screen got status update 3
showing standard frames
old user !f008d1c7cea0/Unknown cea0/?A0
updating changed=0 user !f008d1c7cea0/Unknown cea0/?A0
Adding packet record (id=0x5036ae74 Fr0xa0 To0xff, WantAck0, HopLim3 Payload:Use r)
enqueuing for send (id=0x5036ae74 Fr0xa0 To0xff, WantAck0, HopLim3 encrypted)
txGood=0,rxGood=0,rxBad=0
Screen: Started…
Battery 0mV 0%
Screen got status update 1
GPS fix type 0
Ignoring invalid GPS time
New GPS pos lat=0.000000, lon=0.000000, alt=0, pdop=0.000000
Screen got status update 2
showing standard frames
Starting low level send (id=0x5036ae74 Fr0xa0 To0xff, WantAck0, HopLim3 encrypte d)
Transition powerFSM transition=boot timeout, from=BOOT to=ON
Setting bluetooth en able=1
Pre BT: 200988 heap size
Starting bluetooth
*** Mesh service:
Completed sending (id=0x5036ae74 Fr0xa0 To0xff, WantAck0, HopLim3 encrypted)
authenticated and connected to phone
showing standard frames
getFromRadio, !available
Trigger powerFSM 9
Client wants config, nonce=9
Reset nodeinfo read pointer
getFromRadio, state=2
encoding toPhone packet to phone variant=3, 52 bytes
getFromRadio, state=3
encoding toPhone packet to phone variant=6, 81 bytes
getFromRadio, state=4
Sending nodeinfo: num=0xd1c7cea0, lastseen=0, id=!f008d1c7cea0, name=Unknown cea 0
encoding toPhone packet to phone variant=4, 52 bytes
getFromRadio, state=4
Done sending nodeinfos
getFromRadio, state=5
encoding toPhone packet to phone variant=8, 2 bytes
getFromRadio, !available
Trigger powerFSM 9
Client is setting owner
sending owner !f008d1c7cea0/ed/e
Update DB node 0xd1c7cea0, rx_time=0
old user !f008d1c7cea0/Unknown cea0/?A0
updating changed=1 user !f008d1c7cea0/ed/e
Trigger powerFSM 8
Transition powerFSM transition=NodeDB update, from=ON to=ON
Add ing packet record (id=0x5036ae75 Fr0xa0 To0xff, WantAck0, HopLim3 Payload:User)
enqueuing for send (id=0x5036ae75 Fr0xa0 To0xff, WantAck0, HopLim3 encrypted)
txGood=1,rxGood=0,rxBad=0
Can not send yet, busyRx
GPS fix type 0
Ignoring invalid GPS time
Can not send yet, busyRx
Can not send yet, busyRx
Lora RX (id=0x5036ae74 Fr0xa0 To0xff, WantAck0, HopLim2 encrypted)
Rx someone rebroadcasting for us (id=0x5036ae74 Fr0xa0 To0xff, WantAck0, HopLim2 encrypted)
Found existing packet record for fr=0xd1c7cea0,to=0xffffffff,id=1345760884
Ignoring incoming msg, because we’ve already seen it: fr=0xd1c7cea0,to=0xfffffff f,id=1345760884,hop_limit=2
Starting low level send (id=0x5036ae75 Fr0xa0 To0xff, WantAck0, HopLim3 encrypte d)
Completed sending (id=0x5036ae75 Fr0xa0 To0xff, WantAck0, HopLim3 encrypted)
GPS fix type 0
Ignoring invalid GPS time
Lora RX (id=0x095dc69d Fr0xc8 To0xa0, WantAck0, HopLim3 encrypted)
Adding packet record (id=0x095dc69d Fr0xc8 To0xa0, WantAck0, HopLim3 encrypted)
FIXME not implementedFIXME-update-db Sniffing packet
Delivering rx packet (id=0x095dc69d Fr0xc8 To0xa0, WantAck0, HopLim3 Payload:Use r)
Trigger powerFSM 3
Ignoring incoming time, because we have a GPS
Forwarding to phone (id=0x095dc69d Fr0xc8 To0xa0, WantAck0, HopLim3 Payload:User )
Update DB node 0xd1c7fdc8, rx_time=0
Node status update: 2 online, 2 total
Screen got status update 3
showing standard frames
old user //
updating changed=1 user !f008d1c7fdc8/Unknown fdc8/?C8
Trigger powerFSM 8
Transition powerFSM transition=NodeDB update, from=ON to=ON
Tel ling client we have new packets 1
Telling client we have new packets 1
Sending network ping to 0xd1c7fdc8, with position=0, wantReplies=1
sending owner !f008d1c7cea0/ed/e
Update DB node 0xd1c7cea0, rx_time=0
old user !f008d1c7cea0/ed/e
updating changed=0 user !f008d1c7cea0/ed/e
Adding packet record (id=0x5036ae76 Fr0xa0 To0xc8, WantAck0, HopLim3 Payload:Use r WANTRESP)
enqueuing for send (id=0x5036ae76 Fr0xa0 To0xc8, WantAck0, HopLim3 encrypted)
txGood=2,rxGood=2,rxBad=0
getFromRadio, state=6
encoding toPhone packet to phone variant=2, 72 bytes
getFromRadio, !available
Can not send yet, busyRx
Can not send yet, busyRx
Can not send yet, busyRx
Can not send yet, busyRx
Can not send yet, busyRx
Can not send yet, busyRx
Can not send yet, busyRx
Lora RX (id=0x095dc69e Fr0xc8 To0xa0, WantAck0, HopLim3 encrypted)
Adding packet record (id=0x095dc69e Fr0xc8 To0xa0, WantAck0, HopLim3 encrypted)
FIXME not implementedFIXME-update-db Sniffing packet
Delivering rx packet (id=0x095dc69e Fr0xc8 To0xa0, WantAck0, HopLim3 Payload:Use r WANTRESP)
Trigger powerFSM 3
Ignoring incoming time, because we have a GPS
Forwarding to phone (id=0x095dc69e Fr0xc8 To0xa0, WantAck0, HopLim3 Payload:User WANTRESP)
Update DB node 0xd1c7fdc8, rx_time=0
old user !f008d1c7fdc8/Unknown fdc8/?C8
updating changed=0 user !f008d1c7fdc8/Unknown fdc8/?C8
Sending network ping to 0xd1c7fdc8, with position=0, wantReplies=0
sending owner !f008d1c7cea0/ed/e
Update DB node 0xd1c7cea0, rx_time=0
old user !f008d1c7cea0/ed/e
updating changed=0 user !f008d1c7cea0/ed/e
Adding packet record (id=0x5036ae77 Fr0xa0 To0xc8, WantAck0, HopLim3 Payload:Use r)
enqueuing for send (id=0x5036ae77 Fr0xa0 To0xc8, WantAck0, HopLim3 encrypted)
txGood=2,rxGood=3,rxBad=0
Telling client we have new packets 2
Telling client we have new packets 2
getFromRadio, state=6
encoding toPhone packet to phone variant=2, 74 bytes
getFromRadio, !available
Can not send yet, busyRx
Can not send yet, busyRx
GPS fix type 0
Ignoring invalid GPS time
Can not send yet, busyRx
Can not send yet, busyRx
Lora RX (id=0x5036ae75 Fr0xa0 To0xff, WantAck0, HopLim2 encrypted)
Rx someone rebroadcasting for us (id=0x5036ae75 Fr0xa0 To0xff, WantAck0, HopLim2 encrypted)
Found existing packet record for fr=0xd1c7cea0,to=0xffffffff,id=1345760885
Ignoring incoming msg, because we’ve already seen it: fr=0xd1c7cea0,to=0xfffffff f,id=1345760885,hop_limit=2
Starting low level send (id=0x5036ae76 Fr0xa0 To0xc8, WantAck0, HopLim3 encrypte d)
Completed sending (id=0x5036ae76 Fr0xa0 To0xc8, WantAck0, HopLim3 encrypted)
Can not send yet, busyRx
Can not send yet, busyRx
Can not send yet, busyRx
Can not send yet, busyRx
Lora RX (id=0x095dc69f Fr0xc8 To0xa0, WantAck0, HopLim3 encrypted)
Adding packet record (id=0x095dc69f Fr0xc8 To0xa0, WantAck0, HopLim3 encrypted)
FIXME not implementedFIXME-update-db Sniffing packet
Delivering rx packet (id=0x095dc69f Fr0xc8 To0xa0, WantAck0, HopLim3 Payload:Use r)
Trigger powerFSM 3
Ignoring incoming time, because we have a GPS
Forwarding to phone (id=0x095dc69f Fr0xc8 To0xa0, WantAck0, HopLim3 Payload:User )
Update DB node 0xd1c7fdc8, rx_time=0
old user !f008d1c7fdc8/Unknown fdc8/?C8
updating changed=0 user !f008d1c7fdc8/Unknown fdc8/?C8
Telling client we have new packets 3
Telling client we have new packets 3
GPS fix type 0
Ignoring invalid GPS time
getFromRadio, state=6
encoding toPhone packet to phone variant=2, 72 bytes
getFromRadio, !available
Starting low level send (id=0x5036ae77 Fr0xa0 To0xc8, WantAck0, HopLim3 encrypte d)
Completed sending (id=0x5036ae77 Fr0xa0 To0xc8, WantAck0, HopLim3 encrypted)
GPS fix type 0
Ignoring invalid GPS time
GPS fix type 0
Ignoring invalid GPS time
GPS fix type 0
Ignoring invalid GPS time

++++++++++++++++++++++++++++++++++++++++++++++++++++++
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
++++++++++++++++++++++++++++++++++++++++++++++++++++++++

THIS ONE WORKS

old user !f008d1c7cea0/Unknown cea0/?A0
updating changed=0 user !f008d1c7cea0/Unknown cea0/?A0
Adding packet record (id=0x6204b605 Fr0xa0 To0xff, WantAck0, HopLim3 Payload:User)
enqueuing for send (id=0x6204b605 Fr0xa0 To0xff, WantAck0, HopLim3 encrypted)
txGood=0,rxGood=0,rxBad=0
Screen: Started…
Battery 0mV 0%
Screen got status update 1
Starting low level send (id=0x6204b605 Fr0xa0 To0xff, WantAck0, HopLim3 encrypted)
GPS fix type 0
Ignoring invalid GPS time
New GPS pos lat=0.000000, lon=0.000000, alt=0, pdop=0.000000
Screen got status update 2
showing standard frames
Transition powerFSM transition=boot timeout, from=BOOT to=ON
Setting bluetooth enable=1
Pre BT: 201128 heap size
Starting bluetooth
*** Mesh service:
Completed sending (id=0x6204b605 Fr0xa0 To0xff, WantAck0, HopLim3 encrypted)
GPS fix type 0
Ignoring invalid GPS time
GPS fix type 0
Ignoring invalid GPS time
GPS fix type 0
Ignoring invalid GPS time
onPassKeyNotify 113725
Trigger powerFSM 7
Transition powerFSM transition=Bluetooth pairing, from=ON to=ON
showing bluetooth screen
phone authenticate failed 85
showing standard frames
GPS fix type 0
Ignoring invalid GPS time
GPS fix type 0
Ignoring invalid GPS time

++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

The pass key does change between different pairing events but generally once paired, you don’t need to re-pair with the new key. The new key will only be displayed on screen or in putty when you try re-pair with the device.

You could try “forget” the devices in your Bluetooth settings and even clear the app data in the Android settings and then try re-pairing from within the Meshtastic app.

Hi,

Maybe the key is not suppose to change but it did in my case. The cea0 device needed a new key this morning and displayed it on the screen.

2 Likes

This is the second report I’ve heard of this and yeah, sounds not correct:

Hi,

If you need to to test or capture anything. Please let me know. Not a programmer but can do some testing to help out.

1 Like

I have exactly the same issue with both the Android phone that I have. It just drops the bluetooth connection after the unit sleeps and never recovers without re-pairing. Also TTGO
Justin

1 Like

Hi g8, what phone model, Android app version and device firmware version please?

Hi Kevin.

Two Phones with exactly the same issue:

ZTE Blade (Branded as Vodafone Smart Ultra 6) Android 6.0.1 App 0.7.93
Wiley Fox Swift Android 7.1.2, App 0.7.91

Both UK phones.

I tried disabling BT scanning on the phone, but to no avail. One the BT goes into sleep, that’s it. I suspect the changing PIN number might have something to do with it.

Stop Press: The Wiley Fox has just woken up and sent messages, so perhaps disabling BT scanning has helped? Not sure about the ZTE Blade yet.

Stope Press II Seems that that “wake up” was a one off…

Another update, after the phone disconnects I keep getting “pairing requests” from the meshtastic device, so again I think its the changing PIN number that’s the root issue.

Justin.

1 Like