I’ve set up my new Grizzl-E Mini Connect with OCPP and it’s connected to Charge HQ. I can see the charger status and it’s reporting correctly on the CHQ dashboard, however commands I send are not working. If I try to change the charge rate or select “Stop” the charger continues to charge.
I’m not sure if this is an issue on the charger or an issue on the Charge HQ end, how do I determine what is happening?
I was contemplating getting a Grizzl-E Mini or Ultimate as well and was really, really hoping its OCPP support would work with ChargeHQ and just stumbled upon your post. Were you able to make any progress / find out what was going on (i.e. by trying ChargeHQs test environment and -steps etc) and ideally fix it?
Thanks!
-JB
@cory.imdieke if you perform the testing per this guide (or at least, the first bit until it fails), and note down the exact time of each step you take, I can check the logs.
The Grizzl-E has not been officially validated against Charge HQ so we can’t promise it will work, but I’m happy to take a quick look to see if there’s any obvious problem. Cheers.
I reached out to United Chargerrs / the company behind the Grizzl-E chargers inquiring about their latest generation chargers (Ultimate & Mini) that have entirely new FW and better (?) OCPP 1.6 compliance than their previously 3rd-party/sort of “outsourced” FW had… and Gleb, their CEO, said OCPP CSMS providers should/could just reach out to him to get some sort of collaboration going. Not sure if that’s an option for you @jbanyer but wanted to throw it out there and it might make debugging/fixing things easier if two vendors talked to each other vs. customers being the middlemen which might lose/miss important details.
@jbattermann thanks for the info. We have no plans currently to formally integrate with United / Grizzl-E chargers but we’ll get in touch with them if that changes. Cheers.
Got it, thanks for the reply / info!
Hello
I have just had my MG charger replaced under warranty, and I am setting it up.
So far, the Charge HQ app can see the charger and is getting the correct feed from my wattwatcher monitors.
It doesn’t control the charger at all. It seems stuck at the “Starting” phase. During which the charger is running at full charge. It never moves past this stage.
I have it set to excess solar only.
It seems to be getting all the correct information but there is no control. It is clear from the monitor that there isn’t enough solar to charge, yet the charger is on flat out.
Logs sent to ChargeHQ and MG, hopefully a response soon
I have an Ocular Wallbox IQ that was happily working for about a week before last night (02/05) it just stopped acknowledging commands from ChargeHQ and started charging at full speed whenever I plugged it in.
ChargeHQ reports the charger as being online, but also reports it as being unplugged when it’s plugged in.
The logs for the Ocular are reporting the following:
[10:18:52.319 Charger_DrvPoint_WebSocket.c:430]e[0mLWS_CALLBACK_USERe[0m
[10:18:52.320 Charger_DrvPoint_WebSocket.c:121]e[0morigin https://ocpp.chargehq.nete[0m
[10:18:52.320 Charger_DrvPoint_WebSocket.c:122]e[0mURL /ocpp16/eXXXXXe[0m
[10:18:52.320 Charger_DrvPoint_WebSocket.c:144]e[0;36mUsing SSLe[0m
[10:18:52.320 Charger_DrvPoint_WebSocket.c:151]e[0;36mNot Allow SelfSigne[0m
[10:18:52.320 Charger_DrvPoint_WebSocket.c:157]e[0;36mNot Skip HostName Checke[0m
[10:18:52.320 Charger_DrvPoint_WebSocket.c:163]e[0;36mNot Allow Expirede[0m
[10:18:52.511 Charger_DrvPoint_WebSocket.c:438]e[0;36mLWS_CALLBACK_CLIENT_APPEND_HANDSHAKE_HEADER 24e[0m
[10:18:52.567 Charger_DrvPoint_WebSocket.c:388]e[0mEstablishede[0m
[10:18:52.567 Charger_DrvPoint_WebSocket.c:422]e[0;36mLWS_CALLBACK_CLIENT_CLOSED Connect Closed! Try Again!e[0m
(EVSE ID redacted from above. Unsure if it’s sensitive information or not)
So it appears to connect, but then the WS connection is just dropped, which might explain why ChargeHQ thinks it’s online but is unable to issue any controls to it.
Again, this was all working fine until last night with no changes (that I’m aware of) on my end.
Any chance you can take a peek at this please @jbanyer ? I can provide you with my EVSE ID in a DM if you require it.
@singe have you tried restarting your charger? The logs show a strange issue with the connectivity was occurring overnight, although it looks okay right now (11am Sat Sydney time).
@jay Yeah, I have. I’ve done a factory reset and also called Ocular tech support.
Right now I’ve moved the charger back to Ocular’s OCPP server which at least gives me some of the basic functionality, though I’d like to move back to Charge HQ
@jay To muddy the waters a bit here, I did have a temporary EV charger that was removed and replaced with the new one I’m using about a week ago. I noticed that when I removed the old charger and added the new one to Charge HQ that it gave me the same EVSE ID
There’s a non-zero possibility that the previous charger may have been installed someplace else. If two chargers were trying to use the same EVSE ID, could that cause weird issues like this? Is there a way my Charge HQ account could be assigned a new EVSE ID for my charger?
@singe if the old charger was powered up and had an internet connection, then yes, that may be causing the problem. I would suggest you change your EVSE ID. To do that, disconnect the charger in Charge HQ, then go to add a new one, and edit the EVSE ID on the first screen. Just make a small change to the default EVSE ID (which will be the same as before), eg add a number at the end.
I didn’t realize I could edit it! I thought the EVSE ID was being assigned to me.
Will try in just a moment. I think this is the most likely culprit. Attached are a couple of screenshots: One showing the firmware version of the charger currently reporting to ChargeHQ, the other other of the charger currently in my garage (as reported by the Ocular app)
Will report back in just a sec
Yup! That did the trick. Thanks Jay! Appreciate you taking time on your Saturday 
Charge HQ is a great product. As an Amber customer, I’m looking forward to seeing the functionality integrated with Amber soon! 
