# Asun 650

**URL:** <https://community.homey.app/t/asun-650/38911>\
**Category:** Devices\
**Created:** [December 10, 2020, 8:34am UTC](https://community.homey.app/t/asun-650/38911 "2020-12-10T08:34:09Z")\
**Posts on this page:** 9\
**Page:** 1

<div class="post-metadata">

**Author:** ![Reuvie](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/reuvie/32/4479_2.png) [@Reuvie](https://community.homey.app/u/Reuvie)\
**Post date:** [December 10, 2020, 8:34am UTC](https://community.homey.app/t/asun-650/38911/1 "2020-12-10T08:34:09Z")

</div>

Hello,

I have multiple asun switches installed in order to lower the sunscreens. This is normally done automatically. But sometimes they fail to open. What i allready figured out is that i perform a automatic reboot of Homey on wednesday and saturday. And they miss the command to open on thursday and sunday. So there seems to be something wrong when i reboot homey. Can someone help?

---

<div class="post-metadata">

**Author:** ![Reuvie](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/reuvie/32/4479_2.png) [@Reuvie](https://community.homey.app/u/Reuvie)\
**Post date:** [December 10, 2020, 8:37am UTC](https://community.homey.app/t/asun-650/38911/2 "2020-12-10T08:37:38Z")

</div>

HOmey somes up with message “timed out 30000ms”

---

<div class="post-metadata">

**Author:** ![Edwin\_D](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/edwin_d/32/136417_2.png) [@Edwin\_D](https://community.homey.app/u/Edwin_D)\
**Post date:** [December 10, 2020, 4:27pm UTC](https://community.homey.app/t/asun-650/38911/3 "2020-12-10T16:27:49Z")

</div>

If this is similar to Somfy, then Homey does not see if the screens are manipulated by the remote. If that is the case then it can happen that Homey thinks screens are already open and ignore the commands.

Assuming Asun has a middle (stop) button and you did not assign a middle position to that button: What I do is have Homey issue the stop command about 40 seconds after the up or down command (more than it takes to move the screen). That way Homey will always send up or down when I want it to.

---

<div class="post-metadata">

**Author:** ![Dijker](https://avatars.discourse-cdn.com/v4/letter/d/b9bd4f/32.png) [@Dijker](https://community.homey.app/u/Dijker)\
**Post date:** [December 10, 2020, 5:57pm UTC](https://community.homey.app/t/asun-650/38911/4 "2020-12-10T17:57:02Z")

</div>

Pls share your flow

---

<div class="post-metadata">

**Author:** ![Edwin\_D](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/edwin_d/32/136417_2.png) [@Edwin\_D](https://community.homey.app/u/Edwin_D)\
**Post date:** [December 10, 2020, 8:16pm UTC](https://community.homey.app/t/asun-650/38911/5 "2020-12-10T20:16:26Z")

</div>

[https://homey.app/f/QUYiep](https://homey.app/f/QUYiep)

---

<div class="post-metadata">

**Author:** ![Reuvie](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/reuvie/32/4479_2.png) [@Reuvie](https://community.homey.app/u/Reuvie)\
**Post date:** [December 10, 2020, 8:16pm UTC](https://community.homey.app/t/asun-650/38911/6 "2020-12-10T20:16:52Z")

</div>

@ dijker the problem is not flow related but device related. When they dont open up via flow they cant be opened up manually via homey devices.

@Edwin_D will try that eventhough it works again. Seems every time at 10:15 it starts working again

---

<div class="post-metadata">

**Author:** ![Edwin\_D](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/edwin_d/32/136417_2.png) [@Edwin\_D](https://community.homey.app/u/Edwin_D)\
**Post date:** [December 10, 2020, 8:19pm UTC](https://community.homey.app/t/asun-650/38911/7 "2020-12-10T20:19:54Z")

</div>

If the status in Homey is shown as something other than the direction it won’t go in, than it is indeed another problem.

---

<div class="post-metadata">

**Author:** ![Dijker](https://avatars.discourse-cdn.com/v4/letter/d/b9bd4f/32.png) [@Dijker](https://community.homey.app/u/Dijker)\
**Post date:** [December 10, 2020, 9:00pm UTC](https://community.homey.app/t/asun-650/38911/8 "2020-12-10T21:00:53Z")

</div>

> [@Reuvie](#):
>
> the problem is not flow related

I know but this explains already something.  
Afaik The issue with the ASUN-650 is there is no status still on the signal. The relay is normal open on both contacts.  
Sending a ON switched to up for max 120 seconds. If you send the same signal within that time the relay switches off.  
Same for the OFF signal to the other contact.

After a restart of Homey it doesn’t know the current state up or down.

> Edit, reacting on wrong flow… that’s not from the op and a different type of device. Just ignore.

---

<div class="post-metadata">

**Author:** ![Reuvie](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/reuvie/32/4479_2.png) [@Reuvie](https://community.homey.app/u/Reuvie)\
**Post date:** [December 10, 2020, 10:14pm UTC](https://community.homey.app/t/asun-650/38911/9 "2020-12-10T22:14:17Z")

</div>

[https://homey.app/f/McDJep](https://homey.app/f/McDJep)

This is one of the Flow I use. I just added the Still status with time delay of 40 sec within this flow. Lets see how things go.
