[iot] Andere Probleme mit dem iot-Adapter bzw der Nutzung

Leviathan09

Aber, jetzt kommt es.
Habe jetzt mal den Adaper gestoppt, nochmal unter "White list für Services" meine Einträge entfernt, den Adapter gestartet, wieder etwas in der "White list für Services" eingetragen und das gespeicher.
Nachdem der Adapter dann neugestartet ist bekam ich zwar immer noch die Fehler Meldung in den Logs aber mir wurde dennoch ein neuer API-Key generiert und die URL ist nun vollständig.
Darauf muss man erstmal kommen das so zu probieren.

Und es funktioniert auch:

liv-in-sky

@Leviathan09

ja darauf muss man erstmal kommen

Leviathan09

@liv-in-sky Aber auf jeden Fall nochmal Danke für deine Hilfe und rasche Antwor

Holzlenkrad

@Holzlenkrad said in [iot] Andere Probleme mit dem iot-Adapter bzw der Nutzung:

Wenn ich dort jetzt jedoch Änderungen vornehme, also z.B. Gerät neu Funktionen zuordne, dann werden diese nicht in den Adapter übernommen.

So, nach genauerem Studium der Readme habe ich dann noch mal die Datenpunkte, die nicht übernommen wurden nach bearbeitet. Der Adapter verzeiht ja relativ wenig, wenn z.B. die Einheit nicht genau passt.
Da wäre es schön, wenn die Entwickler der anderen Adapter darauf achten würden, dass die Datenpunkte für Farbtemperaturen der Lampen z.B. wirklich immer die Einheit Kelvin hätten

Ein Problem habe ich dennoch, meine Temperatursensoren werden nicht automatisch übernommen.
Die haben alle die Role value.temperature, den Type 'number' und die Einheit °C.
So binden verschiedene Adapter die Temperatursensoren einheitlich ein...

marcuskl

Wie sieht es eigentlich mit diesem Problem aus ?

iot.0	2019-06-09 10:21:47.195	info	Connection changed: connect
iot.0	2019-06-09 10:21:41.882	info	Connection lost
iot.0	2019-06-09 10:21:41.881	info	Connection changed: disconnect
iot.0	2019-06-09 10:21:41.880	error	read ECONNRESET
....
iot.0	2019-06-09 10:18:20.348	info	Connection changed: connect
iot.0	2019-06-09 10:18:15.068	info	Connection lost
iot.0	2019-06-09 10:18:15.068	info	Connection changed: disconnect
iot.0	2019-06-09 10:18:15.067	error	read ECONNRESET
...
iot.0	2019-06-09 10:14:28.102	info	Connection changed: connect
iot.0	2019-06-09 10:14:22.800	info	Connection lost
iot.0	2019-06-09 10:14:22.800	info	Connection changed: disconnect
iot.0	2019-06-09 10:14:22.799	error	read ECONNRESET
...

Kann hier jemand helfen ??
Es geht jetzt schon ein halbes Jahr so

apollon77

Tja, leider ist das nicht so simpel ... https://github.com/aws/aws-iot-device-sdk-js/issues/251

warp735

Hallo zusammen,

ich such mir jetzt schon ne Weile n Wolf, find aber keine Lösung

Hatte schon ne ganze Weile den Cloudadapter mit free Lizenz laufen. Wollte nur mein VIS von extern sehen und hat auch wunderbar geklappt.

Nun habe ich mir vor kurzem eine pro Lizenz gekauft und bin auf iot umgestiegen.
Lampen steuern mit google home klappt, Adapter ist auch grün.. aber von extern komme ich nicht mehr auf iobroker. Erst wieder, wenn ich ZUSAÄTZLICH den Cloudadapter laufen lasse

Ist Fernzugriff noch nicht in iot implementiert oder was übersehe ich?! Will nicht beide Adapter laufen lassen.

Gruß Benni

dslraser

@warp735 sagte in [iot] Andere Probleme mit dem iot-Adapter bzw der Nutzung:

Hallo zusammen,

ich such mir jetzt schon ne Weile n Wolf, find aber keine Lösung

Hatte schon ne ganze Weile den Cloudadapter mit free Lizenz laufen. Wollte nur mein VIS von extern sehen und hat auch wunderbar geklappt.

Nun habe ich mir vor kurzem eine pro Lizenz gekauft und bin auf iot umgestiegen.
Lampen steuern mit google home klappt, Adapter ist auch grün.. aber von extern komme ich nicht mehr auf iobroker. Erst wieder, wenn ich ZUSAÄTZLICH den Cloudadapter laufen lasse

Ist Fernzugriff noch nicht in iot implementiert oder was übersehe ich?! Will nicht beide Adapter laufen lassen.

Gruß Benni

Fernzugriff ist Cloud. Assistenten ist iot.

warp735

Alles klar... ich danke dir. Dann kann ich natürlich lange rumprobieren

Wird das mal noch geändert? Hab das in allen Beiträgen so verstanden, das man cloud abschalten kann, wenn man iot nutzt.

dslraser

@warp735
das sind dann verschiedene Dienste. Ich habe es genau so verstanden, das es bewusst getrennt wird, damit iot(Alexa und Co) separat sind.

apollon77

@dslraser korrekt. Fernzugriff ist und bleibt Cloud.

Buhu91

Eventuell kann man mir hier im Thema helfen:

Ich habe das Problem, dass ich im IOT Adapter keine Geräte mehr angezeigt bekomme.
Ich hatte vorgestern Probleme mit ein paar Datenpunkten, und dachte es wäre clever einfach mal alle Geräte im IOT Adapter zu löschen und aus meiner Smartgeräte liste von Alexa.
Nun dachte ich, dass die bisherigen Datenpunkte einfach wieder nach dem Aktualisieren wieder im IOT Adapter erscheinen. Aber da tut sich gar nichts.
Ich hab schon neu gestartet, neu installiert, eine zweite Instanz installiert aber die Seite bei den Alexa Geräten bleibt leer. Auch als ich die Nacht den Adapter durchlaufen gelassen hab.

Gibts da irgend eine Methode wie ich den Adapter dazubringe die Geräte neu anzulegen?

apollon77

Welche iot Version?

Ansonsten naja Geräte gelöscht ist erstmal gelöscht. Du kannst dann bei den Funktionen und räumen Haken setzen. Dann legt er die wieder automatisch an. Meinst du das?

Buhu91

Hey,
Aktuell hab ich die 1.1.8 Instaliert.
Ich hab schon mal versucht alle haken zu entfernen, neuzustarten, Haken wieder setzen, neustarten des Adapters um eventuell so wieder an die Automatisch generieren Punkte zu kommen, das hat aber nicht geklappt.

Klar ist das erstmal gelöscht, aber es muss doch eine Möglichkeit geben da irgendwie wieder ranzukommen oder?
Kann ja auch mal passieren, dass man mal das falsche smart-gerät anklickt und schon wäre es für immer weg,

Eigentlich hab ich keine Lust wegen so etwas alles neu zu Installieren, aber ich denke inzwischen darüber nach, denn ohne Alexa ist das alles nur noch halb so schön.

tombox

@Buhu91 Hast du die Möglichkeit die jeweils Datenpunkte unter "Objekte" zu löschen und sie von dem jeweiligen Adapter neuerstellen zu lassen, dann müsste sie wieder vom IoT Adapter erkannt werden.

Du kannst auch manuell checken ob in der RAW Beschreibung auf "smartNames: false" und diese Zeile dann manuell löschen.

tcj

Kann bitte jemand kundiges auch hier mal schauen:
https://forum.iobroker.net/topic/25408/iot-alexa-schaltet-true-false-statt-on-off/1

Danke

Buhu91

@tombox Dankeschön, das Löschen und Neuerstellen der Datenpunkte hat die Lösung gebracht.
Das Löschen der Zeile in RAW hab ich davor Probiert, aber hat keine Abhilfe gebracht, gleich nach dem Löschen und Speichern, hat es wieder die Zeile Hinzugefügt.
Nochmals danke für deine Hilfe!

fantasticmaxpower

Hallo, ich habe es vor dem Wochenende auf Anhieb geschafft mit dem iot. Adapter via Google Assistant Lampen und Dimmer (Homematic) per Sprachbefehl AN und AUS zu schalten.
Nach einer Änderung habe ich "Hey Google, synchronisiere meine Geräte " ausgeführt. Ab diesem Moment war die Verknüpfung IOBroker in der Google Home App verschwunden. Ich habe seitdem jeden Thread hier im Forum durch, habe x mal neu installiert und neue User angelegt, OHNE ERFOLG. Die IOT Instanz ist grün, wenn ich in der Google Home App die Iobroker Verknüpfung starte, kommt die Meldung im LOG :

GHOME] No devices defined. Did you add not sensor or indicate states to rooms and enums?

Außerdem wird mir im Adapter im Reiter Google Devices nichts angezeigt, es läuft stets der Kreis und im LOG steht alle paar Sekunden:

Request google home devices

Im Reiter "intelligente Aufzählungen" sind alle Schalter Eingeschaltet. Die aktuellste iot Version ist installiert.

Zudem findet sich im LOG eine Caught ERror Meldung die ich nicht verstehe.

2019-10-14 16:00:02.199 - info: ical.0 starting. Version 1.7.0 in /opt/iobroker/node_modules/iobroker.ical, node: v8.16.0
2019-10-14 16:00:02.783 - info: ical.0 processing URL: Abfallkalender https://calendar.google.com/calendar/ical/5sj5sklb37t0dmuchmgoh81gm0%40group.calendar.google.com/private-2972214c632eabd90b51ae825f09ff2f/basic.ics
2019-10-14 16:00:08.354 - info: host.ioBroker-RasPi instance system.adapter.ical.0 terminated with code 0 (OK)
2019-10-14 16:04:51.011 - info: iobroker del cloud.0
2019-10-14 16:04:52.252 - info: iobroker Delete adapter "cloud.0"
2019-10-14 16:04:52.323 - info: iobroker host.ioBroker-RasPi Counted 1 instances of cloud
2019-10-14 16:04:52.446 - info: iobroker host.ioBroker-RasPi Counted 2 channels of cloud.0
2019-10-14 16:04:53.014 - info: iobroker host.ioBroker-RasPi Counted 19 states of cloud.0
2019-10-14 16:04:53.026 - info: iobroker host.ioBroker-RasPi Counted 6 states (cloud.0.*) from states
2019-10-14 16:04:53.031 - info: iobroker host.ioBroker-RasPi Counted 8 states (system.adapter.cloud.0.*) from states
2019-10-14 16:04:57.380 - info: iobroker host.ioBroker-RasPi Deleting 22 object(s).
2019-10-14 16:04:57.498 - info: host.ioBroker-RasPi object change system.adapter.cloud.0
2019-10-14 16:04:57.499 - info: host.ioBroker-RasPi object deleted system.adapter.cloud.0
2019-10-14 16:04:57.503 - info: iobroker host.ioBroker-RasPi Deleting 14 state(s).
2019-10-14 16:04:57.545 - info: iobroker exit 0
2019-10-14 16:05:12.752 - info: iobroker del cloud
2019-10-14 16:05:13.981 - info: iobroker Delete adapter "cloud"
2019-10-14 16:05:14.046 - info: iobroker host.ioBroker-RasPi no instances of adapter cloud found
2019-10-14 16:05:14.087 - info: iobroker host.ioBroker-RasPi Counted 1 adapters for cloud
2019-10-14 16:05:14.753 - info: iobroker host.ioBroker-RasPi Counted 1 states of cloud
2019-10-14 16:05:14.765 - info: iobroker host.ioBroker-RasPi Counted 1 states (system.adapter.cloud.*) from states
2019-10-14 16:05:14.795 - info: iobroker host.ioBroker-RasPi Deleting 2 object(s).
2019-10-14 16:05:14.818 - info: iobroker host.ioBroker-RasPi Deleting 1 state(s).
2019-10-14 16:05:15.739 - info: iobroker npm uninstall iobroker.cloud --silent --save --prefix "/opt/iobroker" (System call)
2019-10-14 16:05:15.778 - error: host.ioBroker-RasPi Cannot write files: /opt/iobroker/node_modules/iobroker.js-controller/lib/objects/../../../../iobroker-data/files/cloud.admin/_data.json: ENOENT: no such file or directory, open '/opt/iobroker/node_modules/iobroker.js-controller/lib/objects/../../../../iobroker-data/files/cloud.admin/_data.json'
2019-10-14 16:06:04.936 - info: iobroker ../src/linux/DeviceINQ.cc:35:37: fatal error: bluetooth/bluetooth.h: Datei oder Verzeichnis nicht gefunden #include
^
compilation terminated.
2019-10-14 16:06:04.945 - info: iobroker make: *** [Release/obj.target/BluetoothSerialPort/src/linux/DeviceINQ.o] Fehler 1
2019-10-14 16:06:09.497 - info: iobroker exit 0
2019-10-14 16:06:24.400 - info: iobroker del iot
2019-10-14 16:06:25.667 - info: iobroker Delete adapter "iot"
2019-10-14 16:06:25.732 - info: iobroker host.ioBroker-RasPi Counted 1 instances of iot
2019-10-14 16:06:25.797 - info: iobroker host.ioBroker-RasPi Counted 1 adapters for iot
2019-10-14 16:06:25.898 - info: iobroker host.ioBroker-RasPi Counted 3 channels of iot
2019-10-14 16:06:26.458 - info: iobroker host.ioBroker-RasPi Counted 27 states of iot
2019-10-14 16:06:26.469 - info: iobroker host.ioBroker-RasPi Counted 7 states (iot.*) from states
2019-10-14 16:06:26.471 - info: iobroker host.ioBroker-RasPi Counted 9 states (system.adapter.iot.*) from states
2019-10-14 16:06:26.502 - info: iobroker host.ioBroker-RasPi Deleting 32 object(s).
2019-10-14 16:06:26.676 - info: host.ioBroker-RasPi object change system.adapter.iot.0
2019-10-14 16:06:26.677 - info: host.ioBroker-RasPi object deleted system.adapter.iot.0
2019-10-14 16:06:26.677 - info: host.ioBroker-RasPi stopInstance system.adapter.iot.0
2019-10-14 16:06:26.677 - info: host.ioBroker-RasPi stopInstance system.adapter.iot.0 killing pid 3282
2019-10-14 16:06:26.682 - info: iobroker host.ioBroker-RasPi Deleting 16 state(s).
2019-10-14 16:06:26.724 - error: host.ioBroker-RasPi instance system.adapter.iot.0 terminated with code 0 (OK)
2019-10-14 16:06:26.724 - info: host.ioBroker-RasPi Do not restart adapter system.adapter.iot.0 because disabled or deleted
2019-10-14 16:06:27.488 - error: host.ioBroker-RasPi Cannot write files: /opt/iobroker/node_modules/iobroker.js-controller/lib/objects/../../../../iobroker-data/files/iot.admin/_data.json: ENOENT: no such file or directory, open '/opt/iobroker/node_modules/iobroker.js-controller/lib/objects/../../../../iobroker-data/files/iot.admin/_data.json'
2019-10-14 16:06:27.559 - info: iobroker npm uninstall iobroker.iot --silent --save --prefix "/opt/iobroker" (System call)
2019-10-14 16:07:16.878 - info: iobroker ../src/linux/DeviceINQ.cc:35:37: fatal error: bluetooth/bluetooth.h: Datei oder Verzeichnis nicht gefunden #include
^
compilation terminated.
2019-10-14 16:07:16.884 - info: iobroker make: *** [Release/obj.target/BluetoothSerialPort/src/linux/DeviceINQ.o] Fehler 1
2019-10-14 16:07:21.153 - info: iobroker exit 0
2019-10-14 16:07:40.671 - info: iobroker add iot --host ioBroker-RasPi
2019-10-14 16:07:43.897 - info: iobroker NPM version: 6.4.1
2019-10-14 16:07:44.787 - info: iobroker npm install iobroker.iot --production --save --prefix "/opt/iobroker" (System call)
2019-10-14 16:08:40.131 - info: iobroker ../src/linux/DeviceINQ.cc:35:37: fatal error: bluetooth/bluetooth.h: Datei oder Verzeichnis nicht gefunden #include
^
compilation terminated.
2019-10-14 16:08:40.140 - info: iobroker make: *** [Release/obj.target/BluetoothSerialPort/src/linux/DeviceINQ.o] Fehler 1
2019-10-14 16:08:40.154 - info: iobroker gyp ERR! build error gyp ERR! stack Error: `make` failed with exit code: 2
gyp ERR! stack at ChildProcess.onExit (/usr/lib/node_modules/npm/node_modules/node-gyp/lib/build.js:262:23)
gyp ERR! stack at emitTwo (events.js:126:13)
gyp ERR! stack at ChildProcess.emit (events.js:214:7)
gyp ERR! stack at Process.ChildProcess._handle.onexit (internal/child_process.js:198:12)
gyp ERR! System Linux 4.14.98-v7+
gyp ERR! command "/usr/bin/node" "/usr/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "configure" "build"
gyp ERR! cwd /opt/iobroker/node_modules/node-bluetooth
gyp ERR! node -v v8.16.0
gyp ERR! node-gyp -v v3.8.0
gyp ERR! not ok
2019-10-14 16:08:45.032 - info: iobroker npm
2019-10-14 16:08:45.033 - info: iobroker WARN optional SKIPPING OPTIONAL DEPENDENCY: osx-temperature-sensor@1.0.4 (node_modules/osx-temperature-sensor):npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for osx-temperature-sensor@1.0.4: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"arm"})
2019-10-14 16:08:45.035 - info: iobroker npm WARN optional SKIPPING OPTIONAL DEPENDENCY: xpc-connection@0.1.4 (node_modules/xpc-connection):npm WARN
2019-10-14 16:08:45.036 - info: iobroker notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for xpc-connection@0.1.4: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"arm"})npm WARN optional SKIPPING OPTIONAL DEPENDENCY: node-bluetooth@1.2.6 (node_modules/node-bluetooth):
npm
2019-10-14 16:08:45.037 - info: iobroker WARN optional SKIPPING OPTIONAL DEPENDENCY: node-bluetooth@1.2.6 install: `node-gyp configure build`npm WARN optional SKIPPING OPTIONAL DEPENDENCY: Exit status 1
2019-10-14 16:08:45.039 - info: iobroker
2019-10-14 16:08:45.122 - info: iobroker host.ioBroker-RasPi install adapter iot
2019-10-14 16:08:45.145 - info: iobroker got /opt/iobroker/node_modules/iobroker.iot/admin
2019-10-14 16:08:45.277 - info: iobroker upload [20] iot.admin /opt/iobroker/node_modules/iobroker.iot/admin/static/media/copy-content.6fe0b363.svg static/media/copy-content.6fe0b363.svg image/svg+xml
2019-10-14 16:08:45.342 - info: iobroker upload [19] iot.admin /opt/iobroker/node_modules/iobroker.iot/admin/static/js/runtime~main.d653cc00.js.map static/js/runtime~main.d653cc00.js.map application/json
2019-10-14 16:08:45.406 - info: iobroker upload [18] iot.admin /opt/iobroker/node_modules/iobroker.iot/admin/static/js/runtime~main.d653cc00.js static/js/runtime~main.d653cc00.js application/javascript
2019-10-14 16:08:45.467 - info: iobroker upload [17] iot.admin /opt/iobroker/node_modules/iobroker.iot/admin/static/js/main.52677f0c.chunk.js.map static/js/main.52677f0c.chunk.js.map application/json
2019-10-14 16:08:45.577 - info: iobroker upload [16] iot.admin /opt/iobroker/node_modules/iobroker.iot/admin/static/js/main.52677f0c.chunk.js static/js/main.52677f0c.chunk.js application/javascript
2019-10-14 16:08:45.678 - info: iobroker upload [15] iot.admin /opt/iobroker/node_modules/iobroker.iot/admin/static/js/2.125d4b51.chunk.js.map static/js/2.125d4b51.chunk.js.map application/json
2019-10-14 16:08:48.404 - info: iobroker upload [14] iot.admin /opt/iobroker/node_modules/iobroker.iot/admin/static/js/2.125d4b51.chunk.js static/js/2.125d4b51.chunk.js application/javascript
2019-10-14 16:08:49.509 - info: iobroker upload [13] iot.admin /opt/iobroker/node_modules/iobroker.iot/admin/static/css/main.d4bed9c6.chunk.css.map static/css/main.d4bed9c6.chunk.css.map application/json
2019-10-14 16:08:49.696 - info: iobroker upload [12] iot.admin /opt/iobroker/node_modules/iobroker.iot/admin/static/css/main.d4bed9c6.chunk.css static/css/main.d4bed9c6.chunk.css text/css
2019-10-14 16:08:49.755 - info: iobroker upload [11] iot.admin /opt/iobroker/node_modules/iobroker.iot/admin/static/css/2.0302007b.chunk.css.map static/css/2.0302007b.chunk.css.map application/json
2019-10-14 16:08:49.815 - info: iobroker upload [10] iot.admin /opt/iobroker/node_modules/iobroker.iot/admin/static/css/2.0302007b.chunk.css static/css/2.0302007b.chunk.css text/css
2019-10-14 16:08:49.873 - info: iobroker upload [9] iot.admin /opt/iobroker/node_modules/iobroker.iot/admin/service-worker.js service-worker.js application/javascript
2019-10-14 16:08:49.930 - info: iobroker upload [8] iot.admin /opt/iobroker/node_modules/iobroker.iot/admin/precache-manifest.1bdb4d94c9bb79beb117b2e1a0a9136e.js precache-manifest.1bdb4d94c9bb79beb117b2e1a0a9136e.js application/javascript
2019-10-14 16:08:49.987 - info: iobroker upload [7] iot.admin /opt/iobroker/node_modules/iobroker.iot/admin/manifest.json manifest.json application/json
2019-10-14 16:08:50.044 - info: iobroker upload [6] iot.admin /opt/iobroker/node_modules/iobroker.iot/admin/iot.png iot.png image/png
2019-10-14 16:08:50.108 - info: iobroker upload [5] iot.admin /opt/iobroker/node_modules/iobroker.iot/admin/index_m.html index_m.html text/html
2019-10-14 16:08:50.556 - info: iobroker upload [4] iot.admin /opt/iobroker/node_modules/iobroker.iot/admin/favicon.ico favicon.ico image/x-icon
2019-10-14 16:08:50.780 - info: iobroker upload [3] iot.admin /opt/iobroker/node_modules/iobroker.iot/admin/blockly.js blockly.js application/javascript
2019-10-14 16:08:50.839 - info: iobroker upload [2] iot.admin /opt/iobroker/node_modules/iobroker.iot/admin/asset-manifest.json asset-manifest.json application/json
2019-10-14 16:08:50.895 - info: iobroker upload [1] iot.admin /opt/iobroker/node_modules/iobroker.iot/admin/alexalogo.png alexalogo.png image/png
2019-10-14 16:08:50.956 - info: iobroker upload [0] iot.admin /opt/iobroker/node_modules/iobroker.iot/admin/actions.js actions.js application/javascript
2019-10-14 16:08:51.250 - info: iobroker host.ioBroker-RasPi object system.adapter.iot created
2019-10-14 16:08:51.301 - info: iobroker host.ioBroker-RasPi create instance iot
2019-10-14 16:08:51.323 - info: iobroker host.ioBroker-RasPi object iot.0.certs.forceUserCreate created
2019-10-14 16:08:51.362 - info: iobroker host.ioBroker-RasPi object iot.0.certs.urlKey created
2019-10-14 16:08:51.394 - info: iobroker host.ioBroker-RasPi object iot.0.certs.certificate created
2019-10-14 16:08:51.426 - info: iobroker host.ioBroker-RasPi object iot.0.certs.private created
2019-10-14 16:08:51.457 - info: iobroker host.ioBroker-RasPi object iot.0.certs.public created
2019-10-14 16:08:51.489 - info: iobroker host.ioBroker-RasPi object iot.0.certs.id created
2019-10-14 16:08:51.521 - info: iobroker host.ioBroker-RasPi object iot.0.certs created
2019-10-14 16:08:51.554 - info: iobroker host.ioBroker-RasPi object iot.0.services created
2019-10-14 16:08:51.585 - info: iobroker host.ioBroker-RasPi object iot.0.smart.updatesResult created
2019-10-14 16:08:51.616 - info: iobroker host.ioBroker-RasPi object iot.0.smart.updatesYA created
2019-10-14 16:08:51.648 - info: iobroker host.ioBroker-RasPi object iot.0.smart.updatesGH created
2019-10-14 16:08:51.679 - info: iobroker host.ioBroker-RasPi object iot.0.smart.updates3 created
2019-10-14 16:08:51.710 - info: iobroker host.ioBroker-RasPi object iot.0.smart.updates created
2019-10-14 16:08:51.742 - info: iobroker host.ioBroker-RasPi object iot.0.smart.lastResponse created
2019-10-14 16:08:51.773 - info: iobroker host.ioBroker-RasPi object iot.0.smart.lastCommandObj created
2019-10-14 16:08:51.805 - info: iobroker host.ioBroker-RasPi object iot.0.smart.lastCommand created
2019-10-14 16:08:51.836 - info: iobroker host.ioBroker-RasPi object iot.0.smart.lastRoom created
2019-10-14 16:08:51.868 - info: iobroker host.ioBroker-RasPi object iot.0.smart.lastFunction created
2019-10-14 16:08:51.899 - info: iobroker host.ioBroker-RasPi object iot.0.info.remoteTill created
2019-10-14 16:08:51.929 - info: iobroker host.ioBroker-RasPi object iot.0.info.connection created
2019-10-14 16:08:51.960 - info: iobroker host.ioBroker-RasPi object iot.0.info created
2019-10-14 16:08:51.993 - info: iobroker host.ioBroker-RasPi object system.adapter.iot.0.outputCount created
2019-10-14 16:08:52.026 - info: iobroker host.ioBroker-RasPi object system.adapter.iot.0.inputCount created
2019-10-14 16:08:52.059 - info: iobroker host.ioBroker-RasPi object system.adapter.iot.0.uptime created
2019-10-14 16:08:52.096 - info: iobroker host.ioBroker-RasPi object system.adapter.iot.0.memRss created
2019-10-14 16:08:52.134 - info: iobroker host.ioBroker-RasPi object system.adapter.iot.0.memHeapTotal created
2019-10-14 16:08:52.171 - info: iobroker host.ioBroker-RasPi object system.adapter.iot.0.memHeapUsed created
2019-10-14 16:08:52.207 - info: iobroker host.ioBroker-RasPi object system.adapter.iot.0.connected created
2019-10-14 16:08:52.245 - info: iobroker host.ioBroker-RasPi object system.adapter.iot.0.alive created
2019-10-14 16:08:52.289 - info: host.ioBroker-RasPi object change system.adapter.iot.0
2019-10-14 16:08:52.298 - info: iobroker host.ioBroker-RasPi object system.adapter.iot.0 created
2019-10-14 16:08:52.334 - info: iobroker exit 0
2019-10-14 16:09:42.264 - info: host.ioBroker-RasPi object change system.adapter.iot.0
2019-10-14 16:09:48.163 - info: host.ioBroker-RasPi object change system.adapter.iot.0
2019-10-14 16:09:48.163 - info: host.ioBroker-RasPi "system.adapter.iot.0" enabled
2019-10-14 16:09:48.181 - info: host.ioBroker-RasPi instance system.adapter.iot.0 started with pid 18636
2019-10-14 16:09:50.231 - info: iot.0 States connected to redis: 127.0.0.1:6379
2019-10-14 16:09:50.446 - info: iot.0 starting. Version 1.1.8 in /opt/iobroker/node_modules/iobroker.iot, node: v8.16.0
2019-10-14 16:09:50.457 - info: iot.0 Connecting with a18wym7vjdl22g.iot.eu-west-1.amazonaws.com
2019-10-14 16:09:50.473 - error: iot.0 Cannot read URL key: Not exists
2019-10-14 16:09:52.780 - info: iot.0 Connection changed: connect
2019-10-14 16:15:10.352 - info: host.ioBroker-RasPi object change system.adapter.iot.0
2019-10-14 16:15:10.353 - info: host.ioBroker-RasPi stopInstance system.adapter.iot.0
2019-10-14 16:15:10.354 - info: host.ioBroker-RasPi stopInstance system.adapter.iot.0 killing pid 18636
2019-10-14 16:15:10.412 - info: host.ioBroker-RasPi instance system.adapter.iot.0 terminated with code 0 (OK)
2019-10-14 16:15:13.514 - info: host.ioBroker-RasPi object change system.adapter.iot.0
2019-10-14 16:15:13.544 - info: host.ioBroker-RasPi instance system.adapter.iot.0 started with pid 18721
2019-10-14 16:15:15.987 - info: iot.0 States connected to redis: 127.0.0.1:6379
2019-10-14 16:15:16.202 - info: iot.0 starting. Version 1.1.8 in /opt/iobroker/node_modules/iobroker.iot, node: v8.16.0
2019-10-14 16:15:16.213 - info: iot.0 Connecting with a18wym7vjdl22g.iot.eu-west-1.amazonaws.com
2019-10-14 16:15:18.242 - info: iot.0 Connection changed: connect
2019-10-14 16:16:00.064 - info: iot.0 Request google home devices
2019-10-14 16:16:10.055 - info: iot.0 Request google home devices
2019-10-14 16:16:10.418 - info: host.ioBroker-RasPi object change system.adapter.iot.0
2019-10-14 16:16:10.419 - info: host.ioBroker-RasPi stopInstance system.adapter.iot.0
2019-10-14 16:16:10.419 - info: host.ioBroker-RasPi stopInstance system.adapter.iot.0 killing pid 18721
2019-10-14 16:16:10.536 - error: Caught by controller[1]: (node:18721) UnhandledPromiseRejectionWarning: TypeError: Cannot read property 'smartName' of undefined
2019-10-14 16:16:10.537 - error: Caught by controller[1]: at GoogleHome.getSmartName (/opt/iobroker/node_modules/iobroker.iot/lib/GoogleHome.js:1316:38)
2019-10-14 16:16:10.537 - error: Caught by controller[1]: at Object.keys.forEach.id (/opt/iobroker/node_modules/iobroker.iot/lib/GoogleHome.js:1704:38)
2019-10-14 16:16:10.537 - error: Caught by controller[1]: at Array.forEach ()
2019-10-14 16:16:10.537 - error: Caught by controller[1]: at _readObjects.then.data (/opt/iobroker/node_modules/iobroker.iot/lib/GoogleHome.js:1703:38)
2019-10-14 16:16:10.538 - error: Caught by controller[1]: at
2019-10-14 16:16:10.538 - error: Caught by controller[2]: (node:18721) UnhandledPromiseRejectionWarning: 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(). (rejection id: 3)
2019-10-14 16:16:10.538 - info: host.ioBroker-RasPi instance system.adapter.iot.0 terminated with code 0 (OK)
2019-10-14 16:16:12.953 - info: host.ioBroker-RasPi instance system.adapter.iot.0 started with pid 18732
2019-10-14 16:16:15.152 - info: iot.0 States connected to redis: 127.0.0.1:6379
2019-10-14 16:16:15.393 - info: iot.0 starting. Version 1.1.8 in /opt/iobroker/node_modules/iobroker.iot, node: v8.16.0
2019-10-14 16:16:15.404 - info: iot.0 Connecting with a18wym7vjdl22g.iot.eu-west-1.amazonaws.com
2019-10-14 16:16:19.325 - info: iot.0 Connection changed: connect
2019-10-14 16:18:07.418 - warn: iot.0 [GHOME] No devices defined. Did you add not sensor or indicate states to rooms and enums?
2019-10-14 16:23:10.080 - info: iot.0 Request google home devices
2019-10-14 16:23:18.639 - info: iot.0 Request google home devices
2019-10-14 16:23:20.079 - info: iot.0 Request google home devices
2019-10-14 16:23:25.400 - info: iot.0 Request google home devices
2019-10-14 16:23:35.403 - info: iot.0 Request google home devices
2019-10-14 16:23:45.409 - info: iot.0 Request google home devices
2019-10-14 16:23:55.408 - info: iot.0 Request google home devices
2019-10-14 16:24:05.413 - info: iot.0 Request google home devices
2019-10-14 16:26:37.565 - warn: iot.0 [GHOME] No devices defined. Did you add not sensor or indicate states to rooms and enums?
2019-10-14 17:00:00.050 - info: host.ioBroker-RasPi instance system.adapter.ical.0 started with pid 19419
2019-10-14 17:00:02.416 - info: ical.0 States connected to redis: 127.0.0.1:6379
2019-10-14 17:00:02.611 - info: ical.0 starting. Version 1.7.0 in /opt/iobroker/node_modules/iobroker.ical, node: v8.16.0
2019-10-14 17:00:03.321 - info: ical.0 processing URL: Abfallkalender https://calendar.google.com/calendar/ical/5sj5sklb37t0dmuchmgoh81gm0%40group.calendar.google.com/private-2972214c632eabd90b51ae825f09ff2f/basic.ics
2019-10-14 17:00:08.893 - info: host.ioBroker-RasPi instance system.adapter.ical.0 terminated with code 0 (OK)
2019-10-14 18:00:00.052 - info: host.ioBroker-RasPi instance system.adapter.ical.0 started with pid 20214
2019-10-14 18:00:02.136 - info: ical.0 States connected to redis: 127.0.0.1:6379
2019-10-14 18:00:02.334 - info: ical.0 starting. Version 1.7.0 in /opt/iobroker/node_modules/iobroker.ical, node: v8.16.0
2019-10-14 18:00:08.026 - info: ical.0 processing URL: Abfallkalender https://calendar.google.com/calendar/ical/5sj5sklb37t0dmuchmgoh81gm0%40group.calendar.google.com/private-2972214c632eabd90b51ae825f09ff2f/basic.ics
2019-10-14 18:00:13.595 - info: host.ioBroker-RasPi instance system.adapter.ical.0 terminated with code 0 (OK)
2019-10-14 19:00:00.048 - info: host.ioBroker-RasPi instance system.adapter.ical.0 started with pid 21012
2019-10-14 19:00:02.060 - info: ical.0 States connected to redis: 127.0.0.1:6379
2019-10-14 19:00:02.256 - info: ical.0 starting. Version 1.7.0 in /opt/iobroker/node_modules/iobroker.ical, node: v8.16.0
2019-10-14 19:00:02.857 - info: ical.0 processing URL: Abfallkalender https://calendar.google.com/calendar/ical/5sj5sklb37t0dmuchmgoh81gm0%40group.calendar.google.com/private-2972214c632eabd90b51ae825f09ff2f/basic.ics
2019-10-14 19:00:08.429 - info: host.ioBroker-RasPi instance system.adapter.ical.0 terminated with code 0 (OK)
2019-10-14 19:12:43.118 - info: host.ioBroker-RasPi received SIGTERM
2019-10-14 19:12:43.126 - info: web.0 terminating http server on port 8082
2019-10-14 19:12:43.124 - info: admin.0 terminating http server on port 8081
2019-10-14 19:12:43.120 - info: host.ioBroker-RasPi stopInstance system.adapter.admin.0
2019-10-14 19:12:43.121 - info: host.ioBroker-RasPi stopInstance system.adapter.admin.0 killing pid 737
2019-10-14 19:12:43.121 - info: host.ioBroker-RasPi stopInstance system.adapter.discovery.0
2019-10-14 19:12:43.122 - warn: host.ioBroker-RasPi stopInstance system.adapter.discovery.0 not running
2019-10-14 19:12:43.122 - info: host.ioBroker-RasPi stopInstance system.adapter.web.0
2019-10-14 19:12:43.123 - info: host.ioBroker-RasPi stopInstance system.adapter.web.0 killing pid 747
2019-10-14 19:12:43.123 - info: host.ioBroker-RasPi stopInstance system.adapter.rpi2.0
2019-10-14 19:12:43.124 - warn: host.ioBroker-RasPi stopInstance system.adapter.rpi2.0 not running
2019-10-14 19:12:43.124 - info: host.ioBroker-RasPi stopInstance system.adapter.socketio.0
2019-10-14 19:12:43.124 - warn: host.ioBroker-RasPi stopInstance system.adapter.socketio.0 not running
2019-10-14 19:12:43.125 - info: host.ioBroker-RasPi stopInstance system.adapter.vis.0
2019-10-14 19:12:43.125 - info: host.ioBroker-RasPi stopInstance system.adapter.history.0
2019-10-14 19:12:43.127 - info: host.ioBroker-RasPi stopInstance system.adapter.mobile.0
2019-10-14 19:12:43.128 - info: host.ioBroker-RasPi stopInstance system.adapter.hm-rpc.1
2019-10-14 19:12:43.129 - info: host.ioBroker-RasPi stopInstance system.adapter.hm-rpc.2
2019-10-14 19:12:43.135 - info: host.ioBroker-RasPi stopInstance system.adapter.hm-rpc.3
2019-10-14 19:12:43.135 - warn: host.ioBroker-RasPi stopInstance system.adapter.hm-rpc.3 not running
2019-10-14 19:12:43.136 - info: host.ioBroker-RasPi stopInstance system.adapter.hm-rega.1
2019-10-14 19:12:43.136 - info: host.ioBroker-RasPi stopInstance system.adapter.hm-rega.1 killing pid 1876
2019-10-14 19:12:43.142 - info: host.ioBroker-RasPi stopInstance system.adapter.scenes.0
2019-10-14 19:12:43.143 - warn: host.ioBroker-RasPi stopInstance system.adapter.scenes.0 not running
2019-10-14 19:12:43.144 - info: host.ioBroker-RasPi stopInstance system.adapter.pushover.0
2019-10-14 19:12:43.145 - info: host.ioBroker-RasPi stopInstance system.adapter.pushover.0 killing pid 727
2019-10-14 19:12:43.153 - info: host.ioBroker-RasPi stopInstance system.adapter.vis-hqwidgets.0
2019-10-14 19:12:43.153 - info: host.ioBroker-RasPi stopInstance system.adapter.vis-timeandweather.0
2019-10-14 19:12:43.154 - info: host.ioBroker-RasPi stopInstance system.adapter.vis-metro.0
2019-10-14 19:12:43.155 - info: host.ioBroker-RasPi stopInstance system.adapter.vis-map.0
2019-10-14 19:12:43.155 - info: host.ioBroker-RasPi stopInstance system.adapter.vis-google-fonts.0
2019-10-14 19:12:43.156 - info: host.ioBroker-RasPi stopInstance system.adapter.vis-jqui-mfd.0
2019-10-14 19:12:43.156 - info: host.ioBroker-RasPi stopInstance system.adapter.dwd.0
2019-10-14 19:12:43.157 - warn: host.ioBroker-RasPi stopInstance system.adapter.dwd.0 not scheduled
2019-10-14 19:12:43.157 - info: host.ioBroker-RasPi stopInstance system.adapter.radar.0
2019-10-14 19:12:43.158 - warn: host.ioBroker-RasPi stopInstance system.adapter.radar.0 not running
2019-10-14 19:12:43.158 - info: host.ioBroker-RasPi stopInstance system.adapter.javascript.0
2019-10-14 19:12:43.159 - info: host.ioBroker-RasPi stopInstance system.adapter.javascript.0 killing pid 807
2019-10-14 19:12:43.159 - info: host.ioBroker-RasPi stopInstance system.adapter.ical.0
2019-10-14 19:12:43.162 - info: host.ioBroker-RasPi stopInstance canceled schedule system.adapter.ical.0
2019-10-14 19:12:43.162 - info: host.ioBroker-RasPi stopInstance system.adapter.musiccast.0
2019-10-14 19:12:43.163 - warn: host.ioBroker-RasPi stopInstance system.adapter.musiccast.0 not running
2019-10-14 19:12:43.163 - info: host.ioBroker-RasPi stopInstance system.adapter.yamaha.0
2019-10-14 19:12:43.164 - warn: host.ioBroker-RasPi stopInstance system.adapter.yamaha.0 not running
2019-10-14 19:12:43.165 - info: host.ioBroker-RasPi stopInstance system.adapter.yr.0
2019-10-14 19:12:43.165 - warn: host.ioBroker-RasPi stopInstance system.adapter.yr.0 not scheduled
2019-10-14 19:12:43.166 - info: host.ioBroker-RasPi stopInstance system.adapter.info.0
2019-10-14 19:12:43.167 - warn: host.ioBroker-RasPi stopInstance system.adapter.info.0 not running
2019-10-14 19:12:43.167 - info: host.ioBroker-RasPi stopInstance system.adapter.radar2.0
2019-10-14 19:12:43.168 - warn: host.ioBroker-RasPi stopInstance system.adapter.radar2.0 not running
2019-10-14 19:12:43.168 - info: host.ioBroker-RasPi stopInstance system.adapter.iot.0
2019-10-14 19:12:43.169 - info: host.ioBroker-RasPi stopInstance system.adapter.iot.0 killing pid 18732
2019-10-14 19:12:43.210 - info: host.ioBroker-RasPi instance system.adapter.admin.0 terminated with code 0 (OK)
2019-10-14 19:12:43.257 - info: host.ioBroker-RasPi instance system.adapter.web.0 terminated with code 0 (OK)
2019-10-14 19:12:43.272 - info: host.ioBroker-RasPi instance system.adapter.javascript.0 terminated with code 0 (OK)
2019-10-14 19:12:43.284 - info: host.ioBroker-RasPi instance system.adapter.hm-rega.1 terminated with code 0 (OK)
2019-10-14 19:12:43.291 - info: host.ioBroker-RasPi instance system.adapter.iot.0 terminated with code 0 (OK)
2019-10-14 19:12:43.430 - info: host.ioBroker-RasPi instance system.adapter.history.0 terminated with code 0 (OK)
2019-10-14 19:12:43.674 - info: host.ioBroker-RasPi instance system.adapter.pushover.0 terminated with code 0 (OK)
2019-10-14 19:12:44.130 - info: host.ioBroker-RasPi stopInstance timeout "1000 system.adapter.hm-rpc.1 killing pid 2006
2019-10-14 19:12:44.135 - info: host.ioBroker-RasPi stopInstance timeout "1000 system.adapter.hm-rpc.2 killing pid 2012
2019-10-14 19:12:44.135 - info: hm-rpc.1 binrpc -> 192.168.0.10:8701/ init ["xmlrpc_bin://192.168.0.206:18701",""]
2019-10-14 19:12:44.140 - info: hm-rpc.2 binrpc -> 192.168.0.10:2001/ init ["xmlrpc_bin://192.168.0.206:12001",""]
2019-10-14 19:12:44.198 - info: host.ioBroker-RasPi instance system.adapter.hm-rpc.1 terminated with code 0 (OK)
2019-10-14 19:12:44.199 - info: host.ioBroker-RasPi All instances are stopped.
2019-10-14 19:12:44.218 - info: host.ioBroker-RasPi instance system.adapter.hm-rpc.2 terminated with code 0 (OK)
2019-10-14 19:12:44.219 - info: host.ioBroker-RasPi All instances are stopped.
2019-10-14 19:12:44.384 - info: host.ioBroker-RasPi terminated
2019-10-14 19:15:21.769 - info: host.ioBroker-RasPi iobroker.js-controller version 1.5.14 js-controller starting
2019-10-14 19:15:21.777 - info: host.ioBroker-RasPi Copyright (c) 2014-2018 bluefox, 2014 hobbyquaker
2019-10-14 19:15:21.777 - info: host.ioBroker-RasPi hostname: ioBroker-RasPi, node: v8.16.0
2019-10-14 19:15:21.782 - info: host.ioBroker-RasPi ip addresses: 192.168.0.206 2a02:908:1b2:7ea0:88ec:707b:3423:742f fe80::98ce:337c:aafc:59c2
2019-10-14 19:15:22.594 - info: host.ioBroker-RasPi inMem-objects listening on port 9001
2019-10-14 19:15:22.616 - info: host.ioBroker-RasPi InMemoryDB connected
2019-10-14 19:15:22.673 - info: host.ioBroker-RasPi 31 instances found
2019-10-14 19:15:22.713 - info: host.ioBroker-RasPi starting 15 instances
2019-10-14 19:15:22.842 - info: host.ioBroker-RasPi instance system.adapter.admin.0 started with pid 21614
2019-10-14 19:15:22.862 - info: host.ioBroker-RasPi States connected to redis: 127.0.0.1:6379
2019-10-14 19:15:25.755 - info: admin.0 States connected to redis: 127.0.0.1:6379
2019-10-14 19:15:25.900 - info: admin.0 starting. Version 3.6.7 in /opt/iobroker/node_modules/iobroker.admin, node: v8.16.0
2019-10-14 19:15:25.974 - info: admin.0 requesting all states
2019-10-14 19:15:25.977 - info: admin.0 requesting all objects
2019-10-14 19:15:25.979 - info: admin.0 Request actual repository...
2019-10-14 19:15:27.157 - info: host.ioBroker-RasPi instance system.adapter.web.0 started with pid 21628
2019-10-14 19:15:27.809 - info: admin.0 received all states
2019-10-14 19:15:29.498 - info: admin.0 received all objects
2019-10-14 19:15:29.529 - warn: admin.0 No repository source configured
2019-10-14 19:15:29.573 - info: admin.0 http server listening on port 8081
2019-10-14 19:15:29.574 - info: admin.0 Use link "http://localhost:8081" to configure.
2019-10-14 19:15:29.701 - info: host.ioBroker-RasPi Update repository "default" under "http://download.iobroker.net/sources-dist.json"
2019-10-14 19:15:30.504 - info: web.0 States connected to redis: 127.0.0.1:6379
2019-10-14 19:15:30.612 - info: web.0 starting. Version 2.4.1 in /opt/iobroker/node_modules/iobroker.web, node: v8.16.0
2019-10-14 19:15:30.753 - info: host.ioBroker-RasPi instance system.adapter.history.0 started with pid 21642
2019-10-14 19:15:31.347 - info: admin.0 Repository received successfully.
2019-10-14 19:15:31.499 - info: web.0 socket.io server listening on port 8082
2019-10-14 19:15:31.504 - info: web.0 http server listening on port 8082
2019-10-14 19:15:32.260 - info: history.0 States connected to redis: 127.0.0.1:6379
2019-10-14 19:15:32.321 - info: history.0 starting. Version 1.8.6 in /opt/iobroker/node_modules/iobroker.history, node: v8.16.0
2019-10-14 19:15:32.447 - info: history.0 enabled logging of Außentemperatur (Count=1), Alias=true
2019-10-14 19:15:32.448 - info: history.0 enabled logging of hm-rpc.2.LEQ0846785.4.VALVE_STATE (Count=2), Alias=false
2019-10-14 19:15:32.449 - info: history.0 enabled logging of hm-rpc.2.MEQ0053460.4.VALVE_STATE (Count=3), Alias=false
2019-10-14 19:15:32.449 - info: history.0 enabled logging of hm-rpc.2.MEQ0055761.4.VALVE_STATE (Count=4), Alias=false
2019-10-14 19:15:32.450 - info: history.0 enabled logging of hm-rpc.2.MEQ0055771.4.VALVE_STATE (Count=5), Alias=false
2019-10-14 19:15:32.450 - info: history.0 enabled logging of Badezimmer klein Temperatur (Count=6), Alias=true
2019-10-14 19:15:32.450 - info: history.0 enabled logging of hm-rpc.2.MEQ0451694.4.VALVE_STATE (Count=7), Alias=false
2019-10-14 19:15:32.450 - info: history.0 enabled logging of Wohn- Esszimmer Temperatur (Count=8), Alias=true
2019-10-14 19:15:32.451 - info: history.0 enabled logging of Kinderzimmer Temperatur (Count=9), Alias=true
2019-10-14 19:15:32.451 - info: history.0 enabled logging of Badezimmer Temperatur (Count=10), Alias=true
2019-10-14 19:15:32.451 - info: history.0 enabled logging of hm-rpc.2.OEQ1670804.1.TEMPERATURE (Count=11), Alias=false
2019-10-14 19:15:32.452 - info: history.0 enabled logging of hm-rpc.2.OEQ1714060.4.VALVE_STATE (Count=12), Alias=false
2019-10-14 19:15:34.757 - info: host.ioBroker-RasPi instance system.adapter.hm-rpc.1 started with pid 21656
2019-10-14 19:15:38.299 - info: hm-rpc.1 States connected to redis: 127.0.0.1:6379
2019-10-14 19:15:38.370 - info: hm-rpc.1 starting. Version 1.10.0 in /opt/iobroker/node_modules/iobroker.hm-rpc, node: v8.16.0
2019-10-14 19:15:38.564 - info: hm-rpc.1 [META] Meta data updated
2019-10-14 19:15:38.806 - info: host.ioBroker-RasPi instance system.adapter.hm-rpc.2 started with pid 21670
2019-10-14 19:15:40.922 - info: hm-rpc.2 States connected to redis: 127.0.0.1:6379
2019-10-14 19:15:41.041 - info: hm-rpc.2 starting. Version 1.10.0 in /opt/iobroker/node_modules/iobroker.hm-rpc, node: v8.16.0
2019-10-14 19:15:41.298 - info: hm-rpc.2 [META] Meta data updated
2019-10-14 19:15:42.740 - info: host.ioBroker-RasPi instance system.adapter.hm-rega.1 started with pid 21684
2019-10-14 19:15:42.762 - info: hm-rpc.1 binrpc server is trying to listen on 192.168.0.206:18701
2019-10-14 19:15:42.763 - info: hm-rpc.1 binrpc client is trying to connect to 192.168.0.10:8701/ with ["xmlrpc_bin://192.168.0.206:18701","hm-rpc.1"]
2019-10-14 19:15:43.091 - info: hm-rpc.1 binrpc -> listDevices 18
2019-10-14 19:15:43.125 - info: hm-rpc.1 new CUxD devices/channels after filter: 0
2019-10-14 19:15:43.131 - info: hm-rpc.1 Connected
2019-10-14 19:15:45.220 - info: hm-rpc.2 binrpc server is trying to listen on 192.168.0.206:12001
2019-10-14 19:15:45.220 - info: hm-rpc.2 binrpc client is trying to connect to 192.168.0.10:2001/ with ["xmlrpc_bin://192.168.0.206:12001","hm-rpc.2"]
2019-10-14 19:15:45.259 - info: hm-rpc.2 binrpc <- system.listMethods ["hm-rpc.2"]
2019-10-14 19:15:45.276 - info: hm-rpc.2 binrpc <- listDevices ["hm-rpc.2"]
2019-10-14 19:15:45.307 - info: hm-rpc.2 binrpc -> 248 devices
2019-10-14 19:15:45.557 - info: hm-rpc.2 Connected
2019-10-14 19:15:46.655 - info: hm-rega.1 States connected to redis: 127.0.0.1:6379
2019-10-14 19:15:46.736 - info: host.ioBroker-RasPi instance system.adapter.pushover.0 started with pid 21694
2019-10-14 19:15:46.753 - info: hm-rega.1 starting. Version 2.4.12 in /opt/iobroker/node_modules/iobroker.hm-rega, node: v8.16.0
2019-10-14 19:15:46.809 - info: hm-rega.1 subscribe hm-rpc.2.BidCoS-RF.50.PRESS_SHORT
2019-10-14 19:15:46.931 - info: hm-rega.1 ReGaHSS 192.168.0.10 up
2019-10-14 19:15:47.036 - info: hm-rega.1 time difference local-ccu 0s
2019-10-14 19:15:47.073 - info: hm-rega.1 update favorites to enum.favorites
2019-10-14 19:15:47.119 - info: hm-rega.1 update functions to enum.functions
2019-10-14 19:15:47.210 - info: hm-rega.1 update rooms to enum.rooms
2019-10-14 19:15:47.965 - info: hm-rega.1 hm-rpc.2.MEQ0345075.1 has been added to room Wohn- Esszimmer
2019-10-14 19:15:47.965 - info: hm-rega.1 hm-rpc.2.LEQ0751823.1 has been added to room Wohn- Esszimmer
2019-10-14 19:15:47.966 - info: hm-rega.1 hm-rpc.2.LEQ0846785.4 has been added to room Wohn- Esszimmer
2019-10-14 19:15:47.966 - info: hm-rega.1 hm-rpc.2.MEQ0397792.2 has been removed from room Wohn- Esszimmer
2019-10-14 19:15:47.967 - info: hm-rega.1 hm-rpc.2.MEQ0397792.1 has been removed from room Wohn- Esszimmer
2019-10-14 19:15:47.967 - info: hm-rega.1 hm-rpc.2.MEQ0399707.2 has been removed from room Wohn- Esszimmer
2019-10-14 19:15:47.967 - info: hm-rega.1 hm-rpc.2.MEQ0399707.1 has been removed from room Wohn- Esszimmer
2019-10-14 19:15:47.970 - info: hm-rega.1 hm-rpc.2.OEQ0538939.3 has been added to room Schlafzimmer
2019-10-14 19:15:47.971 - info: hm-rega.1 hm-rpc.2.OEQ1714060.4 has been added to room Schlafzimmer
2019-10-14 19:15:47.971 - info: hm-rega.1 hm-rpc.2.OEQ0484079.1 has been removed from room Schlafzimmer
2019-10-14 19:15:47.972 - info: hm-rega.1 hm-rpc.2.OEQ0484079.2 has been removed from room Schlafzimmer
2019-10-14 19:15:48.004 - info: hm-rega.1 hm-rpc.2.NEQ0946032.1 has been added to room Flur
2019-10-14 19:15:48.005 - info: hm-rega.1 hm-rpc.2.MEQ0670337.2 has been removed from room Flur
2019-10-14 19:15:48.005 - info: hm-rega.1 hm-rpc.2.MEQ0670337.1 has been removed from room Flur
2019-10-14 19:15:48.375 - info: pushover.0 States connected to redis: 127.0.0.1:6379
2019-10-14 19:15:48.438 - info: pushover.0 starting. Version 1.0.4 in /opt/iobroker/node_modules/iobroker.pushover, node: v8.16.0
2019-10-14 19:15:48.851 - info: hm-rega.1 got 21 programs
2019-10-14 19:15:48.914 - info: hm-rega.1 added/updated 21 programs
2019-10-14 19:15:48.915 - info: hm-rega.1 deleted 0 programs
2019-10-14 19:15:49.092 - info: hm-rega.1 got 15 variables
2019-10-14 19:15:49.167 - info: hm-rega.1 added/updated 15 variables
2019-10-14 19:15:49.167 - info: hm-rega.1 deleted 0 variables
2019-10-14 19:15:49.168 - info: hm-rega.1 request state values
2019-10-14 19:15:49.819 - info: hm-rega.1 got state values
2019-10-14 19:16:10.752 - info: host.ioBroker-RasPi instance system.adapter.javascript.0 started with pid 21714
2019-10-14 19:16:14.484 - info: javascript.0 States connected to redis: 127.0.0.1:6379
2019-10-14 19:16:14.532 - info: javascript.0 starting. Version 3.6.4 in /opt/iobroker/node_modules/iobroker.javascript, node: v8.16.0
2019-10-14 19:16:14.583 - info: javascript.0 requesting all states
2019-10-14 19:16:14.587 - info: javascript.0 requesting all objects
2019-10-14 19:16:14.816 - info: host.ioBroker-RasPi instance scheduled system.adapter.ical.0 0 * * * *
2019-10-14 19:16:14.833 - info: host.ioBroker-RasPi instance system.adapter.ical.0 started with pid 21728
2019-10-14 19:16:16.271 - info: javascript.0 received all states
2019-10-14 19:16:17.283 - info: ical.0 States connected to redis: 127.0.0.1:6379
2019-10-14 19:16:17.390 - info: ical.0 starting. Version 1.7.0 in /opt/iobroker/node_modules/iobroker.ical, node: v8.16.0
2019-10-14 19:16:17.719 - info: javascript.0 received all objects
2019-10-14 19:16:17.891 - info: javascript.0 Start javascript script.js.Briefkasten.Briefkasten_voll_leer
2019-10-14 19:16:17.918 - info: javascript.0 script.js.Briefkasten.Briefkasten_voll_leer: registered 1 subscription and 0 schedules
2019-10-14 19:16:17.919 - info: javascript.0 Start javascript script.js.Anwesenheit.Anwesenheit_max
2019-10-14 19:16:17.923 - info: javascript.0 script.js.Anwesenheit.Anwesenheit_max: registered 1 subscription and 0 schedules
2019-10-14 19:16:17.924 - info: javascript.0 Start javascript script.js.Anwesenheit.Anwesenheit_jelena
2019-10-14 19:16:17.929 - info: javascript.0 script.js.Anwesenheit.Anwesenheit_jelena: registered 1 subscription and 0 schedules
2019-10-14 19:16:17.930 - info: javascript.0 Start javascript script.js.Anwesenheit.Abwesenheit_Bedingung
2019-10-14 19:16:17.933 - info: javascript.0 script.js.Anwesenheit.Abwesenheit_Bedingung: registered 1 subscription and 0 schedules
2019-10-14 19:16:17.935 - info: javascript.0 Start javascript script.js.Anwesenheit.Abwesenheit_master
2019-10-14 19:16:17.939 - info: javascript.0 script.js.Anwesenheit.Abwesenheit_master: registered 2 subscriptions and 0 schedules
2019-10-14 19:16:17.940 - info: javascript.0 Start javascript script.js.Internetradio.Wandtaster_Bedienung
2019-10-14 19:16:17.946 - info: javascript.0 script.js.Internetradio.Wandtaster_Bedienung: registered 12 subscriptions and 0 schedules
2019-10-14 19:16:18.745 - info: host.ioBroker-RasPi instance system.adapter.iot.0 started with pid 21742
2019-10-14 19:16:20.996 - info: iot.0 States connected to redis: 127.0.0.1:6379
2019-10-14 19:16:21.198 - info: iot.0 starting. Version 1.1.8 in /opt/iobroker/node_modules/iobroker.iot, node: v8.16.0
2019-10-14 19:16:21.240 - info: iot.0 Connecting with a18wym7vjdl22g.iot.eu-west-1.amazonaws.com
2019-10-14 19:16:23.091 - info: ical.0 processing URL: Abfallkalender https://calendar.google.com/calendar/ical/5sj5sklb37t0dmuchmgoh81gm0%40group.calendar.google.com/private-2972214c632eabd90b51ae825f09ff2f/basic.ics
2019-10-14 19:16:28.702 - info: host.ioBroker-RasPi instance system.adapter.ical.0 terminated with code 0 (OK)
2019-10-14 19:16:30.829 - info: iot.0 Connection changed: connect
2019-10-14 19:17:14.760 - info: iot.0 Request google home devices
2019-10-14 19:17:24.763 - info: iot.0 Request google home devices
2019-10-14 19:17:33.860 - warn: iot.0 [GHOME] No devices defined. Did you add not sensor or indicate states to rooms and enums?
2019-10-14 19:17:34.764 - info: iot.0 Request google home devices
2019-10-14 19:17:44.764 - info: iot.0 Request google home devices
2019-10-14 19:17:54.856 - info: iot.0 Request google home devices
2019-10-14 19:18:01.086 - info: iot.0 Request google home devices
2019-10-14 19:18:11.088 - info: iot.0 Request google home devices
2019-10-14 19:18:21.088 - info: iot.0 Request google home devices
2019-10-14 19:18:31.225 - info: iot.0 Request google home devices
2019-10-14 19:18:41.092 - info: iot.0 Request google home devices
2019-10-14 19:19:05.959 - info: host.ioBroker-RasPi object change system.adapter.iot.0
2019-10-14 19:19:05.963 - info: host.ioBroker-RasPi stopInstance system.adapter.iot.0
2019-10-14 19:19:05.964 - info: host.ioBroker-RasPi stopInstance system.adapter.iot.0 killing pid 21742
2019-10-14 19:19:06.047 - error: Caught by controller[7]: (node:21742) UnhandledPromiseRejectionWarning: TypeError: Cannot read property 'smartName' of undefined
2019-10-14 19:19:06.048 - error: Caught by controller[7]: at GoogleHome.getSmartName (/opt/iobroker/node_modules/iobroker.iot/lib/GoogleHome.js:1316:38)
2019-10-14 19:19:06.049 - error: Caught by controller[7]: at Object.keys.forEach.id (/opt/iobroker/node_modules/iobroker.iot/lib/GoogleHome.js:1704:38)
2019-10-14 19:19:06.049 - error: Caught by controller[7]: at Array.forEach ()
2019-10-14 19:19:06.049 - error: Caught by controller[7]: at _readObjects.then.data (/opt/iobroker/node_modules/iobroker.iot/lib/GoogleHome.js:1703:38)
2019-10-14 19:19:06.050 - error: Caught by controller[7]: at
2019-10-14 19:19:06.050 - error: Caught by controller[8]: (node:21742) UnhandledPromiseRejectionWarning: 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(). (rejection id: 12)
2019-10-14 19:19:06.050 - info: host.ioBroker-RasPi instance system.adapter.iot.0 terminated with code 0 (OK)
2019-10-14 19:19:08.481 - info: host.ioBroker-RasPi instance system.adapter.iot.0 started with pid 21833
2019-10-14 19:19:10.767 - info: iot.0 States connected to redis: 127.0.0.1:6379
2019-10-14 19:19:11.615 - info: iot.0 starting. Version 1.1.8 in /opt/iobroker/node_modules/iobroker.iot, node: v8.16.0
2019-10-14 19:19:11.661 - info: iot.0 Connecting with a18wym7vjdl22g.iot.eu-west-1.amazonaws.com
2019-10-14 19:19:12.590 - info: iot.0 Connection changed: connect
2019-10-14 19:43:20.903 - warn: iot.0 [GHOME] No devices defined. Did you add not sensor or indicate states to rooms and enums?
2019-10-14 20:00:00.065 - info: host.ioBroker-RasPi instance system.adapter.ical.0 started with pid 22429
2019-10-14 20:00:02.107 - info: ical.0 States connected to redis: 127.0.0.1:6379
2019-10-14 20:00:02.210 - info: ical.0 starting. Version 1.7.0 in /opt/iobroker/node_modules/iobroker.ical, node: v8.16.0
2019-10-14 20:00:45.506 - warn: ical.0 Error reading from URL "https://calendar.google.com/calendar/ical/5sj5sklb37t0dmuchmgoh81gm0%40group.calendar.google.com/private-2972214c632eabd90b51ae825f09ff2f/basic.ics": Error: getaddrinfo EAI_AGAIN calendar.google.com:443
2019-10-14 20:00:45.508 - warn: ical.0 Error reading "https://calendar.google.com/calendar/ical/5sj5sklb37t0dmuchmgoh81gm0%40group.calendar.google.com/private-2972214c632eabd90b51ae825f09ff2f/basic.ics": Error: getaddrinfo EAI_AGAIN calendar.google.com:443
2019-10-14 20:00:45.515 - info: ical.0 Set events.3.Hausmüll to false
2019-10-14 20:00:51.072 - info: host.ioBroker-RasPi instance system.adapter.ical.0 terminated with code 0 (OK)
2019-10-14 21:00:00.066 - info: host.ioBroker-RasPi instance system.adapter.ical.0 started with pid 23261
2019-10-14 21:00:02.129 - info: ical.0 States connected to redis: 127.0.0.1:6379
2019-10-14 21:00:02.223 - info: ical.0 starting. Version 1.7.0 in /opt/iobroker/node_modules/iobroker.ical, node: v8.16.0
2019-10-14 21:00:33.059 - info: ical.0 processing URL: Abfallkalender https://calendar.google.com/calendar/ical/5sj5sklb37t0dmuchmgoh81gm0%40group.calendar.google.com/private-2972214c632eabd90b51ae825f09ff2f/basic.ics
2019-10-14 21:00:33.079 - info: ical.0 Set events.3.Hausmüll to true
2019-10-14 21:00:38.629 - info: host.ioBroker-RasPi instance system.adapter.ical.0 terminated with code 0 (OK)
2019-10-14 21:36:49.655 - warn: iot.0 [GHOME] No devices defined. Did you add not sensor or indicate states to rooms and enums?
2019-10-14 21:37:26.574 - info: iot.0 Request google home devices
2019-10-14 21:37:36.573 - info: iot.0 Request google home devices
2019-10-14 21:37:46.577 - info: iot.0 Request google home devices
2019-10-14 21:37:56.578 - info: iot.0 Request google home devices
2019-10-14 21:38:06.576 - info: iot.0 Request google home devices

Hat jemand ne Idee? @apollon77

Bin ich hier im richtigen Thread?

BBTown

@fantasticmaxpower
Du müßtest im IoT Adapter unter der Rubrik"Intelligente Aufzählungen" einmal sowohl innerhalb der Funktionen als auch Räumen diese Aktivieren, dann sollten bspw. die Geräte in der Google-Übersicht erscheinen.

Erst wenn dort Einträge vorhanden sind, können diese in der App gefunden werden.

fantasticmaxpower

@BBTown Hi, es sind alle Funktionen und Räume unter "intelligente Aufzählungen" eingeschaltet. Aber es findet trotzdem keine Verbindung statt.

Du meinst diese blauen Schiebeschalter oder? Die sind alle nacht rechts geschoben und blau

NEWS

[iot] Andere Probleme mit dem iot-Adapter bzw der Nutzung

Support us

253

32.4k

81.4k

1.3m