So I got the vera2. I’m so confused. Plugged it into the network and went to micasaverde.com/vera2
It found the device and had me go through a couple updates. I am on version 1.1.1008.
I’m attempting to do anything with z-wave without much luck. First of all, I have a red cog in the corner that says ZWave: No ZWave dongle. Is that normal? The zwave light is on the front of the unit.
Attempting to use the Wizard, I select to add ZWave devices, choose option 1, and then go to a please wait screen that hangs indefinitely.
Any documentation I find doesn’t match my UI at all. I have blue screens, and have found all sorts of “other” screens.
Can anyone help me to figure out how to add my first z-wave device?
Ok, troubleshooting the wizard makes it clear it’s problem is related to the zwave not being ready. Here’s the soap response error I see in the browser
Double check and make sure you are using the right power adapter. There are two in the box, one for the battery and one for the router. I got them reversed when I first unpacked everything and when I hooked it up I had a similar issue with things not powering up all the way and not getting a Z-wave light.
If that doesn’t do it, it sounds like something is wrong with your Vera2 unit. On the Vera2 the Z-wave dongle is internal. If your Z-wave light is not coming on, I’d bet your having a hardware problem. I’d contact MCV and open a ticket with them. They might have a quick fix.
Yep, made sure I had the right one (12V/1A) before ever plugging it in.
If that doesn't do it, it sounds like something is wrong with your Vera2 unit. On the Vera2 the Z-wave dongle is internal. If your Z-wave light is not coming on, I'd bet your having a hardware problem. I'd contact MCV and open a ticket with them. They might have a quick fix.
The Z-wave light is on, but clearly there is something wrong recognizing it. I hope MCV can resolve, will call their support if unresolved.
Oops, sorry, mis-read your original post. Yeah, it sounds like it might be a hardware issue, however MCV might have some software fix. If I were desperate to get it working, I’d try downgrading to the old UI2 latest firmware while wiping settings. Firmware changes are always dangerous though, and you being on 1.1.1008, I believe your actually on the beta release of UI4. I really don’t know how that would react.
I got my Vera2 a couple of weeks ago and set it up without any problems.
During the setup, did it direct you to that site for updates?
I’m asking because mine did not do that…considering you basically updated to a beta.
[quote=“mario23, post:8, topic:166203”]I got my Vera2 a couple of weeks ago and set it up without any problems.
During the setup, did it direct you to that site for updates?
I’m asking because mine did not do that…considering you basically updated to a beta.[/quote]
Someone had posted in the UI4 forums that new units were shipping with instructions to go to that site instead of findvera.com which is updating the units to the UI4 beta.
This sounds just like what happened to me when I first started configuring my Vera2. I would get the red cog and it would say “No Z-Wave dongle”. I could not communicate with any of my shiny new toys. I was in the process of composing my support request while still troubleshooting and searching the forums for ANYTHING. I restarted, pressed all of the buttons on the back, updated the firmware and finally restored to factory defaults. As soon as I reverted to factory defaults it came back to life.
I’m as anxious as the next guy to get UI4 but had decided to stay conservative on the updates with all of the issues I had read about UI3. I would have to suggest going back to UI2 and restoring factory defaults. It was a painless process for me back then because all I had configured was my findvera.com username and naming all of my rooms.
I bought mine from Amazon [smart home usa] and it came with a piece of paper that instructed to go to that website.
I have attempted to revert to anything prior but so far it has just reset settings without going to a non UI4 release. I’ll keep trying… I just want basic, basic functionality to work at this point.
FYI, MCV was able to quickly diagnose and resolve the issue. Here was their explanation about what went wrong:
“The ZWave chip just needed a reflash for some reason. I’ve seen it happen a few times. I just added code to our engine to reflash the ZWave chip if it gets stuck again, so you don’t have to do anything.”