Binding Request : Buderus web gateway

Markinus · February 1, 2017, 7:30am

As first the device has to go online. In a second step you have to search for the things (services) and link them to items.

NCO · February 1, 2017, 10:41am

Thanks, it was online in a previous version (with the OH 2.0.0-1 release.
Now it’s still uninitialized.
I installed JCE for Java 8.

So I need to check the log first.
However, to understand the channel structure on OH2, one example for an item would be helpful.

Termits · February 1, 2017, 5:06pm

Hello, everything works, but now happens, stop show the value of control disappears almost all parameters.

and things is empty properties

some parametr in log is:
2017-02-01 18:09:16.086 [INFO ] [b.binding.km200.internal.KM200Device] - 0;0;0;0;$$PROTECTED$$;/gateway/version;;;

Markinus · February 1, 2017, 6:19pm

The KM200 Binding in OH2 is searching full automatically for items and channels. If the device is only then you have to go to inbox and start a search for things. If you do it then the services are appearing (as things). For every service (thing) the binding is automatically searching for channels. In this thing you can connect them to items (or in simple mode PaperUI is doing it for you).

Markinus · February 1, 2017, 6:23pm

Send me the whole logfile, please.

NCO · February 1, 2017, 6:37pm

I deleted all items and the thing and added it after a reboot.
Actually I followed your step by step description a few posts above (3 days ago to @lukics).
The detection of the KM200 worked flawlessly showing up as “km200:kmdevice:kmdevice”.
However I still get no additional things / channels shown in PaperUI and get a lot of cryptic log entries:

However, the latter entries indicate, that there is a connection to the gateway (which according to PaperUI is still offline

2017-02-01 21:03:49.208 [DEBUG] [ng.km200.handler.KM200GatewayHandler] - initialize Key: ip4Address Value: 192.168.178.43
2017-02-01 21:03:49.210 [DEBUG] [ng.km200.handler.KM200GatewayHandler] - initialize Key: gatewayPassword Value: xxxxxxxxx
2017-02-01 21:03:49.211 [DEBUG] [ng.km200.handler.KM200GatewayHandler] - initialize Key: privatePassword Value: xxxxxxxx
2017-02-01 21:03:49.336 [INFO ] [ng.km200.handler.KM200GatewayHandler] - Received data..
2017-02-01 21:03:49.345 [INFO ] [ng.km200.handler.KM200GatewayHandler] - Test of the communication to the gateway was successful..
2017-02-01 21:03:49.347 [INFO ] [ng.km200.handler.KM200GatewayHandler] - Init services..
2017-02-01 21:03:49.370 [DEBUG] [ng.km200.handler.KM200GatewayHandler] - /dhwCircuits
2017-02-01 21:03:49.371 [DEBUG] [hab.binding.km200.internal.KM200Comm] - Init: /dhwCircuits
2017-02-01 21:03:49.49Ã¬$h<92>Ã^SÂ·Â£wÂ¾Ã¡qÃ<83>Ã8Yxn^]Ã¤`Ã§^NK'{<97>Ã¸.<81>w<8b>RKÃx`Ã§$#Ã³$"[Â¤<9f>"Â¾^_ÂªÃLÃ´Ã§Â³:ig<88><98>Ãª<95>p^NFA^B1 [character 2 line9^Ã,WÃ¿{^h7y^W<82>Ã<84>Ã+Ã¥Â³ÃU^P^]^GÃÂ¦^FÃ¬&Â¬ÃÃ¨<87><98>E^^^Â¹Â¸#<94><90>Â¥Ã¥ÃÃ¿^L<98><8f><9d>
2017-02-01 21:03:49.493 [DEBUG] [ng.km200.handler.KM200GatewayHandler] - /gateway
2017-02-01 21:03:49.494 [DEBUG] [hab.binding.km200.internal.KM200Comm] - Init: /gateway
2017-02-01 21:03:49.588 [ERROR] [hab.binding.km200.internal.KM200Comm] - Parsingexception in JSON: A JSONObject text must begin with '{' at 1 [character 2 linee                <83>^QÂ¦!<82>,sQÂ¨Ã¶C<94>^V<9c>ÃÃÂ ^]~ÂªÃfdL"<92>kÃ¡^_"~Â´(Ã¾Â§S^RÃ±^@TÃ <86>IÃJ<86>ÃÂ±,ÃAÃ³RVÃ-{Z(<80><97>Â¥Â·Ã¤ZÃ¼Â¾HÂ°^Z<99>Â±Â°b<87>j^?<Ã£ÃÂ§Ã¾<88: ?D<ÃÃ¨Ã
0>])Â«<96>Â®Ã¤TÃÂ¿8^Py<91>^VÃ7eÃ¨Â²@<84>DvÂ´^X^NÃ^Y<87>Ã^?Ã Ã§%A<9a>Ã,XlÃÂ¥-n<~|Â¬Ã£<82>g<80>O^<82>uMh(.Ã»<92><9a>lÃ<8b><87>^^Â¾M<86>^CÃÃ¼
ÃÃ^_Dm\Ã®ÃÃ¤Ã©?Ã»d(1ÃcK^]^H^Gd<92><9b>Ã¡@Ã¼Â°Ã:C^MÃ^T<9b><83><83>Â ^C`gÃ¤f=zÃÂµ^PÂ£^AÃ¢Ã£<88>5J4^^42HÃ¦Ã¥Ã¢dÂ°^F^P<95>tÃÃ¼Â³.Â®^DÂ¢4nÂ¡Ã°><88><88><90>Ã
iÃªÃ^LÃ[Ã¯Â¥Ã¹Ã¢~[ÃÂ¡Ã³V^\ÃÃ©Ã¶^@<95>"Ã^\<9c>MIÃÂ³Â°z<<8b>~Ã-Ã£Â§^GI42HÃ¦Ã¥Ã¢dÂ°^F^P<95>tÃÃ¼Â³.sÃ»B^\Ã¿'<8b>J1Ã*Ã^Kn<8b>ÃeÃ
Ã¶^Mn0<94>^?^@P$^L<93>Ã¡<8c>:\Ã«RK42HÃ¦Ã¥Ã¢dÂ°^F^P<95>tÃÃ¼Â³.sÃ»B^\Ã¿'<8b>J1Ã*Ã^Kn<8b>Ã(Ã<88><95>4Â¯HxÃÃÂ¨xP,ÃÃ§Ã¢~[ÃÂ¡Ã³V^\ÃÃ©Ã¶^@<95>"Ã^\^?.<96>Â¾Ã©<92>    Ã¶Ã¦<9e>Ã¿Â¨>>¦<9e>Ã¿Â¨Â§Â¿T<93>Â°FÃ =Â¦]XÂ¡^@Ã®ÃÂº-h^MÃ<88>Â³Â¶Ã"$ÃÃ¡~6vÃ<8f>LÂ¶ÂºÃ³lÃªpÂ¶^O\Ã¬^T^PÃ³gÃ6ÂÂ´F^@^R~ÃÃ©>MKtEÃ°Ã<9b>{1"   ^TTUÃ®Ã»^T?{Â¼Ã^[=IÃ©Ã>xqÂ«y<8b><8d>Ã°<89><9c>cÂ¤Ã¢^@DÂ¨^R*Â¥Â¬^LÃÃÃ´Ã§Â®Ã¯^_^L<8e> ^DÂ«<^\Â·ÃsÂ¦Ãµ<94>Â¼F!N°`<97>EÃÃ¥Ã½<9a>e-`ÃaÃ                           Ã¹
2017-02-01 21:03:49.589 [DEBUG] [ng.km200.handler.KM200GatewayHandler] - /heatingCircuits²ÃM^FyIÃÂ<92>Â¦1Q<9f>u<91>ÃÃÃ¨Ã£C6|<9d>^GÃÃ
2017-02-01 21:03:49.590 [DEBUG] [hab.binding.km200.internal.KM200Comm] - Init: /heatingCircuits

Markinus · February 2, 2017, 1:47pm

This looks like the encryption/decription is not working correctly. Check the passwords

NCO · February 2, 2017, 4:32pm

Hmmm… just to make sure that I got it right:
I generated the salt key with this tool:
https://ssl-account.com/km200.andreashahn.info/
By using my personal Password and the gateway password on the km200 sticker (without the “-”).
I have put this into the PaperUI and got the cryptic error messages mentioned above.

I will check again my setting though.

NCO · February 2, 2017, 6:46pm

By the way.
Putting the configuration into the km200.cfg does not work on OH2, right?

Markinus · February 2, 2017, 6:49pm

The .cfg file is only for OH1 Bindings in lagacy mode on OH2.
You can do it if you install the km200 lagacy binding directly from the PaperUI (instead of use this alpha OH2.0 binding).

NCO · February 2, 2017, 7:54pm

Thanks, @Markinus

Could you please also check if I understood the key generation below correctly?

NCO · February 2, 2017, 8:07pm

Damn it! I got it.
Never mind.

Maybe this helps others to get to the point quicker than I did:

The private key, which is needed to connect to the Gateway (Option 1 in Paper UI for the KM200) needs to be generated.
You can do this here:
https://ssl-account.com/km200.andreashahn.info/

Two things are needed:

You need the gateway password or Geräte Password (on the Km200 sticker, but without the “-”).
The personal password or Benutzer Passwort you’ve set up using the App for the first connection (e.g. iOS App from Buderus).
The generated key is the one you need to put into Option 1 at Paper UI.
After that the connection should be done.

Markinus · February 2, 2017, 8:08pm

It should be correct. If you use the generator on this side, then you need to put this key to the PrivKey option in the PaperUI, nothing else.

Markinus · February 2, 2017, 8:08pm

Ahh, great.

NCO · February 3, 2017, 7:59am

It seems to be working fine!
Thanks a lot for your efforts to bring the KM200 to Openhab!!!
That was the missing piece in my homeautomation.
THANK YOU so MUCH!

I still have some question though
In my Paper UI the Things “notifications” and “temperatures” do not show any channels.
Is this ok, or did the autodetection miss something?

NCO · February 3, 2017, 10:33am

Hi,

have you been able to solve it?
I encountered the same issue.

Just a few parameters are still populated with data:
hc1 Switch Program:
hc1-switchprogram:weekday
hc1-switchprogram:nbrCycles
hc1-switchprogram:day
hc1-switchprogram:night

I forgot these:

whopperg · February 3, 2017, 5:59pm

@Markinus:
Everything is working now. I’ve Updated the OH1 wiki with some Infos that where missing / are good to know.

So i don’t know if you got this service paths already so i just leave this here:
(i cant remember where i get this, so if anybody has some issues or the source, i’ll be happy to add this info here)

Path: /gateway/DateTime
Value: 2017-02-03T19:18:13
Unit: 
Path: /gateway/instAccess
Value: off
Unit: 
Path: /gateway/uuid
Value: 123456789
Unit: 
Path: /gateway/versionFirmware
Value: 04.00.04
Unit: 
Path: /gateway/versionHardware
Value: iCom_Low_NSC_v1
Unit: 
Path: /heatingCircuits
Value: iCom_Low_NSC_v1
Unit:
Path: /heatingCircuits/hc1
Value: iCom_Low_NSC_v1
Unit:
Path: /heatingCircuits/hc1/activeSwitchProgram
Value: A
Unit: 
Path: /heatingCircuits/hc1/actualSupplyTemperature
Value: 27.2
Unit: C 
Path: heatingCircuits/hc1/controlType
Value: 27.2
Unit: 
Path: /heatingCircuits/hc1/currentOpModeInfo
Value: 27.2
Unit:
Path: /heatingCircuits/hc1/currentRoomSetpoint
Value: 21
Unit: C 
Path: /heatingCircuits/hc1/designTemp
Value: 21
Unit:
Path: /heatingCircuits/hc1/fastHeatupFactor
Value: 21
Unit:
Path: /heatingCircuits/hc1/heatCurveMax
Value: 21
Unit:
Path: /heatingCircuits/hc1/heatCurveMin
Value: 21
Unit:
Path: /heatingCircuits/hc1/manualRoomSetpoint
Value: 13
Unit: C 
Path: /heatingCircuits/hc1/operationMode
Value: auto
Unit: 
Path: /heatingCircuits/hc1/pumpModulation
Value: 49
Unit: % 
Path: /heatingCircuits/hc1/roomInfluence
Value: 49
Unit:
Path: /heatingCircuits/hc1/roomtemperature
Value: 22.1
Unit: C 
Path: /heatingCircuits/hc1/roomTempOffset
Value: 22.1
Unit:
Path: /heatingCircuits/hc1/setpointOptimization
Value: 22.1
Unit:
Path: /heatingCircuits/hc1/solarInfluence
Value: 22.1
Unit:
Path: /heatingCircuits/hc1/status
Value: ACTIVE
Unit: 
Path: /heatingCircuits/hc1/suWiSwitchMode
Value: ACTIVE
Unit:
Path: /heatingCircuits/hc1/suWiThreshold
Value: ACTIVE
Unit:
Path: /heatingCircuits/hc1/switchPrograms
Value: ACTIVE
Unit:
Path: /heatingCircuits/hc1/temperatureLevels
Value: ACTIVE
Unit:
Path: /heatingCircuits/hc1/temperatureRoomSetpoint
Value: 13
Unit: C 
Path: /heatingCircuits/hc1/temporaryRoomSetpoint
Value: -1
Unit: C 
Path: /heatingCircuits/hc2/activeSwitchProgram
Value: A
Unit: 
Path: /heatingCircuits/hc2/actualSupplyTemperature
Value: 25
Unit: C 
Path: /heatingCircuits/hc2/controlType
Value: 25
Unit:
Path: /heatingCircuits/hc2/currentOpModeInfo
Value: 25
Unit:
Path: /heatingCircuits/hc2/currentRoomSetpoint
Value: 22
Unit: C 
Path: /heatingCircuits/hc2/designTemp
Value: 22
Unit:
Path: /heatingCircuits/hc2/fastHeatupFactor
Value: 22
Unit:
Path: /heatingCircuits/hc2/heatCurveMax
Value: 22
Unit:
Path: /heatingCircuits/hc2/heatCurveMin
Value: 22
Unit:
Path: /heatingCircuits/hc2/manualRoomSetpoint
Value: 13
Unit: C 
Path: /heatingCircuits/hc2/operationMode
Value: auto
Unit: 
Path: /heatingCircuits/hc2/pumpModulation
Value: 100
Unit: % 
Path: /heatingCircuits/hc2/roomInfluence
Value: 100
Unit:
Path: /heatingCircuits/hc2/roomtemperature
Value: 22.1
Unit: C 
Path: /heatingCircuits/hc2/roomTempOffset
Value: 22.1
Unit:
Path: /heatingCircuits/hc2/setpointOptimization
Value: 22.1
Unit:
Path: /heatingCircuits/hc2/solarInfluence
Value: 22.1
Unit:
Path: /heatingCircuits/hc2/status
Value: ACTIVE
Unit: 
Path: /heatingCircuits/hc2/suWiSwitchMode
Value: ACTIVE
Unit:
Path: /heatingCircuits/hc2/suWiThreshold
Value: ACTIVE
Unit:
Path: /heatingCircuits/hc2/switchPrograms
Value: ACTIVE
Unit:
Path: /heatingCircuits/hc2/temperatureLevels
Value: ACTIVE
Unit:
Path: /heatingCircuits/hc2/temperatureRoomSetpoint
Value: 13
Unit: C 
Path: /heatingCircuits/hc2/temporaryRoomSetpoint
Value: -1
Unit: C 
Path: /heatSources
Value: -1
Unit:
Path: /heatSources/actualCHPower
Value: 0
Unit: kW 
Path: /heatSources/actualDHWPower
Value: 0
Unit: kW 
Path: /heatSources/actualPower
Value: 0
Unit: kW 
Path: heatSources/actualsupplytemperature
Value: 0
Unit:
Path: /heatSources/ChimneySweeper
Value: off
Unit: 
Path: /heatSources/CHpumpModulation
Value: 45
Unit: % 
Path: /heatSources/flameCurrent
Value: 0
Unit: µA 
Path: /heatSources/flameStatus
Value: off
Unit: 
Path: /heatSources/gasAirPressure
Value: 0
Unit: Pascal 
Path: /heatSources/nominalCHPower
Value: 14
Unit: kW 
Path: /heatSources/nominalDHWPower
Value: 15
Unit: kW 
Path: /heatSources/numberOfStarts
Value: 55541
Unit: 
Path: /heatSources/powerSetpoint
Value: 100
Unit: % 
Path: /heatSources/returnTemperature
Value: -3276.8
Unit: C 
Path: /heatSources/systemPressure
Value: 25.5
Unit: bar 
Path: /heatSources/workingTime
Value: 25.5
Unit:
Path: /notifications
Value: 25.5
Unit:
Path: /recordings
Value: 25.5
Unit:
Path: /recordings/heatingCircuits
Value: 25.5
Unit:
Path: /recordings/heatingCircuits/hc1
Value: 25.5
Unit:
Path: /recordings/heatingCircuits/hc1/roomtemperature
Value: 25.5
Unit:
Path: /recordings/heatSources
Value: 25.5
Unit:
Path: /recordings/heatSources/actualCHPower
Value: 25.5
Unit:
Path: /recordings/heatSources/actualDHWPower
Value: 25.5
Unit:
Path: /recordings/heatSources/actualPower
Value: 25.5
Unit:
Path: /recordings/system
Value: 25.5
Unit:
Path: /recordings/system/heatSources
Value: 25.5
Unit:
Path: /recordings/system/heatSources/hs1
Value: 25.5
Unit:
Path: /recordings/system/heatSources/hs1/actualPower
Value: 25.5
Unit:
Path: /recordings/system/sensors
Value: 25.5
Unit:
Path: /recordings/system/sensors/temperatures
Value: 25.5
Unit:
Path: /recordings/system/sensors/temperatures/outdoor_t1
Value: 25.5
Unit:
Path: /solarCircuits
Value: 25.5
Unit:
Path: /solarCircuits/sc1/collectorTemperature
Value: 8
Unit: C 
Path: /solarCircuits/sc1/pumpModulation
Value: 0
Unit: % 
Path: /solarCircuits/sc1/solarYield
Value: 0
Unit: Wh 
Path: /solarCircuits/sc1/status
Value: ACTIVE
Unit: 
Path: /system
Value: ACTIVE
Unit:
Path: /system/appliance
Value: ACTIVE
Unit:
Path: /system/appliance/actualPower
Value: 0
Unit: % 
Path: /system/appliance/actualSupplyTemperature
Value: 27
Unit: C 
Path: /system/appliance/ChimneySweeper
Value: 0
Unit: 
Path: /system/appliance/CHpumpModulation
Value: 45
Unit: % 
Path: /system/appliance/flameCurrent
Value: 0
Unit: µA 
Path: /system/appliance/gasAirPressure
Value: 0
Unit: Pascal 
Path: /system/appliance/nominalBurnerLoad
Value: 14
Unit: kW 
Path: /system/appliance/numberOfStarts
Value: 55541
Unit: 
Path: /system/appliance/powerSetpoint
Value: 100
Unit: % 
Path: /system/appliance/systemPressure
Value: 25.5
Unit: bar 
Path: /system/appliance/workingTime
Value: 25.5
Unit:
Path: /system/brand
Value: Buderus
Unit: 
Path: /system/bus
Value: EMS2_0
Unit: 
Path: /system/healthStatus
Value: ok
Unit: 
Path: /system/heatSources/hs1
Value: ok
Unit:
Path: /system/heatSources/hs1/actualModulation
Value: 0
Unit: % 
Path: /system/heatSources/hs1/actualPower
Value: 0
Unit: kW 
Path: /system/heatSources/hs1/energyReservoir
Value: 0
Unit: kWh 
Path: /system/heatSources/hs1/fuel
Value: 0
Unit:
Path: /system/heatSources/hs1/fuel/density
Value: 0.82
Unit: kg/l 
Path: /system/heatSources/hs1/fuelConsmptCorrFactor
Value: 1
Unit: 
Path: /system/heatSources/hs1/nominalFuelConsumption
Value: 1.8
Unit: l/h 
Path: /system/heatSources/hs1/reservoirAlert
Value: 0
Unit: kWh 
Path: /system/info
Value: 0
Unit:
Path: /system/minOutdoorTemp
Value: -10
Unit: C 
Path: /system/sensors
Value: -10
Unit:
Path: /system/sensors/temperatures
Value: -10
Unit:
Path: /system/sensors/temperatures/chimney
Value: -3276.8
Unit: C 
Path: /system/sensors/temperatures/hotWater_t1
Value: -3276.8
Unit:
Path: /system/sensors/temperatures/hotWater_t2
Value: 58.6
Unit: C 
Path: /system/sensors/temperatures/outdoor_t1
Value: 6.8
Unit: C 
Path: /system/sensors/temperatures/return
Value: -3276.8
Unit: C 
Path: /system/sensors/temperatures/supply_t1
Value: 27
Unit: C 
Path: /system/sensors/temperatures/supply_t1_setpoint
Value: 31
Unit: C 
Path: /system/sensors/temperatures/switch
Value: -3276.8
Unit: C 
Path: /system/systemType
Value: NSC_ICOM_GATEWAY
Unit:

Markinus · February 3, 2017, 6:10pm

Great!

They should show something. Send me your log file please, maybe there is something different.

The problem is that there isn’t a official syntax definition of this files. Depending on the heating system, the control unit and firmware version the services are a bit different. (And the structures).

Markinus · February 3, 2017, 6:11pm

Enable debug in OH2 and send me the logfile after this problem appeared.

NCO · February 3, 2017, 6:13pm

Thanks, @whopperg,

There are some items I did not see yet on PaperUI (I am running OH2).

However, I did not get the point how to switch from day to night mode. I would like to use this for simple “present” and “not present” conditions at home.

I played around with the following hint in the wiki:
Switch budMode "Mode [%s]" {km200="service:/heatingCircuits/hc3/operationMode on:auto off:night"}

As far as I understand the hc3 in this case should go to auto if the switch is set to ON and to night, if the switch is set to OFF.
Am I right?

This doesn’t work though