-
-
Notifications
You must be signed in to change notification settings - Fork 3.6k
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
[pentair] Many enhancements since original commit, including #13485
Conversation
If you have created one PR for each new feature/enhancement rather than one enormous PR of almost 8000 new lines, you will have encouraged a faster review. |
The majority was reviewed in this PR: [https://github.com//pull/8844]. Many of the changes were as a result of that review and many hours were spent to address the comments (even when they were just stylistic comments). Unfortunately, github got out of sync with my branch and the suggestion was to submit a new review - where I ran out of time. As a recent comment was made on removing gnu.io and the Pentair binding was listed as not having made the change, I decided to resubmit now. |
@fwolter was apparently involved in the previous PR, I hope he will continue with this new PR. |
Is this ready for review again? You added the work in progress label? |
After the review process for a different binding (juicenet), I decided to take a once over the code and address some of the same types of edits suggested in that review. Its taking a little longer than anticipated and in the process cleaning up some of the code. It will probably be several days before i'm done, but it should "hopefully" make your review much simpler. |
@fwolter, I've submitted a new version. There are quite a few changes to clean up and restructure the code. I think it reads much better and fixed a lot of the style issues. Unfortunately, the changes were fairly large in number. |
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 reviewed the readme and the first code file for now. Here is my feedback.
There are some checkstyle warnings left. You could take a look at target/code-analysis/report.html
after building it with mvn clean install
.
There are some compiler warnings about null access left. You could take a look at mvn clean install
. To fix these, you need to store the field to a local variable and do the null check on that.
| tank1 | Number | R | Tank 1 level. | | ||
| tank2 | Number | R | Tank 2 level. | |
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.
Is this in percent?
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.
No, these are values between 1-7. I added this in the description.
| mode1 | Number | R | Mode 1 status. | | ||
| mode2 | Number | R | Mode 2 status. | |
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.
Do you know what this is about?
(byte) ControllerCommand.SET_CIRCUIT_SWITCH.send, (byte) 0x02, (byte) circuit, | ||
(byte) ((state) ? 1 : 0) }; | ||
|
||
logger.debug("setCircuitSwitch: {}, {}", circuit, state); |
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.
Can this message be replaced by using the debugger? See point 4 https://www.openhab.org/docs/developer/guidelines.html#f-logging
|
||
logger.debug("setCircuitSwitch: {}, {}", circuit, state); | ||
if (!getWriter().writePacket(packet, ControllerCommand.SET_CIRCUIT_SWITCH.response, 1)) { | ||
logger.trace("setCircuitSwitch: Timeout"); |
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.
Logging. Same as above. Please check all.
Hi @jsjames! Can you fix the review comments and merge conflicts? |
This pull request has been mentioned on openHAB Community. There might be relevant details there: https://community.openhab.org/t/pentair-serial-connection-not-working/149860/5 |
790cbf0
to
2ba923f
Compare
@jsjames can you resolve the conflicts? |
2f4d091
to
ff99c67
Compare
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.
Might come back to some parts later on. Finished all files. Can you also update your branch to main as that makes it easier to checkout and build locally agains current main.
...inding.pentair/src/test/java/org/openhab/binding/pentair/internal/PentairHeatStatusTest.java
Outdated
Show resolved
Hide resolved
...ab.binding.pentair/src/test/java/org/openhab/binding/pentair/internal/PentairParserTest.java
Outdated
Show resolved
Hide resolved
...ab.binding.pentair/src/test/java/org/openhab/binding/pentair/internal/PentairParserTest.java
Outdated
Show resolved
Hide resolved
bundles/org.openhab.binding.pentair/src/main/resources/OH-INF/thing/intellichlor.xml
Show resolved
Hide resolved
...ir/src/main/java/org/openhab/binding/pentair/internal/discovery/PentairDiscoveryService.java
Outdated
Show resolved
Hide resolved
...air/src/main/java/org/openhab/binding/pentair/internal/handler/PentairControllerHandler.java
Outdated
Show resolved
Hide resolved
...air/src/main/java/org/openhab/binding/pentair/internal/handler/PentairControllerHandler.java
Outdated
Show resolved
Hide resolved
...air/src/main/java/org/openhab/binding/pentair/internal/handler/PentairControllerHandler.java
Outdated
Show resolved
Hide resolved
@jsjames are you able to proceed with this PR? |
Yes, I will update the PR within the coming week.
…On Fri, May 31, 2024 at 1:09 AM lsiepel ***@***.***> wrote:
@jsjames <https://github.com/jsjames> are you able to proceed with this
PR?
—
Reply to this email directly, view it on GitHub
<#13485 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAHUUTOFBICH4UYWTCBQOUTZFAV35AVCNFSM6AAAAAAQ4C6B46VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCNBRGQ2DGNJQGY>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
167810d
to
3660df8
Compare
Signed-off-by: Jeff James <jeff@james-online.com>
Signed-off-by: Jeff James <jeff@james-online.com>
Signed-off-by: Jeff James <jeff@james-online.com>
@isiepel, should be ready to go. |
As there is only one milestone left with just a few days before stable release, i hope you can confirm this PR is well tested and confirmed by atleast some users to work well. If so, i can merge this. Otherwise i would prefer to postpone a merge to after the stable release. |
I have been using this for awhile and have shared built version for others to try over time. I can’t say it was exhaustively tested by others, but in my home system it works 1000% better than original. Having said that, if you want to do right after the the milestone, that is fine with me as well.
… On Jun 10, 2024, at 1:11 PM, lsiepel ***@***.***> wrote:
nu.io dependency. Reworked some of the state changes in the basebridgehandler.
As there is only one milestone left with just a few days before stable release, i hope you can confirm this PR is well tested and confirmed by atleast some users to work well. If so, i can merge this. Otherwise i would prefer to postpone a merge to after the stable release.
—
Reply to this email directly, view it on GitHub <#13485 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAHUUTKSLBLBFHNL22UN4PLZGYB5ZAVCNFSM6AAAAAAQ4C6B46VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCNJZGE4TQNJSHE>.
You are receiving this because you were mentioned.
|
That means it won’t be in 4.2 stable. It will be included in first 4.3 milestone. If that is ok, I’ll merge it later, but would be nice if we can get some feedback in the next two weeks and get it in 4.2 |
Can you resolve the conflict? I will then merge this |
This conflict was introduced when the PR to update the spelling in a log message. That log message no longer exists which caused the conflict. You can just overwrite the change in the master when you checkin this PR. |
I'm not comitting changes to this PR, as by then i can't merge this. |
Okay - i was hoping you could just overwrite the previous accepted change. I'm not a git expert, so I'll try to figure out how to resolve the conflict. |
Signed-off-by: jsjames <jeff@james-online.com>
Now this is merged, can you create an upgrade notice for the breaking change? |
I added a [4.3.0] tag, hopefully that was correct. |
…#13485) * Updated per design review comments * Added unitHint to Dimensionless items Signed-off-by: Jeff James <jeff@james-online.com>
…#13485) * Updated per design review comments * Added unitHint to Dimensionless items Signed-off-by: Jeff James <jeff@james-online.com> Signed-off-by: Patrik Gfeller <patrik.gfeller@proton.me>
…#13485) * Updated per design review comments * Added unitHint to Dimensionless items Signed-off-by: Jeff James <jeff@james-online.com>
…#13485) * Updated per design review comments * Added unitHint to Dimensionless items Signed-off-by: Jeff James <jeff@james-online.com>
Closes 13485