I got my Vera2 this weekend and tried both UI3 and UI2 and am currently on 988 so I can use Home Buddy. All my devices and scenes are working well except I cannot get Findvera working (on both UI2 and UI3). I opened a ticket, but I figure I would post here to see if anyone has run into that same issue before. And yes, I did clear my browser cache already.
When I go to findvera.com on my lan, it shows this, but says Vera is not found on Home Network. I can get to Vera by manually going to the IP address. Also, this IP address is an outdated address, I ended up assigning a static IP to Vera. It is almost like this old IP is cached somewhere in Vera.
[b]You are connected to your home network. Click the button below to connect directly to Vera while at home. Normally no password is required.
#1xxxx, IP address 10.1.2.11[/b]
When I got into Vera and go to the Findvera tab, I get this error message:
FindVera remote server not assigned.
I also get an error when I go to Troubleshoot Networking:
Personally I would still revert to .979 as it has been known to work good for many months now and it seems like they keep messing up ever since they tried to add the square connect functionality. Plus they messed with some other things that make it worse. It works with Home Buddy too.
Do you know if it works with the Vera2 hardware? I don’t see why it wouldn’t, but you never know.
Edit: 979 does not work with the Vera2. Most of the lights stay lit with the power light staying amber on the hardware. I can get into it, but it says z-wave does not work.
Was anyone else able to load 979 on their Vera2?
Looks like I am back to square one, I also had to redo all my scenes even though I did manual backup and restore.
and so-on, as nodes are “expanded” out as the # of attached Vera’s increases. Some users get allocated to each, and our Vera’s “Tunnel” to one of these nodes (to get through the Firewall, since it’s initiated within each of our Networks)
I always thought that this [RAx.FINDVERA.COM] provisioning process occurred when you “established” your FindVera.com account via the UI (but I could be really wrong here)
Whilst we all initially login to www.findvera.com, we eventually get “sent” (browser-redirected) to the RAx server that’s associated with our Vera/FindVera account in order to “control” it.
I’m reading somewhat behind the lines based upon what my Vera is doing, and what it’s connecting to, so I could be way off base with the above description.
I’m wondering if this “association” (to a particular named Vera RAx.FINDVERA.COM) server hasn’t been setup correctly in your UI3. If that’s the case, then it really has to be fixed by the MCV Support team.
Lots of “guessing” here but I wouldn’t be surprised based upon what you’ve listed above.
I was contacted by tech support this morning, however, I was not able to enable the tech support back door which probably has to do with the problems I am having. I let them know and will wait to see what they say.
Yes, support contacted me today and said there were some DNS issues that should now be fixed. However, it seems that my issue is more complicated. They are still looking into it.
Edit: Here is what support said so far, I wonder how that happened.
This is very weird. The nvram (non volatile flash ram) on your box
got wiped out. This is the ‘permanent’ memory that stores your serial
number and other provision data. This should never happen.
I can see that your box was ok on this date: 2010-02-19 23:33:46 and
reported version: 1.0.987. It couldn’t have reported the version if
it didn’t have the serial number, so for sure on the 19th it was
there.
Do you know when it stopped working? Was it when you upgraded to 988?
How did you upgrade to 988? Did you use the normal web interface
(Advanced, Download)? And did you choose the ‘restore to factory
default’ option? Or did you do the ‘preserve settings’ and get stuck?
Did you ever try to do a factory reset of the box by hitting the
reset button? Did you ever hold down any buttons while powering it
on? We’re going to try to find the exact sequence that caused this
happen and reproduce it so we can figure out how to work around it.
Is this issue solved, I am stuck in the same screen. In my case my vera got in a somewhat screwed state after a power failure. If i manually restore settings through ssh I seem to get things up and running again. But this seems to be until the next power down sequence. Then also dhcp seems to fail. I lived up with this fact for two times (manually restoring settings), but two days ago vera rebooted again. And it’s getting very frustrating playing sysadm. Today i tried reflashing but that does not help, also my SSID is not my ‘own’. So most problably my non volatile memory got partially fubared.
Support has not responded to my requests.
So can you please indicate how you solved this issue.
I can get it back up again, but this is not persistant…
I’ve placed a support call through the webform (again) I really hope MCV reacts. Does anybody else has troubles filling in that form using chrome (my security form seems not to be accepted, in ie it works)
After a long debugging session it appeared that my verion did not got provisioned correctly. Vera reads part of the etc from non volatile or from a server. In my case it kept on trying to read locally, whilst my vera should have retrieved from the remote location.
It is sort of resolved i hope since i manually started the proviosing script, i should try to reboot if afterwards my vera is still in correct state. But i dont dare to that yet, it wS very late yesterday night. And i dont have micasVerde tech support to fall back on.
I also have a manually modified script by mv, which i dont know if it has to be reverted.
So if you ever have a vera with this exception find out if the provisioning works…
Best Home Automation shopping experience. Shop at Ezlo!