Spool Manager/OctoDash Issue

As mentioned in another post I am currently making Test Builds before upgrading my Live 2023 install to Current.

Process was a follows.

Burnt a fresh Latest Build & Booted it in a Spare Pi.
Restored a Backup from my Operational Octoprint.

All loaded & appears to operate fine.

Installed OctoDash & Setup the API Key; all that seemed OK.

But the Spool Manager in OctoDash just gives me a Blank Screen when I get to the list of Filaments.
Spool Manager in Octoprint Shows all my previous data Just fine.

Have searched for a solution but nothing seems to offer a solution.

Edit:-

Just Upgraded it from 2.6.1 to 2.6.2 with No Change.
I can confirm that the API is working, as I can list the Files that were present in the Restored Data.

You have to backup spool manager thru the plugin, then restore that backup thru the plugin as well

Really hard to help you here, no logs attached :frowning:

I would recommend using a phone as secondary screen. For example: I use my Galaxy S9 with OctoApp and running kiosk mode, this works much better as i get proper screen darkening when i turn off the lights and its really nice because it works with many plugins. I then mounted a phone stand and a charging cable and i am loving it

That Doesn't Seem Relevant in my Case, as I did a Full Restore from My Live Pi on the Test Install Pi.

All My Spool Data is Present in the OctoPrint Web Interface of the Test Instance.
It's Just OctoDash that is not Displaying the Spools.
It Does Display the Files stored on the Instance though.

Yeah, Sorry. Original Post was in Haste & Away from My Desk.

octoprint-systeminfo-20251004073114.zip (1.0 MB)

Didn't Know about OctoApp when I setup My System 2 1/2 Years Ago.

A Portable Monitor would be Handy.
At Present I have a Couple of Print Monitors I Built back then.

GitHub - Qrome/printer-monitor: OctoPrint 3D Printer Monitor using Wemos D1 Mini ESP8266

I think that's what @5ft24 was trying to explain: To get your Spool data, you first have to make a backup of the spool data in spool manager of your old setup and then restore that spool data to your new setup.

Disagree,

As the Spool Data is already there completely in the Test Setup.

All That Happens if I Backup & Restore as suggested , is that the Usage Data gets updated on the New Setup to reflect usages since the Test Setup was built.

The Original Install of Octodash requires nothing like that as it is only using the Plug-in to retrieve the Data from OctoPrint.

Only Main Difference I see between my working setup of OctoDash 2.3.1 and the 2.6.2 on the Test Pi is that When you Touch the Filament Icon on the Test Pi, it first asks you for Tool0 or Tool1, then goes to the empty filament list.

On the Working Pi Touching the Icon takes you straight to the Filament List.

Edit:-

This is OctoPrint on the Test Pi. There are 12 Rolls Present...

But in OctoDash on the Test Pi...

Out of Interest,

Realised another variation on the Remote Monitoring.
I have VNC Viewer on My Phone & can Easily View the Touch Screen from there.

Also have a VPN Tunnel to My Office, So I can View it Remotely as well.

1 Like

I am not sure if octodash works with VNC viewer. Before, there was an android build of octodash, but unchartedbull killed that quite quickly (i believe due to issues).

Please respect my grammer, i am german

it 100% works over VNC, that's how I debug some of the OctoDash issues during development.