How to slow down refresh frequency of Everything Presence Lite device?

ESPHome
1

Just have my first ESP-Home device: an Everything Presence Lite sensor.
I installed it with succes.

Now I notice a huge amount of incoming data, several updates per second, which gives a huge increase of my HA database, in three days time, it is now leading in the max count of records in my database.
I wonder how to decrease this amount of data to, per example, one update per second.

Is something like this possible?

I saw some filter options in the ESPhome site, but I just like some advise here, since I am a newbee in ESPhome.

Thanks!!

2 
    filters:
      - sliding_window_moving_average:
          window_size: 15
          send_every: 15

this will publish data every ~ 15sec.

or, if the component is a polling one, you can use update_interval.

njoy!

3

@oxynatOr Thanks for your reply. This is going to help.

Unfortunately, I have a next question: Where do I have to add these lines?
The base yaml is very short and points to github:

substitutions:
  name: everything-presence-lite
  friendly_name: Everything Presence Lite
packages:
  EverythingSmartTechnology.Everything_Presence_Lite: github://everythingsmarthome/everything-presence-lite/everything-presence-lite-ha.yaml@main
esphome:
  name: ${name}
  name_add_mac_suffix: false
  friendly_name: ${friendly_name}
api:
  encryption:
    key: xxxxxxxxxxxx


wifi:
  ssid: !secret wifi_ssid
  password: !secret wifi_password
4

have you try this?

Offsets for mmWave

The mmWave sensor has an adjustable timeout period inside of Home Assistant using the mmWave Off Latency control. The value is measured in seconds and the default is for 15 seconds. I generally wouldn’t recommend setting this below 10s to help with false clearing.

5

That is mainly Everything Presence One info, as stated on top. No mmWabe setting available for EPL, Everything Presence Lite :slightly_frowning_face:

6

The Dokus even say:

This page is not up to date yet and still contains screenshots from the Everything Presence One, rather than the Lite - working on updating it very soon!

i’m sorry. i thought its the lite, like the text is saying :frowning:

u are 100% sure you don’t have anything in Home-Assistant?
you need to follow the doku step by step, that means the device must be added in Home-Assistant under ESPHome.

Just to make sure because you say it the first device you have

Editing all the YAMLS is such a task :frowning:

7

@oxynatOr

These are all the input settings, The 10 hidden ones are for Zone3 and Zone4, so no mmWave settings to change anything fro frequency.

image
image391×906 30.7 KB

Am i going to get the yaml local and try to implement your filters settings.

8

Now I have this: (one example)

sensor:
  - platform: template
    name: "Target 1 X"
    id: target1_x
    accuracy_decimals: 0
    unit_of_measurement: 'mm'
    state_class: measurement
    device_class: distance
    filters:
      - heartbeat: 5s

Or is update_interval a better solution here?

9

ah wait…

there is globe you can set.

so you need to conifg a Input-Helper inside HA. And place the lines inside the yaml of your ESP-Device. And then use the service tab.

or, you can set it after the boot.

  on_boot:
    priority: -100.0
    then:
      - globals.set:
          id: mmwave_update_time
          value: 5000