Add ZJ Beny to supported devices

[Mark-Hetherington]

Summary by CodeRabbit

• Documentation
  • Updated the supported devices guide with details for a new charging station.
  • Included a product page link and a note clarifying different model features regarding OCPP support.

[coderabbitai]

Walkthrough

The pull request updates the documentation by adding a new section for the ZJ Beny BCP-A2N-P charging station within the docs/supported-devices.md file. This update introduces a heading with a hyperlink to the product page and includes a note to clarify that several models with similar names exist, with varying OCPP support. The new section is inserted before the "Others" section that covers unsupported chargers.

Changes

File	Change Summary
docs/supported-devices.md	Added a new section for "ZJ Beny BCP-A2N-P" including a hyperlink and a note about varying model features.

Suggested reviewers

• lbbrhzn

Poem

I’m a hopping CodeRabbit with a joyful cheer,
Updating docs so new info is clear.
A fresh section sprouts like a springtime bloom,
Guiding users to a charging station room.
With links and notes, our docs now dance free—
A nibble of progress in every line I see! 🐇

---

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.

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (1)

docs/supported-devices.md (1)

124-126: New Supported Device Section Added Successfully

The new section for the ZJ Beny BCP-A2N-P is a clear and useful addition that aligns with the PR objective. However, static analysis flagged a header style issue on line 124 (MD003): it expected setext style rather than the current ATX style. Consider updating the heading to conform with the project’s markdown guidelines. For example:

-## [ZJ Beny BCP-A2N-P](https://ultipower.com.au/products/zj-beny-home-charging-station-ac-7kw-32a-type-2-ocpp)
+ [ZJ Beny BCP-A2N-P](https://ultipower.com.au/products/zj-beny-home-charging-station-ac-7kw-32a-type-2-ocpp)
+ ================================================================

Alternatively, if ATX style is intentionally used, you might update the markdownlint configuration to avoid this warning.

🧰 Tools

🪛 markdownlint-cli2 (0.17.2)

124-124: Heading style
Expected: setext; Actual: atx

(MD003, heading-style)

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 80fc9d4 and 230877c.

📒 Files selected for processing (1)

• docs/supported-devices.md (1 hunks)

🧰 Additional context used

🪛 markdownlint-cli2 (0.17.2)

docs/supported-devices.md

124-124: Heading style
Expected: setext; Actual: atx

(MD003, heading-style)

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 92.66%. Comparing base (80fc9d4) to head (230877c).
Report is 5 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #1556   +/-   ##
=======================================
  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.

🚀 New features to boost your workflow:

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