Update docs to fix mixed use of DHT12 and DHT22 #4
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
UncleGrumpy
approved these changes
Feb 1, 2025
UncleGrumpy
left a comment
UncleGrumpy
left a comment
There was a problem hiding this comment.
This look correct to me. Thanks for the fix.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
The docs mention DHT 12 in some places while I assume DHT22 is meant. Altough DHT11, DHT12 and DHT22 are al three valid types, the code only has a type option taking dht_11 or dht_22
atomvm_dht/src/dht.erl
Line 39 in f057c44