bitfocus
[BUG] companion pi 4.2 error
Make sure you're on the latest stable or beta build
- [x] I have tested this on the latest stable or beta release
Is this a bug in companion itself or a module?
- [x] I believe this to be a bug in companion and not a specific module
Is there an existing issue for this?
- [x] I have searched the existing issues
Describe the bug
Version 4.2 installed on Raspberry Pi does not work. This is the same even if you use companion-update or download and install the companion pi image. The error below appears. If I roll back to 4.1.6 using companion-update again, it works fine.
pi@CompanionPi:~ $ sudo systemctl status companion × companion.service - Bitfocus Companion Loaded: loaded (/etc/systemd/system/companion.service; enabled; preset: enabled) Active: failed (Result: exit-code) since Wed 2025-12-10 14:07:27 GMT; 5min ago Duration: 257ms Invocation: 5b15d84c87ea43c18e7ff8b23af6cfb6 Process: 1056 ExecStart=/usr/local/src/companionpi/launch.sh (code=exited, status=1/FAILURE) Main PID: 1056 (code=exited, status=1/FAILURE)
Dec 10 14:07:27 CompanionPi systemd[1]: companion.service: Scheduled restart job, restart counter is at 5. Dec 10 14:07:27 CompanionPi systemd[1]: companion.service: Start request repeated too quickly. Dec 10 14:07:27 CompanionPi systemd[1]: companion.service: Failed with result 'exit-code'. Dec 10 14:07:27 CompanionPi systemd[1]: Failed to start companion.service - Bitfocus Companion.
Steps To Reproduce
No response
Expected Behavior
No response
Environment (please complete the following information)
- OS:
- Browser:
- Companion Version:
Additional context
No response
A friend had the same issue. It is due to bufferutil missing as it's removed here during the build process if companion is built for linux/arm64. The reason for that is that bufferutil doesn't ship prebuilds for linux/arm64. Why I don't know. There is some old issue (websockets/bufferutil#150) about that, that doesn't really give any good explanation.
I added this ugly fix to the archlinux aur package that works around the issue and makes 4.2.0 work on linux/arm64.
Thank you @scientress for this hotfix, so I'll stay on 4.1x until its fixed in the official built.
BTW I can confirm that 4.16 works great on Companion PI
There is a fix ready for 4.2.1. Ill leave this open until that is released
Today, I confirmed that version 4.2.1 was distributed, installed it, and confirmed that it operates without problems. thank you