What happens is the PIN prompt appears on the camera and stays there until I sent it the value, it then shows a connection failed message for about 10 seconds and then shows a message saying no device is attached .
I have attached some (blurry!) pictures of the camera during this process.
Not sure if the no device connected is a bit of a red herring though as the camera shows this when you connect to it via nRF for example but aren't bonded yet.
For reference, here is an nRF log of performing the same process manually from an unbonded phone (so its essentially in the same state as the Pixl) to the camera and writing the same value to the characteristic UUID 5dd3465f-1aee-4299-8493-d2eca2f8e1bb
It is at the point of sending the value to that characteristic that the PIN screen is invoked on the camera and in this log I have obviously entered the PIN on the phone to complete the process and then am able to send to the characteristic and then register and receive notifications on the other characteristic.
nRF Connect, 2019-02-04
Pocket Cinema Camera 4K A:1C2 (90:FD:9F:B8:CA:37)
V 11:08:00.011 Connecting to 90:FD:9F:B8:CA:37...
D 11:08:00.011 gatt = device.connectGatt(autoConnect = false, TRANSPORT_LE)
D 11:08:00.274 [Server callback] Connection state changed with status: 0 and new state: CONNECTED (2)
I 11:08:00.274 [Server] Device with address 90:FD:9F:B8:CA:37 connected
I 11:08:00.275 [Server] MTU changed to 64
D 11:08:00.384 [Callback] Connection state changed with status: 0 and new state: CONNECTED (2)
D 11:08:00.384 [Broadcast] Action received: android.bluetooth.device.action.ACL_CONNECTED
I 11:08:00.384 Connected to 90:FD:9F:B8:CA:37
D 11:08:00.392 wait(1600ms)
V 11:08:02.007 Discovering services...
D 11:08:02.007 gatt.discoverServices()
D 11:08:02.023 [Callback] Services discovered with status: 0
I 11:08:02.023 Services discovered
V 11:08:02.051 Generic Access (0x1800)
- Device Name [R] (0x2A00)
- Appearance [R] (0x2A01)
Device Information (0x180A)
- Manufacturer Name String [R] (0x2A29)
- Model Number String [R] (0x2A24)
Unknown Service (291d567a-6d75-11e6-8b77-86f30ca893d3)
- Unknown Characteristic [W] (5dd3465f-1aee-4299-8493-d2eca2f8e1bb)
- Unknown Characteristic [I] (b864e140-76a0-416a-bf30-5876504537d9)
Client Characteristic Configuration (0x2902)
- Unknown Characteristic [N] (6d8f2110-86f1-41bf-9afb-451d87e976c8)
Client Characteristic Configuration (0x2902)
- Unknown Characteristic [N R W] (7fe8691d-95dc-4fc5-8abd-ca74339b51b9)
Client Characteristic Configuration (0x2902)
- Unknown Characteristic [W] (ffac0c52-c9fb-41a0-b063-cc76282eb89c)
- Unknown Characteristic [R] (8f1fd018-b508-456f-8f82-3d392bee2706)
D 11:08:02.052 gatt.setCharacteristicNotification(b864e140-76a0-416a-bf30-5876504537d9, true)
D 11:08:02.054 gatt.setCharacteristicNotification(6d8f2110-86f1-41bf-9afb-451d87e976c8, true)
D 11:08:02.058 gatt.setCharacteristicNotification(7fe8691d-95dc-4fc5-8abd-ca74339b51b9, true)
V 11:08:15.364 Writing request to characteristic 5dd3465f-1aee-4299-8493-d2eca2f8e1bb
D 11:08:15.364 gatt.writeCharacteristic(5dd3465f-1aee-4299-8493-d2eca2f8e1bb, value=0xFF04000000010000)
D 11:08:15.819 [Broadcast] Action received: android.bluetooth.device.action.BOND_STATE_CHANGED, bond state changed to: BOND_BONDING (11)
D 11:08:15.837 [Broadcast] Action received: android.bluetooth.device.action.PAIRING_REQUEST, pairing variant: PAIRING_VARIANT_PIN (0)
D 11:08:24.100 [Broadcast] Action received: android.bluetooth.device.action.BOND_STATE_CHANGED, bond state changed to: BOND_BONDED (12)
I 11:08:24.100 Device bonded
I 11:08:24.125 Data written to 5dd3465f-1aee-4299-8493-d2eca2f8e1bb, value: (0x) FF-04-00-00-00-01-00-00
A 11:08:24.126 "(0x) FF-04-00-00-00-01-00-00" sent
V 11:08:36.136 Writing request to characteristic 5dd3465f-1aee-4299-8493-d2eca2f8e1bb
D 11:08:36.136 gatt.writeCharacteristic(5dd3465f-1aee-4299-8493-d2eca2f8e1bb, value=0xFF04000000010000)
I 11:08:36.196 Data written to 5dd3465f-1aee-4299-8493-d2eca2f8e1bb, value: (0x) FF-04-00-00-00-01-00-00
A 11:08:36.196 "(0x) FF-04-00-00-00-01-00-00" sent
V 11:08:47.245 Disabling notifications for 7fe8691d-95dc-4fc5-8abd-ca74339b51b9
D 11:08:47.245 gatt.setCharacteristicNotification(7fe8691d-95dc-4fc5-8abd-ca74339b51b9, false)
D 11:08:47.246 gatt.writeDescriptor(00002902-0000-1000-8000-00805f9b34fb, value=0x0000)
I 11:08:47.311 Data written to descr. 00002902-0000-1000-8000-00805f9b34fb, value: (0x) 00-00
A 11:08:47.311 "Notifications and indications disabled" sent
V 11:08:47.313 Notifications and indications disabled for 7fe8691d-95dc-4fc5-8abd-ca74339b51b9
V 11:08:50.416 Enabling notifications for 7fe8691d-95dc-4fc5-8abd-ca74339b51b9
D 11:08:50.416 gatt.setCharacteristicNotification(7fe8691d-95dc-4fc5-8abd-ca74339b51b9, true)
D 11:08:50.417 gatt.writeDescriptor(00002902-0000-1000-8000-00805f9b34fb, value=0x0100)
I 11:08:50.479 Data written to descr. 00002902-0000-1000-8000-00805f9b34fb, value: (0x) 01-00
A 11:08:50.479 "Notifications enabled" sent
V 11:08:50.481 Notifications enabled for 7fe8691d-95dc-4fc5-8abd-ca74339b51b9
V 11:08:58.285 Disabling indications for b864e140-76a0-416a-bf30-5876504537d9
D 11:08:58.285 gatt.setCharacteristicNotification(b864e140-76a0-416a-bf30-5876504537d9, false)
D 11:08:58.286 gatt.writeDescriptor(00002902-0000-1000-8000-00805f9b34fb, value=0x0000)
I 11:08:58.377 Data written to descr. 00002902-0000-1000-8000-00805f9b34fb, value: (0x) 00-00
A 11:08:58.377 "Notifications and indications disabled" sent
V 11:08:58.378 Notifications and indications disabled for b864e140-76a0-416a-bf30-5876504537d9
V 11:08:59.207 Enabling indications for b864e140-76a0-416a-bf30-5876504537d9
D 11:08:59.208 gatt.setCharacteristicNotification(b864e140-76a0-416a-bf30-5876504537d9, true)
D 11:08:59.209 gatt.writeDescriptor(00002902-0000-1000-8000-00805f9b34fb, value=0x0200)
I 11:08:59.303 Data written to descr. 00002902-0000-1000-8000-00805f9b34fb, value: (0x) 02-00
A 11:08:59.303 "Indications enabled" sent
V 11:08:59.304 Indications enabled for b864e140-76a0-416a-bf30-5876504537d9
I 11:08:59.352 Indication received from b864e140-76a0-416a-bf30-5876504537d9, value: (0x) FF-05-00-00-01-07-01-02-00
A 11:08:59.352 "(0x) FF-05-00-00-01-07-01-02-00" received
Espruino is a JavaScript interpreter for low-power Microcontrollers. This site is both a support community for Espruino and a place to share what you are working on.
What happens is the PIN prompt appears on the camera and stays there until I sent it the value, it then shows a connection failed message for about 10 seconds and then shows a message saying no device is attached .
I have attached some (blurry!) pictures of the camera during this process.
Not sure if the no device connected is a bit of a red herring though as the camera shows this when you connect to it via nRF for example but aren't bonded yet.
For reference, here is an nRF log of performing the same process manually from an unbonded phone (so its essentially in the same state as the Pixl) to the camera and writing the same value to the characteristic UUID 5dd3465f-1aee-4299-8493-d2eca2f8e1bb
It is at the point of sending the value to that characteristic that the PIN screen is invoked on the camera and in this log I have obviously entered the PIN on the phone to complete the process and then am able to send to the characteristic and then register and receive notifications on the other characteristic.