Skip to content
  • Home
  • Aktuell
  • Tags
  • 0 Ungelesen 0
  • Kategorien
  • Unreplied
  • Beliebt
  • GitHub
  • Docu
  • Hilfe
Skins
  • Light
  • Brite
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Standard: (Kein Skin)
  • Kein Skin
Einklappen
ioBroker Logo

Community Forum

donate donate
  1. ioBroker Community Home
  2. Deutsch
  3. ioBroker Allgemein
  4. [How-to] Node.js ioBroker richtig updaten-2021/22 Edition

NEWS

  • UPDATE 31.10.: Amazon Alexa - ioBroker Skill läuft aus ?
    apollon77A
    apollon77
    48
    3
    8.7k

  • Monatsrückblick – September 2025
    BluefoxB
    Bluefox
    13
    1
    2.2k

  • Neues Video "KI im Smart Home" - ioBroker plus n8n
    BluefoxB
    Bluefox
    16
    1
    3.1k

[How-to] Node.js ioBroker richtig updaten-2021/22 Edition

Geplant Angeheftet Gesperrt Verschoben ioBroker Allgemein
812 Beiträge 97 Kommentatoren 365.9k Aufrufe 83 Watching
  • Älteste zuerst
  • Neuste zuerst
  • Meiste Stimmen
Antworten
  • In einem neuen Thema antworten
Anmelden zum Antworten
Dieses Thema wurde gelöscht. Nur Nutzer mit entsprechenden Rechten können es sehen.
  • B backfisch88

    Hallo

    jedes mal (schon öfter probiert), wenn ich auf nodejs 14 upgrade läuft danach der mihome-vacuum Adapter nicht mehr.
    Es läuft alles Reibungslos, bis es ein Befehl von IOBroker kommt... nach einigen Minuten ist er wieder verbunden (manchmal auch länger) und das Spiel geht von vorne los
    mit node 12.X lief alles normal

    Auszug aus dem Log

    
    mihome-vacuum.0
    2021-11-18 13:32:51.245	info	Map selected create states...
    
    mihome-vacuum.0
    2021-11-18 13:32:50.686	info	settest next timer: not available
    
    mihome-vacuum.0
    2021-11-18 13:32:50.159	info	select standard vacuum protocol....
    
    mihome-vacuum.0
    2021-11-18 13:32:50.144	warn	No Answer for DeviceModel use model from Config
    
    mihome-vacuum.0
    2021-11-18 13:32:50.144	warn	No Answer for DeviceModel use old one
    
    mihome-vacuum.0
    2021-11-18 13:32:50.143	warn	YOUR DEVICE IS CONNECTED BUT DID NOT ANSWER YET - CONNECTION CAN TAKE UP TO 10 MINUTES - PLEASE BE PATIENT AND DO NOT TURN THE ADAPTER OFF
    
    mihome-vacuum.0
    2021-11-18 13:32:40.089	info	IOT enabled, create state
    
    mihome-vacuum.0
    2021-11-18 13:32:39.827	info	starting. Version 3.3.1 in /opt/iobroker/node_modules/iobroker.mihome-vacuum, node: v14.18.1, js-controller: 3.3.19
    host.IOBroker
    2021-11-18 13:32:37.671	info	instance system.adapter.mihome-vacuum.0 started with pid 14078
    host.IOBroker
    2021-11-18 13:32:36.632	info	Restart adapter system.adapter.mihome-vacuum.0 because enabled
    host.IOBroker
    2021-11-18 13:32:36.631	info	instance system.adapter.mihome-vacuum.0 terminated with code NaN ()
    host.IOBroker
    2021-11-18 13:32:36.624	warn	instance system.adapter.mihome-vacuum.0 terminated due to SIGBUS
    
    mihome-vacuum.0
    2021-11-18 13:31:26.406	info	trigger cleaning segment 17
    
    mihome-vacuum.0
    2021-11-18 13:31:16.313	info	create state for carpet_mode
    
    mihome-vacuum.0
    2021-11-18 13:31:15.114	info	create states for mop
    
    mihome-vacuum.0
    2021-11-18 13:31:15.103	info	create states for water box
    
    mihome-vacuum.0
    2021-11-18 13:31:15.087	info	change states from State control.fan_power
    
    mihome-vacuum.0
    2021-11-18 13:31:15.068	info	Map selected create states...
    
    mihome-vacuum.0
    2021-11-18 13:31:14.463	info	settest next timer: not available
    
    mihome-vacuum.0
    2021-11-18 13:31:13.932	info	select standard vacuum protocol....
    
    mihome-vacuum.0
    2021-11-18 13:31:13.815	info	IOT enabled, create state
    
    mihome-vacuum.0
    2021-11-18 13:31:13.539	info	starting. Version 3.3.1 in /opt/iobroker/node_modules/iobroker.mihome-vacuum, node: v14.18.1, js-controller: 3.3.19
    
    mihome-vacuum.0 | 2021-11-18 12:49:49.814 | info | Map selected create states...
    -- | -- | -- | --
    mihome-vacuum.0 | 2021-11-18 12:49:49.125 | info | settest next timer: not available
    mihome-vacuum.0 | 2021-11-18 12:49:48.595 | info | select standard vacuum protocol....
    mihome-vacuum.0 | 2021-11-18 12:49:48.569 | warn | No Answer for DeviceModel use model from Config
    mihome-vacuum.0 | 2021-11-18 12:49:48.568 | warn | No Answer for DeviceModel use old one
    mihome-vacuum.0 | 2021-11-18 12:49:48.567 | warn | YOUR DEVICE IS CONNECTED BUT DID NOT ANSWER YET - CONNECTION CAN TAKE UP TO 10 MINUTES - PLEASE BE PATIENT AND DO NOT TURN THE ADAPTER OFF
    mihome-vacuum.0 | 2021-11-18 12:49:38.508 | info | IOT enabled, create state
    mihome-vacuum.0 | 2021-11-18 12:49:38.255 | info | starting. Version 3.3.1 in /opt/iobroker/node_modules/iobroker.mihome-vacuum, node: v14.18.1, js-controller: 3.3.19
    host.IOBroker | 2021-11-18 12:49:36.130 | info | instance system.adapter.mihome-vacuum.0 started with pid 6957
    host.IOBroker | 2021-11-18 12:49:35.072 | info | Restart adapter system.adapter.mihome-vacuum.0 because enabled
    host.IOBroker | 2021-11-18 12:49:35.071 | info | instance system.adapter.mihome-vacuum.0 terminated with code NaN ()
    host.IOBroker | 2021-11-18 12:49:35.070 | warn | instance system.adapter.mihome-vacuum.0 terminated due to SIGABRT
    host.IOBroker | 2021-11-18 12:49:35.063 | error | Caught by controller[0]: free(): invalid pointer
    mihome-vacuum.0 | 2021-11-18 12:49:15.488 | info | trigger cleaning segment 17
    mihome-vacuum.0 | 2021-11-18 12:49:00.086 | info | create state for carpet_mode
    mihome-vacuum.0 | 2021-11-18 12:48:58.907 | info | create states for mop
    mihome-vacuum.0 | 2021-11-18 12:48:58.904 | info | create states for water box
    mihome-vacuum.0 | 2021-11-18 12:48:58.872 | info | change states from State control.fan_power
    mihome-vacuum.0 | 2021-11-18 12:48:58.839 | info | Map selected create states..
    

    jemand eine Idee?
    updated über
    curl -sL https://deb.nodesource.com/setup_14.x | sudo -E bash -
    sudo apt-get install -y nodejs
    iobroker fix

    zusätzlich:
    iobroker rebuild ioBroker.mihome-vacuum
    iobroker rebuild ioBroker.mihome-vacuum --install

    und ein rebuild in: opt/iobroker/
    und iobroker stop && sudo apt update && sudo apt upgrade -y && iobroker start

    und in github ein issue aufgemacht, wo ich hierhin verwiesen wurde :)

    und nochmal im DEBUG

    
    mihome-vacuum.0
    2021-11-18 13:39:10.415	debug	load Map creator... true
    
    mihome-vacuum.0
    2021-11-18 13:39:10.257	debug	Schedule restart: 0 0,1 * * *
    
    mihome-vacuum.0
    2021-11-18 13:39:10.172	info	starting. Version 3.3.1 in /opt/iobroker/node_modules/iobroker.mihome-vacuum, node: v14.18.1, js-controller: 3.3.19
    
    mihome-vacuum.0
    2021-11-18 13:39:09.903	debug	Plugin sentry Initialize Plugin (enabled=true)
    
    mihome-vacuum.0
    2021-11-18 13:39:06.008	warn	Terminated (UNCAUGHT_EXCEPTION): Without reason
    
    mihome-vacuum.0
    2021-11-18 13:39:06.007	debug	Plugin sentry destroyed
    
    mihome-vacuum.0
    2021-11-18 13:39:06.006	info	terminating
    
    mihome-vacuum.0
    2021-11-18 13:39:06.005	error	Socket Close
    
    mihome-vacuum.0
    2021-11-18 13:39:05.799	error	undefined
    
    mihome-vacuum.0
    2021-11-18 13:39:05.798	error	unhandled promise rejection: undefined
    
    mihome-vacuum.0
    2021-11-18 13:39:05.798	error	Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch().
    
    mihome-vacuum.0
    2021-11-18 13:39:05.796	debug	MIIO Receive Timeout for "app_segment_clean" <<<
    
    mihome-vacuum.0
    2021-11-18 13:39:04.078	debug	Message= {"id":17,"method":"get_multi_maps_list"}
    
    mihome-vacuum.0
    2021-11-18 13:39:04.077	debug	ERROR at setGetSoundVolume: MESSAGE TIMEOUT
    
    mihome-vacuum.0
    2021-11-18 13:39:04.076	debug	MIIO Receive Timeout for "get_sound_volume" <<<
    
    mihome-vacuum.0
    2021-11-18 13:39:03.794	debug	Message= {"id":16,"method":"app_segment_clean","params":[17]}
    
    mihome-vacuum.0
    2021-11-18 13:39:03.793	info	trigger cleaning segment 17
    
    mihome-vacuum.0
    2021-11-18 13:39:03.792	debug	start Cleaning: 18 MObj: {"command":"cleanSegments","message":"17","from":"system.adapter.mihome-vacuum.0","_id":62189570,"segments":[17],"channels":["mihome-vacuum.0.rooms.73001006380"]}
    
    mihome-vacuum.0
    2021-11-18 13:39:03.791	debug	We are in onMessage:{"command":"cleanSegments","message":{"segments":[17],"channels":["mihome-vacuum.0.rooms.73001006380"]},"from":"system.adapter.mihome-vacuum.0","_id":62189570}
    
    mihome-vacuum.0
    2021-11-18 13:39:03.784	debug	sendTo "cleanSegments" to system.adapter.mihome-vacuum.0 from system.adapter.mihome-vacuum.0
    
    mihome-vacuum.0
    2021-11-18 13:39:03.779	debug	command: roomClean parent: 73001006380
    
    S Offline
    S Offline
    SSW-mcor
    schrieb am zuletzt editiert von
    #131

    Hab grad auf meinen Windows-Systemen die empfohlene Version "v14.18.1" drauf - bis auf dass die Konsolen danach wie immer nicht mehr gingen, alles gut :grinning:

    1 Antwort Letzte Antwort
    0
    • B backfisch88

      Hallo

      jedes mal (schon öfter probiert), wenn ich auf nodejs 14 upgrade läuft danach der mihome-vacuum Adapter nicht mehr.
      Es läuft alles Reibungslos, bis es ein Befehl von IOBroker kommt... nach einigen Minuten ist er wieder verbunden (manchmal auch länger) und das Spiel geht von vorne los
      mit node 12.X lief alles normal

      Auszug aus dem Log

      
      mihome-vacuum.0
      2021-11-18 13:32:51.245	info	Map selected create states...
      
      mihome-vacuum.0
      2021-11-18 13:32:50.686	info	settest next timer: not available
      
      mihome-vacuum.0
      2021-11-18 13:32:50.159	info	select standard vacuum protocol....
      
      mihome-vacuum.0
      2021-11-18 13:32:50.144	warn	No Answer for DeviceModel use model from Config
      
      mihome-vacuum.0
      2021-11-18 13:32:50.144	warn	No Answer for DeviceModel use old one
      
      mihome-vacuum.0
      2021-11-18 13:32:50.143	warn	YOUR DEVICE IS CONNECTED BUT DID NOT ANSWER YET - CONNECTION CAN TAKE UP TO 10 MINUTES - PLEASE BE PATIENT AND DO NOT TURN THE ADAPTER OFF
      
      mihome-vacuum.0
      2021-11-18 13:32:40.089	info	IOT enabled, create state
      
      mihome-vacuum.0
      2021-11-18 13:32:39.827	info	starting. Version 3.3.1 in /opt/iobroker/node_modules/iobroker.mihome-vacuum, node: v14.18.1, js-controller: 3.3.19
      host.IOBroker
      2021-11-18 13:32:37.671	info	instance system.adapter.mihome-vacuum.0 started with pid 14078
      host.IOBroker
      2021-11-18 13:32:36.632	info	Restart adapter system.adapter.mihome-vacuum.0 because enabled
      host.IOBroker
      2021-11-18 13:32:36.631	info	instance system.adapter.mihome-vacuum.0 terminated with code NaN ()
      host.IOBroker
      2021-11-18 13:32:36.624	warn	instance system.adapter.mihome-vacuum.0 terminated due to SIGBUS
      
      mihome-vacuum.0
      2021-11-18 13:31:26.406	info	trigger cleaning segment 17
      
      mihome-vacuum.0
      2021-11-18 13:31:16.313	info	create state for carpet_mode
      
      mihome-vacuum.0
      2021-11-18 13:31:15.114	info	create states for mop
      
      mihome-vacuum.0
      2021-11-18 13:31:15.103	info	create states for water box
      
      mihome-vacuum.0
      2021-11-18 13:31:15.087	info	change states from State control.fan_power
      
      mihome-vacuum.0
      2021-11-18 13:31:15.068	info	Map selected create states...
      
      mihome-vacuum.0
      2021-11-18 13:31:14.463	info	settest next timer: not available
      
      mihome-vacuum.0
      2021-11-18 13:31:13.932	info	select standard vacuum protocol....
      
      mihome-vacuum.0
      2021-11-18 13:31:13.815	info	IOT enabled, create state
      
      mihome-vacuum.0
      2021-11-18 13:31:13.539	info	starting. Version 3.3.1 in /opt/iobroker/node_modules/iobroker.mihome-vacuum, node: v14.18.1, js-controller: 3.3.19
      
      mihome-vacuum.0 | 2021-11-18 12:49:49.814 | info | Map selected create states...
      -- | -- | -- | --
      mihome-vacuum.0 | 2021-11-18 12:49:49.125 | info | settest next timer: not available
      mihome-vacuum.0 | 2021-11-18 12:49:48.595 | info | select standard vacuum protocol....
      mihome-vacuum.0 | 2021-11-18 12:49:48.569 | warn | No Answer for DeviceModel use model from Config
      mihome-vacuum.0 | 2021-11-18 12:49:48.568 | warn | No Answer for DeviceModel use old one
      mihome-vacuum.0 | 2021-11-18 12:49:48.567 | warn | YOUR DEVICE IS CONNECTED BUT DID NOT ANSWER YET - CONNECTION CAN TAKE UP TO 10 MINUTES - PLEASE BE PATIENT AND DO NOT TURN THE ADAPTER OFF
      mihome-vacuum.0 | 2021-11-18 12:49:38.508 | info | IOT enabled, create state
      mihome-vacuum.0 | 2021-11-18 12:49:38.255 | info | starting. Version 3.3.1 in /opt/iobroker/node_modules/iobroker.mihome-vacuum, node: v14.18.1, js-controller: 3.3.19
      host.IOBroker | 2021-11-18 12:49:36.130 | info | instance system.adapter.mihome-vacuum.0 started with pid 6957
      host.IOBroker | 2021-11-18 12:49:35.072 | info | Restart adapter system.adapter.mihome-vacuum.0 because enabled
      host.IOBroker | 2021-11-18 12:49:35.071 | info | instance system.adapter.mihome-vacuum.0 terminated with code NaN ()
      host.IOBroker | 2021-11-18 12:49:35.070 | warn | instance system.adapter.mihome-vacuum.0 terminated due to SIGABRT
      host.IOBroker | 2021-11-18 12:49:35.063 | error | Caught by controller[0]: free(): invalid pointer
      mihome-vacuum.0 | 2021-11-18 12:49:15.488 | info | trigger cleaning segment 17
      mihome-vacuum.0 | 2021-11-18 12:49:00.086 | info | create state for carpet_mode
      mihome-vacuum.0 | 2021-11-18 12:48:58.907 | info | create states for mop
      mihome-vacuum.0 | 2021-11-18 12:48:58.904 | info | create states for water box
      mihome-vacuum.0 | 2021-11-18 12:48:58.872 | info | change states from State control.fan_power
      mihome-vacuum.0 | 2021-11-18 12:48:58.839 | info | Map selected create states..
      

      jemand eine Idee?
      updated über
      curl -sL https://deb.nodesource.com/setup_14.x | sudo -E bash -
      sudo apt-get install -y nodejs
      iobroker fix

      zusätzlich:
      iobroker rebuild ioBroker.mihome-vacuum
      iobroker rebuild ioBroker.mihome-vacuum --install

      und ein rebuild in: opt/iobroker/
      und iobroker stop && sudo apt update && sudo apt upgrade -y && iobroker start

      und in github ein issue aufgemacht, wo ich hierhin verwiesen wurde :)

      und nochmal im DEBUG

      
      mihome-vacuum.0
      2021-11-18 13:39:10.415	debug	load Map creator... true
      
      mihome-vacuum.0
      2021-11-18 13:39:10.257	debug	Schedule restart: 0 0,1 * * *
      
      mihome-vacuum.0
      2021-11-18 13:39:10.172	info	starting. Version 3.3.1 in /opt/iobroker/node_modules/iobroker.mihome-vacuum, node: v14.18.1, js-controller: 3.3.19
      
      mihome-vacuum.0
      2021-11-18 13:39:09.903	debug	Plugin sentry Initialize Plugin (enabled=true)
      
      mihome-vacuum.0
      2021-11-18 13:39:06.008	warn	Terminated (UNCAUGHT_EXCEPTION): Without reason
      
      mihome-vacuum.0
      2021-11-18 13:39:06.007	debug	Plugin sentry destroyed
      
      mihome-vacuum.0
      2021-11-18 13:39:06.006	info	terminating
      
      mihome-vacuum.0
      2021-11-18 13:39:06.005	error	Socket Close
      
      mihome-vacuum.0
      2021-11-18 13:39:05.799	error	undefined
      
      mihome-vacuum.0
      2021-11-18 13:39:05.798	error	unhandled promise rejection: undefined
      
      mihome-vacuum.0
      2021-11-18 13:39:05.798	error	Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch().
      
      mihome-vacuum.0
      2021-11-18 13:39:05.796	debug	MIIO Receive Timeout for "app_segment_clean" <<<
      
      mihome-vacuum.0
      2021-11-18 13:39:04.078	debug	Message= {"id":17,"method":"get_multi_maps_list"}
      
      mihome-vacuum.0
      2021-11-18 13:39:04.077	debug	ERROR at setGetSoundVolume: MESSAGE TIMEOUT
      
      mihome-vacuum.0
      2021-11-18 13:39:04.076	debug	MIIO Receive Timeout for "get_sound_volume" <<<
      
      mihome-vacuum.0
      2021-11-18 13:39:03.794	debug	Message= {"id":16,"method":"app_segment_clean","params":[17]}
      
      mihome-vacuum.0
      2021-11-18 13:39:03.793	info	trigger cleaning segment 17
      
      mihome-vacuum.0
      2021-11-18 13:39:03.792	debug	start Cleaning: 18 MObj: {"command":"cleanSegments","message":"17","from":"system.adapter.mihome-vacuum.0","_id":62189570,"segments":[17],"channels":["mihome-vacuum.0.rooms.73001006380"]}
      
      mihome-vacuum.0
      2021-11-18 13:39:03.791	debug	We are in onMessage:{"command":"cleanSegments","message":{"segments":[17],"channels":["mihome-vacuum.0.rooms.73001006380"]},"from":"system.adapter.mihome-vacuum.0","_id":62189570}
      
      mihome-vacuum.0
      2021-11-18 13:39:03.784	debug	sendTo "cleanSegments" to system.adapter.mihome-vacuum.0 from system.adapter.mihome-vacuum.0
      
      mihome-vacuum.0
      2021-11-18 13:39:03.779	debug	command: roomClean parent: 73001006380
      
      apollon77A Offline
      apollon77A Offline
      apollon77
      schrieb am zuletzt editiert von
      #132

      @backfisch88 Ich glaube der Fehler hier sieht jetzt eher aus wie https://github.com/iobroker-community-adapters/ioBroker.mihome-vacuum/issues/428

      Beitrag hat geholfen? Votet rechts unten im Beitrag :-) https://paypal.me/Apollon77 / https://github.com/sponsors/Apollon77

      • Debug-Log für Instanz einschalten? Admin -> Instanzen -> Expertenmodus -> Instanz aufklappen - Loglevel ändern
      • Logfiles auf Platte /opt/iobroker/log/… nutzen, Admin schneidet Zeilen ab
      B 1 Antwort Letzte Antwort
      0
      • C Offline
        C Offline
        Cino
        schrieb am zuletzt editiert von Cino
        #133

        Ich habe auch Probleme mit dem Update und Zigbee. Bin schon die ganzen Befehle hier im Thread durchgegangen.

        host.iobroker
        2021-11-19 05:56:44.411	info	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.
        host.iobroker
        2021-11-19 05:56:44.411	error	instance system.adapter.zigbee.0 terminated with code 1 (JS_CONTROLLER_STOPPED)
        host.iobroker
        2021-11-19 05:56:44.411	error	Caught by controller[0]: }
        host.iobroker
        2021-11-19 05:56:44.410	error	Caught by controller[0]: code: 'ERR_DLOPEN_FAILED'
        host.iobroker
        2021-11-19 05:56:44.410	error	Caught by controller[0]: at Module.load (node:internal/modules/cjs/loader:981:32) {
        host.iobroker
        2021-11-19 05:56:44.410	error	Caught by controller[0]: at Object.Module._extensions..js (node:internal/modules/cjs/loader:1153:10)
        host.iobroker
        2021-11-19 05:56:44.409	error	Caught by controller[0]: at Module._compile (node:internal/modules/cjs/loader:1101:14)
        host.iobroker
        2021-11-19 05:56:44.409	error	Caught by controller[0]: at Object.<anonymous> (/opt/iobroker/node_modules/zigbee-herdsman/node_modules/@serialport/bindings/lib/linux.js:2:36)
        host.iobroker
        2021-11-19 05:56:44.409	error	Caught by controller[0]: at bindings (/opt/iobroker/node_modules/zigbee-herdsman/node_modules/bindings/bindings.js:112:48)
        host.iobroker
        2021-11-19 05:56:44.408	error	Caught by controller[0]: at require (node:internal/modules/cjs/helpers:102:18)
        host.iobroker
        2021-11-19 05:56:44.408	error	Caught by controller[0]: at Module.require (node:internal/modules/cjs/loader:1005:19)
        host.iobroker
        2021-11-19 05:56:44.408	error	Caught by controller[0]: at Function.Module._load (node:internal/modules/cjs/loader:822:12)
        host.iobroker
        2021-11-19 05:56:44.407	error	Caught by controller[0]: at Module.load (node:internal/modules/cjs/loader:981:32)
        host.iobroker
        2021-11-19 05:56:44.407	error	Caught by controller[0]: at Object.Module._extensions..node (node:internal/modules/cjs/loader:1183:18)
        host.iobroker
        2021-11-19 05:56:44.407	error	Caught by controller[0]: the module (for instance, using `npm rebuild` or `npm install`).
        host.iobroker
        2021-11-19 05:56:44.406	error	Caught by controller[0]: NODE_MODULE_VERSION 93. Please try re-compiling or re-installing
        host.iobroker
        2021-11-19 05:56:44.406	error	Caught by controller[0]: NODE_MODULE_VERSION 72. This version of Node.js requires
        host.iobroker
        2021-11-19 05:56:44.406	error	Caught by controller[0]: was compiled against a different Node.js version using
        host.iobroker
        2021-11-19 05:56:44.405	error	Caught by controller[0]: Error: The module '/opt/iobroker/node_modules/zigbee-herdsman/node_modules/@serialport/bindings/build/Release/bindings.node'
        host.iobroker
        2021-11-19 05:56:44.405	error	Caught by controller[0]: ^
        host.iobroker
        2021-11-19 05:56:44.405	error	Caught by controller[0]: throw e;
        host.iobroker
        2021-11-19 05:56:44.404	error	Caught by controller[0]: /opt/iobroker/node_modules/zigbee-herdsman/node_modules/bindings/bindings.js:121
        

        IOB@RPI4
        Shelly, Zigbee, ebus

        crunchipC 1 Antwort Letzte Antwort
        0
        • C Cino

          Ich habe auch Probleme mit dem Update und Zigbee. Bin schon die ganzen Befehle hier im Thread durchgegangen.

          host.iobroker
          2021-11-19 05:56:44.411	info	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.
          host.iobroker
          2021-11-19 05:56:44.411	error	instance system.adapter.zigbee.0 terminated with code 1 (JS_CONTROLLER_STOPPED)
          host.iobroker
          2021-11-19 05:56:44.411	error	Caught by controller[0]: }
          host.iobroker
          2021-11-19 05:56:44.410	error	Caught by controller[0]: code: 'ERR_DLOPEN_FAILED'
          host.iobroker
          2021-11-19 05:56:44.410	error	Caught by controller[0]: at Module.load (node:internal/modules/cjs/loader:981:32) {
          host.iobroker
          2021-11-19 05:56:44.410	error	Caught by controller[0]: at Object.Module._extensions..js (node:internal/modules/cjs/loader:1153:10)
          host.iobroker
          2021-11-19 05:56:44.409	error	Caught by controller[0]: at Module._compile (node:internal/modules/cjs/loader:1101:14)
          host.iobroker
          2021-11-19 05:56:44.409	error	Caught by controller[0]: at Object.<anonymous> (/opt/iobroker/node_modules/zigbee-herdsman/node_modules/@serialport/bindings/lib/linux.js:2:36)
          host.iobroker
          2021-11-19 05:56:44.409	error	Caught by controller[0]: at bindings (/opt/iobroker/node_modules/zigbee-herdsman/node_modules/bindings/bindings.js:112:48)
          host.iobroker
          2021-11-19 05:56:44.408	error	Caught by controller[0]: at require (node:internal/modules/cjs/helpers:102:18)
          host.iobroker
          2021-11-19 05:56:44.408	error	Caught by controller[0]: at Module.require (node:internal/modules/cjs/loader:1005:19)
          host.iobroker
          2021-11-19 05:56:44.408	error	Caught by controller[0]: at Function.Module._load (node:internal/modules/cjs/loader:822:12)
          host.iobroker
          2021-11-19 05:56:44.407	error	Caught by controller[0]: at Module.load (node:internal/modules/cjs/loader:981:32)
          host.iobroker
          2021-11-19 05:56:44.407	error	Caught by controller[0]: at Object.Module._extensions..node (node:internal/modules/cjs/loader:1183:18)
          host.iobroker
          2021-11-19 05:56:44.407	error	Caught by controller[0]: the module (for instance, using `npm rebuild` or `npm install`).
          host.iobroker
          2021-11-19 05:56:44.406	error	Caught by controller[0]: NODE_MODULE_VERSION 93. Please try re-compiling or re-installing
          host.iobroker
          2021-11-19 05:56:44.406	error	Caught by controller[0]: NODE_MODULE_VERSION 72. This version of Node.js requires
          host.iobroker
          2021-11-19 05:56:44.406	error	Caught by controller[0]: was compiled against a different Node.js version using
          host.iobroker
          2021-11-19 05:56:44.405	error	Caught by controller[0]: Error: The module '/opt/iobroker/node_modules/zigbee-herdsman/node_modules/@serialport/bindings/build/Release/bindings.node'
          host.iobroker
          2021-11-19 05:56:44.405	error	Caught by controller[0]: ^
          host.iobroker
          2021-11-19 05:56:44.405	error	Caught by controller[0]: throw e;
          host.iobroker
          2021-11-19 05:56:44.404	error	Caught by controller[0]: /opt/iobroker/node_modules/zigbee-herdsman/node_modules/bindings/bindings.js:121
          
          crunchipC Abwesend
          crunchipC Abwesend
          crunchip
          Forum Testing Most Active
          schrieb am zuletzt editiert von
          #134

          @cino sagte in [How-to] Node.js für ioBroker richtig updaten - 2021 Edition:

          Bin schon die ganzen Befehle hier im Thread durchgegangen.

          Dann zeig auch mal das Ergebnis der Eingaben

          umgestiegen von Proxmox auf Unraid

          1 Antwort Letzte Antwort
          0
          • C Offline
            C Offline
            Cino
            schrieb am zuletzt editiert von Cino
            #135

            Sorry, ich mach das nochmal neu. Das ist alles durcheinander gekommen.

            pi@iobroker:/opt/iobroker/node_modules/zigbee-herdsman/node_modules/@serialport/                                               bindings/build/Release $ npm install --loglevel error --production
            
            > @serialport/bindings@9.2.5 install
            > prebuild-install --tag-prefix @serialport/bindings@ || node-gyp rebuild
            
            make: Verzeichnis „/opt/iobroker/node_modules/zigbee-herdsman/node_modules/@seri                                               alport/bindings/build“ wird betreten
              CXX(target) Release/obj.target/bindings/src/serialport.o
            ../src/serialport.cpp: In function ‘Nan::NAN_METHOD_RETURN_TYPE Open(Nan::NAN_ME                                               THOD_ARGS_TYPE)’:
            ../src/serialport.cpp:78:51: warning: cast between incompatible function types f                                               rom ‘void (*)(uv_work_t*)’ {aka ‘void (*)(uv_work_s*)’} to ‘uv_after_work_cb’ {a                                               ka ‘void (*)(uv_work_s*, int)’} [-Wcast-function-type]
               78 |   uv_queue_work(uv_default_loop(), req, EIO_Open, (uv_after_work_cb)EIO_                                               AfterOpen);
                  |                                                   ^~~~~~~~~~~~~~~~~~~~~~                                               ~~~~~~~~~
            ../src/serialport.cpp: In function ‘Nan::NAN_METHOD_RETURN_TYPE Update(Nan::NAN_                                               METHOD_ARGS_TYPE)’:
            ../src/serialport.cpp:135:53: 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]
              135 |   uv_queue_work(uv_default_loop(), req, EIO_Update, (uv_after_work_cb)EI                                               O_AfterUpdate);
                  |                                                     ^~~~~~~~~~~~~~~~~~~~                                               ~~~~~~~~~~~~~
            ../src/serialport.cpp: In function ‘Nan::NAN_METHOD_RETURN_TYPE Close(Nan::NAN_M                                               ETHOD_ARGS_TYPE)’:
            ../src/serialport.cpp:175:52: 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]
              175 |   uv_queue_work(uv_default_loop(), req, EIO_Close, (uv_after_work_cb)EIO                                               _AfterClose);
                  |                                                    ^~~~~~~~~~~~~~~~~~~~~                                               ~~~~~~~~~~~
            ../src/serialport.cpp: In function ‘Nan::NAN_METHOD_RETURN_TYPE Flush(Nan::NAN_M                                               ETHOD_ARGS_TYPE)’:
            ../src/serialport.cpp:215:52: 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]
              215 |   uv_queue_work(uv_default_loop(), req, EIO_Flush, (uv_after_work_cb)EIO                                               _AfterFlush);
                  |                                                    ^~~~~~~~~~~~~~~~~~~~~                                               ~~~~~~~~~~~
            ../src/serialport.cpp: In function ‘Nan::NAN_METHOD_RETURN_TYPE Set(Nan::NAN_MET                                               HOD_ARGS_TYPE)’:
            ../src/serialport.cpp:271:50: 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]
              271 |   uv_queue_work(uv_default_loop(), req, EIO_Set, (uv_after_work_cb)EIO_A                                               fterSet);
                  |                                                  ^~~~~~~~~~~~~~~~~~~~~~~                                               ~~~~~~~
            ../src/serialport.cpp: In function ‘Nan::NAN_METHOD_RETURN_TYPE Get(Nan::NAN_MET                                               HOD_ARGS_TYPE)’:
            ../src/serialport.cpp:316:50: 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]
              316 |   uv_queue_work(uv_default_loop(), req, EIO_Get, (uv_after_work_cb)EIO_A                                               fterGet);
                  |                                                  ^~~~~~~~~~~~~~~~~~~~~~~                                               ~~~~~~~
            ../src/serialport.cpp: In function ‘Nan::NAN_METHOD_RETURN_TYPE GetBaudRate(Nan:                                               :NAN_METHOD_ARGS_TYPE)’:
            ../src/serialport.cpp:366:58: 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]
              366 |   uv_queue_work(uv_default_loop(), req, EIO_GetBaudRate, (uv_after_work_                                               cb)EIO_AfterGetBaudRate);
                  |                                                          ^~~~~~~~~~~~~~~                                               ~~~~~~~~~~~~~~~~~~~~~~~
            ../src/serialport.cpp: In function ‘Nan::NAN_METHOD_RETURN_TYPE Drain(Nan::NAN_M                                               ETHOD_ARGS_TYPE)’:
            ../src/serialport.cpp:412:52: 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]
              412 |   uv_queue_work(uv_default_loop(), req, EIO_Drain, (uv_after_work_cb)EIO                                               _AfterDrain);
                  |                                                    ^~~~~~~~~~~~~~~~~~~~~                                               ~~~~~~~~~~~
            ../src/serialport.cpp: At global scope:
            ../src/serialport.cpp:433:28: warning: unnecessary parentheses in declaration of                                                ‘ToParityEnum’ [-Wparentheses]
              433 | SerialPortParity NAN_INLINE(ToParityEnum(const v8::Local<v8::String>& v8                                               str)) {
                  |                            ^
            ../src/serialport.cpp:452:30: warning: unnecessary parentheses in declaration of                                                ‘ToStopBitEnum’ [-Wparentheses]
              452 | SerialPortStopBits NAN_INLINE(ToStopBitEnum(double stopBits)) {
                  |                              ^
            In file included from ../node_modules/nan/nan.h:58,
                             from ../src/./serialport.h:13,
                             from ../src/serialport.cpp:1:
            /home/iobroker/.cache/node-gyp/16.13.0/include/node/node.h:821:7: warning: cast                                                between incompatible function types from ‘void (*)(Nan::ADDON_REGISTER_FUNCTION_                                               ARGS_TYPE)’ {aka ‘void (*)(v8::Local<v8::Object>)’} to ‘node::addon_register_fun                                               c’ {aka ‘void (*)(v8::Local<v8::Object>, v8::Local<v8::Value>, void*)’} [-Wcast-                                               function-type]
              821 |       (node::addon_register_func) (regfunc),                          \
                  |       ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
            /home/iobroker/.cache/node-gyp/16.13.0/include/node/node.h:855:3: note: in expan                                               sion of macro ‘NODE_MODULE_X’
              855 |   NODE_MODULE_X(modname, regfunc, NULL, 0)  // NOLINT (readability/null_                                               usage)
                  |   ^~~~~~~~~~~~~
            ../src/serialport.cpp:486:1: note: in expansion of macro ‘NODE_MODULE’
              486 | NODE_MODULE(serialport, init);
                  | ^~~~~~~~~~~
              CXX(target) Release/obj.target/bindings/src/serialport_unix.o
            ../src/serialport_unix.cpp: In function ‘int setup(int, OpenBaton*)’:
            ../src/serialport_unix.cpp:179:82: warning: ‘%s’ directive output may be truncat                                               ed writing up to 1023 bytes into a region of size 1005 [-Wformat-truncation=]
              179 | rorString, sizeof(data->errorString), "Error %s Cannot open %s", strerro                                               r(errno), data->path);
                  |                                                             ^~
            
            ../src/serialport_unix.cpp:179:13: note: ‘snprintf’ output 20 or more bytes (ass                                               uming 1043) into a destination of size 1024
              179 |     snprintf(data->errorString, sizeof(data->errorString), "Error %s Can                                               not open %s", strerror(errno), data->path);
                  |     ~~~~~~~~^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~                                               ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
            ../src/serialport_unix.cpp: In function ‘void EIO_Open(uv_work_t*)’:
            ../src/serialport_unix.cpp:89:84: warning: ‘%s’ directive output may be truncate                                               d writing up to 1023 bytes into a region of size 1003 [-Wformat-truncation=]
               89 | rString, sizeof(data->errorString), "Error: %s, cannot open %s", strerro                                               r(errno), data->path);
                  |                                                             ^~
            
            ../src/serialport_unix.cpp:89:13: note: ‘snprintf’ output 22 or more bytes (assu                                               ming 1045) into a destination of size 1024
               89 |     snprintf(data->errorString, sizeof(data->errorString), "Error: %s, c                                               annot open %s", strerror(errno), data->path);
                  |     ~~~~~~~~^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~                                               ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
              CXX(target) Release/obj.target/bindings/src/poller.o
              CXX(target) Release/obj.target/bindings/src/serialport_linux.o
              SOLINK_MODULE(target) Release/obj.target/bindings.node
              COPY Release/bindings.node
            make: Verzeichnis „/opt/iobroker/node_modules/zigbee-herdsman/node_modules/@seri                                               alport/bindings/build“ wird verlassen
            
            added 65 packages, and audited 66 packages in 29s
            
            8 packages are looking for funding
              run `npm fund` for details
            
            found 0 vulnerabilities
            
            
            host.iobroker
            2021-11-19 06:30:40.587	info	iobroker npm-rebuild: exit 0
            host.iobroker
            2021-11-19 06:30:39.564	info	iobroker npm-rebuild: Rebuild zigbee done
            host.iobroker
            2021-11-19 06:30:39.539	info	iobroker npm-rebuild: npm ERR! A complete log of this run can be found in:npm ERR! /home/iobroker/.npm/_logs/2021-11-19T05_30_39_483Z-debug.log
            host.iobroker
            2021-11-19 06:30:39.531	info	iobroker npm-rebuild:
            host.iobroker
            2021-11-19 06:30:39.483	info	iobroker npm-rebuild: npm ERR! Fix the upstream dependency conflict, or retrynpm ERR! this command with --force, or --legacy-peer-depsnpm ERR! to accept an incorrect (and potentially broken) dependency resolution.npm ERR! npm ERR! See /home/iobroker/.npm/eresolve-report.txt for a full report.
            host.iobroker
            2021-11-19 06:30:39.480	info	iobroker npm-rebuild: npm ERR! While resolving: iobroker.zigbee@1.6.6npm ERR! Found: eslint@7.32.0npm ERR! node_modules/eslintnpm ERR! dev eslint@"^7.18.0" from the root projectnpm ERR! npm ERR! Could not resolve dependency:npm ERR! peer eslint@"4.x" from lint-diff@1.2.1npm ERR! node_modules/lint-diffnpm ERR! dev lint-diff@"*" from the root projectnpm ERR!
            host.iobroker
            2021-11-19 06:30:39.462	info	iobroker npm-rebuild: npm ERR!
            host.iobroker
            2021-11-19 06:30:39.461	info	iobroker npm-rebuild: npm ERR! ERESOLVE unable to resolve dependency tree
            host.iobroker
            2021-11-19 06:30:39.441	info	iobroker npm-rebuild: npm ERR! code ERESOLVE
            host.iobroker
            2021-11-19 06:30:38.629	info	instance system.adapter.heatingcontrol.0 started with pid 9210
            host.iobroker
            2021-11-19 06:30:34.124	info	instance system.adapter.lgtv.0 started with pid 9096
            host.iobroker
            2021-11-19 06:30:33.277	info	iobroker npm-rebuild: npm install --loglevel error --production (System call1) in "/opt/iobroker/node_modules/iobroker.zigbee"
            host.iobroker
            2021-11-19 06:30:31.860	info	iobroker rebuild zigbee --install
            

            IOB@RPI4
            Shelly, Zigbee, ebus

            apollon77A 1 Antwort Letzte Antwort
            0
            • C Cino

              Sorry, ich mach das nochmal neu. Das ist alles durcheinander gekommen.

              pi@iobroker:/opt/iobroker/node_modules/zigbee-herdsman/node_modules/@serialport/                                               bindings/build/Release $ npm install --loglevel error --production
              
              > @serialport/bindings@9.2.5 install
              > prebuild-install --tag-prefix @serialport/bindings@ || node-gyp rebuild
              
              make: Verzeichnis „/opt/iobroker/node_modules/zigbee-herdsman/node_modules/@seri                                               alport/bindings/build“ wird betreten
                CXX(target) Release/obj.target/bindings/src/serialport.o
              ../src/serialport.cpp: In function ‘Nan::NAN_METHOD_RETURN_TYPE Open(Nan::NAN_ME                                               THOD_ARGS_TYPE)’:
              ../src/serialport.cpp:78:51: warning: cast between incompatible function types f                                               rom ‘void (*)(uv_work_t*)’ {aka ‘void (*)(uv_work_s*)’} to ‘uv_after_work_cb’ {a                                               ka ‘void (*)(uv_work_s*, int)’} [-Wcast-function-type]
                 78 |   uv_queue_work(uv_default_loop(), req, EIO_Open, (uv_after_work_cb)EIO_                                               AfterOpen);
                    |                                                   ^~~~~~~~~~~~~~~~~~~~~~                                               ~~~~~~~~~
              ../src/serialport.cpp: In function ‘Nan::NAN_METHOD_RETURN_TYPE Update(Nan::NAN_                                               METHOD_ARGS_TYPE)’:
              ../src/serialport.cpp:135:53: 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]
                135 |   uv_queue_work(uv_default_loop(), req, EIO_Update, (uv_after_work_cb)EI                                               O_AfterUpdate);
                    |                                                     ^~~~~~~~~~~~~~~~~~~~                                               ~~~~~~~~~~~~~
              ../src/serialport.cpp: In function ‘Nan::NAN_METHOD_RETURN_TYPE Close(Nan::NAN_M                                               ETHOD_ARGS_TYPE)’:
              ../src/serialport.cpp:175:52: 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]
                175 |   uv_queue_work(uv_default_loop(), req, EIO_Close, (uv_after_work_cb)EIO                                               _AfterClose);
                    |                                                    ^~~~~~~~~~~~~~~~~~~~~                                               ~~~~~~~~~~~
              ../src/serialport.cpp: In function ‘Nan::NAN_METHOD_RETURN_TYPE Flush(Nan::NAN_M                                               ETHOD_ARGS_TYPE)’:
              ../src/serialport.cpp:215:52: 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]
                215 |   uv_queue_work(uv_default_loop(), req, EIO_Flush, (uv_after_work_cb)EIO                                               _AfterFlush);
                    |                                                    ^~~~~~~~~~~~~~~~~~~~~                                               ~~~~~~~~~~~
              ../src/serialport.cpp: In function ‘Nan::NAN_METHOD_RETURN_TYPE Set(Nan::NAN_MET                                               HOD_ARGS_TYPE)’:
              ../src/serialport.cpp:271:50: 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]
                271 |   uv_queue_work(uv_default_loop(), req, EIO_Set, (uv_after_work_cb)EIO_A                                               fterSet);
                    |                                                  ^~~~~~~~~~~~~~~~~~~~~~~                                               ~~~~~~~
              ../src/serialport.cpp: In function ‘Nan::NAN_METHOD_RETURN_TYPE Get(Nan::NAN_MET                                               HOD_ARGS_TYPE)’:
              ../src/serialport.cpp:316:50: 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]
                316 |   uv_queue_work(uv_default_loop(), req, EIO_Get, (uv_after_work_cb)EIO_A                                               fterGet);
                    |                                                  ^~~~~~~~~~~~~~~~~~~~~~~                                               ~~~~~~~
              ../src/serialport.cpp: In function ‘Nan::NAN_METHOD_RETURN_TYPE GetBaudRate(Nan:                                               :NAN_METHOD_ARGS_TYPE)’:
              ../src/serialport.cpp:366:58: 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]
                366 |   uv_queue_work(uv_default_loop(), req, EIO_GetBaudRate, (uv_after_work_                                               cb)EIO_AfterGetBaudRate);
                    |                                                          ^~~~~~~~~~~~~~~                                               ~~~~~~~~~~~~~~~~~~~~~~~
              ../src/serialport.cpp: In function ‘Nan::NAN_METHOD_RETURN_TYPE Drain(Nan::NAN_M                                               ETHOD_ARGS_TYPE)’:
              ../src/serialport.cpp:412:52: 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]
                412 |   uv_queue_work(uv_default_loop(), req, EIO_Drain, (uv_after_work_cb)EIO                                               _AfterDrain);
                    |                                                    ^~~~~~~~~~~~~~~~~~~~~                                               ~~~~~~~~~~~
              ../src/serialport.cpp: At global scope:
              ../src/serialport.cpp:433:28: warning: unnecessary parentheses in declaration of                                                ‘ToParityEnum’ [-Wparentheses]
                433 | SerialPortParity NAN_INLINE(ToParityEnum(const v8::Local<v8::String>& v8                                               str)) {
                    |                            ^
              ../src/serialport.cpp:452:30: warning: unnecessary parentheses in declaration of                                                ‘ToStopBitEnum’ [-Wparentheses]
                452 | SerialPortStopBits NAN_INLINE(ToStopBitEnum(double stopBits)) {
                    |                              ^
              In file included from ../node_modules/nan/nan.h:58,
                               from ../src/./serialport.h:13,
                               from ../src/serialport.cpp:1:
              /home/iobroker/.cache/node-gyp/16.13.0/include/node/node.h:821:7: warning: cast                                                between incompatible function types from ‘void (*)(Nan::ADDON_REGISTER_FUNCTION_                                               ARGS_TYPE)’ {aka ‘void (*)(v8::Local<v8::Object>)’} to ‘node::addon_register_fun                                               c’ {aka ‘void (*)(v8::Local<v8::Object>, v8::Local<v8::Value>, void*)’} [-Wcast-                                               function-type]
                821 |       (node::addon_register_func) (regfunc),                          \
                    |       ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
              /home/iobroker/.cache/node-gyp/16.13.0/include/node/node.h:855:3: note: in expan                                               sion of macro ‘NODE_MODULE_X’
                855 |   NODE_MODULE_X(modname, regfunc, NULL, 0)  // NOLINT (readability/null_                                               usage)
                    |   ^~~~~~~~~~~~~
              ../src/serialport.cpp:486:1: note: in expansion of macro ‘NODE_MODULE’
                486 | NODE_MODULE(serialport, init);
                    | ^~~~~~~~~~~
                CXX(target) Release/obj.target/bindings/src/serialport_unix.o
              ../src/serialport_unix.cpp: In function ‘int setup(int, OpenBaton*)’:
              ../src/serialport_unix.cpp:179:82: warning: ‘%s’ directive output may be truncat                                               ed writing up to 1023 bytes into a region of size 1005 [-Wformat-truncation=]
                179 | rorString, sizeof(data->errorString), "Error %s Cannot open %s", strerro                                               r(errno), data->path);
                    |                                                             ^~
              
              ../src/serialport_unix.cpp:179:13: note: ‘snprintf’ output 20 or more bytes (ass                                               uming 1043) into a destination of size 1024
                179 |     snprintf(data->errorString, sizeof(data->errorString), "Error %s Can                                               not open %s", strerror(errno), data->path);
                    |     ~~~~~~~~^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~                                               ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
              ../src/serialport_unix.cpp: In function ‘void EIO_Open(uv_work_t*)’:
              ../src/serialport_unix.cpp:89:84: warning: ‘%s’ directive output may be truncate                                               d writing up to 1023 bytes into a region of size 1003 [-Wformat-truncation=]
                 89 | rString, sizeof(data->errorString), "Error: %s, cannot open %s", strerro                                               r(errno), data->path);
                    |                                                             ^~
              
              ../src/serialport_unix.cpp:89:13: note: ‘snprintf’ output 22 or more bytes (assu                                               ming 1045) into a destination of size 1024
                 89 |     snprintf(data->errorString, sizeof(data->errorString), "Error: %s, c                                               annot open %s", strerror(errno), data->path);
                    |     ~~~~~~~~^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~                                               ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
                CXX(target) Release/obj.target/bindings/src/poller.o
                CXX(target) Release/obj.target/bindings/src/serialport_linux.o
                SOLINK_MODULE(target) Release/obj.target/bindings.node
                COPY Release/bindings.node
              make: Verzeichnis „/opt/iobroker/node_modules/zigbee-herdsman/node_modules/@seri                                               alport/bindings/build“ wird verlassen
              
              added 65 packages, and audited 66 packages in 29s
              
              8 packages are looking for funding
                run `npm fund` for details
              
              found 0 vulnerabilities
              
              
              host.iobroker
              2021-11-19 06:30:40.587	info	iobroker npm-rebuild: exit 0
              host.iobroker
              2021-11-19 06:30:39.564	info	iobroker npm-rebuild: Rebuild zigbee done
              host.iobroker
              2021-11-19 06:30:39.539	info	iobroker npm-rebuild: npm ERR! A complete log of this run can be found in:npm ERR! /home/iobroker/.npm/_logs/2021-11-19T05_30_39_483Z-debug.log
              host.iobroker
              2021-11-19 06:30:39.531	info	iobroker npm-rebuild:
              host.iobroker
              2021-11-19 06:30:39.483	info	iobroker npm-rebuild: npm ERR! Fix the upstream dependency conflict, or retrynpm ERR! this command with --force, or --legacy-peer-depsnpm ERR! to accept an incorrect (and potentially broken) dependency resolution.npm ERR! npm ERR! See /home/iobroker/.npm/eresolve-report.txt for a full report.
              host.iobroker
              2021-11-19 06:30:39.480	info	iobroker npm-rebuild: npm ERR! While resolving: iobroker.zigbee@1.6.6npm ERR! Found: eslint@7.32.0npm ERR! node_modules/eslintnpm ERR! dev eslint@"^7.18.0" from the root projectnpm ERR! npm ERR! Could not resolve dependency:npm ERR! peer eslint@"4.x" from lint-diff@1.2.1npm ERR! node_modules/lint-diffnpm ERR! dev lint-diff@"*" from the root projectnpm ERR!
              host.iobroker
              2021-11-19 06:30:39.462	info	iobroker npm-rebuild: npm ERR!
              host.iobroker
              2021-11-19 06:30:39.461	info	iobroker npm-rebuild: npm ERR! ERESOLVE unable to resolve dependency tree
              host.iobroker
              2021-11-19 06:30:39.441	info	iobroker npm-rebuild: npm ERR! code ERESOLVE
              host.iobroker
              2021-11-19 06:30:38.629	info	instance system.adapter.heatingcontrol.0 started with pid 9210
              host.iobroker
              2021-11-19 06:30:34.124	info	instance system.adapter.lgtv.0 started with pid 9096
              host.iobroker
              2021-11-19 06:30:33.277	info	iobroker npm-rebuild: npm install --loglevel error --production (System call1) in "/opt/iobroker/node_modules/iobroker.zigbee"
              host.iobroker
              2021-11-19 06:30:31.860	info	iobroker rebuild zigbee --install
              
              apollon77A Offline
              apollon77A Offline
              apollon77
              schrieb am zuletzt editiert von
              #136

              @cino kannst du zigbee vllt aktualisieren? Da scheint bei dir irgendwas rech strange zu sein. Ansonsten lösch das node_modules/iobroker.zigbee Verzeichnuis und starte die Instanz neu, dann sollte es neu installiert weren. Hat mich dem Node.js Update weniger zu tun ...

              Beitrag hat geholfen? Votet rechts unten im Beitrag :-) https://paypal.me/Apollon77 / https://github.com/sponsors/Apollon77

              • Debug-Log für Instanz einschalten? Admin -> Instanzen -> Expertenmodus -> Instanz aufklappen - Loglevel ändern
              • Logfiles auf Platte /opt/iobroker/log/… nutzen, Admin schneidet Zeilen ab
              1 Antwort Letzte Antwort
              0
              • crunchipC Abwesend
                crunchipC Abwesend
                crunchip
                Forum Testing Most Active
                schrieb am zuletzt editiert von
                #137

                @cino gemeint war eher die Ausgabe von node/nodejs/npm

                umgestiegen von Proxmox auf Unraid

                1 Antwort Letzte Antwort
                0
                • DiginixD Offline
                  DiginixD Offline
                  Diginix
                  schrieb am zuletzt editiert von
                  #138

                  @apollon77 Habe heute nodeJS von 12 auf 14 aktualisiert und dabei noch den JS-Controller von 3.3.18 auf 3.3.19.
                  Update selbst inkl:

                  iobroker fix
                  npm rebuild
                  

                  Danach verhielten sich dennoch div. Adapter merkwürdig. Der web ist z.T. im loop pro Sek mehrfach abgestürzt mit:

                  2021-11-19 12:54:18 - warn: web.0 (2835245) Cannot parse "undefined"
                  2021-11-19 12:54:18 - warn: web.0 (2835245) socket.io [use] unknown user
                  

                  Außerdem wurden dann mehrere Adapter immer neu gestartet mit Meldung "already running".
                  Am Ende habe ich über alle /opt/iobroker/node_modules/iobroker.%adapter% ein

                  iobroker rebuild %adapter% --install
                  

                  laufen lassen.
                  In /opt/iobroker/node_modules gibt es natürlich noch viele Ordner die nicht nicht "iobroker.xxx" heißen. Ob darin nun noch was aus nodeJS 12 Zeiten ist und rebuilded werden müsste, kann ich nicht sagen.
                  Nach einem kompletten Reboot läuft nun seit 1h erstmal alles ruhig.

                  ..:: So long! Tom ::..

                  NUC7i3 (Ubuntu Proxmox VM) | Echo Dots 2+3. Gen | Xiaomi Sensoren | Mi Robot 1S | Yeelight | Sonoff | Shelly | H801 RGB | Gosund SP1 | NodeMCU+ESP32 | Kostal Plenticore PV+BYD | openWB

                  1 Antwort Letzte Antwort
                  0
                  • B backfisch88

                    Hallo

                    jedes mal (schon öfter probiert), wenn ich auf nodejs 14 upgrade läuft danach der mihome-vacuum Adapter nicht mehr.
                    Es läuft alles Reibungslos, bis es ein Befehl von IOBroker kommt... nach einigen Minuten ist er wieder verbunden (manchmal auch länger) und das Spiel geht von vorne los
                    mit node 12.X lief alles normal

                    Auszug aus dem Log

                    
                    mihome-vacuum.0
                    2021-11-18 13:32:51.245	info	Map selected create states...
                    
                    mihome-vacuum.0
                    2021-11-18 13:32:50.686	info	settest next timer: not available
                    
                    mihome-vacuum.0
                    2021-11-18 13:32:50.159	info	select standard vacuum protocol....
                    
                    mihome-vacuum.0
                    2021-11-18 13:32:50.144	warn	No Answer for DeviceModel use model from Config
                    
                    mihome-vacuum.0
                    2021-11-18 13:32:50.144	warn	No Answer for DeviceModel use old one
                    
                    mihome-vacuum.0
                    2021-11-18 13:32:50.143	warn	YOUR DEVICE IS CONNECTED BUT DID NOT ANSWER YET - CONNECTION CAN TAKE UP TO 10 MINUTES - PLEASE BE PATIENT AND DO NOT TURN THE ADAPTER OFF
                    
                    mihome-vacuum.0
                    2021-11-18 13:32:40.089	info	IOT enabled, create state
                    
                    mihome-vacuum.0
                    2021-11-18 13:32:39.827	info	starting. Version 3.3.1 in /opt/iobroker/node_modules/iobroker.mihome-vacuum, node: v14.18.1, js-controller: 3.3.19
                    host.IOBroker
                    2021-11-18 13:32:37.671	info	instance system.adapter.mihome-vacuum.0 started with pid 14078
                    host.IOBroker
                    2021-11-18 13:32:36.632	info	Restart adapter system.adapter.mihome-vacuum.0 because enabled
                    host.IOBroker
                    2021-11-18 13:32:36.631	info	instance system.adapter.mihome-vacuum.0 terminated with code NaN ()
                    host.IOBroker
                    2021-11-18 13:32:36.624	warn	instance system.adapter.mihome-vacuum.0 terminated due to SIGBUS
                    
                    mihome-vacuum.0
                    2021-11-18 13:31:26.406	info	trigger cleaning segment 17
                    
                    mihome-vacuum.0
                    2021-11-18 13:31:16.313	info	create state for carpet_mode
                    
                    mihome-vacuum.0
                    2021-11-18 13:31:15.114	info	create states for mop
                    
                    mihome-vacuum.0
                    2021-11-18 13:31:15.103	info	create states for water box
                    
                    mihome-vacuum.0
                    2021-11-18 13:31:15.087	info	change states from State control.fan_power
                    
                    mihome-vacuum.0
                    2021-11-18 13:31:15.068	info	Map selected create states...
                    
                    mihome-vacuum.0
                    2021-11-18 13:31:14.463	info	settest next timer: not available
                    
                    mihome-vacuum.0
                    2021-11-18 13:31:13.932	info	select standard vacuum protocol....
                    
                    mihome-vacuum.0
                    2021-11-18 13:31:13.815	info	IOT enabled, create state
                    
                    mihome-vacuum.0
                    2021-11-18 13:31:13.539	info	starting. Version 3.3.1 in /opt/iobroker/node_modules/iobroker.mihome-vacuum, node: v14.18.1, js-controller: 3.3.19
                    
                    mihome-vacuum.0 | 2021-11-18 12:49:49.814 | info | Map selected create states...
                    -- | -- | -- | --
                    mihome-vacuum.0 | 2021-11-18 12:49:49.125 | info | settest next timer: not available
                    mihome-vacuum.0 | 2021-11-18 12:49:48.595 | info | select standard vacuum protocol....
                    mihome-vacuum.0 | 2021-11-18 12:49:48.569 | warn | No Answer for DeviceModel use model from Config
                    mihome-vacuum.0 | 2021-11-18 12:49:48.568 | warn | No Answer for DeviceModel use old one
                    mihome-vacuum.0 | 2021-11-18 12:49:48.567 | warn | YOUR DEVICE IS CONNECTED BUT DID NOT ANSWER YET - CONNECTION CAN TAKE UP TO 10 MINUTES - PLEASE BE PATIENT AND DO NOT TURN THE ADAPTER OFF
                    mihome-vacuum.0 | 2021-11-18 12:49:38.508 | info | IOT enabled, create state
                    mihome-vacuum.0 | 2021-11-18 12:49:38.255 | info | starting. Version 3.3.1 in /opt/iobroker/node_modules/iobroker.mihome-vacuum, node: v14.18.1, js-controller: 3.3.19
                    host.IOBroker | 2021-11-18 12:49:36.130 | info | instance system.adapter.mihome-vacuum.0 started with pid 6957
                    host.IOBroker | 2021-11-18 12:49:35.072 | info | Restart adapter system.adapter.mihome-vacuum.0 because enabled
                    host.IOBroker | 2021-11-18 12:49:35.071 | info | instance system.adapter.mihome-vacuum.0 terminated with code NaN ()
                    host.IOBroker | 2021-11-18 12:49:35.070 | warn | instance system.adapter.mihome-vacuum.0 terminated due to SIGABRT
                    host.IOBroker | 2021-11-18 12:49:35.063 | error | Caught by controller[0]: free(): invalid pointer
                    mihome-vacuum.0 | 2021-11-18 12:49:15.488 | info | trigger cleaning segment 17
                    mihome-vacuum.0 | 2021-11-18 12:49:00.086 | info | create state for carpet_mode
                    mihome-vacuum.0 | 2021-11-18 12:48:58.907 | info | create states for mop
                    mihome-vacuum.0 | 2021-11-18 12:48:58.904 | info | create states for water box
                    mihome-vacuum.0 | 2021-11-18 12:48:58.872 | info | change states from State control.fan_power
                    mihome-vacuum.0 | 2021-11-18 12:48:58.839 | info | Map selected create states..
                    

                    jemand eine Idee?
                    updated über
                    curl -sL https://deb.nodesource.com/setup_14.x | sudo -E bash -
                    sudo apt-get install -y nodejs
                    iobroker fix

                    zusätzlich:
                    iobroker rebuild ioBroker.mihome-vacuum
                    iobroker rebuild ioBroker.mihome-vacuum --install

                    und ein rebuild in: opt/iobroker/
                    und iobroker stop && sudo apt update && sudo apt upgrade -y && iobroker start

                    und in github ein issue aufgemacht, wo ich hierhin verwiesen wurde :)

                    und nochmal im DEBUG

                    
                    mihome-vacuum.0
                    2021-11-18 13:39:10.415	debug	load Map creator... true
                    
                    mihome-vacuum.0
                    2021-11-18 13:39:10.257	debug	Schedule restart: 0 0,1 * * *
                    
                    mihome-vacuum.0
                    2021-11-18 13:39:10.172	info	starting. Version 3.3.1 in /opt/iobroker/node_modules/iobroker.mihome-vacuum, node: v14.18.1, js-controller: 3.3.19
                    
                    mihome-vacuum.0
                    2021-11-18 13:39:09.903	debug	Plugin sentry Initialize Plugin (enabled=true)
                    
                    mihome-vacuum.0
                    2021-11-18 13:39:06.008	warn	Terminated (UNCAUGHT_EXCEPTION): Without reason
                    
                    mihome-vacuum.0
                    2021-11-18 13:39:06.007	debug	Plugin sentry destroyed
                    
                    mihome-vacuum.0
                    2021-11-18 13:39:06.006	info	terminating
                    
                    mihome-vacuum.0
                    2021-11-18 13:39:06.005	error	Socket Close
                    
                    mihome-vacuum.0
                    2021-11-18 13:39:05.799	error	undefined
                    
                    mihome-vacuum.0
                    2021-11-18 13:39:05.798	error	unhandled promise rejection: undefined
                    
                    mihome-vacuum.0
                    2021-11-18 13:39:05.798	error	Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch().
                    
                    mihome-vacuum.0
                    2021-11-18 13:39:05.796	debug	MIIO Receive Timeout for "app_segment_clean" <<<
                    
                    mihome-vacuum.0
                    2021-11-18 13:39:04.078	debug	Message= {"id":17,"method":"get_multi_maps_list"}
                    
                    mihome-vacuum.0
                    2021-11-18 13:39:04.077	debug	ERROR at setGetSoundVolume: MESSAGE TIMEOUT
                    
                    mihome-vacuum.0
                    2021-11-18 13:39:04.076	debug	MIIO Receive Timeout for "get_sound_volume" <<<
                    
                    mihome-vacuum.0
                    2021-11-18 13:39:03.794	debug	Message= {"id":16,"method":"app_segment_clean","params":[17]}
                    
                    mihome-vacuum.0
                    2021-11-18 13:39:03.793	info	trigger cleaning segment 17
                    
                    mihome-vacuum.0
                    2021-11-18 13:39:03.792	debug	start Cleaning: 18 MObj: {"command":"cleanSegments","message":"17","from":"system.adapter.mihome-vacuum.0","_id":62189570,"segments":[17],"channels":["mihome-vacuum.0.rooms.73001006380"]}
                    
                    mihome-vacuum.0
                    2021-11-18 13:39:03.791	debug	We are in onMessage:{"command":"cleanSegments","message":{"segments":[17],"channels":["mihome-vacuum.0.rooms.73001006380"]},"from":"system.adapter.mihome-vacuum.0","_id":62189570}
                    
                    mihome-vacuum.0
                    2021-11-18 13:39:03.784	debug	sendTo "cleanSegments" to system.adapter.mihome-vacuum.0 from system.adapter.mihome-vacuum.0
                    
                    mihome-vacuum.0
                    2021-11-18 13:39:03.779	debug	command: roomClean parent: 73001006380
                    
                    DiginixD Offline
                    DiginixD Offline
                    Diginix
                    schrieb am zuletzt editiert von Diginix
                    #139

                    @backfisch88 sagte in [How-to] Node.js für ioBroker richtig updaten - 2021 Edition:

                    Hallo

                    jedes mal (schon öfter probiert), wenn ich auf nodejs 14 upgrade läuft danach der mihome-vacuum Adapter nicht mehr.
                    Es läuft alles Reibungslos, bis es ein Befehl von IOBroker kommt... nach einigen Minuten ist er wieder verbunden (manchmal auch länger) und das Spiel geht von vorne los
                    mit node 12.X lief alles normal

                    Wie du ein Post weiter oben lesen kannst, habe ich heute auch ein Rundumschlag mit Updates gemacht.
                    Ich nutze mihome-vacuum in Ver. 3.3.1 mit einem Xiaomi M1S. Der Adapter funktionierte nach dem dem nodeJS Update sofort, nur Canvas musste für die Karte neu gebaut werden. Seit dem hat der Sauger auch schon 3 Räume mit immer aktueller Karte gesaugt.

                    ..:: So long! Tom ::..

                    NUC7i3 (Ubuntu Proxmox VM) | Echo Dots 2+3. Gen | Xiaomi Sensoren | Mi Robot 1S | Yeelight | Sonoff | Shelly | H801 RGB | Gosund SP1 | NodeMCU+ESP32 | Kostal Plenticore PV+BYD | openWB

                    B 1 Antwort Letzte Antwort
                    0
                    • C Offline
                      C Offline
                      Cino
                      schrieb am zuletzt editiert von
                      #140

                      Heute morgen aufgewacht und der Zigbee Adapter lief. Keine Ahnung warum.

                      IOB@RPI4
                      Shelly, Zigbee, ebus

                      Thomas BraunT 1 Antwort Letzte Antwort
                      0
                      • C Cino

                        Heute morgen aufgewacht und der Zigbee Adapter lief. Keine Ahnung warum.

                        Thomas BraunT Online
                        Thomas BraunT Online
                        Thomas Braun
                        Most Active
                        schrieb am zuletzt editiert von
                        #141

                        @cino sagte in [How-to] Node.js für ioBroker richtig updaten - 2021 Edition:

                        Heute morgen aufgewacht und der Zigbee Adapter lief. Keine Ahnung warum.

                        Vermutlich, weil der rebuild zwischenzeitlich durchgelaufen ist.

                        Linux-Werkzeugkasten:
                        https://forum.iobroker.net/topic/42952/der-kleine-iobroker-linux-werkzeugkasten
                        NodeJS Fixer Skript:
                        https://forum.iobroker.net/topic/68035/iob-node-fix-skript
                        iob_diag: curl -sLf -o diag.sh https://iobroker.net/diag.sh && bash diag.sh

                        C 1 Antwort Letzte Antwort
                        0
                        • apollon77A apollon77

                          @backfisch88 Ich glaube der Fehler hier sieht jetzt eher aus wie https://github.com/iobroker-community-adapters/ioBroker.mihome-vacuum/issues/428

                          B Offline
                          B Offline
                          backfisch88
                          schrieb am zuletzt editiert von
                          #142

                          @apollon77 habe wieder auf 12.X Downgraded.

                          egal was man macht... nach einem Befehl ist der Adapter auf rot... Staubsauger reagiert in der App, aber im Adapter eben nicht... auch nach neustart des Adapters manchmal nicht... Reconnect Zeit zwischen 2 Minuten und X Stunden

                          Thomas BraunT 1 Antwort Letzte Antwort
                          0
                          • DiginixD Diginix

                            @backfisch88 sagte in [How-to] Node.js für ioBroker richtig updaten - 2021 Edition:

                            Hallo

                            jedes mal (schon öfter probiert), wenn ich auf nodejs 14 upgrade läuft danach der mihome-vacuum Adapter nicht mehr.
                            Es läuft alles Reibungslos, bis es ein Befehl von IOBroker kommt... nach einigen Minuten ist er wieder verbunden (manchmal auch länger) und das Spiel geht von vorne los
                            mit node 12.X lief alles normal

                            Wie du ein Post weiter oben lesen kannst, habe ich heute auch ein Rundumschlag mit Updates gemacht.
                            Ich nutze mihome-vacuum in Ver. 3.3.1 mit einem Xiaomi M1S. Der Adapter funktionierte nach dem dem nodeJS Update sofort, nur Canvas musste für die Karte neu gebaut werden. Seit dem hat der Sauger auch schon 3 Räume mit immer aktueller Karte gesaugt.

                            B Offline
                            B Offline
                            backfisch88
                            schrieb am zuletzt editiert von
                            #143

                            @diginix saugen tut er... aber eben nur ein mal... dann geht der Adapter sofort auf Rot

                            1 Antwort Letzte Antwort
                            0
                            • B backfisch88

                              @apollon77 habe wieder auf 12.X Downgraded.

                              egal was man macht... nach einem Befehl ist der Adapter auf rot... Staubsauger reagiert in der App, aber im Adapter eben nicht... auch nach neustart des Adapters manchmal nicht... Reconnect Zeit zwischen 2 Minuten und X Stunden

                              Thomas BraunT Online
                              Thomas BraunT Online
                              Thomas Braun
                              Most Active
                              schrieb am zuletzt editiert von
                              #144

                              @backfisch88

                              Dann mach beim Adapter ein Issue auf, damit der Maintainer sich das ggf. anschauen kann. Wobei sich das sehr nach einem Individual-Problem anhört.

                              Linux-Werkzeugkasten:
                              https://forum.iobroker.net/topic/42952/der-kleine-iobroker-linux-werkzeugkasten
                              NodeJS Fixer Skript:
                              https://forum.iobroker.net/topic/68035/iob-node-fix-skript
                              iob_diag: curl -sLf -o diag.sh https://iobroker.net/diag.sh && bash diag.sh

                              B 1 Antwort Letzte Antwort
                              0
                              • Thomas BraunT Thomas Braun

                                @cino sagte in [How-to] Node.js für ioBroker richtig updaten - 2021 Edition:

                                Heute morgen aufgewacht und der Zigbee Adapter lief. Keine Ahnung warum.

                                Vermutlich, weil der rebuild zwischenzeitlich durchgelaufen ist.

                                C Offline
                                C Offline
                                Cino
                                schrieb am zuletzt editiert von
                                #145

                                @thomas-braun said in [How-to] Node.js für ioBroker richtig updaten - 2021 Edition:

                                @cino sagte in [How-to] Node.js für ioBroker richtig updaten - 2021 Edition:

                                Heute morgen aufgewacht und der Zigbee Adapter lief. Keine Ahnung warum.

                                Vermutlich, weil der rebuild zwischenzeitlich durchgelaufen ist.

                                Ja aber in den Logs stand doch von wegen 3 mal versucht und der Adapter wird deaktiviert.

                                IOB@RPI4
                                Shelly, Zigbee, ebus

                                G 1 Antwort Letzte Antwort
                                0
                                • C Cino

                                  @thomas-braun said in [How-to] Node.js für ioBroker richtig updaten - 2021 Edition:

                                  @cino sagte in [How-to] Node.js für ioBroker richtig updaten - 2021 Edition:

                                  Heute morgen aufgewacht und der Zigbee Adapter lief. Keine Ahnung warum.

                                  Vermutlich, weil der rebuild zwischenzeitlich durchgelaufen ist.

                                  Ja aber in den Logs stand doch von wegen 3 mal versucht und der Adapter wird deaktiviert.

                                  G Offline
                                  G Offline
                                  guergen
                                  schrieb am zuletzt editiert von guergen
                                  #146

                                  Nach dem Update von nodejs auf v14.18.1 kommt beim maxcul-Adapter folgender Fehler:

                                  maxcul.0
                                  	2021-11-19 19:32:59.319	error	Exception-Code: ERR_DLOPEN_FAILED: Module did not self-register: '/opt/iobroker/node_modules/@serialport/bindings/build/Release/bindings.node'.
                                  maxcul.0
                                  	2021-11-19 19:32:59.319	error	Error: Module did not self-register: '/opt/iobroker/node_modules/@serialport/bindings/build/Release/bindings.node'. at Object.Module._extensions..node (internal/modules/cjs/loader.js:1144:18) at Module.load (internal/modules/cjs/loader.js:950:32) at Function.Module._load (internal/modules/cjs/loader.js:790:12) at Module.require (internal/modules/cjs/loader.js:974:19) at require (internal/modules/cjs/helpers.js:93:18) at bindings (/opt/iobroker/node_modules/bindings/bindings.js:112:48) at Object.<anonymous> (/opt/iobroker/node_modules/@serialport/bindings/lib/linux.js:2:36) at Module._compile (internal/modules/cjs/loader.js:1085:14) at Object.Module._extensions..js (internal/modules/cjs/loader.js:1114:10) at Module.load (internal/modules/cjs/loader.js:950:32) at Function.Module._load (internal/modules/cjs/loader.js:790:12) at Module.require (internal/modules/cjs/loader.js:974:19) at require (internal/modules/cjs/helpers.js:93:18) at Object.<anonymous> (/opt/iobroker/node_modules/@serialport/bindings/lib/index.js:14:22) at Module._compile (internal/modules/cjs/loader.js:1085:14) at Object.Module._extensions..js (internal/modules/cjs/loader.js:1114:10)
                                  maxcul.0
                                  	2021-11-19 19:32:59.317	error	uncaught exception: Module did not self-register: '/opt/iobroker/node_modules/@serialport/bindings/build/Release/bindings.node'.
                                  

                                  Werde aus den ganzen "Lösungen" nicht ganz schlau....
                                  npm rebuild hat nichts gebracht
                                  NPM v6.14.15
                                  js-controller 3.3.19

                                  Beim Slave hat alles geklappt
                                  Bin jetzt auf dem Host auf 12 zurück, ohne Heizung geht es grade nicht ;-)

                                  Thomas BraunT apollon77A 2 Antworten Letzte Antwort
                                  0
                                  • G guergen

                                    Nach dem Update von nodejs auf v14.18.1 kommt beim maxcul-Adapter folgender Fehler:

                                    maxcul.0
                                    	2021-11-19 19:32:59.319	error	Exception-Code: ERR_DLOPEN_FAILED: Module did not self-register: '/opt/iobroker/node_modules/@serialport/bindings/build/Release/bindings.node'.
                                    maxcul.0
                                    	2021-11-19 19:32:59.319	error	Error: Module did not self-register: '/opt/iobroker/node_modules/@serialport/bindings/build/Release/bindings.node'. at Object.Module._extensions..node (internal/modules/cjs/loader.js:1144:18) at Module.load (internal/modules/cjs/loader.js:950:32) at Function.Module._load (internal/modules/cjs/loader.js:790:12) at Module.require (internal/modules/cjs/loader.js:974:19) at require (internal/modules/cjs/helpers.js:93:18) at bindings (/opt/iobroker/node_modules/bindings/bindings.js:112:48) at Object.<anonymous> (/opt/iobroker/node_modules/@serialport/bindings/lib/linux.js:2:36) at Module._compile (internal/modules/cjs/loader.js:1085:14) at Object.Module._extensions..js (internal/modules/cjs/loader.js:1114:10) at Module.load (internal/modules/cjs/loader.js:950:32) at Function.Module._load (internal/modules/cjs/loader.js:790:12) at Module.require (internal/modules/cjs/loader.js:974:19) at require (internal/modules/cjs/helpers.js:93:18) at Object.<anonymous> (/opt/iobroker/node_modules/@serialport/bindings/lib/index.js:14:22) at Module._compile (internal/modules/cjs/loader.js:1085:14) at Object.Module._extensions..js (internal/modules/cjs/loader.js:1114:10)
                                    maxcul.0
                                    	2021-11-19 19:32:59.317	error	uncaught exception: Module did not self-register: '/opt/iobroker/node_modules/@serialport/bindings/build/Release/bindings.node'.
                                    

                                    Werde aus den ganzen "Lösungen" nicht ganz schlau....
                                    npm rebuild hat nichts gebracht
                                    NPM v6.14.15
                                    js-controller 3.3.19

                                    Beim Slave hat alles geklappt
                                    Bin jetzt auf dem Host auf 12 zurück, ohne Heizung geht es grade nicht ;-)

                                    Thomas BraunT Online
                                    Thomas BraunT Online
                                    Thomas Braun
                                    Most Active
                                    schrieb am zuletzt editiert von
                                    #147

                                    @guergen

                                    maxcul deinstallieren und nochmal neu installieren.

                                    Linux-Werkzeugkasten:
                                    https://forum.iobroker.net/topic/42952/der-kleine-iobroker-linux-werkzeugkasten
                                    NodeJS Fixer Skript:
                                    https://forum.iobroker.net/topic/68035/iob-node-fix-skript
                                    iob_diag: curl -sLf -o diag.sh https://iobroker.net/diag.sh && bash diag.sh

                                    1 Antwort Letzte Antwort
                                    0
                                    • G guergen

                                      Nach dem Update von nodejs auf v14.18.1 kommt beim maxcul-Adapter folgender Fehler:

                                      maxcul.0
                                      	2021-11-19 19:32:59.319	error	Exception-Code: ERR_DLOPEN_FAILED: Module did not self-register: '/opt/iobroker/node_modules/@serialport/bindings/build/Release/bindings.node'.
                                      maxcul.0
                                      	2021-11-19 19:32:59.319	error	Error: Module did not self-register: '/opt/iobroker/node_modules/@serialport/bindings/build/Release/bindings.node'. at Object.Module._extensions..node (internal/modules/cjs/loader.js:1144:18) at Module.load (internal/modules/cjs/loader.js:950:32) at Function.Module._load (internal/modules/cjs/loader.js:790:12) at Module.require (internal/modules/cjs/loader.js:974:19) at require (internal/modules/cjs/helpers.js:93:18) at bindings (/opt/iobroker/node_modules/bindings/bindings.js:112:48) at Object.<anonymous> (/opt/iobroker/node_modules/@serialport/bindings/lib/linux.js:2:36) at Module._compile (internal/modules/cjs/loader.js:1085:14) at Object.Module._extensions..js (internal/modules/cjs/loader.js:1114:10) at Module.load (internal/modules/cjs/loader.js:950:32) at Function.Module._load (internal/modules/cjs/loader.js:790:12) at Module.require (internal/modules/cjs/loader.js:974:19) at require (internal/modules/cjs/helpers.js:93:18) at Object.<anonymous> (/opt/iobroker/node_modules/@serialport/bindings/lib/index.js:14:22) at Module._compile (internal/modules/cjs/loader.js:1085:14) at Object.Module._extensions..js (internal/modules/cjs/loader.js:1114:10)
                                      maxcul.0
                                      	2021-11-19 19:32:59.317	error	uncaught exception: Module did not self-register: '/opt/iobroker/node_modules/@serialport/bindings/build/Release/bindings.node'.
                                      

                                      Werde aus den ganzen "Lösungen" nicht ganz schlau....
                                      npm rebuild hat nichts gebracht
                                      NPM v6.14.15
                                      js-controller 3.3.19

                                      Beim Slave hat alles geklappt
                                      Bin jetzt auf dem Host auf 12 zurück, ohne Heizung geht es grade nicht ;-)

                                      apollon77A Offline
                                      apollon77A Offline
                                      apollon77
                                      schrieb am zuletzt editiert von
                                      #148

                                      @guergen sagte in [How-to] Node.js für ioBroker richtig updaten - 2021 Edition:

                                      /opt/iobroker/node_modules/@serialport/bindings

                                      Mal in das Verzeichnis wechseln und dort ein "npm install --production" machen

                                      Beitrag hat geholfen? Votet rechts unten im Beitrag :-) https://paypal.me/Apollon77 / https://github.com/sponsors/Apollon77

                                      • Debug-Log für Instanz einschalten? Admin -> Instanzen -> Expertenmodus -> Instanz aufklappen - Loglevel ändern
                                      • Logfiles auf Platte /opt/iobroker/log/… nutzen, Admin schneidet Zeilen ab
                                      M 1 Antwort Letzte Antwort
                                      1
                                      • apollon77A apollon77

                                        @guergen sagte in [How-to] Node.js für ioBroker richtig updaten - 2021 Edition:

                                        /opt/iobroker/node_modules/@serialport/bindings

                                        Mal in das Verzeichnis wechseln und dort ein "npm install --production" machen

                                        M Offline
                                        M Offline
                                        Marty56
                                        schrieb am zuletzt editiert von
                                        #149

                                        @apollon77 Ich habe node v12.22.7. Ist das richtig, dass ich noch ca. 2 Jahre mit dem Update warten kann?

                                        HW:NUC (16 GB Ram)
                                        OS: Debian Bullseye, Promox V7, node v16.x npm 8.19.3

                                        J Thomas BraunT apollon77A 3 Antworten Letzte Antwort
                                        0
                                        • M Marty56

                                          @apollon77 Ich habe node v12.22.7. Ist das richtig, dass ich noch ca. 2 Jahre mit dem Update warten kann?

                                          J Offline
                                          J Offline
                                          Jan1
                                          schrieb am zuletzt editiert von
                                          #150

                                          @marty56
                                          Theoretisch ja nur praktisch nicht sinnvoll. Ich bin schon lange auf 14 und null Probleme ;)

                                          M 1 Antwort Letzte Antwort
                                          0
                                          Antworten
                                          • In einem neuen Thema antworten
                                          Anmelden zum Antworten
                                          • Älteste zuerst
                                          • Neuste zuerst
                                          • Meiste Stimmen


                                          Support us

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

                                          964

                                          Online

                                          32.4k

                                          Benutzer

                                          81.5k

                                          Themen

                                          1.3m

                                          Beiträge
                                          Community
                                          Impressum | Datenschutz-Bestimmungen | Nutzungsbedingungen | Einwilligungseinstellungen
                                          ioBroker Community 2014-2025
                                          logo
                                          • Anmelden

                                          • Du hast noch kein Konto? Registrieren

                                          • Anmelden oder registrieren, um zu suchen
                                          • Erster Beitrag
                                            Letzter Beitrag
                                          0
                                          • Home
                                          • Aktuell
                                          • Tags
                                          • Ungelesen 0
                                          • Kategorien
                                          • Unreplied
                                          • Beliebt
                                          • GitHub
                                          • Docu
                                          • Hilfe