[insteon] Fix imeter solo product first record location #18075
+1
−1
Conversation
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
Signed-off-by: Jeremy Setton <[email protected]>
|
This pull request has been mentioned on openHAB Community. There might be relevant details there: |
jlaur
added
the
additional testing preferred
|
@jsetton - I added the "additional testing preferred" after checking your recent posts in the referenced thread. However, I can't keep up with the thread, so please remove the label once the testing has been confirmed and the PR is ready to be merged. |
|
The testing has been confirmed. |
jsetton
removed
the
additional testing preferred
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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 change corrects the first database record location configuration for iMeter Solo products.
This fix should be backported as the database verification for iMeter Solo products is currently failing leaving the thing in pending configuration status.