[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]

Hi,

thanks for the help with this command. But it looks like all is right:

openhab> bundle:list -s | grep keba 193 | Active | 80 | 2.1.0.201707241545 | Keba Binding | org.openhab.binding.keba

The bundled binding I uninstalled before config. And I think, that this is right binding because I have to use the recontact instead of kekontactp20 configuration.

Addons.cfg has no keba entry: cat /opt/openHAB2/conf/services/addons.cfg | grep keba (thanks for the syntax :D).

[ghost]

Hi,

Another small update: with build 989 from yesterday the addon wont load anymore. Is there a new version from the addon for download?

[ghost]

Hi again,

downgraded to the stable 2.1.0. All is working fine, except the jar file isn´t available in the addons folder. Is it necessary to have 2.2.0, or are there other dependencies?

[ghost]

Found in another threat where you are involved: Is the downloaded size correct:

-rw-r--r--. 1 openhab openhab 29736 24. Jul 16:47 org.openhab.binding.keba_2.1.0.201707241545.jar

[kgoderis]

@masterdiver My own env runs build 945. It is not necessary to have 2.2.0, but if you loose the add-ons folder while downgrading, you have to copy over the file again.

[ghost]

The file and my config stayed where it should be. Is the size of the jar file correct? Ok. Then I will updgrade to the 2.2 Snapshot again and see if it coming up.

[ghost]

Can´t find the version you are using anymore. But with the latest build from this morning I have the same problem. The binding isn't used although it is with the right credentials in the /opt/openHAB2/addons folder. Please test it one more on a fresh install. Maybe you have dependencies that are not any more in the build.

[GernotHot]

@kgoderis Hi Karel, downgrading the firmware usually does not work. But I made a test with the same firmware as yours (I upgraded one of my boxes) and here it works with the netcat-command. You probably tried to reinstall the most current firmware? And you also checked the correct dip-switches?

If it still does not work, imho the only way is to change the box. It should be covered under the warranty.

[kgoderis]

Can´t find the version you are using anymore.

https://github.com/openhab/openhab2-addons/issues/2038#issuecomment-317434385

[ghost]

The openHAB2 version I mean.

[kgoderis]

@GernotHot I solved the issue in the meantime. I opened the Keba, and the @#$&@! electrician that did the installation misconfigured the DIP switches, despite the fact that he assured* me that he did everything right.

Everything seems to be running very smoothly now with https://github.com/openhab/openhab2-addons/issues/2038#issuecomment-317434385

[ghost]

Hi,

sorry, but I´m not able to test anymore. The Keba add-on won´t come online. I also re uploaded it to the adding folder. Same problem with last Build 998.

Thing is still:

Thing keba:kecontact:1 and Thing keba:kecontact:2

bundle:list also didn't´t show me a Keba binding. The add-on isn't recognized via openHAB2.

[GernotHot]

@kgoderis Nice to hear, that it worked :) . I will try the new patch tomorrow morning and give you a feedback!

[GernotHot]

@kgoderis Hi Karel, I tried the integration of your last commit into my daily build 2.2 - but I failed. So, I use still the older (and buggy) version of your module and I were not able to test the new release.

What is missing for a deployment into the current daily built branch? Can I support you somehow?

[ghost]

@GernotHot Hi, this is my problem since I had it running for a short time with an older build. Tried different things, but also new copy, disabling old binding and so on didn't work to get the new binding to work.

[jonaswikstrom]

Hello

Sorry to intrude on this thread, it is maby a bit O.T but searching the web for my problem pointed me here. I have a P30 that only responds to "report 1" and not to "report 2" and "report 3" same behaviour described by you @kgoderis.

I cant find any problems with the configuration of my P30. The DIP DSW1.3 is switched on.

Any other information on how you got this to work @kgoderis?

My firmware by the way is 3.08.7

Thanks in advance and sorry for the OT.

[kgoderis]

@jonaswikstrom For me the issue was with the dip switch not being set correctly (I rebooted the KEBA after switching it to the correct position). Did you verify that this is also the case when using netcat on the command line (just to rule out that this is not an issue with the binding)?

[jonaswikstrom]

@kgoderis Thanks for the reply.

For me the dip seems to be correct, the DSW1 switch 3 is on.

echo "report 1" | netcat -p 7090 -u 192.168.1.122 7090

Results in correct JSON:

{ "ID": "1", "Product": "KC-P30-EC2201C2-E00-CW", "Serial": "17759635", "Firmware":"P30 v 3.08.7 (170404-153240)", "COM-module": 1, "Sec": 258938 }

echo "report 2" | netcat -p 7090 -u 192.168.1.122 7090

This command won't give a result at all.

[erik73]

@jonaswikstrom I have exactly the same problem as you. My P30 responds to ”report 1”. The other commands does not returen anything. Did you find a solution?

[erik73]

I found the problem. The dip switches are not the normal kind I was used to. To enable dip switch 3 for example, it should be pushed in at the top. To turn it off, you push it in at the bottom.

After sorting that out I can issue the UDP commands and get data in return!

[kgoderis]

@kaikreuzer this one can be closed

[gabrielklein]

I have the same issue with report 1, report 2, report 3

report 1 => works fine report 2, report 3 => don't work.

I've tried to change Dip 3 without success.

First I think it's just not available :( (Sadly not really well documented)

Energy monitor values shown as -,-- indicate : not available with this product

But I get the events "plug", "charging"... etc...

[MikeTheTux]

I had the same issue. Report 1 works, also with DIP3 OFF. The others not ...

After setting the DIP switch, you need to power OFF and ON the box. SW-reset via WebGUI seems not to be sufficient.

Via WebGUI DSW Settings 1.3 | ON | UDP interface (SmartHome) is enabled or UDP report 1 ("DIP-Sw1", "0x20" Bit set) you can see that the switch config was taken over.