ah, gut zu wissen 
Aber nein. Da sieht jetzt nix verdächtig aus oder so. Gnarf.
+-- [email protected]
+-- [email protected]
+-- [email protected]
+-- [email protected]
+-- [email protected]
+-- [email protected]
+-- [email protected]
+-- [email protected]
+-- [email protected]
+-- [email protected]
+-- [email protected]
+-- [email protected]
+-- [email protected]
`-- [email protected]
Hast du das „normale“ people-plugin noch installiert? Evtl. mal dieses deinstallieren und dann die plus-version nochmals aufspielen......
Hey 
Ja, das habe ich vorher mit sudo npm uninstall Pluginname -g runtergeschmissen.
Das müsste doch theoretisch reichen, oder?
Aus der alten config.json hab ich auch alle people-zeilen rausgekickt und sie auch durch jsonlint geschubst.
Okay. Is ja nicht so, dass ich es nicht weiter versuchen würde.
Was hab ich probiert?
1. Plugin neuinstalliert per: sudo npm install -g --unsafe-perm homebridge-people-plus
Nach dem Start der homebridge passiert folgendes:
[2018-10-31 20:22:11] [Test] Initializing PeoplePlus accessory...
/usr/local/lib/node_modules/homebridge-people-plus/node_modules/raw-socket/index.js:47
this.wrap = new raw.SocketWrap (
^
Error: Operation not permitted
at new Socket (/usr/local/lib/node_modules/homebridge-people-plus/node_modules/raw-socket/index.js:47:14)
at Object.exports.createSocket (/usr/local/lib/node_modules/homebridge-people-plus/node_modules/raw-socket/index.js:202:9)
at Session.getSocket (/usr/local/lib/node_modules/homebridge-people-plus/node_modules/net-ping/index.js:147:20)
at new Session (/usr/local/lib/node_modules/homebridge-people-plus/node_modules/net-ping/index.js:101:7)
at Object.exports.createSession (/usr/local/lib/node_modules/homebridge-people-plus/node_modules/net-ping/index.js:545:9)
at new NetworkObserver (/usr/local/lib/node_modules/homebridge-people-plus/network.js:13:29)
at Function.get net [as net] (/usr/local/lib/node_modules/homebridge-people-plus/index.js:82:25)
at PeoplePlusAccessory.get net [as net] (/usr/local/lib/node_modules/homebridge-people-plus/index.js:88:33)
at PeoplePlusAccessory.setupDeviceObserver (/usr/local/lib/node_modules/homebridge-people-plus/index.js:67:25)
at new PeoplePlusAccessory (/usr/local/lib/node_modules/homebridge-people-plus/index.js:31:14)
at new <anonymous> (/usr/local/lib/node_modules/homebridge-people-plus/node_modules/homebridge-plugin-helpers/index.js:19:11)
at Server._loadAccessories (/usr/local/lib/node_modules/homebridge/lib/server.js:297:29)
at Server.run (/usr/local/lib/node_modules/homebridge/lib/server.js:87:38)
at module.exports (/usr/local/lib/node_modules/homebridge/lib/cli.js:45:10)
at Object.<anonymous> (/usr/local/lib/node_modules/homebridge/bin/homebridge:17:22)
at Module._compile (module.js:653:30)
at Object.Module._extensions..js (module.js:664:10)
at Module.load (module.js:566:32)
at tryModuleLoad (module.js:506:12)
at Function.Module._load (module.js:498:3)
at Function.Module.runMain (module.js:694:10)
at startup (bootstrap_node.js:204:16)2. Plugin wieder deinstalliert.
3. Plugin erneut installiert als root. Befehl: sudo npm install -g --unsafe-perm homebridge-people-plus
Das Ergebnis ist exakt wie das obige. Und nun weiß ich wirklich absolut nicht mehr weiter.
boah ich geh echt noch kaputt an diesem Unterfangen 
Sorry wenn ich nerve Jungs - Aber ich bekomme dieses People-Plus Plugin einfach nicht ans laufen, geschweige denn installiert.
root@RAWWR:~# npm install -g homebridge-people-plus
> [email protected] install /usr/local/lib/node_modules/homebridge-people-plus/node_modules/raw-socket
> node-gyp rebuild
gyp WARN EACCES user "root" does not have permission to access the dev dir "/root/.node-gyp/8.12.0"
gyp WARN EACCES attempting to reinstall using temporary dev dir "/usr/local/lib/node_modules/homebridge-people-plus/node_modules/raw-socket/.node-gyp"
gyp WARN install got an error, rolling back install
gyp WARN install got an error, rolling back install
gyp ERR! configure error
gyp ERR! stack Error: EACCES: permission denied, mkdir '/usr/local/lib/node_modules/homebridge-people-plus/node_modules/raw-socket/.node-gyp'
gyp ERR! System Linux 4.14.71-v7+
gyp ERR! command "/usr/local/bin/node" "/usr/local/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "rebuild"
gyp ERR! cwd /usr/local/lib/node_modules/homebridge-people-plus/node_modules/raw-socket
gyp ERR! node -v v8.12.0
gyp ERR! node-gyp -v v3.8.0
gyp ERR! not ok
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! [email protected] install: `node-gyp rebuild`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the [email protected] install script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm ERR! A complete log of this run can be found in:
npm ERR! /root/.npm/_logs/2018-10-31T15_40_38_418Z-debug.log
root@RAWWR:~# Das ist ist das log, welches der Raspi am ende auswirft:
0 info it worked if it ends with ok
1 verbose cli [ '/usr/local/bin/node',
1 verbose cli '/usr/local/bin/npm',
1 verbose cli 'install',
1 verbose cli '-g',
1 verbose cli 'homebridge-people-plus' ]
2 info using [email protected]
3 info using [email protected]
4 verbose npm-session de5913595e1109ef
5 silly install loadCurrentTree
6 silly install readGlobalPackageData
7 http fetch GET 200 https://registry.npmjs.org/homebridge-people-plus 1112ms
8 silly pacote tag manifest for homebridge-people-plus@latest fetched in 1223ms
9 timing stage:loadCurrentTree Completed in 2261ms
10 silly install loadIdealTree
11 silly install cloneCurrentTreeToIdealTree
12 timing stage:loadIdealTree:cloneCurrentTree Completed in 2ms
13 silly install loadShrinkwrap
14 timing stage:loadIdealTree:loadShrinkwrap Completed in 9ms
15 silly install loadAllDepsIntoIdealTree
16 silly resolveWithNewModule [email protected] checking installable status
17 http fetch GET 200 https://registry.npmjs.org/net-ping 261ms
18 silly pacote range manifest for net-ping@^1.2.0 fetched in 283ms
19 silly resolveWithNewModule [email protected] checking installable status
20 http fetch GET 200 https://registry.npmjs.org/bluebird 373ms
21 silly pacote range manifest for bluebird@^3.4.7 fetched in 419ms
22 silly resolveWithNewModule [email protected] checking installable status
23 http fetch GET 304 https://registry.npmjs.org/ping 412ms (from cache)
24 silly pacote range manifest for ping@^0.1.10 fetched in 427ms
25 silly resolveWithNewModule [email protected] checking installable status
26 http fetch GET 200 https://registry.npmjs.org/arp-a 800ms
27 silly pacote range manifest for arp-a@^0.5.1 fetched in 814ms
28 silly resolveWithNewModule [email protected] checking installable status
29 http fetch GET 200 https://registry.npmjs.org/homebridge-plugin-helpers 903ms
30 silly pacote range manifest for homebridge-plugin-helpers@>=0.1.0 fetched in 916ms
31 silly resolveWithNewModule [email protected] checking installable status
32 http fetch GET 200 https://registry.npmjs.org/raw-socket 97ms
33 silly pacote range manifest for raw-socket@* fetched in 108ms
34 silly resolveWithNewModule [email protected] checking installable status
35 http fetch GET 304 https://registry.npmjs.org/nan 114ms (from cache)
36 silly pacote range manifest for [email protected].* fetched in 134ms
37 silly resolveWithNewModule [email protected] checking installable status
38 http fetch GET 304 https://registry.npmjs.org/q 78ms (from cache)
39 silly pacote range manifest for [email protected] fetched in 91ms
40 silly resolveWithNewModule [email protected] checking installable status
41 timing stage:loadIdealTree:loadAllDepsIntoIdealTree Completed in 1343ms
42 timing stage:loadIdealTree Completed in 1377ms
43 silly currentTree lib
44 silly idealTree lib
44 silly idealTree `-- [email protected]
44 silly idealTree +-- [email protected]
44 silly idealTree +-- [email protected]
44 silly idealTree +-- [email protected]
44 silly idealTree +-- [email protected]
44 silly idealTree +-- [email protected]
44 silly idealTree +-- [email protected]
44 silly idealTree +-- [email protected]
44 silly idealTree `-- [email protected]
45 silly install generateActionsToTake
46 timing stage:generateActionsToTake Completed in 49ms
47 silly diffTrees action count 9
48 silly diffTrees add [email protected]
49 silly diffTrees add [email protected]
50 silly diffTrees add [email protected]
51 silly diffTrees add [email protected]
52 silly diffTrees add [email protected]
53 silly diffTrees add [email protected]
54 silly diffTrees add [email protected]
55 silly diffTrees add [email protected]
56 silly diffTrees add [email protected]
57 silly decomposeActions action count 72
58 silly decomposeActions fetch [email protected]
59 silly decomposeActions extract [email protected]
60 silly decomposeActions preinstall [email protected]
61 silly decomposeActions build [email protected]
62 silly decomposeActions install [email protected]
63 silly decomposeActions postinstall [email protected]
64 silly decomposeActions finalize [email protected]
65 silly decomposeActions refresh-package-json [email protected]
66 silly decomposeActions fetch [email protected]
67 silly decomposeActions extract [email protected]
68 silly decomposeActions preinstall [email protected]
69 silly decomposeActions build [email protected]
70 silly decomposeActions install [email protected]
71 silly decomposeActions postinstall [email protected]
72 silly decomposeActions finalize [email protected]
73 silly decomposeActions refresh-package-json [email protected]
74 silly decomposeActions fetch [email protected]
75 silly decomposeActions extract [email protected]
76 silly decomposeActions preinstall [email protected]
77 silly decomposeActions build [email protected]
78 silly decomposeActions install [email protected]
79 silly decomposeActions postinstall [email protected]
80 silly decomposeActions finalize [email protected]
81 silly decomposeActions refresh-package-json [email protected]
82 silly decomposeActions fetch [email protected]
83 silly decomposeActions extract [email protected]
84 silly decomposeActions preinstall [email protected]
85 silly decomposeActions build [email protected]
86 silly decomposeActions install [email protected]
87 silly decomposeActions postinstall [email protected]
88 silly decomposeActions finalize [email protected]
89 silly decomposeActions refresh-package-json [email protected]
90 silly decomposeActions fetch [email protected]
91 silly decomposeActions extract [email protected]
92 silly decomposeActions preinstall [email protected]
93 silly decomposeActions build [email protected]
94 silly decomposeActions install [email protected]
95 silly decomposeActions postinstall [email protected]
96 silly decomposeActions finalize [email protected]
97 silly decomposeActions refresh-package-json [email protected]
98 silly decomposeActions fetch [email protected]
99 silly decomposeActions extract [email protected]
100 silly decomposeActions preinstall [email protected]
101 silly decomposeActions build [email protected]
102 silly decomposeActions install [email protected]
103 silly decomposeActions postinstall [email protected]
104 silly decomposeActions finalize [email protected]
105 silly decomposeActions refresh-package-json [email protected]
106 silly decomposeActions fetch [email protected]
107 silly decomposeActions extract [email protected]
108 silly decomposeActions preinstall [email protected]
109 silly decomposeActions build [email protected]
110 silly decomposeActions install [email protected]
111 silly decomposeActions postinstall [email protected]
112 silly decomposeActions finalize [email protected]
113 silly decomposeActions refresh-package-json [email protected]
114 silly decomposeActions fetch [email protected]
115 silly decomposeActions extract [email protected]
116 silly decomposeActions preinstall [email protected]
117 silly decomposeActions build [email protected]
118 silly decomposeActions install [email protected]
119 silly decomposeActions postinstall [email protected]
120 silly decomposeActions finalize [email protected]
121 silly decomposeActions refresh-package-json [email protected]
122 silly decomposeActions fetch [email protected]
123 silly decomposeActions extract [email protected]
124 silly decomposeActions preinstall [email protected]
125 silly decomposeActions build [email protected]
126 silly decomposeActions install [email protected]
127 silly decomposeActions postinstall [email protected]
128 silly decomposeActions finalize [email protected]
129 silly decomposeActions refresh-package-json [email protected]
130 silly install executeActions
131 silly doSerial global-install 72
132 verbose correctMkdir /root/.npm/_locks correctMkdir not in flight; initializing
133 verbose lock using /root/.npm/_locks/staging-3a08f0df5026584d.lock for /usr/local/lib/node_modules/.staging
134 silly doParallel extract 9
135 silly extract [email protected]
136 silly extract [email protected]
137 silly extract [email protected]
138 silly extract [email protected]
139 silly extract [email protected]
140 silly extract [email protected]
141 silly extract [email protected]
142 silly extract [email protected]
143 silly extract [email protected]
144 silly tarball trying [email protected].* by hash: sha512-bAdJv7fBLhWC+/Bls0Oza+mvTaNQtP+1RyhhhvD95pgUJz6XM5IzgmxOkItJ9tkoCiplvAnXI1tNmmUD/eScyA==
145 silly tarball trying [email protected] by hash: sha1-fjL3W0E4EpHQRhHxvxQQmsAGUdc=
146 silly tarball trying raw-socket@* by hash: sha512-OcplcSbIIyEZxW6YFsqbvyrUrqvwFNmA4jhA9ZmMhquLrd9VBzIrFRRZ2qaD98UpyVk/VYJLemO8haECHMmEgQ==
147 silly tarball trying arp-a@^0.5.1 by hash: sha1-moci6q6QP1nPwoGTsAQc9Em90Vo=
148 silly tarball trying bluebird@^3.4.7 by hash: sha512-dhHTWMI7kMx5whMQntl7Vr9C6BvV10lFXDAasnqnrMYhXVCzzk6IO9Fo2L75jXHT07WrOngL1WDXOp+yYS91Yg==
149 silly tarball trying homebridge-plugin-helpers@>=0.1.0 by hash: sha1-asPl6xQ3arP5AlUcSO5MGSmMlJI=
150 silly tarball trying net-ping@^1.2.0 by hash: sha512-ZKxj/kVPKL2RIsV9nR6I8nMT8Pi3k6ciTBKxD/6gd5lga9qcNmlyqNv+dbXqYGBvHsmG9yIpsfajr8X054x2fQ==
151 silly tarball trying ping@^0.1.10 by hash: sha1-/5cGzH+UhUMvIfZ+tx5xlxazUNQ=
152 silly tarball trying homebridge-people-plus@latest by hash: sha1-Ewd5qmoQxvVsV1NDwmjPXdnmOYk=
153 silly tarball no local data for [email protected].*. Extracting by manifest.
154 silly tarball no local data for raw-socket@*. Extracting by manifest.
155 silly tarball no local data for arp-a@^0.5.1. Extracting by manifest.
156 silly tarball no local data for bluebird@^3.4.7. Extracting by manifest.
157 silly tarball no local data for homebridge-plugin-helpers@>=0.1.0. Extracting by manifest.
158 silly tarball no local data for net-ping@^1.2.0. Extracting by manifest.
159 silly tarball no local data for ping@^0.1.10. Extracting by manifest.
160 silly tarball no local data for homebridge-people-plus@latest. Extracting by manifest.
161 http fetch GET 200 https://registry.npmjs.org/nan 305ms (from cache)
162 silly extract [email protected] extracted to /usr/local/lib/node_modules/.staging/q-9a83d309 (483ms)
163 http fetch GET 200 https://registry.npmjs.org/arp-a/-/arp-a-0.5.2.tgz 368ms
164 http fetch GET 200 https://registry.npmjs.org/homebridge-plugin-helpers/-/homebridge-plugin-helpers-0.1.0.tgz 386ms
165 http fetch GET 200 https://registry.npmjs.org/raw-socket/-/raw-socket-1.6.3.tgz 396ms
166 http fetch GET 200 https://registry.npmjs.org/net-ping/-/net-ping-1.2.3.tgz 386ms
167 silly extract homebridge-plugin-helpers@>=0.1.0 extracted to /usr/local/lib/node_modules/.staging/homebridge-plugin-helpers-93757dcc (506ms)
168 silly extract arp-a@^0.5.1 extracted to /usr/local/lib/node_modules/.staging/arp-a-77b127df (523ms)
169 silly extract net-ping@^1.2.0 extracted to /usr/local/lib/node_modules/.staging/net-ping-ea1ccfc6 (542ms)
170 silly extract raw-socket@* extracted to /usr/local/lib/node_modules/.staging/raw-socket-420e8641 (562ms)
171 http fetch GET 200 https://registry.npmjs.org/bluebird/-/bluebird-3.5.2.tgz 458ms
172 silly extract bluebird@^3.4.7 extracted to /usr/local/lib/node_modules/.staging/bluebird-56752b83 (643ms)
173 http fetch GET 200 https://registry.npmjs.org/ping/-/ping-0.1.10.tgz 645ms
174 silly extract ping@^0.1.10 extracted to /usr/local/lib/node_modules/.staging/ping-0a3cc859 (765ms)
175 http fetch GET 200 https://registry.npmjs.org/nan/-/nan-2.10.0.tgz 947ms
176 http fetch GET 200 https://registry.npmjs.org/homebridge-people-plus/-/homebridge-people-plus-0.1.1.tgz 1204ms
177 silly extract homebridge-people-plus@latest extracted to /usr/local/lib/node_modules/.staging/homebridge-people-plus-274af380 (1337ms)
178 silly extract [email protected].* extracted to /usr/local/lib/node_modules/.staging/nan-666b4e91 (1367ms)
179 timing action:extract Completed in 1378ms
180 silly doReverseSerial unbuild 72
181 silly doSerial remove 72
182 silly doSerial move 72
183 silly doSerial finalize 72
184 silly finalize /usr/local/lib/node_modules/homebridge-people-plus/node_modules/nan
185 silly finalize /usr/local/lib/node_modules/homebridge-people-plus/node_modules/q
186 silly finalize /usr/local/lib/node_modules/homebridge-people-plus/node_modules/raw-socket
187 silly finalize /usr/local/lib/node_modules/homebridge-people-plus/node_modules/arp-a
188 silly finalize /usr/local/lib/node_modules/homebridge-people-plus/node_modules/bluebird
189 silly finalize /usr/local/lib/node_modules/homebridge-people-plus/node_modules/homebridge-plugin-helpers
190 silly finalize /usr/local/lib/node_modules/homebridge-people-plus/node_modules/net-ping
191 silly finalize /usr/local/lib/node_modules/homebridge-people-plus/node_modules/ping
192 silly finalize /usr/local/lib/node_modules/homebridge-people-plus
193 timing action:finalize Completed in 102ms
194 silly doParallel refresh-package-json 9
195 silly refresh-package-json /usr/local/lib/node_modules/homebridge-people-plus/node_modules/nan
196 silly refresh-package-json /usr/local/lib/node_modules/homebridge-people-plus/node_modules/q
197 silly refresh-package-json /usr/local/lib/node_modules/homebridge-people-plus/node_modules/raw-socket
198 silly refresh-package-json /usr/local/lib/node_modules/homebridge-people-plus/node_modules/arp-a
199 silly refresh-package-json /usr/local/lib/node_modules/homebridge-people-plus/node_modules/bluebird
200 silly refresh-package-json /usr/local/lib/node_modules/homebridge-people-plus/node_modules/homebridge-plugin-helpers
201 silly refresh-package-json /usr/local/lib/node_modules/homebridge-people-plus/node_modules/net-ping
202 silly refresh-package-json /usr/local/lib/node_modules/homebridge-people-plus/node_modules/ping
203 silly refresh-package-json /usr/local/lib/node_modules/homebridge-people-plus
204 timing action:refresh-package-json Completed in 297ms
205 silly doParallel preinstall 9
206 silly preinstall [email protected]
207 info lifecycle [email protected]~preinstall: [email protected]
208 silly preinstall [email protected]
209 info lifecycle [email protected]~preinstall: [email protected]
210 silly preinstall [email protected]
211 info lifecycle [email protected]~preinstall: [email protected]
212 silly preinstall [email protected]
213 info lifecycle [email protected]~preinstall: [email protected]
214 silly preinstall [email protected]
215 info lifecycle [email protected]~preinstall: [email protected]
216 silly preinstall [email protected]
217 info lifecycle [email protected]~preinstall: [email protected]
218 silly preinstall [email protected]
219 info lifecycle [email protected]~preinstall: [email protected]
220 silly preinstall [email protected]
221 info lifecycle [email protected]~preinstall: [email protected]
222 silly preinstall [email protected]
223 info lifecycle [email protected]~preinstall: [email protected]
224 timing action:preinstall Completed in 13ms
225 silly doSerial build 72
226 silly build [email protected]
227 info linkStuff [email protected]
228 silly linkStuff [email protected] has /usr/local/lib/node_modules/homebridge-people-plus/node_modules as its parent node_modules
229 silly linkStuff [email protected] is part of a global install
230 silly linkStuff [email protected] is installed into a global node_modules
231 silly build [email protected]
232 info linkStuff [email protected]
233 silly linkStuff [email protected] has /usr/local/lib/node_modules/homebridge-people-plus/node_modules as its parent node_modules
234 silly linkStuff [email protected] is part of a global install
235 silly linkStuff [email protected] is installed into a global node_modules
236 silly build [email protected]
237 info linkStuff [email protected]
238 silly linkStuff [email protected] has /usr/local/lib/node_modules/homebridge-people-plus/node_modules as its parent node_modules
239 silly linkStuff [email protected] is part of a global install
240 silly linkStuff [email protected] is installed into a global node_modules
241 silly build [email protected]
242 info linkStuff [email protected]
243 silly linkStuff [email protected] has /usr/local/lib/node_modules/homebridge-people-plus/node_modules as its parent node_modules
244 silly linkStuff [email protected] is part of a global install
245 silly linkStuff [email protected] is installed into a global node_modules
246 silly build [email protected]
247 info linkStuff [email protected]
248 silly linkStuff [email protected] has /usr/local/lib/node_modules/homebridge-people-plus/node_modules as its parent node_modules
249 silly linkStuff [email protected] is part of a global install
250 silly linkStuff [email protected] is installed into a global node_modules
251 silly build [email protected]
252 info linkStuff [email protected]
253 silly linkStuff [email protected] has /usr/local/lib/node_modules/homebridge-people-plus/node_modules as its parent node_modules
254 silly linkStuff [email protected] is part of a global install
255 silly linkStuff [email protected] is installed into a global node_modules
256 silly build [email protected]
257 info linkStuff [email protected]
258 silly linkStuff [email protected] has /usr/local/lib/node_modules/homebridge-people-plus/node_modules as its parent node_modules
259 silly linkStuff [email protected] is part of a global install
260 silly linkStuff [email protected] is installed into a global node_modules
261 silly build [email protected]
262 info linkStuff [email protected]
263 silly linkStuff [email protected] has /usr/local/lib/node_modules/homebridge-people-plus/node_modules as its parent node_modules
264 silly linkStuff [email protected] is part of a global install
265 silly linkStuff [email protected] is installed into a global node_modules
266 silly build [email protected]
267 info linkStuff [email protected]
268 silly linkStuff [email protected] has /usr/local/lib/node_modules as its parent node_modules
269 silly linkStuff [email protected] is part of a global install
270 silly linkStuff [email protected] is installed into a global node_modules
271 silly linkStuff [email protected] is installed into the top-level global node_modules
272 timing action:build Completed in 15ms
273 silly doSerial global-link 72
274 silly doParallel update-linked 0
275 silly doSerial install 72
276 silly install [email protected]
277 info lifecycle [email protected]~install: [email protected]
278 silly install [email protected]
279 info lifecycle [email protected]~install: [email protected]
280 silly install [email protected]
281 info lifecycle [email protected]~install: [email protected]
282 verbose lifecycle [email protected]~install: unsafe-perm in lifecycle false
283 verbose lifecycle [email protected]~install: PATH: /usr/local/lib/node_modules/npm/node_modules/npm-lifecycle/node-gyp-bin:/usr/local/lib/node_modules/homebridge-people-plus/node_modules/raw-socket/node_modules/.bin:/usr/local/lib/node_modules/homebridge-people-plus/node_modules/.bin:/usr/local/lib/node_modules/.bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
284 verbose lifecycle [email protected]~install: CWD: /usr/local/lib/node_modules/homebridge-people-plus/node_modules/raw-socket
285 silly lifecycle [email protected]~install: Args: [ '-c', 'node-gyp rebuild' ]
286 silly lifecycle [email protected]~install: Returned: code: 1 signal: null
287 info lifecycle [email protected]~install: Failed to exec install script
288 timing action:install Completed in 1695ms
289 verbose unlock done using /root/.npm/_locks/staging-3a08f0df5026584d.lock for /usr/local/lib/node_modules/.staging
290 timing stage:rollbackFailedOptional Completed in 121ms
291 timing stage:runTopLevelLifecycles Completed in 7417ms
292 verbose stack Error: [email protected] install: `node-gyp rebuild`
292 verbose stack Exit status 1
292 verbose stack at EventEmitter.<anonymous> (/usr/local/lib/node_modules/npm/node_modules/npm-lifecycle/index.js:301:16)
292 verbose stack at emitTwo (events.js:126:13)
292 verbose stack at EventEmitter.emit (events.js:214:7)
292 verbose stack at ChildProcess.<anonymous> (/usr/local/lib/node_modules/npm/node_modules/npm-lifecycle/lib/spawn.js:55:14)
292 verbose stack at emitTwo (events.js:126:13)
292 verbose stack at ChildProcess.emit (events.js:214:7)
292 verbose stack at maybeClose (internal/child_process.js:915:16)
292 verbose stack at Process.ChildProcess._handle.onexit (internal/child_process.js:209:5)
293 verbose pkgid [email protected]
294 verbose cwd /root
295 verbose Linux 4.14.71-v7+
296 verbose argv "/usr/local/bin/node" "/usr/local/bin/npm" "install" "-g" "homebridge-people-plus"
297 verbose node v8.12.0
298 verbose npm v6.4.1
299 error code ELIFECYCLE
300 error errno 1
301 error [email protected] install: `node-gyp rebuild`
301 error Exit status 1
302 error Failed at the [email protected] install script.
302 error This is probably not a problem with npm. There is likely additional logging output above.
303 verbose exit [ 1, true ]Alles anzeigenDas ist einfach: der User homebridge darf sudo nicht benutzen. Dem kann aber abgeholfen werden, indem er in der Datei /etc/sudoers eingetragen wird.
Mach das:
sudo nano /etc/sudoers.d/homebridge
Eine leerer Editor ist das Ergebnis, das die Datei /etc/sudoers.d/homebridge noch nicht existiert (wahrscheinlich nicht).
Dort trägst du jetzt ein:
homebridge ALL=(root) SETENV:NOPASSWD: /usr/local/bin/ps4-waker standby
speicherst den Schmodder ab und versuchst es nochmal.
Die obige Änderung der Rechte des Users homebridge bedeutet nicht, dass der jetzt für alles sudo-Rechte hat. Es bedeutet, dass er sudo mit diesem einen Befehl benutzen kann. Man kann natürlich die Rechte auch für alle Befehle des Systems verteilen. Ich rate ab, aber sei's drum: homebridge ALL=(ALL:ALL) ALL). Ich empfehle aber, dem User homebridge nur die sudo-Rechte für die Befehle zu geben, die er auch wirklich braucht.
Bei mir sieht das so aus (vor allem für das Plugin homebridge-config-ui-x):
homebridge ALL=(root) SETENV:NOPASSWD: /usr/bin/npm, /bin/systemctl restart homebridge, /bin/journalctl, /usr/bin/node /usr/lib/node_modules/homebridge-config-ui-x/node_modules/nsp/bin/nsp check
In meiner Config darf der User homebridge beispielsweise die Homebridge restarten, aber nicht etwa stoppen. Mit der PS4 darf der User homebridge nix anstellen, was ursächlich daran liegt, dass ich über keine PS4 verfüge
Testen kann man das prima auf der Shell, indem man dort als User homebridge die Befehle eingibt:
sudo /usr/local/bin/ps4-waker standby (sollte nun funktionieren)
sudo ls (sollte nicht funktionieren, weil's ein Passwort will)
Schlusswort: warum sollte der User homebridge keine vollen Rechte haben? Ich finde, es sollte drei Arten von Benutzern auf einem System geben: den totalen Master (root), seinen Hilfssheriff (pi) und die Luser, also jene, die keinen speziellen oder nur sehr wenige spezielle Rechte haben. Meiner Meinung nach sollten so wenig Services wie möglich als root gestartet werden, wobei sich das oft nicht umgehen lässt. Im Fall von Homebridge aber schon.
Etwas nicht als root laufen zu lassen, ist immer sicherer, als es doch zu tun. Lässt man Homebrigde als root laufen, so hat der Prozess homebridge die gleichen Rechte wie root. Echte Cracks, die deinen Node.js-Server überfallen können, können dann mit deinem System über diesen Server machen was sie wollen, weil sie nun einen Prozess unter Kontrolle haben, der alles auf dem System anstellen darf. Bist du dir völlig sicher, dass deine Freundin oder dein Freund oder deine achtjährige Tochter, das Wunderkind, nicht über diese Fähigkeiten verfügen??? Nur weil ich paranoid bin, heißt das noch lange nicht, dass sie nicht hinter mir her sind.
Konfiguration der config.json per App? Verboten. Konfiguration der config.json per Webinterface? Verboten. Homebridge stoppen, Raspi runterfahren? Verboten, verboten, verboten.
Liebe Freunde, die ihre Installation unter root oder pi betreiben: kein Grund zur Schnappatmung. Lasst es so. Aber wägt das Risiko ab. Da eure Homebrigde (hoffentlich) von draußen nicht ohne weiteres zu erreichen ist, ist sie ja hinreichend sicher. Aber Unix/Linux-state-of-the-art ist es nun mal nicht. Falls ihr es euch zutraut: ändert es. Aber man sollte schon hinreichend sicher auf dem System sein. Alles andere ist nur frustrierend.
Viel Erfolg.Stefan
wow, danke für die tolle Anleitung.
ich probiere hier seit einer gefühlten Ewigkeit rum, das PS4 Ding ans laufen zu bekommen und wende hier wild kürzlich "erlerntes", gefährliches halbwissen an.
Meine Homebridge läuft natürlich unter dem user pi. Also genau so, wie man es nicht machen soll, aber nun gut.
Folgendes hab ich nun versucht:
sudo nano /etc/sudoers.d/pi
(ja, du hast gesagt, dass man das nich machen soll. ich wollte aber erstmal überhaupt schauen, obs klappt)
pi ALL=(ALL:ALL) ALLUnd anschliessend hab ich die config.json im Verzeichnis /home/pi/.homebridge editiert und folgendes fabriziert:
{
"platform": "cmdSwitch2",
"name": "CMD Switch",
"switches": [
{
"name": "Playstation",
"on_cmd": "node /usr/local/lib/node_modules/ps4-waker/bin/cmd.js -c /root/pi/.ps4-wake.credentials.json",
"off_cmd": "node /usr/local/lib/node_modules/ps4-waker/bin/cmd.js -c /root/.ps4-wake.credentials.json standby",
"state_cmd": "node /usr/local/lib/node_modules/ps4-waker/bin/cmd.js -c /root.ps4-wake.credentials.json search | grep -i '200 Ok'",
"polling": false,
"interval": 5,
"manufacturer": "Sony Corporation"
}
]
},Ergebnis: Es funktioniert. AAAAABer: Ich würde gerne verstehen, was ich nun in die sudoers.d/pi eintragen muss, damit der user pi keine kompletten root rechte hat, sondern nur für die funktionen verwendet werden darf, die in diesem falle benötigt werden.
Wäre toll wenn du mir da einmal auf die sprünge helfen kannst. Hab da jetzt echt schon ne ewigkeit rumgefriemelt... nur halt ohne erfolg
perfekt. Ich danke euch beiden
Moin Leute,
ich habe gerade in einem Anfall von geistiger Umnachtung versehentlich meine Homebridge aus Home entfernt.
"Macht ja nüscht" dachte ich mir. "Kannste ja neu hinzufügen" - Aber Pustekuchen.
Das Ding taucht nicht mehr auf, wenn ich in Home oben auf das + tappe.
Wenn ich den QR Code aus dem Terminal scanne teilt home mir mit, dass ich das Gerät bereits hinzugefügt habe und es zurücksetzen muss.
Wie kriege ich das jetzt gefixt?
Das verwendet die Mac-Adresse und nicht die IP bzw. den Namen.
Würde eher auf homebridge-people setzten und dann mit Namen oder IP arbeiten und nicht mit der Mac-Adresse wie es homebridge-people-plus machen will. Was hast du denn überhaupt vor, so dass du 2x ein solchen Plugin nutzen willst?
Wir haben mit mehreren Leuten einen gemeinsamen Proberaum, wo des öfteren mal Dinge "verschwinden".
Und nein, ich möchte lieber mit Mac Adressen arbeiten. Das People Plugin war zum testen da. Als ich vom People-Plus erfuhr wollte ich das halt lieber nutzen.
Ich verzweifle an der Installation vom people-plus plugin.
Sofern ich das Teil via "sudo npm install -g homebridge-people-plus" installieren möchte, erhalte ich folgenden Output:
> [email protected] install /usr/local/lib/node_modules/homebridge-people-plus/node_modules/raw-socket
> node-gyp rebuild
gyp WARN EACCES user "root" does not have permission to access the dev dir "/root/.node-gyp/8.12.0"
gyp WARN EACCES attempting to reinstall using temporary dev dir "/usr/local/lib/node_modules/homebridge-people-plus/node_modules/raw-socket/.node-gyp"
gyp WARN install got an error, rolling back install
gyp WARN install got an error, rolling back install
gyp ERR! configure error
gyp ERR! stack Error: EACCES: permission denied, mkdir '/usr/local/lib/node_modules/homebridge-people-plus/node_modules/raw-socket/.node-gyp'
gyp ERR! System Linux 4.14.71-v7+
gyp ERR! command "/usr/local/bin/node" "/usr/local/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "rebuild"
gyp ERR! cwd /usr/local/lib/node_modules/homebridge-people-plus/node_modules/raw-socket
gyp ERR! node -v v8.12.0
gyp ERR! node-gyp -v v3.8.0
gyp ERR! not ok
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! [email protected] install: `node-gyp rebuild`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the [email protected] install script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm ERR! A complete log of this run can be found in:
npm ERR! /root/.npm/_logs/2018-10-30T18_59_23_110Z-debug.logNach einigem Hin und Her nutzte ich dann letztlich "sudo npm install --unsafe-perm homebridge-people-plus -g". Die Installation klappte. Nach dem Anpassen der config.json und Hinzufügen der Demo accesory erhalte ich beim starten der homebridge folgende Meldung:
[Glavin's iPhone] Initializing PeoplePlus accessory...
/usr/local/lib/node_modules/homebridge-people-plus/node_modules/raw-socket/index.js:47
this.wrap = new raw.SocketWrap (
^
Error: Operation not permitted
at new Socket (/usr/local/lib/node_modules/homebridge-people-plus/node_modules/raw-socket/index.js:47:14)
at Object.exports.createSocket (/usr/local/lib/node_modules/homebridge-people-plus/node_modules/raw-socket/index.js:202:9)
at Session.getSocket (/usr/local/lib/node_modules/homebridge-people-plus/node_modules/net-ping/index.js:147:20)
at new Session (/usr/local/lib/node_modules/homebridge-people-plus/node_modules/net-ping/index.js:101:7)
at Object.exports.createSession (/usr/local/lib/node_modules/homebridge-people-plus/node_modules/net-ping/index.js:545:9)
at new NetworkObserver (/usr/local/lib/node_modules/homebridge-people-plus/network.js:13:29)
at Function.get net [as net] (/usr/local/lib/node_modules/homebridge-people-plus/index.js:82:25)
at PeoplePlusAccessory.get net [as net] (/usr/local/lib/node_modules/homebridge-people-plus/index.js:88:33)
at PeoplePlusAccessory.setupDeviceObserver (/usr/local/lib/node_modules/homebridge-people-plus/index.js:67:25)
at new PeoplePlusAccessory (/usr/local/lib/node_modules/homebridge-people-plus/index.js:31:14)
at new <anonymous> (/usr/local/lib/node_modules/homebridge-people-plus/node_modules/homebridge-plugin-helpers/index.js:19:11)
at Server._loadAccessories (/usr/local/lib/node_modules/homebridge/lib/server.js:297:29)
at Server.run (/usr/local/lib/node_modules/homebridge/lib/server.js:87:38)
at module.exports (/usr/local/lib/node_modules/homebridge/lib/cli.js:45:10)
at Object.<anonymous> (/usr/local/lib/node_modules/homebridge/bin/homebridge:17:22)
at Module._compile (module.js:653:30)
at Object.Module._extensions..js (module.js:664:10)
at Module.load (module.js:566:32)
at tryModuleLoad (module.js:506:12)
at Function.Module._load (module.js:498:3)
at Function.Module.runMain (module.js:694:10)
at startup (bootstrap_node.js:204:16)was ist da los? das normale people plugin funktioniert soweit. Wäre toll wenn mir jemand helfen könnte.