Skip to content
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

Reenable Smarty integration #124148

Merged
merged 9 commits into from
Sep 4, 2024
Merged

Conversation

martinssipenko
Copy link
Contributor

Breaking change

Proposed change

Type of change

  • Dependency upgrade
  • Bugfix (non-breaking change which fixes an issue)
  • New integration (thank you!)
  • New feature (which adds functionality to an existing integration)
  • Deprecation (breaking change to happen in the future)
  • Breaking change (fix/feature causing existing functionality to break)
  • Code quality improvements to existing code or addition of tests

Additional information

This PR addresses/is related to:

Checklist

  • The code change is tested and works locally.
  • Local tests pass. Your PR cannot be merged unless tests pass
  • There is no commented out code in this PR.
  • I have followed the development checklist
  • I have followed the perfect PR recommendations
  • The code has been formatted using Ruff (ruff format homeassistant tests)
  • Tests have been added to verify that the new code works.

If user exposed functionality or configuration variables are added/changed:

If the code communicates with devices, web services, or third-party tools:

  • The manifest file has all fields filled out correctly.
    Updated and included derived files by running: python3 -m script.hassfest.
  • New or updated dependencies have been added to requirements_all.txt.
    Updated by running python3 -m script.gen_requirements_all.
  • For the updated dependencies - a link to the changelog, or at minimum a diff between library versions is added to the PR description.

To help with the load of incoming pull requests:

Copy link

@home-assistant home-assistant bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hi @martinssipenko

It seems you haven't yet signed a CLA. Please do so here.

Once you do that we will be able to review and accept this pull request.

Thanks!

@home-assistant home-assistant bot added new-integration small-pr PRs with less than 30 lines. labels Aug 18, 2024
@home-assistant home-assistant bot marked this pull request as draft August 18, 2024 09:02
@home-assistant
Copy link

Please take a look at the requested changes, and use the Ready for review button when you are done, thanks 👍

Learn more about our pull request process.

Copy link

@home-assistant home-assistant bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@home-assistant
Copy link

Hey there @z0mbieprocess, mind taking a look at this pull request as it has been labeled with an integration (smarty) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of smarty can trigger bot actions by commenting:

  • @home-assistant close Closes the pull request.
  • @home-assistant rename Awesome new title Renames the pull request.
  • @home-assistant reopen Reopen the pull request.
  • @home-assistant unassign smarty Removes the current integration label and assignees on the pull request, add the integration domain after the command.
  • @home-assistant add-label needs-more-information Add a label (needs-more-information, problem in dependency, problem in custom component) to the pull request.
  • @home-assistant remove-label needs-more-information Remove a label (needs-more-information, problem in dependency, problem in custom component) on the pull request.

@joostlek
Copy link
Member

Do you have a link to the new library?

Copy link
Member

@joostlek joostlek left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

https://github.com/martinssipenko/pysmarty2/blob/master/requirements.txt

Looks like we are pinning modbus, let's not do that and try to set a lower boundary so we can update modbus in HA without having to get the lib bumped at the same time

@home-assistant home-assistant bot marked this pull request as draft August 18, 2024 12:18
@martinssipenko
Copy link
Contributor Author

@joostlek sorry, this was my first day in python :)

I've made the changes you requested in the library and released them in v0.10.1. I also updated HA to point to this new smarty2 lib version.

@martinssipenko martinssipenko marked this pull request as ready for review August 19, 2024 04:55
@home-assistant home-assistant bot requested a review from joostlek August 19, 2024 04:55
@martinssipenko
Copy link
Contributor Author

@joostlek could you please take a look at this?

Copy link
Member

@joostlek joostlek left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It would also be awesome if you could pick up codeowner ship and maybe we can even migrate this integration to the config flow

@joostlek
Copy link
Member

joostlek commented Sep 4, 2024

Please don't merge dev into your branch, now I have to run the CI again and wait longer

@martinssipenko
Copy link
Contributor Author

@joostlek I’m okay with codeownership, it it okay if I change that is seperate PR?

Regarding config flow - I’ll check out what I can do about it.

@joostlek
Copy link
Member

joostlek commented Sep 4, 2024

Looks like this integration has some potential to be reworked using the config flow :) But yes, we can do the codeownership in a separate PR

@joostlek joostlek merged commit af51241 into home-assistant:dev Sep 4, 2024
36 of 38 checks passed
iloveicedgreentea pushed a commit to iloveicedgreentea/core that referenced this pull request Sep 4, 2024
* Reenable Smarty integration

* Updated codeowners to myself

* Revert "Updated codeowners to myself"

This reverts commit 639fef3.

* Upgraded pysmarty2 to version 0.10.1 which is not pinned to specific pymodbus version

* Update requirements_all.txt
@github-actions github-actions bot locked and limited conversation to collaborators Sep 5, 2024
@martinssipenko martinssipenko deleted the reenable-smarty branch September 13, 2024 16:48
@joostlek
Copy link
Member

@martinssipenko can you maybe send me a message on discord? :)

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants