Securifi Community Forum
Securifi Products => Almond+ => Topic started by: jnowland on February 12, 2015, 12:51:52 pm
-
I updated my firmware last night and the rules, which previously did not work now work. However, it would be nice to be able to edit the rules instead of having to delete and re-create to make changes. Also, and switch I have, be it GE/JASCO or Linear only show up with a dimming option. No "on/off" option as the GE Wink bulb has. Without being able to use the number pad to enter a percentage value, if I want to light to come on in full brightness, I have to manually click the up arrow until it reaches 99. Any advise? Thank you
-
I think that is actually just how that switch works. I know even when I use my physical switch to power on/off it actually fades up/down depending on whether I am turning it on or off. It took a while to get used to hitting the switch and instead of the attached lights shutting off, they slowly dimmed down to off.
-
I'm not referring to how the switch works, or even the Almond APP. I was referring to the Rules. When setting up a Rule, there is only a dimming option. One of the switches I have connected to a light, which does not dim with the switch. Therefore, simply having the option to set up a rule to shut on/off would be better then only having a dimming option.
-
+1
it would be nice to be able to edit the rules instead of having to delete and re-create to make changes.
-
When creating rules between times of day, I keep getting error "invalid time" and it will not accept that part of the rule. Tried creating the rules 4 times with the same error. Any suggestions?
Rule I'm trying to create: Between 6pm - 6am + door open, then entry lights come on.
-
Lars/Securifi have documented this limitation in the just released version: that rules cannot cross the midnight boundary (if I read that correctly).
It's stated that the limitation will be removed in followup releases.
http://wiki.securifi.com/index.php?title=Rules_UI_-_Almond%2B_2014#Complex_timer_rule
-
Lars/Securifi have documented this limitation in the just released version: that rules cannot cross the midnight boundary (if I read that correctly).
It's stated that the limitation will be removed in followup releases.
http://wiki.securifi.com/index.php?title=Rules_UI_-_Almond%2B_2014#Complex_timer_rule
The not crossing midnight is not new. The problem with 70 is that when you try the work around of 2 rules that worked in 69cb ( rule 1 6:00pm- 11:59 PM, then rule 2 from 12:00AM- 7:00AM ) The 12:00-7:00AM keeps resetting itself to 0:00-0-01 . I have tried varying the start time 12:00; 12:01; 12:05, 12:15 and it doesn't seem to matter it always resets itself to 0:00-0:01.
I just gave up on the "between" assuming nobody should be touching lights in the middle of the night anyways. Did 2 rules "if off than on at 12:01 and if on then off at 7:00AM.
-
The not crossing midnight is not new. The problem with 70 is that when you try the work around of 2 rules that worked in 69cb ( rule 1 6:00pm- 11:59 PM, then rule 2 from 12:00AM- 7:00AM ) The 12:00-7:00AM keeps resetting itself to 0:00-0-01 . I have tried varying the start time 12:00; 12:01; 12:05, 12:15 and it doesn't seem to matter it always resets itself to 0:00-0:01.
I just gave up on the "between" assuming nobody should be touching lights in the middle of the night anyways. Did 2 rules "if off than on at 12:01 and if on then off at 7:00AM.
My second rule for my motion detector to turn on lights is like that. It was entered as 0001 -0800 to turn on a light with motion, but shows as yours does. I have found that the rule still works as I entered to though.
-
This is a UI bug and will be fixed.