-
Notifications
You must be signed in to change notification settings - Fork 494
Support greater profiling for parent/child switch devices #2153
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
Closed
Closed
Changes from all commits
Commits
Show all changes
8 commits
Select commit
Hold shift + click to select a range
a2397f0
add support for re-profiling parent switch devices and for profiling …
hcarter-775 255334a
ignore electrical sensor dt
hcarter-775 f3f4030
remove print
hcarter-775 3525fe2
update the logic to be cleaner
hcarter-775 aef53f3
gate another profile type
hcarter-775 349e9ef
Merge branch 'main' into profile-energy-child-plugs
hcarter-775 40a8983
extend energy profiling logic
hcarter-775 f4892df
fix small issue, add test
hcarter-775 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 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
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
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
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
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.
This loop makes an assumption that the nth electrical ep will correspond to the nth switch ep, but what if only some eps support electrical power/energy, and some don't? For example, a 6 plug device with 3 outlets that support power and 1 that supports power and energy, one that supports only energy, and one that supports none. I would assume this is not a likely scenario, but a simpler combination of these factors could happen in a real device.
Overall it seems like it should not be on us as the client to try to make assumptions about which electrical endpoint corresponds to which switch endpoint. Shouldn't the electrical device type that is relevant to a given switch/plug be combined on the same endpoint? I might need to refresh myself on the spec for clarity, but it seems ambiguous if this convention is not used.