Error: Host not active

nokoston · January 12, 2009, 5:24pm

Hello,

Just curious as I’ve been getting more and more of those lately … Trying to connect via findvera.com or localhost, I now sometimes gets those “FAIL: Host is not active” error and the only way to recover is to unplug/replug my vera box (running 426). Am I the only one seeing this?

thanks,
-j.

nokoston · January 13, 2009, 3:00am

mmh, so I came home tonight and vera was still giving me the same error … except this time, powering off/on the box didn’t help (couldn’t connect using local IP, findvera did find it but was really having issues loading the dashboard).

So, I double-tapped the black reset button in the back and now it works even less findvera.com does find my ra server (and IP of my vera box), I can log in … but then I get the “ERROR: Host is not active - Your host cannot be accessed. Please check that the host is powered on and has a working internet connection.”

Trying to access via the IP just show me the “loading” gif anim but never get to the UI.

I wrote an app to control vera and prior to reset I was still able to control my lights with my tool but now that I have resetted it, I don’t see any room or anything …
Doing a data_request for zwave status works and returns 1 1 (ie, ZWaveNetworkStatus/JobStatus is zws_OK).

Is there any other kind of hard reset I can give a shot (I know I’m already going to have to resetup everything anyway)?

Note that the box has been starting to give me those issues during the holiday breaks, around 423-426 updates (not sure if this is related though).

ANY kind of help would be much appreciated as right now my box is totally useless … if you need access or more information, I’d be more than happy to provide anything needed.

thanks,
-j.

nokoston · January 13, 2009, 3:23am

Note also that zwave status is returning expected values … so some parts are working but I can’t access any web interface to reorganize or control anything :

1 1
11 0 0 1 1 0
12 OFF/0 1 0 4 4 Job completed ok: Successfully polled node 0
13 ON/62 1 0 4 1 0
14 ON/35 1 0 4 1 0
15 ON/60 1 0 4 4 Job completed ok: Successfully polled node 0
16 OFF/0 1 0 4 1 0

(just trying to add info in case it helps understanding/debugging what’s going on with my setup)

nokoston · January 13, 2009, 10:54pm

MCV, any chance you could help out here (or provide suggestions on things to try out)?

nokoston · January 15, 2009, 5:13am

just wanted to put a little update: not sure what really helped but after resetting my vera box couple of times, removing my airport extreme from my home network, and then putting it back … things appears to be working again.

Alex · January 16, 2009, 7:08pm

Hello nokoston , usually this kind of errors appear when we are working at the system, (but they shouldn’t last long), so for this kind of situations, is recommended that you just reload the page, after a while :

nokoston · January 16, 2009, 8:14pm

yeah, not sure why it lasted so long this time. I tried to reload, tried different browser as well (both connecting via local or findvera.com). Maybe there were something fishy in my setup (although I didn’t change anything and it’s same setup again now that it was before - yet it’s working now).

Anyhow, I’m glad to be able to control my devices remotely again!

thanks,
-j.

micasaverde · January 19, 2009, 2:25pm

Once you double click the black button, it does a complete factory reset. So your vera will no longer contact the findvera server and enable to remote access until you go to the findvera.com tab on Vera’s web setup page and enable the remote access service again. My recommendation is that, when it happens, and it’s in a bad state, rather than resetting it or powering it off and on, just go to live chat on micasaverde.com, support, or call our tech support line. Even after hours, the calls are forwarded to our tech’s cell phones so someone can usually respond.

Then we can see exactly what’s wrong and fix it permanently, as opposed to just resetting the box until it works. When users have called us while the box is in a ‘bad state’, we’ve been able to track down the cause and, so far, in every single case, upload a permanent fix. It’s usually some peculiarity with your particular network that we have to account for. The last time, for example, it was that the dhcp server in the user’s dsl modem gave out the ip address before the pppoe connection was active, so we added a retry timeout to work around this. All these issues are resolvable if we can get at the box and “catch it in the act” to see what’s wrong.