Charging openHAB with OCPP

Hi @splatch , thanks for the link. Installed it and connected my Ocular IQ charger. On charger side logging shows an established connection. But I don’t see anything happening on openHAB side and the the charger thing is stuck in initializing. I tried different loggers but don’t see any logs.

Which logger can I enable to see what’s happening?

I configured the Things as follows. Is that correct?

Bridge co7io-ocpp:server:ocppserver "OCPP Server" [ port="9113", heartbeat="10" ]
Thing co7io-ocpp:charger:OcularEvCharger "OCPP Charger" (co7io-ocpp:server:ocppserver) [ serialNumber="xxx"]
Thing co7io-ocpp:connector:OcularConnector "OCPP Connector" (co7io-ocpp:charger:OcularEvCharger ) [ connectorId="1"]

Thanks for some hints, cheers.

Set debug log for org.connectorio.addons.binding.ocpp and eu.chargetime.ocpp. These two will show you binding and library level actions. The chargetime.ocpp is not very chatty. Some charges have different behavior and I am not really clear is there a one way to fetch their state which works for all of them.

Thank you @splatch. Is the Thing configuration correct?

The log is as follows.

22:11:37.063[DEBUG] [eu.chargetime.ocpp.WebSocketListener] - On connection open (resource descriptor: /xxxxxxxxxx)
22:11:37.069[INFO] [org.connectorio.addons.binding.ocpp.internal.server.OcppServer] - New OCPP connection yyyyyyyyyyyyy with identifier /xxxxxxxxxx from address /192.168.x.xx:46646.
22:11:37.074[DEBUG] [eu.chargetime.ocpp.Server] - Session created: yyyyyyyyyyyyy
22:11:55.674[DEBUG] [eu.chargetime.ocpp.WebSocketListener] - On connection close (resource descriptor: /xxxxxxxxxx, code: 1006, reason: Connection reset, remote: false)
22:11:55.677[INFO] [org.connectorio.addons.binding.ocpp.internal.server.OcppServer] - Terminated connection zzzzzzzzzzzzzzz.

Looks like a handshake issue - fourth line indicates that charger closed connection. Have you tried to connect charger to any other server before?

I’m getting an error when trying to follow that link.

I’ve updated link, it got some extra characters. KAR files are still there.

I found the issue which prevented the charger from connecting and created a PR.

Thanks for having a look, cheers.

Thanks for changes, I approved a build over github infrastructure, so there will be pr-122 build compatible with OH 5.0.x. Would be great if someone else could also test these changes with charger of different brand than yours. Can you give it a try @chris @jlikonen?

Is this version compatible with 5.1.3 and where is the latest kar-file?

I’ll try eventually with mine. It’s a autel charger and I know they are normally different then other charger.