I certainly hope this isn’t redundant. And maybe someone will find it useful.
First, I’m pleased to report that. after at least a dozen hours of effort, I finally have HA’s OCPP integration working with a Grizzl-E EV charger. (That’s three acronyms in one sentence. Not bad.)
Kudos to the integration’s developer. You do nice work. Not so the United Chargers’ coder. First, look at this image.
This is all you need to make the OCPP integration work with a Grizzl-E charger. Not a character less–especially that slash at the end of the URL. Don’t omit it. You’ll be sorry if you do. My charger, at least, goes offline. A clever coder would have tested for the trailing slash and, if it was missing, would have added one. By the way, the IP address is that of your HA server.
Once things are working, there are still major difficulties. My charger now reboots about every 30 seconds. The charger’s LED changes from blue to magenta for a fraction of a second, accompanied by an HA notification–
plus ~100 lines added to the log. I shut down the server to see if the OCPP integration was triggering the reboots, and discovered that the magenta LED no longer means only that the charger is offline. It also indicates that there’s no OCPP connection. And since the LED is already magenta, there’s no way to tell if charger is rebooting. (Note to UC coder: you still have yellow and orange to work with.) Observe that, when it’s in this state, the charger’s home page–
indicates that it’s offline, even though it isn’t. See the IP address at the top? It;s definitely online.
1 post - 1 participant