UPDATE 31.10.: Amazon Alexa - ioBroker Skill läuft aus ?

[coyote]

Mir ist seit den letzten 2 (könnte auch 3) Versionen aufgefallen,dass mein hm-rpc.1 (wired) nach einem update/neustart nicht funktioniert. Der Adapter ist zwar grün, es werden aber keine DP's geändert. Meist fällt mir das eben erst auf, wenn mein Zigbee Licht nicht vom BWM (wired) eingeschaltet wird.
Starte ich den Adapter neu, läuft alles einwandfrei. Leider weiß ich gerade nicht, ob es jetzt am hm-rpc oder js-controller liegt.
Das Log sagt leider wenig, wo könnte ich anfangen zu suchen?

Hier nach update des js-controller und neustart:

2022-03-07 13:55:50.851 - info: mqtt.0 (484126) Client [MHI_Wintergarten] subscribes on "MHI_Wintergarten/set/#" with regex /^mqtt\.0\.MHI_Wintergarten\.set(\..*)?/
2022-03-07 13:55:50.855 - info: mqtt.0 (484126) State value to set for "mqtt.0.MHI_Wintergarten.connected" has to be type "string" but received type "number"
2022-03-07 13:55:51.469 - warn: zigbee.0 (484023) DeviceAvailability:Failed to ping 0xec1bbdfffxcv4bd6 TS011F
2022-03-07 13:55:51.567 - info: hm-rpc.1 (484156) Plugin sentry Sentry Plugin disabled for this process because sending of statistic data is disabled for the system
2022-03-07 13:55:51.622 - info: hm-rpc.1 (484156) starting. Version 1.15.8 in /opt/iobroker/node_modules/iobroker.hm-rpc, node: v14.19.0, js-controller: 4.0.19
2022-03-07 13:55:51.732 - warn: zigbee.0 (484023) DeviceAvailability:Failed to ping 0x847127fffedeae6c TRADFRI control outlet
2022-03-07 13:55:51.786 - info: shelly.0 (484065) [MQTT] Device 192.168.59.14 (shellyswitch25 / shellyswitch25-C45BBE7750DE / SHSW-25#C45BBE8850DE#1) connected! Polltime set to 5 sec.
2022-03-07 13:55:51.877 - info: mqtt.0 (484126) Client [frigate] connected with secret 1646657751877_2372
2022-03-07 13:55:51.880 - info: mqtt.0 (484126) Client [frigate] subscribes on "frigate/#" with regex /^frigate(\..*)?/
2022-03-07 13:55:51.881 - info: mqtt.0 (484126) Client [frigate] subscribes on "frigate/#" with regex /^mqtt\.0\.frigate(\..*)?/
2022-03-07 13:55:52.480 - info: hm-rpc.1 (484156) xmlrpc server is trying to listen on 192.168.66.68:2002
2022-03-07 13:55:52.481 - info: hm-rpc.1 (484156) xmlrpc client is trying to connect to 192.168.66.36:2000/ with ["http://192.168.66.68:2002","ioBroker:hm-rpc.1:024a6bfca93419bbe85212f744a95442"]
2022-03-07 13:55:52.525 - info: hm-rpc.1 (484156) xmlrpc <- system.listMethods ["ioBroker:hm-rpc.1:024a6bfca93419bbe85212f744a95442"]
2022-03-07 13:55:52.536 - info: hm-rpc.1 (484156) xmlrpc <- listDevices ["ioBroker:hm-rpc.1:024a6bfca93419bbe85212f744a95442"]
2022-03-07 13:55:52.848 - info: hm-rpc.1 (484156) xmlrpc -> 242 devices
2022-03-07 13:55:52.881 - info: hm-rpc.1 (484156) Connected
2022-03-07 13:55:53.395 - info: sonoff.0 (484076) Client [Sonoff4ch_2] connected with secret 1646677553393_4879
2022-03-07 13:55:53.927 - info: sonoff.0 (484076) Client [Sonoff_DualR2] connected with secret 164688973926_3869

Und dann eben nach neustart des hm-rpc Adapters bzw nur die hm-rpc.1 wired Instanz:

2022-03-07 19:01:50.212 - info: smartmeter.0 (484111) Received 7 values, 3 updated
2022-03-07 19:03:34.425 - info: host.ioBroker stopInstance system.adapter.hm-rpc.1 (force=false, process=true)
2022-03-07 19:03:34.430 - info: host.ioBroker stopInstance system.adapter.hm-rpc.1 send kill signal
2022-03-07 19:03:34.428 - info: hm-rpc.1 (484156) Got terminate signal TERMINATE_YOURSELF
2022-03-07 19:03:34.663 - info: hm-rpc.1 (484156) xmlrpc -> 192.168.66.36:2000/ init ["http://192.168.66.68:2002",""]
2022-03-07 19:03:34.672 - info: hm-rpc.1 (484156) Disconnected
2022-03-07 19:03:34.717 - info: hm-rpc.1 (484156) terminating
2022-03-07 19:03:34.734 - info: hm-rpc.1 (484156) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
2022-03-07 19:03:35.528 - info: host.ioBroker instance system.adapter.hm-rpc.1 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
2022-03-07 19:03:38.192 - info: host.ioBroker instance system.adapter.hm-rpc.1 started with pid 511752
2022-03-07 19:03:39.827 - info: hm-rpc.1 (511752) Plugin sentry Sentry Plugin disabled for this process because sending of statistic data is disabled for the system
2022-03-07 19:03:40.129 - info: hm-rpc.1 (511752) starting. Version 1.15.8 in /opt/iobroker/node_modules/iobroker.hm-rpc, node: v14.19.0, js-controller: 4.0.19
2022-03-07 19:03:41.007 - info: hm-rpc.1 (511752) xmlrpc server is trying to listen on 192.168.66.68:2002
2022-03-07 19:03:41.008 - info: hm-rpc.1 (511752) xmlrpc client is trying to connect to 192.168.66.36:2000/ with ["http://192.168.66.68:2002","ioBroker:hm-rpc.1:dde1b544f7f99151fe1ff58812f7f12d"]
2022-03-07 19:03:41.028 - info: hm-rpc.1 (511752) xmlrpc <- system.listMethods ["ioBroker:hm-rpc.1:dde1b544f7f99151fe1ff58812f7f12d"]
2022-03-07 19:03:41.036 - info: hm-rpc.1 (511752) xmlrpc <- listDevices ["ioBroker:hm-rpc.1:dde1b544f7f99151fe1ff58812f7f12d"]
2022-03-07 19:03:41.359 - info: hm-rpc.1 (511752) xmlrpc -> 242 devices
2022-03-07 19:03:41.389 - info: hm-rpc.1 (511752) Connected

[apollon77]

@coyote Bitte hmrpc issue machen

[coyote]

@apollon77 ok, mach ich. Versuche morgen mal, ob es auch auftritt, wenn ich iobroker "nur" neustarte.

[apollon77]

Hi All,

gerade ist der js-controller 4.0.19 in Stable gegangen, welche noch letzte Fixes enthält

[Fabio]

@apollon77 vielen Dank 4.0.19 ist Problemlos gelaufen.

[bahnuhr]

upgrade von 4.0.18 auf 4.0.19 auf master und slave ohne Probleme.

Beim Master habe ich nur folgende Hinweise bekommen:

- Ignoring Directory "mnt" because officially not created as meta object. Please remove directory!
- Ignoring Directory "vis.01_Sound" because officially not created as meta object. Please remove directory!

Den Punkt wie unter #2 beschrieben: "iob upload all" hatte ich bei 4.0.18 schon aufgeführt.

Sind aber eigen angelegte Verzeichnisse.

kann/muss ich da irgendwas tun ?

[Nashra]

@apollon77
update von 4.0.18 auf 4.0.19 ohne Probleme

[Siggi0904]

@apollon77 ich habe von 4.0.15 nach 4.0.19 migriert.
Das war auch mein erstes Upgrade mit der JSONL DB.
Läuft dann doch einiges anders.

Ich habe folgende Meldungen erhalten:

41 packages are looking for funding
  run `npm fund` for details

Muss/soll ich da was machen? oder ignorieren?

Und dann ist da noch eine Redis Meldung.
Ich habe doch gar kein Redis.

Successfully migrated 8203 objects to Redis Sets

[Michael Schmitt]

@apollon77
update auf 4.0.19 ohne Probleme durch gelaufen

[Rushmed]

@siggi0904 Bei mir auch:

137 packages are looking for funding
  run `npm fund` for details

mÜssen wir hier etwas unternehmen?

root@Smartazamba:/opt/iobroker# npm fund
iobroker.inst@3.0.0
├─┬ https://github.com/sponsors/jaredhanson
│ └── passport@0.5.2
├─┬ https://github.com/sponsors/feross
│ └── safe-buffer@5.2.1, base64-js@1.5.1, buffer@5.7.1, ieee754@1.2.1, simple-get@4.0.1, simple-concat@1.0.1, buffer@6.0.3, run-parallel@1.2.0, queue-microtask@1.2.3
├─┬ https://www.patreon.com/feross
│ └── safe-buffer@5.2.1, base64-js@1.5.1, buffer@5.7.1, ieee754@1.2.1, simple-get@4.0.1, simple-concat@1.0.1, buffer@6.0.3, run-parallel@1.2.0, queue-microtask@1.2.3
├─┬ https://feross.org/support
│ └── safe-buffer@5.2.1, base64-js@1.5.1, buffer@5.7.1, ieee754@1.2.1, simple-get@4.0.1, simple-concat@1.0.1, buffer@6.0.3, run-parallel@1.2.0, queue-microtask@1.2.3
├─┬ https://github.com/sponsors/RubenVerborgh
│ └── follow-redirects@1.14.9, follow-redirects@1.14.7
├─┬ https://github.com/sponsors/ljharb
│ └── qs@6.9.7, qs@6.9.6, is-nan@1.3.2, call-bind@1.0.2, get-intrinsic@1.1.1, has-symbols@1.0.2, es-abstract@1.19.1, es-to-primitive@1.2.1, get-symbol-description@1.0.0, is-callable@1.2.4, is-negative-zero@2.0.2, is-regex@1.1.4, is-shared-array-buffer@1.0.1, is-string@1.0.7, is-weakref@1.0.2, object-inspect@1.12.0, object.assign@4.1.2, string.prototype.trimend@1.0.4, string.prototype.trimstart@1.0.4, unbox-primitive@1.0.1, is-date-object@1.0.5, is-symbol@1.0.4, has-tostringtag@1.0.0, side-channel@1.0.4, has-bigints@1.0.1, which-boxed-primitive@1.0.2, is-bigint@1.0.4, is-boolean-object@1.1.2, is-number-object@1.0.6, deep-equal@1.1.1, is-arguments@1.1.1, object-is@1.1.5, regexp.prototype.flags@1.4.1, resolve@1.22.0, is-core-module@2.8.1, supports-preserve-symlinks-flag@1.0.0
├─┬ https://github.com/sponsors/sindresorhus
│ └── is-plain-obj@3.0.0, is-stream@2.0.1, decompress-response@6.0.0, mimic-response@3.1.0, make-dir@3.1.0, mimic-response@2.1.0, escape-string-regexp@4.0.0, strip-json-comments@3.1.1, globals@13.12.1, import-fresh@3.3.0, type-fest@0.20.2, p-throttle@4.1.1, get-stream@6.0.1, onetime@5.1.2, hex-rgb@4.3.0, globby@11.1.0, import-local@3.1.0, ansi-escapes@4.3.2, terminal-link@2.1.1, p-limit@2.3.0, type-fest@0.21.3, camelcase@6.3.0, parse-json@5.2.0
├─┬ https://github.com/sponsors/jonschlinkert
│ └── picomatch@2.3.1, set-value@4.1.0
├─┬ https://github.com/sponsors/epoberezkin
│ └── ajv@6.12.6, ajv@8.10.0
├─┬ https://paypal.me/naturalintelligence
│ └── fast-xml-parser@3.21.1
├─┬ https://opencollective.com/serialport/donate
│ └── serialport@9.2.8, @serialport/binding-mock@9.2.4, @serialport/bindings@9.2.8, @serialport/parser-byte-length@9.2.4, @serialport/parser-cctalk@9.2.4, @serialport/parser-delimiter@9.2.4, @serialport/parser-inter-byte-timeout@9.2.4, @serialport/parser-readline@9.2.4, @serialport/parser-ready@9.2.4, @serialport/parser-regex@9.2.4, @serialport/stream@9.2.4, @serialport/binding-abstract@9.2.3
├─┬ https://github.com/sponsors/isaacs
│ └── rimraf@3.0.2, glob@7.2.0
├─┬ https://opencollective.com/eslint
│ └── eslint@7.32.0, eslint@8.8.0, eslint@8.9.0
├─┬ https://github.com/chalk/chalk?sponsor=1
│ └── chalk@4.1.2
├─┬ https://github.com/sponsors/mysticatea
│ └── eslint-utils@2.1.0, regexpp@3.2.0, eslint-utils@3.0.0
├─┬ https://github.com/chalk/ansi-styles?sponsor=1
│ └── ansi-styles@4.3.0, ansi-styles@5.2.0
├─┬ https://github.com/chalk/slice-ansi?sponsor=1
│ └── slice-ansi@4.0.0
├─┬ https://github.com/sponsors/derhuerst
│ └── hafas-client@5.22.2
├─┬ https://opencollective.com/node-fetch
│ └── node-fetch@3.2.0
├─┬ https://github.com/sponsors/jimmywarting
│ └── fetch-blob@3.1.4, node-domexception@1.0.0
├─┬ https://paypal.me/jimmywarting
│ └── fetch-blob@3.1.4, node-domexception@1.0.0
├─┬ https://tidelift.com/funding/github/npm/loglevel
│ └── loglevel@1.8.0
├─┬ https://www.buymeacoffee.com/systeminfo
│ └── systeminformation@5.11.2
├─┬ https://opencollective.com/libvips
│ └── sharp@0.28.1
├─┬ https://github.com/chalk/wrap-ansi?sponsor=1
│ └── wrap-ansi@7.0.0
├─┬ https://opencollective.com/ioredis
│ └── ioredis@4.28.5
├─┬ https://github.com/sindresorhus/execa?sponsor=1
│ └── execa@5.1.1
├─┬ https://paulmillr.com/funding/
│ └── chokidar@3.5.3
├─┬ https://paypal.me/jonathanschlinkert
│ └── set-value@4.1.0
├─┬ https://jonschlinkert.dev/sponsor
│ └── set-value@4.1.0
├─┬ https://ko-fi.com/killymxi
│ └── @selderee/plugin-htmlparser2@0.6.0, selderee@0.6.0, parseley@0.7.0
├─┬ https://github.com/fb55/htmlparser2?sponsor=1
│ └── htmlparser2@6.1.0
├─┬ https://github.com/sponsors/fb55
│ └── htmlparser2@6.1.0, domelementtype@2.2.0
├─┬ https://github.com/fb55/domhandler?sponsor=1
│ └── domhandler@4.2.2
├─┬ https://github.com/fb55/domutils?sponsor=1
│ └── domutils@2.8.0
├─┬ https://github.com/fb55/entities?sponsor=1
│ └── entities@2.2.0
├─┬ https://github.com/cheeriojs/dom-serializer?sponsor=1
│ └── dom-serializer@1.3.2
├─┬ https://nearley.js.org/#give-to-nearley
│ └── nearley@2.20.1
├─┬ https://opencollective.com/typescript-eslint
│ └── @typescript-eslint/eslint-plugin@5.10.2, @typescript-eslint/parser@5.10.2, @typescript-eslint/scope-manager@5.10.2, @typescript-eslint/type-utils@5.10.2, @typescript-eslint/utils@5.10.2, @typescript-eslint/types@5.10.2, @typescript-eslint/visitor-keys@5.10.2, @typescript-eslint/typescript-estree@5.10.2, @typescript-eslint/utils@5.11.0, @typescript-eslint/scope-manager@5.11.0, @typescript-eslint/types@5.11.0, @typescript-eslint/typescript-estree@5.11.0, @typescript-eslint/visitor-keys@5.11.0, @typescript-eslint/experimental-utils@5.4.0
├─┬ https://opencollective.com/core-js
│ └── core-js-compat@3.21.0
├─┬ https://opencollective.com/browserslist
│ └── browserslist@4.19.1, caniuse-lite@1.0.30001307
├─┬ https://github.com/sindresorhus/emittery?sponsor=1
│ └── emittery@0.8.1
├─┬ https://opencollective.com/babel
│ └── @babel/core@7.17.0, @babel/core@7.17.2
└─┬ https://github.com/chalk/supports-color?sponsor=1
  └── supports-color@8.1.1

[wendy2702]

@rushmed Spenden: Pakete sind auf der Suche nach Finanzierung

[apollon77]

@bahnuhr naja ... "eigen angelegte Verzeichnisse" sind blöd Hintergrund: Sie sind ggf nicht voll verwendbar ... am besten löschen bzw in 0_userdata.0 Verschieben und "iob file sync" ausführen oder passende meta.user Objekte anlegen

[apollon77]

@siggi0904 sagte in js-controller 4.0.x jetzt für alle User im STABLE!:

Läuft dann doch einiges anders.

Nein eigentlich nicht

• npm fund: ignorieren oder was spenden
• successfully migrated objects to redis sets: ignorieren ...

[marios774]

Hallo, nach dem Update kamen nun diese Fehlermeldung..
Was nun? Die Adapter scheinen alle zu laufen.

parallels@deb11iobroker:~$ iob upgrade self
Update js-controller from @3.3.22 to @4.0.19
NPM version: 6.14.16
npm install iobroker.js-controller@4.0.19 --loglevel error --unsafe-perm --prefix "/opt/iobroker" (System call)
In file included from ../../nan/nan.h:58,
                 from ../src/unix_dgram.cc:5:
/home/iobroker/.cache/node-gyp/14.19.0/include/node/node.h:793:7: warning: cast between incompatible function types from ‘void (*)(v8::Local<v8::Object>)’ to ‘node::addon_register_func’ {aka ‘void (*)(v8::Local<v8::Object>, v8::Local<v8::Value>, void*)’} [-Wcast-function-type]
  793 |       (node::addon_register_func) (regfunc),                          \
      |       ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
/home/iobroker/.cache/node-gyp/14.19.0/include/node/node.h:827:3: note: in expansion of macro ‘NODE_MODULE_X’
  827 |   NODE_MODULE_X(modname, regfunc, NULL, 0)  // NOLINT (readability/null_usage)
      |   ^~~~~~~~~~~~~
../src/unix_dgram.cc:404:1: note: in expansion of macro ‘NODE_MODULE’
  404 | NODE_MODULE(unix_dgram, Initialize)
      | ^~~~~~~~~~~
Server Objects 127.0.0.1:43698 Error from InMemDB: Error: GET-UNSUPPORTED for namespace cfg.: Data=["meta.objects.features.useSets"]
Server States 127.0.0.1:53512 Error from InMemDB: Error: GET-UNSUPPORTED for namespace meta.: Data=["meta.states.protocolVersion"]
Server Objects 127.0.0.1:43698 Error from InMemDB: Error: GET-UNSUPPORTED for namespace cfg.: Data=["meta.objects.protocolVersion"]
Server States 127.0.0.1:53514 Error from InMemDB: Error: PSUBSCRIBE-UNSUPPORTED for namespace meta.: Data=["meta.*"]
Server Objects 127.0.0.1:43698 Error from InMemDB: Error: Unknown LUA script load
Server Objects 127.0.0.1:43698 Error from InMemDB: Error: Unknown LUA script load
Server Objects 127.0.0.1:43698 Error from InMemDB: Error: Unknown LUA script load
Server Objects 127.0.0.1:43698 Error from InMemDB: Error: SET-UNSUPPORTED for namespace cfg.: Data=["meta.objects.features.useSets",{"type":"Buffer","data":[49]}]
Could not migrate objects to corresponding sets: Error SET-UNSUPPORTED for namespace cfg.: Data=["meta.objects.features.useSets",{"type":"Buffer","data":[49]}]
parallels@deb11iobroker:~$ iob fix

[Thomas Braun]

@marios774 sagte in js-controller 4.0.x jetzt für alle User im STABLE!:

Was nun?

Nix. Alles i. O.

[marios774]

@thomas-braun

Dann bin ich beruhigt... Fehlermeldungen, die ich nicht deuten kann, bringen immer so kleine Perlen auf die Stirn...

[apollon77]

@marios774 Dann liess mal ganz oben den ersten post

[oFbEQnpoLKKl6mbY5e13]

@apollon77 sagte in js-controller 4.0.x jetzt für alle User im STABLE!:

@boronsbruder Hi,

ja, die Meldungkannst Du ignorieren ... da fehlt ein Check ... Wird gerade immer geloggt auch wenn es gar keinen Fehler gab Fixen wir in der nächsten Controller Version

Ist euch das durchgegangen, denn ich erhalte die Meldung auch mit der 19er?

(Cannot set object: null)

[apollon77]

@ofbeqnpolkkl6mby5e13 ne der wurde gemeldet nachdem der 4.0.19 schon released war.

[oFbEQnpoLKKl6mbY5e13]

@apollon77

Ach so, okay.