search

homebridge / docker-homebridge

Homebridge Docker. HomeKit support for the impatient using Docker on x86_64, Raspberry Pi (armhf) and ARM64. Includes ffmpeg + libfdk-aac.
https://hub.docker.com/r/homebridge/homebridge/
GNU General Public License v3.0
2.58k stars 241 forks source link

Homebridge Config Ui-X says "homebridge not running" / Nest API complains about unsuccessfull auth #285

Closed glowfishDE closed 4 years ago

glowfishDE commented 4 years ago

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:

image

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:

[4/6/2020, 4:17:41 PM] Loaded config.json with 0 accessories and 3 platforms.
[4/6/2020, 4:17:41 PM] ---
[4/6/2020, 4:17:41 PM] Loaded plugin: homebridge-dummy
[4/6/2020, 4:17:41 PM] Registering accessory 'homebridge-dummy.DummySwitch'
[4/6/2020, 4:17:41 PM] ---
[4/6/2020, 4:17:41 PM] Loaded plugin: homebridge-fritz
[4/6/2020, 4:17:41 PM] Registering platform 'homebridge-fritz.Fritz!Box'
[4/6/2020, 4:17:41 PM] ---
[4/6/2020, 4:17:41 PM] Loaded plugin: homebridge-homematic
[4/6/2020, 4:17:41 PM] Registering platform 'homebridge-homematic.HomeMatic'
[4/6/2020, 4:17:41 PM] ---
[4/6/2020, 4:17:41 PM] Loaded plugin: homebridge-nest
[4/6/2020, 4:17:41 PM] Registering platform 'homebridge-nest.Nest'
[4/6/2020, 4:17:41 PM] ---
[4/6/2020, 4:17:41 PM] Loaded plugin: homebridge-config-ui-x
[4/6/2020, 4:17:41 PM] Registering platform 'homebridge-config-ui-x.config'
[4/6/2020, 4:17:41 PM] ---
[4/6/2020, 4:17:41 PM] Loading 3 platforms...
[4/6/2020, 4:17:41 PM] [HomeMatic CCU2] Initializing HomeMatic platform...
[4/6/2020, 4:17:41 PM] [HomeMatic CCU2] [Core] merging configurations
[4/6/2020, 4:17:41 PM] [HomeMatic CCU2] Homematic Plugin Version 0.0.219
[4/6/2020, 4:17:41 PM] [HomeMatic CCU2] Plugin by thkl  https://github.com/thkl
[4/6/2020, 4:17:41 PM] [HomeMatic CCU2] Homematic is a registered trademark of the EQ-3 AG
[4/6/2020, 4:17:41 PM] [HomeMatic CCU2] Please report any issues to https://github.com/thkl/homebridge-homematic/issues
[4/6/2020, 4:17:41 PM] [HomeMatic CCU2] running in production mode
[4/6/2020, 4:17:41 PM] [HomeMatic CCU2] will connect to your ccu at 192.168.1.10
[4/6/2020, 4:17:41 PM] [HomeMatic CCU2] IMPORTANT !! Starting this version, your homematic custom configuration is located in /homebridge/homematic_config.json
[4/6/2020, 4:17:41 PM] [HomeMatic CCU2] [RPC] using xmprpc for communication with BidCos-RF
[4/6/2020, 4:17:41 PM] [HomeMatic CCU2] init RPC for BidCos-RF.
[4/6/2020, 4:17:41 PM] [HomeMatic CCU2] [RPC] local ip used : 192.168.1.149. you may change that with local_ip parameter in config
[4/6/2020, 4:17:41 PM] [HomeMatic CCU2] init RPC for VirtualDevices.
[4/6/2020, 4:17:42 PM] [HomeMatic CCU2] [RPC] local ip used : 192.168.1.149. you may change that with local_ip parameter in config
[4/6/2020, 4:17:42 PM] [HomeMatic CCU2] init RPC for HmIP-RF.
[4/6/2020, 4:17:42 PM] [HomeMatic CCU2] [RPC] local ip used : 192.168.1.149. you may change that with local_ip parameter in config
[4/6/2020, 4:17:42 PM] [FritzBox 7590] Initializing Fritz!Box platform...
[4/6/2020, 4:17:42 PM] [Nest] Initializing Nest platform...
[4/6/2020, 4:17:42 PM] [Nest] Fetching Nest devices.
[4/6/2020, 4:17:42 PM] Loading 0 accessories...
[4/6/2020, 4:17:42 PM] [HomeMatic CCU2] [RPC] server for interface BidCos-RF. is listening on port 9090.
[4/6/2020, 4:17:42 PM] [HomeMatic CCU2] [RPC] Creating Local HTTP Client for CCU RPC Events
[4/6/2020, 4:17:42 PM] [HomeMatic CCU2] [RPC] server for interface VirtualDevices. is listening on port 9093.
[4/6/2020, 4:17:42 PM] [HomeMatic CCU2] [RPC] Creating Local HTTP Client for CCU RPC Events
[4/6/2020, 4:17:42 PM] [HomeMatic CCU2] [RPC] server for interface HmIP-RF. is listening on port 9092.
[4/6/2020, 4:17:42 PM] [HomeMatic CCU2] [RPC] Creating Local HTTP Client for CCU RPC Events
[4/6/2020, 4:17:42 PM] [HomeMatic CCU2] if PONG is PONG CCU is alive
[4/6/2020, 4:17:43 PM] [HomeMatic CCU2] Adding DoorBell as Motion Sensor
[4/6/2020, 4:17:43 PM] [HomeMatic CCU2] Initializing platform accessory 'Window Room 1'...
...
...
...
[4/6/2020, 4:17:43 PM] [Nest] Google authentication was unsuccessful. Make sure you did not log out of your Google account after getting your googleAuth parameters.
[4/6/2020, 4:17:43 PM] [Nest] Access token acquisition via googleAuth failed (code undefined).
[4/6/2020, 4:17:43 PM] [HomeMatic CCU2] [Core] will cache ccu response to /homebridge/ccu.json
[4/6/2020, 4:17:44 PM] [FritzBox 7590] Fritz!Box platform login successful
[4/6/2020, 4:17:44 PM] [FritzBox 7590] Discovering accessories
[4/6/2020, 4:17:44 PM] [FritzBox 7590] Using tr64 api for guest Wifi
[4/6/2020, 4:17:45 PM] [FritzBox 7590] Updating guest WLAN
[4/6/2020, 4:17:45 PM] [HomeMatic CCU2] Unable to fetch new versions
[4/6/2020, 4:17:45 PM] [HomeMatic CCU2] [Core] NPM 0.0.219 vs Local 0.0.219
[4/6/2020, 4:17:47 PM] [FritzBox 7590] Alarm sensors found: none
[4/6/2020, 4:17:47 PM] [FritzBox 7590] Buttons found: none
[4/6/2020, 4:17:47 PM] [FritzBox 7590] Outlets found: 012345678901,xxxxxxxxxxxxx
[4/6/2020, 4:17:47 PM] [FritzBox 7590] Updating outlet 012345678901
[4/6/2020, 4:17:47 PM] [FritzBox 7590] Updating outlet xxxxxxxxxxxx

Docker Start Command:

I run the docker container in a synolgoy environment:

See screenshots below.

Homebridge Config:

{
    "bridge": {
        "name": "Homebridge",
        "username": "AA:BB:CC:EE:FF:DD",
        "port": 51826,
        "pin": "123-456-789"
    },
    "accessories": [],
    "platforms": [
        {
            "platform": "HomeMatic",
            "name": "HomeMatic CCU2",
            "ccu_ip": "192.168.1.10",
            "enable_hmip": "true",
            "filter_device": [],
            "filter_channel": [],
            "outlets": [
                "BidCos-RF.12345678:1"
            ],
            "doors": [
                "BidCos-RF.74343583:4"
            ],
            "windows": [],
            "switches": [],
            "RotaryHandles": [],
            "WindowContacts": [],
            "SmokeDetector": [],
            "programs": [
                "OpenDoor"
            ],
            "ios10": true,
            "variables": [],
            "subsection": "Homekit",
            "special": [
                {
                    "name": "Garagedoor",
                    "type": "HM-THKL-GARAGEDOOR",
                    "parameter": {
                        "address_sensor_close": "BidCos-RF.2222222:1.STATE",
                        "state_sensor_close": false,
                        "state_sensor_open": true,
                        "address_actor_open": "HmIP-RF.333333333:3.STATE",
                        "message_actor_open": {
                            "on": true,
                            "off": false
                        }
                    }
                }
            ],
            "services": [
                {
                    "type": "HM-THKL-GARAGEDOOR",
                    "service": "HomeMaticHomeKitGarageDoorService"
                }
            ]
        },
        {
            "platform": "Fritz!Box",
            "name": "FritzBox 7590",
            "username": "username",
            "password": "password,
            "url": "http://fritz.box",
            "interval": 60,
            "options": {
                "strictSSL": false
            }
        },
        {
            "name": "Nest",
            "googleAuth": {
                "issueToken": "https://accounts.google.com/o/oauth2/iframerpc?action=issueToken&response_type=token%20id_token&login_hint=redacted-redacted&client_id=redactedrq.apps.googleusercontent.com&origin=https%3A%2F%2Fhome.nest.com&scope=openid%20profile%20email%20https%3A%2F%2Fwww.googleapis.com%2Fauth%2Fnest-account&ss_domain=https%3A%2F%2Fhome.nest.com",
                "cookies": "OCAK=redacted; SID=redacted; __Secure-redacted.; HSID=redacted; SSID=redacted; APISID=redacted; SAPISID=redacted; __Secure-HSID=redacted; __Secure-SSID=redacted; __Secure-APISID=redacted; __Secure-3PAPISID=redacted; ACCOUNT_CHOOSER=redacted; NID=redacted; CONSENT=YES+redacted; GAPS=1:redacted; LSID=lso|s.DE|s.youtube:redacted.; __Host-3PLSID=lso|s.redacted|s.youtube:redacted.; SIDCC=redacted",
                "apiKey": "redacted"
            },
            "platform": "Nest"
        }
    ]
}

Screenshots:

image

image

Environment:

bdpna commented 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.

glowfishDE commented 4 years ago

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..

oznu commented 4 years ago

The logs show this is an issue with your Nest token.

oznu commented 4 years ago

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).

glowfishDE commented 4 years ago

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).