"Max" number of devices on Vera2

Community Playground General Discussions
1

Hi,

I’ve got a Vera2 running UI4/1.1.1362 (downgraded from 1.5.x after hitting the initial wave of pretty severe V2/UI5 bugs which appear to have, more or less, been fixed now). Prior to the “upgrade” to UI5 my Vera 2/1.1.1362 was a stable, happy li’l lady.

After the downgrade she starts off "normal then gets progressively slower until I have to hard reset - i.e. a likely memory leak?, the Luup/Lua engine restarts up to once per hour - I have a start-up scene that e-mails me every time Luup/Lua restarts, and although she continues to respond to pings, it becomes impossible to SSH or use the web UI to access her at this point.

The only change I made after the downgrade was add another - note that I had one running already prior to the upgrade debacle - couple of Ping Sensor devices and now I’m wondering if the problem I’m having is because - according to @AP15E’s LSI v0.1 device - I have 65 devices and 75 scenes (several of which have multiple events/triggers associated with them).

What is the practical limit for the V2 in terms of managing devices & scenes? I though I’d read something along the lines of 75-80 devices?

2

You might want to remove some of the ping sensors and see if that corrects the problem. There has been talk that the ping sensor can cause vera 2 to have memory issues and slowness. Best to eliminate what you added after and see if that fixes the problem? If that does not work, try doing a restore of your last known good UI4 backup with out the additional additions.

  • Garrett
3

[quote=“sjolshagen, post:1, topic:170122”]Hi,

After the downgrade she starts off "normal then gets progressively slower until I have to hard reset - i.e. a likely memory leak?, the Luup/Lua engine restarts up to once per hour - I have a start-up scene that e-mails me every time Luup/Lua restarts, and although she continues to respond to pings, it becomes impossible to SSH or use the web UI to access her at this point.[/quote]

How did you setup the scene to monitor the restart?

4

In it’s most simple form, I used the luup.call_action() function in the Startup tab which launches a scene containing the luup/lua to send me an e-mail message via a local (home) SMTP server I’ve got running. Although, in truth, I have abstracted it a little more and have a “runScene()” (amongst others) function defined in the startup code and thus will always get run whenever the LUA engine restarts.

5

Quickies to add to Startup Lua.

To log to file:

local LOG_FILENAME = "/tmp/log/cmh/LuaUPnP_restart_history.txt" local logFileHandle = assert(io.open(LOG_FILENAME, "a+")) logFileHandle:write(os.date().."\n") logFileHandle:close()

To log to Prowl:

[code]local url = require(“socket.url”)
local apikey = “”
local event = “LuaUPnP Restart”
local description = os.date()

luup.inet.wget(“http://api.prowlapp.com/publicapi/add?apikey=“..apikey..”&application=Vera&event=“..url.escape(event)..”&description=“..url.escape(description)..”&priority=0”)[/code]

With thanks to @futzle for the [tt]url.escape[/tt] technique.

6

@oTi@, @sjolshagen and @futzle.

Thank you for the fine work.

7

[quote=“garrettwp, post:2, topic:170122”]You might want to remove some of the ping sensors and see if that corrects the problem. There has been talk that the ping sensor can cause vera 2 to have memory issues and slowness. Best to eliminate what you added after and see if that fixes the problem? If that does not work, try doing a restore of your last known good UI4 backup with out the additional additions.

  • Garrett[/quote]

So, I did remove all but one Ping sensor - the one is required so I can tell when my outdoor foscam freezes and can restart it again. However, the steady slow-down continued (now for a few weeks) and I finally, this morning, opened a support case with MCV. We’ll see what they say (and if they say “upgrade to UI5” or “you need a newer Vera” I may wind up getting irritated :wink: