Cloud.0 funktioniert nicht mehr, entfernen nicht möglich
-
` > pi@ioBroker-RasPi:~ $ node -v
v8.12.0 `
Wie soll das geschehen sein?Gruß Michael
-
> Naja du hattest mal node 11 drauf … du erinnerst dich?
Das ist richtigSorry aber nein. Node 8 ist schon ok nur aktuell halt. Nodejs 11 ist eine dev versionDanach in 8.12.0 geändert
> 8.12 ist gut.
Das war der letzte Standpi@ioBroker-RasPi:~ $ cd /opt/iobroker pi@ioBroker-RasPi:/opt/iobroker $und jetzt
npm rebuildausführen?
-
pi@ioBroker-RasPi:/opt/iobroker $ npm rebuild > iobroker@1.1.2 install /opt/iobroker/node_modules/iobroker > node lib/prepareSetup.js && node lib/setup.js NPM version: 6.4.1 npm version >= 5: disabling package-lock npm install iobroker.discovery@stable --production --save npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@1.2.7 (node_modules/fsevents): npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@1.2.7: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"arm"}) + iobroker.discovery@1.2.4 removed 208 packages, updated 1 package and audited 6316 packages in 81.826s found 70 vulnerabilities (51 low, 3 moderate, 16 high) run `npm audit fix` to fix them, or `npm audit` for details packet folder is: /opt/iobroker/node_modules/iobroker.discovery | exists: true npm install iobroker.admin@stable --production --save npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@1.2.7 (node_modules/fsevents): npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@1.2.7: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"arm"}) + iobroker.admin@3.5.10 removed 163 packages and updated 1 package in 74.857s packet folder is: /opt/iobroker/node_modules/iobroker.admin | exists: true npm install iobroker.js-controller@stable --production --save > iobroker.js-controller@1.4.2 preinstall /opt/iobroker/node_modules/iobroker.js-controller > node lib/preinstall_check.js NPM version: 6.4.1 npm version >= 5: disabling package-lock > ursa-optional@0.9.10 install /opt/iobroker/node_modules/ursa-optional > node rebuild.js Killed packet folder is: /opt/iobroker/node_modules/iobroker.js-controller | exists: true Write "./iobroker start" to start the ioBroker Cannot set permissions of /opt/iobroker/node_modules/iobroker.js-controller/iobroker You can still manually copy Cannot create file /usr/bin/iobroker!. Non critical ----------------------------------------------------- You can manually copy file into /usr/bin/. Just write: sudo cp /opt/iobroker/node_modules/iobroker/install/iobroker /usr/bin/ sudo chmod 777 /usr/bin/iobroker ----------------------------------------------------- Cannot copy file to /etc/init.d/iobroker.sh: Error: EACCES: permission denied, open '/etc/init.d/iobroker.sh' ----------------------------------------------------- You can manually copy file and install autostart: sudo cp /opt/iobroker/node_modules/iobroker/install/linux/iobroker.sh /etc/init.d/ sudo chmod 777 /etc/init.d/iobroker.sh sudo bash /opt/iobroker/node_modules/iobroker/install/linux/install.sh ----------------------------------------------------- or just start "sudo bash /opt/iobroker/install.sh" ----------------------------------------------------- npm ERR! path /opt/iobroker/node_modules/iobroker.admin/node_modules/body-parser/package.json npm ERR! code ENOENT npm ERR! errno -2 npm ERR! syscall open npm ERR! enoent ENOENT: no such file or directory, open '/opt/iobroker/node_modules/iobroker.admin/node_modules/body-parser/package.json' npm ERR! enoent This is related to npm not being able to find a file. npm ERR! enoent npm ERR! A complete log of this run can be found in: npm ERR! /home/pi/.npm/_logs/2019-01-28T20_28_52_758Z-debug.log pi@ioBroker-RasPi:/opt/iobroker $Hier sind aber jetzt einige Fehler??
-
leider nicht
host.ioBroker-RasPi 2019-01-28 21:44:17.799 info Restart adapter system.adapter.zigbee.0 because enabled host.ioBroker-RasPi 2019-01-28 21:44:17.799 error instance system.adapter.zigbee.0 terminated with code 1 () Caught 2019-01-28 21:44:17.799 error by controller[0]: at Object.Module._extensions..js (module.js:663:10) Caught 2019-01-28 21:44:17.799 error by controller[0]: at Module._compile (module.js:652:30) Caught 2019-01-28 21:44:17.799 error by controller[0]: at Object. <anonymous>(/opt/iobroker/node_modules/iobroker.zigbee/node_modules/serialport/lib/bindings/linux.js:2:36) Caught 2019-01-28 21:44:17.799 error by controller[0]: at bindings (/opt/iobroker/node_modules/iobroker.zigbee/node_modules/bindings/bindings.js:81:44) Caught 2019-01-28 21:44:17.799 error by controller[0]: at require (internal/module.js:11:18) Caught 2019-01-28 21:44:17.799 error by controller[0]: at Module.require (module.js:596:17) Caught 2019-01-28 21:44:17.798 error by controller[0]: at Function.Module._load (module.js:497:3) Caught 2019-01-28 21:44:17.798 error by controller[0]: at tryModuleLoad (module.js:505:12) Caught 2019-01-28 21:44:17.798 error by controller[0]: at Module.load (module.js:565:32) Caught 2019-01-28 21:44:17.798 error by controller[0]: at Object.Module._extensions..node (module.js:681:18) Caught 2019-01-28 21:44:17.798 error by controller[0]: the module (for instance, using `npm rebuild` or `npm install`). Caught 2019-01-28 21:44:17.798 error by controller[0]: NODE_MODULE_VERSION 57\. Please try re-compiling or re-installing Caught 2019-01-28 21:44:17.798 error by controller[0]: NODE_MODULE_VERSION 67\. This version of Node.js requires Caught 2019-01-28 21:44:17.798 error by controller[0]: was compiled against a different Node.js version using Caught 2019-01-28 21:44:17.797 error by controller[0]: Error: The module '/opt/iobroker/node_modules/iobroker.zigbee/node_modules/serialport/build/Release/serialport.node' Caught 2019-01-28 21:44:17.797 error by controller[0]: ^ Caught 2019-01-28 21:44:17.797 error by controller[0]: throw e Caught 2019-01-28 21:44:17.797 error by controller[0]: /opt/iobroker/node_modules/iobroker.zigbee/node_modules/bindings/bindings.js:88 host.ioBroker-RasPi 2019-01-28 21:44:16.590 info instance system.adapter.zigbee.0 started with pid 24800 host.ioBroker-RasPi 2019-01-28 21:44:16.544 info object change system.adapter.zigbee.0 host.ioBroker-RasPi 2019-01-28 21:40:06.951 info instance system.adapter.dwd.0 terminated with code 0 (OK)</anonymous> -
Hier das log
-
Die Zigbee Instanz läuft wieder.
zigbee.0 2019-01-28 22:41:35.319 info (0x00158d00023213f6): WSDCGQ11LM - Xiaomi Aqara temperature, humidity and pressure sensor (EndDevice) zigbee.0 2019-01-28 22:41:35.318 info (0x00158d0002329079): WSDCGQ11LM - Xiaomi Aqara temperature, humidity and pressure sensor (EndDevice) zigbee.0 2019-01-28 22:41:35.314 info (0x00158d00024906fa): WSDCGQ11LM - Xiaomi Aqara temperature, humidity and pressure sensor (EndDevice) zigbee.0 2019-01-28 22:41:35.301 info zigbee-shepherd ready. version: 2.6.3 rev 20180815 zigbee.0 2019-01-28 22:41:35.288 info zigbee-shepherd started! zigbee.0 2019-01-28 22:41:34.480 info Start on port: /dev/serial/by-id/usb-Texas_Instruments_TI_CC2531_USB_CDC___0X00124B0012013B01-if00 with panID 6754 channel 11 zigbee.0 2019-01-28 22:41:34.461 info starting. Version 0.7.7 in /opt/iobroker/node_modules/iobroker.zigbee, node: v8.11.3 zigbee.0 2019-01-28 22:41:34.287 info States connected to redis: 127.0.0.1:6379 host.ioBroker-RasPi 2019-01-28 22:41:32.441 info instance system.adapter.zigbee.0 started with pid 27981 host.ioBroker-RasPi 2019-01-28 22:41:32.420 info object change system.adapter.zigbee.0 host.ioBroker-RasPi 2019-01-28 22:40:58.510 info instance system.adapter.zigbee.0 terminated with code 0 (OK) Caught 2019-01-28 22:40:58.509 error by controller[1]: Mon, 28 Jan 2019 21:40:58 GMT cc-znp:SREQ --> ZDO:mgmtPermitJoinReq, { addrmode: 15, dstaddr: 65532, duration: 0, tcsignificance: 0 } Caught 2019-01-28 22:40:58.509 error by controller[1]: 2019-01-28T21:40:58.453Z zigbee-shepherd:request REQ --> ZDO:mgmtPermitJoinReq Caught 2019-01-28 22:40:58.509 error by controller[1]: 2019-01-28T21:40:58.447Z zigbee-shepherd zigbee-shepherd is stopping. zigbee.0 2019-01-28 22:40:58.469 info terminating host.ioBroker-RasPi 2019-01-28 22:40:58.441 info stopInstance system.adapter.zigbee.0 killing pid 27926 host.ioBroker-RasPi 2019-01-28 22:40:58.440 info stopInstance system.adapter.zigbee.0Danke!
Werde den Zustand bis morgen beobachten.
Gruß Michael
-
Hallo apollon77,
Die Zigbee Instanz ist jetzt seit gestern ohne Abbruch durchgelaufen.
Es gibt zwar noch im Log einige gelb oder orange gekennzeichnete Eintragungen,
aber ich gehe mal davon aus , das das keine bedrohlichen Fehler sind.
Nun möchte ich natürlich Alexa wieder zuschalten. Dafür benötige ich aber eine Cloud.
Nur welche? Free Clouds soll es ja nicht mehr geben oder irre ich mich in dieser Hinsicht.
Gruß Michael
-
javascript.0 2019-01-29 20:34:39.786 warn at Timer.listOnTimeout (timers.js:290:5) javascript.0 2019-01-29 20:34:39.785 warn at tryOnTimeout (timers.js:323:5) javascript.0 2019-01-29 20:34:39.785 warn at ontimeout (timers.js:511:34) javascript.0 2019-01-29 20:34:39.785 warn at Timeout._onTimeout (/opt/iobroker/node_modules/iobroker.javascript/lib/sandbox.js:1294:29) javascript.0 2019-01-29 20:34:39.784 warn at Object.setState (/opt/iobroker/node_modules/iobroker.javascript/lib/sandbox.js:1236:28) javascript.0 2019-01-29 20:34:39.782 warn Wrong type of fhem.0.Ventilation.state: "boolean". Please fix, while deprecated and will not work in next versions. fhem.0 2019-01-29 20:34:38.786 info event ioBroker "fhem.0.GewaechshausHeizung.state off" > set GewaechshausHeizung off javascript.0 2019-01-29 20:34:38.781 warn at TCP.onread (net.js:597:20) javascript.0 2019-01-29 20:34:38.781 warn at Socket.Readable.push (_stream_readable.js:208:10) javascript.0 2019-01-29 20:34:38.780 warn at readableAddChunk (_stream_readable.js:250:11) javascript.0 2019-01-29 20:34:38.780 warn at addChunk (_stream_readable.js:263:12) javascript.0 2019-01-29 20:34:38.780 warn at Socket.emit (events.js:211:7) javascript.0 2019-01-29 20:34:38.780 warn at emitOne (events.js:116:13) javascript.0 2019-01-29 20:34:38.780 warn at Socket. <anonymous>(/opt/iobroker/node_modules/redis/index.js:274:27) javascript.0 2019-01-29 20:34:38.780 warn at JavascriptRedisParser.execute (/opt/iobroker/node_modules/redis-parser/lib/parser.js:574:12) javascript.0 2019-01-29 20:34:38.779 warn at JavascriptRedisParser.returnReply (/opt/iobroker/node_modules/redis/index.js:192:18) javascript.0 2019-01-29 20:34:38.779 warn at RedisClient.return_reply (/opt/iobroker/node_modules/redis/index.js:833:9) javascript.0 2019-01-29 20:34:38.779 warn at return_pub_sub (/opt/iobroker/node_modules/redis/index.js:794:18) javascript.0 2019-01-29 20:34:38.779 warn at RedisClient.emit (events.js:217:7) javascript.0 2019-01-29 20:34:38.779 warn at emitThree (events.js:136:13) javascript.0 2019-01-29 20:34:38.779 warn at RedisClient. <anonymous>(/opt/iobroker/node_modules/iobroker.js-controller/lib/states/statesInRedis.js:596:25) javascript.0 2019-01-29 20:34:38.779 warn at change (/opt/iobroker/node_modules/iobroker.js-controller/lib/adapter.js:3425:37) javascript.0 2019-01-29 20:34:38.778 warn at Object.stateChange (/opt/iobroker/node_modules/iobroker.javascript/main.js:358:25) javascript.0 2019-01-29 20:34:38.778 warn at Object.callback (/opt/iobroker/node_modules/iobroker.javascript/lib/sandbox.js:756:38) javascript.0 2019-01-29 20:34:38.778 warn at Object. <anonymous>(script.js.Gewächshaus.Heizung_schalten:25:7) javascript.0 2019-01-29 20:34:38.778 warn at setState (/opt/iobroker/node_modules/iobroker.javascript/lib/sandbox.js:1236:28) javascript.0 2019-01-29 20:34:38.775 warn Wrong type of fhem.0.GewaechshausHeizung.state: "boolean". Please fix, while deprecated and will not work in next versions. fhem.0 2019-01-29 20:32:16.055 info check channel fhem.0.CN_Brennstoffverbrauch | name: CN.Brennstoffverbrauch | room: 1.3.1 Heizraum | role: undefined | function: no | 1/1 fhem.0 2019-01-29 20:32:15.453 info check channel CN.Brennstoffverbrauch > jsonlist2 CN.Brennstoffverbrauch fhem.0 2019-01-29 20:32:13.949 info check channel fhem.0.CN_Brennstoffkosten | name: CN.Brennstoffkosten | room: 1.3.1 Heizraum | role: undefined | function: no | 1/1 fhem.0 2019-01-29 20:32:13.750 info check channel CN.Brennstoffkosten > jsonlist2 CN.Brennstoffkosten</anonymous></anonymous></anonymous>Das ist ein Part von den orangenen Eintragungen.
Zur Cloud;
Alexa soll integriert werden, dann möchte ich vis nutzen, gelegentlich wenn wir z.B. im Urlaub sind möchte ich mir ioBroker ansehen
z.B. wenn etwas nicht läuft.
Gruß Michael
-
Hallo,
Ich habe jetzt mal die Log Einträge kontrolliert.
Bei den orangenen Einträgen handelt es sich immer um javascript.0 Einträge.
Ich glaube, das etwas mit den Blocklys nicht stimmt obwohl sie richtig schalten.
host.ioBroker-RasPi 2019-01-29 21:50:00.047 info instance system.adapter.dwd.0 started with pid 24674 fhem.0 2019-01-29 21:48:24.619 info event ioBroker "fhem.0.Ventilation.state off" > set Ventilation off javascript.0 2019-01-29 21:48:24.616 warn at Timer.listOnTimeout (timers.js:290:5) javascript.0 2019-01-29 21:48:24.616 warn at tryOnTimeout (timers.js:323:5) javascript.0 2019-01-29 21:48:24.616 warn at ontimeout (timers.js:511:34) javascript.0 2019-01-29 21:48:24.616 warn at Timeout._onTimeout (/opt/iobroker/node_modules/iobroker.javascript/lib/sandbox.js:1294:29) javascript.0 2019-01-29 21:48:24.616 warn at Object.setState (/opt/iobroker/node_modules/iobroker.javascript/lib/sandbox.js:1236:28) javascript.0 2019-01-29 21:48:24.615 warn Wrong type of fhem.0.Ventilation.state: "boolean". Please fix, while deprecated and will not work in next versions. fhem.0 2019-01-29 21:48:23.616 info event ioBroker "fhem.0.GewaechshausHeizung.state off" > set GewaechshausHeizung off javascript.0 2019-01-29 21:48:23.615 warn at TCP.onread (net.js:597:20) javascript.0 2019-01-29 21:48:23.615 warn at Socket.Readable.push (_stream_readable.js:208:10) javascript.0 2019-01-29 21:48:23.615 warn at readableAddChunk (_stream_readable.js:250:11) javascript.0 2019-01-29 21:48:23.615 warn at addChunk (_stream_readable.js:263:12) javascript.0 2019-01-29 21:48:23.615 warn at Socket.emit (events.js:211:7) javascript.0 2019-01-29 21:48:23.615 warn at emitOne (events.js:116:13) javascript.0 2019-01-29 21:48:23.615 warn at Socket. <anonymous>(/opt/iobroker/node_modules/redis/index.js:274:27) javascript.0 2019-01-29 21:48:23.614 warn at JavascriptRedisParser.execute (/opt/iobroker/node_modules/redis-parser/lib/parser.js:574:12) javascript.0 2019-01-29 21:48:23.614 warn at JavascriptRedisParser.returnReply (/opt/iobroker/node_modules/redis/index.js:192:18) javascript.0 2019-01-29 21:48:23.614 warn at RedisClient.return_reply (/opt/iobroker/node_modules/redis/index.js:833:9) javascript.0 2019-01-29 21:48:23.614 warn at return_pub_sub (/opt/iobroker/node_modules/redis/index.js:794:18) javascript.0 2019-01-29 21:48:23.614 warn at RedisClient.emit (events.js:217:7) javascript.0 2019-01-29 21:48:23.614 warn at emitThree (events.js:136:13) javascript.0 2019-01-29 21:48:23.614 warn at RedisClient. <anonymous>(/opt/iobroker/node_modules/iobroker.js-controller/lib/states/statesInRedis.js:596:25) javascript.0 2019-01-29 21:48:23.614 warn at change (/opt/iobroker/node_modules/iobroker.js-controller/lib/adapter.js:3425:37) javascript.0 2019-01-29 21:48:23.614 warn at Object.stateChange (/opt/iobroker/node_modules/iobroker.javascript/main.js:358:25) javascript.0 2019-01-29 21:48:23.614 warn at Object.callback (/opt/iobroker/node_modules/iobroker.javascript/lib/sandbox.js:756:38) javascript.0 2019-01-29 21:48:23.613 warn at Object. <anonymous>(script.js.Gewächshaus.Heizung_schalten:25:7) javascript.0 2019-01-29 21:48:23.613 warn at setState (/opt/iobroker/node_modules/iobroker.javascript/lib/sandbox.js:1236:28) javascript.0 2019-01-29 21:48:23.613 warn Wrong type of fhem.0.GewaechshausHeizung.state: "boolean". Please fix, while deprecated and will not work in next versions.</anonymous></anonymous></anonymous>Wäre es sinnvoll die Einträge unter Skripte einzustellen?
Gruß Michael
-
Das Relevante hier ist das:
javascript.0 2019-01-29 21:48:24.615 warn Wrong type of fhem.0.Ventilation.state: "boolean". Please fix, while deprecated and will not work in next versions.
Du hast einen State der einen bestimmten Datentyp hat und Du schreibst einen anderen rein. Ja Du musst deine Blockly so anpassen das der Datenyp korrekt ist
-
Danke für Deinen Hinweis. Habe mir gerade mal das Blockly angesehen,
komme aber nicht auf den Fehler.
Werde die Frage morgen unter Skripte einstellen.
Wenn dann alle Punkte bereinigt sind werde ich mit der Cloud weiter machen.
Danke für Deine Unterstützung.
Gruß Michael
445
Online32.7k
Benutzer82.5k
Themen1.3m
Beiträge