1
0
Fork 0
mirror of https://github.com/maziggy/bambuddy.git synced 2026-05-09 08:25:54 +02:00

[GH-ISSUE #837] [Bug]: HomeAssistant invalid access token #565

Closed
opened 2026-05-07 00:11:41 +02:00 by BreizhHardware · 2 comments

Originally created by @daFreeMan on GitHub (Mar 28, 2026).
Original GitHub issue: https://github.com/maziggy/bambuddy/issues/837

Originally assigned to: @maziggy on GitHub.

Bug Description

Running bambuddy on Unraid in Docker. I've created a new Long-lived Access Token in HomeAssistant and copy/pasted it into the appropriate field in Settings > Network. When I click the Test button, it tells me:

Connection Failed: Invalid access token

I've tried several times. I've deleted the LLAT in HA and created a new one. Copy/Pasting the new one gives the same result.

I'm running HAOS in a VM on the same Unraid server.

Expected Behavior

I would expect it to connect to HomeAssistant.

Steps to Reproduce

  1. Go to Settings > Network
  2. Enter HAOS IP:port
  3. Enter LLAT copy/pasted from HAOS
  4. Click Test button
  5. See error

Printer Model

A1 Mini

Bambuddy Version

v0.2.2.1

Printer Firmware Version

1.04.00.00

Installation Method

Docker

Operating System

Docker

Relevant Logs / Support Package

bambuddy-support-20260327-194507.zip

Screenshots

Image

Additional Context

Maybe I need a firmware update on the printer? I don't have a Developer Mode at all.

Image

Checklist

  • I have searched existing issues to ensure this bug hasn't already been reported
  • I am using the latest version of Bambuddy
  • My printer is set to LAN Only mode
  • My printer has Developer Mode enabled
Originally created by @daFreeMan on GitHub (Mar 28, 2026). Original GitHub issue: https://github.com/maziggy/bambuddy/issues/837 Originally assigned to: @maziggy on GitHub. ### Bug Description Running bambuddy on Unraid in Docker. I've created a new Long-lived Access Token in HomeAssistant and copy/pasted it into the appropriate field in `Settings` > `Network`. When I click the `Test` button, it tells me: `Connection Failed: Invalid access token` I've tried several times. I've deleted the LLAT in HA and created a new one. Copy/Pasting the new one gives the same result. I'm running HAOS in a VM on the same Unraid server. ### Expected Behavior I would expect it to connect to HomeAssistant. ### Steps to Reproduce 1. Go to Settings > Network 2. Enter HAOS IP:port 3. Enter LLAT copy/pasted from HAOS 4. Click Test button 5. See error ### Printer Model A1 Mini ### Bambuddy Version v0.2.2.1 ### Printer Firmware Version 1.04.00.00 ### Installation Method Docker ### Operating System Docker ### Relevant Logs / Support Package [bambuddy-support-20260327-194507.zip](https://github.com/user-attachments/files/26313560/bambuddy-support-20260327-194507.zip) ### Screenshots <img width="632" height="682" alt="Image" src="https://github.com/user-attachments/assets/340155c0-31c9-412f-84d6-1c2e0b5110e2" /> ### Additional Context Maybe I need a firmware update on the printer? I don't have a Developer Mode at all. ![Image](https://github.com/user-attachments/assets/50c2d81b-bacf-49c3-96d6-20a20fbc7a5f) ### Checklist - [x] I have searched existing issues to ensure this bug hasn't already been reported - [x] I am using the latest version of Bambuddy - [x] My printer is set to LAN Only mode - [x] My printer has Developer Mode enabled
BreizhHardware 2026-05-07 00:11:41 +02:00
  • closed this issue
  • added the
    bug
    label
Author
Owner

@maziggy commented on GitHub (Mar 28, 2026):

You printer setup has nothing to do with HA connection.

Just changed to version 0.2.2.1 and it works as expected. When looking at your logs, I clearly see that Home Assistant is refusing your token. So the problem must be on HA side, not Bambuddy.

Common gotchas: make sure you copy the entire token (it's very long), and note that tokens can't be viewed again after creation — if you lost the original, you need to create a new one.


If you find Bambuddy useful, please consider giving it a on GitHub — it helps others discover the project!

<!-- gh-comment-id:4147570160 --> @maziggy commented on GitHub (Mar 28, 2026): You printer setup has nothing to do with HA connection. Just changed to version 0.2.2.1 and it works as expected. When looking at your logs, I clearly see that Home Assistant is refusing your token. So the problem must be on HA side, not Bambuddy. Common gotchas: make sure you copy the entire token (it's very long), and note that tokens can't be viewed again after creation — if you lost the original, you need to create a new one. ----- If you find Bambuddy useful, please consider giving it a ⭐ on [GitHub](https://github.com/maziggy/bambuddy) — it helps others discover the project!
Author
Owner

@daFreeMan commented on GitHub (Mar 28, 2026):

Very bizarre, @maziggy. I created a 3rd token, copied it (using the copy button every time, I'd swear), and this time it works. 🤷‍♂️

I'll chalk it up to user error...

Thanks for looking at this.

<!-- gh-comment-id:4147970270 --> @daFreeMan commented on GitHub (Mar 28, 2026): Very bizarre, @maziggy. I created a 3rd token, copied it (using the copy button every time, I'd swear), and this time it works. 🤷‍♂️ I'll chalk it up to user error... Thanks for looking at this.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/bambuddy-maziggy-1#565
No description provided.