its not the full esp config but its the section related to the battery sensors that are filling up the database fast
I used to also have this for reference voltage
# - platform: adc
# pin: VCC
# id: "VCC"
# name: "VCC"
# internal: true
# update_interval: 1s
# attenuation: auto
and before I had the esp32 with the ESP8266 it was something a bit different but I have lost the old configs now
the influx db grows at a reasonable rate with lots of 1 and 5 second data points while logging solar mppt trackers and over 100 aquarium temps, TDS and PSI sensors
but recorders db is 20x the size daily and most of that is pointing towards the battery sensor thats meant to just be keeping track of the voltage of each individual battery so I can catch a dead cell be for I have another 7v , 17v , 17v, 17v day
as you have said excluding will keep data going to influx I will give that a go
I really wish they would put long term data into a separate database, as I would like to keep the energy dash board backed up daily the rest that it logs does not matter as long as I have a few days worth backed up
it might have been a paste issue , going through the ESP’s now to see if one of them looks like that ,
so far they have been correct my guess is i touched my middle click on the wheel mouse and it just pasted it , its been extremely touchy while scrolling since the rubber fell apart
Excluding from the recorder does not effect influx db. To exclude in influx you must place it under the influx: heading in config.yaml, see exclude key