Octoprint: Server not autoconnecting on startup if port is set to AUTO

[ismangil]

What were you doing?

Ticked auto-connect on server startup

What did you expect to happen?

Server will connect to printer when server starts or restarted

What happened instead?

Server did not try to connect on startup

Did the same happen when running OctoPrint in safe mode?

Yes.

Version of OctoPrint

1.3.6

Operating System running OctoPrint

OctoPi 0.14.0

Printer model & used firmware incl. version

Marlin 1.1.4 GitHub

Browser and Version of Browser, Operating System running Browser

Any browser

Link to octoprint.log

https://gist.github.com/ismangil/6cf1e38e832b5d314f7961b371e7c166

Link to contents of terminal tab or serial.log

Link to contents of Javascript console in the browser

Screenshot(s)/video(s) showing the problem:

I have read the FAQ.

[4325123]

Just saying I have the same issue too. I'm wondering if it has something to do with octoprint starting before the printer is being detected.

[kantlivelong]

@ismangil can you provide fresh logs for both octoprint.log and serial.log with the issue occurring?

[ismangil]

@kantlivelong Here it is: https://gist.github.com/ismangil/cc99d24ee982a04a2aba946609bf2cdf

Note the serial.log is only generated once I manually click Connect, because the server is not auto-connecting.

[kantlivelong]

Yeah not much of use there as far as I can tell. If you login to SSH and run cat /var/log/syslog | grep kernel | grep -A5 -B5 "tty" you should see when the serial device was detected by the kernel. Does it show up before OctoPrint starts?

[ismangil]

@kantlivelong you may have something there. If I I'm looking at the log correctly, OctoPrint may be starting up before /dev/ttyUSB0 become available. I suppose in this case it's an OctoPi configuration issue on how to wait a bit or detect ttyUSB0.

[kantlivelong]

The PortLister plugin should work as a workaround. I personally use it as it also will reconnect after resetting the printer controller.

[ismangil]

@kantlivelong however, that doesn't explain why it doesn't auto connect on server restart (not a reboot) doesn't it? The port is already there, yet OctoPrint is still not autoconnecting.

[kantlivelong]

Hmm...

What's the make and model of printer/controller are you using?

[ismangil]

MKS GEN L 1.0

[ismangil]

I've found the cause: If port is left on AUTO then

if port in connectionOptions["ports"]:

fails, because AUTO is not on the list of ports.

Yet when I click connect, it's able to connect. So the solution seems the autoconnect logic needs to follow the manual button logic.

For my current use, if I specify the specific port, then it can autoconnect just fine.

I've updated the issue title.

[kantlivelong]

Well that's interesting... I've confirmed your findings here as well.

[kantlivelong]

Hi @ismangi,

I've submitted a PR that fixes this.

[jneilliii]

Does this also effect the Virtual Printer port? I can never seem to get that one to autoconnect when testing my plugins.

[kantlivelong]

@jneilliii only if you had the serial port set to AUTO.

[jneilliii]

I just tested against 1.3.7rc4 and the behavior is still the same for me with VIRTUAL serial port, and the option selected as AUTO. This is the output in the terminal.

Changing monitoring state from "Offline" to "Detecting serial port"
Serial port list: ['VIRTUAL']
Connecting to: VIRTUAL
Changing monitoring state from "Detecting serial port" to "Error: Connection error, see Terminal tab"
Unexpected error while connecting to serial port: AUTO OSError: '[Errno 2] No such file or directory: 'VIRTUAL'' @ comm.py:_openSerial:2304 (hook default)

[foosel]

VIRTUAL doesn't and has never supported auto detection, so this is expected behaviour.

[foosel]

Closing as 1.3.7 was just released.

[nickm324]

This issue still exists in 1.3.10.

[foosel]

@nickm324 then please fill out the ticket template so this can be looked into

[Edo78]

I'm experiencing the very same issue, even in safe mode. I'm on OctoPrint 1.3.10 running on OctoPi 0.15.1

It's not a big deal since I set the right value and now I'm autoconnecting but it's stilla bug ... do you want me to create a new issue for this bug?

[seltix5]

Hello,
I have the same problem. Is there already a new issue created for this bug sinse this one is closed?

I have OctoPrint 1.3.11 running on OctoPi 0.16.0

[foosel]

Please open a new ticket.

[seltix5]

new issue created https://github.com/foosel/OctoPrint/issues/3267