Fix temperature unit

[smoki3]

Fix for:

#1559

[coderabbitai]

Walkthrough

The pull request updates the mapping dictionary in custom_components/ocpp/const.py. A new entry is added to DEFAULT_CLASS_UNITS_HA, associating SensorDeviceClass.TEMPERATURE with ha.UnitOfTemperature.CELSIUS. This change expands the classification mechanism to include temperature measurements without altering existing mappings.

Changes

File(s)	Change Summary
custom_components/ocpp/const.py	Added new mapping for SensorDeviceClass.TEMPERATURE: associated with ha.UnitOfTemperature.CELSIUS

Poem

I hopped along the code, so spry,
Adding mappings beneath the sky.
A Celsius touch, crisp and new,
Brings warmth to sensors through and through.
Cheers from this coding rabbit—hip hip, hoo!
🥕🐇

---

📜 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 bbfddb8 and 10ce866.

📒 Files selected for processing (1)

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

🔇 Additional comments (1)

custom_components/ocpp/const.py (1)

137-137: Appropriate mapping for temperature device class!

This change ensures that temperature readings will default to Celsius when no explicit unit is provided by the OCPP protocol. The addition follows the existing pattern in the dictionary and aligns with the comment on line 129.

This fix addresses the temperature unit issue mentioned in #1559 by providing a default unit for temperature sensors, ensuring consistent and proper reporting in the Home Assistant UI.

✨ Finishing Touches

• 📝 Generate Docstrings

---

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 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.71%. Comparing base (bbfddb8) to head (10ce866).
Report is 1 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #1560   +/-   ##
=======================================
  Coverage   92.71%   92.71%           
=======================================
  Files          12       12           
  Lines        2032     2032           
=======================================
  Hits         1884     1884           
  Misses        148      148           

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

🚀 New features to boost your workflow:

• ❄ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.