@rintrium Danke für das Update des Adapters! 
F
Best posts made by Fortune95
-
RE: Alpha Test js-controller 4.0posted in Tester
@apollon77 sagte in Alpha Test js-controller 4.0:
@fortune95 Legst Du dann bitte 4 GitHub issues an? ;-)) (bzw 3 weil ich glaube shelly gibts schon)
Done!
-
RE: Alpha Test js-controller 4.0posted in Tester
@apollon77
Upadate auf 4.0.3 lief mit den bereits bekannten Warnungen von den Adaptern Yamaha, Shelly und shuttercontrol durch.
Braucht der neue js-controller weniger Speicher?
-
RE: Shelly Adapter 5.2.0 für Plus- und Pro-Geräte erweitertposted in Tester
Hi, hatte heute morgen folgenden Fehler nach einem Neustart des Adapters im Log:
2022-02-22 06:12:00.875 - error: shelly.0 (15030) uncaught exception: This socket has been ended by the other party 2022-02-22 06:12:00.876 - error: shelly.0 (15030) Error: This socket has been ended by the other party at Socket.writeAfterFIN [as write] (net.js:468:14) at connack (/opt/iobroker/node_modules/mqtt-connection/node_modules/mqtt-packet/writeToStream.js:300:10) at generate (/opt/iobroker/node_modules/mqtt-connection/node_modules/mqtt-packet/writeToStream.js:32:14) at Writable.write [as _write] (/opt/iobroker/node_modules/mqtt-connection/lib/writeToStream.js:13:9) at writeOrBuffer (internal/streams/writable.js:358:12) at Writable.write (internal/streams/writable.js:303:10) at Connection.Duplexify._write (/opt/iobroker/node_modules/duplexify/index.js:208:22) at doWrite (/opt/iobroker/node_modules/duplexify/node_modules/readable-stream/lib/_stream_writable.js:428:64) at writeOrBuffer (/opt/iobroker/node_modules/duplexify/node_modules/readable-stream/lib/_stream_writable.js:417:5) at Connection.Writable.write (/opt/iobroker/node_modules/duplexify/node_modules/readable-stream/lib/_stream_writable.js:334:11) 2022-02-22 06:12:00.877 - error: shelly.0 (15030) Exception-Code: EPIPE: This socket has been ended by the other party 2022-02-22 06:12:00.880 - error: shelly.0 (15030) uncaught exception: This socket has been ended by the other party 2022-02-22 06:12:00.880 - error: shelly.0 (15030) Error: This socket has been ended by the other party at Socket.writeAfterFIN [as write] (net.js:468:14) at writeVarByteInt (/opt/iobroker/node_modules/mqtt-connection/node_modules/mqtt-packet/writeToStream.js:804:17) at connack (/opt/iobroker/node_modules/mqtt-connection/node_modules/mqtt-packet/writeToStream.js:302:3) at generate (/opt/iobroker/node_modules/mqtt-connection/node_modules/mqtt-packet/writeToStream.js:32:14) at Writable.write [as _write] (/opt/iobroker/node_modules/mqtt-connection/lib/writeToStream.js:13:9) at writeOrBuffer (internal/streams/writable.js:358:12) at Writable.write (internal/streams/writable.js:303:10) at Connection.Duplexify._write (/opt/iobroker/node_modules/duplexify/index.js:208:22) at doWrite (/opt/iobroker/node_modules/duplexify/node_modules/readable-stream/lib/_stream_writable.js:428:64) at writeOrBuffer (/opt/iobroker/node_modules/duplexify/node_modules/readable-stream/lib/_stream_writable.js:417:5) 2022-02-22 06:12:00.880 - error: shelly.0 (15030) Exception-Code: EPIPE: This socket has been ended by the other party 2022-02-22 06:12:00.881 - error: shelly.0 (15030) uncaught exception: This socket has been ended by the other party 2022-02-22 06:12:00.881 - error: shelly.0 (15030) Error: This socket has been ended by the other party at Socket.writeAfterFIN [as write] (net.js:468:14) at connack (/opt/iobroker/node_modules/mqtt-connection/node_modules/mqtt-packet/writeToStream.js:303:10) at generate (/opt/iobroker/node_modules/mqtt-connection/node_modules/mqtt-packet/writeToStream.js:32:14) at Writable.write [as _write] (/opt/iobroker/node_modules/mqtt-connection/lib/writeToStream.js:13:9) at writeOrBuffer (internal/streams/writable.js:358:12) at Writable.write (internal/streams/writable.js:303:10) at Connection.Duplexify._write (/opt/iobroker/node_modules/duplexify/index.js:208:22) at doWrite (/opt/iobroker/node_modules/duplexify/node_modules/readable-stream/lib/_stream_writable.js:428:64) at writeOrBuffer (/opt/iobroker/node_modules/duplexify/node_modules/readable-stream/lib/_stream_writable.js:417:5) at Connection.Writable.write (/opt/iobroker/node_modules/duplexify/node_modules/readable-stream/lib/_stream_writable.js:334:11) 2022-02-22 06:12:00.881 - error: shelly.0 (15030) Exception-Code: EPIPE: This socket has been ended by the other party 2022-02-22 06:12:00.882 - error: shelly.0 (15030) uncaught exception: This socket has been ended by the other party 2022-02-22 06:12:00.882 - error: shelly.0 (15030) Error: This socket has been ended by the other party at Socket.writeAfterFIN [as write] (net.js:468:14) at connack (/opt/iobroker/node_modules/mqtt-connection/node_modules/mqtt-packet/writeToStream.js:305:10) at generate (/opt/iobroker/node_modules/mqtt-connection/node_modules/mqtt-packet/writeToStream.js:32:14) at Writable.write [as _write] (/opt/iobroker/node_modules/mqtt-connection/lib/writeToStream.js:13:9) at writeOrBuffer (internal/streams/writable.js:358:12) at Writable.write (internal/streams/writable.js:303:10) at Connection.Duplexify._write (/opt/iobroker/node_modules/duplexify/index.js:208:22) at doWrite (/opt/iobroker/node_modules/duplexify/node_modules/readable-stream/lib/_stream_writable.js:428:64) at writeOrBuffer (/opt/iobroker/node_modules/duplexify/node_modules/readable-stream/lib/_stream_writable.js:417:5) at Connection.Writable.write (/opt/iobroker/node_modules/duplexify/node_modules/readable-stream/lib/_stream_writable.js:334:11) 2022-02-22 06:12:00.882 - error: shelly.0 (15030) Exception-Code: EPIPE: This socket has been ended by the other party 2022-02-22 06:12:00.883 - warn: shelly.0 (15030) Terminated (UNCAUGHT_EXCEPTION): Without reason 2022-02-22 06:12:00.950 - error: host.iobroker Caught by controller[1]: Error: This socket has been ended by the other party 2022-02-22 06:12:00.955 - error: host.iobroker Caught by controller[1]: at Socket.writeAfterFIN [as write] (net.js:468:14) 2022-02-22 06:12:00.955 - error: host.iobroker Caught by controller[1]: at connack (/opt/iobroker/node_modules/mqtt-connection/node_modules/mqtt-packet/writeToStream.js:300:10) 2022-02-22 06:12:00.955 - error: host.iobroker Caught by controller[1]: at generate (/opt/iobroker/node_modules/mqtt-connection/node_modules/mqtt-packet/writeToStream.js:32:14) 2022-02-22 06:12:00.955 - error: host.iobroker Caught by controller[1]: at Writable.write [as _write] (/opt/iobroker/node_modules/mqtt-connection/lib/writeToStream.js:13:9) 2022-02-22 06:12:00.955 - error: host.iobroker Caught by controller[1]: at writeOrBuffer (internal/streams/writable.js:358:12) 2022-02-22 06:12:00.956 - error: host.iobroker Caught by controller[1]: at Writable.write (internal/streams/writable.js:303:10) 2022-02-22 06:12:00.956 - error: host.iobroker Caught by controller[1]: at Connection.Duplexify._write (/opt/iobroker/node_modules/duplexify/index.js:208:22) 2022-02-22 06:12:00.956 - error: host.iobroker Caught by controller[1]: at doWrite (/opt/iobroker/node_modules/duplexify/node_modules/readable-stream/lib/_stream_writable.js:428:64) 2022-02-22 06:12:00.956 - error: host.iobroker Caught by controller[1]: at writeOrBuffer (/opt/iobroker/node_modules/duplexify/node_modules/readable-stream/lib/_stream_writable.js:417:5) 2022-02-22 06:12:00.956 - error: host.iobroker Caught by controller[1]: at Connection.Writable.write (/opt/iobroker/node_modules/duplexify/node_modules/readable-stream/lib/_stream_writable.js:334:11) 2022-02-22 06:12:00.956 - error: host.iobroker Caught by controller[2]: Error: This socket has been ended by the other party 2022-02-22 06:12:00.956 - error: host.iobroker Caught by controller[2]: at Socket.writeAfterFIN [as write] (net.js:468:14) 2022-02-22 06:12:00.956 - error: host.iobroker Caught by controller[2]: at writeVarByteInt (/opt/iobroker/node_modules/mqtt-connection/node_modules/mqtt-packet/writeToStream.js:804:17) 2022-02-22 06:12:00.956 - error: host.iobroker Caught by controller[2]: at connack (/opt/iobroker/node_modules/mqtt-connection/node_modules/mqtt-packet/writeToStream.js:302:3) 2022-02-22 06:12:00.957 - error: host.iobroker Caught by controller[2]: at generate (/opt/iobroker/node_modules/mqtt-connection/node_modules/mqtt-packet/writeToStream.js:32:14) 2022-02-22 06:12:00.957 - error: host.iobroker Caught by controller[2]: at Writable.write [as _write] (/opt/iobroker/node_modules/mqtt-connection/lib/writeToStream.js:13:9) 2022-02-22 06:12:00.957 - error: host.iobroker Caught by controller[2]: at writeOrBuffer (internal/streams/writable.js:358:12) 2022-02-22 06:12:00.957 - error: host.iobroker Caught by controller[2]: at Writable.write (internal/streams/writable.js:303:10) 2022-02-22 06:12:00.957 - error: host.iobroker Caught by controller[2]: at Connection.Duplexify._write (/opt/iobroker/node_modules/duplexify/index.js:208:22) 2022-02-22 06:12:00.957 - error: host.iobroker Caught by controller[2]: at doWrite (/opt/iobroker/node_modules/duplexify/node_modules/readable-stream/lib/_stream_writable.js:428:64) 2022-02-22 06:12:00.957 - error: host.iobroker Caught by controller[2]: at writeOrBuffer (/opt/iobroker/node_modules/duplexify/node_modules/readable-stream/lib/_stream_writable.js:417:5) 2022-02-22 06:12:00.957 - error: host.iobroker Caught by controller[2]: Error: This socket has been ended by the other party 2022-02-22 06:12:00.957 - error: host.iobroker Caught by controller[2]: at Socket.writeAfterFIN [as write] (net.js:468:14) 2022-02-22 06:12:00.957 - error: host.iobroker Caught by controller[2]: at connack (/opt/iobroker/node_modules/mqtt-connection/node_modules/mqtt-packet/writeToStream.js:303:10) 2022-02-22 06:12:00.958 - error: host.iobroker Caught by controller[2]: at generate (/opt/iobroker/node_modules/mqtt-connection/node_modules/mqtt-packet/writeToStream.js:32:14) 2022-02-22 06:12:00.958 - error: host.iobroker Caught by controller[2]: at Writable.write [as _write] (/opt/iobroker/node_modules/mqtt-connection/lib/writeToStream.js:13:9) 2022-02-22 06:12:00.958 - error: host.iobroker Caught by controller[2]: at writeOrBuffer (internal/streams/writable.js:358:12) 2022-02-22 06:12:00.958 - error: host.iobroker Caught by controller[2]: at Writable.write (internal/streams/writable.js:303:10) 2022-02-22 06:12:00.958 - error: host.iobroker Caught by controller[2]: at Connection.Duplexify._write (/opt/iobroker/node_modules/duplexify/index.js:208:22) 2022-02-22 06:12:00.958 - error: host.iobroker Caught by controller[2]: at doWrite (/opt/iobroker/node_modules/duplexify/node_modules/readable-stream/lib/_stream_writable.js:428:64) 2022-02-22 06:12:00.958 - error: host.iobroker Caught by controller[2]: at writeOrBuffer (/opt/iobroker/node_modules/duplexify/node_modules/readable-stream/lib/_stream_writable.js:417:5) 2022-02-22 06:12:00.958 - error: host.iobroker Caught by controller[2]: at Connection.Writable.write (/opt/iobroker/node_modules/duplexify/node_modules/readable-stream/lib/_stream_writable.js:334:11) 2022-02-22 06:12:00.958 - error: host.iobroker Caught by controller[3]: Error: This socket has been ended by the other party 2022-02-22 06:12:00.958 - error: host.iobroker Caught by controller[3]: at Socket.writeAfterFIN [as write] (net.js:468:14) 2022-02-22 06:12:00.959 - error: host.iobroker Caught by controller[3]: at connack (/opt/iobroker/node_modules/mqtt-connection/node_modules/mqtt-packet/writeToStream.js:305:10) 2022-02-22 06:12:00.959 - error: host.iobroker Caught by controller[3]: at generate (/opt/iobroker/node_modules/mqtt-connection/node_modules/mqtt-packet/writeToStream.js:32:14) 2022-02-22 06:12:00.959 - error: host.iobroker Caught by controller[3]: at Writable.write [as _write] (/opt/iobroker/node_modules/mqtt-connection/lib/writeToStream.js:13:9) 2022-02-22 06:12:00.959 - error: host.iobroker Caught by controller[3]: at writeOrBuffer (internal/streams/writable.js:358:12) 2022-02-22 06:12:00.959 - error: host.iobroker Caught by controller[3]: at Writable.write (internal/streams/writable.js:303:10) 2022-02-22 06:12:00.959 - error: host.iobroker Caught by controller[3]: at Connection.Duplexify._write (/opt/iobroker/node_modules/duplexify/index.js:208:22) 2022-02-22 06:12:00.961 - error: host.iobroker Caught by controller[3]: at doWrite (/opt/iobroker/node_modules/duplexify/node_modules/readable-stream/lib/_stream_writable.js:428:64) 2022-02-22 06:12:00.961 - error: host.iobroker Caught by controller[3]: at writeOrBuffer (/opt/iobroker/node_modules/duplexify/node_modules/readable-stream/lib/_stream_writable.js:417:5) 2022-02-22 06:12:00.962 - error: host.iobroker Caught by controller[3]: at Connection.Writable.write (/opt/iobroker/node_modules/duplexify/node_modules/readable-stream/lib/_stream_writable.js:334:11) 2022-02-22 06:12:00.962 - error: host.iobroker instance system.adapter.shelly.0 terminated with code 1 (JS_CONTROLLER_STOPPED)
Latest posts made by Fortune95
-
RE: [Neuer Adapter] SelveRFposted in Tester
@rintrium bei mir läuft die neue Version einwandfrei!
Danke! -
RE: Alpha Test js-controller Kiera (v6.0)posted in Tester
@foxriver76
Du warst schneller Danke!
Mit der github Version startet der Adapter jetzt. -
RE: Alpha Test js-controller Kiera (v6.0)posted in Tester
iobroker@iobroker:/opt/iobroker$ npm ls @iobroker/adapter-core iobroker.inst@3.0.0 /opt/iobroker +-- iobroker.admin@6.17.13 | +-- @iobroker/adapter-core@3.1.4 | `-- @iobroker/socket-classes@1.5.0 | `-- @iobroker/adapter-core@3.1.4 +-- iobroker.alias-manager@1.2.6 | `-- @iobroker/adapter-core@2.6.12 +-- iobroker.backitup@2.11.0 | `-- @iobroker/adapter-core@3.1.4 +-- iobroker.bydhvs@1.5.0 | `-- @iobroker/adapter-core@3.1.4 +-- iobroker.daswetter@3.1.13 | `-- @iobroker/adapter-core@3.0.4 +-- iobroker.device-reminder@3.1.2 | `-- @iobroker/adapter-core@3.1.4 +-- iobroker.discovery@4.5.0 | `-- @iobroker/adapter-core@3.1.4 +-- iobroker.dwd@2.8.5 | `-- @iobroker/adapter-core@2.6.12 deduped +-- iobroker.ebus@3.3.0 | `-- @iobroker/adapter-core@3.1.4 +-- iobroker.energiefluss-erweitert@0.4.1 | `-- @iobroker/adapter-core@3.1.4 +-- iobroker.esphome@0.5.0-beta.8 | `-- @iobroker/adapter-core@3.1.4 +-- iobroker.feiertage@1.2.0 | `-- @iobroker/adapter-core@3.1.4 +-- iobroker.fritzdect@2.5.9 | `-- @iobroker/adapter-core@2.6.12 deduped +-- iobroker.gruenbeck@0.0.43 | `-- @iobroker/adapter-core@3.1.4 +-- iobroker.heatingcontrol@2.12.5 | `-- @iobroker/adapter-core@3.0.4 +-- iobroker.hm-rega@4.0.0 | `-- @iobroker/adapter-core@3.1.4 +-- iobroker.hm-rpc@1.17.0 | +-- @iobroker/adapter-core@3.1.4 | `-- @iobroker/dm-utils@0.1.9 | `-- @iobroker/adapter-core@3.1.4 +-- iobroker.homeconnect@1.4.0 | `-- @iobroker/adapter-core@3.1.4 +-- iobroker.homekit-controller@0.5.10 | `-- @iobroker/adapter-core@3.1.4 +-- iobroker.ical@1.15.0 | `-- @iobroker/adapter-core@3.1.4 +-- iobroker.influxdb@4.0.2 | `-- @iobroker/adapter-core@3.1.4 +-- iobroker.iot@3.3.0 | `-- @iobroker/adapter-core@3.1.4 +-- iobroker.iqontrol@2.3.0 | `-- @iobroker/adapter-core@2.6.12 deduped +-- iobroker.javascript@8.3.1 | `-- @iobroker/adapter-core@3.1.4 +-- iobroker.jeelink@1.2.3 | `-- @iobroker/adapter-core@2.6.12 deduped +-- iobroker.js-controller@6.0.1-alpha.0-20240525-56d9e4a2e | `-- @iobroker/adapter-core@2.6.12 deduped +-- iobroker.klf200@1.2.0 | `-- @iobroker/adapter-core@3.1.4 +-- iobroker.mercedesme@0.2.3 | `-- @iobroker/adapter-core@3.1.4 +-- iobroker.mihome-vacuum@4.2.0 | `-- @iobroker/adapter-core@3.1.4 +-- iobroker.modbus@6.2.2 | `-- @iobroker/adapter-core@3.1.4 +-- iobroker.mqtt@5.2.0 | `-- @iobroker/adapter-core@3.1.4 +-- iobroker.node-red@5.2.1 | `-- @iobroker/adapter-core@3.1.4 +-- iobroker.openknx@0.9.0 | `-- @iobroker/adapter-core@3.1.4 +-- iobroker.pushover@3.0.6 | `-- @iobroker/adapter-core@3.1.4 +-- iobroker.pvforecast@2.9.1 | `-- @iobroker/adapter-core@3.1.4 +-- iobroker.selverf@0.6.3 | `-- @iobroker/adapter-core@2.6.12 deduped +-- iobroker.shelly@7.0.0 | `-- @iobroker/adapter-core@3.1.4 +-- iobroker.shuttercontrol@1.7.0 | `-- @iobroker/adapter-core@3.1.4 +-- iobroker.simple-api@2.8.0 | `-- @iobroker/adapter-core@3.1.4 +-- iobroker.sma-em@1.0.1 | `-- @iobroker/adapter-core@3.1.4 +-- iobroker.smartcontrol@2.0.1 | `-- @iobroker/adapter-core@3.1.4 +-- iobroker.socketio@6.7.0 | `-- @iobroker/adapter-core@3.1.4 +-- iobroker.sonoff@3.0.3 | `-- @iobroker/adapter-core@3.1.4 +-- iobroker.tankerkoenig@3.4.0 | `-- @iobroker/adapter-core@3.1.4 +-- iobroker.telegram@3.2.1 | `-- @iobroker/adapter-core@3.1.4 +-- iobroker.text2command@3.0.3 | `-- @iobroker/adapter-core@3.1.4 +-- iobroker.tr-064@4.3.0 | `-- @iobroker/adapter-core@3.1.4 +-- iobroker.unifi@0.7.0 | `-- @iobroker/adapter-core@3.1.4 +-- iobroker.vis-2@2.9.64 | `-- @iobroker/adapter-core@3.1.4 +-- iobroker.web@6.2.5 | +-- @iobroker/adapter-core@3.1.4 | +-- iobroker.socketio@6.6.1 | | `-- @iobroker/adapter-core@3.1.4 deduped | `-- iobroker.ws@2.5.11 | `-- @iobroker/adapter-core@3.1.4 deduped +-- iobroker.ws@2.6.1 | `-- @iobroker/adapter-core@3.1.4 +-- iobroker.yahka@1.0.3 | `-- @iobroker/adapter-core@2.6.12 deduped +-- iobroker.yamaha@0.5.3 | `-- @iobroker/adapter-core@2.6.12 deduped `-- iobroker.zigbee@1.10.3 `-- @iobroker/adapter-core@3.1.4 -
RE: Alpha Test js-controller Kiera (v6.0)posted in Tester
Der Admin hat die Version 6.17.13
iobroker@iobroker:~$ npm ls @iobroker/adapter-core iobroker@ /home/iobroker `-- iobroker.js-controller@6.0.1-alpha.0-20240522-72e34be5c `-- @iobroker/adapter-core@3.1.4 -
RE: Alpha Test js-controller Kiera (v6.0)posted in Tester
Update lief durch, nur der Heatcontrol Adapter startet wie zuvor nicht.
Soll ich ein issue beim Adapter öffnen? -
RE: Alpha Test js-controller Kiera (v6.0)posted in Tester
@foxriver76
Habs versucht geht aber immer noch nicht.
Update hat auch nichhts gefunden...iobroker@iobroker:/opt/iobroker$ npm update up to date in 2m 207 packages are looking for funding run `npm fund` for details iobroker@iobroker:/opt/iobroker$ -
RE: Alpha Test js-controller Kiera (v6.0)posted in Tester
@foxriver76
Aktuelle Version läuft.
Nur der Adapter Heatingcontrol läuft nicht an:2024-05-24 18:21:38.650 - error: host.iobroker Caught by controller[0]: /opt/iobroker/node_modules/iobroker.heatingcontrol/node_modules/@iobroker/adapter-co re/build/controllerTools.js:83 2024-05-24 18:21:38.651 - error: host.iobroker Caught by controller[0]: throw new Error(`Cannot resolve JS-Controller module ${name}.js`); 2024-05-24 18:21:38.651 - error: host.iobroker Caught by controller[0]: ^ 2024-05-24 18:21:38.651 - error: host.iobroker Caught by controller[0]: Error: Cannot resolve JS-Controller module letsencrypt.js 2024-05-24 18:21:38.651 - error: host.iobroker Caught by controller[0]: at resolveNamedModule (/opt/iobroker/node_modules/iobroker.heatingcontrol/node_m odules/@iobroker/adapter-core/build/controllerTools.js:83:11) 2024-05-24 18:21:38.652 - error: host.iobroker Caught by controller[0]: at Object.<anonymous> (/opt/iobroker/node_modules/iobroker.heatingcontrol/node_m odules/@iobroker/adapter-core/build/controllerTools.js:157:18) 2024-05-24 18:21:38.652 - error: host.iobroker Caught by controller[0]: at Module._compile (node:internal/modules/cjs/loader:1358:14) 2024-05-24 18:21:38.652 - error: host.iobroker Caught by controller[0]: at Module._extensions..js (node:internal/modules/cjs/loader:1416:10) 2024-05-24 18:21:38.652 - error: host.iobroker Caught by controller[0]: at Module.load (node:internal/modules/cjs/loader:1208:32) 2024-05-24 18:21:38.652 - error: host.iobroker Caught by controller[0]: at Module._load (node:internal/modules/cjs/loader:1024:12) 2024-05-24 18:21:38.652 - error: host.iobroker Caught by controller[0]: at Module.require (node:internal/modules/cjs/loader:1233:19) 2024-05-24 18:21:38.652 - error: host.iobroker Caught by controller[0]: at require (node:internal/modules/helpers:179:18) 2024-05-24 18:21:38.652 - error: host.iobroker Caught by controller[0]: at Object.<anonymous> (/opt/iobroker/node_modules/iobroker.heatingcontrol/node_m odules/@iobroker/adapter-core/build/index.js:19:27) 2024-05-24 18:21:38.652 - error: host.iobroker Caught by controller[0]: at Module._compile (node:internal/modules/cjs/loader:1358:14) 2024-05-24 18:21:38.652 - error: host.iobroker Caught by controller[0]: Node.js v20.13.1 2024-05-24 18:21:38.652 - error: host.iobroker instance system.adapter.heatingcontrol.0 terminated with code 1 (JS_CONTROLLER_STOPPED)Adapter Instanzen:
+ system.adapter.admin.0 : admin : iobroker - enabled, port: 8081, bind: 0.0.0.0, run as: admin system.adapter.alias-manager.0 : alias-manager : iobroker - disabled + system.adapter.backitup.0 : backitup : iobroker - enabled + system.adapter.bydhvs.0 : bydhvs : iobroker - enabled system.adapter.daswetter.0 : daswetter : iobroker - disabled + system.adapter.device-reminder.0 : device-reminder : iobroker - enabled system.adapter.devices.0 : devices : iobroker - disabled + system.adapter.discovery.0 : discovery : iobroker - enabled system.adapter.dwd.0 : dwd : iobroker - enabled + system.adapter.ebus.0 : ebus : iobroker - enabled system.adapter.energiefluss-erweitert.0 : energiefluss-erweitert: iobroker - disabled system.adapter.esphome.0 : esphome : iobroker - disabled system.adapter.feiertage.0 : feiertage : iobroker - enabled system.adapter.fritzdect.0 : fritzdect : iobroker - disabled + system.adapter.gruenbeck.0 : gruenbeck : iobroker - enabled system.adapter.heatingcontrol.0 : heatingcontrol : iobroker - disabled + system.adapter.hm-rega.0 : hm-rega : iobroker - enabled + system.adapter.hm-rpc.0 : hm-rpc : iobroker - enabled, port: 0 + system.adapter.homeconnect.0 : homeconnect : iobroker - enabled system.adapter.homekit-controller.0 : homekit-controller : iobroker - disabled system.adapter.ical.0 : ical : iobroker - enabled + system.adapter.influxdb.0 : influxdb : iobroker - enabled, port: 8086 + system.adapter.iot.0 : iot : iobroker - enabled + system.adapter.iqontrol.0 : iqontrol : iobroker - enabled + system.adapter.javascript.0 : javascript : iobroker - enabled + system.adapter.jeelink.0 : jeelink : iobroker - enabled + system.adapter.klf200.0 : klf200 : iobroker - enabled + system.adapter.mercedesme.0 : mercedesme : iobroker - enabled system.adapter.mihome-vacuum.0 : mihome-vacuum : iobroker - disabled, port: 54321 + system.adapter.modbus.0 : modbus : iobroker - enabled + system.adapter.mqtt.0 : mqtt : iobroker - enabled, port: 1883, bind: 192.168.12.219 system.adapter.node-red.0 : node-red : iobroker - disabled, port: 1880, bind: 0.0.0.0 + system.adapter.openknx.0 : openknx : iobroker - enabled + system.adapter.pushover.0 : pushover : iobroker - enabled + system.adapter.pvforecast.0 : pvforecast : iobroker - enabled + system.adapter.selverf.0 : selverf : iobroker - enabled + system.adapter.shelly.0 : shelly : iobroker - enabled, port: 1895, bind: 192.168.12.219 + system.adapter.shuttercontrol.0 : shuttercontrol : iobroker - enabled + system.adapter.sma-em.0 : sma-em : iobroker - enabled + system.adapter.smartcontrol.0 : smartcontrol : iobroker - enabled + system.adapter.sonoff.0 : sonoff : iobroker - enabled, port: 1884, bind: 0.0.0.0 + system.adapter.tankerkoenig.0 : tankerkoenig : iobroker - enabled + system.adapter.telegram.0 : telegram : iobroker - enabled, port: 8443, bind: 0.0.0.0 + system.adapter.text2command.0 : text2command : iobroker - enabled + system.adapter.tr-064.0 : tr-064 : iobroker - enabled + system.adapter.unifi.0 : unifi : iobroker - enabled system.adapter.vis-2-widgets-material.0 : vis-2-widgets-material: iobroker - enabled system.adapter.vis-2.0 : vis-2 : iobroker - disabled + system.adapter.web.0 : web : iobroker - enabled, port: 8082, bind: 0.0.0.0, run as: admin + system.adapter.yahka.0 : yahka : iobroker - enabled + system.adapter.yamaha.0 : yamaha : iobroker - enabled + system.adapter.zigbee.1 : zigbee : iobroker - enabled, port: tcp://192.168.12.212:6638 -
RE: Test Alpha Homekit-Controller 0.0.xposted in Tester
@apollon77
OK, also nochmal...Nachdem ich den Adapter über die Shell gestartet hatte passierte im Log erstmal gar nichts.
Darufhin habe ich mal den Knopf am Eve gedrückt um ihn aufzuwecken. Wenn ich es richtig interpretiere hat er sich dann auch im Adapter kurz gemeldet.
Beim nachfolgenden Identifizieren kam jedoch prompt die bekannte Fehlermeldung.iobroker@iobroker:~$ DEBUG=hap* node /opt/iobroker/node_modules/iobroker.homekit-controller/build/main.js 0 --debug --logs 2022-03-17 06:11:29.897 - debug: homekit-controller.0 (23910) Redis Objects: Use Redis connection: 127.0.0.1:9001 2022-03-17 06:11:29.922 - debug: homekit-controller.0 (23910) Objects client ready ... initialize now 2022-03-17 06:11:29.923 - debug: homekit-controller.0 (23910) Objects create System PubSub Client 2022-03-17 06:11:29.924 - debug: homekit-controller.0 (23910) Objects create User PubSub Client 2022-03-17 06:11:29.957 - debug: homekit-controller.0 (23910) Objects client initialize lua scripts 2022-03-17 06:11:29.959 - debug: homekit-controller.0 (23910) Objects connected to redis: 127.0.0.1:9001 2022-03-17 06:11:29.975 - debug: homekit-controller.0 (23910) Redis States: Use Redis connection: 127.0.0.1:6379 2022-03-17 06:11:29.977 - debug: homekit-controller.0 (23910) States create System PubSub Client 2022-03-17 06:11:29.978 - debug: homekit-controller.0 (23910) States create User PubSub Client 2022-03-17 06:11:29.980 - debug: homekit-controller.0 (23910) States connected to redis: 127.0.0.1:6379 2022-03-17 06:11:29.991 - debug: homekit-controller.0 (23910) Plugin sentry Initialize Plugin (enabled=true) 2022-03-17 06:11:30.043 - error: homekit-controller.0 (23910) adapter disabled 2022-03-17 06:11:30.085 - info: homekit-controller.0 (23910) starting. Version 0.4.3 (non-npm: Apollon77/ioBroker.homekit-controller#b7c7f7174ee7700864d870c2125c4d00aba85aa5) in /opt/iobroker/node_modules/iobroker.homekit-controller, node: v14.19.0, js-controller: 4.0.21 2022-03-17 06:11:30.160 - debug: homekit-controller.0 (23910) state homekit-controller.0.info.connection changed: false (ack = true) 2022-03-17 06:11:30.164 - debug: homekit-controller.0 (23910) Init 1 known devices without discovery ... 2022-03-17 06:11:30.164 - debug: homekit-controller.0 (23910) Init BLE-6E:B1:4A:68:AA:BB as known device 2022-03-17 06:11:30.165 - info: homekit-controller.0 (23910) BLE-6E:B1:4A:68:AA:BB (Eve Degree 5980) found without pairing data but available for pairing: Create basic objects 2022-03-17 06:11:30.165 - debug: homekit-controller.0 (23910) Service: {"name":"Eve Degree 5980","CoID":76,"TY":6,"AIL":49,"SF":1,"DeviceID":"6e:b1:4a:68:aa:bb","ACID":10,"GSN":6,"CN":3,"CV":2,"c#":3,"id":"6e:b1:4a:68:aa:bb","ci":10,"availableToPair":true} 2022-03-17 06:11:30.174 - debug: homekit-controller.0 (23910) state homekit-controller.0.BLE-6E:B1:4A:68:AA:BB.info.connectionType changed: BLE (ack = true) 2022-03-17 06:11:30.177 - debug: homekit-controller.0 (23910) state homekit-controller.0.BLE-6E:B1:4A:68:AA:BB.info.id changed: 6e:b1:4a:68:aa:bb (ack = true) 2022-03-17 06:11:30.181 - debug: homekit-controller.0 (23910) state homekit-controller.0.BLE-6E:B1:4A:68:AA:BB.info.connected changed: false (ack = true) 2022-03-17 06:11:30.186 - debug: homekit-controller.0 (23910) state homekit-controller.0.BLE-6E:B1:4A:68:AA:BB.admin.isPaired changed: false (ack = true) 2022-03-17 06:11:30.190 - debug: homekit-controller.0 (23910) state homekit-controller.0.BLE-6E:B1:4A:68:AA:BB.info.lastDiscovered changed: 1647493890166 (ack = true) 2022-03-17 06:14:23.793 - debug: homekit-controller.0 (23910) Message getDiscoveredDevices received: {"command":"getDiscoveredDevices","message":null,"from":"system.adapter.admin.0","callback":{"message":null,"id":169,"ack":false,"time":1647494063792},"_id":67504347}) 2022-03-17 06:14:23.794 - debug: homekit-controller.0 (23910) Response to Command getDiscoveredDevices: {"success":true,"error":false,"devices":[{"id":"BLE-6E:B1:4A:68:AA:BB","serviceType":"BLE","connected":false,"discovered":true,"availableToPair":true,"discoveredName":"Eve Degree 5980","discoveredCategory":"Sensor","pairedWithThisInstance":false}]} 2022-03-17 06:15:33.249 - debug: homekit-controller.0 (23910) Message identify received: {"command":"identify","message":{"deviceId":"BLE-6E:B1:4A:68:AA:BB"},"from":"system.adapter.admin.0","callback":{"message":{"deviceId":"BLE-6E:B1:4A:68:AA:BB"},"id":170,"ack":false,"time":1647494133248},"_id":67504348}) 2022-03-17 06:15:33.249 - debug: homekit-controller.0 (23910) Device BLE-6E:B1:4A:68:AA:BB: Identify triggered 2022-03-17 06:15:33.250 - debug: homekit-controller.0 (23910) Response to Command identify: {"success":false,"error":"Cannot identify device BLE-6E:B1:4A:68:AA:BB because of error undefined: Cannot read property 'state' of undefined"}Im hcidump gibt es aber keinen Eintrag zu dem Zeitpunkt wo ich den Eve geweckt hatte?
-
RE: Test Alpha Homekit-Controller 0.0.xposted in Tester
@apollon77
Manchmal ist es so einfach...
Hier die Logs:
log.txtiobroker@iobroker:~$ DEBUG=hap* node /opt/iobroker/node_modules/iobroker.homekit-controller/build/main.js 0 --debug --logs 2022-03-16 05:17:11.668 - debug: homekit-controller.0 (16117) Redis Objects: Use Redis connection: 127.0.0.1:9001 2022-03-16 05:17:11.708 - debug: homekit-controller.0 (16117) Objects client ready ... initialize now 2022-03-16 05:17:11.709 - debug: homekit-controller.0 (16117) Objects create System PubSub Client 2022-03-16 05:17:11.710 - debug: homekit-controller.0 (16117) Objects create User PubSub Client 2022-03-16 05:17:11.733 - debug: homekit-controller.0 (16117) Objects client initialize lua scripts 2022-03-16 05:17:11.735 - debug: homekit-controller.0 (16117) Objects connected to redis: 127.0.0.1:9001 2022-03-16 05:17:11.749 - debug: homekit-controller.0 (16117) Redis States: Use Redis connection: 127.0.0.1:6379 2022-03-16 05:17:11.751 - debug: homekit-controller.0 (16117) States create System PubSub Client 2022-03-16 05:17:11.751 - debug: homekit-controller.0 (16117) States create User PubSub Client 2022-03-16 05:17:11.754 - debug: homekit-controller.0 (16117) States connected to redis: 127.0.0.1:6379 2022-03-16 05:17:11.766 - debug: homekit-controller.0 (16117) Plugin sentry Initialize Plugin (enabled=true) 2022-03-16 05:17:11.818 - error: homekit-controller.0 (16117) adapter disabled 2022-03-16 05:17:11.866 - info: homekit-controller.0 (16117) starting. Version 0.4.3 (non-npm: Apollon77/ioBroker.homekit-controller#b7c7f7174ee7700864d870c2125c4d00aba85aa5) in /opt/iobroker/node_modules/iobroker.homekit-controller, node: v14.19.0, js-controller: 4.0.21 2022-03-16 05:17:11.936 - debug: homekit-controller.0 (16117) state homekit-controller.0.info.connection changed: false (ack = true) 2022-03-16 05:17:11.940 - debug: homekit-controller.0 (16117) Init 1 known devices without discovery ... 2022-03-16 05:17:11.940 - debug: homekit-controller.0 (16117) Init BLE-6E:B1:4A:68:AA:BB as known device 2022-03-16 05:17:11.940 - info: homekit-controller.0 (16117) BLE-6E:B1:4A:68:AA:BB (Eve Degree 5980) found without pairing data but available for pairing: Create basic objects 2022-03-16 05:17:11.941 - debug: homekit-controller.0 (16117) Service: {"name":"Eve Degree 5980","CoID":76,"TY":6,"AIL":49,"SF":1,"DeviceID":"6e:b1:4a:68:aa:bb","ACID":10,"GSN":6,"CN":3,"CV":2,"c#":3,"id":"6e:b1:4a:68:aa:bb","ci":10,"availableToPair":true} 2022-03-16 05:17:11.952 - debug: homekit-controller.0 (16117) state homekit-controller.0.BLE-6E:B1:4A:68:AA:BB.info.connectionType changed: BLE (ack = true) 2022-03-16 05:17:11.955 - debug: homekit-controller.0 (16117) state homekit-controller.0.BLE-6E:B1:4A:68:AA:BB.info.id changed: 6e:b1:4a:68:aa:bb (ack = true) 2022-03-16 05:17:11.958 - debug: homekit-controller.0 (16117) state homekit-controller.0.BLE-6E:B1:4A:68:AA:BB.info.connected changed: false (ack = true) 2022-03-16 05:17:11.963 - debug: homekit-controller.0 (16117) state homekit-controller.0.BLE-6E:B1:4A:68:AA:BB.admin.isPaired changed: false (ack = true) 2022-03-16 05:17:11.967 - debug: homekit-controller.0 (16117) state homekit-controller.0.BLE-6E:B1:4A:68:AA:BB.info.lastDiscovered changed: 1647404231941 (ack = true) 2022-03-16 05:17:29.918 - debug: homekit-controller.0 (16117) Message getDiscoveredDevices received: {"command":"getDiscoveredDevices","message":null,"from":"system.adapter.admin.0","callback":{"message":null,"id":119,"ack":false,"time":1647404249917},"_id":67504295}) 2022-03-16 05:17:29.919 - debug: homekit-controller.0 (16117) Response to Command getDiscoveredDevices: {"success":true,"error":false,"devices":[{"id":"BLE-6E:B1:4A:68:AA:BB","serviceType":"BLE","connected":false,"discovered":true,"availableToPair":true,"discoveredName":"Eve Degree 5980","discoveredCategory":"Sensor","pairedWithThisInstance":false}]} 2022-03-16 05:17:35.645 - debug: homekit-controller.0 (16117) Message identify received: {"command":"identify","message":{"deviceId":"BLE-6E:B1:4A:68:AA:BB"},"from":"system.adapter.admin.0","callback":{"message":{"deviceId":"BLE-6E:B1:4A:68:AA:BB"},"id":120,"ack":false,"time":1647404255644},"_id":67504296}) 2022-03-16 05:17:35.645 - debug: homekit-controller.0 (16117) Device BLE-6E:B1:4A:68:AA:BB: Identify triggered 2022-03-16 05:17:35.646 - debug: homekit-controller.0 (16117) Response to Command identify: {"success":false,"error":"Cannot identify device BLE-6E:B1:4A:68:AA:BB because of error undefined: Cannot read property 'state' of undefined"} ^Ciobroker@iobroker:~$ DEBUG=hap* node /opt/iobroker/node_modules/iobroker.homekit-controller/build/main.js 0 --debug --logs 2022-03-16 05:19:05.630 - debug: homekit-controller.0 (16134) Redis Objects: Use Redis connection: 127.0.0.1:9001 2022-03-16 05:19:05.650 - debug: homekit-controller.0 (16134) Objects client ready ... initialize now 2022-03-16 05:19:05.656 - debug: homekit-controller.0 (16134) Objects create System PubSub Client 2022-03-16 05:19:05.657 - debug: homekit-controller.0 (16134) Objects create User PubSub Client 2022-03-16 05:19:05.688 - debug: homekit-controller.0 (16134) Objects client initialize lua scripts 2022-03-16 05:19:05.690 - debug: homekit-controller.0 (16134) Objects connected to redis: 127.0.0.1:9001 2022-03-16 05:19:05.703 - debug: homekit-controller.0 (16134) Redis States: Use Redis connection: 127.0.0.1:6379 2022-03-16 05:19:05.705 - debug: homekit-controller.0 (16134) States create System PubSub Client 2022-03-16 05:19:05.706 - debug: homekit-controller.0 (16134) States create User PubSub Client 2022-03-16 05:19:05.708 - debug: homekit-controller.0 (16134) States connected to redis: 127.0.0.1:6379 2022-03-16 05:19:05.720 - debug: homekit-controller.0 (16134) Plugin sentry Initialize Plugin (enabled=true) 2022-03-16 05:19:05.770 - error: homekit-controller.0 (16134) adapter disabled 2022-03-16 05:19:05.824 - info: homekit-controller.0 (16134) starting. Version 0.4.3 (non-npm: Apollon77/ioBroker.homekit-controller#b7c7f7174ee7700864d870c2125c4d00aba85aa5) in /opt/iobroker/node_modules/iobroker.homekit-controller, node: v14.19.0, js-controller: 4.0.21 2022-03-16 05:19:05.893 - debug: homekit-controller.0 (16134) state homekit-controller.0.info.connection changed: false (ack = true) 2022-03-16 05:19:05.897 - debug: homekit-controller.0 (16134) Init 1 known devices without discovery ... 2022-03-16 05:19:05.897 - debug: homekit-controller.0 (16134) Init BLE-6E:B1:4A:68:AA:BB as known device 2022-03-16 05:19:05.898 - info: homekit-controller.0 (16134) BLE-6E:B1:4A:68:AA:BB (Eve Degree 5980) found without pairing data but available for pairing: Create basic objects 2022-03-16 05:19:05.899 - debug: homekit-controller.0 (16134) Service: {"name":"Eve Degree 5980","CoID":76,"TY":6,"AIL":49,"SF":1,"DeviceID":"6e:b1:4a:68:aa:bb","ACID":10,"GSN":6,"CN":3,"CV":2,"c#":3,"id":"6e:b1:4a:68:aa:bb","ci":10,"availableToPair":true} 2022-03-16 05:19:05.909 - debug: homekit-controller.0 (16134) state homekit-controller.0.BLE-6E:B1:4A:68:AA:BB.info.connectionType changed: BLE (ack = true) 2022-03-16 05:19:05.913 - debug: homekit-controller.0 (16134) state homekit-controller.0.BLE-6E:B1:4A:68:AA:BB.info.id changed: 6e:b1:4a:68:aa:bb (ack = true) 2022-03-16 05:19:05.915 - debug: homekit-controller.0 (16134) state homekit-controller.0.BLE-6E:B1:4A:68:AA:BB.info.connected changed: false (ack = true) 2022-03-16 05:19:05.920 - debug: homekit-controller.0 (16134) state homekit-controller.0.BLE-6E:B1:4A:68:AA:BB.admin.isPaired changed: false (ack = true) 2022-03-16 05:19:05.923 - debug: homekit-controller.0 (16134) state homekit-controller.0.BLE-6E:B1:4A:68:AA:BB.info.lastDiscovered changed: 1647404345899 (ack = true) 2022-03-16 05:19:30.853 - debug: homekit-controller.0 (16134) Message getDiscoveredDevices received: {"command":"getDiscoveredDevices","message":null,"from":"system.adapter.admin.0","callback":{"message":null,"id":121,"ack":false,"time":1647404370852},"_id":67504297}) 2022-03-16 05:19:30.853 - debug: homekit-controller.0 (16134) Response to Command getDiscoveredDevices: {"success":true,"error":false,"devices":[{"id":"BLE-6E:B1:4A:68:AA:BB","serviceType":"BLE","connected":false,"discovered":true,"availableToPair":true,"discoveredName":"Eve Degree 5980","discoveredCategory":"Sensor","pairedWithThisInstance":false}]} 2022-03-16 05:19:32.854 - debug: homekit-controller.0 (16134) Message identify received: {"command":"identify","message":{"deviceId":"BLE-6E:B1:4A:68:AA:BB"},"from":"system.adapter.admin.0","callback":{"message":{"deviceId":"BLE-6E:B1:4A:68:AA:BB"},"id":122,"ack":false,"time":1647404372853},"_id":67504298}) 2022-03-16 05:19:32.854 - debug: homekit-controller.0 (16134) Device BLE-6E:B1:4A:68:AA:BB: Identify triggered 2022-03-16 05:19:32.855 - debug: homekit-controller.0 (16134) Response to Command identify: {"success":false,"error":"Cannot identify device BLE-6E:B1:4A:68:AA:BB because of error undefined: Cannot read property 'state' of undefined"}
