Where are Fluidd UI settings stored & why were they lost in KIAUH 2-Moonraker setup?

General Discussion
1

  1. Environment & Setup:

    Setup performed using KIAUH.

    Configuration:

     2 x Klipper Instances

 2 x Moonraker Instances (Configured via KIAUH, likely on different ports like 7125 and 7126)

 1 x Fluidd Instance (Connected to one of the Moonraker instances)

 2 x Physical Printers

    Note: Specific versions, OS details, configuration files, and logs can be provided upon request.

  2. Scenario:

I used KIAUH to set up Klipper for two printers on one host PC, creating two separate Moonraker instances as part of the process. I accessed the Fluidd web interface and successfully configured custom settings, including:

Friendly names for both printers.

A specific UI theme (e.g., dark mode).

These settings worked correctly for a period.

  1. Problem:

After some time (following potentially a reboot, KIAUH update, or service restart - the exact trigger isn’t confirmed), all the custom settings applied within the Fluidd interface were lost. Printer names reverted to defaults, and the theme reset.

  1. Core Questions:

    Where are Fluidd UI settings (like custom printer names and selected themes) supposed to be stored in a standard Klipper/Moonraker/Fluidd setup?

    In a non-standard setup like mine (2 Moonrakers via KIAUH), where would these settings likely have been stored?

    Is this 2-Moonraker configuration, facilitated by KIAUH, expected to reliably save and persist Fluidd UI settings, or could it lead to conflicts or data loss (e.g., during updates or restarts)?

    What could cause these specific UI settings to disappear while the underlying Klipper instances remain functional?

  2. Request:

I am trying to understand the underlying mechanism for storing these UI settings and why they might have disappeared in my specific KIAUH-managed configuration. I can provide detailed logs and configuration files if requested by the development team to help diagnose.