@tasaf1 Please refer to the file_server example which also features file uploading onto flash (SPIFFS partition) : https://github.com/espressif/esp-idf/blob/master/examples/protocols/http_server/file_serving/main/file_server.c#L283 There is a limit of 200KB on the upload file size. Increase it to al...

For the BLE notification case, it should be a matter of adding a new endpoint (characteristic) and just doing the subscription/notification with payloads from calling `protocomm_req_handle`? For this to work the notify bit will have to be enabled for the characteristic corresponding to your endpoin...

Thanks for showing interest! Presently protocomm provides out of the box support for transport over BLE and HTTP Server/SoftAP, though each of these implementations assume simple server-client type scenario with the device(ESP32) hosting the server. Since your requirement is that of a mixed approach...

Sorry about the delayed reply. The port configuration works and can be tested using examples/protocols/http_server/advanced_tests . Here's how the configuration is set: httpd_handle_t hd; httpd_config_t config = HTTPD_DEFAULT_CONFIG(); config.server_port = 1234; ESP_ERROR_CHECK(httpd_start(&hd, &con...

You also need to decrypt the response data in the python script. That may seem unnecessary for your use case, but without that the encryption engine will not update the internal AES-CTR security counter on the client side (See https://docs.espressif.com/projects/esp-idf/en/latest/api-reference/provi...

According to the error log: That means your data is for some reason arriving on the wrong endpoint "prov-config", which is at 0xFF52. Check if that's not the case

It's actually due to BlueZ keeping the old device data in cache. To refresh the cache, find the cache folder corresponding to your ESP32 under "/var/lib/bluetooth/<MAC ID of your Bluetooth controller>/<MAC ID of ESP32>" and remove it. Another way is to disable caching from "/etc/bluetooth/main.conf"...

An easy way of handling various HTTP server errors will soon be available. So one can register an error handler for say 404 error, which is generated when requested URI is not found. Till this features is merged you could use the wildcard matching scheme to handle requests to all URIs "/*" other tha...

@JSchaef Seems like your IDF_PATH is not set correctly. Could you make sure that's not the case

It may be too late for an answer, but URI wildcard matching scheme was recently added to esp_http_server. See the file server example offered by esp_http_server https://github.com/espressif/esp-idf/tree/master/examples/protocols/http_server/file_serving. This demonstrates serving files kept on SPIFF...