Advertsing

[tcpipchip]

My Linux app did a ble connect to the ESP32-S3 and getting notify packages.

Now i can detect the movement using the BLE.

Is that a good practice ?

Or will i have CSI problems ?

And is there a BLE characterist command that i can send to esp32-s3 resets/calibrate to a enviroment person free ?

Am I required to calibrate it regularly? or only the first time of instalation ?

Please give me some important tips :)

Thank you!!!!!!!!!!!

[francescopace]

Hello @tcpipchip, great question, and you’re actually the first person to ask about this specific use case.

From your description, I’m not completely sure whether your Linux application is using ESPectre’s custom BLE telemetry/control interface directly, or if it is simply connecting to the ESP32-S3 over BLE and subscribing to notifications from another service.

For context, ESPectre already includes a lightweight BLE protocol that was originally implemented for The Game, where a browser can communicate with the ESP32 in real time.

Documentation:

• Setup Guide
• The Game BLE protocol

The current BLE interface is designed for:

• Telemetry notifications → movement + threshold updates
• Sysinfo characteristic → text-based system information (threshold, window, detector, etc.)
• Threshold settings (SET_THRESHOLD:X.XX)

There is currently no BLE command for recalibration or reset.

Regarding your other questions:

• Using BLE notifications for movement telemetry is a supported use case.
• BLE activity should not inherently interfere with CSI processing. There is some additional radio overhead, but the BLE channel was designed to coexist with the Wi-Fi CSI pipeline.
• If BLE is not needed, disabling it does reduce overhead slightly, but using it for telemetry is perfectly valid.

Calibration notes:

• In MVS mode, ESPectre performs automatic calibration at every boot. During this phase, the environment should remain still for roughly 10 seconds.
• In ML mode, this calibration step is skipped entirely.
• For runtime recalibration, ESPectre currently exposes the Home Assistant entity (switch.espectre_calibrate)

Regular scheduled recalibration is usually unnecessary. The initial calibration is generally sufficient, and recalibration is only recommended when the environment changes significantly, for example:

• the sensor is moved
• the AP/router is moved
• furniture or room layout changes
• RF conditions change substantially

If useful, I can also add a dedicated BLE recalibration command in a future update.