Closed glowfishDE closed 4 years ago
My docker totally crapped out as well. Not sure if this was the result of the push 4 days ago or not. Don't use it much so just noticed the issue today. Trying to restart the docker container now and I just get an error message. I'm running it on an openmediavault box using Debian. Not sure what I will try next, maybe copying the config, deleting the entire container and re-creating it.
i wanted to try re-creating the whole container too.. but then.. when i did this 4 weeks ago to build it with the latest Node.JS Version, i had to drop my whole Homekit Bridge from the iPhone / iCloud and re-create all rooms and settings.. Having over ~85 Items in it, it is no fun to re-arrange all that again.. takes hours..so i hope my homebridge can be re-vived somehow..
The logs show this is an issue with your Nest token.
I would also recommend raising an issue with the Nest plugin, a failed auth token shouldn't be blocking the rest of Homebridge loading (yet it is).
I can confirm it has to do with the Nest Plugin - i removed the Nest Part from config.json and homebridge starts again.
Thanks for pointing me into the right direction.
As you say Oznu, the rest of the homebridge startup should not be blocked because of the Nest Plugin not being able to auth with its google token properly. I will raise this to the Nest Plugin Dev(s).
Describe Your Problem: Logging into the homebridge-config-ui-x i get a red box saying "Homebridge not running" suddenly after i restarted the whole docker environment:
As you can see from the screenshots, the homebridge process seems to be running, but the UI says it isnt. Also i cannot reach the homebridge from my iphone/ipad.
It just worked until this morning. This setup was working 100% for months. I did a killall -9 homebridge which restarted everything. But still i got the google auth error as well as the "homebridge is NOT running" sign.
Logs:
Docker Start Command:
Homebridge Config:
Screenshots:
Environment: