homebridge/homekit

Begonnen von justme1968, 01 Februar 2016, 16:16:37

Vorheriges Thema - Nächstes Thema

Sky

#2910
Hallo ,

wie kann ich auf der Konsole sehen wer Berechtigter eines Verzeichniss ist ?

Habe mal in /home/pi/.npm/_logs geschaut , dort steht unter anderem
289 error Error: EACCES: permission denied, access '/usr/local/lib/node_modules/homebridge-camera-ffmpeg'
Habe diese unten mal angehängt .

Vielleicht liegt dort mein Problem ?
Manche Dateien unter /usr/lib/node_modules/homebridge haben als Besitzer "nobody pi "
Ich weiß leider nicht ob das richtig ist ,weil ohne das "homebridge-camera-plugin" in meiner config.json die Homebridge funktioniert .


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-camera-ffmpeg' ]
2 info using npm@6.1.0
3 info using node@v6.10.0
4 verbose npm-session 6d88913d1647eb96
5 silly install loadCurrentTree
6 silly install readGlobalPackageData
7 http fetch GET 304 https://registry.npmjs.org/homebridge-camera-ffmpeg 873ms (from cache)
8 silly pacote tag manifest for homebridge-camera-ffmpeg@latest fetched in 1142ms
9 timing stage:loadCurrentTree Completed in 4790ms
10 silly install loadIdealTree
11 silly install cloneCurrentTreeToIdealTree
12 timing stage:loadIdealTree:cloneCurrentTree Completed in 16ms
13 silly install loadShrinkwrap
14 timing stage:loadIdealTree:loadShrinkwrap Completed in 382ms
15 silly install loadAllDepsIntoIdealTree
16 silly resolveWithNewModule homebridge-camera-ffmpeg@0.1.8 checking installable status
17 silly removeObsoleteDep removing homebridge-camera-ffmpeg@0.1.8 from the tree as its been replaced by a newer version or is no longer required
18 silly removeObsoleteDep removing debug@2.6.9 from the tree as its been replaced by a newer version or is no longer required
19 silly removeObsoleteDep removing ms@2.0.0 from the tree as its been replaced by a newer version or is no longer required
20 silly removeObsoleteDep removing googleapis@18.0.0 from the tree as its been replaced by a newer version or is no longer required
21 silly removeObsoleteDep removing async@2.1.5 from the tree as its been replaced by a newer version or is no longer required
22 silly removeObsoleteDep removing lodash@4.17.10 from the tree as its been replaced by a newer version or is no longer required
23 silly removeObsoleteDep removing google-auth-library@0.10.0 from the tree as its been replaced by a newer version or is no longer required
24 silly removeObsoleteDep removing gtoken@1.2.3 from the tree as its been replaced by a newer version or is no longer required
25 silly removeObsoleteDep removing google-p12-pem@0.1.2 from the tree as its been replaced by a newer version or is no longer required
26 silly removeObsoleteDep removing node-forge@0.7.5 from the tree as its been replaced by a newer version or is no longer required
27 silly removeObsoleteDep removing jws@3.1.5 from the tree as its been replaced by a newer version or is no longer required
28 silly removeObsoleteDep removing jwa@1.1.6 from the tree as its been replaced by a newer version or is no longer required
29 silly removeObsoleteDep removing buffer-equal-constant-time@1.0.1 from the tree as its been replaced by a newer version or is no longer required
30 silly removeObsoleteDep removing ecdsa-sig-formatter@1.0.10 from the tree as its been replaced by a newer version or is no longer required
31 silly removeObsoleteDep removing safe-buffer@5.1.2 from the tree as its been replaced by a newer version or is no longer required
32 silly removeObsoleteDep removing mime@1.6.0 from the tree as its been replaced by a newer version or is no longer required
33 silly removeObsoleteDep removing request@2.87.0 from the tree as its been replaced by a newer version or is no longer required
34 silly removeObsoleteDep removing aws-sign2@0.7.0 from the tree as its been replaced by a newer version or is no longer required
35 silly removeObsoleteDep removing aws4@1.7.0 from the tree as its been replaced by a newer version or is no longer required
36 silly removeObsoleteDep removing caseless@0.12.0 from the tree as its been replaced by a newer version or is no longer required
37 silly removeObsoleteDep removing combined-stream@1.0.6 from the tree as its been replaced by a newer version or is no longer required
38 silly removeObsoleteDep removing delayed-stream@1.0.0 from the tree as its been replaced by a newer version or is no longer required
39 silly removeObsoleteDep removing extend@3.0.1 from the tree as its been replaced by a newer version or is no longer required
40 silly removeObsoleteDep removing forever-agent@0.6.1 from the tree as its been replaced by a newer version or is no longer required
41 silly removeObsoleteDep removing form-data@2.3.2 from the tree as its been replaced by a newer version or is no longer required
42 silly removeObsoleteDep removing asynckit@0.4.0 from the tree as its been replaced by a newer version or is no longer required
43 silly removeObsoleteDep removing mime-types@2.1.18 from the tree as its been replaced by a newer version or is no longer required
44 silly removeObsoleteDep removing mime-db@1.33.0 from the tree as its been replaced by a newer version or is no longer required
45 silly removeObsoleteDep removing har-validator@5.0.3 from the tree as its been replaced by a newer version or is no longer required
46 silly removeObsoleteDep removing ajv@5.5.2 from the tree as its been replaced by a newer version or is no longer required
47 silly removeObsoleteDep removing co@4.6.0 from the tree as its been replaced by a newer version or is no longer required
48 silly removeObsoleteDep removing fast-deep-equal@1.1.0 from the tree as its been replaced by a newer version or is no longer required
49 silly removeObsoleteDep removing fast-json-stable-stringify@2.0.0 from the tree as its been replaced by a newer version or is no longer required
50 silly removeObsoleteDep removing json-schema-traverse@0.3.1 from the tree as its been replaced by a newer version or is no longer required
51 silly removeObsoleteDep removing har-schema@2.0.0 from the tree as its been replaced by a newer version or is no longer required
52 silly removeObsoleteDep removing http-signature@1.2.0 from the tree as its been replaced by a newer version or is no longer required
53 silly removeObsoleteDep removing assert-plus@1.0.0 from the tree as its been replaced by a newer version or is no longer required
54 silly removeObsoleteDep removing jsprim@1.4.1 from the tree as its been replaced by a newer version or is no longer required
55 silly removeObsoleteDep removing extsprintf@1.3.0 from the tree as its been replaced by a newer version or is no longer required
56 silly removeObsoleteDep removing json-schema@0.2.3 from the tree as its been replaced by a newer version or is no longer required
57 silly removeObsoleteDep removing verror@1.10.0 from the tree as its been replaced by a newer version or is no longer required
58 silly removeObsoleteDep removing core-util-is@1.0.2 from the tree as its been replaced by a newer version or is no longer required
59 silly removeObsoleteDep removing sshpk@1.14.2 from the tree as its been replaced by a newer version or is no longer required
60 silly removeObsoleteDep removing asn1@0.2.3 from the tree as its been replaced by a newer version or is no longer required
61 silly removeObsoleteDep removing bcrypt-pbkdf@1.0.1 from the tree as its been replaced by a newer version or is no longer required
62 silly removeObsoleteDep removing tweetnacl@0.14.5 from the tree as its been replaced by a newer version or is no longer required
63 silly removeObsoleteDep removing dashdash@1.14.1 from the tree as its been replaced by a newer version or is no longer required
64 silly removeObsoleteDep removing ecc-jsbn@0.1.1 from the tree as its been replaced by a newer version or is no longer required
65 silly removeObsoleteDep removing jsbn@0.1.1 from the tree as its been replaced by a newer version or is no longer required
66 silly removeObsoleteDep removing getpass@0.1.7 from the tree as its been replaced by a newer version or is no longer required
67 silly removeObsoleteDep removing safer-buffer@2.1.2 from the tree as its been replaced by a newer version or is no longer required
68 silly removeObsoleteDep removing is-typedarray@1.0.0 from the tree as its been replaced by a newer version or is no longer required
69 silly removeObsoleteDep removing isstream@0.1.2 from the tree as its been replaced by a newer version or is no longer required
70 silly removeObsoleteDep removing json-stringify-safe@5.0.1 from the tree as its been replaced by a newer version or is no longer required
71 silly removeObsoleteDep removing oauth-sign@0.8.2 from the tree as its been replaced by a newer version or is no longer required
72 silly removeObsoleteDep removing performance-now@2.1.0 from the tree as its been replaced by a newer version or is no longer required
73 silly removeObsoleteDep removing qs@6.5.2 from the tree as its been replaced by a newer version or is no longer required
74 silly removeObsoleteDep removing tough-cookie@2.3.4 from the tree as its been replaced by a newer version or is no longer required
75 silly removeObsoleteDep removing punycode@1.4.1 from the tree as its been replaced by a newer version or is no longer required
76 silly removeObsoleteDep removing tunnel-agent@0.6.0 from the tree as its been replaced by a newer version or is no longer required
77 silly removeObsoleteDep removing uuid@3.2.1 from the tree as its been replaced by a newer version or is no longer required
78 silly removeObsoleteDep removing lodash.noop@3.0.1 from the tree as its been replaced by a newer version or is no longer required
79 silly removeObsoleteDep removing string-template@1.0.0 from the tree as its been replaced by a newer version or is no longer required
80 silly removeObsoleteDep removing ip@1.1.5 from the tree as its been replaced by a newer version or is no longer required
81 http fetch GET 304 https://registry.npmjs.org/ip 301ms (from cache)
82 silly pacote range manifest for ip@^1.1.3 fetched in 327ms
83 silly resolveWithNewModule ip@1.1.5 checking installable status
84 http fetch GET 304 https://registry.npmjs.org/debug 525ms (from cache)
85 http fetch GET 304 https://registry.npmjs.org/google-auth-library 567ms (from cache)
86 http fetch GET 304 https://registry.npmjs.org/googleapis 579ms (from cache)
87 silly pacote range manifest for debug@^2.2.0 fetched in 635ms
88 silly resolveWithNewModule debug@2.6.9 checking installable status
89 silly pacote range manifest for google-auth-library@^0.10.0 fetched in 667ms
90 silly resolveWithNewModule google-auth-library@0.10.0 checking installable status
91 silly pacote range manifest for googleapis@^18.0.0 fetched in 663ms
92 silly resolveWithNewModule googleapis@18.0.0 checking installable status
93 http fetch GET 304 https://registry.npmjs.org/ms 130ms (from cache)
94 silly pacote version manifest for ms@2.0.0 fetched in 145ms
95 silly resolveWithNewModule ms@2.0.0 checking installable status
96 http fetch GET 304 https://registry.npmjs.org/lodash.noop 311ms (from cache)
97 http fetch GET 304 https://registry.npmjs.org/jws 308ms (from cache)
98 silly pacote range manifest for lodash.noop@^3.0.1 fetched in 350ms
99 silly resolveWithNewModule lodash.noop@3.0.1 checking installable status
100 silly pacote range manifest for jws@^3.1.4 fetched in 351ms
101 silly resolveWithNewModule jws@3.1.5 checking installable status
102 http fetch GET 304 https://registry.npmjs.org/request 356ms (from cache)
103 silly pacote range manifest for request@^2.74.0 fetched in 398ms
104 silly resolveWithNewModule request@2.87.0 checking installable status
105 http fetch GET 304 https://registry.npmjs.org/gtoken 421ms (from cache)
106 silly pacote range manifest for gtoken@^1.2.1 fetched in 434ms
107 silly resolveWithNewModule gtoken@1.2.3 checking installable status
108 http fetch GET 304 https://registry.npmjs.org/google-p12-pem 157ms (from cache)
109 http fetch GET 304 https://registry.npmjs.org/mime 169ms (from cache)
110 silly pacote range manifest for google-p12-pem@^0.1.0 fetched in 188ms
111 silly resolveWithNewModule google-p12-pem@0.1.2 checking installable status
112 silly pacote range manifest for mime@^1.4.1 fetched in 195ms
113 silly resolveWithNewModule mime@1.6.0 checking installable status
114 http fetch GET 304 https://registry.npmjs.org/node-forge 119ms (from cache)
115 silly pacote range manifest for node-forge@^0.7.1 fetched in 149ms
116 silly resolveWithNewModule node-forge@0.7.5 checking installable status
117 http fetch GET 304 https://registry.npmjs.org/safe-buffer 205ms (from cache)
118 http fetch GET 304 https://registry.npmjs.org/jwa 212ms (from cache)
119 silly pacote range manifest for safe-buffer@^5.0.1 fetched in 219ms
120 silly resolveWithNewModule safe-buffer@5.1.2 checking installable status
121 silly pacote range manifest for jwa@^1.1.5 fetched in 242ms
122 silly resolveWithNewModule jwa@1.1.6 checking installable status
123 http fetch GET 304 https://registry.npmjs.org/ecdsa-sig-formatter 118ms (from cache)
124 silly pacote version manifest for ecdsa-sig-formatter@1.0.10 fetched in 131ms
125 silly resolveWithNewModule ecdsa-sig-formatter@1.0.10 checking installable status
126 http fetch GET 304 https://registry.npmjs.org/buffer-equal-constant-time 1166ms (from cache)
127 silly pacote version manifest for buffer-equal-constant-time@1.0.1 fetched in 1178ms
128 silly resolveWithNewModule buffer-equal-constant-time@1.0.1 checking installable status
129 http fetch GET 304 https://registry.npmjs.org/aws-sign2 611ms (from cache)
130 http fetch GET 304 https://registry.npmjs.org/caseless 621ms (from cache)
131 http fetch GET 304 https://registry.npmjs.org/aws4 628ms (from cache)
132 http fetch GET 304 https://registry.npmjs.org/combined-stream 649ms (from cache)
133 http fetch GET 304 https://registry.npmjs.org/har-validator 656ms (from cache)
134 silly pacote range manifest for aws-sign2@~0.7.0 fetched in 691ms
135 silly resolveWithNewModule aws-sign2@0.7.0 checking installable status
136 silly pacote range manifest for aws4@^1.6.0 fetched in 701ms
137 silly resolveWithNewModule aws4@1.7.0 checking installable status
138 silly pacote range manifest for caseless@~0.12.0 fetched in 705ms
139 silly resolveWithNewModule caseless@0.12.0 checking installable status
140 silly pacote range manifest for combined-stream@~1.0.5 fetched in 736ms
141 silly resolveWithNewModule combined-stream@1.0.6 checking installable status
142 silly pacote range manifest for har-validator@~5.0.3 fetched in 743ms
143 silly resolveWithNewModule har-validator@5.0.3 checking installable status
144 http fetch GET 304 https://registry.npmjs.org/extend 949ms (from cache)
145 http fetch GET 304 https://registry.npmjs.org/form-data 947ms (from cache)
146 http fetch GET 304 https://registry.npmjs.org/http-signature 947ms (from cache)
147 silly pacote range manifest for extend@~3.0.1 fetched in 1052ms
148 silly resolveWithNewModule extend@3.0.1 checking installable status
149 silly pacote range manifest for form-data@~2.3.1 fetched in 1056ms
150 silly resolveWithNewModule form-data@2.3.2 checking installable status
151 silly pacote range manifest for http-signature@~1.2.0 fetched in 1064ms
152 silly resolveWithNewModule http-signature@1.2.0 checking installable status
153 http fetch GET 304 https://registry.npmjs.org/forever-agent 1083ms (from cache)
154 silly pacote range manifest for forever-agent@~0.6.1 fetched in 1160ms
155 silly resolveWithNewModule forever-agent@0.6.1 checking installable status
156 http fetch GET 304 https://registry.npmjs.org/is-typedarray 1449ms (from cache)
157 http fetch GET 304 https://registry.npmjs.org/isstream 755ms (from cache)
158 http fetch GET 304 https://registry.npmjs.org/json-stringify-safe 755ms (from cache)
159 http fetch GET 304 https://registry.npmjs.org/mime-types 774ms (from cache)
160 http fetch GET 304 https://registry.npmjs.org/oauth-sign 775ms (from cache)
161 silly pacote range manifest for is-typedarray@~1.0.0 fetched in 1511ms
162 silly resolveWithNewModule is-typedarray@1.0.0 checking installable status
163 silly pacote range manifest for isstream@~0.1.2 fetched in 841ms
164 silly resolveWithNewModule isstream@0.1.2 checking installable status
165 silly pacote range manifest for json-stringify-safe@~5.0.1 fetched in 846ms
166 silly resolveWithNewModule json-stringify-safe@5.0.1 checking installable status
167 silly pacote range manifest for mime-types@~2.1.17 fetched in 864ms
168 silly resolveWithNewModule mime-types@2.1.18 checking installable status
169 http fetch GET 304 https://registry.npmjs.org/performance-now 820ms (from cache)
170 silly pacote range manifest for oauth-sign@~0.8.2 fetched in 868ms
171 silly resolveWithNewModule oauth-sign@0.8.2 checking installable status
172 http fetch GET 304 https://registry.npmjs.org/qs 558ms (from cache)
173 http fetch GET 304 https://registry.npmjs.org/tough-cookie 563ms (from cache)
174 silly pacote range manifest for performance-now@^2.1.0 fetched in 897ms
175 silly resolveWithNewModule performance-now@2.1.0 checking installable status
176 http fetch GET 304 https://registry.npmjs.org/tunnel-agent 562ms (from cache)
177 silly pacote range manifest for qs@~6.5.1 fetched in 622ms
178 silly resolveWithNewModule qs@6.5.2 checking installable status
179 silly pacote range manifest for tough-cookie@~2.3.3 fetched in 626ms
180 silly resolveWithNewModule tough-cookie@2.3.4 checking installable status
181 http fetch GET 304 https://registry.npmjs.org/uuid 528ms (from cache)
182 silly pacote range manifest for tunnel-agent@^0.6.0 fetched in 597ms
183 silly resolveWithNewModule tunnel-agent@0.6.0 checking installable status
184 silly pacote range manifest for uuid@^3.1.0 fetched in 559ms
185 silly resolveWithNewModule uuid@3.2.1 checking installable status
186 http fetch GET 304 https://registry.npmjs.org/delayed-stream 227ms (from cache)
187 silly pacote range manifest for delayed-stream@~1.0.0 fetched in 239ms
188 silly resolveWithNewModule delayed-stream@1.0.0 checking installable status
189 http fetch GET 304 https://registry.npmjs.org/asynckit 133ms (from cache)
190 silly pacote range manifest for asynckit@^0.4.0 fetched in 143ms
191 silly resolveWithNewModule asynckit@0.4.0 checking installable status
192 http fetch GET 304 https://registry.npmjs.org/mime-db 119ms (from cache)
193 silly pacote range manifest for mime-db@~1.33.0 fetched in 135ms
194 silly resolveWithNewModule mime-db@1.33.0 checking installable status
195 http fetch GET 304 https://registry.npmjs.org/ajv 151ms (from cache)
196 silly pacote range manifest for ajv@^5.1.0 fetched in 212ms
197 silly resolveWithNewModule ajv@5.5.2 checking installable status
198 http fetch GET 304 https://registry.npmjs.org/har-schema 220ms (from cache)
199 silly pacote range manifest for har-schema@^2.0.0 fetched in 257ms
200 silly resolveWithNewModule har-schema@2.0.0 checking installable status
201 http fetch GET 304 https://registry.npmjs.org/co 239ms (from cache)
202 http fetch GET 304 https://registry.npmjs.org/fast-deep-equal 250ms (from cache)
203 http fetch GET 304 https://registry.npmjs.org/json-schema-traverse 266ms (from cache)
204 silly pacote range manifest for co@^4.6.0 fetched in 283ms
205 silly resolveWithNewModule co@4.6.0 checking installable status
206 silly pacote range manifest for fast-deep-equal@^1.0.0 fetched in 288ms
207 silly resolveWithNewModule fast-deep-equal@1.1.0 checking installable status
208 silly pacote range manifest for json-schema-traverse@^0.3.0 fetched in 287ms
209 silly resolveWithNewModule json-schema-traverse@0.3.1 checking installable status
210 http fetch GET 304 https://registry.npmjs.org/fast-json-stable-stringify 374ms (from cache)
211 silly pacote range manifest for fast-json-stable-stringify@^2.0.0 fetched in 390ms
212 silly resolveWithNewModule fast-json-stable-stringify@2.0.0 checking installable status
213 http fetch GET 304 https://registry.npmjs.org/jsprim 126ms (from cache)
214 http fetch GET 304 https://registry.npmjs.org/assert-plus 136ms (from cache)
215 silly pacote range manifest for jsprim@^1.2.2 fetched in 142ms
216 silly resolveWithNewModule jsprim@1.4.1 checking installable status
217 silly pacote range manifest for assert-plus@^1.0.0 fetched in 149ms
218 silly resolveWithNewModule assert-plus@1.0.0 checking installable status
219 http fetch GET 304 https://registry.npmjs.org/sshpk 216ms (from cache)
220 silly pacote range manifest for sshpk@^1.7.0 fetched in 230ms
221 silly resolveWithNewModule sshpk@1.14.2 checking installable status
222 http fetch GET 304 https://registry.npmjs.org/extsprintf 194ms (from cache)
223 http fetch GET 304 https://registry.npmjs.org/json-schema 196ms (from cache)
224 silly pacote version manifest for extsprintf@1.3.0 fetched in 208ms
225 silly resolveWithNewModule extsprintf@1.3.0 checking installable status
226 silly pacote version manifest for json-schema@0.2.3 fetched in 211ms
227 silly resolveWithNewModule json-schema@0.2.3 checking installable status
228 http fetch GET 304 https://registry.npmjs.org/verror 213ms (from cache)
229 silly pacote version manifest for verror@1.10.0 fetched in 241ms
230 silly resolveWithNewModule verror@1.10.0 checking installable status
231 http fetch GET 304 https://registry.npmjs.org/core-util-is 104ms (from cache)
232 silly pacote version manifest for core-util-is@1.0.2 fetched in 119ms
233 silly resolveWithNewModule core-util-is@1.0.2 checking installable status
234 http fetch GET 304 https://registry.npmjs.org/asn1 434ms (from cache)
235 http fetch GET 304 https://registry.npmjs.org/dashdash 438ms (from cache)
236 http fetch GET 304 https://registry.npmjs.org/getpass 439ms (from cache)
237 http fetch GET 304 https://registry.npmjs.org/safer-buffer 439ms (from cache)
238 http fetch GET 304 https://registry.npmjs.org/jsbn 454ms (from cache)
239 http fetch GET 304 https://registry.npmjs.org/ecc-jsbn 454ms (from cache)
240 http fetch GET 304 https://registry.npmjs.org/tweetnacl 458ms (from cache)
241 http fetch GET 304 https://registry.npmjs.org/bcrypt-pbkdf 456ms (from cache)
242 silly pacote range manifest for asn1@~0.2.3 fetched in 484ms
243 silly resolveWithNewModule asn1@0.2.3 checking installable status
244 silly pacote range manifest for dashdash@^1.12.0 fetched in 488ms
245 silly resolveWithNewModule dashdash@1.14.1 checking installable status
246 silly pacote range manifest for getpass@^0.1.1 fetched in 491ms
247 silly resolveWithNewModule getpass@0.1.7 checking installable status
248 silly pacote range manifest for safer-buffer@^2.0.2 fetched in 494ms
249 silly resolveWithNewModule safer-buffer@2.1.2 checking installable status
250 silly pacote range manifest for jsbn@~0.1.0 fetched in 497ms
251 silly resolveWithNewModule jsbn@0.1.1 checking installable status
252 silly pacote range manifest for ecc-jsbn@~0.1.1 fetched in 501ms
253 silly resolveWithNewModule ecc-jsbn@0.1.1 checking installable status
254 silly pacote range manifest for tweetnacl@~0.14.0 fetched in 508ms
255 silly resolveWithNewModule tweetnacl@0.14.5 checking installable status
256 silly pacote range manifest for bcrypt-pbkdf@^1.0.0 fetched in 509ms
257 silly resolveWithNewModule bcrypt-pbkdf@1.0.1 checking installable status
258 http fetch GET 304 https://registry.npmjs.org/punycode 108ms (from cache)
259 silly pacote range manifest for punycode@^1.4.1 fetched in 122ms
260 silly resolveWithNewModule punycode@1.4.1 checking installable status
261 http fetch GET 304 https://registry.npmjs.org/async 181ms (from cache)
262 http fetch GET 304 https://registry.npmjs.org/string-template 202ms (from cache)
263 silly pacote range manifest for async@~2.1.4 fetched in 390ms
264 silly resolveWithNewModule async@2.1.5 checking installable status
265 silly pacote range manifest for string-template@~1.0.0 fetched in 395ms
266 silly resolveWithNewModule string-template@1.0.0 checking installable status
267 http fetch GET 304 https://registry.npmjs.org/lodash 141ms (from cache)
268 silly pacote range manifest for lodash@^4.14.0 fetched in 161ms
269 silly resolveWithNewModule lodash@4.17.10 checking installable status
270 timing stage:loadIdealTree:loadAllDepsIntoIdealTree Completed in 8650ms
271 timing stage:loadIdealTree Completed in 9349ms
272 silly currentTree lib
272 silly currentTree └─┬ homebridge-camera-ffmpeg@0.1.8
272 silly currentTree   ├── ajv@5.5.2
272 silly currentTree   ├── asn1@0.2.3
272 silly currentTree   ├── assert-plus@1.0.0
272 silly currentTree   ├── async@2.1.5
272 silly currentTree   ├── asynckit@0.4.0
272 silly currentTree   ├── aws-sign2@0.7.0
272 silly currentTree   ├── aws4@1.7.0
272 silly currentTree   ├── bcrypt-pbkdf@1.0.1
272 silly currentTree   ├── buffer-equal-constant-time@1.0.1
272 silly currentTree   ├── caseless@0.12.0
272 silly currentTree   ├── co@4.6.0
272 silly currentTree   ├── combined-stream@1.0.6
272 silly currentTree   ├── core-util-is@1.0.2
272 silly currentTree   ├── dashdash@1.14.1
272 silly currentTree   ├── debug@2.6.9
272 silly currentTree   ├── delayed-stream@1.0.0
272 silly currentTree   ├── ecc-jsbn@0.1.1
272 silly currentTree   ├── ecdsa-sig-formatter@1.0.10
272 silly currentTree   ├── extend@3.0.1
272 silly currentTree   ├── extsprintf@1.3.0
272 silly currentTree   ├── fast-deep-equal@1.1.0
272 silly currentTree   ├── fast-json-stable-stringify@2.0.0
272 silly currentTree   ├── forever-agent@0.6.1
272 silly currentTree   ├── form-data@2.3.2
272 silly currentTree   ├── getpass@0.1.7
272 silly currentTree   ├── google-auth-library@0.10.0
272 silly currentTree   ├── google-p12-pem@0.1.2
272 silly currentTree   ├── googleapis@18.0.0
272 silly currentTree   ├── gtoken@1.2.3
272 silly currentTree   ├── har-schema@2.0.0
272 silly currentTree   ├── har-validator@5.0.3
272 silly currentTree   ├── http-signature@1.2.0
272 silly currentTree   ├── ip@1.1.5
272 silly currentTree   ├── is-typedarray@1.0.0
272 silly currentTree   ├── isstream@0.1.2
272 silly currentTree   ├── jsbn@0.1.1
272 silly currentTree   ├── json-schema-traverse@0.3.1
272 silly currentTree   ├── json-schema@0.2.3
272 silly currentTree   ├── json-stringify-safe@5.0.1
272 silly currentTree   ├── jsprim@1.4.1
272 silly currentTree   ├── jwa@1.1.6
272 silly currentTree   ├── jws@3.1.5
272 silly currentTree   ├── lodash.noop@3.0.1
272 silly currentTree   ├── lodash@4.17.10
272 silly currentTree   ├── mime-db@1.33.0
272 silly currentTree   ├── mime-types@2.1.18
272 silly currentTree   ├── mime@1.6.0
272 silly currentTree   ├── ms@2.0.0
272 silly currentTree   ├── node-forge@0.7.5
272 silly currentTree   ├── oauth-sign@0.8.2
272 silly currentTree   ├── performance-now@2.1.0
272 silly currentTree   ├── punycode@1.4.1
272 silly currentTree   ├── qs@6.5.2
272 silly currentTree   ├── request@2.87.0
272 silly currentTree   ├── safe-buffer@5.1.2
272 silly currentTree   ├── safer-buffer@2.1.2
272 silly currentTree   ├── sshpk@1.14.2
272 silly currentTree   ├── string-template@1.0.0
272 silly currentTree   ├── tough-cookie@2.3.4
272 silly currentTree   ├── tunnel-agent@0.6.0
272 silly currentTree   ├── tweetnacl@0.14.5
272 silly currentTree   ├── uuid@3.2.1
272 silly currentTree   └── verror@1.10.0
273 silly idealTree lib
273 silly idealTree └─┬ homebridge-camera-ffmpeg@0.1.8
273 silly idealTree   ├── ajv@5.5.2
273 silly idealTree   ├── asn1@0.2.3
273 silly idealTree   ├── assert-plus@1.0.0
273 silly idealTree   ├── async@2.1.5
273 silly idealTree   ├── asynckit@0.4.0
273 silly idealTree   ├── aws-sign2@0.7.0
273 silly idealTree   ├── aws4@1.7.0
273 silly idealTree   ├── bcrypt-pbkdf@1.0.1
273 silly idealTree   ├── buffer-equal-constant-time@1.0.1
273 silly idealTree   ├── caseless@0.12.0
273 silly idealTree   ├── co@4.6.0
273 silly idealTree   ├── combined-stream@1.0.6
273 silly idealTree   ├── core-util-is@1.0.2
273 silly idealTree   ├── dashdash@1.14.1
273 silly idealTree   ├── debug@2.6.9
273 silly idealTree   ├── delayed-stream@1.0.0
273 silly idealTree   ├── ecc-jsbn@0.1.1
273 silly idealTree   ├── ecdsa-sig-formatter@1.0.10
273 silly idealTree   ├── extend@3.0.1
273 silly idealTree   ├── extsprintf@1.3.0
273 silly idealTree   ├── fast-deep-equal@1.1.0
273 silly idealTree   ├── fast-json-stable-stringify@2.0.0
273 silly idealTree   ├── forever-agent@0.6.1
273 silly idealTree   ├── form-data@2.3.2
273 silly idealTree   ├── getpass@0.1.7
273 silly idealTree   ├── google-auth-library@0.10.0
273 silly idealTree   ├── google-p12-pem@0.1.2
273 silly idealTree   ├── googleapis@18.0.0
273 silly idealTree   ├── gtoken@1.2.3
273 silly idealTree   ├── har-schema@2.0.0
273 silly idealTree   ├── har-validator@5.0.3
273 silly idealTree   ├── http-signature@1.2.0
273 silly idealTree   ├── ip@1.1.5
273 silly idealTree   ├── is-typedarray@1.0.0
273 silly idealTree   ├── isstream@0.1.2
273 silly idealTree   ├── jsbn@0.1.1
273 silly idealTree   ├── json-schema-traverse@0.3.1
273 silly idealTree   ├── json-schema@0.2.3
273 silly idealTree   ├── json-stringify-safe@5.0.1
273 silly idealTree   ├── jsprim@1.4.1
273 silly idealTree   ├── jwa@1.1.6
273 silly idealTree   ├── jws@3.1.5
273 silly idealTree   ├── lodash.noop@3.0.1
273 silly idealTree   ├── lodash@4.17.10
273 silly idealTree   ├── mime-db@1.33.0
273 silly idealTree   ├── mime-types@2.1.18
273 silly idealTree   ├── mime@1.6.0
273 silly idealTree   ├── ms@2.0.0
273 silly idealTree   ├── node-forge@0.7.5
273 silly idealTree   ├── oauth-sign@0.8.2
273 silly idealTree   ├── performance-now@2.1.0
273 silly idealTree   ├── punycode@1.4.1
273 silly idealTree   ├── qs@6.5.2
273 silly idealTree   ├── request@2.87.0
273 silly idealTree   ├── safe-buffer@5.1.2
273 silly idealTree   ├── safer-buffer@2.1.2
273 silly idealTree   ├── sshpk@1.14.2
273 silly idealTree   ├── string-template@1.0.0
273 silly idealTree   ├── tough-cookie@2.3.4
273 silly idealTree   ├── tunnel-agent@0.6.0
273 silly idealTree   ├── tweetnacl@0.14.5
273 silly idealTree   ├── uuid@3.2.1
273 silly idealTree   └── verror@1.10.0
274 silly install generateActionsToTake
275 warn checkPermissions Missing write access to /usr/local/lib/node_modules/homebridge-camera-ffmpeg
276 warn checkPermissions Missing write access to /usr/local/lib/node_modules
277 timing stage:rollbackFailedOptional Completed in 8ms
278 timing stage:runTopLevelLifecycles Completed in 14287ms
279 verbose stack Error: EACCES: permission denied, access '/usr/local/lib/node_modules/homebridge-camera-ffmpeg'
279 verbose stack     at Error (native)
280 verbose cwd /home/pi
281 verbose Linux 4.9.35-v7+
282 verbose argv "/usr/local/bin/node" "/usr/local/bin/npm" "install" "-g" "homebridge-camera-ffmpeg"
283 verbose node v6.10.0
284 verbose npm  v6.1.0
285 error path /usr/local/lib/node_modules/homebridge-camera-ffmpeg
286 error code EACCES
287 error errno -13
288 error syscall access
289 error Error: EACCES: permission denied, access '/usr/local/lib/node_modules/homebridge-camera-ffmpeg'
289 error     at Error (native)
289 error  { Error: EACCES: permission denied, access '/usr/local/lib/node_modules/homebridge-camera-ffmpeg'
289 error     at Error (native)
289 error   stack: 'Error: EACCES: permission denied, access \'/usr/local/lib/node_modules/homebridge-camera-ffmpeg\'\n    at Error (native)',
289 error   errno: -13,
289 error   code: 'EACCES',
289 error   syscall: 'access',
289 error   path: '/usr/local/lib/node_modules/homebridge-camera-ffmpeg' }
290 error The operation was rejected by your operating system.
290 error It is likely you do not have the permissions to access this file as the current user
290 error
290 error If you believe this might be a permissions issue, please double-check the
290 error permissions of the file and its containing directories, or try running
290 error the command again as root/Administrator (though this is not recommended).
291 verbose exit [ -13, true ]

wires.io

Ich nutze homebridge-fhem seit einiger Zeit für die Anbindung von Homematic-Schaltern an Homekit.

Ich möchte nun damit gerne ein weiteres Gerät in Homekit anlegen und zwar ein "Smart Meter", wo ich die gemessenen Werte für Bezug und PV-Einspeisung auf einen Blick habe. Da sowas in Homekit (noch) nicht vorgesehen ist, würde ich den Umweg über den genericDeviceType "thermometer" gehen, wo im Icon ein Temperaturwert angezeigt wird und nach Long-Press dann eine Übersicht über alle weiteren Messwerte erscheint. Kann das so funktionieren? Und wenn ja, wie lege ich einen solchen Smart Meter in FHEM an?

Danke! (Und sorry, wenn das schon irgendwo beschrieben steht und ich es übersehen habe.)

Sky

Hallo ,

ich habe mein Fhem komplett neu installiert , das Plugin scheint jetzt zu laufen.
Allerdings habe ich noch einen Fehler beim start der Homebridge

Vielleicht weiß jemand was diese Meldung bedeutet ?


pi@raspberrypi:~ $ homebridge
[6/24/2018, 4:41:18 PM] Loaded config.json with 0 accessories and 2 platforms.
[6/24/2018, 4:41:18 PM] ---
[6/24/2018, 4:41:19 PM] Loaded plugin: homebridge-camera-ffmpeg
[6/24/2018, 4:41:19 PM] Registering platform 'homebridge-camera-ffmpeg.Camera-ffmpeg'
[6/24/2018, 4:41:19 PM] ---
[6/24/2018, 4:41:19 PM] Loaded plugin: homebridge-fhem
homebridge API version: 2.2
this is homebridge-fhem 0.4.5
[6/24/2018, 4:41:19 PM] Registering platform 'homebridge-fhem.FHEM'
[6/24/2018, 4:41:19 PM] ---
[6/24/2018, 4:41:19 PM] Loading 2 platforms...
[6/24/2018, 4:41:19 PM] [FHEM] Initializing FHEM platform...
starting longpoll: http://127.0.0.1:8083/fhem?XHR=1&inform=type=status;addglobal=1;filter=.*;since=null;fmt=JSON&timestamp=1529851280517
[6/24/2018, 4:41:20 PM] [FHEM] Fetching FHEM devices...
[6/24/2018, 4:41:20 PM] [Camera-ffmpeg] Initializing Camera-ffmpeg platform...
[6/24/2018, 4:41:20 PM] Loading 0 accessories...
Server error: Error: listen EADDRINUSE :::8282
[6/24/2018, 4:41:20 PM] Outside Front is running on port 41589.
Server listening on: http://<ip>:8283
[6/24/2018, 4:41:20 PM] [FHEM] Checking devices and attributes...
[6/24/2018, 4:41:20 PM] [FHEM]   executing: http://127.0.0.1:8083/fhem?cmd=%7BAttrVal(%22global%22,%22userattr%22,%22%22)%7D&XHR=1
[6/24/2018, 4:41:20 PM] [FHEM]   executing: http://127.0.0.1:8083/fhem?cmd=jsonlist2%20TYPE=siri&XHR=1
[6/24/2018, 4:41:20 PM] [FHEM] siri device is siri
[6/24/2018, 4:41:20 PM] [FHEM]   executing: http://127.0.0.1:8083/fhem?cmd=%7B$defs%7Bsiri%7D-%3E%7B%22homebridge-fhem%20version%22%7D%20=%20%220.4.5%22%7D&XHR=1
[6/24/2018, 4:41:21 PM] [FHEM] Fetching FHEM devices...
[6/24/2018, 4:41:21 PM] [FHEM] fetching: http://127.0.0.1:8083/fhem?cmd=jsonlist2%20room=Homekit&XHR=1
[6/24/2018, 4:41:21 PM] [FHEM] got: 1 results
[6/24/2018, 4:41:21 PM] [FHEM] Hue: no service type detected
[6/24/2018, 4:41:21 PM] [FHEM] no accessory created for Hue (HUEBridge)
Setup Payload:
X-HM://0023ISYWYCP94
Scan this code with your HomeKit app on your iOS device to pair with Homebridge:

Or enter this code with your HomeKit app on your iOS device to pair with Homebridge:

    ┌────────────┐
    │ 031-45-154 │
    └────────────┘

events.js:160
      throw er; // Unhandled 'error' event
      ^

Error: listen EADDRINUSE :::51826
    at Object.exports._errnoException (util.js:1020:11)
    at exports._exceptionWithHostPort (util.js:1043:20)
    at Server._listen2 (net.js:1271:14)
    at listen (net.js:1307:10)
    at Server.listen (net.js:1403:5)
    at EventedHTTPServer.listen (/usr/lib/node_modules/homebridge/node_modules/hap-nodejs/lib/util/eventedhttp.js:60:19)
    at HAPServer.listen (/usr/lib/node_modules/homebridge/node_modules/hap-nodejs/lib/HAPServer.js:158:20)
    at Bridge.Accessory.publish (/usr/lib/node_modules/homebridge/node_modules/hap-nodejs/lib/Accessory.js:607:16)
    at Server._publish (/usr/lib/node_modules/homebridge/lib/server.js:126:16)
    at Server.<anonymous> (/usr/lib/node_modules/homebridge/lib/server.js:402:14)



Wäre super wenn mir einer etwas dazu sagen könnte ....

DANKE  :-\


Typ1er

#2913
deine Homebridge läuft 2x

Der Port ist schon belegt: "Error: listen EADDRINUSE :::51826". = E(rror) ADDRess IN USE

Sky

#2914
Wie geht das denn ?

Meine config.json sieht so aus :


{
    "bridge": {
        "name": "Homebridge",
        "username": "CC:22:3D:E3:CE:30",
        "port": 51826,
        "pin": "031-45-154"
    },

    "platforms": [{
       
            "platform": "FHEM",
            "name": "FHEM",
            "server": "127.0.0.1",
            "port": "8083",
"auth": {"user": "xxx", "pass": "xxx"},
            "filter": "room=Homekit"
        },
       {   
             
          "platform": "Camera-ffmpeg",
           "cameras":[ {
                 "name": "Outside Front",
                   "videoConfig": {
                      "source": "-re -i rtsp://192.168.178.xx:554/user=admin_password=xxxx_channel=1_stream=0.sdp?real_stream--rtp-caching=100",
                      "stillImageSource":"rtsp://192.168.178.xx:554/user=admin_password=xxxx_channel=1_stream=0.sdp?real_stream--rtp-caching=100",
                     "maxStreams": 2,
                      "maxWidth": 1280,
                      "maxHeight": 720,
                      "maxFPS": 50
                   }
                 
           }

      ]
     }
   ],
     
    "accessories": [] 
   
}


Ich starte die Homebridge als Service wie im Wiki beschrieben,

wenn ich "systemctl status homebridge" aufrufe kommt folgendes :


pi@raspberrypi:~ $ systemctl status homebridge
● homebridge.service - LSB: Start daemon at boot time for homebridge
   Loaded: loaded (/etc/init.d/homebridge; generated; vendor preset: enabled)
   Active: active (exited) since Sun 2018-06-24 16:40:10 CEST; 45min ago
     Docs: man:systemd-sysv-generator(8)
  Process: 491 ExecStart=/etc/init.d/homebridge start (code=exited, status=0/SUCCESS)
   CGroup: /system.slice/homebridge.service

Jun 24 16:40:09 raspberrypi systemd[1]: Starting LSB: Start daemon at boot time for homebridge...
Jun 24 16:40:10 raspberrypi su[501]: Successful su for pi by root
Jun 24 16:40:10 raspberrypi su[501]: + ??? root:pi
Jun 24 16:40:10 raspberrypi su[501]: pam_unix(su:session): session opened for user pi by (uid=0)
Jun 24 16:40:10 raspberrypi homebridge[491]: Homebridge starting
Jun 24 16:40:10 raspberrypi homebridge[491]: Homebridge is not running
Jun 24 16:40:10 raspberrypi systemd[1]: Started LSB: Start daemon at boot time for homebridge.


Typ1er

Wie startest du deine Homebridge

Sky

Entschuldigung ,hatte meinen vorherigen Eintrag gerade bearbeitet .

Ich starte wie im Wiki beschrieben als Service ...

Sky

#2917
Ich habe jetzt ein "  sudo killall homebridge " gemacht .

Danach mit "homebridge" gestartet , jetzt läuft es ohne Fehler .

Das Problem ist aber bei einem Neustart des Raspberry wieder das gleiche !!

Aber weshalb startet die Homebridge denn 2X ??

Typ1er

jetzt brauche ich mal einen Tip.

Ich habe einen Fenstersensor zum Lichtschalter umgebaut.

Dieser liefert im state open und close zurück

Wie muss das Homebridgemapping aussehen, damit ich den Schalter nur als toggle habe. Ich möchte ihn per FHEM schalten können, als auch Nativ (und das dann in Homekit einbinden).

Markus M.

Zitat von: Typ1er am 25 Juni 2018, 11:57:46Ich habe einen Fenstersensor zum Lichtschalter umgebaut.
Wie muss das Homebridgemapping aussehen, damit ich den Schalter nur als toggle habe.
Gar nicht?
Oder wie genau hast du den Sensor verdrahtet?
Du bindest nur die Lampe in HomeKit ein und überwachst deine Konstruktion mit einem Notify, dass bei jeder Änderung ein Toggle auf die Lampe macht?!
FHEM dev + HomeBridge + Lenovo Flex15 + HM-CFG-USB + RFXtrx433 + Fritz!Box 7590/7580/546E

HM Aktor/Sensor/Winmatic/Keymatic/Thermostat, HUE, Netatmo Weather/Security/Heating, Xiaomi AirPurifier/Vacuum, Withings Aura/BPM/Cardio/Go/Pulse/Thermo, VSX828, Harmony, Siro ERB15LE
https://paypal.me/mm0

Typ1er

ich hätte den Schalter so wie einen Normalen Hue Taster gern in Homekit

Momentan brauche ich dafür 4 Regeln in Homekit:
Schalter ist an, Lampe aus = Lampe An
Schalter ist an, Lampe ist an= Lampe An
Schalter ist aus, Lampe aus = Lampe Aus
Schalter ist aus, Lampe ist an= Lampe Aus

zusätzlich habe eben noch Hue Schalter, daher brauch die Regeln, dachte kann das irgendwie abkürzen, das es wie ein normale Taster aussieht.

Typ1er

kann mir einer sagen ob ich hier einen Dreher habe? Der Schalter geht soweit. Nur hab irgendwo einen Dreher, wenn den Schalter Manuel in Homekit umlege, muss den Schalter 2 mal schalten bevor was wieder was passiert.
Internals:
   DEF        158d000201dcc3 sensor_magnet.aq2 MiGateway
   IODev      MiGateway1
   IODevMissing 1
   IODevName  MiGateway
   LASTInputDev MiGateway1
   MODEL      sensor_magnet.aq2
   MSGCNT     6
   MiGateway1_MSGCNT 5
   MiGateway1_TIME 2018-06-25 20:59:31
   MiGateway2_MSGCNT 6
   MiGateway2_TIME 2018-06-25 20:59:31
   NAME       XMI_158d000201dcc3
   NR         121
   SID        158d000201dcc3
   STATE      An
   TYPE       XiaomiSmartHome_Device
   VERSION    1.20
   READINGS:
     2018-06-25 20:53:53   battery         ok
     2018-06-25 20:53:53   battery_level   3
     2018-06-25 20:43:30   heartbeat       158d000201dcc3
     2018-06-25 20:59:31   no_close        60
     2018-06-25 20:58:31   state           open
Attributes:
   IODev      MiGateway
   alias      Leselampe
   devStateIcon Aus:ios-off:An An:ios-on-green:Aus
   eventMap   /open:An/close:Aus/
   genericDeviceType switch
   homebridgeMapping On=state,valueOn=open,valueOff=close,cmdOn=An,cmdOff=Aus
   room       52 Wohnzimmer,Homekit,MiSmartHome

wuast94

Also ich bin gerade dabei mein Thermostat einzubinden. Homebridge läuft und erkennt auch schon ein paar devices soweit so gut.

das wo ich jetzt hänge ist das HomeBridge mapping.

erstmal zu den daten in fhem zu einem thermostat was ich habe:

Internals:

DEF HeizungWohn
IODev d_ccu
NAMEHM_Heizung Wohn
NR 49
STATE Initialized
TYPE HMCCUDEV
ccuaddr NEQ0309843
ccudevstate active
ccuif BidCos-RF
ccuname HeizungWohn
ccutype HM-CC-RT-DN
channels 7
firmware 1.4
statevals devstate


Readings:
0.AES_KEY 1 2018-06-28 20:37:57
0.CONFIG_PENDING false 2018-06-28 20:37:57
0.DEVICE_IN_BOOTLOADER false 2018-06-28 20:37:57
0.INHIBIT false 2018-06-28 20:37:57
0.LOWBAT false 2018-06-28 20:37:57
0.RSSI_DEVICE 1 2018-06-28 20:37:57
0.RSSI_PEER 215 2018-06-28 20:37:57
0.STICKY_UNREACH false 2018-06-28 20:37:57
0.UNREACH false 2018-06-28 20:37:57
0.UPDATE_PENDING false 2018-06-28 20:37:57
4.ACTUAL_TEMPERATURE 24.700000 2018-07-10 00:11:33
4.BATTERY_STATE 2.600000 2018-07-10 00:11:33
4.BOOST_STATE 0 2018-07-10 00:11:33
4.CONTROL_MODE 1 2018-07-10 00:11:33
4.FAULT_REPORTING 0 2018-07-10 00:11:33
4.PARTY_START_DAY 1 2018-07-10 00:11:33
4.PARTY_START_MONTH 1 2018-07-10 00:11:33
4.PARTY_START_TIME 0 2018-07-10 00:11:33
4.PARTY_START_YEAR 0 2018-07-10 00:11:33
4.PARTY_STOP_DAY 1 2018-07-10 00:11:33
4.PARTY_STOP_MONTH 1 2018-07-10 00:11:33
4.PARTY_STOP_TIME 0 2018-07-10 00:11:33
4.PARTY_STOP_YEAR 0 2018-07-10 00:11:33
4.PARTY_TEMPERATURE 5.000000 2018-07-10 00:11:33
4.SET_TEMPERATURE 4.500000 2018-07-10 00:11:33
4.VALVE_STATE 0 2018-07-10 00:11:33
hmstate Initialized 2018-07-10 00:11:33
state Initialized 2018-06-28 20:37:42


Attributes

IODev d_ccu deleteattr
genericDeviceType thermostat deleteattr
room HM,Homekit deleteattr


Ich habe es schon versucht herraus zu finden aber auch mit den beispiel konfigurationen komme ich nicht klar .. wahrscheinlich ist es eig einfach und ich habe nur n wichtigen punkt nicht verstanden.

wenn jemand ne beispiel hätte zum mapping zu meinen werten wäre ich sehr dankbar.
mit "4.SET_TEMPERATURE" "value" setze ich zb die temperatur
Zigbee  Temp+Luftdruck+Humi Bewegungsmeldern Tür Kontakte, Klingel, TV, Denon, Schaltbare Steckdosen mit leistungsmessung, und weiteres

Homeassistant mit Nodered

hoppel118

Moinsen @wuast94

ich habe 7 Homematic-Thermostate per VCCU und HM-USB mit FHEM gekoppelt. Meine fhem.cfg sieht dazu wie folgt aus. Da ich nicht weiß, was dir genau fehlt poste ich mal nachfolgend die Bereiche der fhem.cfg, die dir evtl. weiter helfen könnten.

attr global userattr cmdIcon devStateIcon devStateStyle genericDeviceType:switch,outlet,light,blind,speaker,thermostat homebridgeMapping:textField-long icon siriName sortby webCmd webCmdLabel:textField-long widgetOverride

#HM-Gateway
define HMUSB HMLAN 127.0.0.1:1234
attr HMUSB hmId XXXXXX
attr HMUSB hmLanQlen 1_min
attr HMUSB loadLevel 0:low,40:batchLevel,90:high,99:suspended

#HM-ActionDetector
define ActionDetector CUL_HM 000000
attr ActionDetector event-on-change-reading .*
attr ActionDetector model ActionDetector

#HM-VCCU
define VCCU CUL_HM XXXXXX
attr VCCU IODev HMUSB
attr VCCU IOList HMUSB
attr VCCU expert 2_full
attr VCCU model CCU-FHEM
attr VCCU subType virtual
attr VCCU webCmd virtual:update

#HUE Bridge
define HUEBridge HUEBridge XX.XX.XX.XX
attr HUEBridge createGroupReadings 1
attr HUEBridge icon hue_filled_bridge_v2
attr HUEBridge key XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

#Homebridge
define siri siri
define Homebridge dummy
attr Homebridge devStateIcon .*on:general_an .*off:general_aus .*:audio_rec
attr Homebridge eventMap status:status start:start stop:stop restart:restart
attr Homebridge icon it_router
attr Homebridge room Homebridge
attr Homebridge userReadings OnStateChange:(start|stop|restart|status) {  system ("sudo service homebridge ".ReadingsVal($NAME,"state","restart")." &" );;  }
attr Homebridge webCmd status:start:stop:restart

#Thermostat Bad
define OG_Bad_Thermostat CUL_HM 3D9466
attr OG_Bad_Thermostat IODev HMUSB
attr OG_Bad_Thermostat actCycle 000:10
attr OG_Bad_Thermostat actStatus alive
attr OG_Bad_Thermostat alias Bad Thermostat
attr OG_Bad_Thermostat autoReadReg 4_reqStatus
attr OG_Bad_Thermostat expert 2_full
attr OG_Bad_Thermostat firmware 1.4
attr OG_Bad_Thermostat model HM-CC-RT-DN
attr OG_Bad_Thermostat serialNr MEQ0560590
attr OG_Bad_Thermostat subType thermostat
attr OG_Bad_Thermostat webCmd getConfig:clear msgEvents:burstXmit
define FileLog_OG_Bad_Thermostat FileLog ./log/OG_Bad_Thermostat-%Y.log OG_Bad_Thermostat
attr FileLog_OG_Bad_Thermostat logtype text
define OG_Bad_Thermostat_Weather CUL_HM 3D946601
attr OG_Bad_Thermostat_Weather model HM-CC-RT-DN
attr OG_Bad_Thermostat_Weather peerIDs 00000000,
define OG_Bad_Thermostat_Climate CUL_HM 3D946602
attr OG_Bad_Thermostat_Climate model HM-CC-RT-DN
attr OG_Bad_Thermostat_Climate peerIDs 00000000,
define OG_Bad_Thermostat_WindowRec CUL_HM 3D946603
attr OG_Bad_Thermostat_WindowRec model HM-CC-RT-DN
attr OG_Bad_Thermostat_WindowRec peerIDs 00000000,
attr OG_Bad_Thermostat_WindowRec stateFormat last:trigLast
define OG_Bad_Thermostat_Clima CUL_HM 3D946604
attr OG_Bad_Thermostat_Clima alias Bad Thermostat
attr OG_Bad_Thermostat_Clima group Thermostate
attr OG_Bad_Thermostat_Clima homebridgeMapping TargetHeatingCoolingState=heatingState,values=OFF:0;;HEAT:1;;COOL:2;;AUTO:3,cmds=OFF:controlManu+off;;HEAT:controlMode+boost;;AUTO:controlMode+auto;;COOL:controlMode+night CurrentHeatingCoo$
attr OG_Bad_Thermostat_Clima icon sani_heating
attr OG_Bad_Thermostat_Clima model HM-CC-RT-DN
attr OG_Bad_Thermostat_Clima peerIDs 00000000,
attr OG_Bad_Thermostat_Clima room Bad,Thermostate,Homebridge
attr OG_Bad_Thermostat_Clima userReadings heatingState {(ReadingsVal($NAME,"ValvePosition",0) > 0 || ReadingsVal($NAME,"desired-temp","-") eq "on") ? "HEAT" : ReadingsVal($NAME,"desired-temp","-") eq "off" ? "OFF" : ReadingsVal($NAME,"c$
define FileLog_OG_Bad_Thermostat_Clima FileLog ./log/OG_Bad_Thermostat_Clima-%Y.log OG_Bad_Thermostat_Clima
attr FileLog_OG_Bad_Thermostat_Clima logtype text
define OG_Bad_Thermostat_ClimaTeam CUL_HM 3D946605
attr OG_Bad_Thermostat_ClimaTeam model HM-CC-RT-DN
attr OG_Bad_Thermostat_ClimaTeam peerIDs 00000000,
define OG_Bad_Thermostat_remote CUL_HM 3D946606
attr OG_Bad_Thermostat_remote model HM-CC-RT-DN
attr OG_Bad_Thermostat_remote peerIDs 00000000,


Mein FHEM und auch mein HUE Equipment wurde schon länger nicht mehr geupdated. Bin mir gerade nicht sicher, ob die Konfiguration der Hue Bridge so nach den ganzen Updates noch funktioniert. Wenn das was spezielles brauchst, sage mir was. Dann ermittle ich, wie das bei mir konfiguriert ist.

Gruß Hoppel
Server: Openmediavault, XEON E3-1240L-v5, Supermicro X11SSH-CTF, 64GB ECC RAM, SSD, RAID-Z2
Homebridge | Alexa | Yowsup
Homematic | HomeConnect | MQTT | Philips Hue | Sonos | Unifi Network & Protect | vbus | Xiaomi

wuast94

Danke hoppel118

Du konntest anscheinend kommplett ohne homebridge mapping arbeiten..Ich habe alles über die ccu2 eingebunden und deswegen greift die autoerkennung bei mir anscheinend nicht. Also es wird zwar wegen dem genericDeviceType thermostat in homebridge erkannt allerdings funktioniert weder dir Steuerung noch die min Max werte und alles. Dafür muss ich das homebridge mapping machen soweit ich das verstanden habe..Allerdings steige ich da nicht durch :D
Zigbee  Temp+Luftdruck+Humi Bewegungsmeldern Tür Kontakte, Klingel, TV, Denon, Schaltbare Steckdosen mit leistungsmessung, und weiteres

Homeassistant mit Nodered