@prankousky wrote:
Hi everybody,
I used to have
influxdb
set up like thisinfluxdb: host: !secret influxdb_host port: !secret influxdb_host database: !secret influxdb_database username: !secret influxdb_username password: !secret influxdb_password ssl: false verify_ssl: false max_retries: 3 default_measurement: state include: entities: # (...) domains: # (...) tags: instance: prod source: hass
This does exactly what it should for, let’s say
binary_sensor
/input_boolean
entities. Their status changes, it gets logged. However, when I have something likesensor.temperature_printer
(in this case, aDS18B20
onESPHome
), the state might change by the minute (or even 6 times per minute or so), which generates a lot of data.Is there a way to limit this? I am looking for something in the likes of
# (...) include: entities: - entity: sensor.tempearature_printer interval: 2m # / 120s only_on_change: true
This is arbitrary yaml, but what I mean is: for entity
sensor.temperature_printer
log value every2m
; if value has not changed, don’t log it (otherwise do log it).Prior to ESPHome, I had every single sensor integrated via
zigbee2mqtt
, so I could just letnode-red
take care of this; however, I don’t think it is the best solution to generate automations to send changes from the ESPHome entities tomqtt
just so thatnode-red
can work with them. There ought to be a better solution. Is there and I just missed it?Thank you for your ideas
Posts: 1
Participants: 1