2018-10-05 09:46:31.835 [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:holidayModes).
2018-10-05 09:46:31.835 [WARN ] [g.discovery.internal.PersistentInbox] - Cannot create thing. No binding found that supports creating a thing of type km200:holidayModes.
==> /var/log/openhab2/
I just installed the latest snapshot. KM200 Gateway appeared in the inbox. I did the configuration of IP/Private Key via PaperUi. But the item stuck at „offline configuration error“ no bridge configured.
Any idea?
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…
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:
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
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 ?
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.