decoder web app for Sensor Logger

[mhaberler]

the Sensor Logger app can record BLE advertisements but has a limited set of decoders

I had CC build a web app based on the WASM module just published -- all in-browser, no backend required

branch: https://github.com/mhaberler/decoder/tree/sensorlogger-decoder-webapp

example logfiles from iOS and Android to test yourself are here

[1technophile]

were you able to scan BLE advertisements with the app or just decode ?

[mhaberler]

this is strictly a file-based decoder

In Sensor Logger, select Bluetooth devices, record, export log as JSON (sample files under sensorlogs/* were produced this way)
then upload into the app, download the decorated result

WebBLE: I tried in the past and browser support was disappointing - so did not even try here

It might work with Chrome though by now, maybe worth an attempt

[mhaberler]

WebUSB support is a bit better than WebBLE so a dongle-based approach might work better

the nRF sniffer might be a start, and there are several related projects including an open source sniffer rewrite

not elegant but possibly larger footprint

[1technophile]

OpenMQTTGateway supports serial already, Theengs Decoder could integrate a flasher of a BLEtoSERIAL configuration, push this to the browser, decode and display the available sensors for the user

[mhaberler]

oh was not aware of that - is that a stock config? like the nodemcuv2-serial ?

that'd be a very cool way to do it and cost next to nothing - you mean like using esp-web-tools or esptool-js?

@Jason2866 now what the world needs is a scriptable version of https://github.com/Jason2866/WebSerial_ESPTool - detect CPU, fetch the right firmware, flash, done

nah, just joking

[mhaberler]

@1technophile can you point me to an OMG setup which you had in mind? I'd want to try the dongle approach

[1technophile]

here is an example with a C3:

[env:serialtest]
platform = ${com.esp32_platform}
framework = arduino, espidf
board = esp32-c3-devkitm-1
board_build.partitions = partitions/min_spiffs.csv
lib_deps =
  ${com-esp32.lib_deps}
  ${libraries.ble}
build_flags = 
  ${env.build_flags}
  ${com-esp32.build_flags}
  '-DZgatewayBT="BT"'
  '-DDEFAULT_OFFLINE=1'
  '-UZwebUI="WebUI"'
  '-DCHECK_OTA_UPDATE=false'
  '-DUSE_ESP_IDF=true'
  '-DZgatewaySERIAL="SERIAL"'
  '-DDEFAULT_SERIAL=1'
  '-DSERIALtoMQTTmode=1'
  '-DSERIAL_UART=1'
  '-DSERIALBaud=230400'
  '-DSERIAL_RX_GPIO=19'
  '-DSERIAL_TX_GPIO=18'

[mhaberler]

brute-forced with CC (builds - untested), branch development

[env:serialtest]
platform = ${com.esp32_platform}
framework = arduino, espidf
board = esp32-c3-devkitm-1
board_build.partitions = partitions/min_spiffs.csv
board_build.embed_txtfiles =
    managed_components/espressif__esp_insights/server_certs/https_server.crt
    managed_components/espressif__esp_rainmaker/server_certs/rmaker_mqtt_server.crt
    managed_components/espressif__esp_rainmaker/server_certs/rmaker_claim_service_server.crt
    managed_components/espressif__esp_rainmaker/server_certs/rmaker_ota_server.crt
lib_deps =
  ${com-esp32.lib_deps}
  ${libraries.ble}
build_flags =
  ${env.build_flags}
  ${com-esp32.build_flags}
  '-DZgatewayBT="BT"'
  '-DDEFAULT_OFFLINE=1'
  '-UZwebUI="WebUI"'
  '-DCHECK_OTA_UPDATE=false'
  '-DUSE_ESP_IDF=true'
  '-DZgatewaySERIAL="SERIAL"'
  '-DDEFAULT_SERIAL=1'
  '-DSERIALtoMQTTmode=1'
  '-DSERIAL_UART=1'
  '-DSERIALBaud=230400'
  '-DSERIAL_RX_GPIO=19'
  '-DSERIAL_TX_GPIO=18'
  '-DBLEDecoder=false'
  '-DNO_INT_TEMP_READING=true'

[mhaberler]

got the dongle to work, will extend my web decoder to read from it

is the following output format the one I should work from

like match on and strip N: [ OMG->SERIAL ] data sent: ?

or did I twist some flag too high?

T: Creating BLE buffer
N: BT Device detected: 3C:2E:F5:69:84:2C
T: getDeviceByMac 3C:2E:F5:69:84:2C
T: Get services data number: 1
T: Converted service data (7) to 440062011a3a00
T: Service data: 440062011a3a00
T: Service data UUID: 0xfcd2
T: Origin: /BTtoMQTT/3C2EF569842C
T: Enqueue JSON
T: Queue length: 1
T: Dequeue JSON
T: BUS Msg origin: /BTtoMQTT/3C2EF569842C
T: XtoSERIAL
N: [ OMG->SERIAL ] data sent: {"id":"3C:2E:F5:69:84:2C","mac_type":0,"adv_type":0,"name":"SBBT-002C","manufacturerdata":"a90b0109000b01000a2c8469f52e3c","rssi":-91,"servicedata":"440062011a3a00","servicedatauuid":"0xfcd2","origin":"/BTtoMQTT/3C2EF569842C"}

[mhaberler]

well.. the dongle scanner works:

[mhaberler]

try at https://cloud.mah.priv.at/apps/theengs-decoder/

[1technophile]

Nice! I should include the default build in the next release so that we can serve it as a BLE serial USB driver

[mhaberler]

make me understand: web app would connect via WebBLE, OMG would report scan results that link?

[1technophile]

OMG should have a BLEtoSERIAL build in the catalog of environment. This build could be used by project like the decoder to :

1. Push it to an ESP32
2. Connect to the ESP32 to retrieve the BLE advertisements
3. Web app decode the advertisement and display them

[mhaberler]

while I was at it, I added support for the nRF Sniffer dongle - will be autodetected

[mhaberler]

I added direct WebBluetooth scanning, but as expected it's a failure
enable with https://cloud.mah.priv.at/apps/theengs-decoder/?webble=true