AsynRoamCoop

← Back to FAQ

I scheduled the door to open at 7:00, but it actually opened at 07:10. Why?

The device is designed to perform the open action at 7:00. If it opens at 07:10, it usually means the command was delayed by connection quality or by protection during the opening movement.

  1. Network delay: If the door is scheduled to open at 7:00 but the network is weak at that moment, the coop door may not receive the open command at exactly 7:00. The cloud keeps the command pending until the coop door receives it, similar to an email that remains unread until the recipient opens it.

At the next 10-minute wake-up check, or as soon as the door successfully connects to the network, the door will execute the open command.

  1. Track dirt or resistance: If dirt in the track or other resistance blocks the door while it is opening, the coop door pauses briefly to protect the motor from overheating or burning out.

Because the open action did not finish, the device will try to open again when it wakes at the next 10-minute cycle. If resistance remains, it will stop again and retry during the following 10-minute cycle.

The coop door will retry this process up to three times. If it still cannot open after three retries, it records an open failure log and sends an open failure alert. When you see the log or alert, please check the door track, remove dirt or obstructions, and help the device return to normal.

Related questions