Simple guide to scheduled reboot and reboot from phone app

[rigpapa]

You can also ssh to the box and do: [tt]cat /proc/meminfo[/tt]

You can pull this in with Lua like this:

p = io.popen("cat /proc/meminfo") lines = p:read("*a") p:close()

I’ll leave parsing it as an exercise for the reader.

[HSD99]

If you did a log dump, you may have noticed that Vera’s logs are not easy to understand. They are there as a primarily as a developer debug tool. There are lots of things in the log that look scary, but are really normal occurrences. ALTUI’s own tools may actually help more than the Vera logging. There is an active ALTUI forum here, the the developer, amg0, is very active on the forum.

[kwieto]

@rigpapa

That would flush a bunch of caches that are volatile, so they’re being flushed by the reboot anyway. Flushing them may have some use if you’re not rebooting, maybe reducing memory use temporarily, but these are well-managed caches and unless you’re really strapped for RAM for some immediate purpose, flushing them is more likely to create a momentary negative impact on system performance.

I found that both my controllers have tendency to increase cached/used memory from time to time for no apparent reason (same setup, no changes in devices, scenes or plugins).
When I asked Customer Care, they adviced the code for flushing the case.
In fact they advised to run it about every 30 minutes, I modified it in a way that if amount of free memory drops below certain level vera clears the cache; if this doesn’t help, then reboot is executed.

I don’t have strong opinion here, but in general I consider flushing cache potentially less harmful than a reboot, this is why I made two step setup.