Closed hvorragend closed 6 years ago
I'm sorry to say, but this seems to be an error due to FHEM :(
npm info lifecycle homebridge-fhem@0.3.7~postinstall: homebridge-fhem@0.3.7 � ok module.js:529 throw err; ^
Sorry, but this error still appears of I don‘t use any plugins.
It seems to be related with the contents of the .env sample: https://github.com/marcoraddatz/homebridge-docker/blob/master/samples/.env
After removing it, it works like a charm.
Glad to hear that! I'm curious: Have you set non-default parameters? Maybe there was some wrong spelling?
I am using your original sample without any modifications.
It seems to be caused by this line:
HOMEBRIDGE_VERSION=latest
The installation progress is much longer with "latest" in comparison to a non-setted version parameter.
Thanks for sharing. Maybe FHEM isn't compatible with the latest Homebridge version. If no .env
is used, the container's default Homebridge version gets used. If HOMEBRIDGE_VERSION=latest
is set, the scripts will upgrade the existing Homebridge version via npm to the latest version available — that's why it takes so long. I'd always recommend to avoid the usage of the .env
file unless some default settings shall be overridden.
Just for your information: The FHEM-plugin wasn‘t enabled. My latest tests were just clean installations.
Ok. Hopefully it isn't Homebridge itself, but don't see any issues.
Each time I start your homebridge-docker-image, a error appears:
I have to restart the container and then the error disappears.
Do you have an idea?
docker-compose.yml
install.sh
config.json
Error