Charging openHAB with OCPP

Please check logs, and if there are any errors copy them. I’ve tested binding only with simulator as I had no access to real hardware.

Just in case logging category is org.connectorio.addons.binding.ocpp.

OK, there are some errors in the log:

2022-12-16 17:49:44.066 [ERROR] [eu.chargetime.ocpp.WebSocketListener] - On error (resource descriptor: not defined (webSocket is null)) triggered: Cannot assign requested address: bind
	at Method) ~[?:?]
	at ~[?:?]
	at ~[?:?]
	at ~[?:?]
	at ~[?:?]
	at org.java_websocket.server.WebSocketServer.doSetupSelectorAndServerThread( [bundleFile:?]
	at [bundleFile:?]
	at [?:?]

One thing which I have been wondering about my OH3 version. When I start OH3 the Karaf window says 3.3.0 but in Help & About page in the MainUI the version seems to be 3.2.0. I had to install OCPP version 3.2.

Can you tell me how an kar file can be added in OpenHAB, normally I have jar files.

kar files are a “collection” of jar files ( see KAR ).
They can be added in the same way as jar files.

Indeed, main difference is - KAR files can ship more JAR files than just one. They supplement local “system” directory with more libraries if needed. Please be aware that binding just launches OCSP 1.6J server to which charging station can be connected. It does not offer much beyond that.

I noticed that OH 3.2+ introduced some more strict validation of configuration options as well as channels which lead to some troubles in other bindings I made. If you spot any issues do not be surprised and please report it back.
I’ll be doing some testing with simulators early next year and try to add some channels in.


Hello, is still a Version for 3.4 available?

Not yet, but I think that 3.3 version is employable with 3.4 too. Please give it a try. I am still working on integration tests which will let me cross check builds against multiple releases.

So, one step forward :smile:

OCPP from Wallbox is connected to OH, and my Wallbox was automatically discovered.
3 properties are discovered, but thing stay in status initializing, connector in status error bridge.

Are the any channels planed for this binding to steer the Wallboxes?


Maybe change download link…