[velux] New OpenHAB2 binding - feedback welcome!

[sloth0815 (Jonas Böhringer)]

So with a scene I could move a defined set of actuators to a single predefined position but not to any position? Seems a bit limited to manually control actuators.
Playing with the SLIP protocol is probably nothing for the inexperienced.
I wish Velux had put a bit more effort into the KLF200. The GUI is really limited, access via its own WLAN is strange, an why does it not copy defined groups from a KLR200?
Thanks so much for your efforts to making this a very useful tool!

[johannesbonn (Johannes)]

Hello @gs4711,
to Point 5:

@gs4711

Read state of rain sensor: not supported as it is NOT a separate addressable io-homecontrol device,

Is it definitifly not possible to read the rain sensor state or not yet included? Do you have any information about this from the velux guys?
Would be a killer feature for my smart home setup.

Best regards and wish a nice sunday!

Johannes

[gs4711 (Guenther Schreiner)]

Hello Johannes,

it is a fact that the Velux rain sensors does not have a separate io-homecontrol device identifier. I’ll hopefully come back with an answer whether it can be evaluated indirectly via the addressed window.

Regards, Guenther

[sloth0815 (Jonas Böhringer)]

I seem to have found a solution using a slider with groups:
items:

Group:Dimmer:AVG    gShutters_Bed               "Shutters Bedroom"      (gShutters_East)                                             

sitemap:

Slider		item=gShutters_Bed				label="Bedroom shutters"	icon=Rollershutter

However, and I don’t know if this is connected, it sometimes takes really long for the actuators to react. Here is a log of a case where it first did not react at all and then took about a minute.
I get lost in the TRACE log and would really like to know how I can troubleshoot this.

Many thanks,
Jonas

[Windrad (Ingo)]

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.

I removed the windows from the KLF200 konfiguration and also from the OH .items
Then putting them back in the OH konfug via the “inbox”. Same result, sometimes it works, sometimes not.
Do you have any suggestions?
Thanks,
Ingo

[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.