js-controller 4.0.x jetzt für alle User im STABLE!

Thomas4170

Moin moin, ich habe auch das Update gemacht. Instanzen sind bis auf Zigbee problmlos gestartet. Ich habe imForum dann die vorgeschlagen Vorgehensweisen ausgeführt aber Zigbee blieb rot. Ich habe den Adapter dann gelöscht und neu installiert, danach startete der Zigbee-Adapter problemlos.

2022-02-26 06:06:58.295 - error: host.PI-IOBROKER Caught by controller[0]: /opt/iobroker/node_modules/zigbee-herdsman/node_modules/bindings/bindings.js:121
2022-02-26 06:06:58.296 - error: host.PI-IOBROKER Caught by controller[0]: throw e;
2022-02-26 06:06:58.296 - error: host.PI-IOBROKER Caught by controller[0]: ^
2022-02-26 06:06:58.296 - error: host.PI-IOBROKER Caught by controller[0]: Error: The module '/opt/iobroker/node_modules/zigbee-herdsman/node_modules/@serialport/bindings/build/Release/bindings.node'
2022-02-26 06:06:58.297 - error: host.PI-IOBROKER Caught by controller[0]: was compiled against a different Node.js version using
2022-02-26 06:06:58.297 - error: host.PI-IOBROKER Caught by controller[0]: NODE_MODULE_VERSION 83. This version of Node.js requires
2022-02-26 06:06:58.297 - error: host.PI-IOBROKER Caught by controller[0]: NODE_MODULE_VERSION 93. Please try re-compiling or re-installing
2022-02-26 06:06:58.297 - error: host.PI-IOBROKER Caught by controller[0]: the module (for instance, using `npm rebuild` or `npm install`).
2022-02-26 06:06:58.297 - error: host.PI-IOBROKER Caught by controller[0]: at Object.Module._extensions..node (node:internal/modules/cjs/loader:1185:18)
2022-02-26 06:06:58.298 - error: host.PI-IOBROKER Caught by controller[0]: at Module.load (node:internal/modules/cjs/loader:981:32)
2022-02-26 06:06:58.298 - error: host.PI-IOBROKER Caught by controller[0]: at Function.Module._load (node:internal/modules/cjs/loader:822:12)
2022-02-26 06:06:58.298 - error: host.PI-IOBROKER Caught by controller[0]: at Module.require (node:internal/modules/cjs/loader:1005:19)
2022-02-26 06:06:58.298 - error: host.PI-IOBROKER Caught by controller[0]: at require (node:internal/modules/cjs/helpers:102:18)
2022-02-26 06:06:58.299 - error: host.PI-IOBROKER Caught by controller[0]: at bindings (/opt/iobroker/node_modules/zigbee-herdsman/node_modules/bindings/bindings.js:112:48)
2022-02-26 06:06:58.299 - error: host.PI-IOBROKER Caught by controller[0]: at Object. (/opt/iobroker/node_modules/zigbee-herdsman/node_modules/@serialport/bindings/lib/linux.js:2:36)
2022-02-26 06:06:58.299 - error: host.PI-IOBROKER Caught by controller[0]: at Module._compile (node:internal/modules/cjs/loader:1103:14)
2022-02-26 06:06:58.299 - error: host.PI-IOBROKER Caught by controller[0]: at Object.Module._extensions..js (node:internal/modules/cjs/loader:1155:10)
2022-02-26 06:06:58.299 - error: host.PI-IOBROKER Caught by controller[0]: at Module.load (node:internal/modules/cjs/loader:981:32) {
2022-02-26 06:06:58.300 - error: host.PI-IOBROKER Caught by controller[0]: code: 'ERR_DLOPEN_FAILED'
2022-02-26 06:06:58.300 - error: host.PI-IOBROKER Caught by controller[0]: }
2022-02-26 06:06:58.300 - error: host.PI-IOBROKER instance system.adapter.zigbee.0 terminated with code 1 (JS_CONTROLLER_STOPPED)
2022-02-26 06:06:58.300 - info: host.PI-IOBROKER Rebuild for adapter system.adapter.zigbee.0 not successful in 3 tries. Adapter will not be restarted again. Please execute "npm install --production" in adapter directory manually.
2022-02-26 06:23:00.080 - info: host.PI-IOBROKER instance system.adapter.openweathermap.0 started with pid 2589
2022-02-26 06:23:01.236 - info: host.PI-IOBROKER "system.adapter.zigbee.0" disabled
2022-02-26 06:23:02.161 - info: openweathermap.0 (2589) starting. Version 0.1.0 in /opt/iobroker/node_modules/iobroker.openweathermap, node: v16.14.0, js-controller: 3.3.22
2022-02-26 06:23:03.603 - info: host.PI-IOBROKER "system.adapter.zigbee.0" enabled
2022-02-26 06:23:03.720 - info: host.PI-IOBROKER instance system.adapter.zigbee.0 started with pid 2604
2022-02-26 06:23:04.548 - error: host.PI-IOBROKER Caught by controller[0]: /opt/iobroker/node_modules/zigbee-herdsman/node_modules/bindings/bindings.js:121
2022-02-26 06:23:04.549 - error: host.PI-IOBROKER Caught by controller[0]: throw e;
2022-02-26 06:23:04.549 - error: host.PI-IOBROKER Caught by controller[0]: ^
2022-02-26 06:23:04.549 - error: host.PI-IOBROKER Caught by controller[0]: Error: The module '/opt/iobroker/node_modules/zigbee-herdsman/node_modules/@serialport/bindings/build/Release/bindings.node'
2022-02-26 06:23:04.550 - error: host.PI-IOBROKER Caught by controller[0]: was compiled against a different Node.js version using
2022-02-26 06:23:04.550 - error: host.PI-IOBROKER Caught by controller[0]: NODE_MODULE_VERSION 83. This version of Node.js requires
2022-02-26 06:23:04.550 - error: host.PI-IOBROKER Caught by controller[0]: NODE_MODULE_VERSION 93. Please try re-compiling or re-installing
2022-02-26 06:23:04.551 - error: host.PI-IOBROKER Caught by controller[0]: the module (for instance, using `npm rebuild` or `npm install`).
2022-02-26 06:23:04.551 - error: host.PI-IOBROKER Caught by controller[0]: at Object.Module._extensions..node (node:internal/modules/cjs/loader:1185:18)
2022-02-26 06:23:04.551 - error: host.PI-IOBROKER Caught by controller[0]: at Module.load (node:internal/modules/cjs/loader:981:32)
2022-02-26 06:23:04.551 - error: host.PI-IOBROKER Caught by controller[0]: at Function.Module._load (node:internal/modules/cjs/loader:822:12)
2022-02-26 06:23:04.552 - error: host.PI-IOBROKER Caught by controller[0]: at Module.require (node:internal/modules/cjs/loader:1005:19)
2022-02-26 06:23:04.552 - error: host.PI-IOBROKER Caught by controller[0]: at require (node:internal/modules/cjs/helpers:102:18)
2022-02-26 06:23:04.552 - error: host.PI-IOBROKER Caught by controller[0]: at bindings (/opt/iobroker/node_modules/zigbee-herdsman/node_modules/bindings/bindings.js:112:48)
2022-02-26 06:23:04.552 - error: host.PI-IOBROKER Caught by controller[0]: at Object. (/opt/iobroker/node_modules/zigbee-herdsman/node_modules/@serialport/bindings/lib/linux.js:2:36)
2022-02-26 06:23:04.553 - error: host.PI-IOBROKER Caught by controller[0]: at Module._compile (node:internal/modules/cjs/loader:1103:14)
2022-02-26 06:23:04.553 - error: host.PI-IOBROKER Caught by controller[0]: at Object.Module._extensions..js (node:internal/modules/cjs/loader:1155:10)
2022-02-26 06:23:04.553 - error: host.PI-IOBROKER Caught by controller[0]: at Module.load (node:internal/modules/cjs/loader:981:32) {
2022-02-26 06:23:04.553 - error: host.PI-IOBROKER Caught by controller[0]: code: 'ERR_DLOPEN_FAILED'
2022-02-26 06:23:04.553 - error: host.PI-IOBROKER Caught by controller[0]: }
2022-02-26 06:23:04.554 - error: host.PI-IOBROKER instance system.adapter.zigbee.0 terminated with code 1 (JS_CONTROLLER_STOPPED)

VG

babl

@apollon77 allerdings tauchenjetzt warnmeldungen auf nach dem update.

	ELEVATED publishToState: value generated 'false' from device 00158d0006b79823 for 'Time from last motion'
zigbee.0
	2022-02-26 09:04:37.708	warn	ELEVATED publishToState: value generated 'false' from device 00158d0006b79823 for 'Occupancy'
zigbee.0
	2022-02-26 09:04:37.707	warn	ELEVATED publishToState: message received '{"occupancy":false}' from device 00158d0006b79823 type 'RTCGQ11LM'
zigbee.0
	2022-02-26 09:03:37.709	warn	ELEVATED publishToState: value generated 'true' from device 00158d0006b79823 for 'Time from last motion'
zigbee.0
	2022-02-26 09:03:37.709	warn	ELEVATED publishToState: value generated 'true' from device 00158d0006b79823 for 'Occupancy'
zigbee.0
	2022-02-26 09:03:37.708	warn	ELEVATED publishToState: message received '{"occupancy":true}' from device 00158d0006b79823 type 'RTCGQ11LM'
zigbee.0
	2022-02-26 09:03:37.703	warn	ELEVATED publishToState: value generated '255' from device 00158d0006b79823 for 'Link quality'
zigbee.0
	2022-02-26 09:03:37.702	warn	ELEVATED publishToState: message received '{"linkquality":255}' from device 00158d0006b79823 type 'RTCGQ11LM'
zigbee.0
	2022-02-26 09:03:37.691	warn	ELEVATED publishToState: value generated '3' from device 00158d0006b79823 for 'Illuminance'
zigbee.0
	2022-02-26 09:03:37.689	warn	ELEVATED publishToState: value generated 'true' from device 00158d0006b79823 for 'Time from last motion'
zigbee.0
	2022-02-26 09:03:37.689	warn	ELEVATED publishToState: value generated 'true' from device 00158d0006b79823 for 'Occupancy'
zigbee.0
	2022-02-26 09:03:37.688	warn	ELEVATED publishToState: message received '{"occupancy":true,"illuminance":3,"illuminance_lux":3}' from device 00158d0006b79823 type 'RTCGQ11LM'
zigbee.0
	2022-02-26 09:03:37.683	warn	ELEVATED publishToState: value generated '255' from device 00158d0006b79823 for 'Link quality'
zigbee.0
	2022-02-26 09:03:37.683	warn	ELEVATED publishToState: message received '{"linkquality":255}' from device 00158d0006b79823 type 'RTCGQ11LM'
zigbee.0
	2022-02-26 09:03:35.418	warn	ELEVATED publishToState: value generated 'false' from device 00158d0006b79823 for 'Time from last motion'
zigbee.0
	2022-02-26 09:03:35.417	warn	ELEVATED publishToState: value generated 'false' from device 00158d0006b79823 for 'Occupancy'
zigbee.0
	2022-02-26 09:03:35.417	warn	ELEVATED publishToState: message received '{"occupancy":false}' from device 00158d0006b79823 type 'RTCGQ11LM'
zigbee.0
	2022-02-26 09:02:35.419	warn	ELEVATED publishToState: value generated 'true' from device 00158d0006b79823 for 'Time from last motion'
zigbee.0
	2022-02-26 09:02:35.419	warn	ELEVATED publishToState: value generated 'true' from device 00158d0006b79823 for 'Occupancy'
zigbee.0
	2022-02-26 09:02:35.418	warn	ELEVATED publishToState: message received '{"occupancy":true}' from device 00158d0006b79823 type 'RTCGQ11LM'
zigbee.0
	2022-02-26 09:02:35.413	warn	ELEVATED publishToState: value generated '255' from device 00158d0006b79823 for 'Link quality'
zigbee.0
	2022-02-26 09:02:35.412	warn	ELEVATED publishToState: message received '{"linkquality":255}' from device 00158d0006b79823 type 'RTCGQ11LM'
zigbee.0
	2022-02-26 09:02:35.398	warn	ELEVATED publishToState: value generated '3' from device 00158d0006b79823 for 'Illuminance'
zigbee.0
	2022-02-26 09:02:35.396	warn	ELEVATED publishToState: value generated 'true' from device 00158d0006b79823 for 'Time from last motion'
zigbee.0
	2022-02-26 09:02:35.396	warn	ELEVATED publishToState: value generated 'true' from device 00158d0006b79823 for 'Occupancy'
zigbee.0
	2022-02-26 09:02:35.395	warn	ELEVATED publishToState: message received '{"occupancy":true,"illuminance":3,"illuminance_lux":3}' from device 00158d0006b79823 type 'RTCGQ11LM'
zigbee.0
	2022-02-26 09:02:35.389	warn	ELEVATED publishToState: value generated '255' from device 00158d0006b79823 for 'Link quality'
zigbee.0
	2022-02-26 09:02:35.389	warn	ELEVATED publishToState: message received '{"linkquality":255}' from device 00158d0006b79823 type 'RTCGQ11LM'

Was kann ich tun?

apollon77

@thomas4170 haste mal bitte das ganze log. Hier ist nur der letzte rebuild try drin. Würde gern mal alle drei sehen. Also am besten ganzen log ab start des Controllers. Danke

apollon77

@babl am besten bei zigbee fragen Bzw da github issue anlegen - oder @arteck ne Idee?. Hat nix mit dem controller zu tun.

David G.

@apollon77

Das war es. Hab ich gestern schon im Log gesehen. Hatte aber erst Angst, daß was zerschossen wäre ^^.

babl

@apollon77 Alles gut, Problem gelöst, die ID Nummer des Zigbee Geräts war im Debug Messages vom Zigbee Adapter angegeben und daher kamen die Meldungen, also alles gut.

Schimi

@muchul

Habe es nochmal editiert.... als ich es "löschen" wollte waren noch keine Antworten da

Wobei ich es vorher besser fand, als man es einfach auswählen konnte (gerade wenn man mit dem Handy drauf zugegriffen hat)..

Jetzt kann man auch beide Repositories auswählen.... ich denke das es mehr Verwirrung stiften wird...

Nashra

Vielen Dank an alle Beteiligten, install ohne Probleme

jensven

Habe auch gerade nen Update von 3.3.22 auf 4.0.15 gemacht
Es läuft alles auch soweit, bis auf die bekannten error Probleme von den objekten.

Aber während des Updates gab es folgende Errors:

pi@raspberrypi:~ $ iob upgrade self
Update js-controller from @3.3.22 to @4.0.15
NPM version: 6.14.16
npm install iobroker.js-controller@4.0.15 --loglevel error --unsafe-perm --prefix "/opt/iobroker" (System call)
In file included from ../src/unix_dgram.cc:5:
../../nan/nan.h: In function ‘void Nan::AsyncQueueWorker(Nan::AsyncWorker*)’:
../../nan/nan.h:2298:62: warning: cast between incompatible function types from ‘void (*)(uv_work_t*)’ {aka ‘void (*)(uv_work_s*)’} to ‘uv_after_work_cb’ {aka ‘void (*)(uv_work_s*, int)’} [-Wcast-function-type]
     , reinterpret_cast<uv_after_work_cb>(AsyncExecuteComplete)
                                                              ^
In file included from ../../nan/nan.h:54,
                 from ../src/unix_dgram.cc:5:
../src/unix_dgram.cc: At global scope:
/home/iobroker/.cache/node-gyp/14.19.0/include/node/node.h:793:43: 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]
       (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’
   NODE_MODULE_X(modname, regfunc, NULL, 0)  // NOLINT (readability/null_usage)
   ^~~~~~~~~~~~~
../src/unix_dgram.cc:404:1: note: in expansion of macro ‘NODE_MODULE’
 NODE_MODULE(unix_dgram, Initialize)
 ^~~~~~~~~~~
Server Objects 127.0.0.1:45710 Error from InMemDB: Error: GET-UNSUPPORTED for namespace cfg.: Data=["meta.objects.features.useSets"]
Server States 127.0.0.1:58302 Error from InMemDB: Error: GET-UNSUPPORTED for namespace meta.: Data=["meta.states.protocolVersion"]
Server Objects 127.0.0.1:45710 Error from InMemDB: Error: GET-UNSUPPORTED for namespace cfg.: Data=["meta.objects.protocolVersion"]
Server States 127.0.0.1:58304 Error from InMemDB: Error: PSUBSCRIBE-UNSUPPORTED for namespace meta.: Data=["meta.*"]
Server Objects 127.0.0.1:45710 Error from InMemDB: Error: Unknown LUA script load
Server Objects 127.0.0.1:45710 Error from InMemDB: Error: Unknown LUA script load
Server Objects 127.0.0.1:45710 Error from InMemDB: Error: Unknown LUA script load
Server Objects 127.0.0.1:45710 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 names pace cfg.: Data=["meta.objects.features.useSets",{"type":"Buffer","data":[49]}]

Sollte man da was machen? Hat das was mit den bekannten Problemen zu tun ?

apollon77

@jensven alles gut. Sind übliche Warnungen von einem Paket. Ignorieren

Fabio

@apollon77 vielen Dank an euch. Update war erfolgreich keine Probleme.

Einstein67

@apollon77 Ich hab eine komplette Neuinstallation mit dem Script vom 13.2. durchgeführt (Debian11 und Node 16).

JS-Controller, Admin, Backitup und Discovery wurden in der aktuellsten Version installiert.

Backup (Grafana, InfluxDB und IOBroker) wieder hergestellt.

Keine Probleme bei Installation und Restore, alles läuft perfekt. TOP!!

Edit: Auch das Popup (jsonl Konvertierung) ist weg!

Meister Mopper

@apollon77
Nach dem upgrade und Neustart des ioBroker auf meinem master startete der admin-Adapter nicht mit.

Mit iobroker start admin lief's wieder rund

liv-in-sky

Danke für's entwickeln - nach update läuft alles soweit - keine fehler

vis scheint schneller beim laden der views zu sein

bahnuhr

Hallo,

bekomme nun folgende warn und error im log:

telegram.0
2022-02-26 11:10:34.726	error	getMe (reconnect #0) Error:Error: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org

dwd.0
2022-02-26 11:10:33.508	error	Empty or invalid JSON: Cannot read JSON file: Error: getaddrinfo EAI_AGAIN www.dwd.de

hm-rega.0
2022-02-26 11:10:29.731	warn	Script "!# programs.fn 1.3 !# Dieses Script gibt eine Liste der Programme als JSON Strin" ignored, because still pending.

hm-rega.0
2022-02-26 11:10:29.689	warn	Script "!# polling.fn 1.3 !# !# Dieses Script gibt die Werte aller Systemvariablen als J" ignored, because still pending.

telegram.1
2022-02-26 11:10:27.301	error	getMe (reconnect #0) Error:Error: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org

javascript.0
2022-02-26 11:10:20.101	error	Request error: Error: getaddrinfo EAI_AGAIN www.bild.de

javascript.0
2022-02-26 11:10:20.100	error	script.js.Scripte.Sonstige.RSS-Feed: {'errno':-3001,'code':'EAI_AGAIN','syscall':'getaddrinfo','hostname':'www.bild.de'}
host.VM-iobroker
2022-02-26 11:10:17.650	error	instance system.adapter.hm-rpc.1 terminated with code 6 (UNCAUGHT_EXCEPTION)

hm-rpc.1
2022-02-26 11:10:17.016	warn	Terminated (UNCAUGHT_EXCEPTION): Without reason

hm-rpc.1
2022-02-26 11:10:17.013	error	Cannot call init: [xmlrpc_bin://192.168.243.12:8701, ""] Cannot call write after a stream was destroyed

hm-rpc.1
2022-02-26 11:10:17.000	error	Exception-Code: ETIMEDOUT: read ETIMEDOUT

hm-rpc.1
2022-02-26 11:10:16.999	error	Error: read ETIMEDOUT at TCP.onStreamRead (internal/stream_base_commons.js:209:20)

hm-rpc.1
2022-02-26 11:10:16.994	error	uncaught exception: read ETIMEDOUT

telegram.0
2022-02-26 11:10:14.696	warn	polling_error: EFATAL, EFATAL: Error: read ETIMEDOUT

Vielleicht habt ihr dafür eine Erklärung.

apollon77

@bahnuhr ja. Dein System hat scheinbar gerade ein Problem mit DNS namensauflösungen. Also vor allem die EAGAIN sagen genau das. Check also mal Netzwerk und DNS. Vllt mal reboot? Sollte aber alles nix mit dem Controller zu tun haben.

Würde erst das fixen. Falls dann hm-Rpc weiter was sagt muss man da schauen.

apollon77

@meister-mopper was stand im log? Falls du schauen willst.

rasrol

Läuft perfekt.
Ich musste zwar ein Neuinstallation per Script durchführen, aber seither keine Fehler.

Debian 11
Node.js:v14.19.0
NPM:6.14.16

Danke

liv-in-sky

@apollon77

hat das was mit controller 4 zu tun - versuch javascript update - ging vor js-c update auch nicht zum updaten - mit controller 4 kommt beim update des javasc. adapters diese meldung:

host.iobroker59
2022-02-26 11:11:00.509	error	iobroker (node:27388) Warning: Accessing non-existent property 'findOne' of module exports inside circular dependency(node:27388) Warning: Accessing non-existent property 'remove' of module exports inside circular dependency(node:27388) Warning: Accessing non-existent property 'updateOne' of module exports inside circular dependency
host.iobroker59
2022-02-26 11:11:00.505	error	iobroker (node:27388) Warning: Accessing non-existent property 'count' of module exports inside circular dependency(Use `node --trace-warnings ...` to show where the warning was created)

siehe auch:https://forum.iobroker.net/post/768862

nehme an, ist anderes topic - nicht für hier?

apollon77

@liv-in-sky ließ mal in der faq. Du hast ne alte mongodb lib wohl von nem node-red. Liegt eher an nodejs 14+ als am Controller.

NEWS

js-controller 4.0.x jetzt für alle User im STABLE!

Support us

857
Online

30.2k
Users

76.3k
Topics

1.2m
Posts

NEWS

js-controller 4.0.x jetzt für alle User im STABLE!

Support us

857Online

30.2kUsers

76.3kTopics

1.2mPosts

857
Online

30.2k
Users

76.3k
Topics

1.2m
Posts