-
-
Notifications
You must be signed in to change notification settings - Fork 32.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add zeroconf support for velux integration #112451
Closed
Closed
Changes from 12 commits
Commits
Show all changes
13 commits
Select commit
Hold shift + click to select a range
bef727b
Add zeroconf support
pawlizio 9638337
bump pyvlx
pawlizio f958c57
update manifest
pawlizio 7f4c0cc
Add zeroconf tests
pawlizio 48317b5
update typing
pawlizio 7e42b3f
update imports
pawlizio f1b2010
update config_flow
pawlizio 5a8694b
fix fixxtures
pawlizio bc89fbe
remove block_till_done
pawlizio e9f02c3
bump pyvlx
pawlizio 27a7eb8
Fix tests
pawlizio 759168f
Add discovery step
pawlizio d499499
Remove issue tracker from manifest
pawlizio File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,10 +1,18 @@ | ||
{ | ||
"domain": "velux", | ||
"name": "Velux", | ||
"codeowners": ["@Julius2342", "@DeerMaximum"], | ||
"codeowners": ["@Julius2342", "@DeerMaximum", "@pawlizio"], | ||
"config_flow": true, | ||
"documentation": "https://www.home-assistant.io/integrations/velux", | ||
"integration_type": "hub", | ||
"iot_class": "local_polling", | ||
"issue_tracker": "https://github.com/Julius2342/pyvlx/issues", | ||
pawlizio marked this conversation as resolved.
Show resolved
Hide resolved
|
||
"loggers": ["pyvlx"], | ||
"requirements": ["pyvlx==0.2.21"] | ||
"requirements": ["pyvlx==0.2.23"], | ||
pawlizio marked this conversation as resolved.
Show resolved
Hide resolved
|
||
"zeroconf": [ | ||
{ | ||
"type": "_http._tcp.local.", | ||
"name": "velux_klf_lan*" | ||
} | ||
] | ||
} |
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
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
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
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
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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,4 @@ | ||
"""Constants for the Velux tests.""" | ||
PASSWORD = "NotAStrongPassword" | ||
HOST = "127.1.1.1" | ||
HOSTNAME = "VELUX_KLF_LAN_ABCD" |
Oops, something went wrong.
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm not sure about this, do we really need both user triggered and automatic discovery?
Maybe we could add functionality to the Home Assistant
zeroconf
integration which allows fetching services already discovered for a services, similar to what we support for bluetooth:core/homeassistant/components/dormakaba_dkey/config_flow.py
Line 63 in 4ff6453
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think adding that to zeroconf would be helpful long term. Right now users tend to ignore discoveries and than can’t find the integration and than open issues if they have no way to add it manually once it’s ignored. If they do discover that and unignore it, a restart is generally required to find it again.
When we solve these issues we probably don’t need manual adding anymore but we are still a ways off from a solution there. In the mean time it makes sense to implement manual adding via a user flow
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
IMHO, we shouldn't add this here; and instead solve the issue at hand in core instead.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I agree. This PR could drive the needed change in the
zeroconf
integration. @pawlizio Is this something you could look into? You can contact me on Discord if it's not clear where to start.