Fix frequent error "Exception in callback _SelectorDatagramTransport.… #2049
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.
Problem
The localtuya custom component’s UDP discovery handler was logging a high volume of errors:
Although these errors did not affect functionality, they flooded the logs with hundreds of thousands of entries per day, making debugging difficult and increasing log storage.
Solution
This PR improves the datagram_received method to:
Gracefully handle decryption failures by attempting to decode raw data
Handle decoding errors without exceptions
Validate that decrypted data is JSON-formatted before parsing
Log warnings for malformed or unexpected packets instead of raising exceptions
These changes significantly reduce noisy error logs and improve the stability and clarity of localtuya's UDP discovery.