# 📅 Homey Schedules Beta | Megathread

**URL:** <https://community.homey.app/t/homey-schedules-beta-megathread/162396>\
**Category:** Official Announcements\
**Tags:** schedules, automation\
**Created:** [November 18, 2026, 2:48pm UTC](https://community.homey.app/t/homey-schedules-beta-megathread/162396 "2026-11-18T14:48:32Z")\
**Posts on this page:** 13\
**Page:** 1

<div class="post-metadata">

**Author:** ![Harwin](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/harwin/32/115447_2.png) [@Harwin](https://community.homey.app/u/Harwin)\
**Post date:** [November 18, 2026, 2:48pm UTC](https://community.homey.app/t/homey-schedules-beta-megathread/162396/1 "2026-11-18T14:48:32Z")

</div>

# Time-based automations that repeat every week 🕘

Alongside Flow and Advanced Flow, we’re proud to introduce a new type of automation: Schedules. Your devices follow your weekly routine, and you choose when and what they do.

Starting today, you can try Schedules in beta. To make room, the Flow tab in the Homey Mobile App is now the Automation tab, where you’ll find both your Flows and your Schedules.

 ![Schedules — Interface](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/b/0/b064479425b04c0c4a6880c3733cbefe4b1e8a44.jpeg)

## What you can do

A Schedule is made up of events. For each event, you choose:

- The days it repeats on

- When it starts and ends, at a fixed time or relative to sunrise or sunset

- Optional conditions, such as someone being home

- The state of your devices, such as a brightness level or a color

Unlike in a Flow, conditions are checked for as long as an event runs, not just when it starts. When an event ends, your devices automatically return to their default state.

### An example

On weekdays, you want your kitchen lights on:

- From sunrise until 09:00 at 100% brightness

- From 17:00 until 22:00 at 50% brightness

That’s one Schedule with two events. The rest of the time, the lights stay off. The same setup takes four Flows: two to turn the lights on and two to turn them off.

### Schedule or Flow?

Use a Schedule to keep devices in a chosen state between a start and end time. Use a Flow or Advanced Flow to react the moment something happens, like the doorbell ringing.

## Requirements

- Homey Mobile App v11.0.0 or later

- Homey Pro (2023 — 2026), Homey Pro mini, or Homey Self-Hosted Server running v13.5.5 or later

## Join the beta

Schedules is part of the Homey Mobile App beta.

- On iOS, join the [TestFlight program](https://testflight.apple.com/join/tA2e9vby).

- On Android, join the [Open Beta program](https://play.google.com/apps/testing/app.homey).

## Create your first Schedule

1. Open the Automation tab and tap + in the top-right corner.

2. Tap New Schedule.

3. Choose a category, such as Lights.

4. Add your first event and set the default state.

5. Add more events if you like, then tap Save.

Your devices now follow the Schedule.

## Frequently asked questions

### Will Schedules come to the Homey Web App?

Yes, shortly after the Homey Mobile App.

### Will Schedules come to Homey Cloud?

Yes, we’re working on it.

### Will Schedules come to Homey Pro (2016 — 2019)?

No. Major new features like Schedules are built for newer Homeys.

### Can I convert my Flows to Schedules?

Not automatically. Flows can be built in so many ways that there’s no direct translation to a Schedule. You can recreate time-based Flows as a Schedule yourself. Once the Schedule is running, turn off those Flows so they don’t compete with it.

### Can I create Schedules with the Homey MCP Server?

Not yet, but we’re working on it. Once it’s available, an AI assistant connected to the Homey MCP Server can also help you convert time-based Flows into Schedules.

## Feedback

Found an issue? Post it in this thread. If someone has already reported it, like their post instead, so we can see how many people it affects. We follow this thread throughout the beta.

We’d also love to hear how you use Schedules. Share your Schedules, your ideas, and anything you’re still missing. And if Schedules works well for you, ❤ this post to let us know.

---

<div class="post-metadata">

**Author:** ![Harwin](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/harwin/32/115447_2.png) [@Harwin](https://community.homey.app/u/Harwin)\
**Post date:** [November 18, 2026, 2:49pm UTC](https://community.homey.app/t/homey-schedules-beta-megathread/162396/2 "2026-11-18T14:49:08Z")

</div>

Pinned on November 18, 2026, 2:49pm UTC



---

<div class="post-metadata">

**Author:** ![SunBeech](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/sunbeech/32/111391_2.png) [@SunBeech](https://community.homey.app/u/SunBeech)\
**Post date:** [November 18, 2026, 3:17pm UTC](https://community.homey.app/t/homey-schedules-beta-megathread/162396/3 "2026-11-18T15:17:20Z")

</div>

Just a small UI glitch I noted: in some screens the close button (‘X’) is offset to the border of the screen. Some examples of a light schedule:

 ![IMG_3130](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/0/8/08b637854ec06572723ce270ef9c75e8b15a9ebd.jpeg)  
 ![IMG_3131](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/4/c/4cdfe06d661c66e0dea1eece76924b4b56e8b92f.jpeg)  
 ![IMG_3132](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/0/d/0d5903b54cd3b99b8005e6c660651ddb3f2f0a3e.jpeg)

---

<div class="post-metadata">

**Author:** ![SunBeech](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/sunbeech/32/111391_2.png) [@SunBeech](https://community.homey.app/u/SunBeech)\
**Post date:** [November 18, 2026, 3:23pm UTC](https://community.homey.app/t/homey-schedules-beta-megathread/162396/4 "2026-11-18T15:23:23Z")

</div>

How do Schedules, (Advanced) Flows and manual device actions interact? E.g. if a light is supposed to be on according to a schedule and a flow switches it off (or is manually switched off by a user via the device), will the schedule overrule the flow/manual action and switch the light on again?

---

<div class="post-metadata">

**Author:** ![Harwin](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/harwin/32/115447_2.png) [@Harwin](https://community.homey.app/u/Harwin)\
**Post date:** [November 18, 2026, 3:39pm UTC](https://community.homey.app/t/homey-schedules-beta-megathread/162396/5 "2026-11-18T15:39:11Z")

</div>

Good question! A schedule doesn’t keep forcing a device into a state. It only acts at the moments something changes: when an event starts, when it ends, and when a condition makes an event start or stop.

So in your example, the schedule turns the light on when the event starts. If a Flow or someone in the house turns it off after that, it stays off until the schedule’s next change. That change can come from a condition. If the event uses zone activity, for example, motion that makes the zone active again starts the event again and turns the light back on.

If you want a Flow to keep the light off, add a variable condition to the event, for example a Yes/No variable “Hallway override” that has to be No. When a Flow sets it to Yes, the event stops and the schedule leaves the light alone. When the Flow sets it back to No, the event starts again and the light turns back on.

---

<div class="post-metadata">

**Author:** ![DirkG](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/dirkg/32/118897_2.png) [@DirkG](https://community.homey.app/u/DirkG)\
**Post date:** [November 18, 2026, 4:41pm UTC](https://community.homey.app/t/homey-schedules-beta-megathread/162396/7 "2026-11-18T16:41:34Z")

</div>

@Harwin, I did a test with a power outlet that’s supposed to turn on during a specific time period, but only when everyone in the house is asleep. This test worked perfectly.  
Now, however, I want this power outlet to turn on at the start of the schedule when no one is at home, regardless of whether anyone is asleep.  
Since there is no “or” condition like in flows, I thought I workaround could be to duplicate the schedule and change the conditions accordingly in that schedule. So, in the first schedule, the condition is based on sleep status, and in the second schedule, the condition is based on presence.  
However, when I tried to save the schedule, the following error message appeared:

 ![IMG_2611](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/4/0/4060bf2db8a9ca1aa4d812b908fc5f5739a98043.jpeg)

Is this a bug? Or is duplicating not intended, even though this option is available via the context menu? Or what’s the problem? Maybe it’s because both schedules overlap?  
If so, would this use case even be possible with a schedule?

---

<div class="post-metadata">

**Author:** ![Bjorn\_Schalks](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/bjorn_schalks/32/62546_2.png) [@Bjorn\_Schalks](https://community.homey.app/u/Bjorn_Schalks)\
**Post date:** [November 18, 2026, 5:57pm UTC](https://community.homey.app/t/homey-schedules-beta-megathread/162396/8 "2026-11-18T17:57:47Z")

</div>

I reviewed the “Schedule” feature briefly and remain unconvinced of its necessity. Given that the current functionality has effectively supported workflows through “Advanced Flows” for years, the introduction of “Schedule” appears redundant. In my view, this addition—similar to “Moods”—offers no meaningful value and may even represent a step backward. I would prefer the option to manually disable such features, as they can become unnecessary and disruptive to workflow efficiency.

---

<div class="post-metadata">

**Author:** ![SunBeech](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/sunbeech/32/111391_2.png) [@SunBeech](https://community.homey.app/u/SunBeech)\
**Post date:** [November 18, 2026, 6:18pm UTC](https://community.homey.app/t/homey-schedules-beta-megathread/162396/9 "2026-11-18T18:18:49Z")

</div>

Did you look at this aspect of Schedules:

> [@Harwin](#):
>
> Unlike in a Flow, conditions are checked for as long as an event runs, not just when it starts.

I think this (so the continuous checking of conditions) is what distinguishes it from flows.

For example, if you have flows that switches on and off lights based on the time of day, and another set that does the same if you leave or enter the house, you can combine them into one Schedule. The presence condition is evaluated constantly during the time period and the light follows.

---

<div class="post-metadata">

**Author:** ![4x4\_Pete](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/4x4_pete/32/113286_2.png) [@4x4\_Pete](https://community.homey.app/u/4x4_Pete)\
**Post date:** [November 18, 2026, 6:21pm UTC](https://community.homey.app/t/homey-schedules-beta-megathread/162396/10 "2026-11-18T18:21:38Z")

</div>

This feature is nothing to be the least bit enthusiastic about. - Unfortunately 😞  
What else do you have up your sleeves?

---

<div class="post-metadata">

**Author:** ![Doekse](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/doekse/32/109415_2.png) [@Doekse](https://community.homey.app/u/Doekse)\
**Post date:** [November 18, 2026, 6:22pm UTC](https://community.homey.app/t/homey-schedules-beta-megathread/162396/11 "2026-11-18T18:22:21Z")

</div>

Advanced Flows can, as the name suggests, be quite advanced and intimidating for new users. Regular Flows are easier to use, but you can still end up creating a bunch of them for something relatively simple, like turning devices on and off at set times.

Since many automations are based on time, Schedules would make it easier to set these up and keep track of them. They aren’t meant to replace anything, but to live alongside Flows.

---

<div class="post-metadata">

**Author:** ![gerard\_athom](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/gerard_athom/32/121166_2.png) [@gerard\_athom](https://community.homey.app/u/gerard_athom)\
**Post date:** [November 18, 2026, 7:13pm UTC](https://community.homey.app/t/homey-schedules-beta-megathread/162396/12 "2026-11-18T19:13:46Z")

</div>

Thank you for reporting, this seems to be an bug in the current version of the mobile app. Will be fixed in the next one.

---

<div class="post-metadata">

**Author:** ![Henk\_Renting](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/henk_renting/32/87634_2.png) [@Henk\_Renting](https://community.homey.app/u/Henk_Renting)\
**Post date:** [November 18, 2026, 10:38pm UTC](https://community.homey.app/t/homey-schedules-beta-megathread/162396/13 "2026-11-18T22:38:06Z")

</div>

Sounds great!  
What about when home is started after a schedule is started? Or when a schedule is enabled after it’s starting time?

I suppose it’s actions are carried out immediately after, since you wrote “conditions are checked for as long as an event runs”?

---

<div class="post-metadata">

**Author:** ![Henk\_Renting](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/henk_renting/32/87634_2.png) [@Henk\_Renting](https://community.homey.app/u/Henk_Renting)\
**Post date:** [November 18, 2026, 10:44pm UTC](https://community.homey.app/t/homey-schedules-beta-megathread/162396/14 "2026-11-18T22:44:02Z")

</div>

Other question:  
When creating a schedule, the “wizard” doesn’t ask for a name for the schedule, but simply creates one.  
I did notice that you can rename it after creating the schedule or manually click on the three dots while creating it and change the name there.

UI-wise it would seem logical to me if the wizard would ask for a schedule name…?
