-
Notifications
You must be signed in to change notification settings - Fork 13
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Output artifacts when input value becomes unavailable #30
Comments
You can filter all the values with templates! All the fields can handle templating. You could do this, but I agree that the controller should handle this. Tks |
How would one do that with a template? Is there some way to use previous? |
You could turn off the pid if the variable of the input is unavailable. But I agree that the pid should handle this! I'll put it on my to-do list. |
Something that might help other folks, if you're using ESPHome, you can filter out esphome:
name: woodstove
# ...
sensor:
- platform: max6675
# ...
filters:
filter_out: nan
|
Did a little digging around select state_id, entity_id, state, last_updated from states where entity_id = "sensor.woodstove_flue_temperature" and last_updated < "2022-10-19 00:18:30" order by last_updated desc limit 5;
Looks like that gap is when |
In the process of trying this out - platform: template
sensors:
woodstove_flue_temperature_filtered:
friendly_name: "Woodstove Flue Temperature Filtered"
unit_of_measurement: "°F"
value_template: >
{% if states('sensor.woodstove_flue_temperature') in ['unavailable', 'unknown', 'none'] %}
{{ states('sensor.woodstove_flue_temperature_filtered') }}
{% else %}
{{ states('sensor.woodstove_flue_temperature') }}
{% endif %} |
If an input value becomes unavailable,
ha-pid-controller
defaults to 100% output. It would be nice to either handle this inha-pid-controller
or provide documentation for how to filter these valuesThe text was updated successfully, but these errors were encountered: