Loek  Freshman Member

That did the trick. The list is populating again. Thanks @Zyxel_James

@Zyxel_James There is no other router in play here, only some (managed) switches, everything on the same subnet.. The list was displaying fine until I remove all entries a while ago in an attemp to cleanup incorrect identifications. The results of the above commands on CLI: Router# show device info all Router# debug system…

Yeah, I had tried that too, but the list remains empty. Here are screen shots: I will give it another 24 hours, but I'm not hopeful. I'm running firmware V5.37(ABAQ.0)

@kunz You said (quote): "I did try the, “delete the devices”, and then did the re-detect of of the said devices after several days." How did you "re-detect"? Is there a way to force re-detection of devices after deleting them? I have deleted all entries in my Device Insight list, but after weeks (including two reboots),…

If you do the above, is that permanent or will the list populate again after enabling Device Insight again?

Issue is resolved. Apparently the problem was caused by Nest camera(s). They report an incorrect IP address after power outage. Doing a hard reset of the network on the camera device itself resolved the issue.

Well, that's a good thing! Faster is always better.

Since clearing cache did not work, I reinstalled Firefox browser and the p2led error went away. I am wondering though why the LAN leds are orange now instead of green as they were before the move. I could not find anything in the documentation.

After moving to another state, I now have the same error. Tried on different browsers, clearing cache etc. The physical panel shows orange LEDs for P2 (WAN) and P2, P3 (LAN). Any other suggestions to fix this? The virtual panel shows only green for Pwr and Sys.