Spectre-Box - power feather, battery, glass display. 2xesp32 for triangulation

[djcas9]

Messing around with espectre and the power feather board for a three node triangulation and mapping dashboard. Includes stl files etc.

Power Feather: https://powerfeather.dev/

Source: https://git.djcas9.com/djcas9/spectre-screen

[francescopace]

This looks like a very interesting setup, thanks for sharing!

I’m curious to learn more about how you’re approaching the multi-node aspects of the system:
• How are you handling time and phase synchronization across the ESP32 nodes?
• Are the devices sharing a clock / oscillator, or are you compensating drift in software?
• Is CSI processed locally on each node or aggregated centrally before any spatial inference?

Also, do you have any early results or visualizations (e.g. heatmaps, tracks, or stability over time)? It would be great to understand what level of spatial consistency you’re seeing in practice.

Happy to dig deeper once there are more details.

[djcas9]

@francescopace

1. Ugly and basic LTF - lowpass and hampel

time:
  - platform: homeassistant
    id: home_assistant_time

# Synchronize reporting intervals to the same 100ms clock edge
interval:
  - interval: 100ms
    then:
      - logger.log: "Syncing data report..."

espectre:
  id: espectre_csi
  movement_sensor:
    name: "Node Movement Score"
  lowpass_enabled: true
  lowpass_cutoff: 11.0
  hampel_enabled: true

sensor:
  - platform: filter
    name: "Main Node Smoothed Score"
    entity_id: sensor.main_movement_score
    filters:
      - filter: time_simple_moving_average
        window_size: "00:00:05"
        precision: 2

A lot of this wont be turn key as it will be using the floorplan component in HA too.

Still testing everything

2. still working on that packet, sntp.. or some other jitter filter..

3 Each node and in HA

Re: viz.. not yet - its' soooo bad at the moment.. but working on a metal gear solid style enemy radar display.

It's going to be very basic and who knows if I can even get it workign the way i want.. but for some reason I need to see this working.. so i'm going to continue and try.

rough template for x/y

template:
  - sensor:
      - name: "Radar X"
        state: >
          {% set s1 = states('sensor.main_smoothed') | float(0.1) %}
          {% set s2 = states('sensor.node_1_smoothed') | float(0.1) %}
          {% set width = 5.0 %} 
          {{ (( (10/s1)**2 - (10/s2)**2 + width**2 ) / (2 * width)) | round(2) }}
      - name: "Radar Y"
        state: >
          {% set s1 = states('sensor.main_smoothed') | float(0.1) %}
          {% set s3 = states('sensor.node_2_smoothed') | float(0.1) %}
          {% set height = 4.0 %}
          {{ (( (10/s1)**2 - (10/s3)**2 + height**2 ) / (2 * height)) | round(2) }}

will it be close to accurate.. nah.. but for fun it will work for me.