If your going to have a physical button to enable it to be reconfigured you dont have many options. An idea may be to write something to flash storage after the first time its been configured and not allow additional setup attempts unless that file is removed but if someone has physical access to the device there's nothing stopping them connecting over uart and removing it via repl. Alternatively. A physical preventative might be more suitable (lock it in a box)

@eric73 Thank you so much! It worked! Also, it can scan and advertise at the same time.

Hi @nobo23 Are you trying to connect multiple sensors to the WiPy and communicate with them via Bluetooth? Connecting multiple BLE nodes to the WiPy is possible. You can find our BLE examples here. Hope this helps, let me know if you have any questions!

@bmarkus And what are the best values for getting that? (on EU zone)

@manuelc1318 as I wrote, you can transmit data in both directions: write to a characteristic to send data from client to server, and either read from a characteristic or use notifications for data from server to client.

I think I have an older version, ill update.. new firmware fixed the issue!! Thank you for the quick response!

@jmarcelino Sorry for late answer.Yes...packet length extension it will be great if we can configure.

@jmarcelino

Not sure if this could be a possible solution to writing to characteristics, can anyone help me please? https://devzone.nordicsemi.com/f/nordic-q-a/8162/ble-driver-python-concurrent-notifications

Got the issue sorted out myself. The values are documented in the esp-idf: https://github.com/espressif/esp-idf/blob/master/components/bt/bluedroid/api/include/esp_gatt_defs.h#L267 just set the values corresponding to your needs. Be sure to set both permissions and properties. Example: The below characteristic supports only READ and NOTIFY: service.characteristic(uuid=0x2001, permissions=(1<<0), properties=(1 << 1) | (1 << 4), value=0)