OllisGit

Hi @cgcarter1 , unfortunately in you screenshot the mentioned error-line 16959 is not visible, so I have no idea whats going on there.

Hi @biancapascal. please provide more details: - octoprint.log - filament database (if you use file based db), located: ```OP/data/filamentmanager/filament.db```

Hi @gleep52, please check via browser developer tools, if the mentioned url is the same in ```

Hi @gleep52, the screencast-image shows a different url like mentioned in the first comment. If you open the url ```http://192.168.1.5:8999/mjpg/ddd``` in a browser tab the stream is visible, right? Also...

hmmm...running out of ideas. Please try to call your cam stream via curl with verbose command. It should look something like this and should at least include the status, content-type...

Hi @tophattwaffle, nice idea and I already started, but now I am blocked. It is not so easy to receice the spool selection event from the two plugins, so that...

Hi @nashuar, I think your mentioned changed is not a good approach, because this could raise a new error. The ? should prevent this. You already mentioned this. Also this...

@boinappi do you have an explanation about this "collision"? @boinappi , @asylumlife please attach the ```octoprint.log``` maybe I can find the error.

This feature is already tracked in the SpoolManager-Backlog (https://github.com/OllisGit/OctoPrint-SpoolManager/projects/1) ... unfortunately for you, this is tracked in the column "mid-term". So it will take a while to complete.

fyi: @wernight "scanning" spools is also already tracked: https://github.com/OllisGit/OctoPrint-SpoolManager/projects/1#card-27695769