I had 1.14 firmware resent to me. This was last week. It was in an attempt to fix a problem outlined here
None of my Z-wave devices turn off whether it be set to a specific time or using the sunrise parameter as an off time.
I have resaved the rules and also deleted and recreated the rules from scratch to no avail.
I’ve heard a similar issue recently (different firmware though).
Are any of your rules set up with one rule controlling “on” and a separate rule controlling “off” or do you have them set as for example:
Turn On at XX:XX then turn off at XX:XX.
Try setting an on rule. then create a separate rule to turn it off. Does that work as expected?
Jason,
My next step was to do this. But I sure wish ADC would just fix this. As you know, this was a complaint I had and it took a year for them to resolve, which they eventually did (after blaming my equipment for a year or so). I think it is reasonable to expect that they things they have out there should work (eg ways to configure rules).
ADC seems to never want to make it a priority to get to the “root cause” of things. I repeatedly ask in this threads (did they every figure out WHY?) https://suretyhome.com/forums/topic/lights-dont-come-on-after-daylight-savings-change/page/7/
On a side note (I still believe that my panel rearming sporadically at 2:30 AM is on their end, but I doubt they are going to try and research it and just say “buy a new panel”). They offer no assistance to Suretycam, in my opinion, to try and help you guys get to the root cause here.
I will make the separate rules now to see if that fixes it, but it certainly is messy to do it this way
I will make the separate rules now to see if that fixes it, but it certainly is messy to do it this way
The suggestion is not a fix. It is just a troubleshooting step to determine if separate rules have a beneficial effect. If it does work, it can be used as a “bandage” temporarily.
I can assure you that Alarm.com offers the best dealer support I have encountered anyway. Keep in mind there are no blanket fixes and issues must be resolved on not only a panel basis, but on a revision and firmware basis. On 2GIG alone that means possibly double digit panel performance variations to test and adjust coding.
I still believe that my panel rearming sporadically at 2:30 AM is on their end, but I doubt they are going to try and research it and just say “buy a new panel”
I understand the concerns due to DST, but a few things to keep in mind:
Concerning the central topic, can you verify that this started immediately following the firmware update? Or did any of the rules work even once after?
My automation issues with the lights happened immediately after the update
The strange thing on this issue is that before, only the schedules would fail. For example the items that turn off and off at a specific time.
Now, everything fails including sensor triggering actions, when you have things like “when door opens during this time to this end time turn on a light”. This is different than a scheduled on and off time. This did not happen before
It wont execute the end time so the light continues to turn on when the door is opened when the rule starts.
Hmm, so even the times when a triggered rule would no longer be valid are not being followed? But the rule does function properly by all other parameters?
That is definitely different. I am going to have ADC rebuild all rules, hopefully syncing that back up. That is a failure I’ve never heard.
Today the sensor activated rules seems to work.
However my landscape lights still do not turn off despite having a separate off rule created. I have it set to turn off 15 minutes before sun rise
All devices are able to be turned off manually by the app so it looks like they are all working. Rules are just not working to turn these off. I suspect it has something to do with the “sunrise” parameter.
I suspect it has something to do with the “sunrise” parameter.
That is possible. Can you try switching a couple to a specific time and let us know?
And just to verify, all of the sensor activation rules with a specific end time worked?
Yes, I can try
Yes, all the sensor based rules work. You are not allowed to select sunrise or sunset for those as you know. It would be nice if you could in the future and if they worked the bugs out first in the sunrise parameter. It’s seems to have been problematic in the past
My lights again did NOT turn off.
I had them set for a specific time (6:00 AM) to turn off and they did not. The off command was in the same rule that contained the off command.
I will now create a separate off command with a fixed time.
But perhaps in the meantime you can have ADC, rebuild my current rules?
I will now create a separate off command with a fixed time.
Ah, yes, that’s what we want to test. Even if it is just a couple of the rules, which would give us both dual fixed time rules and single on/single off rules to track.
We’ll have ADC send some troubleshooting commands. Let us know which rules work and if there is a pattern. This will help with a quicker resolution. (Hopefully all do, but I have a hunch that based on what you are saying only the single on, single off will)
There seems to only be two sets of rules that are failing. The Front Porch rules and the landscaping lights rule where multiple lights are selected.
Separate rule to turn off was created so I will let you know tomorrow morning
The rule set at a specific time and broken out seperatly worked and lights went off. Can we work on the sunrise issue and the fact that it won’t work unless broken out separately?
Thank you, that’s a good test. We will update Alarm.com with this and see if there are some additional steps to take or if a potential fix can be remotely applied.
New problem. None of the zwave lighting rules that are turning on with times set under sunset. So in summary, now lights don’t come on during sunset and also do not turn off during sunrise
Could you please make this a priority to resolve as this is now a security issue as my home is in the dark now at night and I am traveling this week
Have you tried any of these rules without the “Make Times Approximate” button checked? Just to verify, how long are you waiting to determine that the rules do not trigger?
I don’t have the rules set to make time approximate. I wait until the next day to see if the rules work
Sometimes I wait 2 days to see if a complete cycle of day will fix it.
What is ADC saying about all of this? This is a long standing issue that has happened in the past.