Bluetooth errors

[nionata]

Transmission was successful with up to 4 devices! That being said, issues arose. As more devices started interacting, there were more and more issues.

• Operation was cancelled - likely because there was a scan/advertise at the same time as a write request
• Write request failed - this was a direct result of trying to send a long message

Originally posted by @nionata in https://github.com/nionata/grapevine/issues/35#issuecomment-974889167

[nionata]

[nionata]

I am going to first try and relax the task runner interval. If that doesn't work, I have a feeling the move to transmitting a user id instead of messages directly will resolve some of these issues

Update I tried removing the tickler and it resulted in a single transmission. My hunch is that advertising resumes after a transmission. However, after a connection via the central module, device scanning stops.

[nionata]

Re: write error

After adding a try catch in the peripheral handlers, the write request from the central's POV no longer errors out. Instead, the peripheral now logs this error:

ERROR  [Error: invalid wire type 4 at offset 113]

[nionata]

maximum length is limited to 512 bytes by the specification

The size of the value of any GATT attribute is fixed. By adding additional message meta, I must have exceeded this limit causing the over-wire base64 string to be corrupted. This is the end of the road for bluetooth message transmission. Goodbye v0, hello v1.