Yeah, that one got a lot of us when Ken made that 'improvement' to BI at one point. Just check it to be skipped/off whenever you set up a new cam. I have Omada too so I'm familiar with it.
Mike is there a reason why not having that box checked caused a problem in this case? I don’t have it checked at all and using Ubiquiti equipment I never had any issues like that. Is this something specific to TP-link equipment? I know Sonnie mentioned that these cameras weren’t on the Omada controller.
it has nothing to do with omada or tplink
not sure why you always try to find a network problem.
Like Mike says, its a blueiris problem. And if you search for it, you find people having the same problem without using any omada stuff.
In theory it should be a good feature because people use DHCP. Most consumer cams are dhcp by default.
So blueiris is able to follow the camera if the dhcp lease get revoked.
When did I say that? If I did, I miscommunicated... sorry. OR... maybe that was in another thread back when I did not have the camera connected to network and was pushing them straight to the PC second port, which I changed and now using a VPN and plan to create another VLAN as well. The controller sees the entire network. While I set the static IP in each camera, I also set it in the Omada controller as static.Mike is there a reason why not having that box checked caused a problem in this case? I don’t have it checked at all and using Ubiquiti equipment I never had any issues like that. Is this something specific to TP-link equipment? I know Sonnie mentioned that these cameras weren’t on the Omada controller.
When did I say that? If I did, I miscommunicated... sorry. OR... maybe that was in another thread back when I did not have the camera connected to network and was pushing them straight to the PC second port, which I changed and now using a VPN and plan to create another VLAN as well. The controller sees the entire network. While I set the static IP in each camera, I also set it in the Omada controller as static.