Binding Request : Buderus web gateway

Add-ons Bindings
312

Yes, i took the device and personal password from one working php script and put it into Andreas AES-Key generator. So it should be working.
I also red the documentation about the other options, but i am not sure where to get the MD5Salt.

best regards

313

Try it again and see if the generated key is the same:

https://ssl-account.com/km200.andreashahn.info/

I know itā€™s a pain but for cryptography keys I try not to use copy and paste as sometimes hidden characters end up in the string so try to copy it the old fashioned way in the cfg file

314

I have tried it several times with different browsers and encoding settings and couldnā€™t make it work. I have also tried the old 1.12.0-snapshot version, but get this result:

[ESH-org.openhab.binding.km200.discovery.KM200GatewayDiscovery-1] ERROR org.openhab.binding.km200.internal.KM200Comm - HTTP GET failed: HTTP/1.0 401 Unauthorized
315

@Markinus
Hello, Markus, can you help here, please?

316

HI,

do not use the config file. You have to set all parameters in the PaperUI (in the GUI inteface). Look for the thing and do the configuration on this place. Itā€™s a v2 bilding.

Markinus

317

Hi,

I had to replace the JSON parser in this binding (it was a requirement from the code review). Here is a new version. Please check it whether all stuff is still working as expected.
ā€“lik removedā€“

Greetings
Markus

1 Like
318

Hi Markus,
Is there something wrong with the link to your latest jar file. I have the following message:
image

Trying to install the latest binding again. In Openhab 2.3 all worked, now in latest unstable Openhab 2.4 version I seems to have things that donā€™t get initialised.

Regards,

Wim

319

Hi,
something is wrong on the download-server. I will check it.

Markus

Btw. Itā€™s compiled for 2.3, that could be the reason why it not works with 2.4.

1 Like
320

Hi Markus,

I cleared everything and reconfiguredā€¦ Current openhab version is 2.4.0-SNAPSHOT
Build #1298
And the good news is that everything seems to be working :wink:

Wim

321

Hi,

here is a new Version:

  • Replaced the IP-based gateway discovery method by a new MDNS method
    This Version will search and find the KMXXX device with a new UUID (the correct KM uuid). You have to change or replace your things and items.
    Please give me a feedback whether your device was found correctly.
    org.openhab.binding.km200-2.4.0-SNAPSHOT.jar

Important: It is now compiled for 2.4 so the filename changed. Delete the 2.3 bevore you copy the new one to the addons directory.

Markinus

P.S: Depending on your system could a installation of libjmdns-java be required.

1 Like
322

Markus,

binding-km1001 - 1.12.0 gives an error on my installation.

In the log Iā€™ve found:
2018-07-17 00:52:31.689 [INFO ] [.binding.km200.internal.KM200Binding] - Activated
2018-07-17 00:52:31.699 [INFO ] [.binding.km200.internal.KM200Binding] - Update KM200 Binding configuration, it takes a minuteā€¦
2018-07-17 00:52:31.706 [INFO ] [.binding.km200.internal.KM200Binding] - Starting communication testā€¦
2018-07-17 00:52:31.834 [INFO ] [.binding.km200.internal.KM200Binding] - Received dataā€¦
2018-07-17 00:52:31.838 [INFO ] [.binding.km200.internal.KM200Binding] - Test of the communication to the gateway was successfulā€¦
2018-07-17 00:52:31.840 [INFO ] [.binding.km200.internal.KM200Binding] - Init servicesā€¦
2018-07-17 00:52:34.905 [ERROR] [hab.binding.km200.internal.KM200Comm] - Parsingexception in JSON: A JSONObject text must begin with ā€˜{ā€™ at 1 [character 2 line 1] data: Ƃā„¢ĆƒĀ«aƂĀ”ƃā€™Ć‚ĀŗƂĀ¹ĆƒĀ®Ć‚Āŗā€™
2018-07-17 00:52:52.350 [INFO ] [b.binding.km200.internal.KM200Device] - ##################################################################
2018-07-17 00:52:52.354 [INFO ] [b.binding.km200.internal.KM200Device] - List of avalible services
2018-07-17 00:52:52.357 [INFO ] [b.binding.km200.internal.KM200Device] - readable;writeable;recordable;virtual;type;service;value;allowed;min;max
2018-07-17 00:52:52.361 [INFO ] [b.binding.km200.internal.KM200Device] - 1;0;1;0;floatValue;/heatSources/CHpumpModulation;0.0;;0.0;100.0
2018-07-17 00:52:52.363 [INFO ] [b.binding.km200.internal.KM200Device] - 1;0;0;0;refEnum;/recordings/heatingCircuits;;;
2018-07-17 00:52:52.366 [INFO ] [b.binding.km200.internal.KM200Device] - 1;0;0;0;refEnum;/dhwCircuits/dhw1/dhwTimePrograms;;;

Is there any way to get the parsingexeption out of the way? I guess that this error is the cause that it wonā€™t give me any ā€˜thingsā€™ in openhab2.

FYI: Iā€™m using your KM200-binding on a MBLAN2 (Junkers) but that should be the same/similar.

323

Hi Markinus,
after testing your latest version (which im compiled from your repo) and which didnā€™t work for me, I now found this Snapshot which works, so that I can add things.
But one problem persists: There seems to be something wrong with the Participant in the MDNS Service:

    2018-09-10 09:52:28.984 [ERROR] [y.mdns.internal.MDNSDiscoveryService] - Participant 'org.openhab.binding.km200.internal.discovery.KM200GatewayDiscoveryParticipant' threw an exception
java.lang.NullPointerException: null
	at org.openhab.binding.km200.internal.discovery.KM200GatewayDiscoveryParticipant.getThingTypeUID(KM200GatewayDiscoveryParticipant.java:99) [208:org.openhab.binding.km200:2.4.0.201806171947]
	at org.openhab.binding.km200.internal.discovery.KM200GatewayDiscoveryParticipant.getThingUID(KM200GatewayDiscoveryParticipant.java:67) [208:org.openhab.binding.km200:2.4.0.201806171947]
	at org.openhab.binding.km200.internal.discovery.KM200GatewayDiscoveryParticipant.createResult(KM200GatewayDiscoveryParticipant.java:51) [208:org.openhab.binding.km200:2.4.0.201806171947]
	at org.eclipse.smarthome.config.discovery.mdns.internal.MDNSDiscoveryService.considerService(MDNSDiscoveryService.java:237) [98:org.eclipse.smarthome.config.discovery.mdns:0.10.0.oh230]
	at org.eclipse.smarthome.config.discovery.mdns.internal.MDNSDiscoveryService.serviceResolved(MDNSDiscoveryService.java:229) [98:org.eclipse.smarthome.config.discovery.mdns:0.10.0.oh230]
	at javax.jmdns.impl.ListenerStatus$ServiceListenerStatus.serviceResolved(ListenerStatus.java:106) [28:javax.jmdns:3.5.2]
	at javax.jmdns.impl.JmDNSImpl$1.run(JmDNSImpl.java:887) [28:javax.jmdns:3.5.2]
	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) [?:?]
	at java.util.concurrent.FutureTask.run(FutureTask.java:266) [?:?]
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) [?:?]
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) [?:?]
	at java.lang.Thread.run(Thread.java:748) [?:?]

What do you think?

324

HI,

thx for this information. I think I wound and fixed it. I will upload a new version.

Markus

325

Hi,

here is a new Version:

Important: It is now compiled for 2.4 so the filename changed. Delete the 2.3 bevore you copy the new one to the addons directory.

Markinus

P.S: Depending on your system could a installation of libjmdns-java be required.

326

Hi,

did you try the new version?

Greetings
Markus

327

Yepā€¦ just testing it! Looks good so far :slight_smile: Thank you very much!
Looking forward to test switching Heating Modes with presence detection
Best
Clemens

328

The problem with MDNS Service is now fixed, unfortunately I now canā€™t add things (409 - Conflict). The logs show this error:

2018-09-12 23:19:53.383 [home.event.InboxAddedEvent] - Discovery Result with UID 'km200:sensor:758200495:temperatures' has been added.

==> /var/log/openhab2/openhab.log <==

2018-09-12 23:19:53.383 [INFO ] [g.discovery.internal.PersistentInbox] - Added new thing 'km200:sensor:758200495:temperatures' to inbox.

2018-09-12 23:19:53.393 [INFO ] [g.discovery.internal.PersistentInbox] - Added new thing 'km200:system:758200495:system' to inbox.

==> /var/log/openhab2/events.log <==

2018-09-12 23:19:53.395 [home.event.InboxAddedEvent] - Discovery Result with UID 'km200:system:758200495:system' has been added.

==> /var/log/openhab2/openhab.log <==

2018-09-12 23:20:03.687 [ERROR] [home.core.thing.binding.ThingFactory] - Thing factory (class org.openhab.binding.km200.internal.KM200HandlerFactory) returned null on create thing when it reports to support the thing type (km200:sensor).

2018-09-12 23:20:03.691 [WARN ] [g.discovery.internal.PersistentInbox] - Cannot create thing. No binding found that supports creating a thing of type km200:sensor.

2018-09-12 23:20:05.215 [INFO ] [ery.KM200GatewayDiscoveryParticipant] - Discovered a KMXXX gateway with name: 'iCom [gateway_758200495]' id: '758200495'
329

Hi Markus,

just want to begin with a big thanks for this work you are doing!:hugs::hugs:

I installed your latest Snapshot 2.4 and it works really good!
Just a little shortcoming on my side. I donā€™t get all the available items as channels.
For instance in the gateway thing Iā€™m missing Firmware Version, Hardware Version, Inst Write Access, ā€¦!

In other things I also donā€™t get all the available items like Bustype, ā€¦

I can see them also with parameters in the list of available items and they are all readable!
I found no way to add those missing channels to the things, and also with an item in my buderus.item config I cant get the values.

Do you have any suggestions?

Thanks for your help.

330

Hi!

I found this initialization problem. Now it should works like expected again.
Here is the new Version:
org.openhab.binding.km200-2.4.0-SNAPSHOT.jar

Important: It is now compiled for 2.4 so the filename changed. Delete the 2.3 bevore you copy the new one to the addons directory.

Markinus

P.S: Depending on your system could a installation of libjmdns-java be required.

331

Hi,

this missing values are all static. This is the reason why itā€™s not availible as a channel. You can find it in the KM50/100/200 Gateway properties. Press the ā€œShow Propertiesā€ link.

Greetings
Markus