Init preset FAILED. ERROR - GATT Error Unknown.

[StuGotz]

Thank you for creating this! I wanted to report the error I'm getting almost immediately after pairing my device.

Pixel 6 Pro running Android 16
Chrome Beta 142.0.7444.48
Vitruvian Firmware 3.2.4
Hardware Ver: franklin

No issues connecting via Vitruvian Android App on the same phone. App log below, please let me know anything else I can provide to help troubleshoot

Vitruvian Web Control Ready
Click "Connect to Device" to begin
Requirements:
- Chrome, Edge, or Opera browser
- HTTPS connection (or localhost)
- Bluetooth enabled on your device
Requesting Bluetooth device...
Found device: Vee_00001C12_386F6480
Connecting to GATT server...
Connected! Discovering services...
Found NUS service
Discovered 19 characteristics
Characteristic: 2de5222f-330d-4385-b04a-970b8042bcdf
Characteristic: 36e6c2ee-21c7-404e-aa9b-f74ca4728ad4
Characteristic: 383f7276-49af-4335-9072-f01b0f8acad6
Characteristic: 5fa538ec-d041-42f6-bbd6-c30d475387b7
-> Tagged property polling handle (0x003f)
Characteristic: 67d0dae0-5bfc-4ea2-acc9-ac784dee7f29
Characteristic: 6d094aa3-b60d-4916-8a55-8ed73fb9f6a5
Characteristic: 6d094aa3-b60d-4916-8a55-8ed73fb9f6a6
Characteristic: 6d094aa3-b60d-4916-8a55-8ed73fb9f6a7
Characteristic: 6d094aa3-b60d-4916-8a55-8ed73fb9f6a8
Characteristic: 6d094aa3-b60d-4916-8a55-8ed73fb9f6a9
Characteristic: 6d094aa3-b60d-4916-8a55-8ed73fb9f6aa
Characteristic: 6d094aa3-b60d-4916-8a55-8ed73fb9f6ab
Characteristic: 6d094aa3-b60d-4916-8a55-8ed73fb9f6ac
Characteristic: 6e400002-b5a3-f393-e0a9-e50e24dcca9e
-> Using as command write characteristic
Characteristic: 74e994ac-0e80-4c02-9cd0-76cb31d3959b
Characteristic: 8308f2a6-0875-4a94-a86f-5c5c5e1b068a
-> Tagged rep notification handle (0x0036)
Characteristic: 90e991a6-c548-44ed-969b-eb541014eae3
-> Tagged monitor polling handle (0x0039)
Characteristic: c7b73007-b245-4503-a1ed-9e4e97eb9802
Characteristic: ef0e485a-8749-4314-b1be-01e57cd1712e
Enabling core BLE subscriptions...
Enabling notifications on 36e6c2ee-21c7-404e-aa9b-f74ca4728ad4...
-> Notifications active
Enabling notifications on 383f7276-49af-4335-9072-f01b0f8acad6...
-> Notifications active
Enabling notifications on 67d0dae0-5bfc-4ea2-acc9-ac784dee7f29...
-> Notifications active
Enabling notifications on 74e994ac-0e80-4c02-9cd0-76cb31d3959b...
-> Notifications active
Enabling notifications on 8308f2a6-0875-4a94-a86f-5c5c5e1b068a...
-> Notifications active
Enabling notifications on c7b73007-b245-4503-a1ed-9e4e97eb9802...
-> Notifications active
Enabling notifications on ef0e485a-8749-4314-b1be-01e57cd1712e...
-> Notifications active
Core notifications enabled!
Device ready!
Sending INIT sequence...
-> Init command (4 bytes): 0a 00 00 00
<- Init command acknowledged
-> Init preset (34 bytes): 11 00 00 00 00 00 00 00 00 00 00 00 cd cc cc 3e ff 00 4c ff 23 8c ff 8c 8c ff 00 4c ff 23 8c ff 8c 8c
<- Init preset FAILED
Error: GATT Error Unknown.
Connection failed: GATT Error Unknown.
Device disconnected

[StuGotz]

I don't know how many hardware revisions with specific firmware there are out there for these devices, but I think I've successfully captured a Bluetooth HCI snoop log while using the different modes and changing colors if that could be at all helpful.

[workoutmachineappfree]

That log would be great to take a look at
With it I could compare if the init packet (the one failing) we are sending differs from the one that works from your device
Not sure why that would be happening/if we could fix anything based on it, but it would be a good starting point

Other than that it might be good to check try a different browser on your phone (looks like there are few other browsers on android that suppor tweb bluetooth: https://github.com/WebBluetoothCG/web-bluetooth/blob/main/implementation-status.md)
Also it might be worth trying on a laptop.

[StuGotz]

That log would be great to take a look at

Here you go. I hope it has what you need.

https://limewire.com/d/CuOml#sPogOBy8gO

I'll try some other android browsers and a laptop too.

[StuGotz]

That log would be great to take a look at With it I could compare if the init packet (the one failing) we are sending differs from the one that works from your device Not sure why that would be happening/if we could fix anything based on it, but it would be a good starting point

Other than that it might be good to check try a different browser on your phone (looks like there are few other browsers on android that suppor tweb bluetooth: https://github.com/WebBluetoothCG/web-bluetooth/blob/main/implementation-status.md) Also it might be worth trying on a laptop.

Worked just fine from a laptop and a Pixel 8 Pro. I guess it's time to replace my Pixel 6 Pro. Until I upgraded from Android 15 to 16 the Vitruvian app would crash randomly EVERY time I worked out (even after wiping the phone and reinstalling 15). It's been rock solid after upgrading to 16 though.

Curious if the bluetooth PCAP file actually contained the packets when using the Vitruvian though. I loaded it into Wireshark and quickly realized I had not a clue...