Retry Calibration with AHT20 command on failure #19
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.
If try-except around legacy calibrate command fails, try to send new one instead afterwards.
Addressing #17 and possibly #18 as well
Moved try-except from PR #16 doesn't work with the latest AHT20s (at least the ones I have) but instead gives very cryptic OS error implying the device is not present. Found different first-byte to write for newer AHT20's and tried that (details in #17 ). Made updates that I think will work with AHT10 still as the execution path remains unchanged from before, but retries if that fails.
Tested on my setup (details in #17) and works great (takes the
calibration_failed
path, then calibrates and succeeds).