Fixes duplicated / missing recent temperature datapoints caused by ata_sct_temperature_history
#825
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This commit makes two modification to smart temperature logging:
This is one of the solution mentioned in #824.
Also, this PR / issue should be independent from #494 / #557. That issue seems to stem from unreliable
ata_sct_temperature_history, and the solution proposed in the PR was to add a switch to turn offata_sct_temperature_historysampling. This PR tries to fix some logging issue when (semi-)reliableata_sct_temperature_historyis reported without completely turning it off.