Monatsrückblick Januar/Februar 2026 ist online!

[Marco Willi]

Log.txt

[Marco Willi]

@Thomas-Braun besser so?

[Thomas Braun]

@Marco-Willi
Nee. Entsprechenden Text markieren und dann das Icon </> anklicken.

[Marco Willi]

2020-11-11 20:45:43.328 - info: web.0 (1997) ==>Connected system.user.admin from ::ffff:192.168.1.154
2020-11-11 20:45:44.851 - info: web.0 (1997) <==Disconnect system.user.admin from ::ffff:192.168.1.154 vis.0
2020-11-11 20:45:46.220 - info: web.0 (1997) ==>Connected system.user.admin from ::ffff:192.168.1.154
2020-11-11 20:45:51.888 - info: web.0 (1997) <==Disconnect system.user.admin from ::ffff:192.168.1.154 vis.0
2020-11-11 20:45:52.490 - info: web.0 (1997) ==>Connected system.user.admin from ::ffff:192.168.1.154
2020-11-11 20:45:58.741 - info: web.0 (1997) <==Disconnect system.user.admin from ::ffff:192.168.1.154 vis.0
2020-11-11 20:46:38.826 - info: host.raspberrypi "system.adapter.iot.0" enabled
2020-11-11 20:46:38.864 - info: host.raspberrypi instance system.adapter.iot.0 started with pid 25632
2020-11-11 20:46:40.925 - info: iot.0 (25632) starting. Version 1.5.3 in /opt/iobroker/node_modules/iobroker.iot, node: v12.19.0, js-controller: 3.1.6
2020-11-11 20:46:40.965 - info: iot.0 (25632) Connecting with a18wym7vjdl22g.iot.eu-west-1.amazonaws.com
2020-11-11 20:46:41.560 - info: iot.0 (25632) Connection changed: connect
2020-11-11 20:46:41.629 - error: iot.0 (25632) [GHOME] Url Key error. Google Request and Response are working. But device states are not reported automatically. If you have pro license please try to delete iot.0.certs: {"error":"Email not found or URL key not found"}
2020-11-11 20:46:41.630 - warn: iot.0 (25632) [GHOME] Invalid URL Pro key. Status auto-update is disabled you can set states but receive states only manually: {"error":"Email not found or URL key not found"}
2020-11-11 20:46:47.353 - error: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch().
2020-11-11 20:46:47.354 - error: iot.0 (25632) unhandled promise rejection: Test is not defined
2020-11-11 20:46:47.359 - error: iot.0 (25632) ReferenceError: Test is not defined
at eval (eval at (/opt/iobroker/node_modules/iobroker.iot/lib/GoogleHome.js:2920:62), :1:1)
at /opt/iobroker/node_modules/iobroker.iot/lib/GoogleHome.js:2921:63
at Array.forEach ()
at /opt/iobroker/node_modules/iobroker.iot/lib/GoogleHome.js:2917:43
at Array.forEach ()
at /opt/iobroker/node_modules/iobroker.iot/lib/GoogleHome.js:2825:61
at Array.forEach ()
at /opt/iobroker/node_modules/iobroker.iot/lib/GoogleHome.js:2802:37
at Array.forEach ()
at /opt/iobroker/node_modules/iobroker.iot/lib/GoogleHome.js:2799:35
2020-11-11 20:46:47.375 - info: iot.0 (25632) terminating
2020-11-11 20:46:47.377 - info: iot.0 (25632) Terminated (NO_ERROR): Without reason
2020-11-11 20:46:47.407 - info: iot.0 (25632) Connection changed: disconnect
2020-11-11 20:46:47.408 - info: iot.0 (25632) Connection lost
2020-11-11 20:46:47.927 - error: host.raspberrypi Caught by controller[0]: This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). The promise rejected with the reason:
2020-11-11 20:46:47.928 - error: host.raspberrypi Caught by controller[1]: ReferenceError: Test is not defined
2020-11-11 20:46:47.929 - error: host.raspberrypi Caught by controller[1]: at eval (eval at (/opt/iobroker/node_modules/iobroker.iot/lib/GoogleHome.js:2920:62), :1:1)
2020-11-11 20:46:47.929 - error: host.raspberrypi Caught by controller[1]: at /opt/iobroker/node_modules/iobroker.iot/lib/GoogleHome.js:2921:63
2020-11-11 20:46:47.930 - error: host.raspberrypi Caught by controller[1]: at Array.forEach ()
2020-11-11 20:46:47.930 - error: host.raspberrypi Caught by controller[1]: at /opt/iobroker/node_modules/iobroker.iot/lib/GoogleHome.js:2917:43
2020-11-11 20:46:47.931 - error: host.raspberrypi Caught by controller[1]: at Array.forEach ()
2020-11-11 20:46:47.931 - error: host.raspberrypi Caught by controller[1]: at /opt/iobroker/node_modules/iobroker.iot/lib/GoogleHome.js:2825:61
2020-11-11 20:46:47.931 - error: host.raspberrypi Caught by controller[1]: at Array.forEach ()
2020-11-11 20:46:47.932 - error: host.raspberrypi Caught by controller[1]: at /opt/iobroker/node_modules/iobroker.iot/lib/GoogleHome.js:2802:37
2020-11-11 20:46:47.932 - error: host.raspberrypi Caught by controller[1]: at Array.forEach ()
2020-11-11 20:46:47.933 - error: host.raspberrypi Caught by controller[1]: at /opt/iobroker/node_modules/iobroker.iot/lib/GoogleHome.js:2799:35
2020-11-11 20:46:47.933 - info: host.raspberrypi instance system.adapter.iot.0 terminated with code 0 (NO_ERROR)

[Thomas Braun]

@Marco-Willi

Url Key error. Google Request and Response are working. But device states are not reported automatically. If you have pro license please try to delete iot.0.certs: {"error":"Email not found or URL key not found"}

[Marco Willi]

@Thomas-Braun jap, das habe ich schon ein paar mal gelesen und an den Kopf bekommen. Trotz Mailadressenwechsel und Neuregistrierung immer die gleiche Meldung. Was muss ich tun?

[Thomas Braun]

@Marco-Willi
Hab kein iot pro, daher musste ich da auch noch nie was machen.

[Marco Willi]

@Thomas-Braun soll ich es mal mit free versuchen? Meinste das könnte klappen? Ich will auch keine Lizenz für meine 2 Anfragen am Tag kaufen.

[Marco Willi]

also mit free account bleibt der adapter auf gelb

[Meister Mopper]

@Marco-Willi sagte in Allgemein Google Home mit Iobroker:

@Thomas-Braun jap, das habe ich schon ein paar mal gelesen und an den Kopf bekommen. Trotz Mailadressenwechsel und Neuregistrierung immer die gleiche Meldung. Was muss ich tun?

Da steht ja, dass Du die certs löschen sollst. Hast Du das getan, mal auf den Mülleimer (s. Bild) geklickt?

[Marco Willi]

@Meister-Mopper neiiin hab ich noch nicht. Fürs erste setzt ich das Projekt mal einer Pause aus. Nächste Woche nochmal.
Müsste ich dann was neues anfordern?

[Meister Mopper]

@Marco-Willi Kostet ja nichts!

[Marco Willi]

@meister-mopper

Hi Leute. Habe es jetzt in der zwischenzeit hinbekommen. Lag eher bei einem Verständnisproblem denke ich.
Alles nochmals auf. Sämtliche Verknüpfungen aufgehoben.
Alles neu registiert und wieder verknüpft. Ging nachher relativ flott.
Dann beim Broker die Sensoren die ich abfragen wollte reingeknallt und als Thermostat gekennzeichnet.
„Hey Google aktualisiere Geräte“ dann war iobroker auch mit von der Party und ich konnte die Geräte einem Raum zuordnen. Jetzt klappt es auch mit abfragen der Temps.