Navigation

    Logo
    • Register
    • Login
    • Search
    • Recent
    • Tags
    • Unread
    • Categories
    • Unreplied
    • Popular
    • GitHub
    • Docu
    • Hilfe
    1. Home
    2. Deutsch
    3. ioBroker Allgemein
    4. Verbindung zu iobroker fehlgeschlagen?

    NEWS

    • ioBroker@Smart Living Forum Solingen, 14.06. - Agenda added

    • ioBroker goes Matter ... Matter Adapter in Stable

    • Monatsrückblick - April 2025

    Verbindung zu iobroker fehlgeschlagen?

    This topic has been deleted. Only users with topic management privileges can see it.
    • D
      daniel1to @apollon77 last edited by

      @apollon77

      2019-08-18 07:20:49.980  - warn: hue.0 could not connect to HUE bridge (192.168.178.38:80)
      2019-08-18 07:20:49.980  - error: hue.0 Error: connect EHOSTUNREACH 192.168.178.38:80
      2019-08-18 07:20:50.014  - error: info.0 Error: getaddrinfo ENOTFOUND raw.githubusercontent.com raw.githubusercontent.com:443
      2019-08-18 07:20:50.785  - warn: info.0 Reconnection to DB.
      2019-08-18 07:20:50.788  - warn: info.0 Reconnection to DB.
      2019-08-18 07:20:50.805  - info: info.0 starting. Version 1.3.7 in C:/Program Files/iobroker/SmartHome/node_modules/iobroker.info, node: v10.16.0
      2019-08-18 07:20:50.807  - warn: discovery.0 Reconnection to DB.
      2019-08-18 07:20:50.812  - warn: discovery.0 Reconnection to DB.
      2019-08-18 07:20:50.815  - info: discovery.0 starting. Version 1.3.0 in C:/Program Files/iobroker/SmartHome/node_modules/iobroker.discovery, node: v10.16.0
      2019-08-18 07:20:50.825  - info: discovery.0 starting. Version 1.3.0 in C:/Program Files/iobroker/SmartHome/node_modules/iobroker.discovery, node: v10.16.0
      2019-08-18 07:20:51.200  - warn: admin.0 Reconnection to DB.
      2019-08-18 07:20:51.204  - warn: admin.0 Reconnection to DB.
      2019-08-18 07:20:51.212  - info: admin.0 starting. Version 3.6.2 in C:/Program Files/iobroker/SmartHome/node_modules/iobroker.admin, node: v10.16.0
      2019-08-18 07:20:51.212  - warn: hue.0 Reconnection to DB.
      2019-08-18 07:20:51.214  - warn: hue.0 Reconnection to DB.
      2019-08-18 07:20:51.226  - info: hue.0 starting. Version 1.2.3 in C:/Program Files/iobroker/SmartHome/node_modules/iobroker.hue, node: v10.16.0
      2019-08-18 07:20:51.233  - info: admin.0 starting. Version 3.6.2 in C:/Program Files/iobroker/SmartHome/node_modules/iobroker.admin, node: v10.16.0
      2019-08-18 07:20:51.247  - warn: hue.0 could not connect to HUE bridge (192.168.178.38:80)
      2019-08-18 07:20:51.247  - error: hue.0 Error: connect EHOSTUNREACH 192.168.178.38:80
      2019-08-18 07:20:51.255  - info: hue.0 starting. Version 1.2.3 in C:/Program Files/iobroker/SmartHome/node_modules/iobroker.hue, node: v10.16.0
      2019-08-18 07:20:51.261  - info: admin.0 requesting all states
      2019-08-18 07:20:51.261  - info: admin.0 requesting all objects
      2019-08-18 07:20:51.262  - info: admin.0 Request actual repository...
      2019-08-18 07:20:51.266  - info: admin.0 requesting all states
      2019-08-18 07:20:51.266  - info: admin.0 requesting all objects
      2019-08-18 07:20:51.266  - info: admin.0 Request actual repository...
      2019-08-18 07:20:51.267  - warn: hue.0 could not connect to HUE bridge (192.168.178.38:80)
      2019-08-18 07:20:51.267  - error: hue.0 Error: connect EHOSTUNREACH 192.168.178.38:80
      2019-08-18 07:20:51.430  - warn: knx.0 Reconnection to DB.
      2019-08-18 07:20:51.434  - warn: web.0 Reconnection to DB.
      2019-08-18 07:20:51.515  - warn: knx.0 Reconnection to DB.
      2019-08-18 07:20:51.508  - warn: web.0 Reconnection to DB.
      2019-08-18 07:20:51.540  - info: admin.0 received all states
      2019-08-18 07:20:51.536  - info: knx.0 starting. Version 0.8.6 in C:/Program Files/iobroker/SmartHome/node_modules/iobroker.knx, node: v10.16.0
      2019-08-18 07:20:51.545  - info: knx.0 Connecting to knx GW:  192.168.178.60:3671   with phy. Adr:  1.1.250 and SendDelay of : 50 ms
      2019-08-18 07:20:51.545  - info: knx.0 C:/Program Files/iobroker/SmartHome/node_modules/iobroker.js-controller
      2019-08-18 07:20:51.567  - error: knx.0 uncaught exception: Cannot read property 'address' of undefined
      2019-08-18 07:20:51.567  - error: knx.0 TypeError: Cannot read property 'address' of undefined
          at fsm.getLocalAddress (C:\Program Files\iobroker\SmartHome\node_modules\iobroker.knx\lib\knx-mod\src\FSM.js:356:71)
          at fsm.IpTunnelingConnection.instance.Connect (C:\Program Files\iobroker\SmartHome\node_modules\iobroker.knx\lib\knx-mod\src\IpTunnelingConnection.js:31:30)
          at Object.Connection (C:\Program Files\iobroker\SmartHome\node_modules\iobroker.knx\lib\knx-mod\src\Connection.js:302:36)
          at t (C:\Program Files\iobroker\SmartHome\node_modules\iobroker.knx\knx.js:1:3676)
          at Socket.<anonymous> (C:\Program Files\iobroker\SmartHome\node_modules\iobroker.knx\knx.js:1:9733)
          at Socket.onack (C:\Program Files\iobroker\SmartHome\node_modules\socket.io-client\lib\socket.js:312:9)
          at Socket.onpacket (C:\Program Files\iobroker\SmartHome\node_modules\socket.io-client\lib\socket.js:236:12)
          at Manager.<anonymous> (C:\Program Files\iobroker\SmartHome\node_modules\component-bind\index.js:21:15)
          at Manager.Emitter.emit (C:\Program Files\iobroker\SmartHome\node_modules\socket.io-client\node_modules\component-emitter\index.js:133:20)
          at Manager.ondecoded (C:\Program Files\iobroker\SmartHome\node_modules\socket.io-client\lib\manager.js:332:8)
      2019-08-18 07:20:51.565  - info: info.0 Reading CPU current speed every 3 seconds.
      2019-08-18 07:20:51.566  - info: info.0 Reading CPU data every 3 seconds.
      2019-08-18 07:20:51.569  - error: info.0 Error: getaddrinfo ENOTFOUND raw.githubusercontent.com raw.githubusercontent.com:443
      2019-08-18 07:20:51.574  - info: info.0 Reading user data every 8 seconds.
      2019-08-18 07:20:51.610  - info: info.0 starting. Version 1.3.7 in C:/Program Files/iobroker/SmartHome/node_modules/iobroker.info, node: v10.16.0
      2019-08-18 07:20:51.647  - error: Caught by controller[0]: TypeError: Cannot read property 'address' of undefined
      2019-08-18 07:20:51.647  - error: Caught by controller[0]:     at fsm.getLocalAddress (C:\Program Files\iobroker\SmartHome\node_modules\iobroker.knx\lib\knx-mod\src\FSM.js:356:71)
      2019-08-18 07:20:51.647  - error: Caught by controller[0]:     at fsm.IpTunnelingConnection.instance.Connect (C:\Program Files\iobroker\SmartHome\node_modules\iobroker.knx\lib\knx-mod\src\IpTunnelingConnection.js:31:30)
      2019-08-18 07:20:51.647  - error: Caught by controller[0]:     at Object.Connection (C:\Program Files\iobroker\SmartHome\node_modules\iobroker.knx\lib\knx-mod\src\Connection.js:302:36)
      2019-08-18 07:20:51.647  - error: Caught by controller[0]:     at t (C:\Program Files\iobroker\SmartHome\node_modules\iobroker.knx\knx.js:1:3676)
      2019-08-18 07:20:51.647  - error: Caught by controller[0]:     at Socket.<anonymous> (C:\Program Files\iobroker\SmartHome\node_modules\iobroker.knx\knx.js:1:9733)
      2019-08-18 07:20:51.647  - error: Caught by controller[0]:     at Socket.onack (C:\Program Files\iobroker\SmartHome\node_modules\socket.io-client\lib\socket.js:312:9)
      2019-08-18 07:20:51.647  - error: Caught by controller[0]:     at Socket.onpacket (C:\Program Files\iobroker\SmartHome\node_modules\socket.io-client\lib\socket.js:236:12)
      2019-08-18 07:20:51.647  - error: Caught by controller[0]:     at Manager.<anonymous> (C:\Program Files\iobroker\SmartHome\node_modules\component-bind\index.js:21:15)
      2019-08-18 07:20:51.647  - error: Caught by controller[0]:     at Manager.Emitter.emit (C:\Program Files\iobroker\SmartHome\node_modules\socket.io-client\node_modules\component-emitter\index.js:133:20)
      2019-08-18 07:20:51.647  - error: Caught by controller[0]:     at Manager.ondecoded (C:\Program Files\iobroker\SmartHome\node_modules\socket.io-client\lib\manager.js:332:8)
      2019-08-18 07:20:51.647  - error: host.DESKTOP-GFRKJ98(SmartHome) instance system.adapter.knx.0 terminated with code 0 (OK)
      2019-08-18 07:20:51.647  - info: host.DESKTOP-GFRKJ98(SmartHome) Restart adapter system.adapter.knx.0 because enabled
      2019-08-18 07:20:51.645  - info: web.0 starting. Version 2.4.1 in C:/Program Files/iobroker/SmartHome/node_modules/iobroker.web, node: v10.16.0
      2019-08-18 07:20:51.697  - info: web.0 starting. Version 2.4.1 in C:/Program Files/iobroker/SmartHome/node_modules/iobroker.web, node: v10.16.0
      2019-08-18 07:20:51.785  - info: web.0 socket.io server listening on port 8082
      2019-08-18 07:20:51.789  - info: web.0 socket.io server listening on port 8082
      2019-08-18 07:20:51.832  - info: admin.0 received all objects
      2019-08-18 07:20:51.890  - error: web.0 port 8082 already in use
      2019-08-18 07:20:51.923  - info: admin.0 received all states
      2019-08-18 07:20:51.960  - error: admin.0 port 8081 already in use
      2019-08-18 07:20:52.001  - error: host.DESKTOP-GFRKJ98(SmartHome) instance system.adapter.web.0 terminated with code 1 ()
      2019-08-18 07:20:52.001  - info: host.DESKTOP-GFRKJ98(SmartHome) Restart adapter system.adapter.web.0 because enabled
      2019-08-18 07:20:52.076  - error: host.DESKTOP-GFRKJ98(SmartHome) instance system.adapter.admin.0 terminated by request of the instance itself and will not be restarted, before user restarts it.
      2019-08-18 07:20:52.076  - info: host.DESKTOP-GFRKJ98(SmartHome) Do not restart adapter system.adapter.admin.0 because desired by instance
      2019-08-18 07:20:52.281  - info: info.0 Reading CPU current speed every 3 seconds.
      2019-08-18 07:20:52.281  - info: info.0 Reading CPU data every 3 seconds.
      2019-08-18 07:20:52.287  - error: info.0 Error: getaddrinfo ENOTFOUND raw.githubusercontent.com raw.githubusercontent.com:443
      2019-08-18 07:20:52.414  - info: info.0 Reading memory data every 3 seconds.
      2019-08-18 07:20:52.573  - info: info.0 Reading user data every 8 seconds.
      2019-08-18 07:20:52.815  - info: info.0 Reading disk data every 8 seconds.
      2019-08-18 07:20:53.690  - info: info.0 Reading memory data every 3 seconds.
      2019-08-18 07:20:53.691  - info: info.0 Reading disk data every 8 seconds.
      2019-08-18 07:20:53.933  - info: info.0 Reading battery data every 8 seconds.
      2019-08-18 07:20:54.032  - info: info.0 Reading process data every 8 seconds.
      2019-08-18 07:20:54.069  - info: info.0 Reading process data every 8 seconds.
      2019-08-18 07:20:54.310  - info: info.0 Reading battery data every 8 seconds.
      2019-08-18 07:20:55.230  - warn: hue.0 could not connect to HUE bridge (192.168.178.38:80)
      2019-08-18 07:20:55.230  - error: hue.0 Api Error: method, GET, not available for resource, /
      2019-08-18 07:20:56.468  - warn: hue.0 could not connect to HUE bridge (192.168.178.38:80)
      2019-08-18 07:20:56.468  - error: hue.0 Api Error: method, GET, not available for resource, /
      2019-08-18 07:20:56.468  - warn: hue.0 could not connect to HUE bridge (192.168.178.38:80)
      2019-08-18 07:20:56.468  - error: hue.0 Api Error: method, GET, not available for resource, /
      2019-08-18 07:21:00.336  - warn: hue.0 could not connect to HUE bridge (192.168.178.38:80)
      2019-08-18 07:21:00.336  - error: hue.0 Api Error: method, GET, not available for resource, /
      2019-08-18 07:21:01.629  - warn: hue.0 could not connect to HUE bridge (192.168.178.38:80)
      2019-08-18 07:21:01.629  - error: hue.0 Api Error: method, GET, not available for resource, /
      2019-08-18 07:21:01.629  - warn: hue.0 could not connect to HUE bridge (192.168.178.38:80)
      2019-08-18 07:21:01.629  - error: hue.0 Api Error: method, GET, not available for resource, /
      2019-08-18 07:21:05.435  - warn: hue.0 could not connect to HUE bridge (192.168.178.38:80)
      2019-08-18 07:21:05.435  - error: hue.0 Api Error: method, GET, not available for resource, /
      2019-08-18 07:21:06.770  - warn: hue.0 could not connect to HUE bridge (192.168.178.38:80)
      2019-08-18 07:21:06.770  - error: hue.0 Api Error: method, GET, not available for resource, /
      2019-08-18 07:21:06.770  - warn: hue.0 could not connect to HUE bridge (192.168.178.38:80)
      2019-08-18 07:21:06.770  - error: hue.0 Api Error: method, GET, not available for resource, /
      2019-08-18 07:21:10.552  - warn: hue.0 could not connect to HUE bridge (192.168.178.38:80)
      2019-08-18 07:21:10.552  - error: hue.0 Api Error: method, GET, not available for resource, /
      2019-08-18 07:21:11.914  - warn: hue.0 could not connect to HUE bridge (192.168.178.38:80)
      2019-08-18 07:21:11.914  - error: hue.0 Api Error: method, GET, not available for resource, /
      2019-08-18 07:21:11.914  - warn: hue.0 could not connect to HUE bridge (192.168.178.38:80)
      2019-08-18 07:21:11.914  - error: hue.0 Api Error: method, GET, not available for resource, /
      2019-08-18 07:21:15.703  - warn: hue.0 could not connect to HUE bridge (192.168.178.38:80)
      2019-08-18 07:21:15.703  - error: hue.0 Api Error: method, GET, not available for resource, /
      2019-08-18 07:21:17.073  - warn: hue.0 could not connect to HUE bridge (192.168.178.38:80)
      2019-08-18 07:21:17.073  - error: hue.0 Api Error: method, GET, not available for resource, /
      2019-08-18 07:21:17.074  - warn: hue.0 could not connect to HUE bridge (192.168.178.38:80)
      2019-08-18 07:21:17.074  - error: hue.0 Api Error: method, GET, not available for resource, /
      2019-08-18 07:21:20.802  - warn: hue.0 could not connect to HUE bridge (192.168.178.38:80)
      2019-08-18 07:21:20.803  - error: hue.0 Api Error: method, GET, not available for resource, /
      2019-08-18 07:21:21.655  - info: host.DESKTOP-GFRKJ98(SmartHome) instance system.adapter.knx.0 started with pid 8468
      2019-08-18 07:21:22.012  - info: host.DESKTOP-GFRKJ98(SmartHome) instance system.adapter.web.0 started with pid 21448
      2019-08-18 07:21:22.060  - info: knx.0 starting. Version 0.8.6 in C:/Program Files/iobroker/SmartHome/node_modules/iobroker.knx, node: v10.16.0
      2019-08-18 07:21:22.073  - info: knx.0 Connecting to knx GW:  192.168.178.60:3671   with phy. Adr:  1.1.250 and SendDelay of : 50 ms
      2019-08-18 07:21:22.073  - info: knx.0 C:/Program Files/iobroker/SmartHome/node_modules/iobroker.js-controller
      2019-08-18 07:21:22.111  - info: knx.0  DPP erstellt für : 9/4/33    Schwellwert 2mit DPT1.001
      2019-08-18 07:21:22.111  - info: knx.0  DPP erstellt für : 9/4/32    Schwellwert 1mit DPT1.001
      2019-08-18 07:21:22.132  - info: knx.0 Connected!
      2019-08-18 07:21:22.258  - warn: hue.0 could not connect to HUE bridge (192.168.178.38:80)
      2019-08-18 07:21:22.258  - error: hue.0 Api Error: method, GET, not available for resource, /
      2019-08-18 07:21:22.259  - warn: hue.0 could not connect to HUE bridge (192.168.178.38:80)
      2019-08-18 07:21:22.259  - error: hue.0 Api Error: method, GET, not available for resource, /
      2019-08-18 07:21:22.432  - info: web.0 starting. Version 2.4.1 in C:/Program Files/iobroker/SmartHome/node_modules/iobroker.web, node: v10.16.0
      2019-08-18 07:21:22.557  - info: web.0 socket.io server listening on port 8082
      2019-08-18 07:21:22.558  - info: web.0 http server listening on port 8082
      2019-08-18 07:21:23.808  - info: knx.0  update of actGARefId : P-04A5-0_GA-222     of  knx.0.Wetter.Helligkeit.Schwellwert_2   with value  0
      2019-08-18 07:21:23.910  - info: knx.0  update of actGARefId : P-04A5-0_GA-221     of  knx.0.Wetter.Helligkeit.Schwellwert_1   with value  0
      2019-08-18 07:21:25.898  - warn: hue.0 could not connect to HUE bridge (192.168.178.38:80)
      2019-08-18 07:21:25.898  - error: hue.0 Api Error: method, GET, not available for resource, /
      2019-08-18 07:21:27.404  - warn: hue.0 could not connect to HUE bridge (192.168.178.38:80)
      2019-08-18 07:21:27.404  - error: hue.0 Api Error: method, GET, not available for resource, /
      2019-08-18 07:21:27.404  - warn: hue.0 could not connect to HUE bridge (192.168.178.38:80)
      2019-08-18 07:21:27.404  - error: hue.0 Api Error: method, GET, not available for resource, /
      2019-08-18 07:21:30.995  - warn: hue.0 could not connect to HUE bridge (192.168.178.38:80)
      2019-08-18 07:21:30.995  - error: hue.0 Api Error: method, GET, not available for resource, /
      2019-08-18 07:21:32.534  - warn: hue.0 could not connect to HUE bridge (192.168.178.38:80)
      2019-08-18 07:21:32.534  - error: hue.0 Api Error: method, GET, not available for resource, /
      2019-08-18 07:21:32.534  - warn: hue.0 could not connect to HUE bridge (192.168.178.38:80)
      2019-08-18 07:21:32.534  - error: hue.0 Api Error: method, GET, not available for resource, /
      2019-08-18 07:21:36.090  - warn: hue.0 could not connect to HUE bridge (192.168.178.38:80)
      2019-08-18 07:21:36.090  - error: hue.0 Api Error: method, GET, not available for resource, /
      2019-08-18 07:21:37.684  - warn: hue.0 could not connect to HUE bridge (192.168.178.38:80)
      2019-08-18 07:21:37.684  - error: hue.0 Api Error: method, GET, not available for resource, /
      2019-08-18 07:21:37.684  - warn: hue.0 could not connect to HUE bridge (192.168.178.38:80)
      2019-08-18 07:21:37.684  - error: hue.0 Api Error: method, GET, not available for resource, /
      2019-08-18 07:21:41.197  - warn: hue.0 could not connect to HUE bridge (192.168.178.38:80)
      2019-08-18 07:21:41.197  - error: hue.0 Api Error: method, GET, not available for resource, /
      2019-08-18 07:21:42.840  - warn: hue.0 could not connect to HUE bridge (192.168.178.38:80)
      2019-08-18 07:21:42.840  - error: hue.0 Api Error: method, GET, not available for resource, /
      2019-08-18 07:21:42.840  - warn: hue.0 could not connect to HUE bridge (192.168.178.38:80)
      2019-08-18 07:21:42.840  - error: hue.0 Api Error: method, GET, not available for resource, /
      2019-08-18 07:21:46.310  - warn: hue.0 could not connect to HUE bridge (192.168.178.38:80)
      2019-08-18 07:21:46.310  - error: hue.0 Api Error: method, GET, not available for resource, /
      2019-08-18 07:21:47.990  - warn: hue.0 could not connect to HUE bridge (192.168.178.38:80)
      2019-08-18 07:21:47.990  - error: hue.0 Api Error: method, GET, not available for resource, /
      2019-08-18 07:21:47.991  - warn: hue.0 could not connect to HUE bridge (192.168.178.38:80)
      2019-08-18 07:21:47.991  - error: hue.0 Api Error: method, GET, not available for resource, /
      2019-08-18 07:21:51.535  - warn: hue.0 could not connect to HUE bridge (192.168.178.38:80)
      2019-08-18 07:21:51.535  - error: hue.0 Api Error: method, GET, not available for resource, /
      2019-08-18 07:21:53.427  - warn: hue.0 could not connect to HUE bridge (192.168.178.38:80)
      2019-08-18 07:21:53.427  - error: hue.0 Api Error: method, GET, not available for resource, /
      2019-08-18 07:21:53.428  - warn: hue.0 could not connect to HUE bridge (192.168.178.38:80)
      2019-08-18 07:21:53.428  - error: hue.0 Api Error: method, GET, not available for resource, /
      2019-08-18 07:21:57.113  - warn: hue.0 could not connect to HUE bridge (192.168.178.38:80)
      2019-08-18 07:21:57.113  - error: hue.0 Api Error: method, GET, not available for resource, /
      2019-08-18 07:21:58.781  - warn: hue.0 could not connect to HUE bridge (192.168.178.38:80)
      2019-08-18 07:21:58.781  - error: hue.0 Api Error: method, GET, not available for resource, /
      2019-08-18 07:21:58.839  - warn: hue.0 could not connect to HUE bridge (192.168.178.38:80)
      2019-08-18 07:21:58.839  - error: hue.0 Api Error: method, GET, not available for resource, /
      2019-08-18 07:22:02.216  - warn: hue.0 could not connect to HUE bridge (192.168.178.38:80)
      2019-08-18 07:22:02.216  - error: hue.0 Api Error: method, GET, not available for resource, /
      2019-08-18 07:22:03.937  - warn: hue.0 could not connect to HUE bridge (192.168.178.38:80)
      2019-08-18 07:22:03.937  - error: hue.0 Api Error: method, GET, not available for resource, /
      2019-08-18 07:22:03.938  - warn: hue.0 could not connect to HUE bridge (192.168.178.38:80)
      2019-08-18 07:22:03.938  - error: hue.0 Api Error: method, GET, not available for resource, /
      2019-08-18 07:22:05.697  - warn: knx.0 Value received on unknown GA : 9/4/11
      2019-08-18 07:22:07.300  - warn: hue.0 could not connect to HUE bridge (192.168.178.38:80)
      2019-08-18 07:22:07.300  - error: hue.0 Api Error: method, GET, not available for resource, /
      2019-08-18 07:22:07.711  - warn: knx.0 Value received on unknown GA : 9/4/21
      2019-08-18 07:22:09.093  - warn: hue.0 could not connect to HUE bridge (192.168.178.38:80)
      2019-08-18 07:22:09.093  - error: hue.0 Api Error: method, GET, not available for resource, /
      2019-08-18 07:22:09.094  - warn: hue.0 could not connect to HUE bridge (192.168.178.38:80)
      2019-08-18 07:22:09.094  - error: hue.0 Api Error: method, GET, not available for resource, /
      2019-08-18 07:22:12.417  - warn: hue.0 could not connect to HUE bridge (192.168.178.38:80)
      2019-08-18 07:22:12.418  - error: hue.0 Api Error: method, GET, not available for resource, /
      2019-08-18 07:22:14.255  - warn: hue.0 could not connect to HUE bridge (192.168.178.38:80)
      2019-08-18 07:22:14.255  - error: hue.0 Api Error: method, GET, not available for resource, /
      2019-08-18 07:22:14.255  - warn: hue.0 could not connect to HUE bridge (192.168.178.38:80)
      2019-08-18 07:22:14.255  - error: hue.0 Api Error: method, GET, not available for resource, /
      2019-08-18 07:22:17.526  - warn: hue.0 could not connect to HUE bridge (192.168.178.38:80)
      2019-08-18 07:22:17.526  - error: hue.0 Api Error: method, GET, not available for resource, /
      2019-08-18 07:22:19.424  - warn: hue.0 could not connect to HUE bridge (192.168.178.38:80)
      2019-08-18 07:22:19.424  - error: hue.0 Api Error: method, GET, not available for resource, /
      2019-08-18 07:22:19.425  - warn: hue.0 could not connect to HUE bridge (192.168.178.38:80)
      2019-08-18 07:22:19.425  - error: hue.0 Api Error: method, GET, not available for resource, /
      2019-08-18 07:22:22.627  - warn: hue.0 could not connect to HUE bridge (192.168.178.38:80)
      2019-08-18 07:22:22.627  - error: hue.0 Api Error: method, GET, not available for resource, /
      2019-08-18 07:22:24.592  - warn: hue.0 could not connect to HUE bridge (192.168.178.38:80)
      2019-08-18 07:22:24.593  - error: hue.0 Api Error: method, GET, not available for resource, /
      2019-08-18 07:22:24.593  - warn: hue.0 could not connect to HUE bridge (192.168.178.38:80)
      2019-08-18 07:22:24.593  - error: hue.0 Api Error: method, GET, not available for resource, /
      2019-08-18 07:22:27.731  - warn: hue.0 could not connect to HUE bridge (192.168.178.38:80)
      2019-08-18 07:22:27.731  - error: hue.0 Api Error: method, GET, not available for resource, /
      2019-08-18 07:22:29.741  - warn: hue.0 could not connect to HUE bridge (192.168.178.38:80)
      2019-08-18 07:22:29.741  - error: hue.0 Api Error: method, GET, not available for resource, /
      2019-08-18 07:22:29.741  - warn: hue.0 could not connect to HUE bridge (192.168.178.38:80)
      2019-08-18 07:22:29.741  - error: hue.0 Api Error: method, GET, not available for resource, /
      2019-08-18 07:22:32.832  - warn: hue.0 could not connect to HUE bridge (192.168.178.38:80)
      2019-08-18 07:22:32.832  - error: hue.0 Api Error: method, GET, not available for resource, /
      2019-08-18 07:22:34.885  - warn: hue.0 could not connect to HUE bridge (192.168.178.38:80)
      2019-08-18 07:22:34.885  - error: hue.0 Api Error: method, GET, not available for resource, /
      2019-08-18 07:22:34.885  - warn: hue.0 could not connect to HUE bridge (192.168.178.38:80)
      2019-08-18 07:22:34.885  - error: hue.0 Api Error: method, GET, not available for resource, /
      2019-08-18 07:22:37.935  - warn: hue.0 could not connect to HUE bridge (192.168.178.38:80)
      2019-08-18 07:22:37.935  - error: hue.0 Api Error: method, GET, not available for resource, /
      2019-08-18 07:22:40.042  - warn: hue.0 could not connect to HUE bridge (192.168.178.38:80)
      2019-08-18 07:22:40.042  - error: hue.0 Api Error: method, GET, not available for resource, /
      2019-08-18 07:22:40.042  - warn: hue.0 could not connect to HUE bridge (192.168.178.38:80)
      2019-08-18 07:22:40.042  - error: hue.0 Api Error: method, GET, not available for resource, /
      2019-08-18 07:22:43.035  - warn: hue.0 could not connect to HUE bridge (192.168.178.38:80)
      2019-08-18 07:22:43.035  - error: hue.0 Api Error: method, GET, not available for resource, /
      2019-08-18 07:22:45.189  - warn: hue.0 could not connect to HUE bridge (192.168.178.38:80)
      2019-08-18 07:22:45.189  - error: hue.0 Api Error: method, GET, not available for resource, /
      2019-08-18 07:22:45.189  - warn: hue.0 could not connect to HUE bridge (192.168.178.38:80)
      2019-08-18 07:22:45.189  - error: hue.0 Api Error: method, GET, not available for resource, /
      2019-08-18 07:22:48.139  - warn: hue.0 could not connect to HUE bridge (192.168.178.38:80)
      2019-08-18 07:22:48.139  - error: hue.0 Api Error: method, GET, not available for resource, /
      2019-08-18 07:22:50.345  - warn: hue.0 could not connect to HUE bridge (192.168.178.38:80)
      2019-08-18 07:22:50.345  - error: hue.0 Api Error: method, GET, not available for resource, /
      2019-08-18 07:22:50.345  - warn: hue.0 could not connect to HUE bridge (192.168.178.38:80)
      2019-08-18 07:22:50.345  - error: hue.0 Api Error: method, GET, not available for resource, /
      2019-08-18 07:22:53.238  - warn: hue.0 could not connect to HUE bridge (192.168.178.38:80)
      2019-08-18 07:22:53.238  - error: hue.0 Api Error: method, GET, not available for resource, /
      2019-08-18 07:22:55.504  - warn: hue.0 could not connect to HUE bridge (192.168.178.38:80)
      2019-08-18 07:22:55.504  - error: hue.0 Api Error: method, GET, not available for resource, /
      2019-08-18 07:22:55.504  - warn: hue.0 could not connect to HUE bridge (192.168.178.38:80)
      2019-08-18 07:22:55.504  - error: hue.0 Api Error: method, GET, not available for resource, /
      2019-08-18 07:22:58.342  - warn: hue.0 could not connect to HUE bridge (192.168.178.38:80)
      2019-08-18 07:22:58.342  - error: hue.0 Api Error: method, GET, not available for resource, /
      2019-08-18 07:23:00.666  - warn: hue.0 could not connect to HUE bridge (192.168.178.38:80)
      2019-08-18 07:23:00.666  - error: hue.0 Api Error: method, GET, not available for resource, /
      2019-08-18 07:23:00.666  - warn: hue.0 could not connect to HUE bridge (192.168.178.38:80)
      2019-08-18 07:23:00.666  - error: hue.0 Api Error: method, GET, not available for resource, /
      2019-08-18 07:23:03.461  - warn: hue.0 could not connect to HUE bridge (192.168.178.38:80)
      2019-08-18 07:23:03.461  - error: hue.0 Api Error: method, GET, not available for resource, /
      2019-08-18 07:23:05.820  - warn: hue.0 could not connect to HUE bridge (192.168.178.38:80)
      2019-08-18 07:23:05.820  - error: hue.0 Api Error: method, GET, not available for resource, /
      2019-08-18 07:23:05.820  - warn: hue.0 could not connect to HUE bridge (192.168.178.38:80)
      2019-08-18 07:23:05.820  - error: hue.0 Api Error: method, GET, not available for resource, /
      2019-08-18 07:23:08.574  - warn: hue.0 could not connect to HUE bridge (192.168.178.38:80)
      2019-08-18 07:23:08.574  - error: hue.0 Api Error: method, GET, not available for resource, /
      2019-08-18 07:23:10.976  - warn: hue.0 could not connect to HUE bridge (192.168.178.38:80)
      2019-08-18 07:23:10.976  - error: hue.0 Api Error: method, GET, not available for resource, /
      2019-08-18 07:23:10.976  - warn: hue.0 could not connect to HUE bridge (192.168.178.38:80)
      2019-08-18 07:23:10.976  - error: hue.0 Api Error: method, GET, not available for resource, /
      2019-08-18 07:23:13.678  - warn: hue.0 could not connect to HUE bridge (192.168.178.38:80)
      2019-08-18 07:23:13.678  - error: hue.0 Api Error: method, GET, not available for resource, /
      2019-08-18 07:23:16.137  - warn: hue.0 could not connect to HUE bridge (192.168.178.38:80)
      2019-08-18 07:23:16.137  - error: hue.0 Api Error: method, GET, not available for resource, /
      2019-08-18 07:23:16.138  - warn: hue.0 could not connect to HUE bridge (192.168.178.38:80)
      2019-08-18 07:23:16.138  - error: hue.0 Api Error: method, GET, not available for resource, /
      2019-08-18 07:23:18.783  - warn: hue.0 could not connect to HUE bridge (192.168.178.38:80)
      2019-08-18 07:23:18.783  - error: hue.0 Api Error: method, GET, not available for resource, /
      2019-08-18 07:23:21.294  - warn: hue.0 could not connect to HUE bridge (192.168.178.38:80)
      2019-08-18 07:23:21.295  - error: hue.0 Api Error: method, GET, not available for resource, /
      2019-08-18 07:23:21.295  - warn: hue.0 could not connect to HUE bridge (192.168.178.38:80)
      2019-08-18 07:23:21.295  - error: hue.0 Api Error: method, GET, not available for resource, /
      2019-08-18 07:23:23.883  - warn: hue.0 could not connect to HUE bridge (192.168.178.38:80)
      2019-08-18 07:23:23.883  - error: hue.0 Api Error: method, GET, not available for resource, /
      2019-08-18 07:23:26.450  - warn: hue.0 could not connect to HUE bridge (192.168.178.38:80)
      2019-08-18 07:23:26.450  - error: hue.0 Api Error: method, GET, not available for resource, /
      2019-08-18 07:23:26.450  - warn: hue.0 could not connect to HUE bridge (192.168.178.38:80)
      2019-08-18 07:23:26.450  - error: hue.0 Api Error: method, GET, not available for resource, /
      2019-08-18 07:23:28.984  - warn: hue.0 could not connect to HUE bridge (192.168.178.38:80)
      2019-08-18 07:23:28.984  - error: hue.0 Api Error: method, GET, not available for resource, /
      2019-08-18 07:23:31.614  - warn: hue.0 could not connect to HUE bridge (192.168.178.38:80)
      2019-08-18 07:23:31.614  - error: hue.0 Api Error: method, GET, not available for resource, /
      2019-08-18 07:23:31.614  - warn: hue.0 could not connect to HUE bridge (192.168.178.38:80)
      2019-08-18 07:23:31.614  - error: hue.0 Api Error: method, GET, not available for resource, /
      2019-08-18 07:23:34.077  - warn: hue.0 could not connect to HUE bridge (192.168.178.38:80)
      2019-08-18 07:23:34.077  - error: hue.0 Api Error: method, GET, not available for resource, /
      2019-08-18 07:23:36.757  - warn: hue.0 could not connect to HUE bridge (192.168.178.38:80)
      2019-08-18 07:23:36.757  - error: hue.0 Api Error: method, GET, not available for resource, /
      2019-08-18 07:23:36.758  - warn: hue.0 could not connect to HUE bridge (192.168.178.38:80)
      2019-08-18 07:23:36.758  - error: hue.0 Api Error: method, GET, not available for resource, /
      2019-08-18 07:23:39.179  - warn: hue.0 could not connect to HUE bridge (192.168.178.38:80)
      2019-08-18 07:23:39.179  - error: hue.0 Api Error: method, GET, not available for resource, /
      2019-08-18 07:23:41.912  - warn: hue.0 could not connect to HUE bridge (192.168.178.38:80)
      2019-08-18 07:23:41.912  - error: hue.0 Api Error: method, GET, not available for resource, /
      2019-08-18 07:23:41.913  - warn: hue.0 could not connect to HUE bridge (192.168.178.38:80)
      2019-08-18 07:23:41.913  - error: hue.0 Api Error: method, GET, not available for resource, /
      2019-08-18 07:23:44.279  - warn: hue.0 could not connect to HUE bridge (192.168.178.38:80)
      2019-08-18 07:23:44.279  - error: hue.0 Api Error: method, GET, not available for resource, /
      2019-08-18 07:23:47.065  - warn: hue.0 could not connect to HUE bridge (192.168.178.38:80)
      2019-08-18 07:23:47.065  - error: hue.0 Api Error: method, GET, not available for resource, /
      2019-08-18 07:23:47.065  - warn: hue.0 could not connect to HUE bridge (192.168.178.38:80)
      2019-08-18 07:23:47.065  - error: hue.0 Api Error: method, GET, not available for resource, /
      2019-08-18 07:23:49.382  - warn: hue.0 could not connect to HUE bridge (192.168.178.38:80)
      2019-08-18 07:23:49.382  - error: hue.0 Api Error: method, GET, not available for resource, /
      2019-08-18 07:23:52.222  - warn: hue.0 could not connect to HUE bridge (192.168.178.38:80)
      2019-08-18 07:23:52.222  - error: hue.0 Api Error: method, GET, not available for resource, /
      2019-08-18 07:23:52.222  - warn: hue.0 could not connect to HUE bridge (192.168.178.38:80)
      2019-08-18 07:23:52.222  - error: hue.0 Api Error: method, GET, not available for resource, /
      2019-08-18 07:23:54.492  - warn: hue.0 could not connect to HUE bridge (192.168.178.38:80)
      2019-08-18 07:23:54.492  - error: hue.0 Api Error: method, GET, not available for resource, /
      2019-08-18 07:23:55.684  - warn: knx.0 Value received on unknown GA : 9/4/11
      2019-08-18 07:23:57.382  - warn: hue.0 could not connect to HUE bridge (192.168.178.38:80)
      2019-08-18 07:23:57.382  - error: hue.0 Api Error: method, GET, not available for resource, /
      2019-08-18 07:23:57.382  - warn: hue.0 could not connect to HUE bridge (192.168.178.38:80)
      2019-08-18 07:23:57.382  - error: hue.0 Api Error: method, GET, not available for resource, /
      2019-08-18 07:23:57.690  - warn: knx.0 Value received on unknown GA : 9/4/21
      2019-08-18 07:23:59.592  - warn: hue.0 could not connect to HUE bridge (192.168.178.38:80)
      2019-08-18 07:23:59.592  - error: hue.0 Api Error: method, GET, not available for resource, /
      2019-08-18 07:24:02.539  - warn: hue.0 could not connect to HUE bridge (192.168.178.38:80)
      2019-08-18 07:24:02.539  - error: hue.0 Api Error: method, GET, not available for resource, /
      2019-08-18 07:24:02.540  - warn: hue.0 could not connect to HUE bridge (192.168.178.38:80)
      2019-08-18 07:24:02.540  - error: hue.0 Api Error: method, GET, not available for resource, /
      2019-08-18 07:24:04.693  - warn: hue.0 could not connect to HUE bridge (192.168.178.38:80)
      2019-08-18 07:24:04.693  - error: hue.0 Api Error: method, GET, not available for resource, /
      2019-08-18 07:24:07.715  - warn: hue.0 could not connect to HUE bridge (192.168.178.38:80)
      2019-08-18 07:24:07.715  - error: hue.0 Api Error: method, GET, not available for resource, /
      2019-08-18 07:24:07.716  - warn: hue.0 could not connect to HUE bridge (192.168.178.38:80)
      2019-08-18 07:24:07.716  - error: hue.0 Api Error: method, GET, not available for resource, /
      2019-08-18 07:24:09.796  - warn: hue.0 could not connect to HUE bridge (192.168.178.38:80)
      2019-08-18 07:24:09.796  - error: hue.0 Api Error: method, GET, not available for resource, /
      2019-08-18 07:24:12.898  - warn: hue.0 could not connect to HUE bridge (192.168.178.38:80)
      2019-08-18 07:24:12.898  - error: hue.0 Api Error: method, GET, not available for resource, /
      2019-08-18 07:24:12.898  - warn: hue.0 could not connect to HUE bridge (192.168.178.38:80)
      2019-08-18 07:24:12.898  - error: hue.0 Api Error: method, GET, not available for resource, /
      2019-08-18 07:24:14.905  - warn: hue.0 could not connect to HUE bridge (192.168.178.38:80)
      2019-08-18 07:24:14.905  - error: hue.0 Api Error: method, GET, not available for resource, /
      2019-08-18 07:24:18.068  - warn: hue.0 could not connect to HUE bridge (192.168.178.38:80)
      2019-08-18 07:24:18.068  - error: hue.0 Api Error: method, GET, not available for resource, /
      2019-08-18 07:24:18.069  - warn: hue.0 could not connect to HUE bridge (192.168.178.38:80)
      2019-08-18 07:24:18.069  - error: hue.0 Api Error: method, GET, not available for resource, /
      2019-08-18 07:24:20.025  - warn: hue.0 could not connect to HUE bridge (192.168.178.38:80)
      2019-08-18 07:24:20.025  - error: hue.0 Api Error: method, GET, not available for resource, /
      2019-08-18 07:24:23.216  - warn: hue.0 could not connect to HUE bridge (192.168.178.38:80)
      2019-08-18 07:24:23.217  - error: hue.0 Api Error: method, GET, not available for resource, /
      2019-08-18 07:24:23.217  - warn: hue.0 could not connect to HUE bridge (192.168.178.38:80)
      2019-08-18 07:24:23.217  - error: hue.0 Api Error: method, GET, not available for resource, /
      2019-08-18 07:24:25.356  - warn: hue.0 could not connect to HUE bridge (192.168.178.38:80)
      2019-08-18 07:24:25.356  - error: hue.0 Api Error: method, GET, not available for resource, /
      2019-08-18 07:24:28.431  - warn: hue.0 could not connect to HUE bridge (192.168.178.38:80)
      2019-08-18 07:24:28.431  - error: hue.0 Api Error: method, GET, not available for resource, /
      2019-08-18 07:24:28.432  - warn: hue.0 could not connect to HUE bridge (192.168.178.38:80)
      2019-08-18 07:24:28.433  - error: hue.0 Api Error: method, GET, not available for resource, /
      2019-08-18 07:24:30.477  - warn: hue.0 could not connect to HUE bridge (192.168.178.38:80)
      2019-08-18 07:24:30.477  - error: hue.0 Api Error: method, GET, not available for resource, /
      2019-08-18 07:24:33.576  - warn: hue.0 could not connect to HUE bridge (192.168.178.38:80)
      2019-08-18 07:24:33.576  - error: hue.0 Api Error: method, GET, not available for resource, /
      2019-08-18 07:24:33.576  - warn: hue.0 could not connect to HUE bridge (192.168.178.38:80)
      2019-08-18 07:24:33.576  - error: hue.0 Api Error: method, GET, not available for resource, /
      2019-08-18 07:24:35.581  - warn: hue.0 could not connect to HUE bridge (192.168.178.38:80)
      2019-08-18 07:24:35.581  - error: hue.0 Api Error: method, GET, not available for resource, /
      2019-08-18 07:24:38.746  - warn: hue.0 could not connect to HUE bridge (192.168.178.38:80)
      2019-08-18 07:24:38.746  - error: hue.0 Api Error: method, GET, not available for resource, /
      2019-08-18 07:24:38.746  - warn: hue.0 could not connect to HUE bridge (192.168.178.38:80)
      2019-08-18 07:24:38.746  - error: hue.0 Api Error: method, GET, not available for resource, /
      2019-08-18 07:24:40.680  - warn: hue.0 could not connect to HUE bridge (192.168.178.38:80)
      2019-08-18 07:24:40.680  - error: hue.0 Api Error: method, GET, not available for resource, /
      2019-08-18 07:24:43.912  - warn: hue.0 could not connect to HUE bridge (192.168.178.38:80)
      2019-08-18 07:24:43.912  - error: hue.0 Api Error: method, GET, not available for resource, /
      2019-08-18 07:24:43.912  - warn: hue.0 could not connect to HUE bridge (192.168.178.38:80)
      2019-08-18 07:24:43.912  - error: hue.0 Api Error: method, GET, not available for resource, /
      2019-08-18 07:24:45.782  - warn: hue.0 could not connect to HUE bridge (192.168.178.38:80)
      2019-08-18 07:24:45.782  - error: hue.0 Api Error: method, GET, not available for resource, /
      2019-08-18 07:24:49.067  - warn: hue.0 could not connect to HUE bridge (192.168.178.38:80)
      2019-08-18 07:24:49.068  - error: hue.0 Api Error: method, GET, not available for resource, /
      2019-08-18 07:24:49.068  - warn: hue.0 could not connect to HUE bridge (192.168.178.38:80)
      2019-08-18 07:24:49.068  - error: hue.0 Api Error: method, GET, not available for resource, /
      2019-08-18 07:24:50.889  - warn: hue.0 could not connect to HUE bridge (192.168.178.38:80)
      2019-08-18 07:24:50.889  - error: hue.0 Api Error: method, GET, not available for resource, /
      2019-08-18 07:24:54.231  - warn: hue.0 could not connect to HUE bridge (192.168.178.38:80)
      2019-08-18 07:24:54.231  - error: hue.0 Api Error: method, GET, not available for resource, /
      2019-08-18 07:24:54.231  - warn: hue.0 could not connect to HUE bridge (192.168.178.38:80)
      2019-08-18 07:24:54.231  - error: hue.0 Api Error: method, GET, not available for resource, /
      2019-08-18 07:24:55.990  - warn: hue.0 could not connect to HUE bridge (192.168.178.38:80)
      2019-08-18 07:24:55.990  - error: hue.0 Api Error: method, GET, not available for resource, /
      2019-08-18 07:24:59.370  - warn: hue.0 could not connect to HUE bridge (192.168.178.38:80)
      2019-08-18 07:24:59.370  - error: hue.0 Api Error: method, GET, not available for resource, /
      2019-08-18 07:24:59.370  - warn: hue.0 could not connect to HUE bridge (192.168.178.38:80)
      2019-08-18 07:24:59.370  - error: hue.0 Api Error: method, GET, not available for resource, /
      2019-08-18 07:25:01.077  - warn: hue.0 could not connect to HUE bridge (192.168.178.38:80)
      2019-08-18 07:25:01.077  - error: hue.0 Api Error: method, GET, not available for resource, /
      2019-08-18 07:25:04.533  - warn: hue.0 could not connect to HUE bridge (192.168.178.38:80)
      2019-08-18 07:25:04.533  - error: hue.0 Api Error: method, GET, not available for resource, /
      2019-08-18 07:25:04.533  - warn: hue.0 could not connect to HUE bridge (192.168.178.38:80)
      2019-08-18 07:25:04.533  - error: hue.0 Api Error: method, GET, not available for resource, /
      2019-08-18 07:25:06.188  - warn: hue.0 could not connect to HUE bridge (192.168.178.38:80)
      2019-08-18 07:25:06.188  - error: hue.0 Api Error: method, GET, not available for resource, /
      2019-08-18 07:25:09.679  - warn: hue.0 could not connect to HUE bridge (192.168.178.38:80)
      2019-08-18 07:25:09.679  - error: hue.0 Api Error: method, GET, not available for resource, /
      2019-08-18 07:25:09.680  - warn: hue.0 could not connect to HUE bridge (192.168.178.38:80)
      2019-08-18 07:25:09.680  - error: hue.0 Api Error: method, GET, not available for resource, /
      2019-08-18 07:32:26.412  - error: hue.0 Api Error: method, GET, not available for resource, /
      
      Segway 1 Reply Last reply Reply Quote 0
      • Segway
        Segway @daniel1to last edited by

        @daniel1to

        Der API Key zur HUE-Bridge stimmt nicht daher wirft er die Fehler raus. Deaktiviere mal den HUE Adapter damit das Log damit nicht zugemüllt wird und schaue dann nochmal ins Log und schicke es.

        D 1 Reply Last reply Reply Quote 0
        • Stabilostick
          Stabilostick @daniel1to last edited by Stabilostick

          @daniel1to

          Am fehlenden + -Zeichen vor der admin.0-Adapterinstanz sieht man, dass diese zu dem Zeitpunkt des ersten Beitrags nicht lief. Schaue im Log nach entsprechenden Fehlern.
          ‚iobroker start admin.0’ sollte den Admin starten. Ggf. kannst Du auch mit ‚iobroker add admin 1‘ eine weitere Instanz mit neuem Port hinzufügen.

          1 Reply Last reply Reply Quote 0
          • D
            daniel1to @Segway last edited by

            @Segway

            Würde ich ja tun wenn ich in die Admin Oberfläche kommen würde. Oder verstehe ich dich falsch?

            Homoran 1 Reply Last reply Reply Quote 0
            • Homoran
              Homoran Global Moderator Administrators @daniel1to last edited by

              @daniel1to sagte in Verbindung zu iobroker fehlgeschlagen?:

              Oder verstehe ich dich falsch?

              wahrscheinlich

              @Stabilostick sagte in Verbindung zu iobroker fehlgeschlagen?:

              iobroker start admin.0 sollte den Admin starten. Ggf. kannst Du auch mit iobroker add admin 1 eine weitere Instanz mit neuem Port hinzufügen.

              Das sind Konsolenbefehle

              D 1 Reply Last reply Reply Quote 0
              • D
                daniel1to @Homoran last edited by

                @Homoran

                OK, so bin ich schonmal wieder ins Admin Menü gelangt, vielen Dank dafür!
                Sollte/müsste/könnte ich die erste admin Instanz jetzt löschen oder wie ist zu erklären, das diese nicht funktioniert?

                Homoran 1 Reply Last reply Reply Quote 0
                • Homoran
                  Homoran Global Moderator Administrators @daniel1to last edited by Homoran

                  @daniel1to sagte in Verbindung zu iobroker fehlgeschlagen?:

                  so bin ich schonmal wieder ins Admin Menü gelangt,

                  Wie denn?
                  Option 1 oder 2?

                  @daniel1to sagte in Verbindung zu iobroker fehlgeschlagen?:

                  könnte ich die erste admin Instanz jetzt löschen

                  Ja.

                  Oder das Problem fixen (Konfiguration der Instanz??) und die neue Instanz löschen

                  Stabilostick 1 Reply Last reply Reply Quote 0
                  • Stabilostick
                    Stabilostick @Homoran last edited by

                    @Homoran et al:

                    Vielleicht hat er doppelte Ports. Log ansehen, wenn er im zweiten Admin.1 ist und versucht, den ersten admin.0 zu starten.

                    1 Reply Last reply Reply Quote 0
                    • D
                      daniel1to last edited by daniel1to

                      OK, ich hab jetzt admin.0 gelöscht. Der funktioniert irgendwie nicht. Oder ist es sinnvoll bei .0 zu bleiben?

                      Ich habe mal versucht iobroker zu stoppen...dann erhalte ich folgendes:

                      C:\Program Files\iobroker\SmartHome>iobroker stop
                      2019-08-18 18:08:05,828 INFO  - Stopping the service with id 'iobroker(SmartHome)'
                      2019-08-18 18:08:05,838 FATAL - WMI Operation failure: ServiceCannotAcceptControl
                      WMI.WmiException: ServiceCannotAcceptControl
                         bei WMI.WmiRoot.BaseHandler.CheckError(ManagementBaseObject result)
                         bei WMI.WmiRoot.InstanceHandler.Invoke(Object proxy, MethodInfo method, Object[] args)
                         bei winsw.WrapperService.Run(String[] _args, ServiceDescriptor descriptor)
                         bei winsw.WrapperService.Main(String[] args)
                      WMI.WmiException: ServiceCannotAcceptControl
                         bei WMI.WmiRoot.BaseHandler.CheckError(ManagementBaseObject result)
                         bei WMI.WmiRoot.InstanceHandler.Invoke(Object proxy, MethodInfo method, Object[] args)
                         bei winsw.WrapperService.Run(String[] _args, ServiceDescriptor descriptor)
                         bei winsw.WrapperService.Main(String[] args)
                      
                      Stabilostick 2 Replies Last reply Reply Quote 0
                      • apollon77
                        apollon77 last edited by apollon77

                        Generell sieht das Log alles andere als gesund aus. Die ganzen "Reconnect to DB" sind kritisch! Irgendetwas blockiert da für 20+ Sekunden den Adapterprozess.

                        Bei knx stimmt auch was nicht und so weiter.

                        Was für ein System? RAM? Wieviel frei? (Ausgabe top bzw "free -m")? Wieviele Adapter-Instanzen laufen?

                        Falls das WMI zeig von den info-Systemdaten Checks Probleme macht: ausschalten!

                        Da würde ich mal anfangen:

                        • Alles ausser Admin abschalten
                        • Dann einen Adapter nach dem anderen langsam der Wichtigkeit nach wieder einschalten
                        • Log beobachten, nicht funktionierende Adapter gleich aus lassen und Ursache (Konfig?) fixen

                        Sobald wieder "Reconnect to DB" oder sowas kommt stoppen und Ursachen analysieren

                        D 1 Reply Last reply Reply Quote 0
                        • D
                          daniel1to @apollon77 last edited by daniel1to

                          @apollon77

                          Also ich muss ehrlich gestehen ich verstehe nur einen Bruchteil von alledem. Ich habe gestern nichts gemacht außer iobroker zu installieren und die adapter runterzuladen. Ich habe eigentlich noch gar nicht mehr getan, wollte heute morgen eigentlich damit so langsam anfangen zu üben.

                          Mein PC hat 16GB Ram, daran sollte es wohl nicht scheitern.

                          was bedeutet free -m?

                          Ich lösche mal die adapter und schaue was dann so passiert. Evtl hilft das ja schonmal weiter.

                          Vielen Dank schonmal!

                          Edit: Also ich habe nun alles runter außer die Standardsachen.

                          admin.0	
                          admin.1	
                          discovery.0	
                          info.0	
                          web.0
                          

                          Trotzdem geht es immer nur mit admin.1. Sobald ich den lösche und nur noch admin.0 übrig ist geht es nicht mehr. Vor der Instanz admin.0 befindet sich zudem ein roter Punkt der sagt das keine Verbindung zum Host besteht.

                          Stabilostick apollon77 2 Replies Last reply Reply Quote 0
                          • Stabilostick
                            Stabilostick @daniel1to last edited by

                            @daniel1to
                            Du hast eine Nachricht von mir. Interesse?

                            1 Reply Last reply Reply Quote 0
                            • D
                              daniel1to last edited by

                              Unbenannt.png

                              Soe sieht das ganze aus

                              1 Reply Last reply Reply Quote 0
                              • apollon77
                                apollon77 @daniel1to last edited by apollon77

                                @daniel1to Naja beendend wäre ok gewesen, löschen eher unnötig 🙂
                                Was sagt denn "iobroker list instances" in der ioBroker-Shell?

                                Bzw hier wäre jetzt das Log interessant wenn du admin.0 mal stoppst und startest

                                Homoran 1 Reply Last reply Reply Quote 0
                                • Homoran
                                  Homoran Global Moderator Administrators @apollon77 last edited by

                                  @apollon77
                                  ... und was steht im log unmittelbar nachdem du die Instanz .0 neu startest

                                  1 Reply Last reply Reply Quote 0
                                  • Stabilostick
                                    Stabilostick @daniel1to last edited by Stabilostick

                                    @daniel1to sagte in Verbindung zu iobroker fehlgeschlagen?:

                                    C:\Program Files\iobroker\SmartHome>iobroker stop
                                    2019-08-18 18:08:05,828 INFO  - Stopping the service with id 'iobroker(SmartHome)'
                                    2019-08-18 18:08:05,838 FATAL - WMI Operation failure: ServiceCannotAcceptControl
                                    

                                    Wenn so was kommt, dann stehen im Ordner ‚daemon‘ im ioBroker Verzeichnis weitere Logdateien bzgl. Windows-Dienste und ioBroker zur Verfügung. Auf jeden Fall passt da was überhaupt nicht.

                                    Schon mal in den Chat oben rechts im Forum geschaut?

                                    1 Reply Last reply Reply Quote 0
                                    • D
                                      daniel1to last edited by

                                      List Instances:

                                      C:\Program Files\iobroker\SmartHome>iobroker list instances
                                        system.adapter.admin.0                 : admin       -  enabled, port: 8081, bind: 0.0.0.0, run as: admin
                                      + system.adapter.admin.1                 : admin       -  enabled, port: 8081, bind: 0.0.0.0, run as: admin
                                      + system.adapter.discovery.0             : discovery   -  enabled
                                      + system.adapter.info.0                  : info        -  enabled
                                      + system.adapter.web.0                   : web         -  enabled, port: 8082, bind: 0.0.0.0, run as: admin
                                      
                                      + instance is alive
                                      

                                      Neu Laden:

                                      host.DESKTOP-GFRKJ98(SmartHome)	2019-08-18 18:29:08.468	info	Do not restart adapter system.adapter.admin.0 because desired by instance
                                      host.DESKTOP-GFRKJ98(SmartHome)	2019-08-18 18:29:08.468	error	instance system.adapter.admin.0 terminated by request of the instance itself and will not be restarted, before user restarts it.
                                      admin.0	2019-08-18 18:29:08.429	error	port 8081 already in use
                                      host.DESKTOP-GFRKJ98(SmartHome)	2019-08-18 18:29:08.230	info	Update repository "default" under "http://download.iobroker.net/sources-dist.json"
                                      admin.0	2019-08-18 18:29:08.214	info	received all objects
                                      admin.0	2019-08-18 18:29:08.076	info	received all states
                                      admin.0	2019-08-18 18:29:08.015	info	Request actual repository...
                                      admin.0	2019-08-18 18:29:08.015	info	requesting all objects
                                      admin.0	2019-08-18 18:29:08.015	info	requesting all states
                                      admin.0	2019-08-18 18:29:08.005	info	starting. Version 3.6.2 in C:/Program Files/iobroker/SmartHome/node_modules/iobroker.admin, node: v10.16.0
                                      host.DESKTOP-GFRKJ98(SmartHome)	2019-08-18 18:29:07.435	info	instance system.adapter.admin.0 started with pid 63700 
                                      

                                      @Stabolostick: habe leider das Programm nicht.

                                      Homoran 1 Reply Last reply Reply Quote 0
                                      • Homoran
                                        Homoran Global Moderator Administrators @daniel1to last edited by Homoran

                                        @daniel1to sagte in Verbindung zu iobroker fehlgeschlagen?:

                                        system.adapter.admin.0                 : admin       -  enabled, port: 8081, bind: 0.0.0.0, run as: admin 
                                        + system.adapter.admin.1                 > + admin       -  enabled, port: 8081, bind: 0.0.0.0, run as: admin
                                        

                                        2x Port 8081 geht nicht

                                        D 1 Reply Last reply Reply Quote 0
                                        • D
                                          daniel1to @Homoran last edited by

                                          @Homoran

                                          vorher war aber nur der admin.0 da und der alleine ging ja auch nicht. und der .1 geht trotz alledem.

                                          Homoran 1 Reply Last reply Reply Quote 0
                                          • Homoran
                                            Homoran Global Moderator Administrators @daniel1to last edited by

                                            @daniel1to sagte in Verbindung zu iobroker fehlgeschlagen?:

                                            @Homoran

                                            vorher war aber nur der admin.0 da und der alleine ging ja auch nicht. und der .1 geht trotz alledem.

                                            Dann setze eben mal .0 auf 8089 oder welchen Port du noch frei hast

                                            1 Reply Last reply Reply Quote 0
                                            • First post
                                              Last post

                                            Support us

                                            ioBroker
                                            Community Adapters
                                            Donate
                                            FAQ Cloud / IOT
                                            HowTo: Node.js-Update
                                            HowTo: Backup/Restore
                                            Downloads
                                            BLOG

                                            1.0k
                                            Online

                                            31.7k
                                            Users

                                            79.7k
                                            Topics

                                            1.3m
                                            Posts

                                            iobroker knx
                                            5
                                            42
                                            2486
                                            Loading More Posts
                                            • Oldest to Newest
                                            • Newest to Oldest
                                            • Most Votes
                                            Reply
                                            • Reply as topic
                                            Log in to reply
                                            Community
                                            Impressum | Datenschutz-Bestimmungen | Nutzungsbedingungen
                                            The ioBroker Community 2014-2023
                                            logo