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
[Jonas Karlsson](https://github.com/jonasbkarlsson) has written a [getting started guide](https://github.com/jonasbkarlsson/ocpp/wiki/CTEK-Chargestorm-Connected-2) for connecting CTEK Chargestorm Connected 2.
16
+
17
+
## [Etrel - Inch Pro](https://etrel.com/charging-solutions/inch-pro/)
18
+
To allow a custom OCPP server such as HA to set up a transaction ID, it is necessary to set under Users > Charging Authorization the
19
+
authorization type to either `Central system only` or `Charger whitelist and central system` otherwise the OCPP integration won't
20
+
match transactions and it won't report some meter values such as session time.
## [Evnex E Series & X Series Charging Stations](https://www.evnex.com/)
15
27
(Ability to configure a custom OCPP server such as HA is being discontinued)
28
+
16
29
## [United Chargers Inc. - Grizzl-E](https://grizzl-e.com/about/)
17
30
(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.)
## [Etrel - Inch Pro](https://etrel.com/charging-solutions/inch-pro/)
24
-
To allow a custom OCPP server such as HA to set up a transaction ID, it is necessary to set under Users > Charging Authorization the
25
-
authorization type to either `Central system only` or `Charger whitelist and central system` otherwise the OCPP integration won't
26
-
match transactions and it won't report some meter values such as session time.
27
39
40
+
## Others
28
41
When a charger is not listed as a supported charger it simply means that it has not been reported to work. Whether it will work or not in practice really depends on whether it is compliant with the OCPP standard. Some vendors claim their device is compliant without bothering to do a compliance test, because that takes time and costs money!
29
42
30
43
When it is fully compliant, then it should work out of the box, since the ocpp integration is designed to work for fully compliant chargers. Any issues should be reported, and we will do out best to analyze them. In some cases modifications or workarounds may be needed. As long as these workarounds do not break compliance to the OCPP standard they can be added to this repository.
0 commit comments