[BUG] Import Failing onto Raspberry Pi

[nisted]

Make sure you're on the latest stable or beta build

• I have tested this on the latest stable or beta release

Is this a bug in companion itself or a module?

• I believe this to be a bug in companion and not a specific module

Is there an existing issue for this?

• I have searched the existing issues

Describe the bug

On Raspberry Pi installations of Bitfocus Companion, importing a full Companion configuration consistently fails.
This affects all stable versions from v4.1.1 through v4.2.1.

The same export files import successfully on macOS and Windows, but fail on Raspberry Pi — even when the export originates from the same Pi and the same Companion version. After the failure, Companion restores the previously-installed configuration.

Steps To Reproduce

Steps to reproduce

1. Install Bitfocus Companion on a Raspberry Pi (any stable version from v4.1.1 through v4.2.1).
2. Open the Companion web UI on the Pi using any of the following:

• http://:8000 (e.g. 192.168.1.127:8000)

• http://raspberrypi.local:8000

• http://127.0.0.1:8000 (locally on the Pi)

3. Attempt to import a full Companion export using any export format:

• Compressed

• JSON

• YAML

(Exports tested from macOS, Windows, and the same Raspberry Pi, all running the identical Companion version.)

4. Observe the import process.

Actual behaviour

• The “Importing Config – This may take a while” dialog appears briefly.

• The import then fails with “Failed”.

• A “Houston, we have a problem” warning is shown.

• Companion automatically restores the previously-installed configuration.

• No partial import occurs.

Expected Behavior

The full Companion configuration should import successfully on Raspberry Pi, matching the behaviour observed on macOS and Windows for the same export files and Companion versions.

Environment (please complete the following information)

Device: Raspberry Pi

OS: Raspberry Pi OS (Debian-based)

Companion versions affected: All stable releases from v4.1.1 through v4.2.1

Access method:

Remote browser via IP or hostname

Local browser on the Pi itself

Export formats tested:

Compressed

JSON

YAML

Additional context

• Importing a configuration that contains connections/settings only (no buttons) succeeds.

• Importing individual pages succeeds, including all 104 pages from my normal setup when imported one by one.

• The same Mac-generated export:

• Imports successfully on Windows

• Fails on Raspberry Pi

• Exporting from a Raspberry Pi and importing onto macOS or Windows works correctly.

• Importing a small configuration (few pages/buttons) worked early on, but cannot be reliably re-tested because once a small import succeeds, the full configuration cannot be restored on the Pi.

• The failure appears correlated with larger configurations / file size, although this is currently only a suspicion.

Historical note (ruled out but included for completeness)

At one point, a macOS export was modified externally (via ChatGPT) to shift every button one position down and to the right before being re-imported. Initially this was suspected as a possible cause.

However:

• The entire configuration was later rebuilt on the Pi using individual page imports.

• That rebuilt configuration exported successfully from the Pi to macOS.

• Re-exporting from macOS and importing back onto the Pi still fails.

The only consistent point of failure is importing onto Raspberry Pi.

Logs from a failed import attempt on Raspberry Pi are available if required.

[Julusian]

yeah some logs or a copy of the export would be helpful in figuring this out.
If you dont want to post it here, you can email it me companion@julusian.co.uk