Veralite spontaneously restarting over and over and over again every day?

For the last few weeks, I have been getting repeated notifications several times an hour in the Homewave app saying Vera has started or restarted. Sometimes back to back notifications.

I don’t know why the Veralite is restarting by itself or if these are false notifications from Homewave.

Has anyone seen this issue and is there a fix for it?

Need to look at the Vera Log file to find out the cause.
Often with a Vera Lite it’s a lack of memory.

The more you try to do with a Veralite, the more you’re likely to experience memory problems?

As well as the logs, (http://vera_IP/cgi-bin/cmh/log.sh?Device=LuaUPnP) if nothing stands out for you, look back at the last changes you made, it’s possible an app/plugin or scene recently added is not working as expected. Consider backtracking changes until, you reach a point of improved stability…

The Veralite is doing very little. There is only one device installed so far (a Schlage lock) plus the Homewave app.
Changes made recently were replacing the previous Yale lock with the Schlage lock. IP address on local network has also changed.
Besides the frequent rebooting, the other issue I have is that I cannot get the notification emails I had working with the Yale lock to work after the change to the new Schalge lock. I used to receive an emal notification each time the lock was unlocked.
This is what I see in the log:

08 07/01/15 6:01:55.032 JobHandler_LuaUPnP::HandleActionRequest argument IpAddress=10.9.7.106 <0x2dfa0680>
08 07/01/15 6:01:55.032 JobHandler_LuaUPnP::HandleActionRequest argument MacAddress=48:5a:b6:11:37:e3 <0x2dfa0680>
01 07/01/15 6:02:55.117 FileUtils::ReadURL 28/resp:0 user: pass: size 1 http://10.9.7.106/top.htm response: <0x2bba0680>
01 07/01/15 6:03:10.134 FileUtils::ReadURL 28/resp:0 user:admin pass: size 1 http://10.9.7.106/top.htm response: <0x2bba0680>
01 07/01/15 6:03:25.155 FileUtils::ReadURL 28/resp:0 user: pass: size 1 http://10.9.7.106/index.html response: <0x2bba0680>
01 07/01/15 6:03:40.171 FileUtils::ReadURL 28/resp:0 user:admin pass: size 1 http://10.9.7.106/index.html response: <0x2bba0680>
01 07/01/15 6:03:55.188 FileUtils::ReadURL 28/resp:0 user:dceadmin pass:dcepass size 1 http://10.9.7.106/index.html response: <0x2bba0680>
01 07/01/15 6:04:10.205 FileUtils::ReadURL 28/resp:0 user: pass: size 1 http://10.9.7.106/cgi-bin/CGIProxy.fcgi response: <0x2bba0680>
01 07/01/15 6:04:25.220 FileUtils::ReadURL 28/resp:0 user: pass: size 1 http://10.9.7.106/cgi-bin/get_status.cgi response: <0x2bba0680>
01 07/01/15 6:04:40.236 FileUtils::ReadURL 28/resp:0 user: pass: size 1 http://10.9.7.106/get_status.cgi response: <0x2bba0680>
01 07/01/15 6:04:55.354 FileUtils::ReadURL 28/resp:0 user: pass: size 1 http://10.9.7.106/get_status.cgi response: <0x2bba0680>
01 07/01/15 6:05:10.562 FileUtils::ReadURL 28/resp:0 user: pass: size 1 http://10.9.7.106/check_user.cgi?user=test&pwd=test response: <0x2bba0680>
01 07/01/15 6:05:25.665 FileUtils::ReadURL 28/resp:0 user: pass: size 1 http://10.9.7.106/CgiTagMenu?page=Top&Language=0 response: <0x2bba0680>
01 07/01/15 6:05:40.880 FileUtils::ReadURL 28/resp:0 user:admin pass: size 1 http://10.9.7.106/CgiTagMenu?page=Top&Language=0 response: <0x2bba0680>
01 07/01/15 6:05:55.900 FileUtils::ReadURL 28/resp:0 user:dceadmin pass:dcepass size 1 http://10.9.7.106/CgiTagMenu?page=Top&Language=0 response: <0x2bba0680>
01 07/01/15 6:06:10.917 FileUtils::ReadURL 28/resp:0 user: pass: size 1 http://10.9.7.106/stw-cgi/system.cgi?msubmenu=deviceinfo&action=view response: <0x2bba0680>
01 07/01/15 6:06:25.937 FileUtils::ReadURL 28/resp:0 user:admin pass:admin size 1 http://10.9.7.106/stw-cgi/system.cgi?msubmenu=deviceinfo&action=view response: <0x2bba0680>
01 07/01/15 6:06:50.124 UserData::WriteUserData saved–before move File Size: 7202 save size 7202 <0x2bba0680>
02 07/01/15 6:06:50.124 UserData::TempLogFileSystemFailure start 0 <0x2bba0680>
02 07/01/15 6:06:50.148 UserData::TempLogFileSystemFailure 4375 res:1
-rw-r–r-- 1 root root 33 May 23 17:04 /etc/cmh/HW_Key

Do you have a USB thumb drive installed ? It looks like you have verbose logs enabled … that can eat up your memory if you do not have the USB drive installed.

A call to MCV may get you going since you do not have much on your system.

I don’t have a USB drive connected. Since I have such a simple and basic setup with only one lock and Homewave, I wouldn’t think I would need any upgrading.
I am planning to later add a door sensor, thermostat, and maybe a couple lights and add some simple automation such as having the deadbolt lock automatically when the door is closed. However, since I am having problems with such a simple setup, I don’t want to add anything else or invest any more money into this until I can get it to work reliably.
If verbose logs are on and should not be, does anyone know how to turn this off?

Hi there,

I would strongly recommend to try and get in touch with Customer Care team.

Platform Status: status.getvera.com
USA Toll Free: talkdesk+18669662272
International: talkdesk+17024879770
Email: support@getvera.com
Web: support.getvera.com
Hours of Operation: Monday ? Friday 12:00am to 6:00pm Pacific Time

Unable to reach them. I assume they took the day off for the holiday, but failed to update their phone answering system, so I sat in an unattended phone queue after pressing 2 for technical support and wasted alot of time until it finally just disconnected.

As you only have a lock installed, I would seriously consider taking a back up of both Vera and the zwave network, and then doing a full system reset and just starting again.

Not ideal I know, but considering how little you have it could be worth it. And if you use the same IP and login credentials Homewave will likely be unaffected.

I think I will just want to just reset everything including Homewave and restart everything as a new set up and see if it works better.
If that solves everything, I will look at adding a door sensor that can be used to trigger locking the deadbolt and maybe add some other Z-Wave items such as thermostat and lights.

If similar problems continue, I am cutting my losses before investing in any more Z-Wave products and switching to HomeKit if that works as well as Apple products usually do. I can move this lock to another less used door so it isn’t a total waste of money and just use it manually without battling the Z-Wave glitches.

For products that have been on the market for as long as Z-Wave and Vera have, it doesn’t seem to be polished and user friendly enough.

[quote=“webuser”]I think I will just want to just reset everything including Homewave and restart everything as a new set up and see if it works better.
If that solves everything, I will look at adding a door sensor that can be used to trigger locking the deadbolt and maybe add some other Z-Wave items such as thermostat and lights.

If similar problems continue, I am cutting my losses before investing in any more Z-Wave products and switching to HomeKit if that works as well as Apple products usually do. I can move this lock to another less used door so it isn’t a total waste of money and just use it manually without battling the Z-Wave glitches.

For products that have been on the market for as long as Z-Wave and Vera have, it doesn’t seem to be polished and user friendly enough.[/quote]
Your problems are not Z-Wave problems, they are Vera problems. I cut my losses with Vera and moved to Homeseer 2 months ago, and while not perfect… wow what a difference…