Wow that was fast. I‘ll try. Thanks a lot.
Hi Markus,
Thanks for that addon, it’s working great for me!
I’ve got a question: Is it possible to get the values of “PROTECTED” parameters? I’d be interested in values like
0;0;0;0;$$PROTECTED$$;/heatSources/dhw/energyMonitoring/outputProduced;;;
Those values seem to exist in the gateway, the question is what “protected” means and if it’s maybe still possible to read it somehow.
Thanks a lot!
hubsif.
Edit: accidentally posted in German.
Hi,
I have no Idea how to read that. Maybe you have to auth to the device in some way. I don’t know, I have no documentation how to do that. If someone has some informations then I could change it…
Markus
I have upgraded to the newest version and Openhab is running in a docker container with the -e CRYPTO_POLICY=unlimited \option. At the moment i am getting some values, but a lot values are missing, like shown here:
Has anyone an idea how to fix this?
thanks in advance
Norbert
I just installed the KM200 binding, but the configuration failed with:
2018-11-16 19:42:44.373 [INFO ] [.binding.km200.internal.KM200Binding] - Update KM200 Binding configuration, it takes a minute....
2018-11-16 19:42:44.376 [INFO ] [.binding.km200.internal.KM200Binding] - Starting communication test…
2018-11-16 19:42:44.427 [INFO ] [.binding.km200.internal.KM200Binding] - Received data…
2018-11-16 19:42:44.428 [ERROR] [org.apache.felix.configadmin ] - [org.osgi.service.cm.ManagedService, org.osgi.service.event.EventHandler, id=708, bundle=230/mvn:org.openhab.binding/org.openhab.binding.km200/1.12.0]: Unexpected problem updating configuration org.openhab.km200
java.lang.NullPointerException: charsetName
at java.lang.String.(String.java:424) [?:?]
at java.lang.String.(String.java:491) [?:?]
at org.openhab.binding.km200.internal.KM200Comm.decodeMessage(KM200Comm.java:263) [230:org.openhab.binding.km200:1.12.0]
at org.openhab.binding.km200.internal.KM200Binding.updated(KM200Binding.java:161) [230:org.openhab.binding.km200:1.12.0]
at org.apache.felix.cm.impl.helper.ManagedServiceTracker.updated(ManagedServiceTracker.java:189) [8:org.apache.felix.configadmin:1.8.16]
at org.apache.felix.cm.impl.helper.ManagedServiceTracker.updateService(ManagedServiceTracker.java:152) [8:org.apache.felix.configadmin:1.8.16]
at org.apache.felix.cm.impl.helper.ManagedServiceTracker.provideConfiguration(ManagedServiceTracker.java:85) [8:org.apache.felix.configadmin:1.8.16]
at org.apache.felix.cm.impl.ConfigurationManager$UpdateConfiguration.run(ConfigurationManager.java:1792) [8:org.apache.felix.configadmin:1.8.16]
at org.apache.felix.cm.impl.UpdateThread.run0(UpdateThread.java:141) [8:org.apache.felix.configadmin:1.8.16]
at org.apache.felix.cm.impl.UpdateThread.run(UpdateThread.java:109) [8:org.apache.felix.configadmin:1.8.16]
at java.lang.Thread.run(Thread.java:748) [?:?]
Does anyone know how to solve this?
Thanks in advance
Did you find a solution for this “Brigde missing” issue?
EDIT:
Never mind.
A simple restart of the binding in karaf solved the issue. 
Yes, the problem was the missing JCE.
In my case this wasn’t the problem because I solved this long time ago.
But thanks for your quick response.
I am still often impressed about the speed of help in this forum
All,
yesterday I switched from the “old” km200 1.x to the actual km200 2.4 SNAPSHOT
I have one sync problem though:
I use the following items:
Number Heat_HzSollDay "Tag" {channel="km200:heatingCircuit:xxx:hc1:temperatureLevels_day"}
Number Heat_HzSollNight "Nacht" {channel="km200:heatingCircuit:xxx:hc1:temperatureLevels_night"}
Number Heat_HzSoll "Ziel" {channel="km200:heatingCircuit:xxx:hc1:temperatureRoomSetpoint"}
When I switch at the wall-mounted official control (RC-35) I can change the setpoint for the current mode (day or night). It will not be reflected in one of the items above.
If I send a command to e.g. the Day (Tag) temperature, it’s not reflected in the RC-35.
Was there a change in the handling between 1.x and 2.4 ?
Hi,
the delay before the binding is sending it to the device is a bit longer. It can take some minutes. Change it and wait 2-3 Minutes. Then it should change on the RC-35. I had to change it for better performance and stability.
Markus
Thanks for your quick response.
I will be more patient and will try again 
Hi all,
this binding is merged now into the master and will be availible in the 2.4 release.
Thank you for testing!
Greetings
Markus
Great. I installed M8 yesterday and took the binding from there. Worked smooth.
Thanks for your work and providing this to the community!
I am trying to switch from the 1.x binding to the new 2.x binding. I am running openhab 2.4 Milestone 7 with the KM200 Binding from October, I could not find a newer one
I get the following error during startup. Maybe this is already fixed, as I am using a version of the binding that is 2 Month old?
2018-12-15 17:33:45.367 [ERROR] [nal.common.AbstractInvocationHandler] - An error occurred while calling method 'ThingHandler.initialize()' on 'org.openhab.binding.km200.handler.KM200ThingHandler@6bb648d7': Duplicate channels km200:heatingCircuit:KM100:1:temperatureLevels_night
java.lang.IllegalArgumentException: Duplicate channels km200:heatingCircuit:KM100:1:temperatureLevels_night
at org.eclipse.smarthome.core.thing.util.ThingHelper.ensureUniqueChannels(ThingHelper.java:159) ~[?:?]
at org.eclipse.smarthome.core.thing.util.ThingHelper.ensureUniqueChannels(ThingHelper.java:135) ~[?:?]
at org.eclipse.smarthome.core.thing.binding.builder.ThingBuilder.withChannels(ThingBuilder.java:85) ~[?:?]
at org.openhab.binding.km200.handler.KM200ThingHandler.initialize(KM200ThingHandler.java:265) ~[?:?]
at sun.reflect.GeneratedMethodAccessor93.invoke(Unknown Source) ~[?:?]
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[?:?]
at java.lang.reflect.Method.invoke(Method.java:498) ~[?:?]
at org.eclipse.smarthome.core.internal.common.AbstractInvocationHandler.invokeDirect(AbstractInvocationHandler.java:153) [101:org.eclipse.smarthome.core:0.10.0.oh240M7]
at org.eclipse.smarthome.core.internal.common.Invocation.call(Invocation.java:53) [101:org.eclipse.smarthome.core:0.10.0.oh240M7]
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) [?:?]
2018-12-15 17:33:45.389 [ERROR] [core.thing.internal.ThingManagerImpl] - Exception occurred while initializing handler of thing 'km200:heatingCircuit:KM100:1': Duplicate channels km200:heatingCircuit:KM100:1:temperatureLevels_night
java.lang.IllegalArgumentException: Duplicate channels km200:heatingCircuit:KM100:1:temperatureLevels_night
at org.eclipse.smarthome.core.thing.util.ThingHelper.ensureUniqueChannels(ThingHelper.java:159) ~[?:?]
at org.eclipse.smarthome.core.thing.util.ThingHelper.ensureUniqueChannels(ThingHelper.java:135) ~[?:?]
at org.eclipse.smarthome.core.thing.binding.builder.ThingBuilder.withChannels(ThingBuilder.java:85) ~[?:?]
at org.openhab.binding.km200.handler.KM200ThingHandler.initialize(KM200ThingHandler.java:265) ~[?:?]
at sun.reflect.GeneratedMethodAccessor93.invoke(Unknown Source) ~[?:?]
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[?:?]
at java.lang.reflect.Method.invoke(Method.java:498) ~[?:?]
at org.eclipse.smarthome.core.internal.common.AbstractInvocationHandler.invokeDirect(AbstractInvocationHandler.java:153) [101:org.eclipse.smarthome.core:0.10.0.oh240M7]
at org.eclipse.smarthome.core.internal.common.Invocation.call(Invocation.java:53) [101:org.eclipse.smarthome.core:0.10.0.oh240M7]
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) [?:?]
My things configuration:
Bridge km200:kmdevice:KM100 "Buderus KM100" @ "Heizungskeller" [ privateKey= "12345", maxnbrrepeats=10.0, readDelay=100, refreshInterval=30, maxNbrRepeats=10, ip4Address="192.168.123.45", refreshinterval=30.0, readdelay=100.0 ] {
appliance 1 "appliance"
dhwCircuit 1 "dhwCircuit"
gateway 1 "gateway"
heatingCircuit 1 "HC1"
heatSource 1 "heatSource"
holidayMode 1 "holidayMode"
sensor 1 "sensors"
system 1 "system"
notification 1 "notification"
switchProgram 1 "switchProgram"
}
By the way: What does the 1 in “appliance 1 “appliance”” stand for, could not figure out this…
Thanks for your help!
Hi,
you have to delete the old V1 config and add the things from the new binding only. The best way is with PaperUI.
Markus
Hello @juelicher,
maybe checking the channels and the links in karaf will help - it happened to me that there was stuff left over from previous version (not only with the km200 binding, so not specific to it).
First check you addons-folder that no other version is present - remove it if necessary.
Then I would uninstall the binding, remove the items in you items files (if any), go to the karaf-console, check that the binding is really gone, drop all still available km200 things, channels, links etc…
Stop the openhab2 service.
After this clear the cache.
Then reboot.
Add the binding in PaperUI, let it figure out the gateway, set the parameters (encryption key).
Leave it alone for few minutes to get things started, then check the things it discovered and activate them.
This is what helped me during testing of various version of the binding - a clean starting point is always good basis for solid results and further investigations.
The binding is running here 24/7 for some weeks now, I have no serious issues with it.
You´ll succeed, I´m sure.
Best Regards,
Oggerschummer
Thanks for your advice!
Today I updated openHAB to the 2.4.0 Release version an did a clean reinstall of the KM200 2.x binding. But the problem persists. As soon as I add to the line "heatingCircuit 1 “HC1” to the km200.things configuration I get the “Duplicate channels km200:heatingCircuit:KM100:1:temperatureLevels_night” error during startup. In this case no channels for the heating circuit are shown in the Paper UI.
In case it might help to pinpoint the problem, here is my output from the old 1.x binding during startup regarding “temperatureLevels/night”:
[b.binding.km200.internal.KM200Device] - 1;1;1;0;floatValue;/heatingCircuits/hc4/temperatureLevels/night;17.0;;5.0;29.0
[b.binding.km200.internal.KM200Device] - 1;1;1;0;floatValue;/heatingCircuits/hc1/temperatureLevels/night;16.5;;5.0;29.0
[b.binding.km200.internal.KM200Device] - 1;1;1;0;floatValue;/heatingCircuits/hc2/temperatureLevels/night;19.0;;5.0;29.0
[b.binding.km200.internal.KM200Device] - 1;1;1;0;floatValue;/heatingCircuits/hc3/temperatureLevels/night;17.0;;5.0;29.0
@Markinus
I just upgraded from OH 2.3 with old km1001 binding to OH 2.4 with the new km200 v2 binding.
First of all: Thanks for your great work. The new binding looks much cleaner and the autodetection of things is great (except that I’m an old man preferring to work with text files instead of clicking in a GUI, but that’s my personal problem, not your fault).
It wasn’t trivial to migrate all existing items to the new syntax, but with some manual tweaking after trying to automatically convert the items it now seems to work as expected.
But I didn’t understand one change between v1 and v2 and this is the data type of the gateway DateTime, which was a DateTime type in the old binding but is a string in the new one. Is this really intended or is it a bug?
I’d prefer to have a DateTime here, since it allows me to format it in the sitemap for human readability. For setting this item it wasn’t a big problem to change my daily rule to write
now.toString("yyyy-MM-dd'T'HH:mm:ss")
into the item to update the clock of my KM100.
Greetings
Roland
1 Like
Hi,
the new plugin works great! Thanks!
Does anyone have a complete example to design a graphical user interface in Habpanel?