docs: plain ws, reported model, and the connector status caveat for Autel - #2076
Conversation
…utel Follow-up to lbbrhzn#2072, from two MaxiChargerAC units running here. The section as merged documents only the wss:// + reverse proxy path, which reads as though TLS were required. On a LAN a plain ws:// URL works with no certificate handling at all, so the TLS instructions now say what they are for. Adds the model string the chargers actually report, and the fact that Autel support has told an owner these units do not speak OCPP -- worth contradicting in a document called supported-devices, since a vendor saying "your model cannot do this" is what stops people trying. Adds one automation caveat: sensor.<cpid>_status can read Available while a car is plugged in and not drawing, where status_connector reads SuspendedEV. Observed on two chargers in different states at the same moment. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (1)
📝 WalkthroughWalkthroughThe documentation confirms MaxiChargerAC compatibility, clarifies TLS requirements for local and reverse-proxy connections, and recommends the connector-specific status sensor for automations. ChangesDevice documentation
Estimated code review effort: 1 (Trivial) | ~3 minutes Merge Risk: ⚪ Minimal · up to This is a localized documentation update with no code or runtime behavior changes, so no actionable merge-blocking risk remains after normal checks and review. Suggested reviewers: 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
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. Comment |
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #2076 +/- ##
=======================================
Coverage 96.27% 96.27%
=======================================
Files 12 12
Lines 3250 3250
=======================================
Hits 3129 3129
Misses 121 121 ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
2 participants
Follow-up to #2072, which merged before I could get these into it — I'd left them as a comment there. All three come from two
MaxiChargerACunits running here on OCPP 1.6-J.The section reads as though TLS were required. Everything documented so far is the
wss://+ reverse-proxy path, which is the harder setup. A plainws://<ha-ip>:9000on a LAN works with no certificate handling at all. The TLS instructions are worth keeping — they just needed a line saying what they're for.The reported model, and a vendor claim worth contradicting. These report vendor
Autel, modelMaxiChargerAC, firmwarePFA0102|V0.00.00|V1.38.00||2.4.3.0. Autel support told the owner these units don't support OCPP — that only the AC Smart Elite does. They've been running against this integration for weeks. In a document called supported devices, a vendor telling someone their hardware can't do this is precisely what stops them trying.One automation caveat.
sensor.<cpid>_statuscan readAvailablewhile a car is plugged in and simply not drawing;sensor.<cpid>_status_connectorreadSuspendedEVfor the same charger at the same moment. Anything gating on plugged-in state wants the connector sensor. This came out of having two chargers in different states simultaneously — it isn't visible with one.Documentation only, no code touched.
🤖 Generated with Claude Code
Summary by CodeRabbit