[GH-ISSUE #727] [Bug Report] Bambu A1 K Profiles not showing up.

BreizhHardware commented

2026-05-07 00:10:42 +02:00

Owner

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

Originally assigned to: @maziggy on GitHub.

Bambu A1 K Profiles not showing up.

Screenshot

Reporter Contact

Email: franciscovasq6@gmail.com

System Information

{
  "generated_at": "2026-03-17T00:17:42.938657",
  "app": {
    "version": "0.2.2",
    "debug_mode": false
  },
  "system": {
    "platform": "Linux",
    "platform_release": "6.12.54-Unraid",
    "platform_version": "#1 SMP PREEMPT_DYNAMIC Tue Oct 21 15:58:46 PDT 2025",
    "architecture": "x86_64",
    "python_version": "3.13.12"
  },
  "environment": {
    "docker": true,
    "data_dir": "/app/data",
    "log_dir": "/app/logs",
    "timezone": "America/New_York"
  },
  "database": {
    "archives_total": 34,
    "archives_completed": 19,
    "printers_total": 1,
    "filaments_total": 0,
    "projects_total": 0,
    "smart_plugs_total": 0
  },
  "printers": [
    {
      "index": 1,
      "model": "A1",
      "nozzle_count": 1,
      "is_active": true,
      "mqtt_connected": true,
      "state": "RUNNING",
      "firmware_version": "01.07.02.00",
      "wifi_signal": -28,
      "reachable": true,
      "ams_unit_count": 1,
      "ams_tray_count": 4,
      "has_vt_tray": true,
      "external_camera_configured": false,
      "plate_detection_enabled": false,
      "hms_error_count": 0,
      "developer_mode": null,
      "nozzle_rack_count": 0
    }
  ],
  "settings": {
    "auth_enabled": "true",
    "setup_completed": "true",
    "auto_archive": "true",
    "save_thumbnails": "true",
    "capture_finish_photo": "true",
    "default_filament_cost": "22.0",
    "currency": "USD",
    "energy_cost_per_kwh": "0.15",
    "energy_tracking_mode": "total",
    "check_updates": "true",
    "check_printer_firmware": "true",
    "include_beta_updates": "false",
    "notification_language": "en",
    "bed_cooled_threshold": "35.0",
    "ams_humidity_good": "40",
    "ams_humidity_fair": "60",
    "ams_temp_good": "28.0",
    "ams_temp_fair": "35.0",
    "ams_history_retention_days": "30",
    "per_printer_mapping_expanded": "false",
    "date_format": "us",
    "time_format": "12h",
    "default_printer_id": "None",
    "ftp_retry_enabled": "true",
    "ftp_retry_count": "3",
    "ftp_retry_delay": "2",
    "ftp_timeout": "30",
    "mqtt_enabled": "false",
    "mqtt_broker": "",
    "mqtt_port": "1883",
    "mqtt_topic_prefix": "bambuddy",
    "mqtt_use_tls": "false",
    "ha_enabled": "false",
    "library_archive_mode": "ask",
    "library_disk_warning_gb": "5.0",
    "camera_view_mode": "embedded",
    "preferred_slicer": "bambu_studio",
    "prometheus_enabled": "false",
    "spoolman_enabled": "false",
    "spoolman_sync_mode": "auto",
    "spoolman_disable_weight_sync": "false",
    "spoolman_report_partial_usage": "true",
    "dark_background": "oled",
    "dark_accent": "red",
    "dark_style": "vibrant"
  },
  "docker": {
    "container_memory_limit_bytes": null,
    "container_memory_limit_formatted": null,
    "network_mode_hint": "bridge"
  },
  "virtual_printers": [],
  "integrations": {
    "notification_providers": [
      {
        "type": "callmebot",
        "enabled": false,
        "has_last_error": true
      }
    ],
    "spoolman": {
      "enabled": false,
      "reachable": false
    },
    "mqtt_relay": {
      "enabled": false,
      "connected": false,
      "broker": "",
      "port": 0,
      "topic_prefix": "bambuddy"
    },
    "homeassistant": {
      "enabled": false
    }
  },
  "database_health": {
    "journal_mode": "wal",
    "quick_check": "ok",
    "db_size_bytes": 675840,
    "wal_size_bytes": 4136512
  },
  "dependencies": {
    "fastapi": "0.135.1",
    "uvicorn": "0.42.0",
    "pydantic": "2.12.5",
    "sqlalchemy": "2.0.48",
    "paho-mqtt": "2.1.0",
    "psutil": "7.2.2",
    "httpx": "0.28.1",
    "aiofiles": "25.1.0",
    "cryptography": "46.0.5",
    "opencv-python-headless": "4.13.0.92",
    "numpy": "2.4.3"
  },
  "log_file": {
    "size_bytes": 1483212,
    "size_formatted": "1.4 MB"
  },
  "network": {
    "interface_count": 1,
    "interfaces": [
      {
        "name": "eth0",
        "subnet": "x.x.8.0/24"
      }
    ]
  },
  "websockets": {
    "active_connections": 2
  }
}

Logs (sanitized): bambuddy.log

Submitted via BamBuddy Bug Report

Originally created by @maziggy on GitHub (Mar 17, 2026). Original GitHub issue: https://github.com/maziggy/bambuddy/issues/727 Originally assigned to: @maziggy on GitHub. Bambu A1 K Profiles not showing up. ### Screenshot ![Bug Report Screenshot](https://raw.githubusercontent.com/maziggy/bambuddy/bug-report-assets/screenshots/307177666dfb4b83ab416fdc4a902721.png) <details> <summary>Reporter Contact</summary> Email: franciscovasq6@gmail.com </details> <details> <summary>System Information</summary> ```json { "generated_at": "2026-03-17T00:17:42.938657", "app": { "version": "0.2.2", "debug_mode": false }, "system": { "platform": "Linux", "platform_release": "6.12.54-Unraid", "platform_version": "#1 SMP PREEMPT_DYNAMIC Tue Oct 21 15:58:46 PDT 2025", "architecture": "x86_64", "python_version": "3.13.12" }, "environment": { "docker": true, "data_dir": "/app/data", "log_dir": "/app/logs", "timezone": "America/New_York" }, "database": { "archives_total": 34, "archives_completed": 19, "printers_total": 1, "filaments_total": 0, "projects_total": 0, "smart_plugs_total": 0 }, "printers": [ { "index": 1, "model": "A1", "nozzle_count": 1, "is_active": true, "mqtt_connected": true, "state": "RUNNING", "firmware_version": "01.07.02.00", "wifi_signal": -28, "reachable": true, "ams_unit_count": 1, "ams_tray_count": 4, "has_vt_tray": true, "external_camera_configured": false, "plate_detection_enabled": false, "hms_error_count": 0, "developer_mode": null, "nozzle_rack_count": 0 } ], "settings": { "auth_enabled": "true", "setup_completed": "true", "auto_archive": "true", "save_thumbnails": "true", "capture_finish_photo": "true", "default_filament_cost": "22.0", "currency": "USD", "energy_cost_per_kwh": "0.15", "energy_tracking_mode": "total", "check_updates": "true", "check_printer_firmware": "true", "include_beta_updates": "false", "notification_language": "en", "bed_cooled_threshold": "35.0", "ams_humidity_good": "40", "ams_humidity_fair": "60", "ams_temp_good": "28.0", "ams_temp_fair": "35.0", "ams_history_retention_days": "30", "per_printer_mapping_expanded": "false", "date_format": "us", "time_format": "12h", "default_printer_id": "None", "ftp_retry_enabled": "true", "ftp_retry_count": "3", "ftp_retry_delay": "2", "ftp_timeout": "30", "mqtt_enabled": "false", "mqtt_broker": "", "mqtt_port": "1883", "mqtt_topic_prefix": "bambuddy", "mqtt_use_tls": "false", "ha_enabled": "false", "library_archive_mode": "ask", "library_disk_warning_gb": "5.0", "camera_view_mode": "embedded", "preferred_slicer": "bambu_studio", "prometheus_enabled": "false", "spoolman_enabled": "false", "spoolman_sync_mode": "auto", "spoolman_disable_weight_sync": "false", "spoolman_report_partial_usage": "true", "dark_background": "oled", "dark_accent": "red", "dark_style": "vibrant" }, "docker": { "container_memory_limit_bytes": null, "container_memory_limit_formatted": null, "network_mode_hint": "bridge" }, "virtual_printers": [], "integrations": { "notification_providers": [ { "type": "callmebot", "enabled": false, "has_last_error": true } ], "spoolman": { "enabled": false, "reachable": false }, "mqtt_relay": { "enabled": false, "connected": false, "broker": "", "port": 0, "topic_prefix": "bambuddy" }, "homeassistant": { "enabled": false } }, "database_health": { "journal_mode": "wal", "quick_check": "ok", "db_size_bytes": 675840, "wal_size_bytes": 4136512 }, "dependencies": { "fastapi": "0.135.1", "uvicorn": "0.42.0", "pydantic": "2.12.5", "sqlalchemy": "2.0.48", "paho-mqtt": "2.1.0", "psutil": "7.2.2", "httpx": "0.28.1", "aiofiles": "25.1.0", "cryptography": "46.0.5", "opencv-python-headless": "4.13.0.92", "numpy": "2.4.3" }, "log_file": { "size_bytes": 1483212, "size_formatted": "1.4 MB" }, "network": { "interface_count": 1, "interfaces": [ { "name": "eth0", "subnet": "x.x.8.0/24" } ] }, "websockets": { "active_connections": 2 } } ``` </details> **Logs (sanitized):** [bambuddy.log](https://raw.githubusercontent.com/maziggy/bambuddy/bug-report-assets/logs/4f27dca656374dccb02e0c10f9ee0348.log) --- *Submitted via BamBuddy Bug Report*

BreizhHardware

2026-05-07 00:10:42 +02:00

closed this issue
added the
user-report

bug
labels

BreizhHardware commented

2026-05-07 00:10:43 +02:00

Author

Owner

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

Please upload a support package -> https://wiki.bambuddy.cool/features/system-info/?h=debug#enable-debug-logging

@maziggy commented on GitHub (Mar 17, 2026): Please upload a support package -> https://wiki.bambuddy.cool/features/system-info/?h=debug#enable-debug-logging

BreizhHardware commented

2026-05-07 00:10:43 +02:00

Author

Owner

@platini76 commented on GitHub (Mar 25, 2026):

also on h2c

@platini76 commented on GitHub (Mar 25, 2026): also on h2c

BreizhHardware commented

2026-05-07 00:10:43 +02:00

Author

Owner

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

Please upload a support package -> https://wiki.bambuddy.cool/features/system-info/?h=debug#enable-debug-logging

@maziggy commented on GitHub (Mar 26, 2026): Please upload a support package -> https://wiki.bambuddy.cool/features/system-info/?h=debug#enable-debug-logging

BreizhHardware commented

2026-05-07 00:10:44 +02:00

Author

Owner

@platini76 commented on GitHub (Mar 26, 2026):

I made it through bug internal send

@platini76 commented on GitHub (Mar 26, 2026): I made it through bug internal send

BreizhHardware commented

2026-05-07 00:10:44 +02:00

Author

Owner

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

Too few logs to investigate.

@maziggy commented on GitHub (Mar 26, 2026): Too few logs to investigate.

BreizhHardware commented

2026-05-07 00:10:44 +02:00

Author

Owner

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

bambuddy-support-20260328-171151.zip
Same with P1S. If you need anything else for further testing, let me know.

edit: Updated to latest dev and is working now.

@Christophe999s commented on GitHub (Mar 28, 2026): [bambuddy-support-20260328-171151.zip](https://github.com/user-attachments/files/26324932/bambuddy-support-20260328-171151.zip) Same with P1S. If you need anything else for further testing, let me know. edit: Updated to latest dev and is working now.

BreizhHardware commented

2026-05-07 00:10:44 +02:00

Author

Owner

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

There are no changes at all for the cloud connection.

@maziggy commented on GitHub (Mar 28, 2026): There are no changes at all for the cloud connection.

BreizhHardware commented

2026-05-07 00:10:44 +02:00

Author

Owner

@Christophe999s commented on GitHub (Mar 29, 2026):

It looks like a simple restart of the bambuddy service solves the problem. Had it again this morning and after doing a systemctl restart bambuddy the K profiles were visible again. I'll check again later to see if the problem reoccurs and if a restart solves it.

@Christophe999s commented on GitHub (Mar 29, 2026): It looks like a simple restart of the bambuddy service solves the problem. Had it again this morning and after doing a `systemctl restart bambuddy` the K profiles were visible again. I'll check again later to see if the problem reoccurs and if a restart solves it.

BreizhHardware commented

2026-05-07 00:10:44 +02:00

Author

Owner

@lightmaster commented on GitHub (Mar 30, 2026):

I think this is the same issue I'm seeing (the screenshot from OP says Error 404 for me). I have k-profiles on my X1C/AMS that Bambuddy has pulled and shows on the Profiles page, but when I try to assign the k-profile to a filament, it says there are no matching k-profiles.

bambuddy-support-20260330-195031.zip

@lightmaster commented on GitHub (Mar 30, 2026): I think this is the same issue I'm seeing (the screenshot from OP says Error 404 for me). I have k-profiles on my X1C/AMS that Bambuddy has pulled and shows on the Profiles page, but when I try to assign the k-profile to a filament, it says there are no matching k-profiles. <img width="504" height="694" alt="Image" src="https://github.com/user-attachments/assets/552b8f4d-33bc-4bdc-86d1-a63b6f4f6d68" /> <img width="602" height="365" alt="Image" src="https://github.com/user-attachments/assets/fa7d57ca-e11c-44e0-b172-dbb1c2e69deb" /> [bambuddy-support-20260330-195031.zip](https://github.com/user-attachments/files/26363186/bambuddy-support-20260330-195031.zip)

BreizhHardware commented

2026-05-07 00:10:44 +02:00

Author

Owner

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

There are multiple problems with your installation.

In general your printer's Wifi signal is very weak. This can cause connections to be dropped!!!

First of all to me it looks like you didn't follow the installation instructions.

Developer mode is not enabled on your printer, or there is something else broken. Report shows firmware version 99.00.00.00 for your X1C. This is not valid.
SD card is formatted and inserted into the printer?
"Store sent files on external storage" enabled in slicer?

@maziggy commented on GitHub (Mar 31, 2026): There are multiple problems with your installation. In general your printer's Wifi signal is very weak. This can cause connections to be dropped!!! First of all to me it looks like you didn't follow the installation instructions. - Developer mode is not enabled on your printer, or there is something else broken. Report shows firmware version 99.00.00.00 for your X1C. This is not valid. - SD card is formatted and inserted into the printer? - "Store sent files on external storage" enabled in slicer?

BreizhHardware commented

2026-05-07 00:10:44 +02:00

Author

Owner

@lightmaster commented on GitHub (Mar 31, 2026):

There are multiple problems with your installation.

In general your printer's Wifi signal is very weak. This can cause connections to be dropped!!!

First of all to me it looks like you didn't follow the installation instructions.
* Developer mode is not enabled on your printer, or there is something else broken. Report shows firmware version 99.00.00.00 for your X1C. This is not valid.

* SD card is formatted and inserted into the printer?

* "Store sent files on external storage" enabled in slicer?

I'm running X1Plus, Bambu sets the firmware version they see to 99.00.00.00 so that their firmware updates will never try to install over X1Plus. So developer mode doesn't exist on my printer and I have full root access without needing LAN/Developer mode.

Yes, SD card is installed and the "store sent files on external storage" is enabled, and Bambuddy does grab gcode files that are sent to the printer with those gcode files showing up in the archive page.

Idk why the WiFi always reports as low signal, cuz the camera stream is always stable and gcode files of dozens of MB upload in just a few seconds. I can temporarily move the printer to a few feet from the AP just to rule that out if need be.

@lightmaster commented on GitHub (Mar 31, 2026): > There are multiple problems with your installation. > > In general your printer's Wifi signal is very weak. This can cause connections to be dropped!!! > > First of all to me it looks like you didn't follow the installation instructions. > > * Developer mode is not enabled on your printer, or there is something else broken. Report shows firmware version 99.00.00.00 for your X1C. This is not valid. > > * SD card is formatted and inserted into the printer? > > * "Store sent files on external storage" enabled in slicer? I'm running X1Plus, Bambu sets the firmware version they see to 99.00.00.00 so that their firmware updates will never try to install over X1Plus. So developer mode doesn't exist on my printer and I have full root access without needing LAN/Developer mode. Yes, SD card is installed and the "store sent files on external storage" is enabled, and Bambuddy does grab gcode files that are sent to the printer with those gcode files showing up in the archive page. Idk why the WiFi always reports as low signal, cuz the camera stream is always stable and gcode files of dozens of MB upload in just a few seconds. I can temporarily move the printer to a few feet from the AP just to rule that out if need be.

BreizhHardware commented

2026-05-07 00:10:44 +02:00

Author

Owner

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

I don't know X1Plus, maybe there's something different.

@maziggy commented on GitHub (Mar 31, 2026): I don't know X1Plus, maybe there's something different.

BreizhHardware commented

2026-05-07 00:10:45 +02:00

Author

Owner

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

Show me a screenshot of your slicer calibration screen showing the k-profile you are missing in Bambuddy.

@maziggy commented on GitHub (Mar 31, 2026): Show me a screenshot of your slicer calibration screen showing the k-profile you are missing in Bambuddy.

BreizhHardware commented

2026-05-07 00:10:45 +02:00

Author

Owner

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

Your backend is working correctly — 79 K-profiles are fetched from the printer every time. The issue is on the frontend matching side.

When you configure an AMS slot and select a filament preset, BamBuddy tries to find matching K-profiles by searching the profile name for the filament's material type and brand. Looking at your logs, your profiles are named by color:

"Sparkle Onyx" (ASA)
"Beige" (ASA)
"Black" (ASA)

Since none of these names contain "ASA" or "Bambu", the matcher can't find them and shows "No matching K profiles found."

Workaround for now: Rename your K-profiles to include the material type, e.g. "ASA Sparkle Onyx", "ASA Beige", etc. The matching should pick them up then.

@maziggy commented on GitHub (Mar 31, 2026): Your backend is working correctly — 79 K-profiles are fetched from the printer every time. The issue is on the frontend matching side. When you configure an AMS slot and select a filament preset, BamBuddy tries to find matching K-profiles by searching the profile name for the filament's material type and brand. Looking at your logs, your profiles are named by color: - "Sparkle Onyx" (ASA) - "Beige" (ASA) - "Black" (ASA) Since none of these names contain "ASA" or "Bambu", the matcher can't find them and shows "No matching K profiles found." Workaround for now: Rename your K-profiles to include the material type, e.g. "ASA Sparkle Onyx", "ASA Beige", etc. The matching should pick them up then.

BreizhHardware commented

2026-05-07 00:10:45 +02:00

Author

Owner

@lightmaster commented on GitHub (Mar 31, 2026):

X1Plus is essentially a custom firmware for X1 printers that gives extra features, enables full root SSH access, prevents Bambu's change to the "more secure" middle-man tool or whatever that is (didn't look too much into it since it didn't affect me). https://github.com/X1Plus/X1Plus/wiki

There are around 60 or so k-profiles there. All of the profiles show up on the Profiles -> K-Profiles page in Bambuddy, they just don't show up in the Add/Edit Spools page or on the Configure AMS Slot page. Just says "No matching K profiles found. Default K=0.020 will be used".

@lightmaster commented on GitHub (Mar 31, 2026): X1Plus is essentially a custom firmware for X1 printers that gives extra features, enables full root SSH access, prevents Bambu's change to the "more secure" middle-man tool or whatever that is (didn't look too much into it since it didn't affect me). https://github.com/X1Plus/X1Plus/wiki <img width="930" height="729" alt="Image" src="https://github.com/user-attachments/assets/c5b2cfb4-3978-49b2-852a-32eeec3d3665" /> There are around 60 or so k-profiles there. All of the profiles show up on the Profiles -> K-Profiles page in Bambuddy, they just don't show up in the Add/Edit Spools page or on the Configure AMS Slot page. Just says "No matching K profiles found. Default K=0.020 will be used".

BreizhHardware commented

2026-05-07 00:10:45 +02:00

Author

Owner

@lightmaster commented on GitHub (Mar 31, 2026):

Your backend is working correctly — 79 K-profiles are fetched from the printer every time. The issue is on the frontend matching side.

When you configure an AMS slot and select a filament preset, BamBuddy tries to find matching K-profiles by searching the profile name for the filament's material type and brand. Looking at your logs, your profiles are named by color:
* "Sparkle Onyx" (ASA)

* "Beige" (ASA)

* "Black" (ASA)
Since none of these names contain "ASA" or "Bambu", the matcher can't find them and shows "No matching K profiles found."

Workaround for now: Rename your K-profiles to include the material type, e.g. "ASA Sparkle Onyx", "ASA Beige", etc. The matching should pick them up then.

K. Lemme try that. Not sure if it will work right now while printing, so might have to do that in a couple hours when it's done.

@lightmaster commented on GitHub (Mar 31, 2026): > Your backend is working correctly — 79 K-profiles are fetched from the printer every time. The issue is on the frontend matching side. > > When you configure an AMS slot and select a filament preset, BamBuddy tries to find matching K-profiles by searching the profile name for the filament's material type and brand. Looking at your logs, your profiles are named by color: > > * "Sparkle Onyx" (ASA) > > * "Beige" (ASA) > > * "Black" (ASA) > > > Since none of these names contain "ASA" or "Bambu", the matcher can't find them and shows "No matching K profiles found." > > Workaround for now: Rename your K-profiles to include the material type, e.g. "ASA Sparkle Onyx", "ASA Beige", etc. The matching should pick them up then. K. Lemme try that. Not sure if it will work right now while printing, so might have to do that in a couple hours when it's done.

BreizhHardware commented

2026-05-07 00:10:45 +02:00

Author

Owner

@lightmaster commented on GitHub (Mar 31, 2026):

It let me rename them while printing. Changing "Orange" for Bambu's PLA Basic filament to "PLA Orange" made it show up for both PLA Basic and PLA Silk filaments, renaming it to "PLA Basic Orange" got it to show up for just the PLA Basic filaments and not the PLA Silk filaments. Don't really have anything against renaming them all, just a lot to rename. I just named them by the color alone as Orca Slicer shows the filament type in it's own column and the printer only shows the K-Profiles for the specific type of filament the K-Profile was created for. Using just the color for the name kept the names from being really long with some of them so they showed up on the printer's screen nicer.

Edit: While both "PLA Orange" and "PLA Basic Orange" makes the k-profile show up on the filaments page for PA Profiles, if I go to configure the AMS Slot on the Printer page, neither of those names will show up still.

Edit 2: "Bambu PLA Basic Orange" makes it show up for PLA Basic on the Filaments page and not show up for PLA Silk, however it makes it show up for both PLA Basic and PLA Silk on the Printer page's AMS Slot configuration.

@lightmaster commented on GitHub (Mar 31, 2026): It let me rename them while printing. Changing "Orange" for Bambu's PLA Basic filament to "PLA Orange" made it show up for both PLA Basic and PLA Silk filaments, renaming it to "PLA Basic Orange" got it to show up for just the PLA Basic filaments and not the PLA Silk filaments. Don't really have anything against renaming them all, just a lot to rename. I just named them by the color alone as Orca Slicer shows the filament type in it's own column and the printer only shows the K-Profiles for the specific type of filament the K-Profile was created for. Using just the color for the name kept the names from being really long with some of them so they showed up on the printer's screen nicer. Edit: While both "PLA Orange" and "PLA Basic Orange" makes the k-profile show up on the filaments page for PA Profiles, if I go to configure the AMS Slot on the Printer page, neither of those names will show up still. Edit 2: "Bambu PLA Basic Orange" makes it show up for PLA Basic on the Filaments page and not show up for PLA Silk, however it makes it show up for both PLA Basic and PLA Silk on the Printer page's AMS Slot configuration.

BreizhHardware commented

2026-05-07 00:10:45 +02:00

Author

Owner

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

Then there are still naming issues.

For the filamnents in question, show me the name of filament profile and k-profile.

@maziggy commented on GitHub (Mar 31, 2026): Then there are still naming issues. For the filamnents in question, show me the name of filament profile and k-profile.

BreizhHardware commented

2026-05-07 00:10:46 +02:00

Author

Owner

@lightmaster commented on GitHub (Mar 31, 2026):

That what you're looking for?

@lightmaster commented on GitHub (Mar 31, 2026): <img width="280" height="98" alt="Image" src="https://github.com/user-attachments/assets/df920961-93dd-454b-b18a-8ff207d07078" /> <img width="537" height="897" alt="Image" src="https://github.com/user-attachments/assets/7bf7364d-5cde-4ebc-bd4f-8cf9d751fb71" /> That what you're looking for?

BreizhHardware referenced this issue

2026-05-07 00:15:49 +02:00

[PR #555] [MERGED] v0.2.1.1 #1069

BreizhHardware referenced this issue

2026-05-07 00:15:54 +02:00

[PR #601] [CLOSED] v0.2.2b1 #1083

BreizhHardware referenced this issue

2026-05-07 00:15:54 +02:00

[PR #602] [MERGED] v0.2.2b1 #1084