SET Time for rule

---

Maybe it is already possible (but I have not found it…)? Would it be possible to set a time value in web interface. This value is used in a rule to execute something at the set time? A bit like setting your alarm clock. Now I have, for example a light, which switch off at a specific and I have to edit the rule to change the time. That is an impossible task to explain to my wife… So maybe some time indication with an up and down button?

@dynamite
envagyok has share a nice soulution based on a shell script, buttons and a time variable. have a look here. I use it since some weeks as alarmtime input to turn on the radio by rule and it works great. The alarmtime can be increase derease by pressing + or - buttons in the Frontend or by rules.

If its $alarmtime then turn on radio
If $weekend changes and $weekend = 1 then press +1h button
If $weekend changes and $weekend = 0 then press -1h button

@magic-tune
yes, this is a workaround but it should be made easier for the user since changing times and variables is a thing that a pimatic user needs some time imho.

@dynamite
nice idea but at the moment there’s no such device.

what about an input field device for time values, numbers and string text that would be implemented to the pimatic core. this could all be done within one device. The value type (numer, string, time etc). will be chosen by the user if no auto discovery is possible (don’t know if this is realizable)

maybe this is an approach :

    {
      "id": "variable-input-device",
      "name": "Input field for serveral purpose",
      "class": "VariableInputDevice",
      "attributeType": "number", (string or time)
      "fieldlength": 10
    }

when time is chosen, maybe there could be + and - buttons beside the input field for changing the time value up and down (maybe in 5 minute steps)
fieldlength just for example if needed ?!

here’s a mockup for a time input device

and here for a text or number device

@leader21 Nice elaboration on the value set idea! It is exactly what i meant by my Original post. When can I start using it

Take a look on this topic : http://forum.pimatic.org/topic/584/how-to-make-user-configurable-start-and-stop-times-in-pimatic

take a look at this new device
http://forum.pimatic.org/topic/97/feature-free-text

@leader21 or like this:
http://forum.pimatic.org/topic/832/set-time-via-gui-google-style

@n3ro said:

@leader21 or like this:
http://forum.pimatic.org/topic/832/set-time-via-gui-google-style

nice to have but imho it does not suit to the “simplicity” of pimatic (if you know what i mean?)
let’s see what @sweetpi can make out of the actual input device. there’s still a lot of potential to be unlocked.

This should work: ‘23:20’

It works for me to send this from tasker and change a variable in pimatic.

Hi all, i try the following.

I have a variable input device with number. for exmple the number is 20.

Now i would create a rule like this:

if it is $variableinput minutes before sunset then move x up

but i can not create this rule because it is not possible to say “$variable minutes after/before…:”

it just works in the then part. but thats not what i need.

@developer could someone please change this?
it would be very nice.
Thanks in advance!

@p4co86
try this : if it is $variableinput minutes before sunset starts then move x up

Thanks, this does not work. After it is $variable I can only add and, or, for.

I think the code has to be changed.

ok i see! just testet and you are right.
i’ll open an issue on git.
maybe it’s just a small change.

check here :
https://github.com/pimatic/pimatic/issues/901

Thanks for that!

@leader21

@dynamite
nice idea but at the moment there’s no such device.

what about an input field device for time values, numbers and string text that would be implemented to the pimatic core. this could all be done within one device. The value type (numer, string, time etc). will be chosen by the user if no auto discovery is possible (don’t know if this is realizable)

maybe this is an approach :

    {
      "id": "variable-input-device",
      "name": "Input field for serveral purpose",
      "class": "VariableInputDevice",
      "attributeType": "number", (string or time)
      "fieldlength": 10
    }

when time is chosen, maybe there could be + and - buttons beside the input field for changing the time value up and down (maybe in 5 minute steps)
fieldlength just for example if needed ?!

here’s a mockup for a time input device

in what way did you implemented the InputDevice with the time?
Pimatic always give a error (attributeType is not a property type) when i said time for attributeType.

Oh sorry!! Time is not (yet) implemented. I just did a copy / paste and did not double check with the device config schema.
You can use string instead.

ok, thanks

@leader21 said in SET Time for rule:

what about an input field device for time values, numbers and string text that would be implemented to the pimatic core. this could all be done within one device. The value type (numer, string, time etc). will be chosen by the user if no auto discovery is possible (don’t know if this is realizable)

maybe this is an approach :

    {
      "id": "variable-input-device",
      "name": "Input field for serveral purpose",
      "class": "VariableInputDevice",
      "attributeType": "number", (string or time)
      "fieldlength": 10
    }

when time is chosen, maybe there could be + and - buttons beside the input field for changing the time value up and down (maybe in 5 minute steps)
fieldlength just for example if needed ?!

here’s a mockup for a time input device

I try my best to implement this feature in the next few weeks. Well, its my first time working with github and coffeescript, so I need some time to understand the basics of both. Plan is to start coding August, 3rd. Any help is appreciated

So far I have implemented a simple time input field as a new TimeInputDevice. I didn’t use VariableInputDevice because technically time (“23:58”) is a string. So I couldn’t distinguish between time and some other string.

Pro:

• it works
• browser implements the actual input behaviour

Con:

• no buttons (yet)
• Firefox (desktop) does not support input time yet. I think, I saw a bug report, that read, it should be fixed in Firefox 50.

Todo:

• buttons
• configurable step size (I suggest 15 minutes as standard)
• JavaScript fallback (to support Firefox)
• anything I missed?

Screenshots (Firefox on Android):

very nice!! thx a lot