Hello,
it would be possible to find the data of consumed energy ?
thanks
Tested again, I see some errors in the log when checking the holiday modes (No HTTP500 errors):
Example:
2018-01-12 10:25:04.200 [DEBUG] [ng.km200.handler.KM200GatewayHandler] - Checking: km200:holidayModes:4072950248:hm4:startStop Root: #system#holidayModes#hm4#startStop
2018-01-12 10:25:04.203 [DEBUG] [hab.binding.km200.internal.KM200Comm] - Check state of: /system/holidayModes/hm4/startStop item: String
2018-01-12 10:25:04.206 [DEBUG] [hab.binding.km200.internal.KM200Comm] - Get data
2018-01-12 10:25:04.210 [DEBUG] [hab.binding.km200.internal.KM200Comm] - parseJSONData service: /system/holidayModes/hm4/startStop, data: {"id":"/system/holidayModes/hm4/startStop","type":"stringValue","writeable":1,"recordable":0,"value":"2009-01-01/2009-01-01"}
2018-01-12 10:25:04.212 [DEBUG] [hab.binding.km200.internal.KM200Comm] - parseJSONData type string value: {"id":"/system/holidayModes/hm4/startStop","type":"stringValue","writeable":1,"recordable":0,"value":"2009-01-01/2009-01-01"} Type: String
2018-01-12 10:25:04.318 [DEBUG] [ng.km200.handler.KM200GatewayHandler] - Checking: km200:holidayModes:4072950248:hm4:hcMode Root: #system#holidayModes#hm4#hcMode
2018-01-12 10:25:04.323 [DEBUG] [hab.binding.km200.internal.KM200Comm] - Check state of: /system/holidayModes/hm4/hcMode item: String
2018-01-12 10:25:04.326 [DEBUG] [hab.binding.km200.internal.KM200Comm] - Receive data
2018-01-12 10:25:04.377 [ERROR] [hab.binding.km200.internal.KM200Comm] - Communication is not possible!
2018-01-12 10:25:04.481 [DEBUG] [ng.km200.handler.KM200GatewayHandler] - Checking: km200:holidayModes:4072950248:hm4:dhwMode Root: #system#holidayModes#hm4#dhwMode
2018-01-12 10:25:04.485 [DEBUG] [hab.binding.km200.internal.KM200Comm] - Check state of: /system/holidayModes/hm4/dhwMode item: String
2018-01-12 10:25:04.488 [DEBUG] [hab.binding.km200.internal.KM200Comm] - Receive data
2018-01-12 10:25:04.537 [ERROR] [hab.binding.km200.internal.KM200Comm] - Communication is not possible!
Thomas
Hi,
look to the service-list in the logifle whether you can find such parameters (take a look to the values and units). This are all possible parameters.
Markus
Hi,
your configuration for the switching points control is realy strange (for HC1). Itâs different to all other devices I ever seen.
I cannot handle it easy but I can ignore it. All other stuff should works.
Please check whether itâs starting now:
âlik removedâ
Markus
Hello Markus,
this version is much more stable, I saw nearly no HTTP issues (running for 2 hours now), binding did not stop running up to now. I limited the channels to gateway, appliance, hc1 switch program, temperatures and notification for testing. Will add remaining channels and keep on monitoring.
Think you´re on the right track, will keep you posted.
Thanks,
Thomas
I now added more channels and again ran into the http error:
2018-01-14 14:19:40.980 [DEBUG] [ng.km200.handler.KM200GatewayHandler] - Checking: km200:gateway:4072950248:gateway:logging_userAcceptance Root: #gateway#logging#userAcceptance
2018-01-14 14:19:40.983 [DEBUG] [hab.binding.km200.internal.KM200Comm] - Check state of: /gateway/logging/userAcceptance item: String
2018-01-14 14:19:40.985 [DEBUG] [hab.binding.km200.internal.KM200Comm] - Receive data
2018-01-14 14:19:41.111 [DEBUG] [hab.binding.km200.internal.KM200Comm] - Check state of data: {"id":"/gateway/logging/userAcceptance","type":"stringValue","writeable":1,"recordable":0,"value":"false","allowedValues":["false","true"]}
2018-01-14 14:19:41.114 [DEBUG] [hab.binding.km200.internal.KM200Comm] - parseJSONData service: /gateway/logging/userAcceptance, data: {"id":"/gateway/logging/userAcceptance","type":"stringValue","writeable":1,"recordable":0,"value":"false","allowedValues":["false","true"]}
2018-01-14 14:19:41.117 [DEBUG] [hab.binding.km200.internal.KM200Comm] - parseJSONData type string value: {"id":"/gateway/logging/userAcceptance","type":"stringValue","writeable":1,"recordable":0,"value":"false","allowedValues":["false","true"]} Type: String
2018-01-14 14:19:41.221 [DEBUG] [ng.km200.handler.KM200GatewayHandler] - Checking: km200:heatingCircuit:4072950248:hc1:temperatureRoomSetpoint Root: #heatingCircuits#hc1#temperatureRoomSetpoint
2018-01-14 14:19:41.224 [DEBUG] [hab.binding.km200.internal.KM200Comm] - Check state of: /heatingCircuits/hc1/temperatureRoomSetpoint item: Number
2018-01-14 14:19:41.226 [DEBUG] [hab.binding.km200.internal.KM200Comm] - Receive data
2018-01-14 14:19:49.711 [WARN ] [hab.binding.km200.internal.KM200Comm] - HTTP GET failed: 500, internal server error, repeating..
2018-01-14 14:19:58.711 [WARN ] [hab.binding.km200.internal.KM200Comm] - HTTP GET failed: 500, internal server error, repeating..
2018-01-14 14:20:09.711 [WARN ] [hab.binding.km200.internal.KM200Comm] - HTTP GET failed: 500, internal server error, repeating..
2018-01-14 14:20:22.711 [WARN ] [hab.binding.km200.internal.KM200Comm] - HTTP GET failed: 500, internal server error, repeating..
2018-01-14 14:20:37.711 [WARN ] [hab.binding.km200.internal.KM200Comm] - HTTP GET failed: 500, internal server error, repeating..
2018-01-14 14:20:54.711 [WARN ] [hab.binding.km200.internal.KM200Comm] - HTTP GET failed: 500, internal server error, repeating..
2018-01-14 14:21:13.711 [WARN ] [hab.binding.km200.internal.KM200Comm] - HTTP GET failed: 500, internal server error, repeating..
==> /var/log/openhab2/events.log <==
2018-01-14 14:21:22.866 [ome.event.ItemCommandEvent] - Item 'Toilette_Temperatur' received command 14.4
2018-01-14 14:21:22.876 [vent.ItemStateChangedEvent] - Toilette_Temperatur changed from 14.3 to 14.4
==> /var/log/openhab2/openhab.log <==
2018-01-14 14:21:22.888 [INFO ] [se.smarthome.model.script.TEMPERATUR] - Temperatur:14.4
2018-01-14 14:21:34.711 [WARN ] [hab.binding.km200.internal.KM200Comm] - HTTP GET failed: 500, internal server error, repeating..
==> /var/log/openhab2/events.log <==
2018-01-14 14:21:45.572 [vent.ItemStateChangedEvent] - knxTime changed from 2018-01-14T14:11:45.527+0100 to 2018-01-14T14:21:45.544+0100
2018-01-14 14:21:45.599 [vent.ItemStateChangedEvent] - ntp_ntp_local_dateTime changed from 2018-01-14T14:11:45.527+0100 to 2018-01-14T14:21:45.544+0100
==> /var/log/openhab2/openhab.log <==
2018-01-14 14:21:49.918 [INFO ] [netatmo.handler.NetatmoBridgeHandler] - Initializing API Connection and scheduling token refresh every 5400s
2018-01-14 14:21:57.711 [WARN ] [hab.binding.km200.internal.KM200Comm] - HTTP GET failed: 500, internal server error, repeating..
2018-01-14 14:22:22.712 [WARN ] [hab.binding.km200.internal.KM200Comm] - HTTP GET failed: 500, internal server error, repeating..
2018-01-14 14:22:40.718 [DEBUG] [hab.binding.km200.internal.KM200Comm] - Check state of data:
2018-01-14 14:22:40.722 [DEBUG] [hab.binding.km200.internal.KM200Comm] - parseJSONData service: /heatingCircuits/hc1/temperatureRoomSetpoint, data:
2018-01-14 14:22:40.727 [WARN ] [hab.binding.km200.internal.KM200Comm] - Get empty reply
2018-01-14 14:22:40.832 [DEBUG] [ng.km200.handler.KM200GatewayHandler] - Checking: km200:heatingCircuit:4072950248:hc1:activeSwitchProgram Root: #heatingCircuits#hc1#activeSwitchProgram
2018-01-14 14:22:40.837 [DEBUG] [hab.binding.km200.internal.KM200Comm] - Check state of: /heatingCircuits/hc1/activeSwitchProgram item: String
2018-01-14 14:22:40.862 [DEBUG] [hab.binding.km200.internal.KM200Comm] - Receive data
2018-01-14 14:22:40.913 [ERROR] [hab.binding.km200.internal.KM200Comm] - Communication is not possible!
2018-01-14 14:22:41.017 [DEBUG] [ng.km200.handler.KM200GatewayHandler] - Checking: km200:heatingCircuit:4072950248:hc1:temperatureLevels_eco Root: #heatingCircuits#hc1#temperatureLevels#eco
2018-01-14 14:22:41.020 [DEBUG] [hab.binding.km200.internal.KM200Comm] - Check state of: /heatingCircuits/hc1/temperatureLevels/eco item: Number
2018-01-14 14:22:41.023 [DEBUG] [hab.binding.km200.internal.KM200Comm] - Receive data
2018-01-14 14:22:41.072 [ERROR] [hab.binding.km200.internal.KM200Comm] - Communication is not possible!
2018-01-14 14:22:41.176 [DEBUG] [ng.km200.handler.KM200GatewayHandler] - Checking: km200:heatingCircuit:4072950248:hc1:temperatureLevels_comfort2 Root: #heatingCircuits#hc1#temperatureLevels#comfort2
2018-01-14 14:22:41.180 [DEBUG] [hab.binding.km200.internal.KM200Comm] - Check state of: /heatingCircuits/hc1/temperatureLevels/comfort2 item: Number
2018-01-14 14:22:41.183 [DEBUG] [hab.binding.km200.internal.KM200Comm] - Receive data
2018-01-14 14:22:41.232 [ERROR] [hab.binding.km200.internal.KM200Comm] - Communication is not possible!
2018-01-14 14:22:41.335 [DEBUG] [ng.km200.handler.KM200GatewayHandler] - Checking: km200:heatingCircuit:4072950248:hc1:operationMode Root: #heatingCircuits#hc1#operationMode
2018-01-14 14:22:41.338 [DEBUG] [hab.binding.km200.internal.KM200Comm] - Check state of: /heatingCircuits/hc1/operationMode item: String
2018-01-14 14:22:41.341 [DEBUG] [hab.binding.km200.internal.KM200Comm] - Receive data
2018-01-14 14:22:49.712 [WARN ] [hab.binding.km200.internal.KM200Comm] - HTTP GET failed: 500, internal server error, repeating..
2018-01-14 14:22:58.712 [WARN ] [hab.binding.km200.internal.KM200Comm] - HTTP GET failed: 500, internal server error, repeating..
==> /var/log/openhab2/events.log <==
2018-01-14 14:23:06.558 [ome.event.ItemCommandEvent] - Item 'Wohnzimmer_Temperatur' received command 18.8
2018-01-14 14:23:06.567 [vent.ItemStateChangedEvent] - Wohnzimmer_Temperatur changed from 18.900000000000002 to 18.8
==> /var/log/openhab2/openhab.log <==
2018-01-14 14:23:09.712 [WARN ] [hab.binding.km200.internal.KM200Comm] - HTTP GET failed: 500, internal server error, repeating..
2018-01-14 14:23:22.712 [WARN ] [hab.binding.km200.internal.KM200Comm] - HTTP GET failed: 500, internal server error, repeating..
==> /var/log/openhab2/events.log <==
2018-01-14 14:23:22.852 [ome.event.ItemCommandEvent] - Item 'Toilette_Temperatur' received command 14.4
==> /var/log/openhab2/openhab.log <==
2018-01-14 14:23:22.870 [INFO ] [se.smarthome.model.script.TEMPERATUR] - Temperatur:14.4
2018-01-14 14:23:37.712 [WARN ] [hab.binding.km200.internal.KM200Comm] - HTTP GET failed: 500, internal server error, repeating..
2018-01-14 14:23:54.712 [WARN ] [hab.binding.km200.internal.KM200Comm] - HTTP GET failed: 500, internal server error, repeating..
2018-01-14 14:24:13.713 [WARN ] [hab.binding.km200.internal.KM200Comm] - HTTP GET failed: 500, internal server error, repeating..
==> /var/log/openhab2/events.log <==
2018-01-14 14:24:23.132 [vent.ItemStateChangedEvent] - netatmo_NAMain_671e390b_70ee5004c54e_Pressure changed from 1016.80 to 1016.70
2018-01-14 14:24:23.180 [vent.ItemStateChangedEvent] - netatmo_NAModule1_671e390b_02000004e974_Temperature changed from 5.40 to 5.30
2018-01-14 14:24:23.186 [vent.ItemStateChangedEvent] - netatmo_NAModule1_671e390b_02000004e974_Humidity changed from 69.00 to 67.00
2018-01-14 14:24:23.195 [vent.ItemStateChangedEvent] - netatmo_NAModule1_671e390b_02000004e974_Humidex changed from 3.28 to 3.06
2018-01-14 14:24:23.199 [vent.ItemStateChangedEvent] - netatmo_NAModule1_671e390b_02000004e974_HeatIndex changed from 65.36 to 64.16
2018-01-14 14:24:27.712 [ome.event.ItemCommandEvent] - Item 'Bad_Temperatur' received command 21.3
2018-01-14 14:24:27.727 [vent.ItemStateChangedEvent] - Bad_Temperatur changed from 21.2 to 21.3
==> /var/log/openhab2/openhab.log <==
2018-01-14 14:24:34.713 [WARN ] [hab.binding.km200.internal.KM200Comm] - HTTP GET failed: 500, internal server error, repeating..
2018-01-14 14:24:57.713 [WARN ] [hab.binding.km200.internal.KM200Comm] - HTTP GET failed: 500, internal server error, repeating..
2018-01-14 14:25:22.713 [WARN ] [hab.binding.km200.internal.KM200Comm] - HTTP GET failed: 500, internal server error, repeating..
==> /var/log/openhab2/events.log <==
2018-01-14 14:25:22.841 [ome.event.ItemCommandEvent] - Item 'Toilette_Temperatur' received command 14.4
==> /var/log/openhab2/openhab.log <==
2018-01-14 14:25:22.856 [INFO ] [se.smarthome.model.script.TEMPERATUR] - Temperatur:14.4
2018-01-14 14:25:40.718 [DEBUG] [hab.binding.km200.internal.KM200Comm] - Check state of data:
2018-01-14 14:25:40.722 [DEBUG] [hab.binding.km200.internal.KM200Comm] - parseJSONData service: /heatingCircuits/hc1/operationMode, data:
2018-01-14 14:25:40.726 [WARN ] [hab.binding.km200.internal.KM200Comm] - Get empty reply
2018-01-14 14:25:40.831 [DEBUG] [ng.km200.handler.KM200GatewayHandler] - Checking: km200:heatingCircuit:4072950248:hc1:fastHeatupFactor Root: #heatingCircuits#hc1#fastHeatupFactor
2018-01-14 14:25:40.846 [DEBUG] [hab.binding.km200.internal.KM200Comm] - Check state of: /heatingCircuits/hc1/fastHeatupFactor item: Number
2018-01-14 14:25:40.855 [DEBUG] [hab.binding.km200.internal.KM200Comm] - Receive data
2018-01-14 14:25:49.703 [WARN ] [hab.binding.km200.internal.KM200Comm] - HTTP GET failed: 500, internal server error, repeating..
2018-01-14 14:25:58.704 [WARN ] [hab.binding.km200.internal.KM200Comm] - HTTP GET failed: 500, internal server error, repeating..
2018-01-14 14:26:09.703 [WARN ] [hab.binding.km200.internal.KM200Comm] - HTTP GET failed: 500, internal server error, repeating..
2018-01-14 14:26:22.703 [WARN ] [hab.binding.km200.internal.KM200Comm] - HTTP GET failed: 500, internal server error, repeating..
Is this version going to work in my case too, with the strange hot water switch points?
Hi Marcus,
it is running better now.
But at the end it runs into another error.
Please see the log-file:
KM200_2.xml (255.1 KB)
Screenshot of my âthingsâ:
Best regards
Malte
HI,
this a an another configuration problem. There is a workarround, it should fix it.
Please check whether itâs working now:
âlik removedâ
Markus
I tried the latest snapshot from above,
the binding stops working after trying to reconnect.
Regards,
Thomas
2018-01-15 07:45:17.350 [DEBUG] [ng.km200.handler.KM200GatewayHandler] - Checking: km200:system:4072950248:system:minOutdoorTemp Root: #system#minOutdoorTemp
2018-01-15 07:45:17.354 [DEBUG] [hab.binding.km200.internal.KM200Comm] - Check state of: /system/minOutdoorTemp item: Number
2018-01-15 07:45:17.358 [DEBUG] [hab.binding.km200.internal.KM200Comm] - Receive data
2018-01-15 07:45:17.361 [DEBUG] [hab.binding.km200.internal.KM200Comm] - Starting receive connection...
2018-01-15 07:45:25.736 [WARN ] [hab.binding.km200.internal.KM200Comm] - HTTP GET failed: 500, internal server error, repeating..
2018-01-15 07:45:32.496 [WARN ] [hab.binding.km200.internal.KM200Comm] - HTTP GET failed: 500, internal server error, repeating..
2018-01-15 07:45:32.657 [WARN ] [hab.binding.km200.internal.KM200Comm] - HTTP GET failed: 500, internal server error, repeating..
2018-01-15 07:45:32.916 [WARN ] [hab.binding.km200.internal.KM200Comm] - HTTP GET failed: 500, internal server error, repeating..
2018-01-15 07:45:33.276 [WARN ] [hab.binding.km200.internal.KM200Comm] - HTTP GET failed: 500, internal server error, repeating..
2018-01-15 07:45:33.736 [WARN ] [hab.binding.km200.internal.KM200Comm] - HTTP GET failed: 500, internal server error, repeating..
2018-01-15 07:45:34.296 [WARN ] [hab.binding.km200.internal.KM200Comm] - HTTP GET failed: 500, internal server error, repeating..
2018-01-15 07:45:34.900 [DEBUG] [hab.binding.km200.internal.KM200Comm] - Restarting connection
2018-01-15 07:45:34.956 [WARN ] [hab.binding.km200.internal.KM200Comm] - HTTP GET failed: 500, internal server error, repeating..
2018-01-15 07:45:35.662 [DEBUG] [hab.binding.km200.internal.KM200Comm] - Restarting connection
2018-01-15 07:45:35.716 [WARN ] [hab.binding.km200.internal.KM200Comm] - HTTP GET failed: 500, internal server error, repeating..
2018-01-15 07:45:36.519 [DEBUG] [hab.binding.km200.internal.KM200Comm] - Restarting connection
2018-01-15 07:45:38.506 [WARN ] [hab.binding.km200.internal.KM200Comm] - HTTP GET failed: 500, internal server error, repeating..
2018-01-15 07:45:39.409 [DEBUG] [hab.binding.km200.internal.KM200Comm] - Restarting connection
In log file not show this parameters
Hi Markus,
that version is working now.
Thank you so much!
Best regards
Malte
Hi Markus, Could you perhaps help. Or somebody else
Everything was working till friday. Then I had to re-install Openhabian cause my SD Card failed. I used the same settings like before. But seems I miss something
2018-01-25 18:19:06.117 [hingStatusInfoChangedEvent] - âkm200:kmdevice:05086201â changed from UNINITIALIZED (HANDLER_INITIALIZING_ERROR) to INITIALIZING
2018-01-25 18:19:06.123 [INFO ] [ng.km200.handler.KM200GatewayHandler] - Update KM50/100/200 gateway configuration, it takes a minuteâŚ
2018-01-25 18:19:06.142 [hingStatusInfoChangedEvent] - âkm200:kmdevice:05086201â changed from UNINITIALIZED (HANDLER_INITIALIZING_ERROR) to OFFLINE
2018-01-25 18:19:06.256 [INFO ] [ng.km200.handler.KM200GatewayHandler] - Received dataâŚ
2018-01-25 18:19:06.259 [INFO ] [ng.km200.handler.KM200GatewayHandler] - Test of the communication to the gateway was successfulâŚ
2018-01-25 18:19:11.132 [WARN ] [ome.core.thing.internal.ThingManager] - Initializing handler for thing âkm200:kmdevice:05086201â takes more than 5000ms.
2018-01-25 18:19:11.137 [me.event.ThingUpdatedEvent] - Thing âkm200:kmdevice:05086201â has been updated.
2018-01-25 18:19:52.488 [ERROR] [nal.common.AbstractInvocationHandler] - An error occurred while calling method âThingHandler.initialize()â on âorg.openhab.binding.km200.handler.KM200GatewayHandler@1fdb698â: null
at org.openhab.binding.km200.internal.KM200SwitchProgramService.determineSwitchNames(KM200SwitchProgramService.java:324) [229:org.openhab.binding.km200:2.3.0.201801141914]
at org.openhab.binding.km200.internal.KM200Comm.initVirtualObjects(KM200Comm.java:461) [229:org.openhab.binding.km200:2.3.0.201801141914]
at org.openhab.binding.km200.handler.KM200GatewayHandler.initialize(KM200GatewayHandler.java:206) [229:org.openhab.binding.km200:2.3.0.201801141914]
2018-01-25 18:19:52.504 [ERROR] [ome.core.thing.internal.ThingManager] - Exception occurred while initializing handler of thing âkm200:kmdevice:05086201â: null
at org.openhab.binding.km200.internal.KM200SwitchProgramService.determineSwitchNames(KM200SwitchProgramService.java:324) [229:org.openhab.binding.km200:2.3.0.201801141914]
at org.openhab.binding.km200.internal.KM200Comm.initVirtualObjects(KM200Comm.java:461) [229:org.openhab.binding.km200:2.3.0.201801141914]
at org.openhab.binding.km200.handler.KM200GatewayHandler.initialize(KM200GatewayHandler.java:206) [229:org.openhab.binding.km200:2.3.0.201801141914]
2018-01-25 18:19:52.521 [hingStatusInfoChangedEvent] - âkm200:kmdevice:05086201â changed from OFFLINE to UNINITIALIZED (HANDLER_INITIALIZING_ERROR)
Hi,
did you use auto detection ar did you add the device by hand? Did you remove the device and added it from stratch?
Markus
Did remove all and have nothing else installed.
Did add the gateway manually
Viele GrĂźĂe Mario Spies
Hi,
Great Binding, uninstalled old version via paper ui and updated to the latest version as decribed, everything workâs fine.
Does anyone have an example file for items and sitemap?
Best Regards
Hi guys,
new to OpenHab 2 - today i tried to my KM200. Unfortunately Iâm having some Parsing bug. So far it looks like the Encryption is working (did everything creating the Hash with that Online Tool. Also added the expanded policy for encrypting. So i thought, that i get a feature list of my heating. This is the log so far. Can someone help me?
2018-03-23 16:14:37.582 [INFO ] [.binding.km200.internal.KM200Binding] - Activated
2018-03-23 16:14:37.602 [INFO ] [.binding.km200.internal.KM200Binding] - Update KM200 Binding configuration, it takes a minute....
2018-03-23 16:14:37.632 [INFO ] [.binding.km200.internal.KM200Binding] - Starting communication test..
2018-03-23 16:14:37.678 [INFO ] [ternal.communicator.client.RpcClient] - Interface 'WIRED' on gateway 'homematic-ccu2' not available, disabling support
2018-03-23 16:14:37.749 [INFO ] [ternal.communicator.client.RpcClient] - Interface 'CUXD' on gateway 'homematic-ccu2' not available, disabling support
2018-03-23 16:14:37.980 [INFO ] [ommunicator.AbstractHomematicGateway] - HmGatewayInfo[id=CCU,type=CCU2,firmware=2.31.25,address=OEQ0323112,wired=false,hmip=true,cuxd=false,group=true]
2018-03-23 16:14:38.280 [INFO ] [.binding.km200.internal.KM200Binding] - Received data..
2018-03-23 16:14:38.751 [INFO ] [.binding.km200.internal.KM200Binding] - Test of the communication to the gateway was successful..
2018-03-23 16:14:38.752 [INFO ] [.binding.km200.internal.KM200Binding] - Init services..
2018-03-23 16:14:59.604 [ERROR] [very.HomematicDeviceDiscoveryService] - UID segment 'HU-Hue lightst' contains invalid characters. Each segment of the UID must match the pattern [A-Za-z0-9_-]*.
java.lang.IllegalArgumentException: UID segment 'HU-Hue lightst' contains invalid characters. Each segment of the UID must match the pattern [A-Za-z0-9_-]*.
at org.eclipse.smarthome.core.thing.UID.validateSegment(UID.java:96) [116:org.eclipse.smarthome.core.thing:0.10.0.b1]
at org.eclipse.smarthome.core.thing.UID.<init>(UID.java:74) [116:org.eclipse.smarthome.core.thing:0.10.0.b1]
at org.eclipse.smarthome.core.thing.ThingUID.<init>(ThingUID.java:60) [116:org.eclipse.smarthome.core.thing:0.10.0.b1]
at org.openhab.binding.homematic.internal.discovery.HomematicDeviceDiscoveryService.deviceDiscovered(HomematicDeviceDiscoveryService.java:135) [204:org.openhab.binding.homematic:2.2.0]
at org.openhab.binding.homematic.handler.HomematicBridgeHandler.onDeviceLoaded(HomematicBridgeHandler.java:275) [204:org.openhab.binding.homematic:2.2.0]
at org.openhab.binding.homematic.internal.communicator.AbstractHomematicGateway.loadAllDeviceMetadata(AbstractHomematicGateway.java:388) [204:org.openhab.binding.homematic:2.2.0]
at org.openhab.binding.homematic.internal.discovery.HomematicDeviceDiscoveryService$1.run(HomematicDeviceDiscoveryService.java:104) [204:org.openhab.binding.homematic:2.2.0]
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) [?:?]
at java.util.concurrent.FutureTask.run(FutureTask.java:266) [?:?]
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180) [?:?]
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293) [?:?]
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-03-23 16:15:05.197 [ERROR] [hab.binding.km200.internal.KM200Comm] - Parsingexception in JSON: JSONObject["value"] could not be converted to BigDecimal. data: {"id":"/heatSources/energyMonitoring/consumption","type":"floatValue","writeable":1,"reco$
2018-03-23 16:15:05.614 [ERROR] [hab.binding.km200.internal.KM200Comm] - Parsingexception in JSON: JSONObject["value"] could not be converted to BigDecimal. data: {"id":"/heatSources/energyMonitoring/maxTankLevel","type":"floatValue","writeable":1,"rec$
2018-03-23 16:15:05.755 [ERROR] [hab.binding.km200.internal.KM200Comm] - Parsingexception in JSON: JSONObject["value"] could not be converted to BigDecimal. data: {"id":"/heatSources/energyMonitoring/minTankLevel","type":"floatValue","writeable":1,"rec$
2018-03-23 16:15:05.921 [ERROR] [hab.binding.km200.internal.KM200Comm] - Parsingexception in JSON: JSONObject["value"] could not be converted to BigDecimal. data: {"id":"/heatSources/energyMonitoring/tankLevel","type":"floatValue","writeable":1,"record$
Hi all,
i have a small problem with OH2.1 and latest official km200 binding (
binding-km1001 - 1.11.0). the binding works fine, but i have a problem to change the DateTime of Gateway. in the service list it is marked as writable, but if i trie to change the datetime (i want to synchronize with ntp) it is changed for short time, but on next update of km200 vlaues i get the âoldâ time value.
is it possible to change to change following:
DateTime budDate âDate [%1$td.%1$tm.%1$tY %1$tH:%1$tM]â {km200=âdate_timeâ}
changing other values like temparatures works fine. only datetime dont work
regards, bobby
Good morning,
i have installed the last org.openhab.binding.km200-2.3.0-SNAPSHOT.jar in the add-ons folder and created a âkm200.configâ file with the following content:
PrivKey="XXXXXXXXXXXXXXXXXXXXXXXX"
ip4_address="192.168.XXX.XX"
service.pid="org.openhab.km200"
But the log says:
[ESH-org.openhab.binding.km200.discovery.KM200GatewayDiscovery-1] ERROR org.openhab.binding.km200.internal.KM200Comm - HTTP GET failed: HTTP/1.0 401 Unauthorized
I am using the actual Openhab 2.3.0-SNAPSHOTe Build #1273. Has anyone an idea how to make the bundle working?
thanks in advance
Norbert
Itrâs working. Your KM200 returned a 401 unauthorized to openHAB. Did you check your PrivKey?
If it doesnât work, try the other options:
https://docs.openhab.org/addons/bindings/km2001/readme.html#binding-configuration