[Keba] multiple Keba Wallbox System error Handler

[ghost]

Hello,

I have 2 Keba Wallbox in my system. Let´s say one has IP 192.168.0.20 and the other one 192.168.0.21. Thing Konfiguration:

keba:kecontactp20:1 [ ipAddress="192.168.0.20", refreshInterval=15 ] keba:kecontactp20:2 [ ipAddress="192.168.0.21", refreshInterval=15 ]

But the Keba Handler says this in the logfile:

2017-03-14 17:25:14.395 [WARN ] [ing.keba.handler.KeContactP20Handler] - Received data from '/192.168.0.21:7090' which is not the permitted remote address '/192.168.0.20'

So if I comment the first keba Wallbox in the thing configuration like this

// keba:kecontactp20:1 [ ipAddress="192.168.0.20", refreshInterval=15 ] keba:kecontactp20:2 [ ipAddress="192.168.0.21", refreshInterval=15 ]

the second one is working fine. This is switchable as you like.

Is someone able to show me the configuration with more than one Keba Wallbox in openHAB or is it just a bug in the Keba Handler?

Thanks

[ghost]

By the way I forgot 2 other problems: With the actual firmware on the Keba wallbox the following 2 items are not readable:

• actual state
• firmware

[kgoderis]

It is because of the broadcasting done by the keba. At the time i did not take into account the fact that one would install more than one station. I am in the process of installing a second one myself so I will have to fix that anyways ;-)

[ghost]

Sound good. By the way, can someone give me a rules file for this? I´m not the programming guy, I am an Infrastructure IT guy. Of course changing an some additional things is no problem, but starting from zero is here a little bit tricky. The SMA energy monitor is in the system and two Keba inverter, but they doesn't matter I think. Thanks.

[ghost]

Sorry, I forgot to say, that of course if you need someone for testing then send me the new package. I´m using openHAB on my Synology, but for the add on I think it is equal.

[kgoderis]

With the actual firmware

What version are you running on the station? It is a pain to upgrade them btw

[kgoderis]

By the way, can someone give me a rules file for this?

I am using in conjunction with a Tesla. I can share that, but it depends a bit on what you want to achieve

[ghost]

Hi,

actual I'm on 2.5a3. It is a 2 minute install. You download the exe (yes, windows only :-() file and give it the IP. After that you can have a look at the web interface. This is now also showing all the information (firmware, MAC address, u1-u3, i1-i3, energy session, energy combined, ...)

[ghost]

I am owning an Tesla Model S since friday last week. And my thinking is, that I can set the "Maximum Supply Current" as a percent from the maximum current setting via DIP. So for example that I have 5KW into the grid, via SMA EM, then I can set (with a little bit buffer) 4KW into the car. This is around 6A on every Phase. I´m not sure if it is good to set this into the car, I think the API also doesn't allow this, but in the Keba. Because with two of them I can share the power, if the connection status from both is true. Then you can balance the load to more than one car in the dependency from you PV income.

[ghost]

please have a special look into the "operating state" and "firmware", this is openHAB not able to get with my versions

[kgoderis]

actual I'm on 2.5a3. It is a 2 minute install.

on the new hardware it is.... not the older ones, unfortunately ;-)

[kgoderis]

I am owning an Tesla Model S since friday last week. And my thinking is, that I can set the "Maximum Supply Current" as a percent from the maximum current setting via DIP. So for example that I have 5KW into the grid, via SMA EM, then I can set (with a little bit buffer) 4KW into the car. This is around 6A on every Phase. I´m not sure if it is good to set this into the car, I think the API also doesn't allow this, but in the Keba. Because with two of them I can share the power, if the connection status from both is true. Then you can balance the load to more than one car in the dependency from you PV income.

Welcome to the club :-) There is also a Tesla binding you can try out. I can share with you the Rules I run on the Tesla + Keba combination. I already drafted (but not coded yet) some algorithm to do the load balancing between multiple Keba's . Keba does sell a controller box to do that, but it can easily be programmed in a Rule in openHAB instead.

[ghost]

What newer HW? Do you own a P30? My is P20. I would appreciative any rules file.

[ghost]

The Tesla binding I have online. But how can I change Tesla charing power via the Tesla API? This is not available via Tesla App.

[kgoderis]

Indeed, you can't. You have to control the keba instead

Sent from my iPhone

On 16 Mar 2017, at 15:32, masterdiver notifications@github.com wrote:

The Tesla binding I have online. But how can I change Tesla charing power via the Tesla API? This is not available via Tesla App.

— You are receiving this because you commented. Reply to this email directly, view it on GitHub, or mute the thread.

[ghost]

How are you doing this at the moment?

[kgoderis]

@masterdiver With a complicated Rule. Drop me a note on karel dot Goderis at me dot com and I will send you over the Rules I use

[ghost]

it is on its way :D

[GernotHot]

Hi Karel,

my current project is to control up to four Keba P20 and P30 wallboxes with openHAB and I am facing the same problem.

[kgoderis]

It is on my todo list as i am in the process of adding another keba to my installation

Sent from my iPhone

On 5 May 2017, at 09:14, GernotHot notifications@github.com wrote:

Hi Karel,

my current project is to control up to four Keba P20 and P30 wallboxes with openHAB and I am facing the same problem.

— You are receiving this because you commented. Reply to this email directly, view it on GitHub, or mute the thread.

[GernotHot]

Great! I also added a bug report and also two feature requests to the KEBA-topic. If you need some support (e.g. wireshark traces), please send me a note!

[kgoderis]

This can be assigned to me

[GernotHot]

Hi Karel,

thanks for your fixes. I just configured two wallboxes:

Thing keba:kecontactp20:2 "Box 2"[ ipAddress="192.168.1.62", refreshInterval=1 

and a few items:

Number KebaU1_1 "KebaU1"  {channel="keba:kecontactp20:1:U1"}
Number KebaU2_1 "KebaU2"  {channel="keba:kecontactp20:1:U2"}
Number KebaU3_1 "KebaU3"  {channel="keba:kecontactp20:1:U3"}

and (in a seperate items-file):

Number KebaU1_2 "KebaU1"  {channel="keba:kecontactp20:2:U1"}
Number KebaU2_2 "KebaU2"  {channel="keba:kecontactp20:2:U2"}
Number KebaU3_2 "KebaU3"  {channel="keba:kecontactp20:2:U3"}

In the openhab.log (TRACE-loglevel for KEBA), I see

2017-05-29 15:12:39.951 [INFO ] [el.core.internal.ModelRepositoryImpl] - Loading model 'keba1.items'
2017-05-29 15:12:39.972 [INFO ] [el.core.internal.ModelRepositoryImpl] - Loading model 'keba2.items'
2017-05-29 15:12:41.593 [INFO ] [el.core.internal.ModelRepositoryImpl] - Loading model 'keba.things'
2017-05-29 15:12:42.448 [INFO ] [.dashboard.internal.DashboardService] - Started dashboard at /start
2017-05-29 15:12:42.858 [INFO ] [basic.internal.servlet.WebAppServlet] - Started Basic UI at /basicui/app
2017-05-29 15:12:42.969 [INFO ] [assic.internal.servlet.WebAppServlet] - Started Classic UI at /classicui/app
2017-05-29 15:12:43.100 [INFO ] [arthome.ui.paper.internal.PaperUIApp] - Started Paper UI at /paperui
2017-05-29 15:12:43.246 [INFO ] [ui.habmin.internal.servlet.HABminApp] - Started HABmin servlet at /habmin
2017-05-29 15:12:43.316 [INFO ] [panel.internal.HABPanelDashboardTile] - Started HABPanel at /habpanel
2017-05-29 15:12:43.321 [DEBUG] [org.openhab.binding.keba            ] - BundleEvent STARTING - org.openhab.binding.keba
2017-05-29 15:12:43.334 [DEBUG] [org.openhab.binding.keba            ] - BundleEvent STARTED - org.openhab.binding.keba
2017-05-29 15:12:43.352 [DEBUG] [org.openhab.binding.keba            ] - ServiceEvent REGISTERED - {org.eclipse.smarthome.core.thing.binding.ThingHandlerFactory}={component.name=org.openhab.binding.keba.internal.KebaHandlerFactory, component.id=202, service.id=324, service.bundleid=209, service.scope=bundle} - org.openhab.binding.keba
2017-05-29 15:12:43.502 [TRACE] [a.handler.KeContactBroadcastListener] - There are now 1 Keba handlers registered with the broadcast listener
2017-05-29 15:12:43.502 [DEBUG] [a.handler.KeContactBroadcastListener] - Starting the Keba broadcast listener
2017-05-29 15:12:43.505 [INFO ] [a.handler.KeContactBroadcastListener] - Listening for incoming data on /0:0:0:0:0:0:0:0:7090
2017-05-29 15:12:43.509 [TRACE] [inding.keba.handler.KeContactHandler] - Connecting the channel for /192.168.1.61:7090 
2017-05-29 15:12:43.529 [DEBUG] [inding.keba.handler.KeContactHandler] - Sending 'report 1' on the channel '/192.168.1.2:43521'->'/192.168.1.61:7090'
2017-05-29 15:12:43.530 [DEBUG] [inding.keba.handler.KeContactHandler] - Sending 'report 1' on the channel '/192.168.1.2:43521'->'/192.168.1.61:7090'
2017-05-29 15:12:43.532 [TRACE] [a.handler.KeContactBroadcastListener] - There are now 2 Keba handlers registered with the broadcast listener
2017-05-29 15:12:43.533 [TRACE] [inding.keba.handler.KeContactHandler] - Connecting the channel for /192.168.1.62:7090 
2017-05-29 15:12:43.534 [DEBUG] [inding.keba.handler.KeContactHandler] - Sending 'report 1' on the channel '/192.168.1.2:43521'->'/192.168.1.61:7090'

The BroadcastListener also receives notifications at the beginning:

2017-05-29 15:12:43.609 [DEBUG] [a.handler.KeContactBroadcastListener] - Received {
"ID": "1",
"Product": "KC-P30-ES240022-E0R",
"Serial": "16885123",
"Firmware":"P30 v 3.07.1a1 (170111-112920)",
"COM-module": 0,
"Sec": 419144
}
^@^@...^@^@ from /192.168.1.61:7090 on the broadcast listener port 
2017-05-29 15:12:43.744 [DEBUG] [a.handler.KeContactBroadcastListener] - Received {
"ID": "1",
"Product": "KC-P30-ES240022-E0R",
"Serial": "16885123",
"Firmware":"P30 v 3.07.1a1 (170111-112920)",
"COM-module": 0,
"Sec": 419144
}
^@^@...^@^@ from /192.168.1.61:7090 on the broadcast listener port 
2017-05-29 15:12:45.531 [DEBUG] [inding.keba.handler.KeContactHandler] - Sending 'report 2' on the channel '/192.168.1.2:43521'->'/192.168.1.61:7090'
2017-05-29 15:12:45.532 [DEBUG] [inding.keba.handler.KeContactHandler] - Sending 'report 2' on the channel '/192.168.1.2:43521'->'/192.168.1.61:7090'
2017-05-29 15:12:45.534 [DEBUG] [inding.keba.handler.KeContactHandler] - Sending 'report 2' on the channel '/192.168.1.2:43521'->'/192.168.1.61:7090'
2017-05-29 15:12:45.550 [DEBUG] [a.handler.KeContactBroadcastListener] - Received {
"ID": "2",
"State": 2,
"Error1": 0,
"Error2": 0,
"Plug": 0,
"AuthON": 0,
"Authreq": 0,
"Enable sys": 1,
"Enable user": 1,
"Max curr": 0,
"Max curr %": 1000,
"Curr HW": 0,
"Curr user": 6000,
"Curr FS": 0,
"Tmo FS": 0,
"Curr timer": 0,
"Tmo CT": 0,
"Setenergy": 0,
"Output": 1,
"Input": 0,
"Serial": "16885123",
"Sec": 419146
}
^@^@...^@^@ from /192.168.1.61:7090 on the broadcast listener port 

This works fine and I see some messages between the openhab-server (192.168.1.2) and the Box 1 (16885123, 192.168.1.61:7090). But then, I get the first response from Box 2 (17234123, 192.168.1.62:7090):

2017-05-29 15:12:47.895 [DEBUG] [a.handler.KeContactBroadcastListener] - Received {
"ID": "1",
"Product": "KC-P30-ES240022-E0R",
"Serial": "17234123",
"Firmware":"KEBA P30 v 3.02.4 (160226-065816)",
"Sec": 419148
}
^@^@^@^@ from /192.168.1.62:7090 on the broadcast listener port 

After receiving this message from the second box, no further responses are recognized:

2017-05-29 15:12:49.535 [DEBUG] [inding.keba.handler.KeContactHandler] - Sending 'report 2' on the channel '/192.168.1.2:43521'->'/192.168.1.61:7090'
2017-05-29 15:12:49.537 [DEBUG] [inding.keba.handler.KeContactHandler] - Sending 'report 2' on the channel '/192.168.1.2:43521'->'/192.168.1.61:7090'
2017-05-29 15:12:49.538 [DEBUG] [inding.keba.handler.KeContactHandler] - Sending 'report 2' on the channel '/192.168.1.2:55277'->'/192.168.1.62:7090'
2017-05-29 15:12:51.537 [DEBUG] [inding.keba.handler.KeContactHandler] - Sending 'report 3' on the channel '/192.168.1.2:43521'->'/192.168.1.61:7090'

...

2017-05-29 15:13:30.567 [DEBUG] [inding.keba.handler.KeContactHandler] - Sending 'report 1' on the channel '/192.168.1.2:43521'->'/192.168.1.61:7090'
2017-05-29 15:13:32.568 [DEBUG] [inding.keba.handler.KeContactHandler] - Sending 'report 2' on the channel '/192.168.1.2:55277'->'/192.168.1.62:7090'
2017-05-29 15:13:32.568 [DEBUG] [inding.keba.handler.KeContactHandler] - Sending 'report 2' on the channel '/192.168.1.2:43521'->'/192.168.1.61:7090'
2017-05-29 15:13:34.569 [DEBUG] [inding.keba.handler.KeContactHandler] - Sending 'report 3' on the channel '/192.168.1.2:43521'->'/192.168.1.61:7090'
2017-05-29 15:13:34.569 [DEBUG] [inding.keba.handler.KeContactHandler] - Sending 'report 3' on the channel '/192.168.1.2:55277'->'/192.168.1.62:7090'
2017-05-29 15:13:35.570 [DEBUG] [inding.keba.handler.KeContactHandler] - Sending 'report 1' on the channel '/192.168.1.2:55277'->'/192.168.1.62:7090'
2017-05-29 15:13:35.570 [DEBUG] [inding.keba.handler.KeContactHandler] - Sending 'report 1' on the channel '/192.168.1.2:43521'->'/192.168.1.61:7090'
2017-05-29 15:13:37.571 [DEBUG] [inding.keba.handler.KeContactHandler] - Sending 'report 2' on the channel '/192.168.1.2:43521'->'/192.168.1.61:7090'
2017-05-29 15:13:37.571 [DEBUG] [inding.keba.handler.KeContactHandler] - Sending 'report 2' on the channel '/192.168.1.2:55277'->'/192.168.1.62:7090'
2017-05-29 15:13:39.572 [DEBUG] [inding.keba.handler.KeContactHandler] - Sending 'report 3' on the channel '/192.168.1.2:55277'->'/192.168.1.62:7090'
2017-05-29 15:13:39.572 [DEBUG] [inding.keba.handler.KeContactHandler] - Sending 'report 3' on the channel '/192.168.1.2:43521'->'/192.168.1.61:7090'
2017-05-29 15:13:40.574 [DEBUG] [inding.keba.handler.KeContactHandler] - Sending 'report 1' on the channel '/192.168.1.2:43521'->'/192.168.1.61:7090'

(and so on)

The event.log also does stop recording messages from the boxes at the same time:

2017-05-29 15:12:43.482 [ThingAddedEvent           ] - Thing 'keba:kecontactp20:1' has been added.
2017-05-29 15:12:43.501 [ThingStatusInfoEvent      ] - 'keba:kecontactp20:1' updated: INITIALIZING
2017-05-29 15:12:43.506 [hingStatusInfoChangedEvent] - 'keba:kecontactp20:1' changed from UNINITIALIZED to INITIALIZING
2017-05-29 15:12:43.511 [ThingStatusInfoEvent      ] - 'keba:kecontactp20:1' updated: ONLINE
2017-05-29 15:12:43.512 [hingStatusInfoChangedEvent] - 'keba:kecontactp20:1' changed from INITIALIZING to ONLINE
2017-05-29 15:12:43.533 [ThingAddedEvent           ] - Thing 'keba:kecontactp20:2' has been added.
2017-05-29 15:12:43.534 [ThingStatusInfoEvent      ] - 'keba:kecontactp20:2' updated: ONLINE
2017-05-29 15:12:43.535 [ThingStatusInfoEvent      ] - 'keba:kecontactp20:2' updated: INITIALIZING
2017-05-29 15:12:43.535 [hingStatusInfoChangedEvent] - 'keba:kecontactp20:2' changed from UNINITIALIZED to INITIALIZING
2017-05-29 15:12:43.535 [hingStatusInfoChangedEvent] - 'keba:kecontactp20:2' changed from INITIALIZING to ONLINE
2017-05-29 15:12:45.562 [ItemStateEvent            ] - KebaState_1 updated to 2
2017-05-29 15:12:45.664 [ItemStateEvent            ] - KebaState_1 updated to 2
2017-05-29 15:12:45.771 [ItemStateEvent            ] - KebaState_1 updated to 2
2017-05-29 15:12:47.590 [ItemStateEvent            ] - KebaU1_1 updated to 0
2017-05-29 15:12:47.590 [ItemStateChangedEvent     ] - KebaU1_1 changed from NULL to 0
2017-05-29 15:12:47.598 [ItemStateEvent            ] - KebaU2_1 updated to 0
2017-05-29 15:12:47.600 [ItemStateChangedEvent     ] - KebaU2_1 changed from NULL to 0
2017-05-29 15:12:47.606 [ItemStateEvent            ] - KebaU3_1 updated to 0
2017-05-29 15:12:47.607 [ItemStateChangedEvent     ] - KebaU3_1 changed from NULL to 0
2017-05-29 15:12:47.691 [ItemStateEvent            ] - KebaU1_1 updated to 0
2017-05-29 15:12:47.693 [ItemStateEvent            ] - KebaU2_1 updated to 0
2017-05-29 15:12:47.695 [ItemStateEvent            ] - KebaU3_1 updated to 0
<eof>

According to the wireshark-traces, openhab is still sending "report 1", "report 2" and "report 3" messages to both boxes and also receives responses from the boxes

[kgoderis]

@GernotHot The thing I noticed when revisiting the code is that Keba is always responding with packets to port 7090 of the client, e.g. openHAB, instead of the originating source port. When you observe traffic in Wireshark, do you notice any traffic going to the originating source port at all? And when you say that it receives responses, that includes the answers to the "report 1" etc sent to 192.168.1.62:7090?

[GernotHot]

@kgoderis I can agree on this: all responses by the Keba-wallboxes are sent to 7090 instead of the originating port.

regarding your last question, my statement was unclear: openhab sends messages and the host receives responses and does not sent any "ICMP port unreachable" messages. The openhab.log does not mention any incoming packages.

[GernotHot]

@kgoderis @falkena any news regarding the problem? I am looking forward to test the fix ;-) ... and give you feedback

[kgoderis]

@GernotHot not yet, I am awaiting the installation of a second Keba at my home in order to test it.

[kgoderis]

I finally got my second Keba installed and I am able to test and fix things. Is there anything else that you guys saw that need to be added?

[kgoderis]

@GernotHot It seems that my P30 is only responding to "report 1", and not to "report 2" and "report 3" at all. Did you observe the same situation with your P30's?

[ghost]

Hi,

I have 2 P20 installed. Can't tell anything about P30.

Jens

Am 08.07.2017 um 15:17 schrieb Karel Goderis notifications@github.com:

@GernotHot It seems that my P30 is only responding to "report 1", and not to "report 2" and "report 3" at all. Did you observe the same situation with your P30's?

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or mute the thread.

[kgoderis]

@masterdiver My P20 is fine, although it is running an older firmware. Your P20s are running fine?

[GernotHot]

@kgoderis I tried both a P30x as well as a P30c: all of them are responding to a "report 3":

P30x:

echo "report 3" | netcat -p 7090 -u 192.168.1.60 7090
{
"ID": "3",
"U1": 0,
"U2": 0,
"U3": 0,
"I1": 0,
"I2": 0,
"I3": 0,
"P": 0,
"PF": 0,
"E pres": 0,
"E total": 3471,
"Serial": "17191234",
"Sec": 1533
}

P30c:

echo "report 3" | netcat -p 7090 -u 192.168.1.61 7090
{
"ID": "3",
"U1": 0,
"U2": 0,
"U3": 0,
"I1": 0,
"I2": 0,
"I3": 0,
"P": 0,
"PF": 0,
"E pres": 0,
"E total": 27646,
"Serial": "16881234",
"Sec": 1665
}

I tested it on all four boxes, which (currently) still have different FW-Releases (using "report 1") P30x: "Firmware":"P30 v 3.08.1 (170213-143648)" P30c: "Firmware":"P30 v 3.07.1a1 (170111-112920)" "Firmware":"KEBA P30 v 3.02.4 (160226-065816)" "Firmware":"P30 v 3.06.2a5 (161209-083000)"

[kgoderis]

@GernotHot For me the same simple test (to really compare things) is not working at all on the P30.

I have : "Firmware":"P30 v 3.08.4 (170307-132509)" on the P30c

btw, I have opened a trouble ticket with Keba

[kgoderis]

@GernotHot Is the current snapshot of the binding working for you?

I have no logical explanation as to why "report 1" does work, but "report 2" doesn't. Do you?

[GernotHot]

@kgoderis The snapshot works mostly with one single wallbox.

[GernotHot]

@kgoderis Hi Karel, did you receive any support or update from Keba?

[kgoderis]

@GernotHot Not yet. Anyways, even when I configure the binding to use a single KEBA, it still fails on the P30. I am quite convinced something is fishy wrt the firmware I have, and has nothing to do with the binding...

[GernotHot]

@kgoderis I agree on that. The described problem seems to be a wallbox-specific problem and not one of the mentioned binding-issues. I have a loose contact with Keba and tried to push your issue. How did you get in contact with Keba and did you receive something like a ticket number?

[kgoderis]

@GernotHot I was in touch with Peter from their support team, which forwarded the issue to the software team. There is a troubleticket whichI believe has #11616

In any case, the little netcat test is working for "report 1" and not for "report 3". For me it seems to be related to the specific FW version I am running. When I have some time I will try to downgrade the FW (assuming that older FW are available for download)

[ghost]

Hi guys,

sorry for the delay. Hard work in the real job :D

Is the problem with the report only P30 relevant? I installed openhab fresh and tried to test the new snapshot. First I run into trouble because of the different syntax. This needs to be updated (https://github.com/openhab/openhab2-addons/tree/master/addons/binding/org.openhab.binding.keba) when this version goes into production. This was the problem:

old: keba:kecontactp20: new: keba:kecontact:

So, if anybody run into this problem you need to adjust your config.

After that I have some trouble to get the Things initialized. Did some other run into the same problem? Any tipps?

[ghost]

Hi,

I see my problem right now. Thankfully there is a Mac everywhere :-) I went from Synology to an VM on my ESXi test environment. So all network bindings, e.g. Keba, Kostal, Netatmo, ... are not running. They are in an uninitialized state or offline.

So I have to thing about a new environment for my openhab. Did someone have a similar problem?

[ghost]

Update:

Still problems with the Keba Binding. Kostal is working on my Mac, but the Keba binding stays uninitialized. Version is 2.2.0 build 988

[ghost]

Update:

I´m now on a CentOS VM with the same Configuration (with the new syntax):

Thing keba:kecontact:1 [ipAddress="192.168.0.20", refreshInterval=15] Thing keba:kecontact:2 [ipAddress="192.168.0.21", refreshInterval=15]

Not uninitialized anymore but: Still nothing. No data from the boxes.

[ghost]

Update (last for today):

Uninitialized is back after a few seconds. So still no chance to control the Keba boxes with 2.2.0 snapshot. Worst then this, not one I can handle like in 2.0.

Edit:

After I deleted the two keba:kecontact Things in PaperUI and renamed my Things in my filesystem back to kebab:kecontactp20 I suddenly getting an undefined but online Item. I will test to rename all Items and come back.

Edit2:

After a reboot one Keba is available. But still only one. The second one activating in Things File I can't connect to anyone anymore. The things in Paper UI are also gone. So, still with one Keba.

[kgoderis]

@GernotHot Do you happen to have the binaries/zip files with the older firmwares? only the latest one is available for download

[kgoderis]

@masterdiver It seems to me that you are not having the latest version of the binding's .jar in your installation.

[ghost]

Can you provide me a link to the newest version? I found only the one bundled with Build 988, or the one openhab downloaded after installing that build.

[kgoderis]

org.openhab.binding.keba_2.1.0.201707241545.jar.zip

Here is the jar that will be available in the distro as soon as https://github.com/openhab/openhab2-addons/pull/2443 gets completed and accepted

[ghost]

Just putting it into addons folder? Do I need to delete something else? I installed on linux via Repo.

Tried to copy it to /opt/openhab2/addons and start is via bundle:start ... But it doesn't appear.

Edit: A restart of openhanded showed me the binding unter configuration. Another reconf to keba:kecontact let both things getting online.

But no data! -> To late for today. Have to rename the items as well. ->

1. Box sending Data
2. Box no Data

[ghost]

Where can I see what binding version is used? The old 2.2.0 Snapshot Binding is deleted, so in my mind he should use the one I placed in addons. But still not sure. Looks like month ago.

[kgoderis]

Where can I see what binding version is used? The old 2.2.0 Snapshot Binding is deleted, so in my mind he should use the one I placed in addons. But still not sure. Looks like month ago.

Just drop it in the add-ons folder

Do a "bundle:list -s | grep keba" in the openHAB console to check the bundles that provide the keba binding. Most likely you will have 2 of them, one from the add-ons folder, one from the distribution you installed (and for which you most likely added an entry in addons.cfg)

For the config part, you need to use the "kecontact" thing type as you figured out.