Remove double use of entry, bump plugwise to v.1.7.4

[bouwew]

Summary by CodeRabbit

• Chores
  • Updated Plugwise integration to require plugwise package version 1.7.4 and bumped integration version to 0.57.3.
• Refactor
  • Simplified internal device management for Plugwise integration without affecting user experience.

[coderabbitai]

Walkthrough

This update refactors the PlugwiseDataUpdateCoordinator class by removing the need to pass the ConfigEntry parameter to its private methods _async_add_remove_devices and _async_remove_devices. Instead, these methods now use the instance's self.config_entry attribute directly. The logic for device management and registry updates remains unchanged, with only the method signatures and their call sites simplified to reduce redundancy. Additionally, the manifest.json file was updated to require version 1.7.4 of the plugwise package and increment the integration version to 0.57.3. The pyproject.toml was also modified to specify the license string directly as "MIT" instead of referencing a license file.

Changes

File(s)	Change Summary
custom_components/plugwise/coordinator.py	Refactored private methods _async_add_remove_devices and _async_remove_devices to remove the ConfigEntry parameter, updating internal references to use self.config_entry instead. Simplified method signatures and call sites accordingly.
custom_components/plugwise/manifest.json	Updated manifest to require plugwise package version 1.7.4 (from 1.7.3) and bumped integration version from 0.57.2 to 0.57.3. No functional changes.
pyproject.toml	Changed license declaration from referencing a license file to directly specifying "MIT". Removed the MIT license classifier from the list of classifiers. No other metadata changes.

Suggested labels

require-dev-pass

Suggested reviewers

• CoMPaTech

Possibly related PRs

• Implement HA Core PR 138039 #829: Related to PlugwiseDataUpdateCoordinator changes, focusing on adding a type alias and updating the constructor for type specificity, while this PR simplifies method signatures by removing the ConfigEntry parameter.

Poem

A hop and a skip, the code gets neat,
No more passing config with every repeat.
The coordinator now keeps its own key,
Making device wrangling as easy as can be.
With signatures trimmed and logic the same,
The codebase is lighter—oh what a game!
🐇✨

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 0145dbd and dbe40f4.

📒 Files selected for processing (1)

• pyproject.toml (1 hunks)

✅ Files skipped from review due to trivial changes (1)

• pyproject.toml

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR.
• @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai or @coderabbitai title anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud