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

[zombiee77]

Hallo zusammen,

habe ioBroker unter Windws am laufen.
Als ich versucht habe ioBroker einem Update zu nterziehen assiert folgendes:

C:\iobroker>iobroker update

C:\iobroker>node node_modules/iobroker.js-controller/iobroker.js update
(node:7416) UnhandledPromiseRejectionWarning: ParserError: Protocol error, got "H" as reply type byte. Please report this.
    at handleError (C:\iobroker\node_modules\iobroker.js-controller\node_modules\redis-parser\lib\parser.js:190:15)
    at parseType (C:\iobroker\node_modules\iobroker.js-controller\node_modules\redis-parser\lib\parser.js:304:14)
(node:7416) UnhandledPromiseRejectionWarning: 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(). (rejection id: 1)
(node:7416) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.
(node:7416) UnhandledPromiseRejectionWarning: ParserError: Protocol error, got "H" as reply type byte. Please report this.
    at handleError (C:\iobroker\node_modules\iobroker.js-controller\node_modules\redis-parser\lib\parser.js:190:15)
    at parseType (C:\iobroker\node_modules\iobroker.js-controller\node_modules\redis-parser\lib\parser.js:304:14)
(node:7416) UnhandledPromiseRejectionWarning: 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(). (rejection id: 2)
Used repository: default
hash changed => force download of new sources
update done

Adapter    "icons-fatcow-hosting": 0.1.0   , installed 0.1.0
Adapter    .....


C:\iobroker>iobroker upgrade self

C:\iobroker>node node_modules/iobroker.js-controller/iobroker.js upgrade self
(node:5408) UnhandledPromiseRejectionWarning: ParserError: Protocol error, got "H" as reply type byte. Please report this.
    at handleError (C:\iobroker\node_modules\iobroker.js-controller\node_modules\redis-parser\lib\parser.js:190:15)
    at parseType (C:\iobroker\node_modules\iobroker.js-controller\node_modules\redis-parser\lib\parser.js:304:14)
(node:5408) UnhandledPromiseRejectionWarning: 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(). (rejection id: 1)
(node:5408) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.
(node:5408) UnhandledPromiseRejectionWarning: ParserError: Protocol error, got "H" as reply type byte. Please report this.
    at handleError (C:\iobroker\node_modules\iobroker.js-controller\node_modules\redis-parser\lib\parser.js:190:15)
    at parseType (C:\iobroker\node_modules\iobroker.js-controller\node_modules\redis-parser\lib\parser.js:304:14)
(node:5408) UnhandledPromiseRejectionWarning: 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(). (rejection id: 2)
Update js-controller from @2.1.0 to @2.1.1
NPM version: 6.4.1
npm install iobroker.js-controller@2.1.1 --unsafe-perm --loglevel error --prefix "C:/iobroker" (System call)
npm ERR! path C:\iobroker\node_modules\iobroker.js-controller
npm ERR! code EBUSY
npm ERR! errno -4082
npm ERR! syscall rename
npm ERR! EBUSY: resource busy or locked, rename 'C:\iobroker\node_modules\iobroker.js-controller' -> 'C:\iobroker\node_modules\.iobroker.js-controller.DELETE'

npm ERR! A complete log of this run can be found in:
npm ERR!     C:\Users\oezzi\AppData\Roaming\npm-cache\_logs\2019-11-22T20_36_37_532Z-debug.log
host.ASUS-Notebook Cannot install iobroker.js-controller@2.1.1: 4294963214

Könnt Ihr mir sagen , was da schief läuft?

Liebe Grüße

[Stabilostick]

@zombiee77

Läuft vielleicht der ioBroker-Dienst noch? ioBroker muss vor dem Upgrade gestoppt werden. Welche Node.js-Version nutzt Du?

[zombiee77]

@Stabilostick sagte in js controller upgrade geht nicht unter windows:

ioBroker-Dienst noch? ioBroker muss vor dem Upgrade gestoppt werden. Welche Node.js-Version

Hi Stabilostick,

danke für die schnelle Antwort.
Habe es nun geschafft indem ich mir node js für Windows von:

https://nodejs.org/en/download/releases/

heruntergeladen habe.

Jetzt ging es.

Danke.

LG

z