I finally had time to update my firmware to the latest version in my summer home. I was about 4 versions outdated. I am now experiencing what others have mentioned in other posts concerning non Internet connected time loss. Yes I have a good quality UPS but I still need to telnet into Vera sometimes twice a day because the time resets back to 1999. My neighbors must think I’m crazy with my lights going on and off at weird hours. I now have to unplug Vera since I can no longer trust it to keep the time clock running without reverting back to the default time. I even reset everything and started from scratch but that didn’t seem to make any difference. Has any coding changed that could cause this? Any other NON Internet connected users experiencing the same issues or have a solution?
JimMac, This may shed some light on the issue. I didn’t realize this problem was occurring with NON internet connected Veras. How are you setting the time when Vera boots up? Or do you just leave it at 1999? Vera doesn’t have a battery inside, so one each boot it needs to get the current time from a time server.
Hello MCV,
I’ve raised the very same issue a couple of weeks back ( http://forum.micasaverde.com/index.php?topic=1049.15 ).
It is still true with the latest build last week, that once Vera loses internet connection, EVEN when it is still powered by mains or UPS, the whole thing goes haywire. Jim is just experiencing the same problem.
(Additionally, Sunset/Sunrise still does not work properly, even with permanent internet connection)
Just thought, you might want to know.
When I arrive at my summer house Friday night I telnet into Vera and reset the time as it is always incorrect. Once I set it I will monitor it throughout the weekend. I usually have to reset it at least three times over the weekend. It always reverts back to year 1999 or 2000. I have a scene that should make coffee in the morning but it now makes it any time it chooses. I think there was talk about adding the time change option into the GUI, has this been dropped due to other priorities?
To answer your question “How are you setting the time when Vera boots up?”
I set my time by Telneting into Veras IP and using the command “date -s month-day-hh-mm-yyyy”, I always change the time when I notice it has reset or just after I power up Vera.
Still no luck in solving this issue. I unplugged Vera and brought it back home anticipating a quick fix. Should I open a ticket or is this being looked at?
I’ve spent about 3 hours trying to reproduce the issue that you’re reporting without success.
I didn’t managed to make ntpclient to revert the time to 1999 or 2000 date after I set it manually
with date.
In order to debug this I’ve added some debug info to ntpclient startup scripts. I’ve attached ntpclient-debug.tar file.
Connect to your Vera using telnet or ssh and run this commands:
cd /tmp
wget http://download.findvera.com/betafirmware/ftp/ntpclient-debug.tar
cd /
tar xvf ntpclient-debug.tar
date -s "071516302009" # date -s "month-day-hh-mm-yyyy" - set your current date and timeNOTE THE DATE AND TIME WHEN YOU’VE SET MANUALLY VERA’s DATE & TIME
When you notice that Vera’s date and time are set wrong to 1999 or 2000
login to Vera’s command line and run this
uptimethis will show for how long Vera it’s on.
Look at the time the you’ve note down and calculate according to the time that’s now, if this is almost the same as Vera uptime this means that somewhere it’s a problems and submit an trouble ticket.
If the time it’s different it means that Vera was rebooted and it lost the clock settings.
I will run this script this weekend. It will take more than 3 hours to reproduce this problem. Unplug the unit, disconnect the Internet, reboot, set the time and leave it for a day or two. If it is rebooting while plugged into a UPS then that may be another issue.
I will let you know the results.
I have noticed that Vera may be rebooting with certain firmwares.
Look at the logs. If they dont get higher than a couple hundred then it may be rebooting.
Just a thought
The logs dimension isn’t relevant to Vera’s uptime ( if you have verbose logging on, the logs will fill in a few minutes, the same if you’re adding/configuring a device etc ).
With the latest firmwares we’ve enable the reboot option in Vera’s watchdog. If the watchdog notice an error, an daemon that doesn’t run as it should be or something that could take to an unrecoverable crash it’s restarting Vera automatically to prevent it.
This watchdog it’s NetworkMonitor and has this two logs:
/tmp/log.StartNetworkMonitor
/tmp/log/cmh/NetworkMonitor.log
When you login, type the command: uptime
that will tell you how long it’s been since the last reboot. What’s possible is that one of the Watchdog’s is detecting a problem and rebooting, and since there’s no internet, the time isn’t getting set.
Just back from two weeks of holidays and I have the test results. Over the last two weeks Vera has locked up totally 4 times and rebooted 9 times. When it locks-up all LEDS are on but the web and telnet will not work.
The “uptime” command has verified that Vera is rebooting. I would assume that it would have rebooted more than 9 times as I was only able to check on it once every day or two.
Now we need to find out what is causing it to reboot or lock-up. Maybe this happen to every unit but only those who don’t have an Internet connection to fix the time clock notice the problem.
Have you contact MiCasaVerde support yet?
I will call MiCasaVerde if they don’t respond to this post.
Restarting older thread. I too lose internet connectivity (Vera running 1.0.985 used as router with access point - DSL modem is bridged) several times a day for approximately 60s at a time. I understand there is an “uptime” command that is input at login.
Not to be a dummy, but this is what I see @ login
A windows security window stating the server at 192.168.81.1 at HomeControl requires a username and password followed by input windows for user name and password. When inputting this info, it takes me to the downloads page under the advanced tab. I have searched for where to type “uptime”, but it really isn’t clear to me.
Can someone please clarify with more specific instructions than “enter uptime at login”. Also, is there some solution from MCV addressing this loss of internet?
I think you should update to 988. 985 has issues that causes reboot every few minutes.
Since I installed 988 my vera runs continuous again.
Umtauscher
‘uptime’ is a Unix command, which must be used at Vera’s console.
How to get there:
telnet (or ssh) to Vera’s IP address (see http://wiki.micasaverde.com/index.php/Advanced_Commands)
What about an “uptime plugin”? 
BTW, on the same page are instructions for manually upgrading Vera’s firmware!