fix case issue with migration

[drc38]

Should result in more chargers able to migrate directly from 0.7.0

Summary by CodeRabbit

• Bug Fixes
  • Improved sensor identifier formatting to ensure consistent state matching for enhanced reliability.

[coderabbitai]

Walkthrough

A change was made within the async_migrate_entry function in the OCPP custom component. The code now transforms the value from cpid_data[CONF_CPID] to lowercase before concatenating it with the string "sensor." and the suffix "_id". This update ensures that the sensor ID is consistently formatted to match the expected state key in Home Assistant. No other logic or error handling was altered.

Changes

File	Change Summary
custom_components/ocpp/init.py	Updated the construction of the cp_id variable in async_migrate_entry to convert cpid_data[CONF_CPID] to lowercase for standardized sensor IDs.

Poem

I'm a hopping rabbit, full of glee,
Spotting lowercase changes in our code spree,
Sensor IDs now dance in a uniform tune,
Consistency shining like a crescent moon,
A joyful leap in code—oh, what a boon!

---

📜 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 93f3076 and 00eb82d.

📒 Files selected for processing (1)

• custom_components/ocpp/__init__.py (1 hunks)

⏰ Context from checks skipped due to timeout of 90000ms (1)

• GitHub Check: Run tests

🔇 Additional comments (1)

custom_components/ocpp/__init__.py (1)

183-183: Good fix for case-sensitivity issue in sensor ID lookup.

Converting the CPID to lowercase ensures consistent sensor ID formats, which helps avoid potential issues when retrieving sensor states in Home Assistant. This is a solid fix for the case sensitivity issue mentioned in the PR title.

✨ Finishing Touches

• 📝 Generate Docstrings

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ 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 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 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.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 92.66%. Comparing base (93f3076) to head (00eb82d).
Report is 1 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #1541   +/-   ##
=======================================
  Coverage   92.66%   92.66%           
=======================================
  Files          12       12           
  Lines        2032     2032           
=======================================
  Hits         1883     1883           
  Misses        149      149           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.