39_gassistant.pm (Google Assistant, Google Home)

erotikbaer · 13 April 2020, 18:11:05

so, also mit aktuellem node v13.10.1 und npm 6.12.1 bekomme ich folgende fehler.:

1 warning and 5 errors generated.
gmake: *** [ares.target.mk:220: Release/obj.target/ares/deps/grpc/third_party/cares/cares/ares__close_sockets.o] Error 1
gmake: Leaving directory '/usr/local/lib/node_modules/gassistant-fhem/node_modules/grpc/build'
gyp ERR! build error
gyp ERR! stack Error: `gmake` failed with exit code: 2
gyp ERR! stack     at ChildProcess.onExit (/usr/local/lib/node_modules/npm/node_modules/node-gyp/lib/build.js:194:23)
gyp ERR! stack     at ChildProcess.emit (events.js:316:20)
gyp ERR! stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:275:12)
gyp ERR! System FreeBSD 11.3-RELEASE-p6
gyp ERR! command "/usr/local/bin/node" "/usr/local/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "build" "--fallback-to-build" "--library=static_library" "--module=/usr/local/lib/node_modules/gassistant-fhem/node_modules/grpc/src/node/extension_binary/node-v79-freebsd-x64-unknown/grpc_node.node" "--module_name=grpc_node" "--module_path=/usr/local/lib/node_modules/gassistant-fhem/node_modules/grpc/src/node/extension_binary/node-v79-freebsd-x64-unknown" "--napi_version=5" "--node_abi_napi=napi" "--napi_build_version=0" "--node_napi_label=node-v79"
gyp ERR! cwd /usr/local/lib/node_modules/gassistant-fhem/node_modules/grpc
gyp ERR! node -v v13.10.1
gyp ERR! node-gyp -v v5.0.5
gyp ERR! not ok
node-pre-gyp ERR! build error
node-pre-gyp ERR! stack Error: Failed to execute '/usr/local/bin/node /usr/local/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js build --fallback-to-build --library=static_library --module=/usr/local/lib/node_modules/gassistant-fhem/node_modules/grpc/src/node/extension_binary/node-v79-freebsd-x64-unknown/grpc_node.node --module_name=grpc_node --module_path=/usr/local/lib/node_modules/gassistant-fhem/node_modules/grpc/src/node/extension_binary/node-v79-freebsd-x64-unknown --napi_version=5 --node_abi_napi=napi --napi_build_version=0 --node_napi_label=node-v79' (1)
node-pre-gyp ERR! stack     at ChildProcess.<anonymous> (/usr/local/lib/node_modules/gassistant-fhem/node_modules/grpc/node_modules/node-pre-gyp/lib/util/compile.js:83:29)
node-pre-gyp ERR! stack     at ChildProcess.emit (events.js:316:20)
node-pre-gyp ERR! stack     at maybeClose (internal/child_process.js:1026:16)
node-pre-gyp ERR! stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:286:5)
node-pre-gyp ERR! System FreeBSD 11.3-RELEASE-p6
node-pre-gyp ERR! command "/usr/local/bin/node" "/usr/local/lib/node_modules/gassistant-fhem/node_modules/grpc/node_modules/.bin/node-pre-gyp" "install" "--fallback-to-build" "--library=static_library"
node-pre-gyp ERR! cwd /usr/local/lib/node_modules/gassistant-fhem/node_modules/grpc
node-pre-gyp ERR! node -v v13.10.1
node-pre-gyp ERR! node-pre-gyp -v v0.14.0
node-pre-gyp ERR! not ok
Failed to execute '/usr/local/bin/node /usr/local/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js build --fallback-to-build --library=static_library --module=/usr/local/lib/node_modules/gassistant-fhem/node_modules/grpc/src/node/extension_binary/node-v79-freebsd-x64-unknown/grpc_node.node --module_name=grpc_node --module_path=/usr/local/lib/node_modules/gassistant-fhem/node_modules/grpc/src/node/extension_binary/node-v79-freebsd-x64-unknown --napi_version=5 --node_abi_napi=napi --napi_build_version=0 --node_napi_label=node-v79' (1)
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! grpc@1.24.2 install: `node-pre-gyp install --fallback-to-build --library=static_library`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the grpc@1.24.2 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/2020-04-13T16_08_36_756Z-debug.log

und das "npm rebuild --build-from-source --unsafe-perm grpc" bringt überhaupt keine Ausgabe.

gruß christian

dominik · 13 April 2020, 18:14:36

Ich weiß nicht wann bei "npm rebuild --build-from-source --unsafe-perm grpc" eine Ausgabe kommt, aber das Compilieren selbst - was bei rebuild gemacht wird - kann auf einen RPi schon ca. 2h dauern.

erotikbaer · 13 April 2020, 18:20:06

das ist ja kein rpi, sondern ein recht flotter rechner. und er ist auch "fertig" nur leider tut er nichts beim rebuild.
so siehts aus:
root@FhemNeu:/usr/ports/www/npm # npm rebuild --build-from-source --unsafe-perm grpc
root@FhemNeu:/usr/ports/www/npm #

dominik · 13 April 2020, 19:00:38

Ich habe jetzt mal ein bisschen gegoogelt und konnte einige dieser Fehlermeldungen in Zusammenhang mit FreeBSD finden. Den besten Hinweis den ich bislang gefunden habe war, dass node13 nicht unterstuetzt wird.

Kannst du bitte daher probieren node12 zu installieren und dann nochmals ein
sudo npm install grpc --unsafe-perm

Das Problem liegt leider an grpc, bei RPi/Raspbian wird das als Binary installiert. Fuer FreeBSD gibt es scheinbar keine Binaries.

smoki3 · 13 April 2020, 19:48:20

Sind denn die Sensor Devices auch schon implementiert?

erotikbaer · 13 April 2020, 19:58:59

Zitat von: dominik am 13 April 2020, 19:00:38
Ich habe jetzt mal ein bisschen gegoogelt und konnte einige dieser Fehlermeldungen in Zusammenhang mit FreeBSD finden. Den besten Hinweis den ich bislang gefunden habe war, dass node13 nicht unterstuetzt wird.

Kannst du bitte daher probieren node12 zu installieren und dann nochmals ein
sudo npm install grpc --unsafe-perm

Das Problem liegt leider an grpc, bei RPi/Raspbian wird das als Binary installiert. Fuer FreeBSD gibt es scheinbar keine Binaries.

so, ich könnte heulen...

Code Auswählen

gyp ERR! build error
gyp ERR! stack Error: `gmake` failed with exit code: 2
gyp ERR! stack     at ChildProcess.onExit (/usr/local/lib/node_modules/npm/node_modules/node-gyp/lib/build.js:194:23)
gyp ERR! stack     at ChildProcess.emit (events.js:311:20)
gyp ERR! stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:275:12)
gyp ERR! System FreeBSD 11.3-RELEASE-p6
gyp ERR! command "/usr/local/bin/node" "/usr/local/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "build" "--fallback-to-build" "--library=static_library" "--module=/usr/ports/www/npm-node12/node_modules/grpc/src/node/extension_binary/node-v72-freebsd-x64-unknown/grpc_node.node" "--module_name=grpc_node" "--module_path=/usr/ports/www/npm-node12/node_modules/grpc/src/node/extension_binary/node-v72-freebsd-x64-unknown" "--napi_version=5" "--node_abi_napi=napi" "--napi_build_version=0" "--node_napi_label=node-v72"
gyp ERR! cwd /usr/ports/www/npm-node12/node_modules/grpc
gyp ERR! node -v v12.16.1
gyp ERR! node-gyp -v v5.0.5
gyp ERR! not ok
node-pre-gyp ERR! build error
node-pre-gyp ERR! stack Error: Failed to execute '/usr/local/bin/node /usr/local/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js build --fallback-to-build --library=static_library --module=/usr/ports/www/npm-node12/node_modules/grpc/src/node/extension_binary/node-v72-freebsd-x64-unknown/grpc_node.node --module_name=grpc_node --module_path=/usr/ports/www/npm-node12/node_modules/grpc/src/node/extension_binary/node-v72-freebsd-x64-unknown --napi_version=5 --node_abi_napi=napi --napi_build_version=0 --node_napi_label=node-v72' (1)
node-pre-gyp ERR! stack     at ChildProcess.<anonymous> (/usr/ports/www/npm-node12/node_modules/grpc/node_modules/node-pre-gyp/lib/util/compile.js:83:29)
node-pre-gyp ERR! stack     at ChildProcess.emit (events.js:311:20)
node-pre-gyp ERR! stack     at maybeClose (internal/child_process.js:1021:16)
node-pre-gyp ERR! stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:286:5)
node-pre-gyp ERR! System FreeBSD 11.3-RELEASE-p6
node-pre-gyp ERR! command "/usr/local/bin/node" "/usr/ports/www/npm-node12/node_modules/grpc/node_modules/.bin/node-pre-gyp" "install" "--fallback-to-build" "--library=static_library"
node-pre-gyp ERR! cwd /usr/ports/www/npm-node12/node_modules/grpc
node-pre-gyp ERR! node -v v12.16.1
node-pre-gyp ERR! node-pre-gyp -v v0.14.0
node-pre-gyp ERR! not ok
Failed to execute '/usr/local/bin/node /usr/local/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js build --fallback-to-build --library=static_library --module=/usr/ports/www/npm-node12/node_modules/grpc/src/node/extension_binary/node-v72-freebsd-x64-unknown/grpc_node.node --module_name=grpc_node --module_path=/usr/ports/www/npm-node12/node_modules/grpc/src/node/extension_binary/node-v72-freebsd-x64-unknown --napi_version=5 --node_abi_napi=napi --napi_build_version=0 --node_napi_label=node-v72' (1)
npm WARN enoent ENOENT: no such file or directory, open '/usr/ports/www/npm-node12/package.json'
npm WARN npm-node12 No description
npm WARN npm-node12 No repository field.
npm WARN npm-node12 No README data
npm WARN npm-node12 No license field.

npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! grpc@1.24.2 install: `node-pre-gyp install --fallback-to-build --library=static_library`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the grpc@1.24.2 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/2020-04-13T17_57_03_444Z-debug.log

wenn ich aus dem /usr/ports/devel/grpc kompiliere, wirds die grpc-1.22.0_2,2... da scheint kein fehler aufzutreten. gehe ich recht in der annahme dass gassistant-fhem eine neuere grpc version braucht?

dominik · 13 April 2020, 20:37:40

Die Version 1.22 sollte auch gehen. Ich weiss jetzt jedoch nicht, wie du diese manuell hinzufuegen kannst. In der package.json von gassistant-fhem habe ich grpc 1.24.2 als Abhaengigkeit. Du koenntest dir das Paket vielleicht manuell herunterladen, die package.json editieren und dann installieren oder irgendwie die Version 1.24.2 vortaeuschen.

erotikbaer · 13 April 2020, 20:51:17

ok, dass würde ich glatt versuchen. kannst du mir sagen wie ich das paket manuell runterladen kann?

dominik · 13 April 2020, 21:06:21

Habe das hier gefunden:
https://stackoverflow.com/questions/15035786/download-source-from-npm-without-installing-it

ThorHoff · 13 April 2020, 21:11:53

Hallo

Ich habe ein dickes Problem.
Der Assistant hat immer funktioniert; im Moment ist er nicht mehr nutzbar

Ich hatte zuerst massive Probleme mit der ganzen FHEM-Installation.

Ich stellte daraufhin fest, das der fhem-connect Prozess beim Einschalten immer mehr Speicher allokierte und irgendwann...nach ein paar Minuten...war der raspi nur noch am swappen
Daraufhin nahm ich etliche Geräte aus dem gassistent-Raum heraus - Ohne das sich das Verhalten änderte;
reboot des raspi brachte auch nichts.

Seltsamerweise werden im log die Geräte angezeigt, die ich bereits herausgenommen hatte

Bitte um Hilfe

Grüße

Thorsten

anbei das log:

Code Auswählen


[2020-4-13 20:20:31] using ./gassistant-fhem.cfg
[2020-4-13 20:20:31] ---
[2020-4-13 20:20:31] config:
{"connections":[{"server":"127.0.0.1","webname":"fhem","name":"FHEM","port":"8083","auth":{"user":"xxxxxx","pass":"xxxxxxx"},"filter":"room=GoogleAssistant"}],"gassistant":{"description":"FHEM Connect"}}

[2020-4-13 20:20:31] ---
[2020-4-13 20:20:31] Google Assistant FHEM Connect 1.3.5 started
[2020-4-13 20:20:31] Fetching FHEM connections...
[2020-4-13 20:20:31] [FHEM] starting longpoll: https://127.0.0.1:8083/fhem?XHR=1&inform=type=status;addglobal=1;filter=.*;since=null;fmt=JSON×tamp=1586802031277
[2020-4-13 20:20:32] [FHEM]   executing: https://127.0.0.1:8083/fhem?cmd=jsonlist2%20TYPE%3Dgassistant&fwcsrf=csrf_10257330484554e15&XHR=1
[2020-4-13 20:20:32] [FHEM] FHEM Google Assistant device detected: gassistant
[2020-4-13 20:20:32] [FHEM]   executing: https://127.0.0.1:8083/fhem?cmd=setreading%20gassistant%20gassistant-fhem-version%201.3.5&fwcsrf=csrf_10257330484554e15&XHR=1
[2020-4-13 20:20:32] [FHEM]   executing: https://127.0.0.1:8083/fhem?cmd=set%20gassistant%20loginURL%20https%3A%2F%2Ffhemconnector.eu.auth0.com%2Fauthorize%3Faudience%3Dhttps%3A%2F%2Feurope-west1-fhem-ga-connector.cloudfunctions.net%2F%26scope%3Doffline_access%2520openid%2520profile%26response_type%3Dcode%26client_id%3DEI0TI2Y0W1743Ico53Nvsg1FsmoZniCC%26code_challenge%3DdPPPKw0_wtn__fU3Ouea-HeLO-za_i025M-JCobW9aw%26code_challenge_method%3DS256%26redirect_uri%3Dhttps%3A%2F%2Feurope-west1-fhem-ga-connector.cloudfunctions.net%2Fcodelanding%2Fstart&fwcsrf=csrf_10257330484554e15&XHR=1
[2020-4-13 20:20:32] [FHEM] Get refresh token...
[2020-4-13 20:20:32] [FHEM]   executing: https://127.0.0.1:8083/fhem?cmd=get%20gassistant%20refreshToken&fwcsrf=csrf_10257330484554e15&XHR=1
[2020-4-13 20:20:33] [FHEM]   executing: https://127.0.0.1:8083/fhem?cmd=setreading%20gassistant%20gassistant-fhem-connection%20connecting...&fwcsrf=csrf_10257330484554e15&XHR=1
[2020-4-13 20:20:33] [FHEM] Found refresh token in reading
[2020-4-13 20:20:33] [FHEM]   executing: https://127.0.0.1:8083/fhem?cmd=setreading%20gassistant%20gassistant-fhem-versionAvailable%203.0.0&fwcsrf=csrf_10257330484554e15&XHR=1
[2020-4-13 20:20:36] Refresh tokens finished. Next refresh in 86400 seconds.
[2020-4-13 20:20:36] [FHEM] refreshAllTokens executed
[2020-4-13 20:20:36] [FHEM] Fetching FHEM devices...
[2020-4-13 20:20:36] [FHEM] fetching: https://127.0.0.1:8083/fhem?cmd=jsonlist2%20room=GoogleAssistant&fwcsrf=csrf_10257330484554e15&XHR=1
[2020-4-13 20:20:37] [FHEM] start connection executed
[2020-4-13 20:20:37] [FHEM]   executing: https://127.0.0.1:8083/fhem?cmd=setreading%20gassistant%20gassistant-fhem-lasterror%20none&fwcsrf=csrf_10257330484554e15&XHR=1
[2020-4-13 20:20:37] [FHEM] Checking devices and attributes...
[2020-4-13 20:20:37] [FHEM]   executing: https://127.0.0.1:8083/fhem?cmd=%7BAttrVal(%22global%22%2C%22userattr%22%2C%22%22)%7D&fwcsrf=csrf_10257330484554e15&XHR=1
(node:11472) DeprecationWarning: grpc.load: Use the @grpc/proto-loader module with grpc.loadPackageDefinition instead
[2020-4-13 20:20:38] SERVER FeatureLevel:{"featurelevel":3,"changelog":"performance optimizations"}
[2020-4-13 20:20:38] SYNC   FeatureLevel:{"featurelevel":3}
[2020-4-13 20:20:42] GOOGLE MSG RECEIVED: {"log":"No mappings defined for device WZ_Dimmer_Sitzbereich","msg":"LOG_ERROR","ts":1586697623800}
[2020-4-13 20:20:42] Received firestore2fhem: {"log":"No mappings defined for device WZ_Dimmer_Sitzbereich","msg":"LOG_ERROR","ts":1586697623800}
[2020-4-13 20:20:42] [FHEM]   executing: https://127.0.0.1:8083/fhem?cmd=setreading%20gassistant%20gassistant-fhem-lastServerError%20No%20mappings%20defined%20for%20device%20WZ_Dimmer_Sitzbereich&fwcsrf=csrf_10257330484554e15&XHR=1
[2020-4-13 20:20:42] GOOGLE MSG RECEIVED: {"log":"Error with device Wandtaster","msg":"LOG_ERROR","ts":1585116227555}
[2020-4-13 20:20:42] Received firestore2fhem: {"log":"Error with device Wandtaster","msg":"LOG_ERROR","ts":1585116227555}
[2020-4-13 20:20:42] [FHEM]   executing: https://127.0.0.1:8083/fhem?cmd=setreading%20gassistant%20gassistant-fhem-lastServerError%20Error%20with%20device%20Wandtaster&fwcsrf=csrf_10257330484554e15&XHR=1
[2020-4-13 20:20:42] GOOGLE MSG RECEIVED: {"log":"Error with device Wandtaster","msg":"LOG_ERROR","ts":1585246263041}
[2020-4-13 20:20:42] Received firestore2fhem: {"log":"Error with device Wandtaster","msg":"LOG_ERROR","ts":1585246263041}
[2020-4-13 20:20:42] [FHEM]   executing: https://127.0.0.1:8083/fhem?cmd=setreading%20gassistant%20gassistant-fhem-lastServerError%20Error%20with%20device%20Wandtaster&fwcsrf=csrf_10257330484554e15&XHR=1
[2020-4-13 20:20:42] GOOGLE MSG RECEIVED: {"log":"Error with device TH_OG_Schalter","msg":"LOG_ERROR","ts":1585160756504}
[2020-4-13 20:20:42] Received firestore2fhem: {"log":"Error with device TH_OG_Schalter","msg":"LOG_ERROR","ts":1585160756504}
[2020-4-13 20:20:42] [FHEM]   executing: https://127.0.0.1:8083/fhem?cmd=setreading%20gassistant%20gassistant-fhem-lastServerError%20Error%20with%20device%20TH_OG_Schalter&fwcsrf=csrf_10257330484554e15&XHR=1
[2020-4-13 20:20:42] GOOGLE MSG RECEIVED: {"log":"Error with device Flur_Keller_Schalter","msg":"LOG_ERROR","ts":1585247376498}
[2020-4-13 20:20:42] Received firestore2fhem: {"log":"Error with device Flur_Keller_Schalter","msg":"LOG_ERROR","ts":1585247376498}
[2020-4-13 20:20:42] [FHEM]   executing: https://127.0.0.1:8083/fhem?cmd=setreading%20gassistant%20gassistant-fhem-lastServerError%20Error%20with%20device%20Flur_Keller_Schalter&fwcsrf=csrf_10257330484554e15&XHR=1
[2020-4-13 20:20:42] GOOGLE MSG RECEIVED: {"log":"Error with device TH_OG_Schalter","msg":"LOG_ERROR","ts":1585128757461}
[2020-4-13 20:20:42] Received firestore2fhem: {"log":"Error with device TH_OG_Schalter","msg":"LOG_ERROR","ts":1585128757461}
[2020-4-13 20:20:42] [FHEM]   executing: https://127.0.0.1:8083/fhem?cmd=setreading%20gassistant%20gassistant-fhem-lastServerError%20Error%20with%20device%20TH_OG_Schalter&fwcsrf=csrf_10257330484554e15&XHR=1
[2020-4-13 20:20:42] GOOGLE MSG RECEIVED: {"log":"Error with device Keller_Licht_schalten","msg":"LOG_ERROR","ts":1585247383166}
[2020-4-13 20:20:42] Received firestore2fhem: {"log":"Error with device Keller_Licht_schalten","msg":"LOG_ERROR","ts":1585247383166}
[2020-4-13 20:20:42] [FHEM]   executing: https://127.0.0.1:8083/fhem?cmd=setreading%20gassistant%20gassistant-fhem-lastServerError%20Error%20with%20device%20Keller_Licht_schalten&fwcsrf=csrf_10257330484554e15&XHR=1
[2020-4-13 20:20:42] GOOGLE MSG RECEIVED: {"log":"Error with device Flur_Keller_Schalter","msg":"LOG_ERROR","ts":1585201299662}
[2020-4-13 20:20:42] Received firestore2fhem: {"log":"Error with device Flur_Keller_Schalter","msg":"LOG_ERROR","ts":1585201299662}
[2020-4-13 20:20:42] [FHEM]   executing: https://127.0.0.1:8083/fhem?cmd=setreading%20gassistant%20gassistant-fhem-lastServerError%20Error%20with%20device%20Flur_Keller_Schalter&fwcsrf=csrf_10257330484554e15&XHR=1
[2020-4-13 20:20:42] GOOGLE MSG RECEIVED: {"log":"Error with device WZ_Dimmer_Esstisch","msg":"LOG_ERROR","ts":1585247699755}
[2020-4-13 20:20:42] Received firestore2fhem: {"log":"Error with device WZ_Dimmer_Esstisch","msg":"LOG_ERROR","ts":1585247699755}
[2020-4-13 20:20:42] [FHEM]   executing: https://127.0.0.1:8083/fhem?cmd=setreading%20gassistant%20gassistant-fhem-lastServerError%20Error%20with%20device%20WZ_Dimmer_Esstisch&fwcsrf=csrf_10257330484554e15&XHR=1
[2020-4-13 20:20:42] GOOGLE MSG RECEIVED: {"log":"Error with device WZ_Dimmer_Esstisch","msg":"LOG_ERROR","ts":1585007037163}
[2020-4-13 20:20:42] Received firestore2fhem: {"log":"Error with device WZ_Dimmer_Esstisch","msg":"LOG_ERROR","ts":1585007037163}
[2020-4-13 20:20:42] [FHEM]   executing: https://127.0.0.1:8083/fhem?cmd=setreading%20gassistant%20gassistant-fhem-lastServerError%20Error%20with%20device%20WZ_Dimmer_Esstisch&fwcsrf=csrf_10257330484554e15&XHR=1
[2020-4-13 20:20:42] GOOGLE MSG RECEIVED: {"log":"Error with device TH_OG_Schalter","msg":"LOG_ERROR","ts":1585074288139}
[2020-4-13 20:20:42] Received firestore2fhem: {"log":"Error with device TH_OG_Schalter","msg":"LOG_ERROR","ts":1585074288139}
[2020-4-13 20:20:42] [FHEM]   executing: https://127.0.0.1:8083/fhem?cmd=setreading%20gassistant%20gassistant-fhem-lastServerError%20Error%20with%20device%20TH_OG_Schalter&fwcsrf=csrf_10257330484554e15&XHR=1
[2020-4-13 20:20:42] GOOGLE MSG RECEIVED: {"log":"Error with device Flur_Keller_Schalter","msg":"LOG_ERROR","ts":1585286204994}
[2020-4-13 20:20:42] Received firestore2fhem: {"log":"Error with device Flur_Keller_Schalter","msg":"LOG_ERROR","ts":1585286204994}
[2020-4-13 20:20:42] [FHEM]   executing: https://127.0.0.1:8083/fhem?cmd=setreading%20gassistant%20gassistant-fhem-lastServerError%20Error%20with%20device%20Flur_Keller_Schalter&fwcsrf=csrf_10257330484554e15&XHR=1

dominik · 13 April 2020, 21:15:59

Da hat sich serverseitig einiges an Fehlern angesammelt die kun an den Client geschickt werden. Ich bin noch dran das ordentlich zu beheben.

Bis dahin, schick mir eine kurze PN mit deiner gassistant-fhem-uid dann kann ich die Fehler in der DB löschen.

DerRecke · 13 April 2020, 21:19:17

Ich benutze den gassistant um Geräte zu steuern die via hmccu angebunden sind. Nach einem shutdown restart sind die Lampen alle nicht mehr ansteuerbar. Nach einem set ZE_GAssistant reload geht wieder alles.

Basierend auf den Log-Dateien vermute ich, dass es damit zusammen hängt, dass beim Restart gassistant deutlich eher startet als hmccu und dadurch Infos über die Geräte fehlen (No mappings (e.g. on/off) found for XXX)

Kann man da Abhilfe schaffen?

Hier meine fhem.cfg in Auszügen:

Code Auswählen


...
define ZE_CCU2 HMCCU 192.168.XXX.XXX
setuuid ZE_CCU2 XXXX-XXX-XXX-XXX-XXX
attr ZE_CCU2 room Zentralen
attr ZE_CCU2 rpcinterfaces BidCos-RF,CUxD,HmIP-RF
attr ZE_CCU2 rpcinterval 2
attr ZE_CCU2 rpcport 2001,8701,2010
attr ZE_CCU2 rpcserver on
attr ZE_CCU2 stateFormat rpcstate/state
...
define ZE_GAssistant gassistant
setuuid ZE_GAssistant XXXX-XXX-XXX-XXX-XXX
attr ZE_GAssistant devStateIcon stopped:control_home@red:start stopping:control_on_off@orange running.*:control_on_off@green:stop
attr ZE_GAssistant gassistantFHEM-config ./gassistant-fhem.cfg
attr ZE_GAssistant gassistantFHEM-log ./log/gassistant-%Y-%m-%d.log
attr ZE_GAssistant nrarchive 10
attr ZE_GAssistant room Zentralen
attr ZE_GAssistant stateFormat gassistant-fhem
...

Und die Auszüge aus der FHEM Logdatei aus der ich die Vermutung entnehme, dass gassistant deutlich vor hmccu startet:

Code Auswählen


2020.04.13 20:42:19 3: FHEMWEB WEB CSRF error: csrf_760958354096699 ne csrf_213217539204003 for client WEB_192.168.135.118_51020 / command shutdown restart. For details see the csrfToken FHEMWEB attribute.
2020.04.13 20:42:19 1: HMCCU: [ZE_CCU2 : 31182] Graceful shutdown in 8 seconds
2020.04.13 20:42:19 1: HMCCU: Deregistering RPC server http://192.168.XXX.XXX:7411/fh2001 at http://192.168.XXX.XXX:2001
2020.04.13 20:42:19 1: HMCCU: Deregistering RPC server http://192.168.XXX.XXX:7420/fh2010 at http://192.168.XXX.XXX:2010
2020.04.13 20:42:19 0: HMCCU: Stopping RPC server CB2001 with PID 31261
2020.04.13 20:42:19 0: HMCCU: Stopping RPC server CB2010 with PID 31262
2020.04.13 20:42:19 0: CCURPC: CB2001 Server loop terminated
2020.04.13 20:42:19 0: CCURPC: CB2010 Server loop terminated
2020.04.13 20:42:19 2: CCURPC: Eventcount DD = 0
2020.04.13 20:42:19 2: CCURPC: Eventcount EV = 0
2020.04.13 20:42:19 2: CCURPC: Eventcount EX = 1
2020.04.13 20:42:19 2: CCURPC: Eventcount IN = 1
2020.04.13 20:42:19 2: CCURPC: Eventcount ND = 52
2020.04.13 20:42:19 2: CCURPC: Eventcount RA = 0
2020.04.13 20:42:19 2: CCURPC: Eventcount RD = 0
2020.04.13 20:42:19 2: CCURPC: Eventcount SL = 1
2020.04.13 20:42:19 2: CCURPC: Eventcount UD = 0
2020.04.13 20:42:19 2: CCURPC: Eventcount total = 55
2020.04.13 20:42:19 2: CCURPC: Eventcount writeerror = 0
2020.04.13 20:42:19 2: CCURPC: Eventcount DD = 0
2020.04.13 20:42:19 2: CCURPC: Eventcount EV = 1090
2020.04.13 20:42:19 2: CCURPC: Eventcount EX = 1
2020.04.13 20:42:19 2: CCURPC: Eventcount IN = 1
2020.04.13 20:42:19 2: CCURPC: Eventcount ND = 197
2020.04.13 20:42:19 2: CCURPC: Eventcount RA = 0
2020.04.13 20:42:19 2: CCURPC: Eventcount RD = 0
2020.04.13 20:42:19 2: CCURPC: Eventcount SL = 1
2020.04.13 20:42:19 2: CCURPC: Eventcount ST = 2
2020.04.13 20:42:19 2: CCURPC: Eventcount UD = 0
2020.04.13 20:42:19 2: CCURPC: Eventcount total = 1292
2020.04.13 20:42:19 2: CCURPC: Eventcount writeerror = 0
2020.04.13 20:42:19 1: HMCCU: [ZE_CCU2 : 31182] All RPC servers stopping
2020.04.13 20:42:21 1: Server shutdown delayed due to ZE_GAssistant,ZE_CCU2 for max 10 sec
2020.04.13 20:42:21 0: HMCCU: Received EX event. RPC server CB2001 terminated.
2020.04.13 20:42:21 0: HMCCU: Received EX event. RPC server CB2010 terminated.
2020.04.13 20:42:21 1: HMCCU: [ZE_CCU2 : 31182] All RPC servers inactive
2020.04.13 20:42:21 0: HMCCU: RPC server(s) with PID(s) 31261,31262 shut down. f=1
2020.04.13 20:42:21 3: HMCCU: Eventcount DD = 0
2020.04.13 20:42:21 3: HMCCU: Eventcount EV = 1090
2020.04.13 20:42:21 3: HMCCU: Eventcount EX = 2
2020.04.13 20:42:21 3: HMCCU: Eventcount IN = 2
2020.04.13 20:42:21 3: HMCCU: Eventcount ND = 249
2020.04.13 20:42:21 3: HMCCU: Eventcount RA = 0
2020.04.13 20:42:21 3: HMCCU: Eventcount RD = 0
2020.04.13 20:42:21 3: HMCCU: Eventcount SL = 2
2020.04.13 20:42:21 3: HMCCU: Eventcount ST = 2
2020.04.13 20:42:21 3: HMCCU: Eventcount UD = 0
2020.04.13 20:42:21 3: HMCCU: Eventcount total = 1347
2020.04.13 20:42:21 0: HMCCU: Periodical check found no RPC Servers
2020.04.13 20:42:21 0: HMCCU: All RPC servers stopped
2020.04.13 20:42:21 0: HMCCU: Periodical check found no RPC Servers
2020.04.13 20:42:21 0: HMCCU: All RPC servers stopped
2020.04.13 20:42:21 3: ZE_GAssistant: read: end of file reached while sysread
2020.04.13 20:42:21 3: ZE_GAssistant: stopped
2020.04.13 20:42:31 0: Server shutdown
2020.04.13 20:42:31 1: HMCCU: [ZE_CCU2 : 31182] Graceful shutdown
2020.04.13 20:42:37 1: Including fhem.cfg
2020.04.13 20:42:37 3: telnetPort: port 7072 opened
2020.04.13 20:42:38 3: WEB: port 8083 opened
2020.04.13 20:42:38 2: eventTypes: loaded 5112 events from ./log/eventTypes.txt
2020.04.13 20:42:39 1: HMCCU: [ZE_CCU2 : 5224] Initialized version 4.3.023
2020.04.13 20:42:39 1: HMCCU: [ZE_CCU2 : 5224] HMCCU: Initializing device
2020.04.13 20:42:41 1: HMCCU: [ZE_CCU2 : 5224] HMCCU: Read 52 devices with 277 channels from CCU 192.168.XXX.XXX
2020.04.13 20:42:41 1: HMCCU: [ZE_CCU2 : 5224] HMCCU: Read 4 interfaces from CCU 192.168.XXX.XXX
2020.04.13 20:42:41 1: HMCCU: [ZE_CCU2 : 5224] HMCCU: Read 28 programs from CCU 192.168.XXX.XXX
2020.04.13 20:42:41 1: HMCCU: [ZE_CCU2 : 5224] HMCCU: Read 0 virtual groups from CCU 192.168.XXX.XXX
2020.04.13 20:42:45 3: GOOGLECAST: GoogleCast v2.1.4
2020.04.13 20:42:45 3: GOOGLECAST: DiersHome initializing...
2020.04.13 20:42:45 3: GOOGLECAST: DiersChromeCast initializing...
2020.04.13 20:42:45 3: Tado module initialized.
2020.04.13 20:42:45 3: Tado_Define ZE_TadoBridge: called 
2020.04.13 20:42:45 1: New Tado Home defined. Id: 9932 Name: Familie_Diers
2020.04.13 20:42:45 1: Tado_Define ZE_TadoBridge: Starting timer with interval 120
2020.04.13 20:42:45 3: TadoDevice module initialized.
2020.04.13 20:42:45 3: TadoDevice_Define KG_Gaestezimmer2_Heizung: called 
2020.04.13 20:42:45 3: Tado KG_Gaestezimmer2_Heizung: I/O device is ZE_TadoBridge
2020.04.13 20:42:45 3: Device Code is: ZE_TadoBridge-2
2020.04.13 20:42:46 3: [STV] You are using a deprecated MAC detection mechanism using ifconfig.
2020.04.13 20:42:46 3: [STV] Please install Pearl Modules libnet-address-ip-local-perl and libio-interface-perl
2020.04.13 20:42:46 3: TadoDevice_Define EG_Wohnen_Heizung: called 
2020.04.13 20:42:46 3: Tado EG_Wohnen_Heizung: I/O device is ZE_TadoBridge
2020.04.13 20:42:46 3: Device Code is: ZE_TadoBridge-1
2020.04.13 20:42:46 3: TadoDevice_Define EG_Bad_Heizung: called 
2020.04.13 20:42:46 3: Tado EG_Bad_Heizung: I/O device is ZE_TadoBridge
2020.04.13 20:42:46 3: Device Code is: ZE_TadoBridge-6
2020.04.13 20:42:46 3: TadoDevice_Define DG_Jonas_Heizung: called 
2020.04.13 20:42:46 3: Tado DG_Jonas_Heizung: I/O device is ZE_TadoBridge
2020.04.13 20:42:46 3: Device Code is: ZE_TadoBridge-4
2020.04.13 20:42:46 3: TadoDevice_Define DG_MaxSchlafen_Heizung: called 
2020.04.13 20:42:46 3: Tado DG_MaxSchlafen_Heizung: I/O device is ZE_TadoBridge
2020.04.13 20:42:46 3: Device Code is: ZE_TadoBridge-5
2020.04.13 20:42:46 3: TadoDevice_Define DG_Bad_Heizung: called 
2020.04.13 20:42:46 3: Tado DG_Bad_Heizung: I/O device is ZE_TadoBridge
2020.04.13 20:42:46 3: Device Code is: ZE_TadoBridge-3
2020.04.13 20:42:46 1: Including ./log/fhem.save
2020.04.13 20:42:46 1: Messages collected while initializing FHEM:SecurityCheck:
  WEB is not password protected

Protect this FHEM installation by configuring the allowed device allowed_telnetPort
You can disable this message with attr global motd none

2020.04.13 20:42:46 0: HMCCU: Start of RPC server after FHEM initialization in 12 seconds
2020.04.13 20:42:46 2: ZE_GAssistant: starting gassistant-fhem: /usr/bin/gassistant-fhem -c ./gassistant-fhem.cfg
2020.04.13 20:42:46 3: ZE_GAssistant: starting
2020.04.13 20:42:46 3: ZE_GAssistant: using logfile: ./log/gassistant-2020-04-13.log
2020.04.13 20:42:47 1: usb create starting
2020.04.13 20:42:48 3: Probing ZWDongle device /dev/serial1
2020.04.13 20:42:48 3: Probing CUL device /dev/ttyAMA0
2020.04.13 20:42:48 3: Probing TCM_ESP3 device /dev/ttyAMA0
2020.04.13 20:42:48 3: Probing ZWDongle device /dev/ttyAMA0
2020.04.13 20:42:48 3: Probing SIGNALDuino device /dev/ttyAMA0
2020.04.13 20:42:49 3: Probing MYSENSORS device /dev/ttyAMA0
2020.04.13 20:42:49 3: Probing ArduCounter device /dev/ttyAMA0
2020.04.13 20:42:49 3: Probing ElsnerWS device /dev/ttyAMA0
2020.04.13 20:42:50 3: Probing FRM device /dev/ttyAMA0
2020.04.13 20:42:55 1: usb create end
2020.04.13 20:42:55 0: Featurelevel: 6
2020.04.13 20:42:55 0: Server started with 79 defined entities (fhem.pl:21647/2020-04-12 perl:5.024001 os:linux user:fhem pid:5224)
2020.04.13 20:42:55 3: telnetForBlockingFn_1586803375: port 38619 opened
2020.04.13 20:42:55 3: GOOGLECAST: DiersHome initialized successfully
2020.04.13 20:42:55 2: AttrTemplates: got 169 entries
2020.04.13 20:42:58 1: HMCCU: [ZE_CCU2 : 5224] Internal RPC server is depricated and will be removed soon. Set ccuflags to procrpc
2020.04.13 20:42:58 2: HMCCU: Create child process with timeouts 0.01 and 0.25
2020.04.13 20:42:58 0: HMCCU: Child process for server CB2001 started with PID 5303
2020.04.13 20:42:58 0: CCURPC: CB2001 Creating file queue /tmp/ccuqueue_2001_1
2020.04.13 20:42:58 0: CCURPC: Initializing RPC server CB2001
2020.04.13 20:42:58 2: HMCCU: Create child process with timeouts 0.01 and 0.25
2020.04.13 20:42:58 0: HMCCU: Child process for server CB2010 started with PID 5304
2020.04.13 20:42:58 0: CCURPC: CB2010 Creating file queue /tmp/ccuqueue_2010_1
2020.04.13 20:42:58 0: CCURPC: Initializing RPC server CB2010
2020.04.13 20:42:58 1: HMCCU: [ZE_CCU2 : 5224] All RPC servers starting
2020.04.13 20:42:58 0: HMCCU: [ZE_CCU2] RPC server(s) starting
2020.04.13 20:42:59 0: CCURPC: Callback server created listening on port 7411
2020.04.13 20:42:59 1: CCURPC: CB2001 Adding callback for events
2020.04.13 20:42:59 1: CCURPC: CB2001 Adding callback for new devices
2020.04.13 20:42:59 1: CCURPC: CB2001 Adding callback for deleted devices
2020.04.13 20:42:59 1: CCURPC: CB2001 Adding callback for modified devices
2020.04.13 20:42:59 1: CCURPC: CB2001 Adding callback for replaced devices
2020.04.13 20:42:59 1: CCURPC: CB2001 Adding callback for readded devices
2020.04.13 20:42:59 1: CCURPC: CB2001 Adding callback for list devices
2020.04.13 20:42:59 0: CCURPC: CB2001 Entering server loop
2020.04.13 20:42:59 0: CCURPC: Callback server created listening on port 7420
2020.04.13 20:42:59 1: CCURPC: CB2010 Adding callback for events
2020.04.13 20:42:59 1: CCURPC: CB2010 Adding callback for new devices
2020.04.13 20:42:59 1: CCURPC: CB2010 Adding callback for deleted devices
2020.04.13 20:42:59 1: CCURPC: CB2010 Adding callback for modified devices
2020.04.13 20:42:59 1: CCURPC: CB2010 Adding callback for replaced devices
2020.04.13 20:42:59 1: CCURPC: CB2010 Adding callback for readded devices
2020.04.13 20:42:59 1: CCURPC: CB2010 Adding callback for list devices
2020.04.13 20:42:59 0: CCURPC: CB2010 Entering server loop
2020.04.13 20:43:01 3: After Updating zones: $VAR1 = '1, 6, 3, 5, 2, 4';

2020.04.13 20:43:01 0: HMCCU: Received SL event. RPC server CB2001 enters server loop
2020.04.13 20:43:01 0: HMCCU: Received SL event. RPC server CB2010 enters server loop
2020.04.13 20:43:08 1: HMCCU: Registering callback http://192.168.XXX.XXX:7411/fh2001 with ID CB2001 at http://192.168.XXX.XXX:2001
2020.04.13 20:43:08 1: CCURPC: CB2001 ListDevices. Sending init to HMCCU
2020.04.13 20:43:08 1: HMCCU: RPC callback with URL http://192.168.XXX.XXX:7411/fh2001 initialized
2020.04.13 20:43:08 1: HMCCU: Registering callback http://192.168.XXX.XXX:7420/fh2010 with ID CB2010 at http://192.168.XXX.XXX:2010
2020.04.13 20:43:08 1: HMCCU: RPC callback with URL http://192.168.XXX.XXX:7420/fh2010 initialized
2020.04.13 20:43:08 1: CCURPC: CB2010 ListDevices. Sending init to HMCCU
2020.04.13 20:43:09 2: CCURPC: CB2001 NewDevice received 197 device specifications
2020.04.13 20:43:09 2: CCURPC: CB2010 NewDevice received 52 device specifications
2020.04.13 20:43:10 0: HMCCU: Received IN event. RPC server CB2001 initialized.
2020.04.13 20:43:10 0: HMCCU: Received IN event. RPC server CB2010 initialized.
2020.04.13 20:43:10 1: HMCCU: [ZE_CCU2 : 5224] All RPC servers running
2020.04.13 20:43:10 2: HMCCU: [ZE_CCU2 : 5224] Updating 40 of 40 client devices matching devexp=.* filter=ccudevstate=active
2020.04.13 20:43:12 2: HMCCU: [ZE_CCU2 : 5224] Update success=40 failed=0

Last but not least der entsprechende Auszug aus der gassistant Log-Datei

Code Auswählen


[2020-4-13 20:42:21] Got SIGTERM, shutting down...
[2020-4-13 20:42:21] [FHEM]   executing: http://127.0.0.1:8083/fhem?cmd=setreading%20ZE_GAssistant%20gassistant-fhem-connection%20disconnected&fwcsrf=csrf_213217539204003&XHR=1
Loading cli.js...
Loading version.js...
Loading server.js...
Loading user.js...
Loading logger.js...
Loading fhem.js...
Loading database.js...
Loading localhandleQUERY.js...
Loading utils.js...
Loading localserver.js...
Loading localhandleEXECUTE.js...
[2020-4-13 20:42:53] using ./gassistant-fhem.cfg
[2020-4-13 20:42:53] ---
[2020-4-13 20:42:53] config:
{"connections":[{"name":"FHEM","port":"8083","webname":"fhem","filter":"room=GoogleAssistant","server":"127.0.0.1"}],"gassistant":{"description":"FHEM Connect"}}
[2020-4-13 20:42:53] ---
[2020-4-13 20:42:53] Google Assistant FHEM Connect 3.0.0 started
[2020-4-13 20:42:53] Fetching FHEM connections...
[2020-4-13 20:42:53] [FHEM] starting longpoll: http://127.0.0.1:8083/fhem?XHR=1&inform=type=status;addglobal=1;filter=.*;since=null;fmt=JSON&timestamp=1586803373946
[2020-4-13 20:42:55] [FHEM]   executing: http://127.0.0.1:8083/fhem?cmd=jsonlist2%20TYPE%3Dgassistant&fwcsrf=csrf_473166862284324&XHR=1
[2020-4-13 20:42:55] [FHEM] FHEM Google Assistant device detected: ZE_GAssistant
[2020-4-13 20:42:55] [FHEM]   executing: http://127.0.0.1:8083/fhem?cmd=setreading%20ZE_GAssistant%20gassistant-fhem-version%203.0.0&fwcsrf=csrf_473166862284324&XHR=1
[2020-4-13 20:42:55] [FHEM]   executing: http://127.0.0.1:8083/fhem?cmd=setreading%20ZE_GAssistant%20gassistant-fhem-lastServerError%20none&fwcsrf=csrf_473166862284324&XHR=1
[2020-4-13 20:42:55] [FHEM]   executing: http://127.0.0.1:8083/fhem?cmd=set%20ZE_GAssistant%20loginURL%20https%3A%2F%2Ffhemconnector.eu.auth0.com%2Fauthorize%3Faudience%3Dhttps%3A%2F%2Feurope-west1-fhem-ga-connector.cloudfunctions.net%2F%26scope%3Doffline_access%2520openid%2520profile%26response_type%3Dcode%26client_id%3DEI0TI2Y0W1743Ico53Nvsg1FsmoZniCC%26code_challenge%3Db6fA0CSumaOM0UVmFj7jf35EjRCaceGnN8GJHBZye3k%26code_challenge_method%3DS256%26redirect_uri%3Dhttps%3A%2F%2Feurope-west1-fhem-ga-connector.cloudfunctions.net%2Fcodelanding%2Fstart&fwcsrf=csrf_473166862284324&XHR=1
[2020-4-13 20:42:55] [FHEM] Get refresh token...
[2020-4-13 20:42:55] [FHEM]   executing: http://127.0.0.1:8083/fhem?cmd=get%20ZE_GAssistant%20refreshToken&fwcsrf=csrf_473166862284324&XHR=1
[2020-4-13 20:42:56] [FHEM]   executing: http://127.0.0.1:8083/fhem?cmd=setreading%20ZE_GAssistant%20gassistant-fhem-connection%20connecting...&fwcsrf=csrf_473166862284324&XHR=1
[2020-4-13 20:42:56] [FHEM] Found refresh token in reading
[2020-4-13 20:42:56] [FHEM]   executing: http://127.0.0.1:8083/fhem?cmd=setreading%20ZE_GAssistant%20gassistant-fhem-versionAvailable%203.0.0&fwcsrf=csrf_473166862284324&XHR=1
[2020-4-13 20:42:57] Refresh tokens finished. Next refresh in 86400 seconds.
[2020-4-13 20:42:57] [FHEM] refreshAllTokens executed
[2020-4-13 20:42:59] Start Connection and listen for Firebase
[2020-4-13 20:42:59] [FHEM]   executing: http://127.0.0.1:8083/fhem?cmd=setreading%20ZE_GAssistant%20gassistant-fhem-localHome%20inactive&fwcsrf=csrf_473166862284324&XHR=1
[2020-4-13 20:42:59] [LOCAL] FHEM Connect Google local home server running on port 37000
[2020-4-13 20:42:59] [FHEM] Fetching FHEM devices...
[2020-4-13 20:42:59] [FHEM] fetching: http://127.0.0.1:8083/fhem?cmd=jsonlist2%20room=GoogleAssistant&fwcsrf=csrf_473166862284324&XHR=1
[2020-4-13 20:43:00] [FHEM]   executing: http://127.0.0.1:8083/fhem?cmd=setreading%20ZE_GAssistant%20gassistant-fhem-lasterror%20none&fwcsrf=csrf_473166862284324&XHR=1
[2020-4-13 20:43:00] [FHEM] Checking devices and attributes...
[2020-4-13 20:43:00] [FHEM]   executing: http://127.0.0.1:8083/fhem?cmd=%7BAttrVal(%22global%22%2C%22userattr%22%2C%22%22)%7D&fwcsrf=csrf_473166862284324&XHR=1
[2020-4-13 20:43:00] [FHEM] Connection: OK
[2020-4-13 20:43:00] [FHEM] got: 28 results
[2020-4-13 20:43:01] SERVER FeatureLevel:{"featurelevel":3,"changelog":"performance optimizations"}
[2020-4-13 20:43:01] SYNC   FeatureLevel:{"featurelevel":3}
[2020-4-13 20:43:03] [FHEM] Supported Google Device Types: ac_unit,aircondition,airfreshener,airpurifier,awning,bathtub,bed,blender,blinds,boiler,camera,carbon_monoxide_detector,charger,closet,coffee_maker,coffeemaker,cooktop,curtain,dehumidifier,dehydrator,dishwasher,door,drawer,dryer,fan,faucet,fireplace,fryer,garage,gate,grill,heater,hood,humidifier,kettle,light,lock,remotecontrol,mop,mower,microwave,multicooker,outlet,oven,pergola,petfeeder,pressurecooker,radiator,refrigerator,scene,securitysystem,settop,sensor,shutter,shower,smoke_detector,sousvide,sprinkler,standmixer,switch,tv,thermostat,vacuum,valve,washer,waterheater,waterpurifier,watersoftener,window,yogurtmaker
[2020-4-13 20:43:05] GOOGLE MSG RECEIVED: {"ts":1586803385208,"log":"No mappings (e.g. on/off) found for EG_Kueche_Licht","msg":"LOG_ERROR"}
[2020-4-13 20:43:05] Received firestore2fhem: {"ts":1586803385208,"log":"No mappings (e.g. on/off) found for EG_Kueche_Licht","msg":"LOG_ERROR"}
[2020-4-13 20:43:05] [FHEM]   executing: http://127.0.0.1:8083/fhem?cmd=setreading%20ZE_GAssistant%20gassistant-fhem-lastServerError%20No%20mappings%20(e.g.%20on%2Foff)%20found%20for%20EG_Kueche_Licht&fwcsrf=csrf_473166862284324&XHR=1
[2020-4-13 20:43:05] GOOGLE MSG RECEIVED: {"ts":1586803385208,"log":"No mappings (e.g. on/off) found for EG_Kueche_Licht","msg":"LOG_ERROR"}

dominik · 13 April 2020, 21:32:44

Hi,

danke für die ausführliche Analyse, ja, das hängt ziemlich sicher zusammen. Kannst du mir erklären wie das mit dem hmccu ist? Werden die Geräte nach einem Reboot von FHEM gelöscht und neu erstellt? Oder nur teilweise? Bringt es was, wenn du gassistant ganz ans Ende in der cfg schiebst?

erotikbaer · 13 April 2020, 23:42:21

unglaublich... es läuft...
folgendes brachte bei mir unter freenas 11.3 (Freebsd) Erfolg:
cd /usr/ports/devel/grpc/
make deinstall
pkg remove grpc
npm uninstall grpc
npm uninstall -g grpc --unsafe-perm
npm install request

dann
cd /tmp/
alle was nicht gebraucht wird aus diesem Verzeichnis löschen
npm pack gassistant-fhem

das heruntergeladene gassistant-fhem-3.0.0.tgz umbenennen in gassistant-fhem-edit-3.0.0.tgz
(ich habe das alles per winscp auf meinen win rechner geholt,mit 7zip geöffnet, editiert, gespeichert und wieder mit winscp zurückkopiert)
also das gassistant-fhem-edit-3.0.0.tgz öffnen und die enthaltene gassistant-fhem-3.0.0.tgz\gassistant-fhem-3.0.0.tar\package\package.json editieren.
ich musste bei mir folgendes ändern: neu: "grpc": "^1.22.0" , alt: ich glaube "grpc": "^1.24.1"
dann die Ändeurngen speichern und gegebenenfalls wieder zurückkopieren, falls ihr es wie ich mit winscp geholt habt.

cd /tmp/
npm install -g gassistant-fhem-edit-3.0.0.tgz --unsafe-perm

und bei mir lief es dann!

DANKE DANKE DANKE dominik!!! DANKE

a_quadrat · 14 April 2020, 11:26:10

Zitat von: dominik am 13 April 2020, 21:32:44
Hi,

danke für die ausführliche Analyse, ja, das hängt ziemlich sicher zusammen. Kannst du mir erklären wie das mit dem hmccu ist? Werden die Geräte nach einem Reboot von FHEM gelöscht und neu erstellt? Oder nur teilweise? Bringt es was, wenn du gassistant ganz ans Ende in der cfg schiebst?

Hi, ich nutze auch HMCCU für meine Homematic-Geräte. Bei mir funktioniert es ohne Probleme, auch nach einem restart. Wenn ihr von mir Informationen braucht, stehe ich gern zur Verfügung.

VG Andreas