# \[Feature request\] Logic as time in Energy Flowcards

**URL:** <https://community.homey.app/t/feature-request-logic-as-time-in-energy-flowcards/151502>\
**Category:** Ideas & Suggestions\
**Tags:** featurerequest\
**Created:** [February 22, 2026, 10:58am UTC](https://community.homey.app/t/feature-request-logic-as-time-in-energy-flowcards/151502 "2026-02-22T10:58:25Z")\
**Posts on this page:** 9\
**Page:** 1

<div class="post-metadata">

**Author:** ![Daderu](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/daderu/32/107948_2.png) [@Daderu](https://community.homey.app/u/Daderu)\
**Post date:** [February 22, 2026, 10:58am UTC](https://community.homey.app/t/feature-request-logic-as-time-in-energy-flowcards/151502/1 "2026-02-22T10:58:25Z")

</div>

I would love to have the ability to use logic in te “Time” parts of the Energiecard:

(Tijd - Dutch for Time)

 ![IMG_0017](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/9/9/997577738b7c88d168db66f88b3e4b56084d81d6.jpeg)

This could give the ability use the current time and for example the time I need te car. As “aantal uur” (hours) can already be used with logics (hour needed to charge to full for example).

In Power by The Hour this is already possible, so I think it is an easy fix. I know I can use that app, but it doensn’t have this easyness to find the cheapest hours between given times.

---

<div class="post-metadata">

**Author:** ![Peter\_Kawa](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/peter_kawa/32/173848_2.png) [@Peter\_Kawa](https://community.homey.app/u/Peter_Kawa)\
**Post date:** [February 23, 2026, 3:01am UTC](https://community.homey.app/t/feature-request-logic-as-time-in-energy-flowcards/151502/2 "2026-02-23T03:01:44Z")

</div>

> [@Daderu](#):
>
> but it doensn’t have this easyness to find the cheapest hours between given times.

I think in that case you should ask the PbtH dev why PthH hasn’t got this ‘easyness’, or if he would consider adding it.

---

<div class="post-metadata">

**Author:** ![Daderu](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/daderu/32/107948_2.png) [@Daderu](https://community.homey.app/u/Daderu)\
**Post date:** [February 23, 2026, 5:18am UTC](https://community.homey.app/t/feature-request-logic-as-time-in-energy-flowcards/151502/3 "2026-02-23T05:18:42Z")

</div>

You are right, and I also added a feature request there, but I also proceeded with this feature request, because this is a standard build-in card. And why would we stop making those better if that is a possibility?

---

<div class="post-metadata">

**Author:** ![Peter\_Kawa](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/peter_kawa/32/173848_2.png) [@Peter\_Kawa](https://community.homey.app/u/Peter_Kawa)\
**Post date:** [February 23, 2026, 5:55am UTC](https://community.homey.app/t/feature-request-logic-as-time-in-energy-flowcards/151502/4 "2026-02-23T05:55:59Z")

</div>

Ah I see. I didn’t say to withdraw the feature request, as many other triggercards don’t accept tags or variables as well.  
But this PbtH card does exactly the same, only the `from [time] to [time]` part, like  
`from 2AM to 8AM`  
is written as `the x hours before [time]`, like  
`the 6 hours before 8AM`  
which is the same

 ![Screenshot_20260223_064941_Ecosia](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/4/3/4305d5008b19ee69874c51dfeb175d9411d5fa5a.jpeg)

I think it’s differs for everyone which one is considered the easier one.

---

<div class="post-metadata">

**Author:** ![Robkrekel](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/robkrekel/32/113089_2.png) [@Robkrekel](https://community.homey.app/u/Robkrekel)\
**Post date:** [February 23, 2026, 6:14am UTC](https://community.homey.app/t/feature-request-logic-as-time-in-energy-flowcards/151502/5 "2026-02-23T06:14:20Z")

</div>

Wow, now I understand these trigger cards. It’s before time xx instead of for xx period.

Sometimes trigger cards are interpreted differently by me.

---

<div class="post-metadata">

**Author:** ![Daderu](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/daderu/32/107948_2.png) [@Daderu](https://community.homey.app/u/Daderu)\
**Post date:** [February 23, 2026, 6:42am UTC](https://community.homey.app/t/feature-request-logic-as-time-in-energy-flowcards/151502/6 "2026-02-23T06:42:40Z")

</div>

True! I get it, but to determine the X Hours before [TIME], there is some extra calculation needed. e.g.: [TIME] - Time now. And calculation with time is quite a challange. Hence my refference to easyness. Or do i see harder challanges ahead, that actually are pretty easy to solve?

---

<div class="post-metadata">

**Author:** ![Arie\_J\_Godschalk](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/arie_j_godschalk/32/63027_2.png) [@Arie\_J\_Godschalk](https://community.homey.app/u/Arie_J_Godschalk)\
**Post date:** [February 23, 2026, 8:15am UTC](https://community.homey.app/t/feature-request-logic-as-time-in-energy-flowcards/151502/7 "2026-02-23T08:15:01Z")

</div>

> [@Daderu](#):
>
> And calculation with time is quite a challange.

The BetterLogicLibrary app has special cards and functions for handling time and dates.

---

<div class="post-metadata">

**Author:** ![Rmb](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/rmb/32/79135_2.png) [@Rmb](https://community.homey.app/u/Rmb)\
**Post date:** [February 23, 2026, 8:38am UTC](https://community.homey.app/t/feature-request-logic-as-time-in-energy-flowcards/151502/8 "2026-02-23T08:38:04Z")

</div>

> [@Daderu](#):
>
> And calculation with time is quite a challange

Epoche time makes life easier. There are several posts how to use it.

---

<div class="post-metadata">

**Author:** ![Daderu](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/daderu/32/107948_2.png) [@Daderu](https://community.homey.app/u/Daderu)\
**Post date:** [February 23, 2026, 9:16am UTC](https://community.homey.app/t/feature-request-logic-as-time-in-energy-flowcards/151502/9 "2026-02-23T09:16:16Z")

</div>

I’m going to try this! Thanks for the advice!
