Navigation

    Logo
    • Register
    • Login
    • Search
    • Recent
    • Tags
    • Unread
    • Categories
    • Unreplied
    • Popular
    • GitHub
    • Docu
    • Hilfe
    1. Home
    2. Deutsch
    3. ioBroker Allgemein
    4. [iot-Aktion] iot-Adapter verbindet sich nicht bzw Verbindung ist "gelb"

    NEWS

    • Neuer Blog: Fotos und Eindrücke aus Solingen

    • ioBroker@Smart Living Forum Solingen, 14.06. - Agenda added

    • ioBroker goes Matter ... Matter Adapter in Stable

    [iot-Aktion] iot-Adapter verbindet sich nicht bzw Verbindung ist "gelb"

    This topic has been deleted. Only users with topic management privileges can see it.
    • S
      stanby last edited by

      Vielen Dank für den Tip. Habe es gefunden. Manchmal sieht man den Wald vor Bäumen nicht. Funktioniert wieder alles.

      Gruß

      Wolfgang

      1 Reply Last reply Reply Quote 0
      • nukleuz
        nukleuz last edited by

        Habe heute auf Multihost umgestellt danach blieb der iot-Adapter gelb.

        Neue Keys angefordert und die Zugangsdaten (Passwort) neu eingegeben, obwohl vorhanden.

        Jetzt läuft wieder alles.

        1 Reply Last reply Reply Quote 0
        • Elzershark
          Elzershark last edited by 

          iot.0	2019-01-22 13:03:56.521	info	Connection changed: disconnect
iot.0	2019-01-22 13:03:56.520	error	premature close
iot.0	2019-01-22 13:03:26.512	debug	reconnect
iot.0	2019-01-22 13:03:21.503	info	Connection changed: disconnect
iot.0	2019-01-22 13:03:21.501	error	premature close
iot.0	2019-01-22 13:03:21.491	debug	offline
iot.0	2019-01-22 12:03:07.031	debug	system.adapter.admin.0: logging true
iot.0	2019-01-22 12:02:57.504	debug	sendTo "enums" to system.adapter.admin.0 from system.adapter.iot.0
iot.0	2019-01-22 12:02:57.503	debug	Created ALEXA device: test ["turnOn","turnOff"]
iot.0	2019-01-22 12:02:57.473	info	Request enums
iot.0	2019-01-22 12:02:56.863	debug	sendTo "browse" to system.adapter.admin.0 from system.adapter.iot.0
iot.0	2019-01-22 12:02:56.860	debug	Created ALEXA device: test ["turnOn","turnOff"]
iot.0	2019-01-22 12:02:56.800	info	Request devices
iot.0	2019-01-22 12:02:54.863	debug	system.adapter.admin.0: logging false
iot.0	2019-01-22 12:02:52.190	warn	Invalid URL key. Status update is disabled: {"error":{"error":"No license found or license is no more valid"}}
iot.0	2019-01-22 12:02:52.188	error	Cannot report device state: null
iot.0	2019-01-22 12:02:51.326	debug	URL key is {"key":"1efcc810-1e3a-11e9-806c-237f48ccfdf7"}
iot.0	2019-01-22 12:02:51.293	debug	Created ALEXA device: test ["turnOn","turnOff"]
iot.0	2019-01-22 12:02:51.135	info	Connecting with a18wym7vjdl22g.iot.eu-west-1.amazonaws.com
iot.0	2019-01-22 12:02:51.106	info	starting. Version 0.3.1 in /opt/iobroker/node_modules/iobroker.iot, node: v8.15.0
iot.0	2019-01-22 12:02:50.928	debug	statesDB connected
iot.0	2019-01-22 12:02:50.863	debug	objectDB connected
host.raspberrypi	2019-01-22 12:02:48.971	info	instance system.adapter.iot.0 started with pid 3558
host.raspberrypi	2019-01-22 12:02:46.505	info	instance system.adapter.iot.0 terminated with code 0 (OK)
host.raspberrypi	2019-01-22 12:02:46.446	info	stopInstance system.adapter.iot.0 killing pid 3349
host.raspberrypi	2019-01-22 12:02:46.445	info	stopInstance system.adapter.iot.0

          Bleibt Gelb…

          mit license...

          iot.0	2019-01-22 13:12:30.309	info	Connection changed: disconnect
iot.0	2019-01-22 13:12:30.308	error	premature close
iot.0	2019-01-22 13:12:00.296	debug	reconnect
iot.0	2019-01-22 13:11:55.294	info	Connection changed: disconnect
iot.0	2019-01-22 13:11:55.292	error	premature close
iot.0	2019-01-22 13:11:55.282	debug	offline
iot.0	2019-01-22 13:11:25.276	debug	URL key is {"key":"1efcc810-1e3a-11e9-806c-237f48ccfdf7"}
iot.0	2019-01-22 12:11:23.240	debug	Subscribe done
iot.0	2019-01-22 12:11:23.239	debug	Subscribe 0 states for google home
iot.0	2019-01-22 12:11:23.238	debug	CHECK URL reported: "{\"result\":\"OK\"}"
iot.0	2019-01-22 12:11:22.855	debug	Created ALEXA device: test ["turnOn","turnOff"]
iot.0	2019-01-22 12:11:22.772	debug	Fetching keys...
iot.0	2019-01-22 12:11:22.684	info	Connecting with a18wym7vjdl22g.iot.eu-west-1.amazonaws.com
iot.0	2019-01-22 12:11:22.656	info	starting. Version 0.3.1 in /opt/iobroker/node_modules/iobroker.iot, node: v8.15.0
iot.0	2019-01-22 12:11:22.491	debug	statesDB connected
iot.0	2019-01-22 12:11:22.358	debug	objectDB connected
host.raspberrypi	2019-01-22 12:11:20.587	info	instance system.adapter.iot.0 started with pid 3749
          1 Reply Last reply Reply Quote 0
          • marcuskl
            marcuskl last edited by

            Bei mir kommt täglich diese Meldung~~![](</s><URL url=)<link_text text="https://uploads.tapatalk-cdn.com/201901 ... 36f469.jpg">https://uploads.tapatalk-cdn.com/20190124/3f2df4d08dac3f1488bb1d2ecd36f469.jpg</link_text>" />

            Gesendet von meinem SM-G950F mit Tapatalk~~

            1 Reply Last reply Reply Quote 0
            • apollon77
              apollon77 last edited by

              Der Fehler kommt aus der Google Home Library. Wie hast du das denn hinbekommen?

              1 Reply Last reply Reply Quote 0
              • marcuskl
                marcuskl last edited by

                @apollon77:

                Der Fehler kommt aus der Google Home Library. Wie hast du das denn hinbekommen? ` Ich habe den Adapter nicht mal

                Gesendet von meinem SM-G950F mit Tapatalk

                1 Reply Last reply Reply Quote 0
                • apollon77
                  apollon77 last edited by

                  iot hat schon eine Basisunterstützung für Google Home drin und daher kommt der Fehler.

                  Komisch. ignorier es mal

                  1 Reply Last reply Reply Quote 0
                  • Elzershark
                    Elzershark last edited by

                    Wer diesen Fehler auch hat , muss/sollte bei seinem Linux System ipv6 ausschalten. Amazon verhindert/verzögert das verbinden zur Cloud URL und die iot-Cloud bleibt gelb.

                    unter anderem steht im log auch "timeout". und die Cloud versucht sich zig mal zu verbinden

                    @Elzershark:

                    iot.0	2019-01-22 13:03:56.521	info	Connection changed: disconnect
iot.0	2019-01-22 13:03:56.520	error	premature close
iot.0	2019-01-22 13:03:26.512	debug	reconnect
iot.0	2019-01-22 13:03:21.503	info	Connection changed: disconnect
iot.0	2019-01-22 13:03:21.501	error	premature close
iot.0	2019-01-22 13:03:21.491	debug	offline
iot.0	2019-01-22 12:03:07.031	debug	system.adapter.admin.0: logging true
iot.0	2019-01-22 12:02:57.504	debug	sendTo "enums" to system.adapter.admin.0 from system.adapter.iot.0
iot.0	2019-01-22 12:02:57.503	debug	Created ALEXA device: test ["turnOn","turnOff"]
iot.0	2019-01-22 12:02:57.473	info	Request enums
iot.0	2019-01-22 12:02:56.863	debug	sendTo "browse" to system.adapter.admin.0 from system.adapter.iot.0
iot.0	2019-01-22 12:02:56.860	debug	Created ALEXA device: test ["turnOn","turnOff"]
iot.0	2019-01-22 12:02:56.800	info	Request devices
iot.0	2019-01-22 12:02:54.863	debug	system.adapter.admin.0: logging false
iot.0	2019-01-22 12:02:52.190	warn	Invalid URL key. Status update is disabled: {"error":{"error":"No license found or license is no more valid"}}
iot.0	2019-01-22 12:02:52.188	error	Cannot report device state: null
iot.0	2019-01-22 12:02:51.326	debug	URL key is {"key":"1efcc810-1e3a-11e9-806c-237f48ccfdf7"}
iot.0	2019-01-22 12:02:51.293	debug	Created ALEXA device: test ["turnOn","turnOff"]
iot.0	2019-01-22 12:02:51.135	info	Connecting with a18wym7vjdl22g.iot.eu-west-1.amazonaws.com
iot.0	2019-01-22 12:02:51.106	info	starting. Version 0.3.1 in /opt/iobroker/node_modules/iobroker.iot, node: v8.15.0
iot.0	2019-01-22 12:02:50.928	debug	statesDB connected
iot.0	2019-01-22 12:02:50.863	debug	objectDB connected
host.raspberrypi	2019-01-22 12:02:48.971	info	instance system.adapter.iot.0 started with pid 3558
host.raspberrypi	2019-01-22 12:02:46.505	info	instance system.adapter.iot.0 terminated with code 0 (OK)
host.raspberrypi	2019-01-22 12:02:46.446	info	stopInstance system.adapter.iot.0 killing pid 3349
host.raspberrypi	2019-01-22 12:02:46.445	info	stopInstance system.adapter.iot.0

                    Bleibt Gelb…

                    mit license...

                    iot.0	2019-01-22 13:12:30.309	info	Connection changed: disconnect
iot.0	2019-01-22 13:12:30.308	error	premature close
iot.0	2019-01-22 13:12:00.296	debug	reconnect
iot.0	2019-01-22 13:11:55.294	info	Connection changed: disconnect
iot.0	2019-01-22 13:11:55.292	error	premature close
iot.0	2019-01-22 13:11:55.282	debug	offline
iot.0	2019-01-22 13:11:25.276	debug	URL key is {"key":"1efcc810-1e3a-11e9-806c-237f48ccfdf7"}
iot.0	2019-01-22 12:11:23.240	debug	Subscribe done
iot.0	2019-01-22 12:11:23.239	debug	Subscribe 0 states for google home
iot.0	2019-01-22 12:11:23.238	debug	CHECK URL reported: "{\"result\":\"OK\"}"
iot.0	2019-01-22 12:11:22.855	debug	Created ALEXA device: test ["turnOn","turnOff"]
iot.0	2019-01-22 12:11:22.772	debug	Fetching keys...
iot.0	2019-01-22 12:11:22.684	info	Connecting with a18wym7vjdl22g.iot.eu-west-1.amazonaws.com
iot.0	2019-01-22 12:11:22.656	info	starting. Version 0.3.1 in /opt/iobroker/node_modules/iobroker.iot, node: v8.15.0
iot.0	2019-01-22 12:11:22.491	debug	statesDB connected
iot.0	2019-01-22 12:11:22.358	debug	objectDB connected
host.raspberrypi	2019-01-22 12:11:20.587	info	instance system.adapter.iot.0 started with pid 3749
```` `
                    1 Reply Last reply Reply Quote 0
                    • apollon77
                      apollon77 last edited by

                      @marcuskl:

                      Bei mir kommt täglich diese Meldung![](</s><URL url=)<link_text text="https://uploads.tapatalk-cdn.com/201901 ... 36f469.jpg">https://uploads.tapatalk-cdn.com/20190124/3f2df4d08dac3f1488bb1d2ecd36f469.jpg</link_text>" /> ` AM Ende aktuell zu ignorieren. Wird mit einer kommenden iot Version gefixt

                      1 Reply Last reply Reply Quote 0
                      • Messiahs
                        Messiahs last edited by

                        @apollon77:

                        Nur zur Info.. Meldung kommt bei mir auch. Grundsätzlich lassen sich die Geräte aber über Alexa steuern.

                        Habe aber zusätzlich:

                        iot.0	2019-01-25 23:17:32.308	info	Connection changed: connect
iot.0	2019-01-25 23:17:30.455	warn	Invalid URL key. Status update is disabled: {"error":{"error":"No license found or license is no more valid"}}
iot.0	2019-01-25 23:17:30.454	error	Cannot report device state: null

                        eine Option in ioBroker.pro um iot zu abonieren, habe ich nicht… es wird nur Fernverwaltung angeboten...

                        1 Reply Last reply Reply Quote 0
                        • apollon77
                          apollon77 last edited by

                          Bitte die Meldung aktuell einfach ignorieren. Die kommt aus dem Google-Home Modul und sollte an sich nicht da sein, aber hat auf Alexa keinen Effekt 🙂

                          1 Reply Last reply Reply Quote 0
                          • First post
                            Last post

                          Support us

                          ioBroker
                          Community Adapters
                          Donate
                          FAQ Cloud / IOT
                          HowTo: Node.js-Update
                          HowTo: Backup/Restore
                          Downloads
                          BLOG

                          655
                          Online

                          31.9k
                          Users

                          80.1k
                          Topics

                          1.3m
                          Posts

                          15
                          48
                          7330
                          Loading More Posts
                          • Oldest to Newest
                          • Newest to Oldest
                          • Most Votes
                          Reply
                          • Reply as topic
                          Log in to reply
                          Community
                          Impressum | Datenschutz-Bestimmungen | Nutzungsbedingungen
                          The ioBroker Community 2014-2023
                          logo