npm Error bei mihome-vacuum Adapter Installation
-
Der mihome-vacuum Adapter wird nicht angezeigt
"iob update"
Used repository: stable Adapter "admin" : 6.13.16 , installed 6.13.16 Adapter "backitup" : 2.10.11 , installed 2.10.11 Adapter "daikin" : 1.4.2 , installed 1.4.2 Adapter "discovery" : 4.4.0 , installed 3.0.3 [Updatable] Adapter "ems-esp" : 3.0.3 , installed 2.8.0 [Updatable] Adapter "hm-rega" : 4.0.0 , installed 4.0.0 Adapter "hm-rpc" : 1.16.0 , installed 1.16.0 Adapter "influxdb" : 4.0.2 , installed 4.0.2 Adapter "javascript" : 7.8.0 , installed 7.8.0 Controller "js-controller": 5.0.19 , installed 5.0.19 Adapter "modbus" : 6.1.0 , installed 6.1.0 Adapter "node-red" : 5.2.0 , installed 5.1.0 [Updatable] Adapter "pushover" : 3.0.6 , installed 3.0.6 Adapter "rpi2" : 1.3.2 , installed 1.3.2 Adapter "shelly" : 6.8.0 , installed 6.6.1 [Updatable] Adapter "simple-api" : 2.7.2 , installed 2.7.2 Adapter "smartmeter" : 3.4.0 , installed 3.4.0 Adapter "socketio" : 6.6.1 , installed 4.2.0 [Updatable] Adapter "tado" : 0.5.3 , installed 0.5.3 Adapter "tankerkoenig" : 3.3.7 , installed 2.1.1 [Updatable] Adapter "tuya" : 3.15.0 , installed 3.15.0 Adapter "web" : 6.2.3 , installed 4.3.0 [Updatable] Adapter "ws" : 2.5.11 , installed 1.3.0 [Updatable] Adapter "zigbee" : 1.10.1 , installed 1.10.1"iob upgrade"
This upgrade of "ws" will at least introduce the following changes: ========================================================================== -> 2.5.11: Some packages were updated -> 2.5.10: updated ws-server to increase file limit to 500 MB -> 2.5.9: Corrected the crash if authentication is enabled -> 2.5.8: Corrected adapter termination if the alias has no target -> 2.5.7: upgraded socket-classes to fix vis problems -> 2.5.6: upgraded socket-classes to correct the error by unsubscribing on client disconnect -> 2.5.5: upgraded socket-classes to fix crash cases ========================================================================== BE CAREFUL: THIS IS A MAJOR UPGRADE, WHICH WILL MOST LIKELY INTRODUCE BREAKING CHANGES! Would you like to upgrade ws from @1.3.0 to @2.5.11 now? [(y)es, (n)o]: Y Update ws from @1.3.0 to @2.5.11 NPM version: 10.5.0 Installing iobroker.ws@2.5.11... (System call) added 2 packages, removed 3 packages, and changed 1 package in 9s 134 packages are looking for funding run `npm fund` for details upload [11] ws.admin /opt/iobroker/node_modules/iobroker.ws/admin/i18n/de/translations.json i18n/de/translations.json application/json upload [10] ws.admin /opt/iobroker/node_modules/iobroker.ws/admin/i18n/en/translations.json i18n/en/translations.json application/json upload [9] ws.admin /opt/iobroker/node_modules/iobroker.ws/admin/i18n/es/translations.json i18n/es/translations.json application/json upload [8] ws.admin /opt/iobroker/node_modules/iobroker.ws/admin/i18n/fr/translations.json i18n/fr/translations.json application/json upload [7] ws.admin /opt/iobroker/node_modules/iobroker.ws/admin/i18n/it/translations.json i18n/it/translations.json application/json upload [6] ws.admin /opt/iobroker/node_modules/iobroker.ws/admin/i18n/nl/translations.json i18n/nl/translations.json application/json upload [5] ws.admin /opt/iobroker/node_modules/iobroker.ws/admin/i18n/pl/translations.json i18n/pl/translations.json application/json upload [4] ws.admin /opt/iobroker/node_modules/iobroker.ws/admin/i18n/pt/translations.json i18n/pt/translations.json application/json upload [3] ws.admin /opt/iobroker/node_modules/iobroker.ws/admin/i18n/ru/translations.json i18n/ru/translations.json application/json upload [2] ws.admin /opt/iobroker/node_modules/iobroker.ws/admin/i18n/zh-cn/translations.json i18n/zh-cn/translations.json application/json upload [1] ws.admin /opt/iobroker/node_modules/iobroker.ws/admin/jsonConfig.json jsonConfig.json application/json upload [0] ws.admin /opt/iobroker/node_modules/iobroker.ws/admin/ws.png ws.png image/png This upgrade of "web" will at least introduce the following changes: ========================================================================== -> 6.2.3: update websocket library to increase maximum file size from 100 MB to 500 MB -> 6.2.2: Corrected the crash if authentication is enabled -> 6.2.1: Added the user access list option -> 6.1.10: Corrected the start screen -> 6.1.7: Added the public accessibility check -> 6.1.6: Corrected adapter termination if the alias has no target Corrected socket.io connection -> 6.1.4: upgrade socketio and ws dependencies to fix vis subscribe problem ========================================================================== BE CAREFUL: THIS IS A MAJOR UPGRADE, WHICH WILL MOST LIKELY INTRODUCE BREAKING CHANGES! Would you like to upgrade web from @4.3.0 to @6.2.3 now? [(y)es, (n)o]: ^Y No upgrade of "web" desired. This upgrade of "tankerkoenig" will at least introduce the following changes: ========================================================================== -> 3.3.7: added difference to jsonTable #116 added a log message for the error `parameter error` set the name length to 34 characters Added verification if the api key is encrypted updated the Dependencies -> 3.3.6: corrected the position of the warning message in the user interface Updated documentation and migration guide for stable version 3.3.6 -> 3.3.5: fixed copy/paste bug in the UI -> 3.3.4: Fixed an issue where a zip code starting with 0 was displayed incorrectly [Issue #113]. -> 3.3.3: fixed => adapter does not fetch data after a `requestData error` e.g. internet crash. added adapter migration guide from 3.1.x to 3.3.x or 3.2.x to 3.3.x Problem fixed [Problem #111] -> 3.3.2: Fixed TypeError: Cannot read property 'length' of undefined in addDiscount if value is `boolean / undefined`. Fixed error: DB closed when adapter is stopped Object creation optimized changed query interval default value to 10 minutes and minimum value to 10 minutes added check if station ID is already configured (in edit mode) Added price difference to last price added feature request cheapest station display [Issue #109] -> 3.3.1: Fixed TypeError: Cannot read properties of undefined Issue #104 added complete street datapoint for each station ========================================================================== BE CAREFUL: THIS IS A MAJOR UPGRADE, WHICH WILL MOST LIKELY INTRODUCE BREAKING CHANGES! Would you like to upgrade tankerkoenig from @2.1.1 to @3.3.7 now? [(y)es, (n)o]: Y Update tankerkoenig from @2.1.1 to @3.3.7 host.raspberrypi-4-2 Adapter "system.adapter.tankerkoenig.0" is stopped. NPM version: 10.5.0 Installing iobroker.tankerkoenig@3.3.7... (System call) removed 1 package, and changed 1 package in 8s 134 packages are looking for funding run `npm fund` for details Update "system.adapter.tankerkoenig.0" upload [4] tankerkoenig.admin /opt/iobroker/node_modules/iobroker.tankerkoenig/admin/build/index.js build/index.js application/javascript upload [3] tankerkoenig.admin /opt/iobroker/node_modules/iobroker.tankerkoenig/admin/build/index.js.map build/index.js.map application/json upload [2] tankerkoenig.admin /opt/iobroker/node_modules/iobroker.tankerkoenig/admin/index_m.html index_m.html text/html upload [1] tankerkoenig.admin /opt/iobroker/node_modules/iobroker.tankerkoenig/admin/style.css style.css text/css upload [0] tankerkoenig.admin /opt/iobroker/node_modules/iobroker.tankerkoenig/admin/tankerkoenig.png tankerkoenig.png image/png host.raspberrypi-4-2 Adapter "system.adapter.tankerkoenig.0" is started This upgrade of "socketio" will at least introduce the following changes: ========================================================================== -> 6.6.1: Just some packages were updated -> 6.6.0: Corrected adapter termination if the alias has no target -> 6.5.7: upgrade socket-classes to fix error with vis subscriptions -> 6.5.6: upgraded socket-classes to correct the error by unsubscribing on client disconnect -> 6.5.5: upgrade socket-classes to fix crash cases -> 6.5.4: upgrade socket-classes to fix crash cases -> 6.5.3: added missing node16 requirement ========================================================================== BE CAREFUL: THIS IS A MAJOR UPGRADE, WHICH WILL MOST LIKELY INTRODUCE BREAKING CHANGES! Would you like to upgrade socketio from @4.2.0 to @6.6.1 now? [(y)es, (n)o]: Y Update socketio from @4.2.0 to @6.6.1 ,NPM version: 10.5.0 Installing iobroker.socketio@6.6.1... (System call) added 25 packages, removed 3 packages, and changed 1 package in 10s 134 packages are looking for funding run `npm fund` for details upload [11] socketio.admin /opt/iobroker/node_modules/iobroker.socketio/admin/i18n/de/translations.json i18n/de/translations.json application/json upload [10] socketio.admin /opt/iobroker/node_modules/iobroker.socketio/admin/i18n/en/translations.json i18n/en/translations.json application/json upload [9] socketio.admin /opt/iobroker/node_modules/iobroker.socketio/admin/i18n/es/translations.json i18n/es/translations.json application/json upload [8] socketio.admin /opt/iobroker/node_modules/iobroker.socketio/admin/i18n/fr/translations.json i18n/fr/translations.json application/json upload [7] socketio.admin /opt/iobroker/node_modules/iobroker.socketio/admin/i18n/it/translations.json i18n/it/translations.json application/json upload [6] socketio.admin /opt/iobroker/node_modules/iobroker.socketio/admin/i18n/nl/translations.json i18n/nl/translations.json application/json upload [5] socketio.admin /opt/iobroker/node_modules/iobroker.socketio/admin/i18n/pl/translations.json i18n/pl/translations.json application/json upload [4] socketio.admin /opt/iobroker/node_modules/iobroker.socketio/admin/i18n/pt/translations.json i18n/pt/translations.json application/json upload [3] socketio.admin /opt/iobroker/node_modules/iobroker.socketio/admin/i18n/ru/translations.json i18n/ru/translations.json application/json upload [2] socketio.admin /opt/iobroker/node_modules/iobroker.socketio/admin/i18n/zh-cn/translations.json i18n/zh-cn/translations.json application/json upload [1] socketio.admin /opt/iobroker/node_modules/iobroker.socketio/admin/jsonConfig.json jsonConfig.json application/json upload [0] socketio.admin /opt/iobroker/node_modules/iobroker.socketio/admin/socketio.png socketio.png image/png This upgrade of "shelly" will introduce the following changes: ========================================================================== -> 6.8.0: Updated BLE script to 0.2 (new shelly motion firmware) Updated Shelly i3 number limits Added screenshots to instance configuration -> 6.7.0: Updated handling of ble payloads Added Shelly Wall Display ========================================================================== Would you like to upgrade shelly from @6.6.1 to @6.8.0 now? [(y)es, (n)o]: Y Would you like to upgrade shelly from @6.6.1 to @6.8.0 now? [(y)es, (n)o]: Y Update shelly from @6.6.1 to @6.8.0 NPM version: 10.5.0 Installing iobroker.shelly@6.8.0... (System call) changed 1 package in 8s 134 packages are looking for funding run `npm fund` for details Update "system.adapter.shelly.0" Update "system.adapter.shelly.1" upload [17] shelly.admin /opt/iobroker/node_modules/iobroker.shelly/admin/i18n/de/translations.json i18n/de/translations.json application/json upload [16] shelly.admin /opt/iobroker/node_modules/iobroker.shelly/admin/i18n/en/translations.json i18n/en/translations.json application/json upload [15] shelly.admin /opt/iobroker/node_modules/iobroker.shelly/admin/i18n/es/translations.json i18n/es/translations.json application/json upload [14] shelly.admin /opt/iobroker/node_modules/iobroker.shelly/admin/i18n/fr/translations.json i18n/fr/translations.json application/json upload [13] shelly.admin /opt/iobroker/node_modules/iobroker.shelly/admin/i18n/it/translations.json i18n/it/translations.json application/json upload [12] shelly.admin /opt/iobroker/node_modules/iobroker.shelly/admin/i18n/nl/translations.json i18n/nl/translations.json application/json upload [11] shelly.admin /opt/iobroker/node_modules/iobroker.shelly/admin/i18n/pl/translations.json i18n/pl/translations.json application/json upload [10] shelly.admin /opt/iobroker/node_modules/iobroker.shelly/admin/i18n/pt/translations.json i18n/pt/translations.json application/json upload [9] shelly.admin /opt/iobroker/node_modules/iobroker.shelly/admin/i18n/ru/translations.json i18n/ru/translations.json application/json upload [8] shelly.admin /opt/iobroker/node_modules/iobroker.shelly/admin/i18n/uk/translations.json i18n/uk/translations.json application/json upload [7] shelly.admin /opt/iobroker/node_modules/iobroker.shelly/admin/i18n/zh-cn/translations.json i18n/zh-cn/translations.json application/json upload [6] shelly.admin /opt/iobroker/node_modules/iobroker.shelly/admin/img/mqttGen1.png img/mqttGen1.png image/png upload [5] shelly.admin /opt/iobroker/node_modules/iobroker.shelly/admin/img/mqttGen2.png img/mqttGen2.png image/png upload [4] shelly.admin /opt/iobroker/node_modules/iobroker.shelly/admin/img/restrictedLoginGen1.png img/restrictedLoginGen1.png image/png upload [3] shelly.admin /opt/iobroker/node_modules/iobroker.shelly/admin/img/restrictedLoginGen2.png img/restrictedLoginGen2.png image/png upload [2] shelly.admin /opt/iobroker/node_modules/iobroker.shelly/admin/jsonConfig.json jsonConfig.json application/json upload [1] shelly.admin /opt/iobroker/node_modules/iobroker.shelly/admin/shelly.png shelly.png image/png upload [0] shelly.admin /opt/iobroker/node_modules/iobroker.shelly/admin/words.js words.js application/javascript This upgrade of "node-red" will introduce the following changes: ========================================================================== -> 5.2.0: Added persistence of context data (filesystem) ========================================================================== Would you like to upgrade node-red from @5.1.0 to @5.2.0 now? [(y)es, (n)o]: Y Update node-red from @5.1.0 to @5.2.0 host.raspberrypi-4-2 Adapter "system.adapter.node-red.0" is stopped. NPM version: 10.5.0 Installing iobroker.node-red@5.2.0... (System call) changed 1 package in 8s 134 packages are looking for funding run `npm fund` for details Update "system.adapter.node-red.0" upload [13] node-red.admin /opt/iobroker/node_modules/iobroker.node-red/admin/i18n/de/translations.json i18n/de/translations.json application/json upload [12] node-red.admin /opt/iobroker/node_modules/iobroker.node-red/admin/i18n/en/translations.json i18n/en/translations.json application/json upload [11] node-red.admin /opt/iobroker/node_modules/iobroker.node-red/admin/i18n/es/translations.json i18n/es/translations.json application/json upload [10] node-red.admin /opt/iobroker/node_modules/iobroker.node-red/admin/i18n/fr/translations.json i18n/fr/translations.json application/json upload [9] node-red.admin /opt/iobroker/node_modules/iobroker.node-red/admin/i18n/it/translations.json i18n/it/translations.json application/json upload [8] node-red.admin /opt/iobroker/node_modules/iobroker.node-red/admin/i18n/nl/translations.json i18n/nl/translations.json application/json upload [7] node-red.admin /opt/iobroker/node_modules/iobroker.node-red/admin/i18n/pl/translations.json i18n/pl/translations.json application/json upload [6] node-red.admin /opt/iobroker/node_modules/iobroker.node-red/admin/i18n/pt/translations.json i18n/pt/translations.json application/json upload [5] node-red.admin /opt/iobroker/node_modules/iobroker.node-red/admin/i18n/ru/translations.json i18n/ru/translations.json application/json upload [4] node-red.admin /opt/iobroker/node_modules/iobroker.node-red/admin/i18n/uk/translations.json i18n/uk/translations.json application/json upload [3] node-red.admin /opt/iobroker/node_modules/iobroker.node-red/admin/i18n/zh-cn/translations.json i18n/zh-cn/translations.json application/json upload [2] node-red.admin /opt/iobroker/node_modules/iobroker.node-red/admin/jsonConfig.json jsonConfig.json application/json upload [1] node-red.admin /opt/iobroker/node_modules/iobroker.node-red/admin/node-red.png node-red.png image/png upload [0] node-red.admin /opt/iobroker/node_modules/iobroker.node-red/admin/words.js words.js application/javascript host.raspberrypi-4-2 Adapter "system.adapter.node-red.0" is started This upgrade of "ems-esp" will at least introduce the following changes: ========================================================================== -> 3.0.3: improve km200 data read to avoid errors -> 3.0.2: improve km200 data read to avoid errors - try http get up to 3 times now - especially for recordings -> 3.0.1: change KM200 error messages for recordings -> 3.0.0: Node >= 18 required update heatdemand weight changes to be effective during active instance ems-esp gateway: Raw telegram search for EMS+ thermostats: switchPrograms and holidayModes (RC310/RC300) create writable objects / states for switchPrograms and holidayModes this function is only active when no km200 gateway is selected - ems-esp gateway only improve error messages for km200 (wrong ip / passwords) small changes within PDF adapter documentation -> 3.0.0-alpha.2: Node >= 18 required update heatdemand weight changes to be effective during active instance -> 3.0.0-alpha.1: ems-esp gateway: Raw telegram search for EMS+ thermostats: switchPrograms and holidayModes (RC310/RC300) create writable objects / states for switchPrograms and holidayModes this function is only active when no km200 gateway is selected - ems-esp gateway only improve error messages for km200 (wrong ip / passwords) small changes within PDF adapter documentation -> 3.0.0-alpha.0: Search for ems-esp states for EMS+ thermostats: switchTimes and holidayModes (RC310/RC300) Implement raw telegram search for EMS+ entities and create writable objects / states The search is only active when no km200 gateway is selected ========================================================================== BE CAREFUL: THIS IS A MAJOR UPGRADE, WHICH WILL MOST LIKELY INTRODUCE BREAKING CHANGES! Would you like to upgrade ems-esp from @2.8.0 to @3.0.3 now? [(y)es, (n)o]: Y Update ems-esp from @2.8.0 to @3.0.3 NPM version: 10.5.0 Installing iobroker.ems-esp@3.0.3... (System call) changed 1 package in 8s 134 packages are looking for funding run `npm fund` for details Update "system.adapter.ems-esp.0" upload [6] ems-esp.admin /opt/iobroker/node_modules/iobroker.ems-esp/admin/admin.d.ts admin.d.ts video/mp2t upload [5] ems-esp.admin /opt/iobroker/node_modules/iobroker.ems-esp/admin/ems-esp.png ems-esp.png image/png upload [4] ems-esp.admin /opt/iobroker/node_modules/iobroker.ems-esp/admin/index_m.html index_m.html text/html upload [3] ems-esp.admin /opt/iobroker/node_modules/iobroker.ems-esp/admin/index_m.js index_m.js application/javascript upload [2] ems-esp.admin /opt/iobroker/node_modules/iobroker.ems-esp/admin/km200.png km200.png image/png upload [1] ems-esp.admin /opt/iobroker/node_modules/iobroker.ems-esp/admin/style.css style.css text/css upload [0] ems-esp.admin /opt/iobroker/node_modules/iobroker.ems-esp/admin/words.js words.js application/javascript This upgrade of "discovery" will at least introduce the following changes: ========================================================================== -> 4.4.0: Added WLED Added LaMetric Removed net-tools from proposals -> 4.3.0: Replaced vis with vis-2 -> 4.2.0: Changed detection of myvbus and resol -> 4.1.0: Added detection of myvbus and resol -> 4.0.0: Added: frontier_silicon, sma-em, and speedwire Dropped node14 support, refactoring -> 3.2.0: Added iControl to the suggested adapters -> 3.1.0: Corrected syntax error in the german translation ========================================================================== BE CAREFUL: THIS IS A MAJOR UPGRADE, WHICH WILL MOST LIKELY INTRODUCE BREAKING CHANGES! Would you like to upgrade discovery from @3.0.3 to @4.4.0 now? [(y)es, (n)o]: Y Update discovery from @3.0.3 to @4.4.0 NPM version: 10.5.0 Installing iobroker.discovery@4.4.0... (System call) added 1 package, removed 16 packages, and changed 1 package in 8s 122 packages are looking for funding run `npm fund` for details Update "system.adapter.discovery.0" upload [6] discovery.admin /opt/iobroker/node_modules/iobroker.discovery/admin/discovery.png discovery.png image/png upload [5] discovery.admin /opt/iobroker/node_modules/iobroker.discovery/admin/index.html index.html text/html upload [4] discovery.admin /opt/iobroker/node_modules/iobroker.discovery/admin/index_m.html index_m.html text/html upload [3] discovery.admin /opt/iobroker/node_modules/iobroker.discovery/admin/settings.html settings.html text/html upload [2] discovery.admin /opt/iobroker/node_modules/iobroker.discovery/admin/settings_m.html settings_m.html text/html upload [1] discovery.admin /opt/iobroker/node_modules/iobroker.discovery/admin/translateTools.js translateTools.js application/javascript upload [0] discovery.admin /opt/iobroker/node_modules/iobroker.discovery/admin/words.js words.js application/javascript -
Wo ist denn der mihome-vacuum nun hin?
-
Der mihome-vacuum Adapter ist jetzt auch drin.
Habe jetzt mein Backup eingespielt den Adapter als Beta installiert und nun scheint alles zu funktionieren.Danke für die Hilfe und geduld
Used repository: stable Adapter "admin" : 6.13.16 , installed 6.13.16 Adapter "backitup" : 2.10.11 , installed 2.10.11 Adapter "daikin" : 1.4.2 , installed 1.4.2 Adapter "discovery" : 4.4.0 , installed 4.4.0 Adapter "ems-esp" : 3.0.3 , installed 3.0.3 Adapter "hm-rega" : 4.0.0 , installed 4.0.0 Adapter "hm-rpc" : 1.16.0 , installed 1.16.0 Adapter "influxdb" : 4.0.2 , installed 4.0.2 Adapter "javascript" : 7.8.0 , installed 7.8.0 Controller "js-controller": 5.0.19 , installed 5.0.19 Adapter "mihome-vacuum": 4.1.1 , installed 4.2.0 Adapter "modbus" : 6.1.0 , installed 6.1.0 Adapter "node-red" : 5.2.0 , installed 5.2.0 Adapter "pushover" : 3.0.6 , installed 3.0.6 Adapter "rpi2" : 1.3.2 , installed 1.3.2 Adapter "shelly" : 6.8.0 , installed 6.8.0 Adapter "simple-api" : 2.7.2 , installed 2.7.2 Adapter "smartmeter" : 3.4.0 , installed 3.4.0 Adapter "socketio" : 6.6.1 , installed 6.6.1 Adapter "tado" : 0.5.3 , installed 0.5.3 Adapter "tankerkoenig" : 3.3.7 , installed 3.3.7 Adapter "tuya" : 3.15.0 , installed 3.15.0 Adapter "web" : 6.2.3 , installed 4.3.0 [Updatable] Adapter "ws" : 2.5.11 , installed 2.5.11 Adapter "zigbee" : 1.10.1 , installed 1.10.1 -
@redbeard_81 sagte in npm Error bei mihome-vacuum Adapter Installation:
Adapter "web" : 6.2.3 , installed 4.3.0 [Updatable]
Heb das auch hoch.
-
@redbeard_81 ja, das gleiche Problem hatte ich Anfang dieser Woche auch.
Schön zu sehen, dass dir erstens schnell geholfen wurde, zweitens ich nicht allein betroffen bin. -
Ich habe gerade das Update auf die 4.2.0 und habe das Problem, dass die Installation offenbar sauber durchläuft, der Adapter aber nicht mehr startet ("Verbunden mit Gerät oder Dienst" ist grün, der Rest rot)
iob update und iob upgrade hab ich probiert, keine Resultate:
C:\ioBroker>iob update Used repository: stable Adapter "admin" : 6.13.16 , installed 6.13.16 Adapter "backitup" : 2.11.0 , installed 2.11.0 Adapter "bring" : 1.8.4 , installed 1.8.4 Adapter "daswetter" : 3.1.13 , installed 3.1.13 Adapter "deconz" : 1.4.0 , installed 1.4.0 Adapter "discovery" : 4.4.0 , installed 4.4.0 Adapter "echarts" : 1.7.2 , installed 1.7.2 Adapter "email" : 1.2.2 , installed 1.2.2 Adapter "fb-checkpresence": 1.2.4 , installed 1.2.4 Adapter "history" : 3.0.1 , installed 3.0.1 Adapter "homeconnect" : 1.3.0 , installed 1.3.0 Adapter "ical" : 1.14.3 , installed 1.14.3 Adapter "icons-icons8" : 0.0.1 , installed 0.0.1 Adapter "javascript" : 7.8.0 , installed 7.8.0 Controller "js-controller": 5.0.19 , installed 5.0.19 Adapter "mihome-vacuum": 4.2.0 , installed 4.2.0 Adapter "nina" : 0.0.25 , installed 0.0.25 Adapter "rssfeed" : 2.6.1 , installed 2.6.1 Adapter "sayit" : 3.0.5 , installed 3.0.5 Adapter "simple-api" : 2.7.2 , installed 2.7.2 Adapter "socketio" : 6.6.1 , installed 6.6.1 Adapter "tr-064" : 4.2.18 , installed 4.2.18 Adapter "trashschedule": 3.2.0 , installed 3.2.0 Adapter "vis" : 1.5.4 , installed 1.5.1 [Updatable] Adapter "vis-inventwo" : 3.3.3 , installed 3.3.3 Adapter "vis-players" : 0.1.6 , installed 0.1.6 Adapter "vis-timeandweather": 1.2.2, installed 1.2.2 Adapter "weatherunderground": 3.6.0, installed 3.6.0 Adapter "web" : 6.2.5 , installed 6.2.5 Adapter "whatsapp-cmb" : 0.2.3 , installed 0.2.3 Adapter "ws" : 2.5.11 , installed 2.5.11C:\ioBroker>iob upgrade This upgrade of "vis" will introduce the following changes: ========================================================================== -> 1.5.4: added the new binding operation for getting property of JSON or object Checked the initialization of the `local_` variables fixed subscribeOidAtRuntime Added dynamic web manifest Optimization for basic-view in widget8 Changed binding regex to accept umlauts Corrected first installation of vis ========================================================================== Would you like to upgrade vis from @1.5.1 to @1.5.4 now? [(y)es, (n)o]: n No upgrade of "vis" desired.Vis habe ich aus Gründen nicht aktualisiert, weil ansonsten einige ältere Tablets nicht mehr klarkommen.
Ein "Iob fix" bringt:
Need to install the following packages: @iobroker/fix@5.0.0 Ok to proceed? (y) y "(" kann syntaktisch an dieser Stelle nicht verarbeitet werden. npm notice npm notice New major version of npm available! 9.5.0 -> 10.5.2 npm notice Changelog: https://github.com/npm/cli/releases/tag/v10.5.2 npm notice Run npm install -g npm@10.5.2 to update! npm noticeHat das Eine mit dem Anderen zu tun?
-
@wintermute sagte in npm Error bei mihome-vacuum Adapter Installation:
Ich habe gerade das Update auf die 4.2.0 und habe das Problem, dass die Installation offenbar sauber durchläuft, der Adapter aber nicht mehr startet ("Verbunden mit Gerät oder Dienst" ist grün, der Rest rot)
iob update und iob upgrade hab ich probiert, keine Resultate:
C:\ioBroker>iob update Used repository: stable Adapter "admin" : 6.13.16 , installed 6.13.16 Adapter "backitup" : 2.11.0 , installed 2.11.0 Adapter "bring" : 1.8.4 , installed 1.8.4 Adapter "daswetter" : 3.1.13 , installed 3.1.13 Adapter "deconz" : 1.4.0 , installed 1.4.0 Adapter "discovery" : 4.4.0 , installed 4.4.0 Adapter "echarts" : 1.7.2 , installed 1.7.2 Adapter "email" : 1.2.2 , installed 1.2.2 Adapter "fb-checkpresence": 1.2.4 , installed 1.2.4 Adapter "history" : 3.0.1 , installed 3.0.1 Adapter "homeconnect" : 1.3.0 , installed 1.3.0 Adapter "ical" : 1.14.3 , installed 1.14.3 Adapter "icons-icons8" : 0.0.1 , installed 0.0.1 Adapter "javascript" : 7.8.0 , installed 7.8.0 Controller "js-controller": 5.0.19 , installed 5.0.19 Adapter "mihome-vacuum": 4.2.0 , installed 4.2.0 Adapter "nina" : 0.0.25 , installed 0.0.25 Adapter "rssfeed" : 2.6.1 , installed 2.6.1 Adapter "sayit" : 3.0.5 , installed 3.0.5 Adapter "simple-api" : 2.7.2 , installed 2.7.2 Adapter "socketio" : 6.6.1 , installed 6.6.1 Adapter "tr-064" : 4.2.18 , installed 4.2.18 Adapter "trashschedule": 3.2.0 , installed 3.2.0 Adapter "vis" : 1.5.4 , installed 1.5.1 [Updatable] Adapter "vis-inventwo" : 3.3.3 , installed 3.3.3 Adapter "vis-players" : 0.1.6 , installed 0.1.6 Adapter "vis-timeandweather": 1.2.2, installed 1.2.2 Adapter "weatherunderground": 3.6.0, installed 3.6.0 Adapter "web" : 6.2.5 , installed 6.2.5 Adapter "whatsapp-cmb" : 0.2.3 , installed 0.2.3 Adapter "ws" : 2.5.11 , installed 2.5.11C:\ioBroker>iob upgrade This upgrade of "vis" will introduce the following changes: ========================================================================== -> 1.5.4: added the new binding operation for getting property of JSON or object Checked the initialization of the `local_` variables fixed subscribeOidAtRuntime Added dynamic web manifest Optimization for basic-view in widget8 Changed binding regex to accept umlauts Corrected first installation of vis ========================================================================== Would you like to upgrade vis from @1.5.1 to @1.5.4 now? [(y)es, (n)o]: n No upgrade of "vis" desired.Vis habe ich aus Gründen nicht aktualisiert, weil ansonsten einige ältere Tablets nicht mehr klarkommen.
Ein "Iob fix" bringt:
Need to install the following packages: @iobroker/fix@5.0.0 Ok to proceed? (y) y "(" kann syntaktisch an dieser Stelle nicht verarbeitet werden. npm notice npm notice New major version of npm available! 9.5.0 -> 10.5.2 npm notice Changelog: https://github.com/npm/cli/releases/tag/v10.5.2 npm notice Run npm install -g npm@10.5.2 to update! npm noticeHat das Eine mit dem Anderen zu tun?
Zusätzlich noch "iob info":
C:\ioBroker>iob info Cannot get disk information: Command failed: df -k / Der Befehl "df" ist entweder falsch geschrieben oder konnte nicht gefunden werden. Platform : Windows os : win64 Architecture : x64 CPUs : 2 Model : Intel(R) Xeon(R) CPU 8460Y+ @ 2.0 GHz RAM : 126 GB System uptime : 2d. 20:25:52 Node.js : v18.15.0 time : 1713536349613 timeOffset : -120 NPM : 9.5.0 adapters count : 538 -
ich habe das gleiche Problem seit dem Update auf die neue Version
host.iobroker 2024-04-19 16:31:31.427 error instance system.adapter.mihome-vacuum.0 terminated with code 1 (JS_CONTROLLER_STOPPED) host.iobroker 2024-04-19 16:31:31.426 error Caught by controller[1]: Node.js v20.12.2 host.iobroker 2024-04-19 16:31:31.426 error Caught by controller[0]: } host.iobroker 2024-04-19 16:31:31.425 error Caught by controller[0]: code: 'ERR_INVALID_ARG_VALUE' host.iobroker 2024-04-19 16:31:31.425 error Caught by controller[0]: at Module._compile (node:internal/modules/cjs/loader:1369:14) { host.iobroker 2024-04-19 16:31:31.425 error Caught by controller[0]: at Object.<anonymous> (/opt/iobroker/node_modules/iobroker.mihome-vacuum/node_modules/@iobroker/adapter-core/build/cjs/controllerTools.js:34:22) host.iobroker 2024-04-19 16:31:31.424 error Caught by controller[0]: at require (node:internal/modules/helpers:179:18) host.iobroker 2024-04-19 16:31:31.424 error Caught by controller[0]: at Module.require (node:internal/modules/cjs/loader:1231:19) host.iobroker 2024-04-19 16:31:31.424 error Caught by controller[0]: at Module._load (node:internal/modules/cjs/loader:1022:12) host.iobroker 2024-04-19 16:31:31.424 error Caught by controller[0]: at Module.load (node:internal/modules/cjs/loader:1206:32) host.iobroker 2024-04-19 16:31:31.423 error Caught by controller[0]: at Module._extensions..js (node:internal/modules/cjs/loader:1427:10) host.iobroker 2024-04-19 16:31:31.423 error Caught by controller[0]: at Module._compile (node:internal/modules/cjs/loader:1369:14) host.iobroker 2024-04-19 16:31:31.418 error Caught by controller[0]: at Object.<anonymous> (/opt/iobroker/node_modules/iobroker.mihome-vacuum/node_modules/@iobroker/adapter-core/build/cjs/helpers.js:36:53) host.iobroker 2024-04-19 16:31:31.418 error Caught by controller[0]: at createRequire (node:internal/modules/cjs/loader:1506:13) host.iobroker 2024-04-19 16:31:31.418 error Caught by controller[0]: TypeError [ERR_INVALID_ARG_VALUE]: The argument 'filename' must be a file URL object, file URL string, or absolute path string. Received 'file:// /opt/iobroker/node_modules/iobroker.mihome-vacuum/node_modules/@iobroker/adapter-core/build/cjs/helpers.js' host.iobroker 2024-04-19 16:31:31.417 error Caught by controller[0]: ^ host.iobroker 2024-04-19 16:31:31.417 error Caught by controller[0]: throw new ERR_INVALID_ARG_VALUE('filename', filename, host.iobroker 2024-04-19 16:31:31.416 error Caught by controller[0]: node:internal/modules/cjs/loader:1506Hat jemand eine Idee wo man schauen muss um das zu korrigieren ?
Danke! -
bei Windows bin ich raus..
-
ist nicht der gleiche Fehler, wie der TE hat, aber irgendein script scheint filename falsch deklariert zu haben.. sofern ich den Fehler richtig verstehe.. ist ja nur n Auschschnitt vom Ende des Fehlers.. man muesste da halt mal wissen:
welches System?
welche Version?
Logfile von Begin an, wenn der Adapter startet...Dann natuerlich noch die Grundsaetzlichen infos aus iob diag.
-
@ilovegym
Danke für Deine Rückmeldung!======================= SUMMARY ======================= v.2023-10-10 model name : Intel(R) Celeron(R) CPU J3455 @ 1.50GHz Kernel : x86_64 Userland : amd64 Docker : v9.1.2 Installation: Docker Kernel: x86_64 Userland: amd64 Timezone: Etc/UTC User-ID: 0 X-Server: false Pending OS-Updates: 0 Pending iob updates: 0 Nodejs-Installation: /usr/bin/nodejs v20.12.2 /usr/bin/node v20.12.2 /usr/bin/npm 10.5.0 /usr/bin/npx 10.5.0 /usr/bin/corepack 0.25.2 Recommended versions are nodejs 18.20.2 and npm 10.5.0 Your nodejs installation is correct MEMORY: total used free shared buff/cache available Mem: 12G 6.7G 822M 188M 5.4G 5.7G Swap: 9.6G 60M 9.5G Total: 21G 6.8G 10G Active iob-Instances: 26 Active repo(s): stable ioBroker Core: js-controller 5.0.19 admin 6.13.16 ioBroker Status: iobroker is running on this host. Objects type: jsonl States type: redis Status admin and web instance: + system.adapter.admin.0 : admin : iobroker - enabled, port: 8081, bind: 0.0.0.0 (SSL), run as: admin + system.adapter.web.0 : web : iobroker - enabled, port: 8082, bind: 0.0.0.0, run as: admin Objects: 15173 States: 11749 Size of iob-Database: 16M /opt/iobroker/iobroker-data/objects.jsonl 13M /opt/iobroker/iobroker-data/objects.json.migrated 13M /opt/iobroker/iobroker-data/objects.json.bak.migrated 3.5M /opt/iobroker/iobroker-data/states.json.bak 3.5M /opt/iobroker/iobroker-data/states.json =================== END OF SUMMARY ====================Adapter Log:
host.iobroker 2024-04-19 17:08:23.959 info Restart adapter system.adapter.mihome-vacuum.0 because enabled host.iobroker 2024-04-19 17:08:23.959 error instance system.adapter.mihome-vacuum.0 terminated with code 1 (JS_CONTROLLER_STOPPED) host.iobroker 2024-04-19 17:08:23.959 error Caught by controller[0]: Node.js v20.12.2 host.iobroker 2024-04-19 17:08:23.959 error Caught by controller[0]: } host.iobroker 2024-04-19 17:08:23.958 error Caught by controller[0]: code: 'ERR_INVALID_ARG_VALUE' host.iobroker 2024-04-19 17:08:23.958 error Caught by controller[0]: at Module._compile (node:internal/modules/cjs/loader:1369:14) { host.iobroker 2024-04-19 17:08:23.958 error Caught by controller[0]: at Object.<anonymous> (/opt/iobroker/node_modules/iobroker.mihome-vacuum/node_modules/@iobroker/adapter-core/build/cjs/controllerTools.js:34:22) host.iobroker 2024-04-19 17:08:23.958 error Caught by controller[0]: at require (node:internal/modules/helpers:179:18) host.iobroker 2024-04-19 17:08:23.958 error Caught by controller[0]: at Module.require (node:internal/modules/cjs/loader:1231:19) host.iobroker 2024-04-19 17:08:23.957 error Caught by controller[0]: at Module._load (node:internal/modules/cjs/loader:1022:12) host.iobroker 2024-04-19 17:08:23.957 error Caught by controller[0]: at Module.load (node:internal/modules/cjs/loader:1206:32) host.iobroker 2024-04-19 17:08:23.957 error Caught by controller[0]: at Module._extensions..js (node:internal/modules/cjs/loader:1427:10) host.iobroker 2024-04-19 17:08:23.957 error Caught by controller[0]: at Module._compile (node:internal/modules/cjs/loader:1369:14) host.iobroker 2024-04-19 17:08:23.956 error Caught by controller[0]: at Object.<anonymous> (/opt/iobroker/node_modules/iobroker.mihome-vacuum/node_modules/@iobroker/adapter-core/build/cjs/helpers.js:36:53) host.iobroker 2024-04-19 17:08:23.956 error Caught by controller[0]: at createRequire (node:internal/modules/cjs/loader:1506:13) host.iobroker 2024-04-19 17:08:23.956 error Caught by controller[0]: TypeError [ERR_INVALID_ARG_VALUE]: The argument 'filename' must be a file URL object, file URL string, or absolute path string. Received 'file:// /opt/iobroker/node_modules/iobroker.mihome-vacuum/node_modules/@iobroker/adapter-core/build/cjs/helpers.js' host.iobroker 2024-04-19 17:08:23.956 error Caught by controller[0]: ^ host.iobroker 2024-04-19 17:08:23.955 error Caught by controller[0]: throw new ERR_INVALID_ARG_VALUE('filename', filename, host.iobroker 2024-04-19 17:08:23.954 error Caught by controller[0]: node:internal/modules/cjs/loader:1506 host.iobroker 2024-04-19 17:08:23.723 info instance system.adapter.mihome-vacuum.0 started with pid 5691Mehr log habe ich bzw. wo kann ich mehr log des Adapters finden ?
-
mach mal in der Konsole des iobroker dockers ein "iob upload mihome-vacuum" und starte dann den Adapter nochmal.
In die Konsole des Dockers kommst du im Terminal des Hosts (Synology? Proxmox? ) mit dem command
sudo docker exec -tiu username containername /bin/bashbei mir ist das als user iobroker und der container heisst auch iobroker dann ein
sudo docker exec -tiu iobroker iobroker /bin/bashdanach bist du in /opt/iobroker und kannst als user iobroker die iob commands ausfuehren, ausser diejenigen, die ein iob maintenance brauchen..
Ich gehe davon aus, dass du das buanet-docker-Image benutzt?edit:
das Logfile bekommt man am schoensten, finde ich, in der Konsole mit dem command
iob logs --watch -
@ilovegym said in npm Error bei mihome-vacuum Adapter Installation:
iob upload mihome-vacuum
Das hatte ich schon gemacht, leider auch ohne Erfolg. Ich konnte es mit
npm install iobroker/adapter-corekorrigieren, danach lässt sich der Adapter wieder starten!
Schönes Wochenende! -
@ilovegym ...und ich bei Linux
Alle Reparaturversuche sind fehlgeschlagen - Einspielen des Updates von letzter Nacht hat meinem Iobroker und meinem Staubsauger aber wieder auf die Beine geholfen. Das Update auf die 4.2.0 werde ich dann mal besser auslassen...
-
Adapter "mihome-vacuum": 4.2.0 , installed 4.2.0Läuft.
-
@thomas-braun sagte in npm Error bei mihome-vacuum Adapter Installation:
Adapter "mihome-vacuum": 4.2.0 , installed 4.2.0Läuft.
Auf einem Windows-System? Hast Du irgendwelche Verrenkungen gemacht, damit der Adapter läuft?
-
Läuft natürlich auf einem Betriebssystem.
Gerade nochmal durchgestartet:2024-04-19 18:46:09.700 - info: mihome-vacuum.0 (1232) Got terminate signal TERMINATE_YOURSELF 2024-04-19 18:46:09.727 - error: mihome-vacuum.0 (1232) Socket Close 2024-04-19 18:46:09.731 - info: mihome-vacuum.0 (1232) terminating 2024-04-19 18:46:09.734 - info: mihome-vacuum.0 (1232) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason 2024-04-19 18:46:10.221 - info: mihome-vacuum.0 (1232) terminating 2024-04-19 18:46:15.796 - info: mihome-vacuum.0 (680497) starting. Version 4.2.0 in /opt/iobroker/node_modules/iobroker.mihome-vacuum, node: v21.7.3, js-controller: 5.0.19 2024-04-19 18:46:15.867 - info: mihome-vacuum.0 (680497) IOT enabled, create state 2024-04-19 18:46:16.017 - info: mihome-vacuum.0 (680497) select standard vacuum protocol.... 2024-04-19 18:46:16.494 - info: mihome-vacuum.0 (680497) create state for carpet_mode 2024-04-19 18:46:16.649 - info: mihome-vacuum.0 (680497) settest next timer: not availableKein Ding, kommt sofort wieder hoch.
-
@thomas-braun sagte in npm Error bei mihome-vacuum Adapter Installation:
Läuft natürlich auf einem Betriebssystem.
Da bin ich mir sicher, dass es auf einem Betriebssystem läuft
Aber läuft es auch auf Meinem Betriebssystem? -
Natürlich nicht.
-
