homebridge-config-ui-x: Getting Type Error when Booting

See https://github.com/oznu/homebridge-config-ui-x/issues/969#issuecomment-734022445

Describe The Bug: UI is not booting.

To Reproduce: Updated to 4.34.0

Expected behavior: A full boot of the UI.

Logs:

TypeError: Cannot assign to read only property 'toString' of object '#<Cancel>'
    at Object.<anonymous> (/usr/local/lib/node_modules/homebridge-config-ui-x/node_modules/axios/lib/cancel/Cancel.js:13:27)
    at Module._compile (internal/modules/cjs/loader.js:1063:30)
    at Object.Module._extensions..js (internal/modules/cjs/loader.js:1092:10)
    at Module.load (internal/modules/cjs/loader.js:928:32)
    at Function.Module._load (internal/modules/cjs/loader.js:769:14)
    at Module.require (internal/modules/cjs/loader.js:952:19)
    at require (internal/modules/cjs/helpers.js:88:18)
    at Object.<anonymous> (/usr/local/lib/node_modules/homebridge-config-ui-x/node_modules/axios/lib/axios.js:40:16)
    at Module._compile (internal/modules/cjs/loader.js:1063:30)
    at Object.Module._extensions..js (internal/modules/cjs/loader.js:1092:10)
/usr/local/lib/node_modules/homebridge-config-ui-x/node_modules/axios/lib/cancel/Cancel.js:13
Cancel.prototype.toString = function toString() {

Homebridge Config:

    "platforms": [
        {
            "name": "Config",
            "port": 8581,
            "platform": "config",
            "sudo": true
        },

Screenshots:

Environment:

Node.js Version: 14.15.0
NPM Version: 6.14.9
Homebridge Version: 1.2.3
Homebridge Config UI X Version: 4.34.0
Operating System: macOS Catalina 10.15.7
Process Supervisor: hb-service

About this issue

Original URL
State: closed
Created 4 years ago
Reactions: 12
Comments: 49 (10 by maintainers)

Most upvoted comments

Just putting full instructions in:

This seems to be caused by an outage or issue elsewhere on the internet / npm registry - whatever it was seems to have been resolved now.

For those impacted please run the following commands to repair your installation:

macOS:

npm cache clean --force
sudo npm uninstall -g homebridge-config-ui-x
sudo npm install -g --unsafe-perm homebridge-config-ui-x@latest
sudo hb-service rebuild

Linux:

sudo npm cache clean --force
sudo npm uninstall -g homebridge-config-ui-x
sudo npm install -g --unsafe-perm homebridge-config-ui-x@latest

Windows:

npm cache clean --force
npm uninstall -g homebridge-config-ui-x
npm install -g --unsafe-perm homebridge-config-ui-x@latest

oznu on Nov 26, 2020

Everything’s working good on my end too. I still haven’t installed the Ring plugin - figured I’ll wait for their services to come back online.

nikdata on Nov 26, 2020

Just putting full instructions in:

This seems to be caused by an outage or issue elsewhere on the internet / npm registry - whatever it was seems to have been resolved now.

For those impacted please run the following commands to repair your installation:

macOS:
npm cache clean --force
sudo npm uninstall -g homebridge-config-ui-x
sudo npm install -g --unsafe-perm homebridge-config-ui-x@latest
sudo hb-service rebuild
Linux:
sudo npm cache clean --force
sudo npm uninstall -g homebridge-config-ui-x
sudo npm install -g --unsafe-perm homebridge-config-ui-x@latest
Windows:
npm cache clean --force
npm uninstall -g homebridge-config-ui-x
npm install -g --unsafe-perm homebridge-config-ui-x@latest

This worked for me! had to reinstall some other plugins I might have updated at the same time.

markcsegal on Nov 26, 2020

Setting 4.34.0 back to the “latest” tag.

Can those who downgraded to 4.32.0 please try upgrade back to 4.34.0?

I’m still not sure what caused this issue to occur (or to be resolved) without any changes on my end.

oznu on Nov 26, 2020

Still getting a couple of warning, but those might be unrelated

They’re fine. Thanks for confirming it’s working.

oznu on Nov 26, 2020

I was able to fix it by explicitly uninstalling homebridge-config-ui and then doing a clean install of version 4.32.0.

npm uninstall -g homebridge-config-ui-x && npm install -g homebridge-config-ui-x@4.32.0

This fixed it for me as well!

root@:~# docker exec -it homebridge sh
/homebridge # npm uninstall -g homebridge-config-ui-x && npm install -g homebridge-config-ui-x@4.32.0

Now I can see the UI again. Thanks!

Atothendrew on Nov 25, 2020

I was able to fix it by explicitly uninstalling homebridge-config-ui and then doing a clean install of version 4.32.0.

npm uninstall -g homebridge-config-ui-x && npm install -g homebridge-config-ui-x@4.32.0

johndshea on Nov 25, 2020

Same on Raspberry PI Tried reinstall and downgrade

tml89 on Nov 25, 2020