I am trying to reboot my controller, as it is currently not accessible, however, a power cycle doesn’t work because of the battery backup. How do I get back in?? I can’t SSH either…
Still no answers?
Looks like I have the same issue. Luckily I just started looking at UI7 today, so haven’t lost anything if I have to hit the reset button… I guess I could try pulling the battery.
But right now I may just return this VeraSecure. I know it has been 5 years since I started with UI5, but I know for sure if the initial setup were this bad I would not have stayed one day.
It can be rebooted without pulling the battery.
The solution was posted in another Vera Secure thread.
[url=http://forum.micasaverde.com/index.php/topic,49156.msg322276.html#msg322276]http://forum.micasaverde.com/index.php/topic,49156.msg322276.html#msg322276[/url]
From: https://support.getvera.com/customer/en/portal/articles/2934352-troubleshooting-your-verasecure
Power-cycle your VeraSecure:
[ol][li]Press and hold the reset button, on the side, for 30 seconds[/li]
[li]Release the reset button and unplug the power cord from VeraSecure[/li]
[li]The power light will blink for a few seconds and then the unit will turn off[/li]
[li]Reapply power to start the unit again[/li][/ol]
But that didn’t work for me this morning. I got up at 10am, and all home automation was down. My VeraSecure only had three LEDs lit, Power, Internet, and Wifi. Tried to connect via the local IP, no response. So I then tried the above official way to reboot, and nothing happened, the same lights stayed lit. So disconnected battery, and Vera rebooted and came back in service normally.
Based on the EventWatcher data pushed to my SysLog server I can tell it happened at 5:30am, but of course, the LuaUPnP log had rotated (default “Archive old logs on MiOS (recommended)” selected - if this happens again I will change it). The SnapLog logic to grab LuaUPnP data around the time of a crash did not pickup the event either…
Not sure if this will help you…
Press the reset button three times in six seconds. This will reset your network settings on the vera. This has worked for me in the past when a power cycle failed to bring the vera back to life.
Been there. Figured it out. Have to hold that button for 30 REAL seconds. So I count to 32 just for good measure. Then right after releasing the button, pull the power. Works every time for me.
There’s an easier way, if you are a little geeky and like to sit in front of your computer:
What you need ahead of time:
–The LAN IP address of your veraSecure (like 192.168.0.13)
–Your Vera’s wifi password (assuming it still the factory default)
what you do
–download a program called putty.
–Open putty, input the LAN ip address of the device
–at the login prompt, use “root”
–for the password use the wifi password
–type the following command: reboot
done.
The times that my VeraSecure has locked up - you can’t ssh into it. . .
The times that my VeraSecure has locked up - you can’t ssh into it. . .[/quote]
Exactly. I couldn’t PING it, so no SSH. This is the first time it has happened in 11 months of operation, but it gives me some concern…
I’m still waiting on my replacement . . . not sure if it is that I tried to push the limits (which, if true, is sad because I didn’t have THAT many devices) or the unit just died. Find myself rebooting it (via settings menu) at LEAST every other day or it will fail on its own and I have to manually reboot.