Connection to different bluetooth enabled midi controllers

[Sundeeprk93]

I have asked you in one of your youtube videos of whether it is possible to connect a different bluetooth enabled midi controller like Ampero Control to the Wavshare Zero model and you told that it can be done with a small change in the code.

May I know how it is possible?

[Builty]

Hi. Since that comment, I have added the ability to do this without needing to change the code. You can use the web configuration to enable a custom bluetooth device, and enter its name.
I'm not sure if the Ampero will work, but if it follows the usual Midi standard then it should.

[Sundeeprk93]

I tried connecting to Ampero Control, but it doesn’t connect. On a midi-btle app, this is what the controller is showed as.

Wish there was a bluetooth scanning kinda feature.

[Sundeeprk93]

Also I connected the Ampero Control to my pc and got to know that its device name is Ampero Control. That’s it.

I tried that name , with different combinations, but it doesn't seem to connect to the midi pedal.

There are quite a few problems for me to get a m-vave chocolate.. for one, i already have one bluetooth enabled midi controller. So getting another doesn't make sense.. secondly, i live in india, cant import stuff from china.. hence im struggling to make this work, somehow..

[Sundeeprk93]

Also, additional information..

I tried controlling my tonex one with ampero control, using a the midi chief app. The midi chief app which recognised m-vave chocolate, couldnt scan Ampero Control. The app creator guided me by asking me to pair the Ampero Control with a midi+ble app, and later it was shows as available device in the midi chief app.

[Builty]

I did some reading of the user manual. Have you made sure to disconnect from the device (on your phone) before trying to connect to it with the controller? There is a disconnect button in the app.

Other than that, its a difficult to know what else could be stopping it.

[Sundeeprk93]

I did disconnect. And the led was blinking which indicates that the Ampero Control is in pairing mode..

As far as my understanding goes… even in the case of midi chief, i had to download this app MIDI + BLE, which actually recognises ampero control as a midi device.. after i pair it using this process only, midi chief app recognised it as an “pseudo wired” midi device.

Is it possible for your to manually put in the bluetooth coding address (or something, sorry for my naivety) which i think is mentioned in a screenshot above?

[Builty]

Bluetooth devices have a few different ways how they do pairing. Some like the Chocolate can just be connected to, without needing to do a full pairing routine. It's sometimes calls "Just Works" mode and doesn't use any security.

It sounds like the Ampero can only do pairing via a more secure method with proper pairing.

I have support for secure pairing when the controller acts as a peripheral, but not when its acting as a central device.
I think I will need to add support for secure pairing to make this device work. I can probably do it via the web config.

It will take me some time to get to looking at this though. Its been very busy lately, lots of support requests and also trying to finish off the next firmware version. I have noted it down to look at.

[Sundeeprk93]

One more search, showed this.

“Use a MIDI bridging app:
Download a MIDI bridging app on your phone or computer that can connect to both the Ampero Control via Bluetooth and the other device (via USB or another connection method).”

Like the midi+ble app that scanned and paired with ampero control for Midi Chief app to recognise it as a midi device.

Can something like that be programmed into the chip? Or is it too much to ask from the puny thing of a pcb?

[Builty]

Not sure on that one. I'm sure I can get secure pairing going. If it doesn't send Program Change messages for its footswitches, it might not work in the end.

[Sundeeprk93]

If you can get secured pairing going nothing like it. But why wont it sent PC messages?

Ampero Control is a bluetooth midi device, i used it wired with my hx stomp and also used it to control tonex one via bluetooth, connecting it to my mobile and using the Midi Chief app..

The only problem here is it is not getting connected to the pcb.. if its done, its all good, i guess..

[Builty]

Yeah I think if we could pair it, it will probably work. Right now the code for "central" mode only supports pairing to devices without security. So yeah this is what I need to add.

[Sundeeprk93]

Awesome.. eagerly looking forward for it..

[Sundeeprk93]

https://github.com/midibox/esp32-idf-blemidi

Does this contain any answers to this issue?

[Builty]

That doesn't appear to do secure pairing either. Espressif have code samples, I just need time to go through it all.

[Sundeeprk93]

Oh okay.. take your time..

[Sundeeprk93]

For securing Bluetooth pairing on Espressif ESP32 devices, utilize the gatt_security_server_demo and gatt_security_client_demo provided by ESP-IDF, focusing on setting security parameters (esp_ble_gap_set_security_param), initiating encryption (esp_ble_set_encryption), and handling security events (e.g., ESP_GAP_BLE_SEC_REQ_EVT).
Here's a breakdown of key concepts and code samples:

1. Using esp-idf examples:
   Security Server:
   Start with the gatt_security_server_demo.
   Set security parameters using esp_ble_gap_set_security_param.
   Implement event handling for ESP_GAP_BLE_SEC_REQ_EVT.
   Use esp_ble_gap_security_rsp to respond to peer devices requesting encryption.
   Security Client:
   Use the gatt_security_client_demo.
   Set security parameters using esp_ble_gap_set_security_param.
   Implement event handling for ESP_GAP_BLE_SEC_REQ_EVT.
   Use esp_ble_gap_security_rsp to respond to peer devices requesting encryption.
   Receive ESP_GAP_BLE_AUTH_CMPL_EVT after encryption is complete.

2. Setting Security Parameters:
   C

   #define SECURITY_MASK (ESP_LE_AUTH_BOND | ESP_LE_AUTH_REQ_MITM)
   // ESP_LE_AUTH_BOND: Enables bonding
   // ESP_LE_AUTH_REQ_MITM: Enables MITM protection
   // ESP_LE_AUTH_REQ_SC_ONLY: Enforces Secure Connections
   // ESP_LE_AUTH_REQ_SC_BOND: Enforces Secure Connections with bonding

   #define IO_CAP (ESP_IO_CAP_NONE) // or ESP_IO_CAP_DISPLAY_ONLY
   // ESP_IO_CAP_NONE: The device does not have input or output
   // ESP_IO_CAP_DISPLAY_ONLY: Device only has output

   #define SEC_CONF_AUTH(sec_auth, sec_conf)
   {
   (sec_auth) | (SEC_CONF_AUTH) /* Authentication Request */
   }

   void example_set_security_params() {
   esp_bt_conn_sec_record_t sec_rec = {0};

    // set security parameters
    esp_ble_gap_set_security_param(ESP_BLE_SMP_AUTH_REQ, SEC_CONF_AUTH(SECURITY_MASK, IO_CAP), 0, &sec_rec);
   

   }

3. Initiating and Handling Encryption:
   C

   #define SEC_CONF_AUTH (ESP_BLE_AUTH_REQ_MITM | ESP_BLE_AUTH_BOND)
   void example_initiate_encryption(esp_bt_conn_sec_record_t *peer) {
   esp_ble_set_encryption(peer->addr_type, peer->bd_addr, peer->bd_addr, ESP_BLE_KEY_BIT_ID_EN, 0, NULL, NULL);
   }

   void example_on_evt(esp_ble_gap_event_t event, esp_gap_ble_evt_data_t *event_data)
   {
   switch (event) {
   case ESP_GAP_BLE_SEC_REQ_EVT: {
   printf("ESP_GAP_BLE_SEC_REQ_EVT \n");

         if (sec_auth & ESP_LE_AUTH_REQ_SC_ONLY)
         {
             esp_ble_gap_security_rsp(ESP_BLE_AUTH_REQ_SC_ONLY);
             break;
         }
         if (sec_auth & ESP_LE_AUTH_REQ_MITM)
          {
              esp_ble_gap_security_rsp(ESP_BLE_AUTH_REQ_MITM);
             break;
          }
      break;
   

   }
   }
   }

[Sundeeprk93]

I saw that in the recent release, the bug was fixed for this issue. Can you tell how to connect Ampero control to the 4.3B board?

[Builty]

Hi. You need to check or set the bluetooth device name on the Ampero. I don't have one to give any more details about how.
And then in the Tonex Controller, enable Custom device and enter the same name as the device name.

[Sundeeprk93]

Tried that before also. Tried that now too. Ampero Control doesn't seem to connect like that.

[Builty]

Are you running the latest 1.0.10.2 beta?
This one is tricky for me as I don't own one. I can only go off the reports from other users.

[Sundeeprk93]

Ya I have you said in the recent firmware release note that JJH84 has provided with the back fix, is it not?

And yeah, I did try with the latest beta version as well.

[Builty]

Refer here: #179

JJH84 reported that he was able to connect.

[Sundeeprk93]

Actually my bad, i’ve tried it with the beta 2, it didnt work. But it seems to work with beta 3.

As usual, thank you so much for your effort my brother.