Restart after timeout implemented #11
Open
Conversation
This file contains 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
I use the Meteostick over a long USB connection (Meteostick <-10m-> Raspberry Pi4) and keep having the problem that the Meteostick sporadically no longer sends any data. I switched an active USB over RJ45 Ethernet extender adaptor in between which, however, did not solve the problem. As a solution to the problem, I have adapted the meteostick.py file and implemented a reset if a timeout is recognized when receiving. Communication with the Meteostick works after this code change. The timeout reset action is entered in the raspberry system log.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
I use the Meteostick over a long USB connection (Meteostick <-10m-> Raspberry Pi4) and keep having the problem that the Meteostick sporadically no longer sends any data. I switched an active USB over RJ45 Ethernet extender adaptor in between which, however, did not solve the problem. As a solution to the problem, I have adapted the meteostick.py file and implemented a reset if a timeout is recognized when receiving. Communication with the Meteostick works after this code change. The timeout reset action is entered in the raspberry system log.