# VELUX Binding stop working

**URL:** <https://community.openhab.org/t/velux-binding-stop-working/156794>\
**Category:** Bindings\
**Created:** [June 19, 2024, 6:44pm UTC](https://community.openhab.org/t/velux-binding-stop-working/156794 "2024-06-19T18:44:19Z")\
**Posts on this page:** 20\
**Page:** 1

<div class="post-metadata">

**Author:** ![alda1](https://community.openhab.org/letter_avatar_proxy/v4/letter/a/a6a055/32.png) [@alda1](https://community.openhab.org/u/alda1)\
**Post date:** [June 19, 2024, 6:44pm UTC](https://community.openhab.org/t/velux-binding-stop-working/156794/1 "2024-06-19T18:44:19Z")

</div>

I’m using KLF 200 and Velux binding  
Problem is, that this binding stop working and I don’t know why.  
KLF 200 I can see on the network :  
 ![image](https://community-openhab-org.s3.dualstack.eu-central-1.amazonaws.com/original/3X/2/5/259cd6b7dc7634170615ed3abc31f0121e899b9e.png)

also I can ping a device:

 ![image](https://community-openhab-org.s3.dualstack.eu-central-1.amazonaws.com/original/3X/a/e/ae12124b4e00446dacf1abe4f40f8a11daddf1c6.png)

also I can connect via wifi directly to web page of the device

but under openhab I have a error :

 ![image](https://community-openhab-org.s3.dualstack.eu-central-1.amazonaws.com/original/3X/e/4/e487e323b719dcda0a1f378e5fbfe85c7949475b.png)

configuration is the same how it was working before

Please how to trace a root cause of the problem ?

Thank you

---

<div class="post-metadata">

**Author:** ![Oliver2](https://community.openhab.org/letter_avatar_proxy/v4/letter/o/df705f/32.png) [@Oliver2](https://community.openhab.org/u/Oliver2)\
**Post date:** [June 19, 2024, 7:38pm UTC](https://community.openhab.org/t/velux-binding-stop-working/156794/2 "2024-06-19T19:38:19Z")

</div>

Did you set the correct password? It is not the default password „velux123“ according to the binding‘s documentation.  
If I remeber correctly it is the web user‘s password.

---

<div class="post-metadata">

**Author:** ![alda1](https://community.openhab.org/letter_avatar_proxy/v4/letter/a/a6a055/32.png) [@alda1](https://community.openhab.org/u/alda1)\
**Post date:** [June 19, 2024, 7:48pm UTC](https://community.openhab.org/t/velux-binding-stop-working/156794/3 "2024-06-19T19:48:49Z")

</div>

yes, it’s password from the back side of the unit

---

<div class="post-metadata">

**Author:** ![Chiuaua79](https://community.openhab.org/user_avatar/community.openhab.org/chiuaua79/32/58738_2.png) [@Chiuaua79](https://community.openhab.org/u/Chiuaua79)\
**Post date:** [June 19, 2024, 7:56pm UTC](https://community.openhab.org/t/velux-binding-stop-working/156794/4 "2024-06-19T19:56:37Z")

</div>

Hi Alex,

The KLF200 has the annoying habit of going zombie every now and then for quite a lot of us. Try disabling the bridge thing, unplugging the KLF200, wait some time (10 seconds, or a bit more) before plugging in the KLF200 again. Wait a little more (solid green light on the KLF200) and enable the bridge thing again.

I now have a rule thet does this automatically with the help of a smart plug.

---

<div class="post-metadata">

**Author:** ![alda1](https://community.openhab.org/letter_avatar_proxy/v4/letter/a/a6a055/32.png) [@alda1](https://community.openhab.org/u/alda1)\
**Post date:** [June 19, 2024, 8:00pm UTC](https://community.openhab.org/t/velux-binding-stop-working/156794/5 "2024-06-19T20:00:47Z")

</div>

ok, I will try restart. Please can you share your automatic restart solution ?

---

<div class="post-metadata">

**Author:** ![Chiuaua79](https://community.openhab.org/user_avatar/community.openhab.org/chiuaua79/32/58738_2.png) [@Chiuaua79](https://community.openhab.org/u/Chiuaua79)\
**Post date:** [June 19, 2024, 8:32pm UTC](https://community.openhab.org/t/velux-binding-stop-working/156794/6 "2024-06-19T20:32:08Z")

</div>

See [this topic](https://community.openhab.org/t/trigger-a-rule-when-a-thing-goes-offline-because-of-communication-error/146494/11)

---

<div class="post-metadata">

**Author:** ![alda1](https://community.openhab.org/letter_avatar_proxy/v4/letter/a/a6a055/32.png) [@alda1](https://community.openhab.org/u/alda1)\
**Post date:** [June 19, 2024, 8:57pm UTC](https://community.openhab.org/t/velux-binding-stop-working/156794/7 "2024-06-19T20:57:44Z")

</div>

ok, thanks. Is there any other way how to control velux roller shutters without problematic KLF200?

---

<div class="post-metadata">

**Author:** ![hmerk](https://community.openhab.org/user_avatar/community.openhab.org/hmerk/32/56432_2.png) [@hmerk](https://community.openhab.org/u/hmerk)\
**Post date:** [June 19, 2024, 9:20pm UTC](https://community.openhab.org/t/velux-binding-stop-working/156794/8 "2024-06-19T21:20:15Z")

</div>

It can also be done in blockly

 ![image](https://community-openhab-org.s3.dualstack.eu-central-1.amazonaws.com/original/3X/2/d/2d3255fb1e407950ed76973b5887511b3b71fa24.png)

 ![image](https://community-openhab-org.s3.dualstack.eu-central-1.amazonaws.com/original/3X/2/5/258e6917cd7bb1b40096c3e788dc602945f225c1.png)

Just change the name of the bridge thing and add the name of your switch item…  
AFAIK, the WiFi connection of the KLF200 closes after 10 minutes, therefore I set the second timer to 11 minutes.

---

<div class="post-metadata">

**Author:** ![alda1](https://community.openhab.org/letter_avatar_proxy/v4/letter/a/a6a055/32.png) [@alda1](https://community.openhab.org/u/alda1)\
**Post date:** [June 19, 2024, 9:23pm UTC](https://community.openhab.org/t/velux-binding-stop-working/156794/9 "2024-06-19T21:23:31Z")

</div>

thanks,  
means if wifi is running LAN connection isn’t possible ?

---

<div class="post-metadata">

**Author:** ![hmerk](https://community.openhab.org/user_avatar/community.openhab.org/hmerk/32/56432_2.png) [@hmerk](https://community.openhab.org/u/hmerk)\
**Post date:** [June 19, 2024, 9:24pm UTC](https://community.openhab.org/t/velux-binding-stop-working/156794/10 "2024-06-19T21:24:54Z")

</div>

> [@alda1](#):
>
> means if wifi is running LAN connection isn’t possible ?

Correct. If you enabled the LAN connection, WiFi will be available for a short time after reboot and then shuts down. Communication is possible over LAN only then.

---

<div class="post-metadata">

**Author:** ![alda1](https://community.openhab.org/letter_avatar_proxy/v4/letter/a/a6a055/32.png) [@alda1](https://community.openhab.org/u/alda1)\
**Post date:** [June 19, 2024, 9:27pm UTC](https://community.openhab.org/t/velux-binding-stop-working/156794/11 "2024-06-19T21:27:09Z")

</div>

LAN must be enabled, is used for the “data” communication  
Wifi I can set off for always (if block LAN), because is used only for direct setup via web page

---

<div class="post-metadata">

**Author:** ![hmerk](https://community.openhab.org/user_avatar/community.openhab.org/hmerk/32/56432_2.png) [@hmerk](https://community.openhab.org/u/hmerk)\
**Post date:** [June 19, 2024, 9:30pm UTC](https://community.openhab.org/t/velux-binding-stop-working/156794/12 "2024-06-19T21:30:54Z")

</div>

See the Bindings docs :

> **[Velux - Bindings](https://www.openhab.org/addons/bindings/velux/#login-sequence-fails-and-connection-refused)**
>
> This binding integrates the Velux devices with help of a gateway, the Velux Bridge KLF200, which is able to control 200 actuators.

I did not disable Wifi on the KLF200 completely.

> [@alda1](#):
>
> Wifi I can set off for always (if block LAN), because is used only for direct setup via web page

Which imho is needed when adding new devices to the KLF200…

---

<div class="post-metadata">

**Author:** ![alda1](https://community.openhab.org/letter_avatar_proxy/v4/letter/a/a6a055/32.png) [@alda1](https://community.openhab.org/u/alda1)\
**Post date:** [June 19, 2024, 9:43pm UTC](https://community.openhab.org/t/velux-binding-stop-working/156794/13 "2024-06-19T21:43:07Z")

</div>

oh, thaks. Means every unexpected power shut down can make a big trouble with Velux bridge

---

<div class="post-metadata">

**Author:** ![hmerk](https://community.openhab.org/user_avatar/community.openhab.org/hmerk/32/56432_2.png) [@hmerk](https://community.openhab.org/u/hmerk)\
**Post date:** [June 19, 2024, 9:46pm UTC](https://community.openhab.org/t/velux-binding-stop-working/156794/14 "2024-06-19T21:46:16Z")

</div>

> [@alda1](#):
>
> Means every unexpected power shut down can make a big trouble with Velux bridge

Yes, this can lead to the condition you are actually seeing.

---

<div class="post-metadata">

**Author:** ![alda1](https://community.openhab.org/letter_avatar_proxy/v4/letter/a/a6a055/32.png) [@alda1](https://community.openhab.org/u/alda1)\
**Post date:** [June 19, 2024, 9:49pm UTC](https://community.openhab.org/t/velux-binding-stop-working/156794/15 "2024-06-19T21:49:50Z")

</div>

ok, clear.  
Problem is, it looks like when bridge is in the error, is still trying connect with KLF200 and finally will block LAN communication with openHAB at all.

---

<div class="post-metadata">

**Author:** ![AndrewFG](https://community.openhab.org/user_avatar/community.openhab.org/andrewfg/32/35857_2.png) [@AndrewFG](https://community.openhab.org/u/AndrewFG)\
**Post date:** [June 19, 2024, 10:39pm UTC](https://community.openhab.org/t/velux-binding-stop-working/156794/16 "2024-06-19T22:39:52Z")

</div>

> [@alda1](#):
>
> will block LAN communication with openHAB at all.

This is the so called zombie state. The KLF thinks it still has a live connection from OH and it won’t accept any other connection attempt from OH. Whereas OH thinks the connection is down so it retries making a connection. The only solution is to disable the bridge in OH, then power cycle the bridge, then re-enable the bridge in OH.

---

<div class="post-metadata">

**Author:** ![alda1](https://community.openhab.org/letter_avatar_proxy/v4/letter/a/a6a055/32.png) [@alda1](https://community.openhab.org/u/alda1)\
**Post date:** [June 20, 2024, 5:37am UTC](https://community.openhab.org/t/velux-binding-stop-working/156794/17 "2024-06-20T05:37:39Z")

</div>

Thanks all for help.  
Now Velux Bridge is running again.  
Now I must implement automatic stop of the bridge when communication stop working

---

<div class="post-metadata">

**Author:** ![hmerk](https://community.openhab.org/user_avatar/community.openhab.org/hmerk/32/56432_2.png) [@hmerk](https://community.openhab.org/u/hmerk)\
**Post date:** [June 20, 2024, 6:27am UTC](https://community.openhab.org/t/velux-binding-stop-working/156794/18 "2024-06-20T06:27:25Z")

</div>

Quite simple with the here posted rule examples 😉

---

<div class="post-metadata">

**Author:** ![alda1](https://community.openhab.org/letter_avatar_proxy/v4/letter/a/a6a055/32.png) [@alda1](https://community.openhab.org/u/alda1)\
**Post date:** [June 20, 2024, 7:29am UTC](https://community.openhab.org/t/velux-binding-stop-working/156794/19 "2024-06-20T07:29:06Z")

</div>

only one proble is that rule to disable a bridge doesn’t work for me  
I did it as I found :

```auto
sendHttpPutRequest("http://localhost:8080/rest/things/velux:klf200:192_168_1_55/enable", "text/plain", "false", headers, 1000)

```

But Bridge is still ONLINE

---

<div class="post-metadata">

**Author:** ![hmerk](https://community.openhab.org/user_avatar/community.openhab.org/hmerk/32/56432_2.png) [@hmerk](https://community.openhab.org/u/hmerk)\
**Post date:** [June 20, 2024, 7:49am UTC](https://community.openhab.org/t/velux-binding-stop-working/156794/20 "2024-06-20T07:49:16Z")

</div>

Why not going the Blockly way and avoid old DSL rule ???

[Next page](https://community.openhab.org/t/velux-binding-stop-working/156794.md?page=2)
