Feels Like sensor updates multiple times when input sensors are updated at the same time #86
Description
Is your feature request related to a problem? Please describe.
Yes. My temperature and humidity sensors update at the same time, but the calculation for the Feels Like Temperature happens twice, back-to-back. This causes strange spikes in the history where there are two values for the same point in time (one value is calculated with the current temperature and old humidity, the other is with current values for both)
Describe the solution you'd like
I'm not sure what the best solution is. Options are:
- add an optional 1-second delay before calculating, and ignore any changes during that time (i.e. temp updates, triggering the calculation; humidity updates during the delay but does not trigger an additional calculation; sensor updates with 1-second-old temp and humidity values)
- allow users to specify sensors to use as triggers. For example in my case I could have it only update the Feels Like Temperature when the humidity sensor is updated (but not necessarily changed).
- allow users to specify a minimum age for sensor data. When triggered, check that all input sensors have been updated within that time frame, or don't update the Feels Like Temperature (or mark it unavailable)
Describe alternatives you've considered
I have not been able to find an alternative that resolves this issue.
Additional context
I have automations that trigger on a comparison of two Feels Like Temperature sensors, and it is triggered twice as often as it needs to be, with bad data for the first of each trigger. I can set it to restart mode but it still feels like there should be a solution to the sensors getting updated with old data half the time.