[velux] New OpenHAB2 binding - feedback welcome!

[Celaeno1 (Alex)]

Hello folks,

I just want to bother very briefly and draw attention to another topic. Who has any experience with Somfy rollershutters (e.g. Oximo 50 io) in connection with the KLF 200 and the use of this binding and can share them please?

[SOLVED] Somfy IO rollershutter motors, which system is best for using with OH2?

Hello folks, my local window manufacturer could provide me Somfy IO rollershutter motors and he asked me which RF system I would choose. But I don’t know. I will get only 6 rollershutters, that’s it. And I’m not planning to buy any other Somfy devices. There are many Somfy gateways or RF systems: RTS io-homecontrol TaHoma Connexoon URTSI II rfxtrx433e / rfxtrx433xl Velux KLF 200 via Velux Binding It’s very confusing. Which is best, which is cheapest, which is easiest t…

Thanks a lot.

[gs4711 (Guenther Schreiner)]

Hello Alex,

regarding the different technologies, I’ll encourage you to open a separate new topic as it is completely out-of-scope.

As there have been some users of this binding with Somfy issues, I tried Somfy on my own … and, now, I know the limitations of this combination, i.e. missing unique identification. io-homecontrol seems to be a stable protocol but the cross-vendor implementations are challenging. That’s just my two cents.

[Celaeno1 (Alex)]

@gs4711

I know the limitations of this combination, i.e. missing unique identification. io-homecontrol seems to be a stable protocol but the cross-vendor implementations are challenging.

This means that you would not recommend Somfy+KLF 200 atm? Are there plans to fix or enhance it?

[gs4711 (Guenther Schreiner)]

Hi Johannes,

there might be the possibility to react upon the rain sensor as the House Monitoring Service should send a special information with the flag STATUS_RAIN (The status is from a rain sensor activation.) However I’ve never seen such a message coming from the bridge…

[gs4711 (Guenther Schreiner)]

@Celaeno1

Are there plans to fix or enhance it?

Good question: who tells Somfy to fix this issue?

[Kim_Andersen]

@gs4711

However I’ve never seen such a message coming from the bridge…

How can we get this sorted? Would debugging be able to tell?
(all my Velux windows got rain sensors. So if there is anything I can do, please tell me).

[johannesbonn (Johannes)]

Hallo @gs4711,

And how can I grab this information for a rule?

Best regards

Johannes

[Windrad (Ingo)]

After lots of testing and (re-)configuring I have the Roof-Windows working again.

I did remove everything including the velux-binding from OH2 and set it up from scratch again, but I got the same errors again.

Then I reset the KLF200 to factory default. I used the newly setup OH-config-data to connect to the KLF, but it couldn’t connect. Then I used the Wifi Password instead of the “velux123” like before and it was working. So, I think after a firmwareupdate from V1 to V2 the KLF uses the “velux123” Password and after a factory reset it will use the Wifipassword.

I don’t know, why I got these errormessages and the Windows were not working. But for me it seems the problem was the KLF200 not the OH2.

[gs4711 (Guenther Schreiner)]

Hello Ingo,

what are the exact messages after starting the OH2 or adding the binding?

Regards, Guenther

[Windrad (Ingo)]

Hi Guenther,
I posted the original errormessages on the 22.09.2019:

[quote=“Windrad, post:487, topic:32926, full:true”]
The Roofwindows were working, but now some are not or not allways. The response time is very long (60s).
On some windows I get warnings and they even don’t move. But not every time I try, sometimes the move.

2019-09-22 17:34:32.351 [WARN ] [ding.velux.bridge.slip.SCgetProducts] - Gateway response GW_ACTIVATION_LOG_UPDATED_NTF (1286) cannot be handled at this point of interaction.
2019-09-22 17:35:42.527 [WARN ] [nding.velux.bridge.slip.SCgetProduct] - Gateway response GW_GET_ALL_NODES_INFORMATION_CFM (515) cannot be handled at this point of interaction.
2019-09-22 17:35:42.608 [WARN ] [nding.velux.bridge.slip.SCgetProduct] - Gateway response GW_GET_ALL_NODES_INFORMATION_NTF (516) cannot be handled at this point of interaction.
2019-09-22 17:35:42.655 [WARN ] [nding.velux.bridge.slip.SCgetProduct] - Gateway response GW_GET_ALL_NODES_INFORMATION_NTF (516) cannot be handled at this point of interaction.
2019-09-22 17:35:42.675 [WARN ] [nding.velux.bridge.slip.SCgetProduct] - Gateway response GW_GET_ALL_NODES_INFORMATION_NTF (516) cannot be handled at this point of interaction.
2019-09-22 17:35:42.689 [WARN ] [nding.velux.bridge.slip.SCgetProduct] - Gateway response GW_GET_ALL_NODES_INFORMATION_NTF (516) cannot be handled at this point of interaction.
2019-09-22 17:35:42.704 [WARN ] [nding.velux.bridge.slip.SCgetProduct] - Gateway response GW_GET_ALL_NODES_INFORMATION_NTF (516) cannot be handled at this point of interaction.
2019-09-22 17:35:42.707 [WARN ] [nding.velux.bridge.slip.SCgetProduct] - Gateway response GW_GET_ALL_NODES_INFORMATION_FINISHED_NTF (517) cannot be handled at this point of interaction.

Not very clever by me, but I deleted the logs frequently while working on OH2.
The last log is from yesterday 5 o’clock. That was after creating the OH configs new. At that time OH couldn’t connect to the KLF.

2019-09-25 09:18:21.055 [WARN ] [ing.velux.handler.VeluxBridgeHandler] - velux bridge login sequence failed; expecting bridge is OFFLINE.
2019-09-25 09:18:22.105 [WARN ] [ing.velux.handler.VeluxBridgeHandler] - velux bridge login sequence failed; expecting bridge is OFFLINE.
2019-09-25 09:18:23.146 [INFO ] [ing.velux.handler.VeluxBridgeHandler] - handleCommand(): cannot work on unknown actuator: 56:36:13:5A:12:07:04:26.
2019-09-25 09:18:23.150 [INFO ] [ing.velux.handler.VeluxBridgeHandler] - handleCommand(): updating of item velux:window:speicher:OstenSueden:position (type velux:window/position) failed.
2019-09-25 09:18:24.167 [WARN ] [ing.velux.handler.VeluxBridgeHandler] - velux bridge login sequence failed; expecting bridge is OFFLINE.
2019-09-25 09:18:25.185 [INFO ] [ing.velux.handler.VeluxBridgeHandler] - handleCommand(): cannot work on unknown actuator: 56:36:13:5A:12:07:04:2C.
2019-09-25 09:18:25.188 [INFO ] [ing.velux.handler.VeluxBridgeHandler] - handleCommand(): updating of item velux:window:speicher:Osten:position (type velux:window/position) failed.
2019-09-25 09:18:26.208 [WARN ] [ing.velux.handler.VeluxBridgeHandler] - velux bridge login sequence failed; expecting bridge is OFFLINE.
2019-09-25 09:18:27.224 [INFO ] [ing.velux.handler.VeluxBridgeHandler] - handleCommand(): cannot work on unknown actuator: 56:36:13:5A:11:28:15:36.
2019-09-25 09:18:27.226 [INFO ] [ing.velux.handler.VeluxBridgeHandler] - handleCommand(): updating of item velux:window:speicher:Buero:position (type velux:window/position) failed.
2019-09-25 09:18:28.240 [WARN ] [ing.velux.handler.VeluxBridgeHandler] - velux bridge login sequence failed; expecting bridge is OFFLINE.
2019-09-25 09:18:29.253 [INFO ] [ing.velux.handler.VeluxBridgeHandler] - handleCommand(): updating of item velux:klf200:speicher:status (type velux:klf200/status) failed.
2019-09-25 09:18:30.267 [WARN ] [ing.velux.handler.VeluxBridgeHandler] - velux bridge login sequence failed; expecting bridge is OFFLINE.
2019-09-25 09:18:31.283 [INFO ] [ing.velux.handler.VeluxBridgeHandler] - handleCommand(): cannot work on unknown actuator: 56:36:13:5A:12:07:04:2E.
2019-09-25 09:18:31.286 [INFO ] [ing.velux.handler.VeluxBridgeHandler] - handleCommand(): updating of item velux:window:speicher:Westen:position (type velux:window/position) failed.
2019-09-25 09:18:32.299 [WARN ] [ing.velux.handler.VeluxBridgeHandler] - velux bridge login sequence failed; expecting bridge is OFFLINE.
2019-09-25 09:18:33.315 [INFO ] [ing.velux.handler.VeluxBridgeHandler] - handleCommand(): cannot work on unknown actuator: 56:36:13:5A:12:07:04:02.
2019-09-25 09:18:33.318 [INFO ] [ing.velux.handler.VeluxBridgeHandler] - handleCommand(): updating of item velux:window:speicher:WestenSueden:position (type velux:window/position) failed.

Yesterday afternoon I made the config new and reseted the KLF. But I can not exactly say, which part of the log belongs to an action I actually did. So this log will not be of worth for you.
I promise, I will take care next time…
I could copy every message concerning velux and post it, but I think that wouldn’t help, does it?

This morning I opend a roofwindows (VPN), but it was only opening to 7%. It was raining at that time. The log showed:

2019-09-26 08:54:50.483 [WARN ] [ding.velux.bridge.slip.SCgetProducts] - Gateway response GW_ACTIVATION_LOG_UPDATED_NTF (1286) cannot be handled at this point of interaction.
2019-09-26 08:54:51.492 [WARN ] [nding.velux.bridge.slip.SCgetProduct] - Gateway response GW_GET_ALL_NODES_INFORMATION_CFM (515) cannot be handled at this point of interaction.
2019-09-26 08:54:51.519 [WARN ] [nding.velux.bridge.slip.SCgetProduct] - Gateway response GW_GET_ALL_NODES_INFORMATION_NTF (516) cannot be handled at this point of interaction.
2019-09-26 08:54:51.545 [WARN ] [nding.velux.bridge.slip.SCgetProduct] - Gateway response GW_GET_ALL_NODES_INFORMATION_NTF (516) cannot be handled at this point of interaction.
2019-09-26 08:54:51.569 [WARN ] [nding.velux.bridge.slip.SCgetProduct] - Gateway response GW_GET_ALL_NODES_INFORMATION_NTF (516) cannot be handled at this point of interaction.
2019-09-26 08:54:51.583 [WARN ] [nding.velux.bridge.slip.SCgetProduct] - Gateway response GW_GET_ALL_NODES_INFORMATION_NTF (516) cannot be handled at this point of interaction.
2019-09-26 08:54:51.596 [WARN ] [nding.velux.bridge.slip.SCgetProduct] - Gateway response GW_GET_ALL_NODES_INFORMATION_NTF (516) cannot be handled at this point of interaction.
2019-09-26 08:54:51.599 [WARN ] [nding.velux.bridge.slip.SCgetProduct] - Gateway response GW_GET_ALL_NODES_INFORMATION_FINISHED_NTF (517) cannot be handled at this point of interaction.

All in all, I think only the 4 day old log from the top can tell anything. I will check the next days and write down the corresponding actions to the log.
Thanks for you help,
Ingo

[gs4711 (Guenther Schreiner)]

Hi Ingo,
to handle your window fault message (as stated above: your window reports an error!)

@Windrad

GW_ACTIVATION_LOG_UPDATED_NTF

I had prepared a new version of jarfile which more-or-less ignoring it. Pls. take this one and give it a try.

BTW what is the response of the KLF web interface if you move one of your windows? It could be that there is a more descriptive message appearing…

[Kim_Andersen]

@gs4711

I had prepared a new version of jarfile which more-or-less ignoring it. Pls. take this one and give it a try.

Link?

[gs4711 (Guenther Schreiner)]

https://github.com/gs4711/org.openhab.binding.velux as usual.

[Windrad (Ingo)]

I just checked with the old Binding. No errors at all, they just open and close. I’m short on time the next days, will report later.

[gs4711 (Guenther Schreiner)]

Ingo,

fyi the old binding (prior to 23th of Sept.) will stuck in the middle whenever an error occurs: It will delay the processing of the actions and the status updates.

[Windrad (Ingo)]

Thanks, so it would be best to change the binding before going bug hunting??

[gs4711 (Guenther Schreiner)]

Definitely, especially for your situation where the actuator continously raises an error.

It would be interesting what’s the reason for it (just for clarification: as far as I see, it is a error message in correspondance to the move command which should tell the user that the desired position cannot be reached i.e. as something is within the way of movement).

[Windrad (Ingo)]

O.K., thanks for that hint. One day we had rain, maybe it is the answer of the window that it will not open when raining. Also, the windows are quite big and heavy. I wondered before that these motors open them with only about 100mA (as far as my current clamp tells the truth). But I will have look on that. Next week…

[gs4711 (Guenther Schreiner)]

@Windrad

maybe it is the answer of the window that it will not open when raining

This sounds reasonable!

[Windrad (Ingo)]

Hello Guenther,
I made some tests, Jar from 23.09.2019.
I noticed 2 things:

1. When the KLF gets powercycled, OH does not connect again:

2019-09-29 14:24:32.183 [WARN ] [ng.velux.bridge.slip.SlipVeluxBridge] - io(): Exception occurred during I/O: Connection reset.
2019-09-29 14:24:33.190 [WARN ] [ng.velux.bridge.slip.SlipVeluxBridge] - io(): raised an error during sending: Connection has been shutdown: javax.net.ssl.SSLException: java.net.SocketException: Connection reset.
2019-09-29 14:24:33.193 [INFO ] [g.velux.bridge.slip.io.SSLconnection] - Shutting down Velux bridge connection.
2019-09-29 14:24:33.197 [WARN ] [ng.velux.bridge.slip.SlipVeluxBridge] - bridgeDirectCommunicate(): method io() raised an error: Connection reset.
2019-09-29 14:24:33.200 [INFO ] [ing.velux.handler.VeluxBridgeHandler] - handleCommand(velux:window:speicher:OstenSueden:position,REFRESH): updating of item velux:window:speicher:OstenSueden:position (type velux:window/position) failed.
2019-09-29 14:24:33.211 [INFO ] [g.velux.bridge.slip.io.SSLconnection] - Starting velux bridge connection.
2019-09-29 14:24:39.224 [WARN ] [ng.velux.bridge.slip.SlipVeluxBridge] - bridgeDirectCommunicate(): received GW_ERROR_NTF (Not authenticated), aborting.
2019-09-29 14:24:39.230 [INFO ] [ing.velux.handler.VeluxBridgeHandler] - handleCommand(velux:window:speicher:Osten:position,REFRESH): updating of item velux:window:speicher:Osten:position (type velux:window/position) failed.
2019-09-29 14:24:40.254 [WARN ] [ng.velux.bridge.slip.SlipVeluxBridge] - bridgeDirectCommunicate(): method io() raised an error: null.
2019-09-29 14:24:40.260 [INFO ] [ing.velux.handler.VeluxBridgeHandler] - handleCommand(velux:window:speicher:Buero:position,REFRESH): updating of item velux:window:speicher:Buero:position (type velux:window/position) failed.
2019-09-29 14:24:40.270 [WARN ] [ng.velux.bridge.slip.SlipVeluxBridge] - io(): raised an error during sending: Connection closed by remote host.
2019-09-29 14:24:40.275 [INFO ] [g.velux.bridge.slip.io.SSLconnection] - Shutting down Velux bridge connection.
2019-09-29 14:24:40.281 [WARN ] [ng.velux.bridge.slip.SlipVeluxBridge] - bridgeDirectCommunicate(): method io() raised an error: Unexpected I/O exception..
2019-09-29 14:24:40.286 [INFO ] [ing.velux.handler.VeluxBridgeHandler] - handleCommand(velux:klf200:speicher:status,REFRESH): updating of item velux:klf200:speicher:status (type velux:klf200/status) failed.
2019-09-29 14:24:40.297 [INFO ] [g.velux.bridge.slip.io.SSLconnection] - Starting velux bridge connection.
2019-09-29 14:24:45.917 [WARN ] [ng.velux.bridge.slip.SlipVeluxBridge] - bridgeDirectCommunicate(): received GW_ERROR_NTF (Not authenticated), aborting.
2019-09-29 14:24:45.920 [INFO ] [ing.velux.handler.VeluxBridgeHandler] - handleCommand(velux:window:speicher:Westen:position,REFRESH): updating of item velux:window:speicher:Westen:position (type velux:window/position) failed.
2019-09-29 14:24:46.930 [WARN ] [ng.velux.bridge.slip.SlipVeluxBridge] - bridgeDirectCommunicate(): method io() raised an error: null.
2019-09-29 14:24:46.932 [INFO ] [ing.velux.handler.VeluxBridgeHandler] - handleCommand(velux:window:speicher:WestenSueden:position,REFRESH): updating of item velux:window:speicher:WestenSueden:position (type velux:window/position) failed.
2019-09-29 14:25:41.605 [WARN ] [ng.velux.bridge.slip.SlipVeluxBridge] - io(): raised an error during sending: Connection closed by remote host.
2019-09-29 14:25:41.612 [INFO ] [g.velux.bridge.slip.io.SSLconnection] - Shutting down Velux bridge connection.
2019-09-29 14:25:41.615 [WARN ] [ng.velux.bridge.slip.SlipVeluxBridge] - bridgeDirectCommunicate(): method io() raised an error: Unexpected I/O exception..
2019-09-29 14:25:46.977 [INFO ] [g.velux.bridge.slip.io.SSLconnection] - Starting velux bridge connection.
2019-09-29 14:25:52.563 [WARN ] [ng.velux.bridge.slip.SlipVeluxBridge] - bridgeDirectCommunicate(): received GW_ERROR_NTF (Not authenticated), aborting.
2019-09-29 14:25:52.567 [INFO ] [ing.velux.handler.VeluxBridgeHandler] - handleCommand(velux:window:speicher:OstenSueden:position,REFRESH): updating of item velux:window:speicher:OstenSueden:position (type velux:window/position) failed.
2019-09-29 14:25:53.580 [WARN ] [ng.velux.bridge.slip.SlipVeluxBridge] - bridgeDirectCommunicate(): method io() raised an error: null.
2019-09-29 14:25:53.583 [INFO ] [ing.velux.handler.VeluxBridgeHandler] - handleCommand(velux:window:speicher:Osten:position,REFRESH): updating of item velux:window:speicher:Osten:position (type velux:window/position) failed.
2019-09-29 14:25:53.592 [WARN ] [ng.velux.bridge.slip.SlipVeluxBridge] - io(): raised an error during sending: Connection closed by remote host.
2019-09-29 14:25:53.595 [INFO ] [g.velux.bridge.slip.io.SSLconnection] - Shutting down Velux bridge connection.
2019-09-29 14:25:53.598 [WARN ] [ng.velux.bridge.slip.SlipVeluxBridge] - bridgeDirectCommunicate(): method io() raised an error: Unexpected I/O exception..
2019-09-29 14:25:53.601 [INFO ] [ing.velux.handler.VeluxBridgeHandler] - handleCommand(velux:window:speicher:Buero:position,REFRESH): updating of item velux:window:speicher:Buero:position (type velux:window/position) failed.
2019-09-29 14:25:53.610 [INFO ] [g.velux.bridge.slip.io.SSLconnection] - Starting velux bridge connection.
2019-09-29 14:41:30.887 [WARN ] [ng.velux.bridge.slip.SlipVeluxBridge] - bridgeDirectCommunicate(): received GW_ERROR_NTF (Not authenticated), aborting.
2019-09-29 14:41:30.891 [INFO ] [ing.velux.handler.VeluxBridgeHandler] - handleCommand(velux:klf200:speicher:status,REFRESH): updating of item velux:klf200:speicher:status (type velux:klf200/status) failed.
2019-09-29 14:41:31.906 [WARN ] [ng.velux.bridge.slip.SlipVeluxBridge] - bridgeDirectCommunicate(): method io() raised an error: null.
2019-09-29 14:41:31.909 [INFO ] [ing.velux.handler.VeluxBridgeHandler] - handleCommand(velux:window:speicher:Westen:position,REFRESH): updating of item velux:window:speicher:Westen:position (type velux:window/position) failed.
2019-09-29 14:41:31.920 [WARN ] [ng.velux.bridge.slip.SlipVeluxBridge] - io(): raised an error during sending: Connection closed by remote host.
2019-09-29 14:41:31.923 [INFO ] [g.velux.bridge.slip.io.SSLconnection] - Shutting down Velux bridge connection.
2019-09-29 14:41:31.926 [WARN ] [ng.velux.bridge.slip.SlipVeluxBridge] - bridgeDirectCommunicate(): method io() raised an error: Unexpected I/O exception..
2019-09-29 14:41:31.928 [INFO ] [ing.velux.handler.VeluxBridgeHandler] - handleCommand(velux:window:speicher:WestenSueden:position,REFRESH): updating of item velux:window:speicher:WestenSueden:position (type velux:window/position) failed.
2019-09-29 14:42:32.041 [INFO ] [g.velux.bridge.slip.io.SSLconnection] - Starting velux bridge connection.
2019-09-29 14:42:37.677 [WARN ] [ng.velux.bridge.slip.SlipVeluxBridge] - bridgeDirectCommunicate(): received GW_ERROR_NTF (Not authenticated), aborting.
2019-09-29 14:42:37.680 [INFO ] [ing.velux.handler.VeluxBridgeHandler] - handleCommand(velux:window:speicher:OstenSueden:position,REFRESH): updating of item velux:window:speicher:OstenSueden:position (type velux:window/position) failed.
2019-09-29 14:42:38.694 [WARN ] [ng.velux.bridge.slip.SlipVeluxBridge] - bridgeDirectCommunicate(): method io() raised an error: null.
2019-09-29 14:42:38.697 [INFO ] [ing.velux.handler.VeluxBridgeHandler] - handleCommand(velux:window:speicher:Osten:position,REFRESH): updating of item velux:window:speicher:Osten:position (type velux:window/position) failed.
2019-09-29 14:42:38.711 [WARN ] [ng.velux.bridge.slip.SlipVeluxBridge] - io(): raised an error during sending: Connection closed by remote host.
2019-09-29 14:42:38.714 [INFO ] [g.velux.bridge.slip.io.SSLconnection] - Shutting down Velux bridge connection.
2019-09-29 14:42:38.717 [WARN ] [ng.velux.bridge.slip.SlipVeluxBridge] - bridgeDirectCommunicate(): method io() raised an error: Unexpected I/O exception..
2019-09-29 14:42:38.721 [INFO ] [ing.velux.handler.VeluxBridgeHandler] - handleCommand(velux:window:speicher:Buero:position,REFRESH): updating of item velux:window:speicher:Buero:position (type velux:window/position) failed.

I have to restart OH to get the KLF connected again.

2. since I set up the KLF and the OH newly last week, there have been no problems at all. I dont see any special in the KLF-LOG:

SW version: 0.2.0.0.71.0; Serial: None
csv
ID, time (s), utc_time, msg_type, code, options, description
114,8,8,1,201,,WiFi launch in AP mode
113,5,5,1,300,,LAN launch
112,4,4,1,102,,EFM library start
111,0,0,2,100,,KLF application start
110,1066,1066,1,203,,WiFi stop in AP mode
109,317,317,3,620,305,EFM is not responding
108,7,7,1,201,,WiFi launch in AP mode
107,4,4,1,300,,LAN launch
106,3,3,1,102,,EFM library start
105,0,0,2,100,,KLF application start
104,1455,1569353328,1,203,,WiFi stop in AP mode
103,81,1569351953,1,300,,LAN launch
102,81,1569351953,1,301,,LAN stop
101,20,20,1,201,,WiFi launch in AP mode
100,17,17,1,300,,LAN launch
99,17,17,1,102,,EFM library start
98,0,0,2,100,,KLF application start
97,301,1569351866,2,650,,EFM was externally rebooted
96,300,1569351866,1,652,,EFM restore to factory defaults request
95,300,1569351866,1,110,,Factory data reset
94,300,1569351866,2,651,,EFM was externally put to factory defaults state
93,8,8,1,201,,WiFi launch in AP mode
92,5,5,1,300,,LAN launch
91,4,4,1,102,,EFM library start
90,0,0,2,100,,KLF application start
89,742,1569154082,1,203,,WiFi stop in AP mode
88,7,7,1,201,,WiFi launch in AP mode
87,4,4,1,300,,LAN launch
86,3,3,1,102,,EFM library start
85,0,0,2,100,,KLF application start
84,973,1569147837,1,203,,WiFi stop in AP mode
83,284,1569147148,3,620,305,EFM is not responding
82,8,8,1,201,,WiFi launch in AP mode
81,4,4,1,300,,LAN launch
80,3,3,1,102,,EFM library start
79,0,0,2,100,,KLF application start
78,797,1569004176,1,203,,WiFi stop in AP mode
77,7,7,1,201,,WiFi launch in AP mode
76,4,4,1,300,,LAN launch
75,3,3,1,102,,EFM library start
74,0,0,2,100,,KLF application start
73,1072,1568995153,1,203,,WiFi stop in AP mode
72,7,7,1,201,,WiFi launch in AP mode
71,4,4,1,300,,LAN launch
70,3,3,1,102,,EFM library start
69,0,0,2,100,,KLF application start
68,1192,1192,1,203,,WiFi stop in AP mode
67,7,7,1,201,,WiFi launch in AP mode
66,4,4,1,300,,LAN launch
65,3,3,1,102,,EFM library start
64,0,0,2,100,,KLF application start
63,11,11,1,201,,WiFi launch in AP mode
62,8,8,1,300,,LAN launch
61,4,4,1,102,,EFM library start
60,0,0,2,100,,KLF application start
59,12,12,1,201,,WiFi launch in AP mode
58,8,8,1,300,,LAN launch
57,5,5,1,102,,EFM library start
56,0,0,2,100,,KLF application start
55,613,613,1,203,,WiFi stop in AP mode
54,38,38,1,201,,WiFi launch in AP mode
53,35,35,1,300,,LAN launch
52,28,28,1,102,,EFM library start
51,27,27,2,100,,KLF application start
50,3,3,1,708,,FW update finished phase
49,1107,1568813056,1,707,,FW update schedule STM update phase
48,1107,1568813056,1,706,,FW update move STM chain phase
47,1107,1568813056,1,710,,FW update webcontent update phase
46,1103,1568813053,1,705,,FW update update EFM phase
45,1103,1568813053,3,620,305,EFM is not responding
44,1013,1568812962,3,620,305,EFM is not responding
43,1003,1568812952,1,704,,FW update move EFM chain phase
42,1003,1568812952,1,711,,FW update schedule KLF update phase
41,1003,1568812952,1,703,,FW update unpack binary phase
40,635,1568812584,1,702,,FW update set version phase
39,635,1568812584,1,701,,FW update validate binary image phase
38,629,1568812578,1,700,,FW update start phase
37,551,1568812501,1,109,,Firmware image upload finish phase
36,551,1568812501,1,108,,Firmware image validate phase
35,545,1568812495,1,107,,Firmware image receive data phase
34,259,1568812208,1,106,,Firmware image create file phase
33,259,1568812208,1,105,,Firmware image upload start phase
32,8,8,1,201,,WiFi launch in AP mode
31,7,7,1,300,,LAN launch
30,7,7,1,102,,EFM library start
29,0,0,2,100,,KLF application start
28,1105,1568569804,1,203,,WiFi stop in AP mode
27,5,5,1,201,,WiFi launch in AP mode
26,5,5,1,300,,LAN launch
25,4,4,1,102,,EFM library start
24,0,0,2,100,,KLF application start
23,5,5,1,201,,WiFi launch in AP mode
22,5,5,1,300,,LAN launch
21,4,4,1,102,,EFM library start
20,0,0,2,100,,KLF application start
19,443,1568559195,3,600,6,GW_ERROR_NTF error code
18,135,1568558887,1,103,,LUT to EFS initial transfer
17,4,4,1,201,,WiFi launch in AP mode
16,4,4,1,300,,LAN launch
15,4,4,1,102,,EFM library start
14,0,0,2,100,,KLF application start
13,561,1568544354,1,300,,LAN launch
12,561,1568544354,1,301,,LAN stop
11,8,8,1,201,,WiFi launch in AP mode
10,8,8,1,300,,LAN launch
9,7,7,1,102,,EFM library start
8,0,0,2,100,,KLF application start
7,6,6,1,201,,WiFi launch in AP mode
6,6,6,1,206,,Setting WiFi SSID value
5,6,6,1,300,,LAN launch
4,6,6,1,102,,EFM library start
3,0,0,2,100,,KLF application start
2,0,0,2,100,,KLF application start
1,0,0,2,100,,KLF application start

3. I checked with a wet towel on the rainsensor. When Iset the window to open, it opens only to 7%.
   That is reproduceble, and it makes sense for me. So water stays outside, but you get bit of ventilation.
   No entry in the log, neither OH nor the KLF log.

O.K., so for me the binding does what I need, really good stuff!!!
Would be good it OH can connect after powerloss of the KLF and don’t need to restart OH, but I think I can deal with that.

When I can help in testing, just tel me.
Thanks again,
Ingo