Skip to content

Commit e8adbcb

Browse files
Add United Chargers Grizzl-E to documentation (#675)
* Add United Chargers Grizzl-E to supported devices * Add Grizzl-E details and workaround
1 parent 63cdbfe commit e8adbcb

File tree

2 files changed

+34
-0
lines changed

2 files changed

+34
-0
lines changed

docs/supported-devices.md

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -12,6 +12,8 @@ All OCPP 1.6j compatible devices should be supported, but not every device offer
1212
## [EVLink Wallbox Plus](https://www.se.com/ww/en/product/EVH3S22P0CK/evlink-wallbox-plus---t2-attached-cable---3-phase---32a-22kw/)
1313
## [Evnex E Series & X Series Charging Stations](https://www.evnex.com/)
1414
(Ability to configure a custom OCPP server such as HA is being discontinued)
15+
## [United Chargers Inc. - Grizzl-E](https://grizzl-e.com/about/)
16+
(has some defects in OCPP implementation, which can be worked around. See [User Guide](https://github.com/lbbrhzn/ocpp/blob/main/docs/user-guide.md) section in Documentation for details.)
1517
## [Wallbox Pulsar](https://wallbox.com/en_uk/wallbox-pulsar)
1618
## [Vestel EVC04-AC22SW](https://www.vestel-echarger.com/EVC04_HomeSmart22kW.html)
1719
## [V2C Trydan](https://v2charge.com/trydan)

docs/user-guide.md

Lines changed: 32 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -65,3 +65,35 @@ Measurands (according to OCPP terminology) are actually metrics provided by the
6565
* `Availability` (OFF when something causes a problem or during a reboot etc)
6666
* `Maximum Current` (sets maximum charging current available)
6767
* `Reset`
68+
69+
## Useful Entities and Workarounds for United Chargers Grizzl-E
70+
71+
Comments below relate to Grizzl-E firmware version 5.633, tested Oct-Nov 2022.
72+
73+
### Metrics
74+
The Grizzl-E updates these metrics every 30s during charging sessions:
75+
* `Current Import` (current flowing into EV)
76+
* `Power Active Import` (power flowing into EV)
77+
* `Energy Active Import Register` (cumulative energy supplied to EV during charging session. Resets to zero at start of each session)
78+
* `Time Session` (elapsed time from start of charging session)
79+
80+
### Diagnostics
81+
82+
* `Status Connector` (current charger state: available/preparing/charging/finishing/suspended etc)
83+
* `Stop Reason` (reason the charging session was stopped)
84+
* `Latency Pong` (elapsed time for charger's response to internet ping. Good for diagnosing connectivity issues. Usually less than 1000ms)
85+
* `Version Firmware` (charger firmware version and build)
86+
87+
### Controls
88+
89+
* `Charge Control` (User switches to ON to start charging session, once charger is in Preparing state. Can be automated in HA - see this [comment in Issue #442](https://github.com/lbbrhzn/ocpp/issues/442#issuecomment-1295865797) for details)
90+
* `Availability` (ON when charger is idle. OFF during active charging session, or when something causes a problem)
91+
* `Maximum Current` (sets maximum charging current available. Reverts to value set by charger's internal DIP switch following reboots; tweak slider to reload)
92+
93+
### OCPP Compatibility Issues
94+
95+
Grizzl-E firmware has a few OCPP-compliance defects, including responding to certain OCPP server messages with invalid JSON. 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.
96+
97+
The workaround consists of:
98+
- checking the *Skip OCPP schema validation* checkbox during OCPP server configuration
99+
- commenting-out several lines in `/config/custom_components/ocpp/api.py` and adding a few default values to the OCPP server source code. Details are in this [comment in Issue #442](https://github.com/lbbrhzn/ocpp/issues/442#issuecomment-1237651231)

0 commit comments

Comments
 (0)