You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
## [Evnex E Series & X Series Charging Stations](https://www.evnex.com/)
14
14
(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.)
*`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