Bug: https://github.com/maziggy/bambuddy/issues/1119

Okay, wiped everything with "docker system prune -a" and startet from scratch.

Doesn't work.

Get DB error messages on startup:
database.log.txt
Table spool only show the BL spool.
Table spool_assignment still empty.

Okay, than i will wipe it completely and start from scratch.
Hopefully is it the last time to do this...
Fingers crossed...

Thanks anyway!

On startup with postgresql this messages came up, but i don't think tis is relevant for the problem:

bambuddy-db  | 2026-04-24 14:02:18.762 UTC [37] ERROR:  syntax error at or near "AUTOINCREMENT" at character 112
bambuddy-db  | 2026-04-24 14:02:18.762 UTC [37] STATEMENT:  
bambuddy-db  |                  CREATE TABLE IF NOT EXISTS active_print_spoolman (
bambuddy-db  |                      id INTEGER PRIMARY KEY AUTOINCREMENT,
bambuddy-db  |                      printer_id INTEGER NOT NULL REFERENCES printers(id) ON DELETE CASCADE,
bambuddy-db  |                      archive_id INTEGER NOT NULL REFERENCES print_archives(id) ON DELETE CASCADE,
bambuddy-db  |                      filament_usage TEXT NOT NULL,
bambuddy-db  |                      ams_trays TEXT NOT NULL,
bambuddy-db  |                      slot_to_tray TEXT,
bambuddy-db  |                      layer_usage TEXT,
bambuddy-db  |                      filament_properties TEXT,
bambuddy-db  |                      UNIQUE(printer_id, archive_id)
bambuddy-db  |                  )
bambuddy-db  | 2026-04-24 14:02:18.803 UTC [37] ERROR:  syntax error at or near "AUTOINCREMENT" at character 110
bambuddy-db  | 2026-04-24 14:02:18.803 UTC [37] STATEMENT:  
bambuddy-db  |                  CREATE TABLE IF NOT EXISTS spool_usage_history (
bambuddy-db  |                      id INTEGER PRIMARY KEY AUTOINCREMENT,
bambuddy-db  |                      spool_id INTEGER NOT NULL REFERENCES spool(id) ON DELETE CASCADE,
bambuddy-db  |                      printer_id INTEGER REFERENCES printers(id) ON DELETE SET NULL,
bambuddy-db  |                      print_name VARCHAR(500),
bambuddy-db  |                      weight_used REAL NOT NULL DEFAULT 0,
bambuddy-db  |                      percent_used INTEGER NOT NULL DEFAULT 0,
bambuddy-db  |                      status VARCHAR(20) NOT NULL DEFAULT 'completed',
bambuddy-db  |                      created_at DATETIME NOT NULL DEFAULT CURRENT_TIMESTAMP
bambuddy-db  |                  )

This warnings came up every 15 minutes or so:

bambuddy     | 2026-04-24 16:04:29,965 WARNING [backend.app.api.routes.cloud] Failed to get cloud preset S7043929 (API ID: S7043929): Failed to get setting detail: 400
bambuddy     | 2026-04-24 16:04:30,190 WARNING [backend.app.api.routes.cloud] Failed to get cloud preset S7043928 (API ID: S7043928): Failed to get setting detail: 400
bambuddy     | 2026-04-24 16:04:30,396 INFO [backend.app.services.firmware_check] Got Bambu Lab build ID: skeiEP5Hs-sR8shWSQHlC
bambuddy     | 2026-04-24 16:04:30,444 INFO [backend.app.services.firmware_check] Got Bambu Lab build ID: skeiEP5Hs-sR8shWSQHlC
bambuddy     | 2026-04-24 16:04:30,446 WARNING [backend.app.api.routes.cloud] Failed to get cloud preset S8492713 (API ID: S8492713): Failed to get setting detail: 400
bambuddy     | 2026-04-24 16:04:30,621 WARNING [backend.app.api.routes.cloud] Failed to get cloud preset GFU99 (API ID: GFSU99): Failed to get setting detail: 400
bambuddy     | 2026-04-24 16:04:30,663 WARNING [backend.app.api.routes.cloud] Failed to get cloud preset S7043929 (API ID: S7043929): Failed to get setting detail: 400

In the meantime i lost all of my archived because of the back and forward sqlite and postgresql...

If nobody has a clue, I would start from scratch.

v0.2.3.2 - updatet this morning

Okay, than I don't know.
The tables spool and spool_assignment in the database are empty.

bambuddy=# select * from spool;
 id | material | subtype | color_name | rgba | brand | label_weight | core_weight | core_weight_catalog_id | weight_used | weight_locked | last_scale_weight | last_weighed_at | slicer_filament | slicer_filament_name | nozzle_temp_min | nozzle_temp_max | note | added_full | cost_per_kg | last_used | encode_time | tag_uid | tray_uuid | data_origin | tag_type | archived_at | created_at | updated_at 
----+----------+---------+------------+------+-------+--------------+-------------+------------------------+-------------+---------------+-------------------+-----------------+-----------------+----------------------+-----------------+-----------------+------+------------+-------------+-----------+-------------+---------+-----------+-------------+----------+-------------+------------+------------
(0 rows)

bambuddy=# select * from spool_assignment;
 id | spool_id | printer_id | ams_id | tray_id | fingerprint_color | fingerprint_type | created_at 
----+----------+------------+--------+---------+-------------------+------------------+------------
(0 rows)

Maybe I should wipe the hole installation because i installed bambuddy back in januar and updatet till now....

Hi!
Before I open a bug report, I have a question regarding the connection between Bambuddy and Spoolman.

I set up Bambuddy and Spoolman as Docker container. Testet Bambuddy with sqlite and postgres18 backend and both have the same problem.

I added non Bambu Lab Spools to Spoolman and connected these spools with the ams slot.
The slot is connected with a spool with spoolman.

I start a print and then a message came up with the information, that the spool isn't assigned and on the end of the print spoolman isn't updateing the new weight.

Is spoolman not updating the non Bambu Lab spools, or am I misunderstanding something?

Regards,
Marcus