That's not entirely true. It may be that it does not touch the underlying system, but it is not true that is has no way of doing so. We've done a lot of Python development, and run into this more often than we should. It usually has to do with a dependency of a dependency of a dependency, etc. that causes the problem.
OctoPrint, itself, is not causing this. But, the act of updating is. I am not seeing any dependency that is obviously the problem, either. (Haven't looked into RSA and itsdangerous, but I wouldn't suspect these first.) But, here's what I do know:
I restored a snapshot of my Pi taken back in April (1.4.0). Everything worked, as it did in April. I then did nothing but update to 1.4.2, and the ttyUSBn was no longer recognized. Rolled back to 1.4.0 and 1.4.1 to no effect.
Also, the failure to mount ttyUSBn isn't even an OctoPrint issue. The OS does not recognize the serial port, whether OctoPrint is running or even installed. It does, before upgrading, it doesn't after upgrading - confirmed twice.
I honestly don't think there is anything for the developer to do, here, but it is a reproducible issue that seems to affect some setups in a fairly consistent way. Since I am able to reproduce it, I'll look at it more, when I have time. Should be pretty easy, at this point, to see exactly what is different after the upgrade.
trying the octopi force reinstall now. I've got nothing to lose really. Didn't have any significant plugins installed. was just happy to print and monitor without running outside to the shop all the time. I'll update if i make any progress
Here's more info. When I first installed octoprint and octopi with my new printer I originally worked fine, then I installed a couple plugins and it broke. Giving me the "failed to autodetect serial port error" I can't remember how I fixed it but it involved some commands and it all was working fine for a couple months. Fast forward to today and it will no longer connect with nothing changed except the update.
So I rebooted my pi with my original sd card image from a couple months back and immediately got the failed to autodetect serial port error. Not sure what version it was but maybe 1.3.something.
I did nothing except update octoprint to 1.4.2. Now immediately after the update its this error again.
Maybe that helps, maybe it doesn't...maybe it will help somebody who stumbles across this down the road. ANyways I'll keep updating this thread if i get it fixed
I guess I worded that wrong, you're right - yes it could do, but OctoPrint's code does not try to. It could be a dependency of a dependency like you say, that creates this issue. Without digging into the dependency tree hell, I couldn't tell you!
I'm probably also partially blinded by the number of people who end up with 'my OctoPrint's broken' after they update because the install was corrupted. So many after the 1.4.1/2 update with corrupted installs, which the command above fixed it.
at least for me
~/oprint/bin/pip install --force-reinstall --no-cache-dir octoprint
fixed it!
i did also run ~/oprint/bin/pip --upgrade pip or what ever the pip upgrade command was because it was an old verison
edit never mind.. it started printing and then the print process was stopped because lost connection or something
I was experiencing the same issue after upgrading to 1.4.2
Connection just magically started working after changing USB port on RaspberryPi and resetting the Serial Port and Baudrate to AUTO.
I'm running a test print now.
Edit
Test print worked, but lost ability to connect to OctoPrint server via a web browser shortly after the print began. Test print finished successfully.
I had to restart the server in order to connect to OctoPrint server via a web browser, but was again experiencing connectivity issues with the 3D printer.
I reset the serial and baudrate to auto, shutoff the RaspberryPi, changed the USB port, and started server again. This again allowed OctoPrint server to successfully connect to 3D printer.
Throwing in my two cents, I'm also having the same problem.
I've had a part in my printer (Ender 3) broken for a while, so I haven't tried using octoprint for a couple of months. Now that I've fixed it, I'm getting the
Offline (Error: No more candidates to test, and no working port/baudrate combination detected.)
error.
I've tried: connecting to a different printer mainboard, using a different usb cable, using a different usb port, rolling back to an earlier version of octoprint, manually re flashing octoprint, using the force-reinstall command via ssh. Attached are my logs (main, and serial communication).
Any help would be super appreciated. I want so desperately to finally have my 3D printer back.
So that means octoprint is not aware of the serial port that your printer is connected on. This may mean it needs to be manually added in the additional serial ports option in order to be recognized. If you SSH to your pi and run the command dmesg | grep tty what is returned?
ok ttyAMA0 is the bluetooth chip if I'm not mistaken, so the pi doesn't see the printer at all. this could be a bad USB cable, bad power supply, or possible linux corruption. I'd try the manual reinstall just to see if that makes any difference.
Edit: there's been reports of electrical interference from motors and power cables too.
So I've tried manually reflashing a clean octopi to my raspberry pi's SD card, as well as doing the force-reinstall command. Is there another thing I should try reinstalling/another way to do it? Likewise, I run a small business that includes a mini usb cable with every order, so I've got tons of them lying around, and none seem to work, so that's the one thing I'm pretty confident it shouldn't be. For the power supply issue, the printer powers up and can be used via its monitor, and on the pi end I can connect to the webinterface, just not the printer. Could it still be the powersupply? Genuine question.
I'll try moving it seperate from everything else, but at the moment it's in its own area for from my computer, which is why octoprint is pretty important to me.
Also here's the dmesg | grep usb result.
Worth pointing out that it's connected to wifi via a usb adapter, and I've tried switching the usb cable to the port that the wifi adapter was on, and it still didn't work.
I meant the power supply to the pi, not the printer. If you're not using a true power supply and are using a phone charger wallwart, or ipad charger plug, etc. can cause weird issues.
Yeah, I don't think any of those USB options are relevant.
Sorry, I don't know why I assumed the details of my personal setup would be known to others. Both my printer and pi are powered by my printers PSU, in the case of the pi stepped down to 5vs via a buck converter. Maybe I accidentally hit the buck converters dial and it's not getting the proper voltage now? Could that be it? I can break out the multimeter tomorrow and find out.
I wouldn't naturally think that to be the issue assuming you weren't getting under voltage warnings prior to upgrade. The issue is definitely the pi not seeing the printer though for whatever reason.
