02-03-2018 12:58 PM
04-22-2018 09:19 PM
Had the simular issues. The velop nodes would reset at what appeared to be random times. It wouldn't last 24 hours without resetting. Sometimes it would reset a few times in a row.
Got a Velop 3 node setup and all was well until I added Nest cameras to the mix. Spent a week trying various solutions to this. Even put the Nest camera back on my old router (in bridge mode), which seemed to keep the velop resets down. Still would happen, but not as much. Anyway, fast foward, I was looking at the velop configuration from the sysinfo.cgi page and it occurred to me that the "Device Prioritization", also known as QoS, is the cause. Prior to putting the Nest Cameras on the Velop net I had turned on and a few devices set for it, and it only allows a max of three devices for that list (via the ios app anyway).
So, I turned off QoS device prioritization ... and low and behold no more velop crashes and all devices including the nest cameras are working great.
My theory is that the master Velop node does not have the horse power to run QoS with the demain that devices like Nest cameras have. Even just one Nest camera would cause the Velop system to crash if QoS is enabled.
I do not have any special ports enabled on the Velop system. The only thing custom I left is the seperation of 2.4G
hz and 5GHz networks.