Max! Cube kein Verbindung nach Update

  • Hallo,


    nach dem Update auf homebridge-config-ui-x v4.13.2 kann ich keine Verbindung zum Max! Cube herstellen. Weiß jemand was schief gelaufen ist? Hier das Protokoll:


    Loading logs using "custom" method...

    CMD: journalctl -o cat -n 500 -f -u homebridge


    Started Node.js HomeKit Server.

    [3/30/2020, 16:44:27] Loaded config.json with 0 accessories and 2 platforms.

    [3/30/2020, 16:44:27] ---

    [3/30/2020, 16:44:28] Loaded plugin: homebridge-config-ui-x

    [3/30/2020, 16:44:28] Registering platform 'homebridge-config-ui-x.config'

    [3/30/2020, 16:44:28] ---

    [3/30/2020, 16:44:28] Loaded plugin: homebridge-platform-maxcube

    [3/30/2020, 16:44:28] Registering platform 'homebridge-platform-maxcube.MaxCubePlatform'

    [3/30/2020, 16:44:28] ---

    [3/30/2020, 16:44:28] Loading 2 platforms...

    [3/30/2020, 16:44:28] [Config] Initializing config platform...

    [3/30/2020, 16:44:28] [Config] Spawning homebridge-config-ui-x with PID 426

    [3/30/2020, 16:44:28] [MaxCube Platform] Initializing MaxCubePlatform platform...

    [3/30/2020, 16:44:28] [MaxCube Platform] Try connecting to Max! Cube..

    [3/30/2020, 16:44:28] Loading 0 accessories...

    Error: connect ENETUNREACH 192.168.178.21:62910 - Local (0.0.0.0:0)

    at internalConnect (net.js:917:16)

    at defaultTriggerAsyncIdScope (internal/async_hooks.js:311:12)

    at net.js:1007:9

    at processTicksAndRejections (internal/process/task_queues.js:79:11) {

    errno: 'ENETUNREACH',

    code: 'ENETUNREACH',

    syscall: 'connect',

    address: '192.168.178.21',

    port: 62910

    }

    [3/30/2020, 16:44:28] [MaxCube Platform] Max! Cube could not be found, please restart HomeBridge with Max! Cube connected.

    [3/30/2020, 16:44:28] [MaxCube Platform] Max! Cube connection closed.

    [3/30/2020, 16:44:34] [Config] Homebridge Config UI X v4.13.0 is listening on :: port 8080

    [3/30/2020, 16:58:49] [Config] Running Command: sudo -E -n npm install [email protected]

    homebridge : TTY=pts/0 ; PWD=/usr/local/lib ; USER=root ; COMMAND=/usr/local/bin/npm install [email protected]

    pam_unix(sudo:session): session opened for user root by (uid=0)

    pam_unix(sudo:session): session closed for user root

    [3/30/2020, 17:01:37] [Config] Homebridge restart request received

    [3/30/2020, 17:01:37] [Config] Executing restart command: sudo -n systemctl restart homebridge

    homebridge : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/bin/systemctl restart homebridge

    pam_unix(sudo:session): session opened for user root by (uid=0)

    Stopping Node.js HomeKit Server...

    [3/30/2020, 17:01:37] Got SIGTERM, shutting down Homebridge...

    homebridge.service: Main process exited, code=exited, status=143/n/a

    homebridge.service: Failed with result 'exit-code'.

    Stopped Node.js HomeKit Server.

    homebridge.service: Found left-over process 426 (homebridge-conf) in control group while starting unit. Ignoring.

    This usually indicates unclean termination of a previous run, or service implementation deficiencies.

    homebridge.service: Found left-over process 820 (sh) in control group while starting unit. Ignoring.

    This usually indicates unclean termination of a previous run, or service implementation deficiencies.

    homebridge.service: Found left-over process 821 (sudo) in control group while starting unit. Ignoring.

    This usually indicates unclean termination of a previous run, or service implementation deficiencies.

    homebridge.service: Found left-over process 826 (systemctl) in control group while starting unit. Ignoring.

    This usually indicates unclean termination of a previous run, or service implementation deficiencies.

    Started Node.js HomeKit Server.

    pam_unix(sudo:session): session closed for user root

    [3/30/2020, 17:01:44] Loaded config.json with 0 accessories and 2 platforms.

    [3/30/2020, 17:01:44] ---

    [3/30/2020, 17:01:44] Loaded plugin: homebridge-config-ui-x

    [3/30/2020, 17:01:44] Registering platform 'homebridge-config-ui-x.config'

    [3/30/2020, 17:01:44] ---

    [3/30/2020, 17:01:44] Loaded plugin: homebridge-platform-maxcube

    [3/30/2020, 17:01:44] Registering platform 'homebridge-platform-maxcube.MaxCubePlatform'

    [3/30/2020, 17:01:44] ---

    [3/30/2020, 17:01:44] Loading 2 platforms...

    [3/30/2020, 17:01:44] [Config] Initializing config platform...

    [3/30/2020, 17:01:44] [Config] Spawning homebridge-config-ui-x with PID 852

    [3/30/2020, 17:01:44] [MaxCube Platform] Initializing MaxCubePlatform platform...

    [3/30/2020, 17:01:44] [MaxCube Platform] Try connecting to Max! Cube..

    [3/30/2020, 17:01:44] Loading 0 accessories...

    [3/30/2020, 17:01:49] [Config] Homebridge Config UI X v4.13.2 is listening on :: port 8080

    Error: connect ETIMEDOUT 192.168.178.21:62910

    at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1137:16) {

    errno: 'ETIMEDOUT',

    code: 'ETIMEDOUT',

    syscall: 'connect',

    address: '192.168.178.21',

    port: 62910

    }

    [3/30/2020, 17:02:17] [MaxCube Platform] Max! Cube could not be found, please restart HomeBridge with Max! Cube connected.

    [3/30/2020, 17:02:17] [MaxCube Platform] Max! Cube connection closed.

    [3/30/2020, 17:04:54] [Config] Changes to config.json saved.

    [3/30/2020, 17:05:01] [Config] Homebridge restart request received

    [3/30/2020, 17:05:02] [Config] Executing restart command: sudo -n systemctl restart homebridge

    homebridge : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/bin/systemctl restart homebridge

    pam_unix(sudo:session): session opened for user root by (uid=0)

    Stopping Node.js HomeKit Server...

    [3/30/2020, 17:05:02] Got SIGTERM, shutting down Homebridge...

    homebridge.service: Main process exited, code=exited, status=143/n/a

    homebridge.service: Failed with result 'exit-code'.

    Stopped Node.js HomeKit Server.

    homebridge.service: Found left-over process 852 (homebridge-conf) in control group while starting unit. Ignoring.

    This usually indicates unclean termination of a previous run, or service implementation deficiencies.

    homebridge.service: Found left-over process 1046 (sh) in control group while starting unit. Ignoring.

    This usually indicates unclean termination of a previous run, or service implementation deficiencies.

    homebridge.service: Found left-over process 1047 (sudo) in control group while starting unit. Ignoring.

    This usually indicates unclean termination of a previous run, or service implementation deficiencies.

    homebridge.service: Found left-over process 1052 (systemctl) in control group while starting unit. Ignoring.

    This usually indicates unclean termination of a previous run, or service implementation deficiencies.

    Started Node.js HomeKit Server.

    pam_unix(sudo:session): session closed for user root

    [3/30/2020, 17:05:09] Loaded config.json with 0 accessories and 2 platforms.

    [3/30/2020, 17:05:09] ---

    [3/30/2020, 17:05:09] Loaded plugin: homebridge-config-ui-x

    [3/30/2020, 17:05:09] Registering platform 'homebridge-config-ui-x.config'

    [3/30/2020, 17:05:09] ---

    [3/30/2020, 17:05:09] Loaded plugin: homebridge-platform-maxcube

    [3/30/2020, 17:05:09] Registering platform 'homebridge-platform-maxcube.MaxCubePlatform'

    [3/30/2020, 17:05:09] ---

    [3/30/2020, 17:05:09] Loading 2 platforms...

    [3/30/2020, 17:05:09] [Config] Initializing config platform...

    [3/30/2020, 17:05:09] [Config] Spawning homebridge-config-ui-x with PID 1076

    [3/30/2020, 17:05:09] [MaxCube Platform] Initializing MaxCubePlatform platform...

    [3/30/2020, 17:05:09] [MaxCube Platform] Try connecting to Max! Cube..

    [3/30/2020, 17:05:09] Loading 0 accessories...

    Error: connect ECONNREFUSED 192.168.178.20:62910

    at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1137:16) {

    errno: 'ECONNREFUSED',

    code: 'ECONNREFUSED',

    syscall: 'connect',

    address: '192.168.178.20',

    port: 62910

    }

    [3/30/2020, 17:05:09] [MaxCube Platform] Max! Cube could not be found, please restart HomeBridge with Max! Cube connected.

    [3/30/2020, 17:05:09] [MaxCube Platform] Max! Cube connection closed.

    [3/30/2020, 17:05:13] [Config] Homebridge Config UI X v4.13.2 is listening on :: port 8080


    Danke,

    Stephan

  • Hi, habe die Verbindung um Max! Cube wieder herstellen können. In der Config war eine falsche IP-Adresse eingetragen. Jetzt läuft es wieder. Das Protokoll zeigt aber folgendes:


    [3/30/2020, 17:52:53] [Config] Homebridge restart request received

    [3/30/2020, 17:52:54] [Config] Executing restart command: sudo -n systemctl restart homebridge

    homebridge : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/bin/systemctl restart homebridge

    pam_unix(sudo:session): session opened for user root by (uid=0)

    Stopping Node.js HomeKit Server...

    [3/30/2020, 17:52:54] Got SIGTERM, shutting down Homebridge...

    [3/30/2020, 17:52:58] [MaxCube Platform] Thermostat 1 (Lena) - received new temperature 22.1

    homebridge.service: Main process exited, code=exited, status=143/n/a

    homebridge.service: Failed with result 'exit-code'.

    Stopped Node.js HomeKit Server.

    homebridge.service: Found left-over process 4372 (homebridge-conf) in control group while starting unit. Ignoring.

    This usually indicates unclean termination of a previous run, or service implementation deficiencies.

    homebridge.service: Found left-over process 4503 (sh) in control group while starting unit. Ignoring.

    This usually indicates unclean termination of a previous run, or service implementation deficiencies.

    homebridge.service: Found left-over process 4504 (sudo) in control group while starting unit. Ignoring.

    This usually indicates unclean termination of a previous run, or service implementation deficiencies.

    homebridge.service: Found left-over process 4509 (systemctl) in control group while starting unit. Ignoring.

    This usually indicates unclean termination of a previous run, or service implementation deficiencies.

    homebridge.service: Found left-over process 4510 (journalctl) in control group while starting unit. Ignoring.

    This usually indicates unclean termination of a previous run, or service implementation deficiencies.

    Started Node.js HomeKit Server.

    pam_unix(sudo:session): session closed for user root

    [3/30/2020, 17:53:00] Loaded config.json with 0 accessories and 2 platforms.

    [3/30/2020, 17:53:00] ---

    [3/30/2020, 17:53:01] Loaded plugin: homebridge-config-ui-x

    [3/30/2020, 17:53:01] Registering platform 'homebridge-config-ui-x.config'

    [3/30/2020, 17:53:01] ---

    [3/30/2020, 17:53:01] Loaded plugin: homebridge-platform-maxcube

    [3/30/2020, 17:53:01] Registering platform 'homebridge-platform-maxcube.MaxCubePlatform'

    [3/30/2020, 17:53:01] ---

    [3/30/2020, 17:53:01] Loading 2 platforms...

    [3/30/2020, 17:53:01] [Config] Initializing config platform...

    [3/30/2020, 17:53:01] [Config] Spawning homebridge-config-ui-x with PID 4535

    [3/30/2020, 17:53:01] [MaxCube Platform] Initializing MaxCubePlatform platform...

    [3/30/2020, 17:53:01] [MaxCube Platform] Try connecting to Max! Cube..

    [3/30/2020, 17:53:01] Loading 0 accessories...

    [3/30/2020, 17:53:01] [MaxCube Platform] Connected to Max! Cube.

    [3/30/2020, 17:53:02] [MaxCube Platform] Initializing platform accessory 'Max! Link'...

    [3/30/2020, 17:53:02] [MaxCube Platform] Initializing platform accessory 'Thermostat 1 (Lena)'...

    [3/30/2020, 17:53:02] [MaxCube Platform] Initializing platform accessory 'Zwischenstecker 1 (Fernseher)'...

    [3/30/2020, 17:53:02] [MaxCube Platform] Initializing platform accessory 'Thermostat 1 (Flur)'...

    [3/30/2020, 17:53:02] [MaxCube Platform] Initializing platform accessory 'Thermostat 1 (Esszimmer)'...

    [3/30/2020, 17:53:02] [MaxCube Platform] Initializing platform accessory 'Wandthermostat 1 (Sarah)'...

    [3/30/2020, 17:53:02] [MaxCube Platform] Initializing platform accessory 'Thermostat 2 (Schlafzimmer)'...

    [3/30/2020, 17:53:02] [MaxCube Platform] Initializing platform accessory 'Thermostat 1 (Küche)'...

    [3/30/2020, 17:53:02] [MaxCube Platform] Initializing platform accessory 'Thermostat 1 (Büro)'...

    [3/30/2020, 17:53:02] [MaxCube Platform] Initializing platform accessory 'Thermostat 1 (Wohnzimmer)'...

    [3/30/2020, 17:53:02] [MaxCube Platform] Initializing platform accessory 'Thermostat 1 (Bad)'...

    [3/30/2020, 17:53:02] [MaxCube Platform] Initializing platform accessory 'Thermostat Sarah (Sarah)'...

    [3/30/2020, 17:53:02] [MaxCube Platform] Initializing platform accessory 'Zwischenstecker 2 (Gäste-WC)'...

    [3/30/2020, 17:53:02] [MaxCube Platform] Initializing platform accessory 'Wandthermostat 1 (Lena)'...

    [3/30/2020, 17:53:02] [MaxCube Platform] Initializing platform accessory 'Wandthermostat (Bad)'...

    [3/30/2020, 17:53:02] [MaxCube Platform] Initializing platform accessory 'Fensterkontakt Bad (Bad)'...

    Setup Payload:

    X-HM://0023ISYWY27M7

    Scan this code with your HomeKit app on your iOS device to pair with Homebridge:


    Muss ich etwas unternehmen um die Left-over Einträge loszuwerden?

    Danke

  • Bei Github gibt es ein Issue mit dem selben Thema.

    https://github.com/oznu/homebridge-config-ui-x/issues/538


    Und der Hinweis von oznu


    oznu commented on 12 Feb

    The UI will terminate itself immediately after the Homebridge process exits; but systemd is probably checking before this happens hence the warning.

    You can safely ignore this warning. The logs confirm the UI is terminating correctly as it spawns and binds to port 8083 after the restart - if the UI process was still running you would get a port in use error.


    If this really bugs you, you can tell the UI to run in the same Node.js process as Homebridge using this config option: https://github.com/oznu/homebr…iki/Config-Options#nofork I would not recommend this however.
  • Muss ich etwas unternehmen um die Left-over Einträge loszuwerden?

    Ignoriere sie.