Choose style:
« previous next »
Pages: [1]   Go Down

Author Topic: Issue Linking Almond  (Read 9655 times)

0 Members and 1 Guest are viewing this topic.

Offline mrv777

  • Backer
  • *
  • Posts: 52
  • Thanks: 0
    • Registered : 02/08/2013
    YearsYearsYearsYearsYearsYearsYearsYearsYearsYearsYearsYears
Issue Linking Almond
« on: July 12, 2014, 03:19:16 pm »
I just received my Almond and I'm trying to Link it to my account.  I get the Almond to generate a code, I enter it in the web interface, and the Almond says it is linked.  The web interface says Oops though and that it couldn't be linked. 

Any thoughts?  Thank you
Logged

Offline dbuttke

  • Backer
  • *
  • Posts: 114
  • Thanks: 0
    • Registered : 12/08/2013
    YearsYearsYearsYearsYearsYearsYearsYearsYearsYearsYearsYears
Re: Issue Linking Almond
« Reply #1 on: July 12, 2014, 03:29:04 pm »
Yeah I have noticed that the web interface and the android app and the touchscreen don't say the same things.
For instance I'm connected through the AP right now via ethernet and my android app that is connected to it wireless says Zero connected devices and users!!
Logged

Offline mrv777

  • Backer
  • *
  • Posts: 52
  • Thanks: 0
    • Registered : 02/08/2013
    YearsYearsYearsYearsYearsYearsYearsYearsYearsYearsYearsYears
Re: Issue Linking Almond
« Reply #2 on: July 12, 2014, 04:28:10 pm »
Were you able to get your almond+ linked to your online account?  It seems I can't use the phone app until I do that.  I tried unlinking the account on the almond and linking it again.  The same thing happened though.
Logged

Offline dbuttke

  • Backer
  • *
  • Posts: 114
  • Thanks: 0
    • Registered : 12/08/2013
    YearsYearsYearsYearsYearsYearsYearsYearsYearsYearsYearsYears
Re: Issue Linking Almond
« Reply #3 on: July 12, 2014, 04:55:30 pm »
yes I was able to get it connected to my account. I even disconnected it and reconnected it using another key.
Can't do anything buy reboot it if you don't have home automation stuff though.
Logged

Offline mrv777

  • Backer
  • *
  • Posts: 52
  • Thanks: 0
    • Registered : 02/08/2013
    YearsYearsYearsYearsYearsYearsYearsYearsYearsYearsYearsYears
Re: Issue Linking Almond
« Reply #4 on: July 12, 2014, 07:11:15 pm »
The only thing I can think is that it doesn't like that I switched it to a 192.168.xxx.xxx address.  My network was setup to work with those addresses though and their are static addresses, so I didn't want to change everything.  Is there a known issue with that?

Thank you
Logged

Offline eldaria

  • Kickstarter Developer
  • *
  • Posts: 313
  • Thanks: 1
    • Registered : 26/07/2013
    YearsYearsYearsYearsYearsYearsYearsYearsYearsYearsYearsYears
Re: Issue Linking Almond
« Reply #5 on: July 14, 2014, 04:11:22 am »
Quote from: mrv777 on July 12, 2014, 07:11:15 pm
The only thing I can think is that it doesn't like that I switched it to a 192.168.xxx.xxx address.  My network was setup to work with those addresses though and their are static addresses, so I didn't want to change everything.  Is there a known issue with that?

Thank you

Well during the Beta period the Almond was in the 192.168.1.0 network. I personally had to change that since my existing network was also on this IP range.
The reason was that when the Almond tried to use this same range the routing no longer works since it does not know where to route the traffic when two interfaces have the same network.
Logged

Offline occlusion

  • Backer
  • *
  • Posts: 2
  • Thanks: 0
    • Registered : 14/08/2014
    YearsYearsYearsYearsYearsYearsYearsYearsYearsYearsYears
Re: Issue Linking Almond
« Reply #6 on: August 14, 2014, 04:16:48 pm »
I still have this problem even after I updated the new firmware today.
Is this known issue? Securifi Staffs have not replied in this thread though...
Logged

LGNilsson

  • Guest
Re: Issue Linking Almond
« Reply #7 on: August 23, 2014, 11:00:19 pm »
Shouldn't be a problem at this point, but can you please email support@securifi.com so we can have someone look into it.
Logged
Pages: [1]   Go Up
« previous next »
 

Page created in 0.029 seconds with 17 queries.

bottleneck