Grizzl-E doc updates for firmware 3.x.x on Mini / Ultimate models #1586
Conversation
WalkthroughThis update refines the Grizzl-E charger documentation. The supported-devices file now lists models compatible with firmware 3.x.x (including Mini Connect 2024 and Ultimate) and notes a known issue in firmware 03.09.0 with a pending fix in 03.11.0. The user-guide file clarifies that OCPP compliance issues affect firmware 5.x, while firmware 3.x.x remains unaffected. No changes were made to public entity declarations. Changes
Suggested reviewers
Poem
Tip ⚡🧪 Multi-step agentic review comment chat (experimental)
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. 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
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)
Other keywords and placeholders
CodeRabbit Configuration File (
|
bverkron
changed the title
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 0
🧹 Nitpick comments (2)
docs/user-guide.md (1)
135-135: Clarify Firmware Versioning and Refine Wording
The updated section clearly distinguishes that firmware 5.x exhibits OCPP-compliance defects while firmware 3.x.x (used on Mini Connect and Ultimate) is not plagued by these issues. However, consider refining the sentence for a more formal tone. For example, replacing “expects to release” with “is expected to release” and “fix these problems” with “resolve these issues” could improve clarity and formality.Suggested diff:
-Grizzl-E firmware 5.x has a few OCPP-compliance defects, including responding to certain OCPP server messages with invalid JSON. Firmware 3.x.x on chargers such as the Mini Connect and Ultimate does not seem to have these issues. Symptoms of this problem include repeated reboots of the charger. By editing the OCPP server source code, one can avoid these problematic messages and obtain useful charger behaviour. ChargeLabs (the company working on the Grizzl-E firmware) expects to release version 6 of the firmware in early 2023, which may fix these problems. +Grizzl-E firmware 5.x exhibits several OCPP compliance issues (e.g., responding to certain OCPP server messages with invalid JSON), whereas firmware 3.x.x—used on chargers like the Mini Connect and Ultimate—appears to operate without these issues. These defects may cause symptoms such as repeated charger reboots. As a workaround, one can modify the OCPP server source code to bypass the problematic messages. ChargeLabs (the company behind the Grizzl-E firmware) is expected to release version 6 of the firmware in early 2023, which may resolve these issues.🧰 Tools
🪛 LanguageTool
[style] ~135-~135: Consider using a different verb for a more formal wording.
Context: ...f the firmware in early 2023, which may fix these problems. The workaround consist...(FIX_RESOLVE)
docs/supported-devices.md (1)
134-144: Enhance Clarity on Firmware Differentiation and Update Phrasing
The changes clearly differentiate between Grizzl-E chargers running firmware 3.x.x and those with 5.x.x by list format, which is very helpful. A couple of minor suggestions:
- You may consider rephrasing “work mostly without issue” to “operate reliably” to maintain a more formal tone.
- The sentence “Supported OCPP requests for the 3.x.x firmware are documented in a PDF on their site in under https://grizzl-e.com/connect-to-third-party-ocpp-backend/” could be slightly polished for clarity. For example, “are documented in a PDF available on their website at …” may improve readability.
Suggested diff:
-Grizzl-E chargers with firmware 3.x.x work mostly without issue, such as the following: +Grizzl-E chargers running firmware 3.x.x operate reliably, as demonstrated by: -Known issue: In firmware 03.09.0 amperage changes are accepted but not applied. This is due to the firmware accepting but not handling a value of `ChargePointMaxProfile` in `ChargerProfilePurpose`. United Chargers has stated that this will be addressed in firmware version 03.11.0. +Known issue: In firmware 03.09.0, amperage changes are accepted but not applied due to the firmware not handling the `ChargePointMaxProfile` value within `ChargerProfilePurpose`. United Chargers has stated that this issue will be resolved in firmware version 03.11.0. -Supported OCPP requests for the 3.x.x firmware are documented in a PDF on their site in under https://grizzl-e.com/connect-to-third-party-ocpp-backend/ +Supported OCPP requests for the 3.x.x firmware are documented in a PDF available on their website at https://grizzl-e.com/connect-to-third-party-ocpp-backend/
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (2)
docs/supported-devices.md(1 hunks)docs/user-guide.md(1 hunks)
🧰 Additional context used
🪛 LanguageTool
docs/user-guide.md
[style] ~135-~135: Consider using a different verb for a more formal wording.
Context: ...f the firmware in early 2023, which may fix these problems. The workaround consist...
(FIX_RESOLVE)
Hi there!
I got a Grizzl-E Mini Connect 2024 and have been running it with the HA OCPP integration for a month or two with almost zero issues, despite the major issues and required workarounds reported in the documentation. It seems the Mini Connect and Ultimate models use a different firmware series (3.x.x vs 5.x) and they have resolve the majority of the issues.
This is my Mini Connect running on the latest version of the OCPP integration (0.8.4) with no modifications to the integration code. Not every sensor is provided but the ones that are provided work perfectly so far.
The only issues I've had with the OCPP integration, so far, is amperage changes not being applied. After several discussions with United Chargers they acknowledged the issue and said it should be fixed in an upcoming firmware update.
Here is a copy of the relevant portion of the email thread with them.
They have also setup a dedicated email address for working with them on OCPP implementation issues at integrations@unitedchargers.com. I decided not to include that email address in the documentation directly since it's intended more for developers to work with them on OCPP defects rather than be used as a setup support inbox for general users. But open to discussion on it.
Anyway, I thought this was all really good and useful info for people considering Grizzl-E chargers, specifically the Mini and Ultimate who want to integrate into Home Assistant. With the current documentation they might be scared away thinking it won't work.
Happy to make any recommended changes!
Summary by CodeRabbit