bottleneck
Choose style:

Author Topic: Almond+ Sensors slow response  (Read 6427 times)

0 Members and 1 Guest are viewing this topic.

Offline vansens

  • Backer
  • *
  • Posts: 29
  • Thanks: 0
  • Registered : 02/08/2013
    YearsYearsYearsYearsYearsYearsYearsYearsYearsYearsYearsYears
Almond+ Sensors slow response
« on: September 08, 2014, 10:22:19 pm »
Hi,
I hooked up the router on Friday with 3 power switches, 1 door sensor, 1 motion sensor, all from Securifi.
Somehow, the power switches are extremely laggy in responses. This is via connect.securifi.com, the router web interface and the Android app.
"Cannot connect, please retry" after almost 10 seconds is what I see often. If I do get the switch to change state, I have to wait about 5 seconds before I can even try to toggle it again.

Does anyone else have that speed issue? Any hints would be appreciated!

LGNilsson

  • Guest
Re: Almond+ Sensors slow response
« Reply #1 on: September 09, 2014, 05:41:38 am »
I only have one. Do you have a USB 3.0 device plugged in to your Almond+?
We've found that some USB 3.0 cables are interfering with ZigBee and in as much as we did what we could to try to shield things internally, some cables are of poor standard and are causing 2.4GHz interference.

Offline vansens

  • Backer
  • *
  • Posts: 29
  • Thanks: 0
  • Registered : 02/08/2013
    YearsYearsYearsYearsYearsYearsYearsYearsYearsYearsYearsYears
Re: Almond+ Sensors slow response
« Reply #2 on: September 09, 2014, 01:30:07 pm »
Indeed. I have a USB 3.0 WD Passport drive hooked up to it.
I just disconnected it and all is well again, sensors respond within .4/.5s


Any solution in sight for this one?
« Last Edit: September 09, 2014, 08:32:48 pm by vansens »

LGNilsson

  • Guest
Re: Almond+ Sensors slow response
« Reply #3 on: September 09, 2014, 10:33:55 pm »
The only thing you can really do is to change the USB 3.0 cable.
We've tested a few local brands, but we're going to get some cables in to test so we have a list of ones that work well, as it's impossible to tell from just looking at the cables.
This shouldn't be happening, but apparently some cable manufacturers aren't following the standards properly and then you end up with issues like this.
We're also working on an option to change ZigBee frequency to see if that will help alleviate the issue, but this isn't going to be ready for a while.

 

Page created in 0.03 seconds with 16 queries.

bottleneck