Securifi Community Forum

Securifi Products => Almond+ => Topic started by: umami on January 07, 2017, 11:47:04 pm

Title: Almond+ has serious lag
Post by: umami on January 07, 2017, 11:47:04 pm
This issue has been intermittent on the last firmware rev, now seems to be a permanent condition with the most recent firmware update:

Activating a scene on the Almond+ takes somewhere in the order of 30 seconds for the system to respond, when it responds at all. Also have one outlet dimmer that no longer responds to the Almond+ at all, despite being recognized in the system. I've removed and re-added the dimmer with no luck. I have rebooted the router many, many times.

I'm controlling the system via the iOS app. Cloud connection works as described. Local connection does not work at all.
Title: Re: Almond+ has serious lag
Post by: Ashok on January 08, 2017, 11:58:50 pm
@ umami,

Request you to send us the log files, to find out why the Dimmer is not  working and also local connection doesn't work, are we making sure it is connect to Almond's network at that time?
Title: Re: Almond+ has serious lag
Post by: umami on January 09, 2017, 01:28:54 pm
Attempting to post log files and getting rejected by the server...

Naturally, everything is working today like it hasn't in weeks. I assume once this thread is closed, the Almond+ will return to its usual bad behavior.  ::)
Title: Re: Almond+ has serious lag
Post by: umami on January 14, 2017, 03:37:55 am
I am unable to upload the log files here, and my problems persist. Can you please tell me where/how to send the files?
Title: Re: Almond+ has serious lag
Post by: fillibar on January 14, 2017, 07:44:15 am
If you are using the app's Send Logs feature or the Send Logs from the Diagnostics on the LCD then it is all automatic and there are no files to email. If those are not able to be sent then it does need a little help.
Title: Re: Almond+ has serious lag
Post by: umami on January 16, 2017, 04:40:10 pm
Log files sent from the iOS app.
Title: Re: Almond+ has serious lag
Post by: umami on January 17, 2017, 06:04:27 pm
The issue persists, and varies from perfect operation to lag, to not turning on the dimmer in question at all. I should also add that the distance between the Almond+ and this sensor is about 15 feet.
Title: Re: Almond+ has serious lag
Post by: mparadis on January 17, 2017, 06:13:56 pm
How many devices are in the scene and are you activating it directly from the app or one of the other connected services (IFTTT or Amazon Echo)? I would try removing and re-pairing the problematic light because it may be causing an issue with the response of the other devices as well.
Title: Re: Almond+ has serious lag
Post by: umami on January 24, 2017, 01:19:30 am
I have about four devices in the scene, activating it from the Almond+ itself, the iOS app, and the web interface. There are now two devices in the system that respond intermittently and fail at random. I have removed and re-added, which does not solve the problem. I have sent log files to Securifi twice from the iOS app and have heard nothing from Securifi.

The Almond+ continues to frustrate me with inconsistent behavior two years into my ownership. In fact, if anything, it is worse than it used to be. There was a time when the exact same devices worked flawlessly. I've been struggling for months now with lights not turning on, not turning off, turning on unexpectedly, system lags, and so on.

Title: Re: Almond+ has serious lag
Post by: Ashok on January 24, 2017, 11:53:25 am
@ umami,

I am sorry for the delay, our guys are still debugging it and hopefully, by tomorrow, we would have an update. Thank you!
Title: Re: Almond+ has serious lag
Post by: Ashok on January 25, 2017, 08:51:21 am
@ umami,

It seems like for the same devices, multiple requests are going because Rules and Scenes got almost same actions. Is it possible for you to disable all the Rules for few minutes and then try to Enable scenes, check the performance?
Title: Re: Almond+ has serious lag
Post by: umami on January 25, 2017, 05:30:35 pm
@ashok, I disabled all rules and there is little change. One device remains unresponsive. The rest behave more or less normally, for now. I will test again this evening and see if anything changes.
Title: Re: Almond+ has serious lag
Post by: umami on January 28, 2017, 02:49:22 am
I'm literally laying in bed laughing as commands I sent to the Almond+ over a minute ago are causing the lights to turn off and on as though by someone else. Brilliant.
Title: Re: Almond+ has serious lag
Post by: mparadis on January 28, 2017, 03:21:39 am
Sounds like you have conflicting things set up. Care to share the rules / scenes you have created are.
Title: Re: Almond+ has serious lag
Post by: umami on January 31, 2017, 01:36:37 pm
I went through and cleaned up all the rules and scenes to remove redundancy. System is working better--I will track for a bit and update. Thank you for the ongoing help.

The difference between scenes and rules is a little confusing--it might be nice to have some examples in the help files to demonstrate how these work.
Title: Re: Almond+ has serious lag
Post by: mparadis on February 01, 2017, 10:44:46 am
Of course and good suggestion.

So for your benefit. A RULE is an action or series of actions that occur(s) after some trigger. The trigger can be something physical, like a light switch turning on, a door opening etc or it can be something like when your phone leaves the wifi network, someone else connects to the network, a time of day or related to sunset/rise etc.

A scene is a series of actions that occur at one time. This does not involve a trigger and is activated by pushing the "scene" button under scenes in the app (also can be done using IFTTT but that gets more complicated so for now we will leave it at that).

Actions can be anything including turn outlets on, lock doors, change colors of lights, thermostat changes etc etc. Basically anything you can do manually, you can set up as an action.

What you need to be careful of is overlapping rules. For example:
Rule one: If 7pm and the light is off then turn light on.
Rule two: If 8am and the light is on then turn light off.

This would turn the light on at 7pm and off at 8am.

But if you have another rule
Rule three: If light on and no motion then turn off light.

This could cause the light to flash repeatedly from the time of 7:00:00 pm until 7:01:00 because it is trying to the light on at 7 but if there is no motion it will keep trying to turn the light off which will turn the light back on. So the rule above may work as intended, but it may not, the best is to start simple and make incremental changes. So if there is an issue you can easily identify it. (FYI my example may not be the best but I was trying to be simple).
Title: Re: Almond+ has serious lag
Post by: cthree87 on February 02, 2017, 12:38:10 pm
I went through and cleaned up all the rules and scenes to remove redundancy. System is working better--I will track for a bit and update. Thank you for the ongoing help.

The difference between scenes and rules is a little confusing--it might be nice to have some examples in the help files to demonstrate how these work.

Rules are very powerful and add features IFTTT sorely lacks. Understanding how scenes, rules and IFTTT interact is the key to smooth automation. Good luck. BTW I have one Leviton zwave dimmer which is very laggy and flakey but other switches and dimmers that respond quickly and reliably. The cheapest ones I bought for $5 on clearance at Home Depot run circles around the $50 Leviton dimmers. Go figure. With these devices YMMV wildly.
Title: Re: Almond+ has serious lag
Post by: umami on February 05, 2017, 10:34:43 pm
Still having issues with one device not responding consistently. I've deleted all the redundant rules and scenes. The system was working perfectly for several days, and suddenly I have issues again.

I also have a Rule set that when my iPhone is inactive, set the scene to Away. This used to work a few months ago, but no longer. Wondering if the iOS app needs to be set to either local or cloud to register the iPhone as connected? I've tried it both ways to no avail.

mparadis: Thanks for the explanation--if what you typed had been in the help file, I would have been way ahead of the game.