changed get_os_temperature() to accommodate the AWR129, which has an extra decimal digit for >100˚ C #2446
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.
As a BBQ thermometer, the AWR129 reads higher temperatures than a weather thermometer ever would. The hundreds digit appears, right in order, in the low half of the fifth byte of the message. Since I don't know whether the THR228N and other similar devices handled by the protocol decoder might have something besides "0" in that spot, I've made the code conditional, so that only the AWR129 will be affected.
I tested this in my oven above 200˚C, and the readings increased smoothly at each multiple of 100, rather than wrapping back to zero as it did before this change.