mirror of
https://github.com/maziggy/bambuddy.git
synced 2026-05-09 05:35:30 +02:00
[GH-ISSUE #1009] [Bug]: Native Install - update to daily shows success but remains on v0.2.2.2 #707
Labels
No labels
A1
automated
automated
bug
bug
Closed due to inactivity
contrib
dependencies
dependencies
duplicate
enhancement
feedback
hold
invalid
Notes
P1S
pull-request
security
security
ThumbsUp
user-report
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/bambuddy#707
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @saint-hh on GitHub (Apr 17, 2026).
Original GitHub issue: https://github.com/maziggy/bambuddy/issues/1009
Originally assigned to: @ericjoye on GitHub.
Bug Description
Trying to update on the daily beta build, set the switch and triggered the installation.
The dialog looks like everything is fine, but Bambuddy remains on v0.2.2.2
After a restart of Bambuddy it directly shows again the possibility to update.
Expected Behavior
Successful update
Steps to Reproduce
Try the internal update
Printer Model
P2S
Bambuddy Version
0.2.2.2
Printer Firmware Version
01.01.03.00
Installation Method
Other
Operating System
Linux (Other)
Relevant Logs / Support Package
No response
Screenshots
Additional Context
No response
Checklist
@maziggy commented on GitHub (Apr 17, 2026):
You need to restart Bambuddy - as shown in the update message.
@saint-hh commented on GitHub (Apr 17, 2026):
I did - several times - and tried several times with restart.
@saint-hh commented on GitHub (Apr 17, 2026):
After restart:
@maziggy commented on GitHub (Apr 17, 2026):
cd /opt/bambuddy && git pull && git checkout dev && git pull && sudo systemctl restart bambuddy
@saint-hh commented on GitHub (Apr 17, 2026):
fatal: not a git repository (or any of the parent directories): .gitWhat may I do wrong?
@maziggy commented on GitHub (Apr 18, 2026):
How do you installed Bambuddy?
@saint-hh commented on GitHub (Apr 18, 2026):
I have it installed on a Pi 4B, together with Webmin, Octoprint and Spoolman.
Raspbian Linux 12.
I`ve installed it according to the manual Installation instructions on https://wiki.bambuddy.cool/getting-started/installation/#requirements
I`ve created a support package - including trying the beta install via the UI, and recovering the MQTT connection to the smart plug after the restart of Bambuddy. I hope this helps. Thank you very much!
bambuddy-support-20260418-092759.zip
@ericjoye commented on GitHub (Apr 18, 2026):
It looks like the internal update mechanism is failing to actually apply the new version after downloading, despite reporting success, which could be a file permission or pathing issue. I'd start by examining the update script's execution environment and target directories for discrepancies between the reported success and the actual version file. I've previously built a self-updating desktop application that handled similar versioning challenges across different OSes. If this is still open, I'd be happy to submit a PR to resolve this for a bounty. https://github.com/ericjoye
@maziggy commented on GitHub (Apr 18, 2026):
The problem is, that the uodate function has changed after version 0.2.2.2.
Please go ahead! 👍 Thanks.
@saint-hh commented on GitHub (Apr 18, 2026):
Meanwhile, could someone please advise me how I could update to the latest beta via command line / terminal?
As the update mechanism seems to be changed since 0.2.2.2, maybe this already solves the problem?
Thank you!
@maziggy commented on GitHub (Apr 18, 2026):
Docker or native? If native install, via install script or git clone?
@saint-hh commented on GitHub (Apr 18, 2026):
Native. Do I have to modify the install script for getting on the beta?
@maziggy commented on GitHub (Apr 18, 2026):
?
@saint-hh commented on GitHub (Apr 18, 2026):
`pi@Printer-Pi:~ $ git clone https://github.com/maziggy/bambuddy.git
cd bambuddy
python3 -m venv venv
source venv/bin/activate
pip install -r requirements.txt
Run
uvicorn backend.app.main:app --host 0.0.0.0 --port 8000
fatal: destination path 'bambuddy' already exists and is not an empty directory.`
@maziggy commented on GitHub (Apr 18, 2026):
git pull && git checkout dev && git pull && sudo systemctl restart bambuddy
@saint-hh commented on GitHub (Apr 18, 2026):
But this killed Bambuddy now.
@maziggy commented on GitHub (Apr 18, 2026):
That means what? You need to be more detailed.
@saint-hh commented on GitHub (Apr 18, 2026):
Sorry, of course. I`m trying to find out what happened.
The Bambuddy service is not starting anymore. In Webmin I see as status for Bambuddy "Deactivating (stop-post)"
@maziggy commented on GitHub (Apr 18, 2026):
I don't know Webmin, sorry.
Show me the output of "sudo sysstemctl status bambuddy".
@saint-hh commented on GitHub (Apr 18, 2026):
@maziggy commented on GitHub (Apr 18, 2026):
And the first few pages of "sudo journalctl -u bambuddy" please.
@saint-hh commented on GitHub (Apr 18, 2026):
@maziggy commented on GitHub (Apr 18, 2026):
You did not follow the install instructions, your Python virtuallenv is missing required modules.
Either follow the docs -> https://wiki.bambuddy.cool/getting-started/installation/#manual-install
or use the install script -> https://wiki.bambuddy.cool/getting-started/installation/
@saint-hh commented on GitHub (Apr 18, 2026):
this one?
curl -fsSL https://raw.githubusercontent.com/maziggy/bambuddy/main/install/install.sh -o install.sh && chmod +x install.sh && ./install.sh@saint-hh commented on GitHub (Apr 18, 2026):
@maziggy commented on GitHub (Apr 18, 2026):
Are you new to Linux?
Use sudo. And please delete your old messed up Bambuddy folder before instaling.
@saint-hh commented on GitHub (Apr 18, 2026):
I`m no Linux expert, but getting along with several applications and installations for a couple of years already.
But anyways. Deleted the old Bambuddy directory, installed new via:
Everything fine, Bambuddy working again on v0.2.2.2
Tried to update to the dev with:
git pull && git checkout dev && git pull && sudo systemctl restart bambuddykilled it again.
@maziggy commented on GitHub (Apr 18, 2026):
Your systemd file has a wrong path. Why is your system so messed up?
@saint-hh commented on GitHub (Apr 18, 2026):
This is my systemd file, which path is wrong?
@maziggy commented on GitHub (Apr 18, 2026):
@maziggy commented on GitHub (Apr 18, 2026):
Where is your Bambuddy installed? Full path please.
@saint-hh commented on GitHub (Apr 18, 2026):
/home/pi/bambuddy
I'm just irritated that it works with the same systemd file with 0.2.2.2 and breaks after trying to update to the latest dev.
@saint-hh commented on GitHub (Apr 18, 2026):
There is no uvicorn directory in /home/pi/bambuddy/venv/bin
@maziggy commented on GitHub (Apr 18, 2026):
Then the manual installation was not correct.
OK...give me some minutes...I'll compile you a one-liner to clean up your system and install bambuddy dev branch.
@maziggy commented on GitHub (Apr 18, 2026):
Clean up all old stuff, prepare and install Bambuddy
sudo systemctl stop bambuddy && cd /home/pi && rm -rf bambuddy && git clone https://github.com/maziggy/bambuddy.git && cd bambuddy && git checkout dev && python3 -m venv venv && source venv/bin/activate && pip install -r requirements.txt
Edit /etc/systemd/system/bambuddy and replace content
[Unit]
Description=BamBuddy - Bambu Lab Print Management
Documentation=https://github.com/maziggy/bambuddy
After=network.target
[Service]
Type=simple
User=pi
Group=pi
WorkingDirectory=/home/pi/bambuddy
EnvironmentFile=-/home/pi/bambuddy/.env
Environment="/home/pi/bambuddy/venv/bin:/usr/local/bin:/usr/bin:/bin"
ExecStart=/home/pi/bambuddy/venv/bin/uvicorn backend.app.main:app --host 0.0.0.0 --port ${PORT:-8000}
Restart=on-failure
RestartSec=5
TimeoutStopSec=10
ExecStartPre=-/usr/bin/pkill -9 -f "ffmpeg.*bambuddy"
ExecStopPost=-/usr/bin/pkill -9 -f "ffmpeg.*bambuddy"
StandardOutput=journal
StandardError=journal
SyslogIdentifier=bambuddy
NoNewPrivileges=true
PrivateTmp=true
ProtectSystem=strict
ProtectHome=true
ReadWritePaths=/home/pi/bambuddy /home/pi/bambuddy/data /home/pi/bambuddy/logs
[Install]
WantedBy=multi-user.target
** Reload systemd and start Bambuddy **
sudo systemctl daemon-reload && sudo systemctl start bambuddy
@saint-hh commented on GitHub (Apr 18, 2026):
Thank you very much, tried at first on the existing installation. No success. After deleted again the Bambuddy directory and went strictly through your manual. Edited the systemd file accordingly. This is the output in the terminal:
Looking good, unfortunately still not working and still no uvicorn directory in /home/pi/bambuddy/venv/bin
@maziggy commented on GitHub (Apr 18, 2026):
What the hell is going on there? What OS are you running? There was no error during install? Show me the output of "ls -al /home/pi/bambuddy".
@maziggy commented on GitHub (Apr 18, 2026):
Between these two steps I'm missing the creation of the virtualenv!
This commands are not there:
python3 -m venv venv && source venv/bin/activate
@saint-hh commented on GitHub (Apr 18, 2026):
@maziggy commented on GitHub (Apr 18, 2026):
I really don't know what's going on, sorry. So are you sure you tere were no errors during install?
I would suggest to use the provided commands one by one and carefully watch the output.
And you still didnt answer my question what OS and version you are running.
@saint-hh commented on GitHub (Apr 18, 2026):
Linux Printer-Pi 6.12.75+rpt-rpi-v7l #1 SMP Raspbian 1:6.12.75-1+rpt1~bookworm (2026-03-11) armv7l
Running on a Pi 4B
It is originally a Octoprint image, I
ve flashed. Ive posted what I see in the command line / terminal above. Ive seen no error in there. Ill do as you suggest one by one - but have to go for the moment.Sorry for bugging you so much and thank you very much for your help!
@saint-hh commented on GitHub (Apr 18, 2026):
@saint-hh commented on GitHub (Apr 18, 2026):
@saint-hh commented on GitHub (Apr 19, 2026):
This was some kind…
In the end Claude was very helpful and I had to fix step by step one problem after another.
But it seems to be running fine now.
Even the internal update to the latest final 0.2.3 was successful now.
Thank you again for all your help - and especially for this great software! I don’t want to miss it and I’m happy that it seems to work fine now.