Securifi Community Forum

Securifi Products => Almond 3 => Topic started by: Kinggovernator on July 25, 2018, 12:21:01 am

Title: Arming locations not saving consistently
Post by: Kinggovernator on July 25, 2018, 12:21:01 am
So I have had this problem for sometime. The system arms every night at 12:10 am. I have noticed that every few days it doesn’t  arm the main A3. I have it checked as one to monitor. It unchecks it’s self from my security devices to monitor. If this is not monitored will the siren still go off? And I’m sure it shouldn’t be unchecking it self like this!? Any feed back would be nice ..... I plan on trying to arm it w out it being selected as a device to see if it goes off or not when another device is tripped.
Title: Re: Arming locations not saving consistently
Post by: vikas jilla on July 25, 2018, 12:41:27 am
@Kinggovernator

I have a few doubts:
"The system arms every night at 12:10 am" -- do you have a rule for this to happen?
"every few days it doesn’t  arm the main A3." --  does this mean you have mesh network and in it, all the secondary almonds are getting armed except primary(which I am assuming as the main A3)?
"I have it checked as one to monitor" -- by this, do you mean the location of the main A3 is checked, in the app screen where we show all the locations that can be armed and with options like "instant arm", "arm after Xs", "save locations"?
and please do send logs when this happens. Thank you!
Title: Re: Arming locations not saving consistently
Post by: Kinggovernator on July 25, 2018, 02:41:54 am
Yes I have a rule to arm at 12:10am every night.
Yes I have 3 A3s in mesh. As far as I know they are all arming correctly as well
And yes I have the main A3 in our bedroom listed as “master bedroom”.  And when you go to the section in the app “select locations to arm” it will uncheck it’self. Now this varies from a day to a few days where it will arm as it should. Idk if reboots are causing this maybe? But I have Saved this location to arm numerous times but like I said every so often it unchecks itself  to be armed.
Title: Re: Arming locations not saving consistently
Post by: vikas jilla on July 27, 2018, 02:22:19 am
Hi @Kinggovernator

Thanks for sharing the details. We are working on it to reproduce. Can you please tell if the secondary Almonds are connected wirelessly or with wire?
Title: Re: Arming locations not saving consistently
Post by: Kinggovernator on July 27, 2018, 07:13:44 am
The 2 satellite A3s are both being used wirelessly. It hasn’t done it in a few days but when it does i will send logs. Thanks
Title: Re: Arming locations not saving consistently
Post by: vikas jilla on August 01, 2018, 01:00:45 am
Okay thank you!!
Title: Re: Arming locations not saving consistently
Post by: Kinggovernator on August 20, 2018, 01:01:19 am
Well went almost like 2-3 weeks without any issues w the arming locations issue. Did it twice over the weekend. The first one was unusual, during the arm which I did myself it unsleceted windows/doors location. It’s never done that to my knowledge. Which in itself says it all, not arming any of my window and for sensors which isn’t good. I disarmed and reselcted that location. Then again tonight it didn’t it again w my rule to arm at 12:10. This time the master bedroom unselected it’s self. This is the one that usually does it and it’s the main almond. I sent logs w a simular description.
Title: Re: Arming locations not saving consistently
Post by: RichardS on February 05, 2019, 10:51:40 am
I have been experiencing this problem as well for quite some time, and have had service tickets out on it. The problem is in the cloud as best I can tell, and still remains unresolved. They're working on it, last I heard. Basically, I don't trust what zones it says are armed. Since we only Arm manually, every time before Arming, I uncheck all of the zones, Save, check all of the zones I want Armed, Save, and then Instant Arm. It's a pain in the butt, and my wife is tired of dealing with the work around. She wants something that just works, and for whatever reason, ours doesn't.