{{ message }}
Repository navigation
Show a connection error for an unsupported DSMR serial port URL - #184561
Merged
Merged
Conversation
Contributor
Contributor
There was a problem hiding this comment.
Copilot review overview
🟢 Approval recommended
The targeted exception handling is correct and covered by an appropriate regression test.
Review effort: Balanced
Findings: None
What changed in this PR
Handles unsupported DSMR serial URL schemes as connection failures instead of unexpected config-flow errors.
Changes:
- Catch
serialx.SerialExceptionduring validation. - Test both
OSErrorand unsupported URI schemes.
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
epenet
approved these changes
Oct 7, 2026
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
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.

Breaking change
Proposed change
Serial connections for DSMR go through serialx, which also accepts URLs such as
socket://host:portas the port. For a URL with a scheme it doesn't support, likehttp://192.168.1.20:23, it raisesUnknownUriScheme, aSerialExceptionthat is not anOSError. The config flow only handledOSError, so the flow crashed and showed "Unknown error".The connection validation now also handles serialx's
SerialException, so the user gets the regular "Failed to connect" error and can correct the port. serialx is already a dependency ofdsmr-parser, which uses it for the connection.Type of change
Additional information
Checklist
ruff format homeassistant tests)If user exposed functionality or configuration variables are added/changed:
If the code communicates with devices, web services, or third-party tools:
Updated and included derived files by running:
python3 -m script.hassfest.requirements_all.txt.Updated by running
python3 -m script.gen_requirements_all.To help with the load of incoming pull requests: