Publish processed values instead of raw sensor data about esphome-core HOT 3 CLOSED

That's exactly what sensor filters are for in esphomelib 💪. They pre-process sensor values in order to decrease network traffic and put less pressure on Home Assistant's state machine.

I don't know the exact thresholds for your setup, but something like this might work:

auto o = App.make_ultrasonic_sensor(...);
o.mqtt->clear_filters();
o.mqtt->add_lambda_filter([&](float value) -> Optional<float> {
  if (value > 2.0f || isnan(value))
    // Returning an empty optional stops the value from ebing published.
    return Optional<float>();
  ‎return value;
});

(writing this on my phone, as my laptop doesn't have any power; might not compile as-is)

Sensor filters are only supposed to do some basic pre-processing though, and more sophisticated stuff should be done with template (binary) sensors in Home Assistant. Home Assistant's template engine is amazing and it would be very difficult to create a similar, complete system for esphomelib.

from esphome-core.

And with esphomeyaml this has just gotten a lot easier: https://esphomelib.com/esphomeyaml/components/sensor/index.html#sensor-filters 😀

from esphome-core.

Should be possible with the Template Binary Sensor now :) Closing ...

from esphome-core.