HomeBridgeController
HomeBridgeController copied to clipboard
After update and subsequent rollback I can't launch hombridge with controller installed.
I get this when HomeBridgeControllerLink is enabled. This had worked previously.
path.js:8 throw new TypeError('Path must be a string. Received ' + ^
TypeError: Path must be a string. Received undefined
at assertPath (path.js:8:11)
at Object.posix.resolve (path.js:426:5)
at Conf.loadPrefix (/usr/local/lib/node_modules/homebridge-controllerlink/node_modules/npm/lib/config/load-prefix.js:43:14)
at load_ (/usr/local/lib/node_modules/homebridge-controllerlink/node_modules/npm/lib/config/core.js:109:8)
at Conf.
FYI, I'm getting this too
same here
Ohh sweet. At least I"m not alone. It was working prior.
same here.
Oh Dear. @KraigM, sounds like there may be a recurring issue. Happy to help Debug.
Happy to provide logs/whatever you need.
Same here. I had Homebridge working great, but I wanted to install HomeBridgeController as well to fix Celcius/ Fahrenheit issues, but I can't get HomeBridge to load now.
Same issue for me.
Similar here. I had it running when I was using my Mac as a homebridge station, but when I switched to Pi, it broke and I get this error. FWIW, I get this error on several plugins, not just the homebridge-controllerlink one.
Looking through things, I wonder: could it be using the wrong node
to run homebridge? There are at least two copies installed: one at /usr/bin/node and the one installed under the pi user that's intended to be used.
I was able to fix this by doing the following:
on line 43 of /usr/local/lib/node_modules/homebridge-controllerlink/node_modules/npm/lib/config/load-prefix.js
i changed:
p = path.resolve(cli.prefix)
to
p = path.resolve(String(cli.prefix))
and on line 21 of /usr/local/lib/node_modules/homebridge-controllerlink/node_modules/npm/lib/config/set-user.js
i changed
var prefix = path.resolve(this.get('prefix'))
to
var prefix = path.resolve(String(this.get('prefix')))
@jaredmichaelwilliams this fixed my issue too!
And for me as well. Thanks!
@jaredmichaelwilliams This worked here as well. Thank you.
@jaredmichaelwilliams Thank you!!!!! the fix worked for me.
Thanks for the fix. Can it be published to the source ?
Thnx for the fix !