What version is it running? Current is 2.2.9.146. I've got a C-5 that seems fine, and a C-7. Unfortunately, I only have 1 Zigbee device.
1 Like
Maybe @gopher.ny could look at this, with your permission of course.
Meanwhile, is there anything apparent in your App Stats or Device stats or logs?
I’m guessing with his memory that low right after a reboot, that there is a device spamming the hub so fast that it is pegging the CPU. May have to create a faraday cage (think briefly wrapping the hub in aluminum foil) to get a chance to look at the logs.
1 Like
I am on that version. Thanks for the reply.
Nothing in the logs or appdata for device data that indicated anyting. I couldn't even get into the logs until I rebooted. Did see some errands but was well past the system not responding. Thank you for replying.
Yes I rebooted the device seemed to respond better after a few minutes. Over 50mb worth of memory. I'm just not seeing what's indicating the memory leak. I do have a zigbee device that does do power reporting every I think 10 or 15 minutes. I can disable that. But something tells me it's more than just that.
A report every 10 minutes isn’t going to tax the hub. There’s generally a drop in freememory shortly after reboot as the hub finishes its start up load, but should settle down after that. I have noticed that a http calls seem to have a slight memory leak (Amazon is killing me here right now) so if you have any intergrations that do a lot you may want to look at them first. MakerAPI is also an interface that can be spammed and cause you issues if the integration using it develops a problem.
2 Likes
I have long suspected this has a memory leak. But I have no way to prove it other than stopping use of it made the hub not slow down. But that was a year if not longer ago, so I am not sure if that potential memory leak is still there.
If you or others suspect there is some problem with that or HTTP, I hope that people can get the support staff the information or logs to track it down.
Nothing I can prove, but my Dev hub makes minimal use of http calls and MakerAPI while still interfacing with Zwave and some Zigbee on occasion, and it’s memory drop is very low. Also noticed that http calls that errored out used to have a corresponding drop in free memory around the same time as the error (haven’t tracked it lately). Now granted, the Dev hub is usually less busy unless I’m playing around with new idea and generating some questionable instructions.
2 Likes
Can you PM me your hub's UID? I can take a look at the engineering logs on the hub through the support tool.
3 Likes
