Skip to content

Conversation

ric866
Copy link
Contributor

@ric866 ric866 commented Mar 10, 2025

Added SyncEV Compact charger as a supported device with some of the tweaks to make it work well.
This should also work for the EVNet Discreet (https://www.evnet.bg/products/evnet-discreet/) but I don't have one to test with, so I didn't add it to the list ;)

Summary by CodeRabbit

  • Documentation
    • Added a new support section detailing setup and configuration instructions for a discontinued 7kW smart charger.
    • The guide explains how to adjust charging parameters, set up automations for meter value retrieval, update the heartbeat interval, and perform firmware updates. Customers can also refer to support if issues arise.

Added SyncEV Compact charger as a supported device
Copy link
Contributor

coderabbitai bot commented Mar 10, 2025

Walkthrough

This pull request updates the supported devices documentation by adding a new section for the SyncEV Compact EVCP charger. The section provides detailed information on the charger's specifications as a discontinued 7kw 1PH smart charger with a standard OCPP implementation. It includes setup instructions for SMART mode, outlines the specific measurands (e.g., Voltage, Temperature, Current.Offered, etc.), and offers guidance on creating automations for meter value retrieval and heartbeat adjustments. It also details the required firmware version and procedures for firmware updates via the app.

Changes

File Change Summary
docs/supported-devices.md Added new section SyncEV Compact EVCP detailing charger specifications, configuration instructions, and automation guidance.

Suggested reviewers

  • lbbrhzn

Poem

Hop, hop, in docs so bright,
A new section shines with delight.
SyncEV steps into the light,
Firmware and automations in sight.
With whiskered cheer, I celebrate each byte—
A bunny’s tale of updates done right! 🐰


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
🪧 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.

@ric866 ric866 temporarily deployed to continuous-integration March 10, 2025 11:47 — with GitHub Actions Inactive
Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

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

Actionable comments posted: 0

🧹 Nitpick comments (4)
docs/supported-devices.md (4)

101-104: New Section Introduction & Header Content
– The new section header for the SyncEV Compact EVCP is introduced using an atx heading (##), which appears consistent with other subsections in this document. However, if your style guidelines prefer setext headers for primary sections, please update accordingly.
– In line 102, there is a typographical error: “tolerent” should be corrected to “tolerant”.
– Additionally, note the default credential in line 103 ("The admin panel password is admin"). Although common in documentation, consider adding a note that users should change this default for production use.

Diff suggestion for line 102:

-These are a discontinued (but cheap) 7kw 1PH smart charger, with an OCPP implementation that's seemingly quite close to standard, and tolerent.
+These are a discontinued (but cheap) 7kw 1PH smart charger, with an OCPP implementation that's seemingly quite close to standard, and tolerant.
🧰 Tools
🪛 markdownlint-cli2 (0.17.2)

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

(MD003, heading-style)


105-106: List Item Formatting & Spelling Correction
– The unordered list items in lines 105–106 are indented with extra spaces (3 spaces observed) whereas the markdown guideline expects no indent for top-level list items.
– In line 105, "retreiving" should be corrected to "retrieving".

Diff suggestion for line 105:

-   - Force SMART mode, to allow setting charge rates (use action ocpp.set_charge_rate) and retreiving meter values (use action ocpp.trigger_custom_message)
+ - Force SMART mode, to allow setting charge rates (use action ocpp.set_charge_rate) and retrieving meter values (use action ocpp.trigger_custom_message)

Diff suggestion for line 106:

-   - Manually specify the Measurands
+ - Manually specify the Measurands
🧰 Tools
🪛 markdownlint-cli2 (0.17.2)

105-105: Unordered list indentation
Expected: 0; Actual: 3

(MD007, ul-indent)


106-106: Unordered list indentation
Expected: 0; Actual: 3

(MD007, ul-indent)


107-112: Nested List Indentation
The sub-list items under "Manually specify the Measurands" (lines 107–112) are indented with 6 spaces, yet markdown style guidelines typically expect a 2-space indent for nested items relative to the parent. Please adjust the indentation to improve readability and conform to the guideline.

Diff suggestion (example for line 107; apply similar changes to lines 108–112):

-      - Voltage
+  - Voltage

(Adjust the indent so that each sub-item has 2 spaces relative to its parent list item.)

🧰 Tools
🪛 markdownlint-cli2 (0.17.2)

107-107: Unordered list indentation
Expected: 2; Actual: 6

(MD007, ul-indent)


108-108: Unordered list indentation
Expected: 2; Actual: 6

(MD007, ul-indent)


109-109: Unordered list indentation
Expected: 2; Actual: 6

(MD007, ul-indent)


110-110: Unordered list indentation
Expected: 2; Actual: 6

(MD007, ul-indent)


111-111: Unordered list indentation
Expected: 2; Actual: 6

(MD007, ul-indent)


112-112: Unordered list indentation
Expected: 2; Actual: 6

(MD007, ul-indent)


113-117: List Formatting & Grammar Adjustments in Subsequent Items
– The list items from lines 113 to 117 also have an extra indentation (3 spaces observed); they should start at the same level (no leading spaces) as top-level list items.
– Specifically, in line 114, the phrase “a value different to the one in the chargepoint” should be changed to “a value different from the one in the chargepoint” and “hearbeat” is a typo for “heartbeat.”

Diff suggestion for line 114:

-   - Optionally create an automation updating the hearbeat interval (you have to set a value different to the one in the chargepoint) when the chargepoint reboots.
+ - Optionally create an automation updating the heartbeat interval (you have to set a value different from the one in the chargepoint) when the chargepoint reboots.

Diff suggestion for line 113 (example adjustment):

-   - Create an automation triggering action: ocpp.trigger_custom_message with requested_message set to MeterValues on a schedule of your choice to retrieve the Measurands.
+ - Create an automation triggering action: ocpp.trigger_custom_message with requested_message set to MeterValues on a schedule of your choice to retrieve the Measurands.

(Apply similar un-indentation for lines 115–117.)

🧰 Tools
🪛 LanguageTool

[grammar] ~114-~114: In American English, the usual prepositions after ‘different’ are “from” or “than”.
Context: ...rval (you have to set a value different to the one in the chargepoint) when the ch...

(DIFFERENT_TO)

🪛 markdownlint-cli2 (0.17.2)

113-113: Unordered list indentation
Expected: 0; Actual: 3

(MD007, ul-indent)


114-114: Unordered list indentation
Expected: 0; Actual: 3

(MD007, ul-indent)


115-115: Unordered list indentation
Expected: 0; Actual: 3

(MD007, ul-indent)


116-116: Unordered list indentation
Expected: 0; Actual: 3

(MD007, ul-indent)


117-117: Unordered list indentation
Expected: 0; Actual: 3

(MD007, ul-indent)

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between ce7be5b and d807a98.

📒 Files selected for processing (1)
  • docs/supported-devices.md (1 hunks)
🧰 Additional context used
🪛 LanguageTool
docs/supported-devices.md

[grammar] ~114-~114: In American English, the usual prepositions after ‘different’ are “from” or “than”.
Context: ...rval (you have to set a value different to the one in the chargepoint) when the ch...

(DIFFERENT_TO)

🪛 markdownlint-cli2 (0.17.2)
docs/supported-devices.md

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

(MD003, heading-style)


105-105: Unordered list indentation
Expected: 0; Actual: 3

(MD007, ul-indent)


106-106: Unordered list indentation
Expected: 0; Actual: 3

(MD007, ul-indent)


107-107: Unordered list indentation
Expected: 2; Actual: 6

(MD007, ul-indent)


108-108: Unordered list indentation
Expected: 2; Actual: 6

(MD007, ul-indent)


109-109: Unordered list indentation
Expected: 2; Actual: 6

(MD007, ul-indent)


110-110: Unordered list indentation
Expected: 2; Actual: 6

(MD007, ul-indent)


111-111: Unordered list indentation
Expected: 2; Actual: 6

(MD007, ul-indent)


112-112: Unordered list indentation
Expected: 2; Actual: 6

(MD007, ul-indent)


113-113: Unordered list indentation
Expected: 0; Actual: 3

(MD007, ul-indent)


114-114: Unordered list indentation
Expected: 0; Actual: 3

(MD007, ul-indent)


115-115: Unordered list indentation
Expected: 0; Actual: 3

(MD007, ul-indent)


116-116: Unordered list indentation
Expected: 0; Actual: 3

(MD007, ul-indent)


117-117: Unordered list indentation
Expected: 0; Actual: 3

(MD007, ul-indent)

⏰ Context from checks skipped due to timeout of 90000ms (1)
  • GitHub Check: Run tests

Copy link

codecov bot commented Mar 10, 2025

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 92.62%. Comparing base (ce7be5b) to head (d807a98).
Report is 1 commits behind head on main.

Additional details and impacted files
@@           Coverage Diff           @@
##             main    #1568   +/-   ##
=======================================
  Coverage   92.62%   92.62%           
=======================================
  Files          12       12           
  Lines        2048     2048           
=======================================
  Hits         1897     1897           
  Misses        151      151           

☔ 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.

@lbbrhzn lbbrhzn self-requested a review March 10, 2025 15:02
@lbbrhzn lbbrhzn merged commit cb3477c into lbbrhzn:main Mar 10, 2025
9 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants