I have a C8 that has been in service for around a year now. Everything has been working great until a few weeks ago when the device responses have become intermittent. Most of the time the response is about 30 to 45 seconds delayed to observe the action. I haven't made any changes in the devices in several months so I don't think it is a recent addition or deletion. I have done a z-wave radio reset, checked for ghosts and tried to isolate devices by removing power from parts of my house to see if that changes the outcome. In my logs, there is one item that is suspicious. Does anyone see a concern with this? The device is an Amcrest AD410 doorbell camera.
You didn't mention the controlled shutdown, unplug hub, wait 30 seconds, replug, tactic. Try that if you haven't.
Was the hub up and running for a long time, like maybe a month? Something like that.
The shutdown/power cycle could help.
If you suspect that device, maybe power it down. My doorbell is on its own breaker, so it's easy. Also, is that camera an actual Z-Wave device, or is there an integration or something involved?
And, the perennial favorite: any old Jasco switches?
If it was running along, fat dumb and happy, something changed.
Is that right after a reboot. It looks like allot of devices haven't talked into the hub yet.
The only thing I see obvious from that screen shot is the Aeotec Multisensor is using SO security. That should be avoid if it isn't a entry control device like your door locks. You may want to exclude that device and pair it back without security.
It would also be good to see this after the devices have had time to check in and see that they have connected.
That's not an ongoing problem I've ever noticed on my pair of C-7s. There have been infrequent problems with particular point releases, but nothing endemic to the platform.
As the platform changed so did the free memory available for me. There was a time when I had 6 weeks of up time and 350 meg free memory. I generally find now that I'm below 350 meg after 1 hour before it settles down. After that there's a slow drop and at a fortnight I'll be below 200. The only real change was the platform, my system hasn't changed significantly for a few years with regards to apps or devices (in fact I've recently removed a few apps across to a Pi in an attempt to have a bit more in the bank)
@ velvetfoot - The doorbell camera is an ip camera using the image server app to send photo's via pushover. Are the frequent NTPA adjustments slowing the system down?
As far as the restarts go. I wasn't really trying to suggest you change it, but that we understand why you were restarting it daily. In most cases it is probably not needed, that doesn't mean that you may have a use case that does.
Many people are very sensitive to the discussion of memory on their hub, They also think of memory like it is in windows were you want free memory. That is kind of different when you talk about Linux and Java(JVM). In many cases they will use memory and leave data in memory just in case instead of freeing it up. You also have processes like Java's JVM garbage collection that will free up memory based on certain criteria.
Either way your needs for reboots around memory consumption are likely unique to your environment so don't let anyone tell you when it should or shouldn't be a problem. Base it off of your own observations for your own setup.
My personal experience on my hub was I allowed it to get down around 120mb and then I would trigger a graceful reboot. That is much lower then many people mention, but it worked well for me
