This is a major issue. Don’t worry. We’ll fix it this week, I promise. What I need, though, is to see what’s caused it. As an FYI, there were over 100 new Vera’s that went online in the first few days, and only you two reported it. So it’s not so easy for us to figure it out.
What I’d kindly ask is that when either of you is in front of your computer and can spare about 10 minutes with me, call me at: (866) 966-casa, or (702) 487-9770 and enter extension 803. I’m going to be in the office all weekend. If I have you on the phone when you’re in front of your computer I can show you how to turn on remote assistance and that will let me in so I can see the logs.
Thanks. Sorry about this. It’ll be fixed right away.
OK thanks, good to hear. I will try and find some time to call you this weekend.
I did discover that if you go back to the login page, refresh the page and make sure it is findvera.com and not findvera.com/login and then click on the ‘Setup My Home Network’ button, then you can log-in avoiding the ‘Host not Found’ error message.
I am still not able to loin remotely from my phone (I get the Host not Found and cannot seem to ‘refresh’ it to get the Setup button to appear). I haven’t tried it again from a ‘full’ browser.
Thanks to townsend and aaronox. It seems both issues have been identified.
The first issue with the site not loading happened when you edited data and clicked ‘save’ using the findvera service. We did our testing on an in-house remote access server, and the public is using our production one. One of the web settings (apache) was different, so on the production findvera service, when you hit ‘save’ it escaped some data. This has been fixed. We’ll have a new firmware out soon.
Aaronox had 2 issues. The first is that after you setup findvera, if you change your password, it loses the port setting needed to establish the connection to our server. I created this mantis and we’ll try to fix it today or tomorrow: http://bugs.micasaverde.com/view.php?id=194
Aaronox’s 2nd issue is that his ssh key in the directory: /etc/cmh-ra/keys got deleted. I think this was caused by the hardware reset of the box, but we’re still trying to track the cause.
We’ll have a new firmware upgrade within a couple days that fixes these issues.
The problem is that when you hit the ‘reset’ button it loses the key needed to contact findvera.com. There are 2 fixes: 1) don’t delete the key on a hardware reset, and 2) Make it so you have to hold down the reset button and don’t inadvertently press it. If you’re in a bad state and want to restore to the original factory default, do this:
Go to ‘advanced, download’ (or if the site doesn’t load click the firmware upgrade) and in the bottom, where it lets you put in a URL, enter this:
This is the same firmware you have already, so it’s just “upgrading” to what you’ve got. Alternative, you could edit the file /etc/cmh/version and change the 262 to something < 262, and then when you go to the download page it well tell you a new version is available.
Either way, when prompted, choose ‘restore to factory default’ (as opposed to preserve my settings).
Answered my own question, when you upgrade you have the option to keep the settings or to do a factory restore. I first tried to keep the settings just to see what would happen and of course it doesn’t work. Trying the full factory restore now. BTW I believe it took about 2.5 minutes to flash with the save settings. So far factory rest is going on 17 min.
Flash is at 40+ min so far. I killed it and then went back to findvera.com and clicked on the Setup button, and voila it works. I’m not sure if the upgrade was incomplete, or if there’s a bug where it won’t know? Also, oddly enough it kept the Z-Wave devices, but not the information that went along with them…
What is causing you to flash your device? Did you receive an early version, and just needing an update, or are you trying out all options to weed out any bugs?