This is the forum archive of Homey. For more information about Homey, visit the Official Homey website.
The Homey Community has been moved to https://community.athom.com.
This forum is now read-only for archive purposes.
The Homey Community has been moved to https://community.athom.com.
This forum is now read-only for archive purposes.
Comments
This sounds like a new app. Then you make triggers in start and finish of the specific schedule.
Can't wait to get my hands on the Homey update and your Better Logic !
Thanks for the good work, just made a donation.
Thanks! Much appreciated! Feels great everything the PayPal notifies me with a notification!
* Feature: Added #DD (day), #MM (month), #YYYY (year), #HH (hours), #mm (minutes) #SS (seconds) as reserved words next to timenow in the mathjs flows. You can now for example assign #HH to a variable to get the hours. Also I changed timenow to #timenow for consistency.
Hope it helps!
(small snippet of the new global tags you have in the flow editor)
To make it more usefull, during adding of the device you can select the min/max and step values. So, besides the why, because I can, I think there is a usecase.
Just wondering how I could maybe use this myself
Hm, that might really come in handy indeed!
The sliders sound amazing as well, I can think of loads of uses (especially in combination with HomeyDash for example)
I use timenow in some mathjs cards, you write you changed timenow to #timenow, do I have to change the cards?
Example:
Nope, kept the old one so you won't be mad at me
How to round a number to half decimals
example:
i got a #Outside_Temperature which is -2.4 __ I want it to be changed in -2.5
if i use: round(#Outside_temperature) to (#Rounded_Outside_Temerature) it gives me the number -2
Can someone tell me how to do this?
thanks in advanced
First you multiply the numer times 2, you round and then you devide to 2.
so that would be -2.4*2 = 4,8 -> round that would give -5. Devide it by -2 would give -2.5.
If you want to do it with steps of 0.25 you can do the same trick but use 4 instead of 2.
Hope it helps!
Well, I don't mind if it's changed and brought in line of the other date/time related variables, I think in the long run it would make things easier. So if you change it and give us a heads-up on how to change our flows I have no problem with it.
Thank i appreciate it.
I check a dim value from a hue light for beeing bigger then 0,99.
In a test with entering a value the evaluation is correct.
When I set the dim level of the light to 100% the evaluation goes wrong.
When I make a flow that reportsthe dim level it reports 1 when the dim level is set to 100% so the evaluation should have been correct
(On a side note, it would be more logical if 100 was reported when brightness is set to 100% the way it was in earlier builds, but @emile thinks it's correct this way: https://github.com/athombv/homey/issues/958#issuecomment-257541512)