roflcoopter
Problems when upgrading from 3.0.0 to 3.1.1
Hello @roflcoopter,
I've upgraded my system from 3.0.0 to the latest image (3.1.1). Now I'm facing the following problems:
— The cameras show up, but there's now “Camera is off” written in the OSD for all of them. — All cameras also show the “not recording” icon — Timeline shows that continuous recording is indeed not happening anymore — Live view icon in each camera leads to page with a “Camera XX not found.” message — Events aren't working anymore — I'm also getting the error "Minified React error #185; visit https://reactjs.org/docs/error-decoder.html?invariant=185 for the full message or use the non-minified dev environment for full errors and additional helpful warnings." in several pages
I wasn't able to find anything useful in the logs.
Just pulled the image and it is working fine here. I would suggest stopping the container, removing the image, and then pull and create the container again and see if that clears it up
For what it is worth I upgraded from 3.0.0 to 3.1.1 (via docker compose pull) and it worked for me as well.
Just pulled the image and it is working fine here. I would suggest stopping the container, removing the image, and then pull and create the container again and see if that clears it up
No luck. Viseron is somehow thinking that the cameras are offline, when they are in fact online and showing up in the dashboard. Perhaps this erroneous state is preventing the system from doing its stuff (object detection, recording, etc.).
@roflcoopter Any hints on how I could debug this behavior?
The problem has something to do with codeprojectAi. When I changed the default model (ipcam-general) to ipcam-combined, cameras started to be recorded again.
Would be helpful if you could enable logging and then restart Viseron, hard to know whats going on otherwise. I also need to see your config.
logger:
default_level: debug
The problem has something to do with codeprojectAi. When I changed the default model (ipcam-general) to ipcam-combined, cameras started to be recorded again.
I noticed that when I switched to my own model in CodeProject.AI that it needs to be "kickstarted" with the new model. To do this I go into code CodeProject.AI Explorer and do a Custom Detect.
The behavior I get in the Viseron UI is different that what you are experiencing so this may be unrelated.