For those of you who have upgraded to 1.0.994, any problems? I’m at 1.0.988 and it seems quite stable but I just can’t resist an upgrade.
I upgraded to 994 last night, no problems. Vera now reports my schlage deadbolt as being locked/unlocked correctly and usually updates within seconds of it being unlocked/locked.
Keep in mind that I am just starting to use vera so your mileage may vary… currently only have a schlage deadbolt and a trane thermostat. But they are working fine and the box seems stable.
I went to 994 three days ago. So far, so good.
Working for me also 
-GT
So far, so good. And .994 finally allowed me to get rid of my phantom devices with the “Permanently Delete Dead Node” function, which was not working under .979.
** UPDATE: maybe spoke too soon. Nothing terribly disruptive, but I noticed that all of my device descriptions got truncated…for Scene Controllers only. I went in and corrected my device labels and the changes back to the full label were saved. So not sure why the truncation occurred, and definitely odd that this only occurred for Scene Controller devices. I’m also having some intermittent issues with light control when viewing my camera. According to my settings, Vera is still turning on the correct light when I view the camera, but does not seem to be turning the light off again when I hide the camera. Trouble ticket submitted - we’ll see what MCV says.
994 initially seemed good for me as well.
Unfortunately I found out yesterday, that some of my scenes stopped working.
Lately I found out, the cause was a hidden dns entry silently set up in the internal structure of vera, that caused problems with name resolving in my internal network.
I have already filed a complaint in the security section because I think hijacking the name resolution of vera is a serious security breach. But if you know how to telnet into your vera its easy to fix, once you know what is going on.
Umtauscher
P.S. If you are using SQ-Remote, you should go to 995, because 994 doesn’t work with their latest update.
opendns…
If you run into a problem trying to use the findvera or location page in the gui… you may have a problem with the way the box comes with dns set up in it.
put in a ticket, or look here for what I found.
http://forum.micasaverde.com/index.php?topic=3508.msg17015#msg17015
this problem is not in the vera ui code, but the openwrt distro
SQ suggested I update to MCV firmware .995 last night and everything works locally but Findvera is now not working anywhere with the browsers or SQ…is there anything I can do???
I didn’t understand where some are editing DNS entry and it seems to be a Server issue.
Please Help… or is it a server issue???
my problems were caused by the underlying openwrt distro in vera.
This problem is easily seen by doing a (setup), advanced, net & wifi, troubleshoot network
If you see === Testing DnsServer: 208.67.222.222 ===
show up before your preferred dns resolver… that MAY be your problem.
If you are linux savvy, ssh into the box, vi /etc/config/network
and delete the line containing 208.67.222.222.
If none of the above makes sense, I would put in a trouble ticket…
If you do, enable remote access and be sure to include the numbers
that show up when you enable it in the message to tech support.
It will save you one step and a lot of time.
Good Luck!
Thanks Les,
Ra2.findvera may be down?.??
I would like to know if anyone else is seeing this before I do any other adjustments…even if I understood your suggestion… ;D
Thank for trying to explain it to me though!
sball, same here. findvera.com itself comes up and allows password entry, then https://ra2.findvera.com hangs at login.php. It pings fine, but hangs on port 443.
Assuming that the people who live in the green house have server monitoring, we shouldn’t need a separate post to call attention to this.
FWIW, I emailed support earlier… haven’t heard anything back, I usually have a lot of patience with the firmware release etc… but having a main server offline all weekend is not cool to say the least.
I did read somewhere that they were planning/working on load balancing/redundancy, but that was future talk.