Every print I start, gets paused because there's something on the buildplate. But there isn't. I checked the workflow setting "Plate Clear Confirmation". because I thought it has something to do with it. I even tried the slider both ways, in case it has (accidental) reverse logic. Never had it before I switched to Bambuddy. The printer itself isn't complaining about anything, it's Bambuddy. But I do have to resume the print otherwise it stays paused.
What's going on?

Yeah, I saw on the page for Spoolbuddy that 2Gb is the minimum. I found another mini-PC in my collection that can manage the installation. So, it's all good. Maybe nice to put it on the Bambuddy pages as well.
Wonderful product by the way! It works like a charm. Thanks for sharing this!

This is a very interesting project, so I took my Raspberry Pi 3B (1Gb memory) and tried to install Bambuddy. But it keeps failing. I tried Debian 13 first, but that failed twice, so I tried Ubuntu (both burned with the Raspberry Pi image tool) but that fails too. So I'm stumped now. What can I do? Is the Pi3 not good enough? Do I really need one with more memory?

This is the error:

Run `npm audit` for details.
npm notice
npm notice New major version of npm available! 10.9.7 -> 11.13.0
npm notice Changelog: https://github.com/npm/cli/releases/tag/v11.13.0
npm notice To update run: npm install -g npm@11.13.0
npm notice

> frontend@0.0.0 build
> tsc -b && vite build


<--- Last few GCs --->

[4726:0xffffb8440000]   146637 ms: Scavenge 446.0 (458.9) -> 444.1 (458.9) MB, pooled: 0 MB, 3.19 / 0.00 ms  (average mu = 0.835, current mu = 0.860) allocation failure; 
[4726:0xffffb8440000]   146702 ms: Scavenge 446.0 (458.9) -> 444.1 (462.9) MB, pooled: 0 MB, 6.59 / 0.00 ms  (average mu = 0.835, current mu = 0.860) allocation failure; 


<--- JS stacktrace --->

FATAL ERROR: Reached heap limit Allocation failed - JavaScript heap out of memory
----- Native stack trace -----

 1: 0xe15218 node::OOMErrorHandler(char const*, v8::OOMDetails const&) [node]
 2: 0x11ab5cc v8::Utils::ReportOOMFailure(v8::internal::Isolate*, char const*, v8::OOMDetails const&) [node]
 3: 0x11ab77c v8::internal::V8::FatalProcessOutOfMemory(v8::internal::Isolate*, char const*, v8::OOMDetails const&) [node]
 4: 0x13d137c  [node]
 5: 0x13e92f0 v8::internal::Heap::CollectGarbage(v8::internal::AllocationSpace, v8::internal::GarbageCollectionReason, v8::GCCallbackFlags) [node]
 6: 0x13bfc78 v8::internal::HeapAllocator::AllocateRawWithLightRetrySlowPath(int, v8::internal::AllocationType, v8::internal::AllocationOrigin, v8::internal::AllocationAlignment) [node]
 7: 0x13c0ab0 v8::internal::HeapAllocator::AllocateRawWithRetryOrFailSlowPath(int, v8::internal::AllocationType, v8::internal::AllocationOrigin, v8::internal::AllocationAlignment) [node]
 8: 0x139b9b0 v8::internal::Factory::NewFillerObject(int, v8::internal::AllocationAlignment, v8::internal::AllocationType, v8::internal::AllocationOrigin) [node]
 9: 0x17b724c v8::internal::Runtime_AllocateInYoungGeneration(int, unsigned long*, v8::internal::Isolate*) [node]
10: 0x1cc8cd4  [node]
Aborted (core dumped)

I included a bit more, since it also complains about the npm version. I don't understand that, because I think the Bambuddy installer is the one that installed that. So maybe it should pick the @latest build.

Can anybody tell me what's wrong and how to fix this, if it can be fixed...