Thanks for that!
-
SET Time for rule
-
@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.pimatic v0.9 has been released!
Support Pimatic and get some free stickers
Like us on Facebookmake it so !
-
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
pimatic v0.9 has been released!
Support Pimatic and get some free stickers
Like us on Facebookmake it so !
-
I opened a pull request a week ago. Would be nice if someone could have a look on it
-
sure, already have seen it and taken to the dev team.
will be reviewed and merged shortly if all is ok
we’re a bit laggy due to holiday season ^^
thx again !pimatic v0.9 has been released!
Support Pimatic and get some free stickers
Like us on Facebookmake it so !
-
@leader21 thanks a lot. I just got a little nervous, because I encountered CoffeeScript and Jade for the first time and hope I did it right
-
Is this device already avaiable?
Can’t find any Time Input device… -
ah… found it “VariableTimeInputDevice”
-
Sorry for digging up this old thread but how do I implement the given time into a rule?
I’m looking for something like this:
If it is 30 minutes before $Alarmtime then switch on Bedroomlight with transition time 30 minutes.
I was striving to get back my rising sun in my bedroom