# 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:** 3

<div class="post-metadata">

**Author:** ![MbenzNo](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/mbenzno/32/5704_2.png) [@MbenzNo](https://community.homey.app/u/MbenzNo)\
**Post date:** [March 19, 2019, 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/41 "2019-03-19T22:11:58Z")

</div>

My Night mode is just a Virtual Switch I turn on or off normally by Alexa. The flow checks if the Might mode is Off - then 100% - else 5%.

I will create a request on Github for this issue.

I may have another issue in that new movement does not always reset timer. Most of my lights have two flows. One that checks for movement and start light timer, and another flow that checks for movement stops and then start the same light timer. This normally works as intended, but sometimes the start movement flow times out even if the sensor is in movement alarm, and then the light goes off.  
I need to investigate this more before any Github report.

---

<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:** [March 19, 2019, 10:18pm 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/42 "2019-03-19T22:18:57Z")

</div>

The timer app also has a cancel timer card.  
So when the mode changes to nightmode try to cancel the timer for the 100% and start a timer for 5%

---

<div class="post-metadata">

**Author:** ![Driesk](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/driesk/32/10666_2.png) [@Driesk](https://community.homey.app/u/Driesk)\
**Post date:** [May 25, 2019, 10: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/43 "2019-05-25T22:16:14Z")

</div>

Negeer als de lamp al aan staat (ignore if light is already on) function does not seem top work. If u manually switch a light on and then trigger a motion sensor the timer starts and after a while the light is switched off. Do i miss something?

---

<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:** [May 26, 2019, 4:42am 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/44 "2019-05-26T04:42:13Z")

</div>

What is the type of the switch? (Is it a 2-way?)  
(1-way switches do not give there status to homey)  
Please check:  
1 manually switch on  
2 check the status in homey (is it on)  
3 trigger the motion sensor and see if the lights go off

If you comclude the behaviour is wrong, you can post an issue on github.  
The link is in the “Apps” area (where you downloaded the app)

---

<div class="post-metadata">

**Author:** ![Driesk](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/driesk/32/10666_2.png) [@Driesk](https://community.homey.app/u/Driesk)\
**Post date:** [May 26, 2019, 8:59pm 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/45 "2019-05-26T20:59:29Z")

</div>

It is a double relais switch ( fibaro ) with no buttons attatched and a eminent pir  
I double checked with a Neo coolcam pir and aeotec smartplug gen5.  
Could someone confirm a working setup where the ’ ignore when already switched on’ function works. I use the latest stable homey firmware and app version

---

<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:** [May 26, 2019, 9:52pm 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/46 "2019-05-26T21:52:06Z")

</div>

It is probably because this devices has multiple (sub)device in it.  
I will try to check it later, and can probably add support for that as well then

---

<div class="post-metadata">

**Author:** ![Driesk](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/driesk/32/10666_2.png) [@Driesk](https://community.homey.app/u/Driesk)\
**Post date:** [May 27, 2019, 10:39am 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/47 "2019-05-27T10:39:39Z")

</div>

Thanks in advance, let me know if i can be of any help.

---

<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:** [September 28, 2020, 10:26am 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/48 "2020-09-28T10:26:03Z")

</div>

Hi,  
@LvanderRee thank you for this great app, it’s very essential application. However I have some issues, not able to update devices in existing timers but just some of them - some time ago I have create issue for that - [https://github.com/lvanderree/com.synplyworks.thenmore/issues/18](https://github.com/lvanderree/com.synplyworks.thenmore/issues/18) - do you still support your app please ? What is odd, it is happening just for some of the devices, eg. LG TV, Fibaro Dimmer etc. I have tried to sideload TimerApp and see the log but nothing interesting popups.  
Is there a way to troubleshoot it ?  
Thank you.

---

<div class="post-metadata">

**Author:** ![Rockhoppers](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/rockhoppers/32/3994_2.png) [@Rockhoppers](https://community.homey.app/u/Rockhoppers)\
**Post date:** [October 13, 2020, 10:58am 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/49 "2020-10-13T10:58:33Z")

</div>

Great App, love it as it makes timers so simple.  
Is it possible to have a card to get the time left to run on a timer ?

Andrew

---

<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:** [October 13, 2020, 12: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/50 "2020-10-13T12:16:32Z")

</div>

That is very well possible, but unfortunately I can’t say when I will have time to add it yet. It won’t be very hard to do so, but I have to find some time to sit down for it

---

<div class="post-metadata">

**Author:** ![Rrrr](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/rrrr/32/629_2.png) [@Rrrr](https://community.homey.app/u/Rrrr)\
**Post date:** [December 20, 2020, 8:34am 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/51 "2020-12-20T08:34:05Z")

</div>

@LvanderRee  
Thank you for this great app! I wish I had seen this before, in fact it would be nice if there was an overview with best apps/ apps used by experienced users (is there?). I’m using many (24!) countdowns and it’s so much work to set them up.

I’m seeing less and less postings in this group. Is this because the app is stable with many happy users? Or does you have less time to solve issues or maintain?

Just wondering if I should redo my countdowns 😉

---

<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:** [December 20, 2020, 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/52 "2020-12-20T08:53:25Z")

</div>

Simply try it out and see for yourself 😉

As far as I know the only issue is not so much with this app, but with motion detectors only triggering once when motion has been detected and then stay quiet for a while till there timeout retriggers an event. So the the timer of this app longer than the timeout of your motion detectors.

---

<div class="post-metadata">

**Author:** ![Rrrr](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/rrrr/32/629_2.png) [@Rrrr](https://community.homey.app/u/Rrrr)\
**Post date:** [December 20, 2020, 12: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/53 "2020-12-20T12:42:21Z")

</div>

Thanks for your reply. I couldn’t wait though and already finished replacing two countdowns. Looking great with 10% of the effort, 25% of the complexity and 33% of the number of flows 🙂

---

<div class="post-metadata">

**Author:** ![Rrrr](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/rrrr/32/629_2.png) [@Rrrr](https://community.homey.app/u/Rrrr)\
**Post date:** [December 20, 2020, 2:14pm 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/54 "2020-12-20T14:14:22Z")

</div>

Where can I see if you planned new features?  
It would be nice to:

1. be able to start a new flow when the timer times out and turns off the device.
2. Use a virtual device instead of a real device.

Apologies if I missed something.

---

<div class="post-metadata">

**Author:** ![Rrrr](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/rrrr/32/629_2.png) [@Rrrr](https://community.homey.app/u/Rrrr)\
**Post date:** [December 21, 2020, 8:59am 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/55 "2020-12-21T08:59:09Z")

</div>

Possible bug: When adjusting timer with dimming in the else part of the flow, the timer is adjusted, but dimming isn’t adjusted. (Using control it anyway)

(Fibaro Dimmer 2)

---

<div class="post-metadata">

**Author:** ![Russell\_S](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/russell_s/32/45779_2.png) [@Russell\_S](https://community.homey.app/u/Russell_S)\
**Post date:** [January 11, 2021, 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/56 "2021-01-11T14:44:58Z")

</div>

Hi. Sorry if this has been asked before. I like the simplicity and how easy it is to add timers in flows using this app. Could you tell me if an active count down/s resume if power is lost to the Homey Hub, or if it reboots. Eg active count down/s continue and resume where they left off if interrupted. That is my only concern. If it does resume current count down/s then I will keep using this app… thx Russ

---

<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 25, 2021, 8:19am 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/57 "2021-01-25T08:19:15Z")

</div>

The current implementation is in memory only. It might be a nice feature to make it this robust, and that shouldn’t be very hard. I will try to take a look at it, and add it to the feature list: [Issues · lvanderree/com.synplyworks.thenmore · GitHub](https://github.com/lvanderree/com.synplyworks.thenmore/issues)

---

<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 25, 2021, 8:20am 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/58 "2021-01-25T08:20:34Z")

</div>

> [@Rrrr](#):
>
> Possible bug: When adjusting timer with dimming in the else part of the flow, the timer is adjusted, but dimming isn’t adjusted. (Using control it anyway)

I’ve added it to the issue list: [Issues · lvanderree/com.synplyworks.thenmore · GitHub](https://github.com/lvanderree/com.synplyworks.thenmore/issues)

---

<div class="post-metadata">

**Author:** ![Russell\_S](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/russell_s/32/45779_2.png) [@Russell\_S](https://community.homey.app/u/Russell_S)\
**Post date:** [January 25, 2021, 1: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/59 "2021-01-25T13:04:27Z")

</div>

That would be great… thanks…

---

<div class="post-metadata">

**Author:** ![Jens\_De\_Braekeleer](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/jens_de_braekeleer/32/9803_2.png) [@Jens\_De\_Braekeleer](https://community.homey.app/u/Jens_De_Braekeleer)\
**Post date:** [February 6, 2021, 9:58am 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/60 "2021-02-06T09:58:52Z")

</div>

Used Timer app already a long time without any problems. For some mysterious reason, Timer app stopped working (and it’s mostly during the day). In the evening and at night, never a problem (I don’t have a lot of flows or apps installed, so a memory problem can’t be the issue).  
I’ve restarted the app several times, also my Homey, but the problem persists. My flow is [Shared Flow | Homey](https://homey.app/f/elJNSt). My Fibaro detector is properly working as it registers correctly the movement (but it isn’t transferred to the Timer app).

[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=2)

[Next 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=4)
