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.

Hi @splatch

I wanted to followup to see if this binding was still available (openHAB 5.1.3) I followed the links above and on the repoisitory.connectorio.cloud “ConnectorIO Binary Artifacts Repository it says resource not found so I could not look for a 5.x release

Are you planning to put this as part of the Community bindings on the openHAB community page so that more people can find it. Bundles - openHAB Community

If you are not continuing with it if you could let me know as well please so i can look fore another approach

thanks a million

Brett

Indeed, links have changed due to phasing out previous repository manager, please use this link: ConnectorIO Binary Artifacts Repository.

I gonna update links in first post, so they will point to valid artifacts. There is one more pull request from @PRosenb which I should include in next successful deployment (infrastructure updates ongoing).

Sadly I have no time to maintain posts and links (as you can see).. I know it would help spread things around, but current marketplace form does not make it too easy.

Thanks a million for taking the time to reply - greatly appreciated

Will provide feedback - have a Zappi myenergy WallBox

Take care

Dears,

could you share with me the parameters which I´ve to put into Huawei SCharger Wallbox to have succesfull connection to openhab?

Authentication mode: Insecure transmission with basic authentication
Connect to Business Platform: IP
IP Address: the IP address of my server
Path: ???
Port: 8887
Username: ???
Password: ???

Thank you so much for your help and support :slight_smile:

Hello, leave path empty or set it to /. Username and password can be empty.
OCPP server is separate component and does not share authentication with OH.

Hello, I was wondering if Autel charger support was added or how to help to have it? I’ve tried many OCPP alternative and while the charger connect no problem, they are not able to start/stop a charge, configure the charger for autostart, etc. For now, only EVCC is working and while I do like the project, it require a token for Autel at 150$ so no thanks.

If evcc is using custom code for that probability that plain OCPP will be sufficient is low. With PR started by @PRosenb things started look better, as he was able to plug a real charger he owns. Still its a different brand.

I’m currently short on time to fully refactor PR #129.

Would it make sense to mark the new initialOcularEcoMode custom property as temporary/experimental and merge the PR as-is? This would unblock other users who are waiting on the generic improvements (current limit and start/stop support), while we schedule a follow-up to properly separate out the custom property.

Happy to hear thoughts — open to other approaches too.

I think it is good to go in current form. I will squash merge it today or tomorrow so people with other equipment can test.

Thank you Łukasz. I just added [EXPERIMENTIAL] to the property description so that we can move it easily if needed.