Add energy_monitoring quirk for L535E #1591
Draft
Conversation
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
fantandrea
commented
Oct 14, 2025
| for comp in components_raw["component_list"] | ||
| } | ||
|
|
||
| def _enable_device_quirks(self) -> None: |
Contributor
Author
There was a problem hiding this comment.
I couldn't make it static to be called in _parse_components so I called it just after to fix the self.components without touching the self.components_raw
|
There hasn't been any activity on this pull request recently. This pull request has been automatically marked as stale because of that and will be closed if no further activity occurs within 7 days. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Add a quirk to read the energy data from the L535E device.
According to the TP-Link Support (ref: TKID250908555 #63159), the values exposed in
get_emeter_dataare values computed based on the energy consumption specifications of the device as there is no physical sensor (that's the reason for the missingenergy_monitoringin the component list).TODO:
devtools.dump_devinfoto exportget_emeter_data