homebridge-config-ui-x: v4.50.3 Update Fails
Describe The Bug
Clicking the update button on the web for 4.50.3 and it is failing.
Logs
CMD: npm install -g homebridge-config-ui-x@4.50.3
npm ERR! process terminated
npm ERR! signal SIGTERM
npm ERR! A complete log of this run can be found in:
npm ERR! /home/homebridge/.npm/_logs/2023-05-12T13_35_33_771Z-debug-0.log
Cleaning up npm cache, please wait...
npm cache cleared, please try updating homebridge-config-ui-x again.
Operation failed. Please review log for details.
2110 verbose stack Error: process terminated
2110 verbose stack at /opt/homebridge/lib/node_modules/npm/node_modules/@npmcli/arborist/lib/arborist/reify.js:200:39
2110 verbose stack at process.<anonymous> (/opt/homebridge/lib/node_modules/npm/node_modules/@npmcli/arborist/lib/signal-handling.js:53:5)
2110 verbose stack at process.emit (node:events:525:35)
Config
No response
Homebridge UI Version
4.50.2
Homebridge Version
1.6.1
Node.js Version
16.14.0
Operating System
Raspberry Pi OS / Raspbian
Environment Info
- Using Docker?
- Using Hyper-V?
- Using hb-service?
Raspberry Pi Model
Raspberry Pi Zero W
About this issue
- Original URL
- State: closed
- Created a year ago
- Comments: 27 (13 by maintainers)
Just wanted to follow-up in case this is still an issue for anyone else. I tried deleting and downgrading the UI version – did not work. I then tried deleting and installing the just released 4.50.4 version, still did not work. I finally thought to reinstall the homebridge user, and that got the UI working:
sudo hb-service install --user homebridgeNow I’m having to reinstall plugins.
Updating to 4.50.4 worked. 👍 thanks!
@Staubgeborener All the homebridge collaborators are now contributing to the ongoing maintenance and support of this package and several other core packages, including the docker image.
I just happen to have the been person to hit the release button at this time, so I’m also taking the lead on post release support.
Once this release has settled into the community the plan is to also update all the packages like the docker include that include this. As I wanted to reduce the release risk, I’m staggering the packages.