I see the problem, seems you have a unknown type of service. This exception shouldn’t happen, it’s bug. I will fix it in the evening and upload a new version. (Nothing to do with OH2)
Is the biding working with this exception?
Or did it drop dead?
Same behaviour here. For the record: Running a KM200 against a Junker heating (Combined gas / heat pump device).
Before the list of services is dumped I see something like this:
2017-01-16 15:53:57.442 [ERROR] [.binding.km200.internal.KM200Binding] - Couldn't init service: DHWCIRCUITS
2017-01-16 15:54:08.363 [ERROR] [.binding.km200.internal.KM200Binding] - Couldn't init service: HEATINGCIRCUITS
Then de dump, followed by the error:
2017-01-16 15:54:30.823 [INFO ] [b.binding.km200.internal.KM200Device] - ##################################################################
2017-01-16 15:54:30.825 [INFO ] [b.binding.km200.internal.KM200Device] - List of avalible services
2017-01-16 15:54:30.826 [INFO ] [b.binding.km200.internal.KM200Device] - readable;writeable;recordable;virtual;type;service;value;allowed;min;max
2017-01-16 15:54:30.828 [INFO ] [b.binding.km200.internal.KM200Device] - 1;0;0;0;refEnum;/recordings/heatSources/hs1;;;
2017-01-16 15:54:30.830 [INFO ] [b.binding.km200.internal.KM200Device] - 1;0;0;0;floatValue;/heatSources/CHpumpModulation;41.0;;;
2017-01-16 15:54:30.832 [INFO ] [b.binding.km200.internal.KM200Device] - 1;0;0;0;refEnum;/dhwCircuits/dhw1/switchPrograms;;;
2017-01-16 15:54:30.833 [INFO ] [b.binding.km200.internal.KM200Device] - 1;0;0;0;refEnum;/recordings/heatingCircuits;;;
2017-01-16 15:54:30.835 [INFO ] [b.binding.km200.internal.KM200Device] - 1;0;1;0;floatValue;/heatSources/actualCHPower;10.0;;;
2017-01-16 15:54:30.836 [INFO ] [b.binding.km200.internal.KM200Device] - 1;0;0;0;floatValue;/heatSources/nominalDHWPower;24.0;;;
2017-01-16 15:54:30.838 [INFO ] [b.binding.km200.internal.KM200Device] - 1;1;0;0;stringValue;/gateway/instWriteAccess;off;off|on;;
2017-01-16 15:54:30.840 [INFO ] [b.binding.km200.internal.KM200Device] - 1;0;0;0;stringValue;/heatSources/hs1/flameStatus;on;off|on;;
2017-01-16 15:54:30.841 [INFO ] [b.binding.km200.internal.KM200Device] - 1;0;0;0;refEnum;/heatingCircuits/hc1;;;
2017-01-16 15:54:30.843 [INFO ] [b.binding.km200.internal.KM200Device] - 1;0;0;0;floatValue;/system/appliance/workingTime/centralHeating;623087.0;;;
2017-01-16 15:54:30.844 [INFO ] [b.binding.km200.internal.KM200Device] - 0;0;0;0;;/gateway/knxPassword;;;
2017-01-16 15:54:30.845 [INFO ] [b.binding.km200.internal.KM200Device] - 1;0;0;0;refEnum;/recordings/system/sensors/temperatures;;;
2017-01-16 15:54:30.846 [INFO ] [b.binding.km200.internal.KM200Device] - 1;0;0;0;floatValue;/system/sensors/temperatures/return;-3276.8;;;
2017-01-16 15:54:30.848 [INFO ] [b.binding.km200.internal.KM200Device] - 1;0;0;0;refEnum;/dhwCircuits/dhw1;;;
2017-01-16 15:54:30.849 [INFO ] [b.binding.km200.internal.KM200Device] - 0;0;0;0;;/gateway/update/request;;;
2017-01-16 15:54:30.850 [INFO ] [b.binding.km200.internal.KM200Device] - 1;0;0;0;refEnum;/system/holidayModes;;;
2017-01-16 15:54:30.851 [INFO ] [b.binding.km200.internal.KM200Device] - 1;0;0;0;floatValue;/heatSources/workingTime/totalSystem;910245.0;;;
2017-01-16 15:54:30.853 [INFO ] [b.binding.km200.internal.KM200Device] - 1;0;0;0;floatValue;/heatSources/hs1/nominalDHWPower;24.0;;;
2017-01-16 15:54:30.854 [INFO ] [b.binding.km200.internal.KM200Device] - 1;0;0;0;refEnum;/gateway;;;
2017-01-16 15:54:30.855 [INFO ] [b.binding.km200.internal.KM200Device] - 1;1;0;0;stringValue;/gateway/instAccess;off;off|on;;
2017-01-16 15:54:30.856 [INFO ] [b.binding.km200.internal.KM200Device] - 1;0;0;0;floatValue;/system/appliance/powerSetpoint;79.0;;;
2017-01-16 15:54:30.857 [INFO ] [b.binding.km200.internal.KM200Device] - 1;1;0;0;floatValue;/system/heatSources/hs1/energyReservoir;0.0;;;
2017-01-16 15:54:30.859 [INFO ] [b.binding.km200.internal.KM200Device] - 1;0;0;0;stringValue;/system/systemType;NSC_ICOM_GATEWAY;;;
2017-01-16 15:54:30.862 [INFO ] [b.binding.km200.internal.KM200Device] - 1;0;0;0;floatValue;/heatSources/hs1/CHpumpModulation;45.0;;;
2017-01-16 15:54:30.863 [INFO ] [b.binding.km200.internal.KM200Device] - 1;0;0;0;yRecording;/recordings/heatSources/actualDHWPower;;;
2017-01-16 15:54:30.864 [INFO ] [b.binding.km200.internal.KM200Device] - 1;0;0;0;floatValue;/system/appliance/gasAirPressure;0.0;;;
2017-01-16 15:54:30.865 [INFO ] [b.binding.km200.internal.KM200Device] - 1;0;0;0;floatValue;/heatSources/flameCurrent;27.1;;;
2017-01-16 15:54:30.868 [ERROR] [org.apache.felix.configadmin ] - [org.osgi.service.cm.ManagedService, org.osgi.service.event.EventHandler, id=316, bundle=207/http://www.markinus.de/download/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)[207:org.openhab.binding.km200:1.9.0.201701152210]
at org.openhab.binding.km200.internal.KM200Binding.updated(KM200Binding.java:194)[207: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$ManagedServiceUpdate.provide(ConfigurationManager.java:1461)[3:org.apache.felix.configadmin:1.8.12]
at org.apache.felix.cm.impl.ConfigurationManager$ManagedServiceUpdate.run(ConfigurationManager.java:1417)[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]
Maybe this helps in narrowing it down.
Ok, exception should be fixed. Give me a info whether this version works.
–link removed–
Hi,
it starts now without any error message, but if have a Problem with the message decoding.
I have created a km200.cfg in …services\ but it seems that this is not correct. So can you please tell me the solution for my problem (sorry if i must ask such a basic question but this is my first 1.9 binding in OH2)
Issue is solved, there was a typo inside the config
Works like a charm ! Thanks a lot, will dive deeper into this in the next days.
Totally replaces my previous python scripting.
As the binding throws out a list of supported properties this would be an ideal candidate for an OH2 binding
supporting discovery.
Great stuff !
Hi,
Start up with an ERROR:
2017-01-16 19:00:53.844 [INFO ] [internal.KM200GenericBindingProvider] - Bind Config: service:/heatSources/actualCHPower
2017-01-16 19:00:53.855 [INFO ] [internal.KM200GenericBindingProvider] - Bind Config: service:/heatSources/CHpumpModulation
2017-01-16 19:00:54.142 [INFO ] [.binding.km200.internal.KM200Binding] - Activated
2017-01-16 19:00:54.151 [INFO ] [.binding.km200.internal.KM200Binding] - Update KM200 Binding configuration, it takes a minute....
2017-01-16 19:00:54.164 [INFO ] [.binding.km200.internal.KM200Binding] - Starting communication test..
2017-01-16 19:00:54.311 [INFO ] [.binding.km200.internal.KM200Binding] - Received data..
2017-01-16 19:00:54.334 [INFO ] [.binding.km200.internal.KM200Binding] - Test of the communication to the gateway was successful..
2017-01-16 19:00:54.341 [INFO ] [.binding.km200.internal.KM200Binding] - Init services..
2017-01-16 19:01:02.577 [ERROR] [.binding.km200.internal.KM200Binding] - Couldn't init service: HEATINGCIRCUITS
2017-01-16 19:01:27.394 [INFO ] [b.binding.km200.internal.KM200Device] - ##################################################################
Is this something to take care about?
Items created are getting values though.
No, I don’t think so. I think I will change it to a warning.
There is a lot of root services known. Seems that in your heating system configuration doesn’t known the root service path “heatingCircuits” (or it’s something different).
Do you have in the EasyControl app a “HeatingCircuit 1” ? (Press “I” and then “SystemInfo” or in History/Switching Points)
Thanks, and yes, I will port it to OH2. But it will take some time…weeks…
I have “Heating Circle 1”.
Here my log output:
Is there a source to find a more explaining description of the services. I found one (2nd tab of the gsheet) but this one does not match to my services in the log.
Additionally there are 2 services which return negative values (see gsheet):
/system/sensors/temperatures/return
/system/sensors/temperatures/chimney
Is this a bug?
Thanks for the great work.
Hmm, OK, I have to look to this. I thing there is something different in the data structures.
I need more debug informations:
- Stop Openahab 2
- Enable debug outputs for OH2
- Delete(Move) /var/log/openhab2/openhab.log
- Start Openhab 2
- Wait till all services are listet (There are some outputs more in the file)
- Send to me the /var/log/openhab2/openhab.log file.
Thanks.
have set:
openhab> log:set DEBUG org.openhab.km200
openhab> log:set DEBUG b.binding.km200.internal.KM200Device
still do not see debug information, when reloading binding.
done somthing wrong?
It’s was not correct, try:
log:set DEBUG org.openhab.binding.km200
Sent the log by private message
Ok, thanks. I found the difference. The data structure for setpoints is a bit different.
I think I will fix it today and upload a new version.
There is also something else:
2017-01-17 16:08:48.130 [ItemStateChangedEvent ] - LivingRoomHumi changed from 41.00 to 40.00
2017-01-17 16:09:06.537 [ItemStateChangedEvent ] - HeatingSupplyTemp changed from 11.1000003814697265625 to 10.8999996185302734375
2017-01-17 16:09:19.083 [ItemStateChangedEvent ] - StudyRoomACTemperature changed from 15.5 to 16.0
2017-01-17 16:09:33.287 [ItemStateChangedEvent ] - GuestRoomACTemperature changed from 14.5 to 15.0
2017-01-17 16:09:46.703 [ItemStateChangedEvent ] - BedRoomTemp changed from 10.60 to 10.90
2017-01-17 16:10:22.006 [ItemStateChangedEvent ] - StudyRoomTemp changed from 10.50 to 10.70
2017-01-17 16:10:33.853 [ItemStateChangedEvent ] - GuestRoomACTemperature changed from 15.0 to 15.5
2017-01-17 16:11:06.559 [ItemStateChangedEvent ] - HeatingSupplyTemp changed from 10.8999996185302734375 to 11.1000003814697265625
2017-01-17 16:11:11.687 [ItemStateChangedEvent ] - GarageTemp changed from 8.50 to 8.60
2017-01-17 16:11:20.199 [ItemStateChangedEvent ] - BedroomRoomACTemperature changed from 16.0 to 16.5
2017-01-17 16:11:34.442 [ItemStateChangedEvent ] - GuestRoomACTemperature changed from 15.5 to 15.0
2017-01-17 16:11:42.465 [ItemStateChangedEvent ] - GuestRoomTemp changed from 11.10 to 11.40
2017-01-17 16:12:06.548 [ItemStateChangedEvent ] - HeatingSupplyTemp changed from 11.1000003814697265625 to 10.8999996185302734375
2017-01-17 16:12:20.813 [ItemStateChangedEvent ] - StudyRoomACTemperature changed from 16.0 to 16.5
2017-01-17 16:12:34.953 [ItemStateChangedEvent ] - BedRoomTemp changed from 10.90 to 11.10
2017-01-17 16:12:35.056 [ItemStateChangedEvent ] - GuestRoomACTemperature changed from 15.0 to 15.5
2017-01-17 16:12:35.061 [ItemStateChangedEvent ] - BedRoomHumi changed from 40.00 to 39.00
2017-01-17 16:13:21.002 [ItemStateChangedEvent ] - StudyRoomTemp changed from 10.70 to 10.90
2017-01-17 16:13:35.188 [ItemStateChangedEvent ] - GarageTemp changed from 8.60 to 8.70
some of the values have a decimal value indicating that there is rounding or 0.000001 error in the values.
Ok, this error should be fixed. Give me a info whether this version works, you should see now all switching points.
–link removed–
great start to get the buderus gateway directly integrated into openhab 
I played a bit around with the plugin and figured out that in my environment not all available variables from a specific API services are gathered, when it get’s to an http 500 error.
Concrete example: I was missing /system/sensors/temperatures/outdoor_t1, which I am able to retrieve with a javascript, hence I turned on the DEBUG log for the plugin and saw that gathering the services from /system is aborted after getting an http 500 error:
2017-01-17 18:04:59.129 [DEBUG] [nding.km200.internal.KM200Comm] - Init: /system/info
2017-01-17 18:04:59.268 [DEBUG] [nding.km200.internal.KM200Comm] - 0
2017-01-17 18:04:59.268 [DEBUG] [nding.km200.internal.KM200Comm] - 0
2017-01-17 18:04:59.269 [DEBUG] [nding.km200.internal.KM200Comm] - Typ: systeminfo
2017-01-17 18:04:59.269 [DEBUG] [nding.km200.internal.KM200Comm] - initDevice: type systeminfo: {"id":"/system/info","type":"systeminfo","recordable":0,"writeable":
0,"values":[{"Tok":"8","Id":"123","Ver":"04.09","No":"383733373931323330413031313630353038313000FFFFFFFFFFFF"},{"Tok":"16","Id":"158","Ver":"NF11.09","No":"32353330
3631393136353334323737333831313131313200FFFFFF"},{"Tok":"9","Id":"125","Ver":"NF01.06","No":"000000000000000000000000000000000000000000000000000000"}]}
2017-01-17 18:04:59.269 [DEBUG] [nding.km200.internal.KM200Comm] - Init: /system/minOutdoorTemp
2017-01-17 18:05:07.508 [ERROR] [nding.km200.internal.KM200Comm] - HTTP GET failed: HTTP/1.0 500 Internal Server Error
The http error 500 is happen simetimes. In usuall use it’s not critical but isn’t not good if it happends on init of the binding.
Simple restart OpenHAB again. Usually it shouldn’t happen often. I think about this stuff, what to do is such case. But in the moment simple restart it and your sensor should appear.
looks good, no error.
Are the values where e.g. chimney temperature is negive comming from the gateway or is there an issue with the binding?
Are such figures alsocomming from the gateway or a conversion issue?
2017-01-17 18:53:45.262 [ItemStateChangedEvent ] - HeatingOutsideTemp changed from -5.30000019073486328125 to -5.599999904632568359375