[Request] Show more detailed error for webcam load failures #5011
Labels
done
Done but not yet released
not technically possible
Issue is technically impossible to solve/implement
request
Feature request
Milestone
Is your feature request related to a problem? Please describe.
When a webcam fails to load, OctoPrint shows a message "Webcam stream not loaded". There are many causes of webcam streams not loading in the browser, but to users that are not technically inclined they see this as the error message, but don't understand what it means. This results in posts on the forums/discord server titled "Webcam stream not loaded", with very little supporting information, people jumping on other forum threads with "the same issue" when in fact it is completely different. There is no detail for users who want to troubleshoot themselves to start searching the forums with, so we also find people trying to solve their problem with a whole range of fixes (sometimes making things worse) because they can't tell which one is relevant to their problem.
In the case of CORS issues for example, the error message in the browser clearly explains that it is a CORS problem rather than something different.
Describe the solution you'd like
Provide more information about the reason the stream has failed to load. I would probably put this hidden behind a "more information" clickable thing to avoid cluttering up the screen with irrelevant error messages (maybe they've just unplugged their camera, and it normally works - and don't want to see red error popups for example).
Describe alternatives you've considered
Capturing the browser console as part of the systeminfo bundle. While this would contain the information that I'm after when people post on the forums, it doesn't allow people to troubleshoot/search for help themselves, as they are not likely to look in the systeminfo bundle if they weren't likely to look at the browser console.
Additional context
https://community.octoprint.org/search?q=webcam%20stream%20not%20loaded
The text was updated successfully, but these errors were encountered: