Binding Request : Buderus web gateway

lukics · January 15, 2017, 12:53pm

nope

MarcoLanghans · January 15, 2017, 1:07pm

do you also use OH2? because maybe the Binding is not compatible to OH2 at the moment

Markinus · January 15, 2017, 1:32pm

It is working with 1.83 runtime installation without modifications. There are some preparation for OH2 but it’s not tested yet.

Markinus · January 15, 2017, 1:56pm

I’m using raspbian 8 on RP2.

lukics · January 15, 2017, 4:25pm

I am running ubuntu on RP3 with OH2 incremental built.

Any plans to make it somewhat compatible?

Markinus · January 15, 2017, 4:51pm

I have to look why it’s not working. What kind of error did you get?
The “Require-Bundle: org.slf4j.api error” was fixed, right?

lukics · January 15, 2017, 4:53pm

no, was not fixed by installing libslf4j-java through apt-get.
It is the same error obove

Markinus · January 15, 2017, 5:25pm

It’s the Logger. I will take a look to it.

Markinus · January 15, 2017, 5:30pm

Looks like the server plugin is missing. Loog here:
/usr/share/openhab/server/plugins
is there something like this:
org.slf4j.api_1.7.2.v20121108-1250.jar
?
This file is part of:
openhab-runtime: /usr/share/openhab/server/plugins/org.slf4j.api_1.7.2.v20121108-1250.jar

Markinus · January 15, 2017, 5:41pm

Take a look for this:
http://docs.openhab.org/developers/development/compatibilitylayer.html
There is a compatibility package. You can try it in such way. It will not work out of the box.

Do you really need OH2?

I will take a look to it but it will take some time.

lukics · January 15, 2017, 5:47pm

Yes I would like to stick to OH2.
I will try out the compatibility package.
There is no such file nor a folder matching under openhab2.

Strange is that I am already using some non-oh2 bindings.

Are you using some special stuff?

Markinus · January 15, 2017, 9:37pm

No, all stuff is usuall.
I looking now myself whether it works with OH2.
There is some documentation, like that:
http://docs.openhab.org/tutorials/migration.html

Markinus · January 15, 2017, 10:18pm

Ok, I found it. It was only a suboptimal configuration. Try this:

org.openhab.binding.km200-1.9.0-SNAPSHOT.jar

lukics · January 16, 2017, 6:45am

Thanks, I will try it out this evening.
I have another question:

I am not understanding this stament

There a two ways of de-/encryption password handling:

With the finished private key, here is this one required: 
 km200:PrivKey=0000FFFFEEEEDDDDCCCCBBBBAAAA999988887777666655554444333322221111 

--OR-- the binding is creating the key from the md5salt, the device and the private password. Here are all three required: 
 km200:MD5Salt=111122223333444455556666777788889999aaaabbbbccccddddeeeeffff0000 
 km200:GatewayPassword=AAAABBBBCCCCDDDD 
 km200:PrivatePassword=MYPASSWORD

I do not have a problem putting in the password in “km200:PrivatePassword”. Are the MD5Salt and GatewayPassword as they should or am I missing the point.
What stands GatewayPassword for, do not remember to set such one.

Markinus · January 16, 2017, 7:49am

The gateway password is this one from the device (sticker, without the “-”). But I dont’t think we should explain it here in detail because there are already much informations on other sites. Take a look the symcon haustechnik forum (KM200 thread) or the FHEM KM200 wiki page and the development thread. There is all this stuff explained.

MarcoLanghans · January 16, 2017, 12:09pm

Hi Markus,

i have enabled the compatibility Layer but i still have the same error with your new jar file

2017-01-16 13:06:36.884 [ERROR] [org.openhab.binding.km200 ] - FrameworkEvent ERROR - org.openhab.binding.km200
org.osgi.framework.BundleException: Could not resolve module: org.openhab.binding.km200 [175]
Unresolved requirement: Require-Bundle: org.slf4j.api

at org.eclipse.osgi.container.Module.start(Module.java:434)[org.eclipse.osgi-3.10.101.v20150820-1432.jar:]
at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1582)[org.eclipse.osgi-3.10.101.v20150820-1432.jar:]
at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1561)[org.eclipse.osgi-3.10.101.v20150820-1432.jar:]
at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.doContainerStartLevel(ModuleContainer.java:1533)[org.eclipse.osgi-3.10.101.v20150820-1432.jar:]
at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.dispatchEvent(ModuleContainer.java:1476)[org.eclipse.osgi-3.10.101.v20150820-1432.jar:]
at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.dispatchEvent(ModuleContainer.java:1)[org.eclipse.osgi-3.10.101.v20150820-1432.jar:]
at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230)[org.eclipse.osgi-3.10.101.v20150820-1432.jar:]
at org.eclipse.osgi.framework.eventmgr.EventManager$EventThread.run(EventManager.java:340)[org.eclipse.osgi-3.10.101.v20150820-1432.jar:]

Maybe i do anything wrong, so please wait for Slavisa’s reply

lukics · January 16, 2017, 1:10pm

Seems to load now:

2017-01-16 09:38:13.940 [INFO ] [.binding.km200.internal.KM200Binding] - Activated

Thanks

MarcoLanghans · January 16, 2017, 1:11pm

Hi Slavisa Lukic,

can you please share your steps to activate that binding with me, because it does not work inside my configuration

MarcoLanghans · January 16, 2017, 1:21pm

ok forget it, i just downloaded the jar file again and the binding start now

lukics · January 16, 2017, 1:37pm

Unfortunately I got an error at the end

2017-01-16 14:31:07.191 [INFO ] [b.binding.km200.internal.KM200Device] - 1;0;0;0;floatValue;/system/appliance/gasAirPressure;0.0;;;
2017-01-16 14:31:07.197 [INFO ] [b.binding.km200.internal.KM200Device] - 1;0;0;0;floatValue;/heatSources/flameCurrent;0.0;;;
2017-01-16 14:31:07.204 [ERROR] [org.apache.felix.configadmin        ] - [org.osgi.service.cm.ManagedService, org.osgi.service.event.EventHandler, id=273, bundle=9/file:/usr/share/openhab2/addons/org.openhab.binding.km200-1.9.0-SNAPSHOT.jar]: Unexpected problem updating configuration org.openhab.km200
java.lang.NullPointerException
	at org.openhab.binding.km200.internal.KM200Device.listAllServices(KM200Device.java:190)[9:org.openhab.binding.km200:1.9.0.201701152210]
	at org.openhab.binding.km200.internal.KM200Binding.updated(KM200Binding.java:194)[9:org.openhab.binding.km200:1.9.0.201701152210]
	at org.apache.felix.cm.impl.helper.ManagedServiceTracker.updated(ManagedServiceTracker.java:189)[3:org.apache.felix.configadmin:1.8.12]
	at org.apache.felix.cm.impl.helper.ManagedServiceTracker.updateService(ManagedServiceTracker.java:152)[3:org.apache.felix.configadmin:1.8.12]
	at org.apache.felix.cm.impl.helper.ManagedServiceTracker.provideConfiguration(ManagedServiceTracker.java:85)[3:org.apache.felix.configadmin:1.8.12]
	at org.apache.felix.cm.impl.ConfigurationManager$UpdateConfiguration.run(ConfigurationManager.java:1772)[3:org.apache.felix.configadmin:1.8.12]
	at org.apache.felix.cm.impl.UpdateThread.run0(UpdateThread.java:141)[3:org.apache.felix.configadmin:1.8.12]
	at org.apache.felix.cm.impl.UpdateThread.run(UpdateThread.java:109)[3:org.apache.felix.configadmin:1.8.12]
	at java.lang.Thread.run(Thread.java:745)[:1.8.0_111]

any guess things still will work?

the binding is loaded:

openhab> config:list | grep km200
Pid:            org.openhab.km200
BundleLocation: file:/usr/share/openhab2/addons/org.openhab.binding.km200-1.9.0-SNAPSHOT.jar
   service.pid = org.openhab.km200
openhab>