Do not automatically add emeter to iot strip #865
Merged
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
rytilahti
approved these changes
Apr 25, 2024
Member
rytilahti
left a comment
rytilahti
left a comment
There was a problem hiding this comment.
Let's give it a go and fix it later if need to be, it's more important to get the feature-based emeter sensors in the HA PR than whatever special handling we are going to need potentially for HS300.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
This fixes the current broken tests in #844 caused by the fixtures for
HS107(US)_1.0_1.0.8.jsonandKP400(US)_1.0_1.0.10.jsonhaving theemetervalue in the fixture but noget_realtimevalue. Other strips do not fail because they do not have theemetervalue in the fixture and theFakeIotProtocolcreates one for them.It seems that #299 introduced the adding of Emeter in the smart strip constructor (in commit c8ad99a) and this was added after #243 which adds the Emeter in the IoDevice
update()method so perhaps there is an implication to this change that I'm missing, although it seems_create_emeter_requestis no longer called anywhere so maybe that was a historical reason.N.B. The tests all pass with this PR.
Link to CI run on branch