Skip to content
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

Timestamp derived data does not cater for source data going stale #76

Open
marcobergman opened this issue Feb 17, 2021 · 0 comments
Open

Comments

@marcobergman
Copy link

When one of multiple sources for a derived value goes stale (does not receive updates anymore), but the other sources still update, the derived data is still calculated with fresh timestamps, although it is based on old sensor values, so to speak.

This would become an issue when data displays rely on timestamps to decide whether to give an indication of stale data, e.g. crossed out or empty display.

IMHO the timestamp of a derived value should be the minimum of the timestamps of all source values.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant