This is not technically a bug, I do think the behavior is non-ideal.
Working on a project with an ouster - in this case we’re using the ouster as a tool for the monitoring the movement of people in a space. As we’re not using the ouster’s feed directly, but using some network processing, we’ve run into a circumstance where our tracking solution stops updating when not looking at the portion of the network that contains the ouster TOP.
I think this is the expected behavior of TOPs - as you want them to stop cooking when not being viewed directly. In this case, however, I want that TOP to always be cooking. A proposed solution here would be to add a toggle to the Ouster TOP for continuous cooking.
I realize this is more of a RFE, so please feel free to move this to the other category after review.