So I am back in this state. I noticed about 12 minutes ago Camect UI was unresponsive (spinning, no cameras). I power cycled and tried to “Report Bug” at the highest level as suggested previously in this thread. I could not:
When I submitted the above I got a transparent overlay message that said something like “Could not report bug, Camect is not connected yet”. I verified that Camect is actually running:
- I can ping the device
- The counter page displays and is updating
- It shows this for main page:
Clicking on the camect icon in top left, brings me to:
Which is exactly as I described.
Used third party app to confirm all four cameras are online and operational.
Tried both cloud and local connects with no success.
THen…. Restarted Safari and all is well.
So I am coming to the conclusion that there is some interaction between Safari and Camect that gets resolved on a Safari restart. Yet, I don’t think this is just about Safari. Last time I tried with Chrome as well and it also had the problem (after a fresh start). It seems that only the restart resolves the problem. I suspect it finally closes some (WebRTC?) connection that is somehow stuck on the Camect end (as well?).
What is also odd is the telegram message about just one camera coming online (out of 4), but inspecting its recorded video reveals no gaps (so was it really off-line?). Perhaps it makes these messages after a restart, but then I would have expected it for all 4 cameras.
Looking back at recorded video there seems to have been no interruption which also seems to confirm that Camect was not “dead” but just some UI problem.