This is a BLE implementation for the NRF52840 that acts like a BLE (Bluetooth Low Energy) remote for the Sony Alpha series that support the BLE remotes similar to JJC-RMT-P1BT. I've tried this on a Sony A7 III but from my understanding it should work with ZV-1, RX100VII, ZV-E10, A7C, A6100, A6600, A1, A7RIV, A7SIII, A9II, 6400 and A7RIII as well.

Specifically this code runs on the Adafruit NRF52840 Express which costs about $25. The repo is a PlatformIO project meaning if you open this it should handle dependencies and the toolchain to program your NRF52840. Currently the code will try to pair with whatever camera is open for pairing (described further down) and save that pairing and then automatically reconnect to that camera when avaliable. There is prob better ways of solving this but yeah, took the easy route here.

When trying to discover the camera, you have to specifically scan for the "manufacturer data" as Sony uses this to indicate state etc for the camera. So for example an advertistment header might look like this: 0x2D, 0x01, 0x03, 0x00, 0x64, 0x00, 0x45, 0x31, 0x22, 0xEF, 0x00. Decoding this you get:

The interesting part here is 0x22 0xEF 0x00 which indicates that the camera is open to pairing. If the camera is not in pairing mode you will get 0x22 0xAF 0x00 instead.

We are specifically interested in consuming the 8000FF00-FF00-FFFF-FFFF-FFFFFFFFFFFF service which contains two characteristics.

This is what I initially thought and reflected in the variable names in the code:

However, Greg Leeds did a better job reversing this. With additional testing script done by tao-j, the best guesstimate of the command code is summarized in the following table.

In summary, those codes discovered so far have a length of either 2 or 3 bytes of the format:

+-----------------+-----------------+----------------------+
|     Length      |     Command     | Step size (optional) |
+-----------------+-----------------+----------------------+

The first byte Length is always present, it denotes how many bytes proceeding it: 0x01 for 1 byte, and 0x02 for two bytes. The second byte Command is the actual command, it either simulates a button or indicates a property change like zoom or focus. The third byte Step size is optional, which is usually accompanied by a property change second byte to denote a step size. Known valid step sizes are listed in the bracket for each command, there could be more, only Sony engineering know that so far.

Sadly, an exhaustive scan for Command codes from 0x00 to 0xff revealed no extra hidden code.

For button codes, it's of best practice to issue them in pairs of Down and Up. The shutter button commands must go through the sequence of "Half down -> Fully down -> Half up -> Fully up", otherwise the camera will be stuck in an inoperable state.

• Greg Leeds
• tao-j for further digging, reproing and discovering