unexpected behavior

[jorigel]

1st thanx for Ur work on this . . .
I'm using OctoPrint Version 1.3.12 and OctoPi Version 0.17.0, running on Raspberry Pi 4 Model B Rev 1.1 and of course Your add-on that saves a lot of ways from one floor to the other and back, (thank You for this, too ;-)

First:
In my surrounding the window to select the filament always opens with a preselected filament1 (it does not look like Your picture). I'm not able to decide if this is already a reason for my problem or just a visual dislocation.

Second:
If a different filament is chosen than the one last time used, the software does not switch to the new filament. It stays with the old one and uses it. For me it looks like as if there is a reset on the mmu missing before switching. If I do the choice direct on the printer this seems to be done by the printer before switching to the correct filament of my choice and then it works (the slay is going to the extreme right then dipping on the left a couple of times and then finally reaching for the location of the chosen filament). The software does not under these circumstances and the slay stays where it is using the same old filament as before.

Do You have any idea what is going on here?
'd be nice to hear from You . . .
regards

[Brebinator]

Hi there, to add to the above post, it seems like the ID of the LANE of the MMU Selector seems to screw up and then thinks that it is on LANE #1 (being the default lane for all single material jobs) where the user has decided to use a different MMU LANE for a Single material job, I found this out as I wanted to distribute the wear and tear overall lanes for longer life.