UNSOLVED IOT Adapter lässt sich nicht Installieren

[jack99n]

Hallo,

Kann mir jemand sagen warum sich der IOT Adapter nicht Installieren lässt?

0 info it worked if it ends with ok
1 verbose cli [ 'C:\\Program Files\\nodejs\\node.exe',
1 verbose cli   'C:\\Windows\\system32\\config\\systemprofile\\AppData\\Roaming\\npm\\node_modules\\npm\\bin\\npm-cli.js',
1 verbose cli   'install',
1 verbose cli   'https://github.com/ioBroker/ioBroker.iot/tarball/master',
1 verbose cli   '--production',
1 verbose cli   '--save',
1 verbose cli   '--prefix',
1 verbose cli   'C:/ioBroker' ]
2 info using npm@6.4.1
3 info using node@v8.11.3
4 verbose npm-session 152c1f5ae414efcd
5 silly install loadCurrentTree
6 silly install readGlobalPackageData
7 http fetch GET 200 https://github.com/ioBroker/ioBroker.iot/tarball/master 10617ms
8 silly pacote remote manifest for undefined@https://github.com/ioBroker/ioBroker.iot/tarball/master fetched in 10844ms
9 timing stage:loadCurrentTree Completed in 14362ms
10 silly install loadIdealTree
11 silly install cloneCurrentTreeToIdealTree
12 timing stage:loadIdealTree:cloneCurrentTree Completed in 0ms
13 silly install loadShrinkwrap
14 timing stage:loadIdealTree:loadShrinkwrap Completed in 15ms
15 silly install loadAllDepsIntoIdealTree
16 silly resolveWithNewModule iobroker.iot@0.4.2 checking installable status
17 http fetch GET 304 https://registry.npmjs.org/iobroker.type-detector 879ms (from cache)
18 silly pacote range manifest for iobroker.type-detector@^0.1.0 fetched in 919ms
19 silly resolveWithNewModule iobroker.type-detector@0.1.0 checking installable status
20 http fetch GET 304 https://registry.npmjs.org/request 934ms (from cache)
21 http fetch GET 304 https://registry.npmjs.org/aws-iot-device-sdk 965ms (from cache)
22 silly pacote range manifest for request@^2.88.0 fetched in 971ms
23 silly resolveWithNewModule request@2.88.0 checking installable status
24 silly pacote range manifest for aws-iot-device-sdk@^2.2.1 fetched in 984ms
25 silly resolveWithNewModule aws-iot-device-sdk@2.2.1 checking installable status
26 http fetch GET 304 https://registry.npmjs.org/@iobroker%2fadapter-core 982ms (from cache)
27 silly pacote range manifest for @iobroker/adapter-core@^1.0.3 fetched in 1012ms
28 silly resolveWithNewModule @iobroker/adapter-core@1.0.3 checking installable status
29 http fetch GET 304 https://registry.npmjs.org/@types%2fiobroker 280ms (from cache)
30 silly pacote range manifest for @types/iobroker@^1.4.3 fetched in 324ms
31 silly resolveWithNewModule @types/iobroker@1.4.10 checking installable status
32 http fetch GET 304 https://registry.npmjs.org/@types%2fnode 216ms (from cache)
33 silly pacote range manifest for @types/node@* fetched in 260ms
34 silly resolveWithNewModule @types/node@11.11.3 checking installable status
35 http fetch GET 304 https://registry.npmjs.org/minimist 329ms (from cache)
36 http fetch GET 304 https://registry.npmjs.org/crypto-js 331ms (from cache)
37 silly pacote version manifest for minimist@1.2.0 fetched in 363ms
38 silly resolveWithNewModule minimist@1.2.0 checking installable status
39 silly pacote version manifest for crypto-js@3.1.6 fetched in 363ms
40 silly resolveWithNewModule crypto-js@3.1.6 checking installable status
41 http fetch GET 304 https://registry.npmjs.org/websocket-stream 414ms (from cache)
42 http fetch GET 304 https://registry.npmjs.org/mqtt 469ms (from cache)
43 silly pacote range manifest for websocket-stream@^5.0.1 fetched in 475ms
44 silly resolveWithNewModule websocket-stream@5.1.2 checking installable status
45 silly pacote version manifest for mqtt@2.15.1 fetched in 534ms
46 silly resolveWithNewModule mqtt@2.15.1 checking installable status
47 http fetch GET 304 https://registry.npmjs.org/end-of-stream 677ms (from cache)
48 http fetch GET 304 https://registry.npmjs.org/concat-stream 679ms (from cache)
49 http fetch GET 304 https://registry.npmjs.org/commist 686ms (from cache)
50 http fetch GET 304 https://registry.npmjs.org/mqtt-packet 683ms (from cache)
51 silly pacote range manifest for end-of-stream@^1.1.0 fetched in 705ms
52 silly resolveWithNewModule end-of-stream@1.4.1 checking installable status
53 silly pacote range manifest for concat-stream@^1.6.0 fetched in 747ms
54 silly resolveWithNewModule concat-stream@1.6.2 checking installable status
55 silly pacote range manifest for commist@^1.0.0 fetched in 756ms
56 silly resolveWithNewModule commist@1.1.0 checking installable status
57 silly pacote range manifest for mqtt-packet@^5.4.0 fetched in 757ms
58 silly resolveWithNewModule mqtt-packet@5.6.0 checking installable status
59 http fetch GET 304 https://registry.npmjs.org/readable-stream 783ms (from cache)
60 silly pacote range manifest for readable-stream@^2.3.3 fetched in 881ms
61 silly resolveWithNewModule readable-stream@2.3.6 checking installable status
62 http fetch GET 304 https://registry.npmjs.org/inherits 949ms (from cache)
63 http fetch GET 304 https://registry.npmjs.org/split2 930ms (from cache)
64 http fetch GET 304 https://registry.npmjs.org/help-me 967ms (from cache)
65 silly pacote range manifest for split2@^2.1.1 fetched in 963ms
66 silly resolveWithNewModule split2@2.2.0 checking installable status
67 silly pacote range manifest for inherits@^2.0.3 fetched in 988ms
68 silly resolveWithNewModule inherits@2.0.3 checking installable status
69 silly pacote range manifest for help-me@^1.0.1 fetched in 1003ms
70 silly resolveWithNewModule help-me@1.1.0 checking installable status
71 http fetch GET 304 https://registry.npmjs.org/reinterval 984ms (from cache)
72 silly pacote range manifest for reinterval@^1.1.0 fetched in 999ms
73 silly resolveWithNewModule reinterval@1.1.0 checking installable status
74 http fetch GET 304 https://registry.npmjs.org/xtend 348ms (from cache)
75 http fetch GET 304 https://registry.npmjs.org/pump 1042ms (from cache)
76 silly pacote range manifest for xtend@^4.0.1 fetched in 366ms
77 silly resolveWithNewModule xtend@4.0.1 checking installable status
78 silly pacote range manifest for pump@^2.0.0 fetched in 1058ms
79 silly resolveWithNewModule pump@2.0.1 checking installable status
80 http fetch GET 304 https://registry.npmjs.org/leven 179ms (from cache)
81 silly pacote range manifest for leven@^2.1.0 fetched in 200ms
82 silly resolveWithNewModule leven@2.1.0 checking installable status
83 http fetch GET 304 https://registry.npmjs.org/typedarray 254ms (from cache)
84 silly pacote range manifest for typedarray@^0.0.6 fetched in 258ms
85 silly resolveWithNewModule typedarray@0.0.6 checking installable status
86 http fetch GET 304 https://registry.npmjs.org/buffer-from 262ms (from cache)
87 silly pacote range manifest for buffer-from@^1.0.0 fetched in 268ms
88 silly resolveWithNewModule buffer-from@1.1.1 checking installable status
89 http fetch GET 304 https://registry.npmjs.org/string_decoder 385ms (from cache)
90 http fetch GET 304 https://registry.npmjs.org/isarray 388ms (from cache)
91 http fetch GET 304 https://registry.npmjs.org/process-nextick-args 392ms (from cache)
92 silly pacote range manifest for isarray@~1.0.0 fetched in 394ms
93 silly resolveWithNewModule isarray@1.0.0 checking installable status
94 silly pacote range manifest for string_decoder@~1.1.1 fetched in 466ms
95 silly resolveWithNewModule string_decoder@1.1.1 checking installable status
96 silly pacote range manifest for process-nextick-args@~2.0.0 fetched in 469ms
97 silly resolveWithNewModule process-nextick-args@2.0.0 checking installable status
98 http fetch GET 304 https://registry.npmjs.org/core-util-is 498ms (from cache)
99 silly pacote range manifest for core-util-is@~1.0.0 fetched in 532ms
100 silly resolveWithNewModule core-util-is@1.0.2 checking installable status
101 http fetch GET 304 https://registry.npmjs.org/util-deprecate 593ms (from cache)
102 http fetch GET 304 https://registry.npmjs.org/safe-buffer 595ms (from cache)
103 silly pacote range manifest for util-deprecate@~1.0.1 fetched in 622ms
104 silly resolveWithNewModule util-deprecate@1.0.2 checking installable status
105 silly pacote range manifest for safe-buffer@~5.1.1 fetched in 634ms
106 silly resolveWithNewModule safe-buffer@5.1.2 checking installable status
107 http fetch GET 304 https://registry.npmjs.org/once 372ms (from cache)
108 silly pacote range manifest for once@^1.4.0 fetched in 376ms
109 silly resolveWithNewModule once@1.4.0 checking installable status
110 http fetch GET 304 https://registry.npmjs.org/wrappy 240ms (from cache)
111 silly pacote range manifest for wrappy@1 fetched in 249ms
112 silly resolveWithNewModule wrappy@1.0.2 checking installable status
113 http fetch GET 304 https://registry.npmjs.org/glob-stream 197ms (from cache)
114 silly pacote range manifest for glob-stream@^6.1.0 fetched in 226ms
115 silly resolveWithNewModule glob-stream@6.1.0 checking installable status
116 http fetch GET 304 https://registry.npmjs.org/through2 254ms (from cache)
117 http fetch GET 304 https://registry.npmjs.org/callback-stream 276ms (from cache)
118 silly pacote range manifest for through2@^2.0.1 fetched in 282ms
119 silly resolveWithNewModule through2@2.0.5 checking installable status
120 silly pacote range manifest for callback-stream@^1.0.2 fetched in 293ms
121 silly resolveWithNewModule callback-stream@1.1.0 checking installable status
122 http fetch GET 304 https://registry.npmjs.org/pumpify 848ms (from cache)
123 http fetch GET 304 https://registry.npmjs.org/glob-parent 853ms (from cache)
124 http fetch GET 304 https://registry.npmjs.org/glob 860ms (from cache)
125 http fetch GET 304 https://registry.npmjs.org/is-negated-glob 863ms (from cache)
126 http fetch GET 304 https://registry.npmjs.org/remove-trailing-separator 858ms (from cache)
127 http fetch GET 304 https://registry.npmjs.org/ordered-read-streams 865ms (from cache)
128 http fetch GET 304 https://registry.npmjs.org/extend 871ms (from cache)
129 http fetch GET 304 https://registry.npmjs.org/to-absolute-glob 861ms (from cache)
130 http fetch GET 304 https://registry.npmjs.org/unique-stream 892ms (from cache)
131 silly pacote range manifest for glob-parent@^3.1.0 fetched in 904ms
132 silly resolveWithNewModule glob-parent@3.1.0 checking installable status
133 silly pacote range manifest for pumpify@^1.3.5 fetched in 902ms
134 silly resolveWithNewModule pumpify@1.5.1 checking installable status
135 silly pacote range manifest for glob@^7.1.1 fetched in 909ms
136 silly resolveWithNewModule glob@7.1.3 checking installable status
137 silly pacote range manifest for is-negated-glob@^1.0.0 fetched in 909ms
138 silly resolveWithNewModule is-negated-glob@1.0.0 checking installable status
139 silly pacote range manifest for extend@^3.0.0 fetched in 917ms
140 silly resolveWithNewModule extend@3.0.2 checking installable status
141 silly pacote range manifest for ordered-read-streams@^1.0.0 fetched in 915ms
142 silly resolveWithNewModule ordered-read-streams@1.0.1 checking installable status
143 silly pacote range manifest for remove-trailing-separator@^1.0.1 fetched in 912ms
144 silly resolveWithNewModule remove-trailing-separator@1.1.0 checking installable status
145 silly pacote range manifest for to-absolute-glob@^2.0.0 fetched in 914ms
146 silly resolveWithNewModule to-absolute-glob@2.0.2 checking installable status
147 silly pacote range manifest for unique-stream@^2.0.2 fetched in 925ms
148 silly resolveWithNewModule unique-stream@2.3.1 checking installable status
149 http fetch GET 304 https://registry.npmjs.org/inflight 422ms (from cache)
150 silly pacote range manifest for inflight@^1.0.4 fetched in 540ms
151 silly resolveWithNewModule inflight@1.0.6 checking installable status
152 http fetch GET 304 https://registry.npmjs.org/fs.realpath 644ms (from cache)
153 http fetch GET 304 https://registry.npmjs.org/path-is-absolute 638ms (from cache)
154 http fetch GET 304 https://registry.npmjs.org/minimatch 641ms (from cache)
155 silly pacote range manifest for fs.realpath@^1.0.0 fetched in 652ms
156 silly resolveWithNewModule fs.realpath@1.0.0 checking installable status
157 silly pacote range manifest for path-is-absolute@^1.0.0 fetched in 647ms
158 silly resolveWithNewModule path-is-absolute@1.0.1 checking installable status
159 silly pacote range manifest for minimatch@^3.0.4 fetched in 651ms
160 silly resolveWithNewModule minimatch@3.0.4 checking installable status
161 http fetch GET 304 https://registry.npmjs.org/brace-expansion 207ms (from cache)
162 silly fetchPackageMetaData error for brace-expansion@^1.1.7 Unexpected end of JSON input while parsing near '...grity":"sha512-u0KjSZ'
163 timing stage:rollbackFailedOptional Completed in 2ms
164 timing stage:runTopLevelLifecycles Completed in 21638ms
165 verbose stack SyntaxError: Unexpected end of JSON input while parsing near '...grity":"sha512-u0KjSZ'
165 verbose stack     at JSON.parse (<anonymous>)
165 verbose stack     at parseJson (C:\Windows\system32\config\systemprofile\AppData\Roaming\npm\node_modules\npm\node_modules\json-parse-better-errors\index.js:7:17)
165 verbose stack     at consumeBody.call.then.buffer (C:\Windows\system32\config\systemprofile\AppData\Roaming\npm\node_modules\npm\node_modules\node-fetch-npm\src\body.js:96:50)
165 verbose stack     at <anonymous>
165 verbose stack     at process._tickCallback (internal/process/next_tick.js:188:7)
166 verbose cwd C:\ioBroker\node_modules\iobroker
167 verbose Windows_NT 6.1.7601
168 verbose argv "C:\\Program Files\\nodejs\\node.exe" "C:\\Windows\\system32\\config\\systemprofile\\AppData\\Roaming\\npm\\node_modules\\npm\\bin\\npm-cli.js" "install" "https://github.com/ioBroker/ioBroker.iot/tarball/master" "--production" "--save" "--prefix" "C:/ioBroker"
169 verbose node v8.11.3
170 verbose npm  v6.4.1
171 error Unexpected end of JSON input while parsing near '...grity":"sha512-u0KjSZ'
172 verbose exit [ 1, true ]

[jack99n]

Hallo,

Keiner eine Idee wie ich das Problem lösen könnte?