Fix properties check to use Bleak Write value

[philrittenhouse]

Re: Issue #39 Unable to Write Characteristic

I have tested this change on Windows 10

Let me know if there is anything I missed.

Thanks,
Phil

[dhalbert]

After looking at this in more detail, I think the problem may be instead that this code is wrong:

Adafruit_Blinka_bleio/_bleio/common.py

Lines 531 to 532 in a7d0372

	for prop in _bleak_characteristic.properties:
	properties |= GattCharacteristicsFlags[prop.replace("-", "_")].value

It is assuming that the bleak property bits are the same as the ones I defined. Instead, we need a mapping from each bleak bit to each other bit, or we need to change our bits to match bleak's. The bits chosen here were the same ones that nRF uses, so I think it might be better to do the mapping, rather than just change the bit values. But I need to think about that. I Your change works for that particular bit, but it might not work for the others. I will look at this again tomorrow; it's late at the moment. I'm sorry I led you astray in your initial proposed change.

[philrittenhouse]

I have been doing some digging and I have found a few sources that seem to suggest the characterstic properties are defined in the spec. I don't have access to the spec to confirm but this table from Nordic suggests the values are defined in the BLE Core Spec v4.2

https://devzone.nordicsemi.com/nordic/short-range-guides/b/bluetooth-low-energy/posts/ble-characteristics-a-beginners-tutorial

[ukBaz]

The Core Specification is open to anyone and is available at:

https://www.bluetooth.com/specifications/specs/core-specification/

The version has moved on to 5.3 now but this data shouldn't be changing.

I think this is the table you are referring to:

[markjbianchi]

I came across this same issue (and just now found this pull request), and traced it down to the Characteristic.READ/WRITE/etc bit masks not matching the BLE standard, as shown above. I think the correct fix would be to simply change the property bit mask values in Characteristic class in common.py to match that standard. I have done that locally and it works perfectly now.