I’m running 616, I upgraded firmware 2 days ago and loaded my first device successfully. It’s been working and accessible remotely as well as in home. This morning, the power light is out, so I unplug and replug and can access it via local IP (for a few minutes at a time). Then at some point after plugging in I’m no longer able to access it. I have no access to logs either, since the message “the host is not active” appears on the screen.
On the control page I’m seeing the following, all looks well so far,
Version: 1.0.616
Checking internet connection …
Loading system database …
Loading timezones.json …
Loading local database …
Loading sysinfo …
timezones.json loaded
Internet check status: ok
Then in red I get the following error:
ERROR loading local data, remote access service is not active.
The Internet isn’t a problem, it’s been plugged in and working, and I’m able to type this off the same router. I’ve plugged and unplugged a few times, no changes, same results. I think what I’m hoping for is some sort of general troubleshooting guide to help me figure this problem out (is it on my end, or not). I just can’t figure out the root cause of the problem.
Hmmm, after renaming the device in my AT&T modem (giving it a name), my problems seemed to start to disappear. I normally do that with all of my devices on my internal network, just hadn’t done it with the Vera yet as it’s new. The device stayed online and I was regaining access over a period to the rest of the functions. I’m definitely interested in knowing what was causing it, so I won’t freak out if it starts happening again. I opened it up for Tech Support if you all there want to look at it (I’ll be at work soon, not near the device though.) I could send the info offline or call later, if it helps, but with most tech problems, once the symptoms are gone, it’s hard to diagnose after the fact. No idea if it’s on the MiCasaVerde end or on my end.
>:( >:(
Hours and hours and hours later, my Vera is a virtual paperweight. It won’t communicate with the Internet whatsoever after dealing with tech support emails, DMZs, and dropping of firewalls. I can’t even get it to reset and work it with a local cable to the 81.1 address. I can’t sit at home during their hours and deal with daytime technical support, and I can’t bring the Vera and set up and run it at work.
Ease of set up? Super simple; no tech skills needed. I have a story for the FTC! If this product is ever going mainstream, problems like this have to be easier to resolve.
No kidding on the difficultly in getting it working properly. It seems there are always issues with the unit it self or not be able to even log on to my account on findvera. No kidding I have over 40 hours into getting 2 veras working. I do have a non standard wifi client setup but it was still way too much time for something that is sold as simple. Even when I just updated the firmware last weekend and told it to keep current settings(it didn’t) it took about an hour and a half to get them working properly again. The dumb part on my end in which I should have known better was to do the update over the web. It was down 2 days before I could get out to the rental property and get it going again. Always assume you are going to have to unplug it to get it working again is what I learned. Then redo your settings and then do another reset by unpluging and then it finally works again.
Update: Just tried to log into findvera right now and it’s not working. I put in the user name and password and the “Internet Explorer cannot display the webpage” comes up. There needs to be a face with steam blowing the top of the head off icon.
Well I had to reboot one of the Vera’s today because it wouldn’t communicate with the schlage locks today. It looks like it stopped some time yesterday morning because there was no logs after that time. >:( >:( Somebody make this thing reliable soon please!!! I even have them auto rebooting at 4am everyday. If I could just get them to go a full 24 hours without issue I would be so happy. I could even live with having to do the auto reboot.
The problems you’re describing are basic network connectivity. The message that ‘remote access is not active’ means you’re trying to login remotely through the findvera service, and the ‘remote access tunnel’ to your Vera is not open. All this basic network functionility actually isn’t even in our software, these are standard utilities within the core Linux operating system that have been around forever and are rock-solid. For example, the ‘remote access tunnels’ are actually implemented using ssh, which was invented in 1995 and is the basic way of handling remote network connections on all Linux servers and access points. So I don’t think the problem is actually software bugs. Something else is going on. It’s possible that you have defective hardware. However, whenever we’ve had reports of networking issues like this, in every case I can think of, the user has changed the default network settings. That’s why we always recommend leaving all the network settings in their default values and not changing anything on the net & wi-fi page.
Reiserx, txpatriot, can you still access Vera locally on your local home network, without the internet? By that I mean go to findvera.com and do not login, just click the green button to setup on your local network. If so, can you submit a trouble ticket (choose Advanced, Tech Support from Vera’s setup page), and tell it to submit the logs and local database. Include in the notes your username on the forum so we know it’s related to this thread. I’ll look at the trouble ticket and try to see what’s going on with your networking.
I had the same problem and fixed it today. I could login from Findvera.com but got the ERROR loading local data: remote access service is not active. I fixed it by using the green local button and click in the setup menu on the findvera.com button.
You have to signup at findvera.com again using the same user name and password. I guess that is the way it stores the info on the vera and after upgrade it was lost. After that vera works again.
It sounds like there wasn’t a malfunction, just a misunderstanding of how it’s supposed to work. We’ll try to update the login page on FindVera.com to make it more clear. Basically, the findvera page has 2 functions: the top half is for logging in to the findvera service, and the bottom half is for finding Vera’s on your local network to connect to directly. Before you can use the top half half to login, you must connect locally first and activate your findvera account. To prevent unauthorized access, you can only activate the findvera account from your home network.
Today my Vera started doing the same thing as that of txpatriot.
I have, in the past, been able to “back door” into vera from my ddns service by temporarily putting vera’s local IP address in the DMZ and connecting that way. That method has sometimes worked when I could not get through using findvera.com.
This time, that did not work either. My problem is that I’m 750 miles from vera, her reset button, and the wall plug! Any ideas for me?
I think I have the same problem. I upgraded the firmware a couple days ago. I thought it was working since then but last night it seems to have mostly stopped responding to remote access. And local access too.
This sounds like a different problem. Sometimes I get as far as the “start” screen that has the firmware versions and stuff but I can’t get to Dashboard or Devices before the ra1 error.
Ok, some more info. I power bounced Vera and it was working again (or so I thought?). Saturday I was using the PC at home and it wasn’t working and then the internet went down. I don’t use Vera as my router but instead use the Verizon supplied router. I bounced this and things came back to life. I checked the log on the router and Vera was logged as having some outbound SYN problem and no more NAT connections available.
This was odd and the Verizon router died again a few minutes later. I turned Vera off but still had the internet go down after about 5 minutes and I repeated this process a few times until it was stable. Then turned Vera back on and it all has worked fine since then.
I suspect the Verizon router going bad but I don’t really know what was going on. When it was going bad it was half working and the symptoms didn’t make sense. Also the router is 2 years old rarely needs rebooting. And Vera has happily worked for a couple months until I upgraded the firmware (?).
So at this point I don’t know what is going on. Maybe the Verizon router is on the way out or maybe the Vera is acting wonky. Have to wait to see but I am glad it is functioning again.
Best Home Automation shopping experience. Shop at Ezlo!
>:( >:(