# Timer 0.8.16 test (Homey V3) - 0.7.3 beta (Homey V2) - v0.4.3 stable (Homey V1.5) - (fka Then More) add Timers to temporarily turn on devices

**URL:** <https://community.homey.app/t/timer-0-8-16-test-homey-v3-0-7-3-beta-homey-v2-v0-4-3-stable-homey-v1-5-fka-then-more-add-timers-to-temporarily-turn-on-devices/3722>\
**Category:** Apps\
**Tags:** app, tools\
**Created:** [November 5, 2018, 7:22pm UTC](https://community.homey.app/t/timer-0-8-16-test-homey-v3-0-7-3-beta-homey-v2-v0-4-3-stable-homey-v1-5-fka-then-more-add-timers-to-temporarily-turn-on-devices/3722 "2018-11-05T19:22:29Z")\
**Posts on this page:** 20\
**Page:** 4

<div class="post-metadata">

**Author:** ![LvanderRee](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/lvanderree/32/1853_2.png) [@LvanderRee](https://community.homey.app/u/LvanderRee)\
**Post date:** [February 6, 2021, 8:47pm UTC](https://community.homey.app/t/timer-0-8-16-test-homey-v3-0-7-3-beta-homey-v2-v0-4-3-stable-homey-v1-5-fka-then-more-add-timers-to-temporarily-turn-on-devices/3722/61 "2021-02-06T20:47:33Z")

</div>

Ik kan het nog altijd niet verklaren. Ik ga binnenkort kijken of ik de app een versie boost kan geven, door wat andere gewenste feature te implementeren. Dan zal ik ook eens verder inzoomen of ik dit kan verklaren, of hoe we dit verder kunnen debuggen.

Voor nu kan ik je nog wel de tip meegeven om eens te kijken in de instellingen van de app, daar zie je een overzicht van alle lopende timers. Dus ook als de lijst leeg is, en je loopt langs de bewegingssensor, dan zou de timer daar gelijk moeten verschijnen.

---

<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:** [February 7, 2021, 9:37am UTC](https://community.homey.app/t/timer-0-8-16-test-homey-v3-0-7-3-beta-homey-v2-v0-4-3-stable-homey-v1-5-fka-then-more-add-timers-to-temporarily-turn-on-devices/3722/62 "2021-02-07T09:37:11Z")

</div>

In English language please. I follow this thread and would like to be able to read along. Thank you very much!

---

<div class="post-metadata">

**Author:** ![JonE](https://avatars.discourse-cdn.com/v4/letter/j/f9ae1b/32.png) [@JonE](https://community.homey.app/u/JonE)\
**Post date:** [December 18, 2021, 6:09am UTC](https://community.homey.app/t/timer-0-8-16-test-homey-v3-0-7-3-beta-homey-v2-v0-4-3-stable-homey-v1-5-fka-then-more-add-timers-to-temporarily-turn-on-devices/3722/63 "2021-12-18T06:09:57Z")

</div>

@LvanderRee hi Leon. I have only just now discovered your app. It seems quite useful but for a newcomer like me, it’s not directly understandable how to use your app.  
For example, my son always forgets to switch off his bedroom light after leaving the room. So I’ve installed a motion sensor which should switch off the light after no motion during e.g. 2 minutes, but when motion is detected again, it should rerun the 2-minute period.  
Is there a page where you explain how such a basic flow can be created making use of Timer?  
(also: is it correct that this can be done with only 1 flow?)

---

<div class="post-metadata">

**Author:** ![JonE](https://avatars.discourse-cdn.com/v4/letter/j/f9ae1b/32.png) [@JonE](https://community.homey.app/u/JonE)\
**Post date:** [December 22, 2021, 6:28am UTC](https://community.homey.app/t/timer-0-8-16-test-homey-v3-0-7-3-beta-homey-v2-v0-4-3-stable-homey-v1-5-fka-then-more-add-timers-to-temporarily-turn-on-devices/3722/64 "2021-12-22T06:28:23Z")

</div>

Hi all!  
Is there anyone who could explain to me how to get the above described use case done?  
Thanks so much!

---

<div class="post-metadata">

**Author:** ![FKey](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/fkey/32/14793_2.png) [@FKey](https://community.homey.app/u/FKey)\
**Post date:** [January 6, 2022, 11:53pm UTC](https://community.homey.app/t/timer-0-8-16-test-homey-v3-0-7-3-beta-homey-v2-v0-4-3-stable-homey-v1-5-fka-then-more-add-timers-to-temporarily-turn-on-devices/3722/65 "2022-01-06T23:53:34Z")

</div>

> [@JonE](#):
>
> (also: is it correct that this can be done with only 1 flow?)

No, but homey can handle a lot of flows. So thats not an issue.  
I prefer to split up my flows as much as possible to keep it simple.  
If you are interested you can read my post about “[how to structure your flows”](https://community.homey.app/t/how-to-structure-your-flows/25109)

> [@JonE](#):
>
> Is there anyone who could explain to me how to get the above described use case done?

Here how you can build your flows with the timer.  
When motion is detected:  
 ![image](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/9/2/921d6a22de0733bed9b0faeb518bd74ae22eedea.png)

When motion is off  
 ![image](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/a/f/af2a7abbf40e941451714a83a70291937e7bd5bd.png)

---

<div class="post-metadata">

**Author:** ![FKey](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/fkey/32/14793_2.png) [@FKey](https://community.homey.app/u/FKey)\
**Post date:** [January 7, 2022, 12:08am UTC](https://community.homey.app/t/timer-0-8-16-test-homey-v3-0-7-3-beta-homey-v2-v0-4-3-stable-homey-v1-5-fka-then-more-add-timers-to-temporarily-turn-on-devices/3722/66 "2022-01-07T00:08:46Z")

</div>

> [@LvanderRee](#):
>
> Ik ga binnenkort kijken of ik de app een versie boost kan geven, door wat andere gewenste feature te implementeren.

@LvanderRee  
Love your app! (Especially remembering the state) any change on an update of your app?

 ![image](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/3/4/3408e6743438653fc55fd40aed7a6349f9254e2d.png)  
The “todo” on your [app page](https://homey.app/nl-nl/app/com.synplyworks.thenmore/Timer/) you mention would indeed make it even more usable.

I have a suggestion for solving this:  
Can you add an option to start & stop & reset the timer?

- When motion is detected: activate the timer. But immediately stop it! (Or not start it)

- When motion is stopped: restart & reset the timer (reset is needed to prevent countdown of the timer when motion is stopped repeatedly)

- That would capture the previous state (timer is not cancelled)

- and still start the timer when motion is stopped i.s.o started.

**2nd functionality request** : Is there a way to make the device used in the timer to show up in the related flows section of the device?  
 ![image](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/9/b/9b5fd95d32ff0feab3a6f940595819e1c2b6d4c6.png)

---

<div class="post-metadata">

**Author:** ![Hans-Jochen\_Nissen](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/hans-jochen_nissen/32/9752_2.png) [@Hans-Jochen\_Nissen](https://community.homey.app/u/Hans-Jochen_Nissen)\
**Post date:** [November 2, 2022, 8:16pm UTC](https://community.homey.app/t/timer-0-8-16-test-homey-v3-0-7-3-beta-homey-v2-v0-4-3-stable-homey-v1-5-fka-then-more-add-timers-to-temporarily-turn-on-devices/3722/67 "2022-11-02T20:16:30Z")

</div>

Will you update this app to SDK3 so it can be used in Homey Pro 2023?

---

<div class="post-metadata">

**Author:** ![Sharkys](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/sharkys/32/54029_2.png) [@Sharkys](https://community.homey.app/u/Sharkys)\
**Post date:** [November 2, 2022, 9:42pm UTC](https://community.homey.app/t/timer-0-8-16-test-homey-v3-0-7-3-beta-homey-v2-v0-4-3-stable-homey-v1-5-fka-then-more-add-timers-to-temporarily-turn-on-devices/3722/68 "2022-11-02T21:42:02Z")

</div>

Yes, seems so 🙂

> [@\[Homey Pro (Early 2023)\] App unsupported list](https://community.homey.app/t/homey-pro-early-2023-app-unsupported-list/70324/227):
>
> Yep i am,and will take a look at it later on

---

<div class="post-metadata">

**Author:** ![LvanderRee](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/lvanderree/32/1853_2.png) [@LvanderRee](https://community.homey.app/u/LvanderRee)\
**Post date:** [November 4, 2022, 9:03am UTC](https://community.homey.app/t/timer-0-8-16-test-homey-v3-0-7-3-beta-homey-v2-v0-4-3-stable-homey-v1-5-fka-then-more-add-timers-to-temporarily-turn-on-devices/3722/69 "2022-11-04T09:03:52Z")

</div>

first testing version has been build: [Timer | Homey](https://homey.app/a/com.synplyworks.thenmore/test/)

---

<div class="post-metadata">

**Author:** ![Sharkys](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/sharkys/32/54029_2.png) [@Sharkys](https://community.homey.app/u/Sharkys)\
**Post date:** [November 4, 2022, 1:13pm UTC](https://community.homey.app/t/timer-0-8-16-test-homey-v3-0-7-3-beta-homey-v2-v0-4-3-stable-homey-v1-5-fka-then-more-add-timers-to-temporarily-turn-on-devices/3722/70 "2022-11-04T13:13:51Z")

</div>

Just crashed, but was working fine till crash. I guess you were notified about that?

---

<div class="post-metadata">

**Author:** ![Sharkys](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/sharkys/32/54029_2.png) [@Sharkys](https://community.homey.app/u/Sharkys)\
**Post date:** [November 4, 2022, 1:27pm UTC](https://community.homey.app/t/timer-0-8-16-test-homey-v3-0-7-3-beta-homey-v2-v0-4-3-stable-homey-v1-5-fka-then-more-add-timers-to-temporarily-turn-on-devices/3722/71 "2022-11-04T13:27:22Z")

</div>

![SmartSelect_20221104_142658_Homey](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/4/9/493a50ee3cf869f278dd81792ecaef04df5143a7.jpeg)

---

<div class="post-metadata">

**Author:** ![LvanderRee](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/lvanderree/32/1853_2.png) [@LvanderRee](https://community.homey.app/u/LvanderRee)\
**Post date:** [November 4, 2022, 2:20pm UTC](https://community.homey.app/t/timer-0-8-16-test-homey-v3-0-7-3-beta-homey-v2-v0-4-3-stable-homey-v1-5-fka-then-more-add-timers-to-temporarily-turn-on-devices/3722/72 "2022-11-04T14:20:03Z")

</div>

Thanks, I can see the error in de Development Tools area, but didn’t get a notification.  
The problem however is somewhat difficult to fix for me, since this stack is only showing HomeyApi traces, without any sign of the Timer-source code that triggered it.

Besides upgrading from SDKv2 to SDKv3 I’ve also upgraded athom-api to homey-api, and I wonder why here I see APIV2 is being used, instead of APIV3 which is also provided by HomeyApi. I’ve [created a issue](https://github.com/athombv/homey-web-api-issues/issues/18) for it on HomeyApi

Can you reproduce it, and tell me what you think is causing this?

---

<div class="post-metadata">

**Author:** ![Sharkys](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/sharkys/32/54029_2.png) [@Sharkys](https://community.homey.app/u/Sharkys)\
**Post date:** [November 4, 2022, 2:32pm UTC](https://community.homey.app/t/timer-0-8-16-test-homey-v3-0-7-3-beta-homey-v2-v0-4-3-stable-homey-v1-5-fka-then-more-add-timers-to-temporarily-turn-on-devices/3722/73 "2022-11-04T14:32:00Z")

</div>

Yep, I was wondering the same, why I see V2 🙂  
It starts crashing every time timer got started, ao I reverted - I will try to reinstall and submit also report after crash, if you will see something, within next 10min

---

<div class="post-metadata">

**Author:** ![robertklep](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/robertklep/32/160628_2.png) [@robertklep](https://community.homey.app/u/robertklep)\
**Post date:** [November 4, 2022, 2:44pm UTC](https://community.homey.app/t/timer-0-8-16-test-homey-v3-0-7-3-beta-homey-v2-v0-4-3-stable-homey-v1-5-fka-then-more-add-timers-to-temporarily-turn-on-devices/3722/74 "2022-11-04T14:44:07Z")

</div>

> [@LvanderRee](#):
>
> Can you reproduce it, and tell me what you think is causing this?

Possibly [this line](https://github.com/lvanderree/com.synplyworks.thenmore/blob/9e63f4e65569e23dc4afc3281a4afe120f1b0abe/app.js#L127), where you don’t pass a listener callback to `makeCapabilityInstance`.

---

<div class="post-metadata">

**Author:** ![LvanderRee](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/lvanderree/32/1853_2.png) [@LvanderRee](https://community.homey.app/u/LvanderRee)\
**Post date:** [November 5, 2022, 12:04pm UTC](https://community.homey.app/t/timer-0-8-16-test-homey-v3-0-7-3-beta-homey-v2-v0-4-3-stable-homey-v1-5-fka-then-more-add-timers-to-temporarily-turn-on-devices/3722/75 "2022-11-05T12:04:13Z")

</div>

Thanks @robertklep , you where right!

I could reproduce the error via your finding, and fixed it. I’ve released 0.8.1 for testing.

---

<div class="post-metadata">

**Author:** ![Sharkys](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/sharkys/32/54029_2.png) [@Sharkys](https://community.homey.app/u/Sharkys)\
**Post date:** [November 5, 2022, 10:11pm UTC](https://community.homey.app/t/timer-0-8-16-test-homey-v3-0-7-3-beta-homey-v2-v0-4-3-stable-homey-v1-5-fka-then-more-add-timers-to-temporarily-turn-on-devices/3722/76 "2022-11-05T22:11:02Z")

</div>

@LvanderRee now it’s not crashing but I have realized another issue - seems this condition doesn’t work anymore.

![obrazek](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/d/c/dc2cc15e6a54e8dde0c899ff793dbc02c0895013.png)  
 ![obrazek](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/8/6/862267fe7ef8f729ff3d040526ec36be22e2bdb3.png)

Let me know in case of some logs required.

---

<div class="post-metadata">

**Author:** ![Sharkys](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/sharkys/32/54029_2.png) [@Sharkys](https://community.homey.app/u/Sharkys)\
**Post date:** [January 5, 2023, 10:26pm UTC](https://community.homey.app/t/timer-0-8-16-test-homey-v3-0-7-3-beta-homey-v2-v0-4-3-stable-homey-v1-5-fka-then-more-add-timers-to-temporarily-turn-on-devices/3722/77 "2023-01-05T22:26:57Z")

</div>

@LvanderRee, not sure if you will see anything in the logs - 16b582f5-a596-41f3-bd09-0f0f2940e369

---

<div class="post-metadata">

**Author:** ![LvanderRee](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/lvanderree/32/1853_2.png) [@LvanderRee](https://community.homey.app/u/LvanderRee)\
**Post date:** [January 6, 2023, 8:53am UTC](https://community.homey.app/t/timer-0-8-16-test-homey-v3-0-7-3-beta-homey-v2-v0-4-3-stable-homey-v1-5-fka-then-more-add-timers-to-temporarily-turn-on-devices/3722/78 "2023-01-06T08:53:09Z")

</div>

I think I can fix that as well. I will do so when I fix some other features as well in the version for the new Homey Api

---

<div class="post-metadata">

**Author:** ![Sharkys](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/sharkys/32/54029_2.png) [@Sharkys](https://community.homey.app/u/Sharkys)\
**Post date:** [January 16, 2023, 8:43pm UTC](https://community.homey.app/t/timer-0-8-16-test-homey-v3-0-7-3-beta-homey-v2-v0-4-3-stable-homey-v1-5-fka-then-more-add-timers-to-temporarily-turn-on-devices/3722/79 "2023-01-16T20:43:54Z")

</div>

If I can help anyhow with testing, let me know, happy to help. True is that currently thanks to that condition many flows are actually broken for me, just discovering new and new flows (out of 800) while wondering why something in my home doesn’t work 😉 It’s great that you kept also non-test version, till it’s still OK to use SDK2, it’s easy to switch back.

---

<div class="post-metadata">

**Author:** ![LvanderRee](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/lvanderree/32/1853_2.png) [@LvanderRee](https://community.homey.app/u/LvanderRee)\
**Post date:** [July 23, 2026, 2:37pm UTC](https://community.homey.app/t/timer-0-8-16-test-homey-v3-0-7-3-beta-homey-v2-v0-4-3-stable-homey-v1-5-fka-then-more-add-timers-to-temporarily-turn-on-devices/3722/80 "2026-07-23T14:37:21Z")

</div>

I am happy to inform you that @Sharkys made some great updates (for some time now) which I finally made some time for to review (but it looked perfect) so I pushed his updated to a test version: [Timer | Homey](https://homey.app/nl-nl/app/com.synplyworks.thenmore/Timer/test/)

[Previous page](https://community.homey.app/t/timer-0-8-16-test-homey-v3-0-7-3-beta-homey-v2-v0-4-3-stable-homey-v1-5-fka-then-more-add-timers-to-temporarily-turn-on-devices/3722.md?page=3)
