Navigation

    Logo
    • Register
    • Login
    • Search
    • Recent
    • Tags
    • Unread
    • Categories
    • Unreplied
    • Popular
    • GitHub
    • Docu
    • Hilfe
    1. Home
    2. Deutsch
    3. Cloud Dienste
    4. IoT Adapter: alle Geräte verschwunden

    NEWS

    • Wir empfehlen: Node.js 22.x

    • Neuer Blog: Fotos und Eindrücke aus Solingen

    • ioBroker goes Matter ... Matter Adapter in Stable

    IoT Adapter: alle Geräte verschwunden

    This topic has been deleted. Only users with topic management privileges can see it.
    • Thomas Braun
      Thomas Braun Most Active @Zwer2k last edited by

      @Zwer2k Steht was im Log file wenn der Adapter startet?

      Z 1 Reply Last reply Reply Quote 0
      • Z
        Zwer2k @Thomas Braun last edited by

        @Thomas-Braun

        Ich kann keine Hinweise erkennen

        iot.0	2020-08-14 23:15:51.455	info	(30457) Connection changed: connect
        iot.0	2020-08-14 23:15:51.177	info	(30457) Connecting with a1aaaaaaaadl22g.iot.eu-west-1.amazonaws.com
        iot.0	2020-08-14 23:15:51.162	info	(30457) starting. Version 1.6.4 in /opt/iobroker/node_modules/iobroker.iot, node: v12.16.3, js-controller: 3.1.4
        iot.0	2020-08-14 23:15:47.408	info	(29720) Connection lost
        iot.0	2020-08-14 23:15:47.408	info	(29720) Connection changed: disconnect
        iot.0	2020-08-14 23:15:47.360	info	(29720) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
        iot.0	2020-08-14 23:15:47.359	info	(29720) terminating
        iot.0	2020-08-14 23:15:47.355	info	(29720) Got terminate signal TERMINATE_YOURSELF
        
        Thomas Braun Glasfaser 2 Replies Last reply Reply Quote 0
        • Thomas Braun
          Thomas Braun Most Active @Zwer2k last edited by

          @Zwer2k Aktualisier vielleicht mal den Adapter

          Z 1 Reply Last reply Reply Quote 0
          • Z
            Zwer2k @Thomas Braun last edited by

            @Thomas-Braun
            Vielen Dank für das schnelle Antworten.

            Komischerweise wurde mir erst vor einigen Minuten Aktualisierung auf 1.7.0 angeboten, hab ich auch gleich aktualisiert. Hat leider auch nichts gebracht.

            Thomas Braun 1 Reply Last reply Reply Quote 0
            • Thomas Braun
              Thomas Braun Most Active @Zwer2k last edited by

              @Zwer2k Das sieht mir zwar danach aus, aber nodejs ist richtig im System?

              lsb_release -a && whoami && which nodejs && nodejs -v && which node && node -v && which npm && npm -v && apt policy nodejs
              
              Z 1 Reply Last reply Reply Quote 0
              • Z
                Zwer2k @Thomas Braun last edited by

                @Thomas-Braun sagte in IoT Adapter: alle Geräte verschwunden:

                lsb_release -a && whoami && which nodejs && nodejs -v && which node && node -v && which npm && npm -v && apt policy nodejs

                Sonst funktioniert eigentlich alles

                root@docker1:/home/myuser# docker exec -it iobroker bash
                root@iobroker1:/opt/iobroker# lsb_release -a && whoami && which nodejs && nodejs -v && which node && node -v && which npm && npm -v && apt policy nodejs
                No LSB modules are available.
                Distributor ID: Debian
                Description:    Debian GNU/Linux 9.12 (stretch)
                Release:        9.12
                Codename:       stretch
                root
                /usr/bin/nodejs
                v12.16.3
                /usr/bin/node
                v12.16.3
                /usr/bin/npm
                6.14.5
                nodejs:
                  Installiert:           12.16.3-1nodesource1
                  Installationskandidat: 12.16.3-1nodesource1
                  Versionstabelle:
                 *** 12.16.3-1nodesource1 100
                        100 /var/lib/dpkg/status
                
                
                Thomas Braun 1 Reply Last reply Reply Quote 0
                • Thomas Braun
                  Thomas Braun Most Active @Zwer2k last edited by

                  @Zwer2k
                  Das ist wie erwartet i.O.
                  Auch wenn ich kein Fan von root-shells auf den Dockern bin.

                  1 Reply Last reply Reply Quote 0
                  • Glasfaser
                    Glasfaser @Zwer2k last edited by

                    @Zwer2k sagte in IoT Adapter: alle Geräte verschwunden:

                    Ich kann keine Hinweise erkennen

                    Stelle mal auf silly um ... die Info Log sagt im Allgemeinen nicht viel aus .

                    Z 1 Reply Last reply Reply Quote 0
                    • Z
                      Zwer2k @Glasfaser last edited by

                      @Glasfaser

                      2020-08-15 00:27:36.643  - info: host.iobroker1 instance system.adapter.iot.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
                      2020-08-15 00:27:39.103  - info: host.iobroker1 instance system.adapter.iot.0 started with pid 8715
                      2020-08-15 00:27:39.580  - debug: iot.0 (8715) Redis Objects: Use Redis connection: 192.168.144.180:6379
                      2020-08-15 00:27:39.593  - debug: iot.0 (8715) Objects client ready ... initialize now
                      2020-08-15 00:27:39.595  - debug: iot.0 (8715) Objects create System PubSub Client
                      2020-08-15 00:27:39.596  - debug: iot.0 (8715) Objects create User PubSub Client
                      2020-08-15 00:27:39.596  - debug: iot.0 (8715) Objects client initialize lua scripts
                      2020-08-15 00:27:39.601  - debug: iot.0 (8715) Objects connected to redis: 192.168.144.180:6379
                      2020-08-15 00:27:39.603  - debug: iot.0 (8715) objectDB connected
                      2020-08-15 00:27:39.604  - debug: iot.0 (8715) Redis States: Use Redis connection: 192.168.144.180:6379
                      2020-08-15 00:27:39.607  - debug: iot.0 (8715) States create User PubSub Client
                      2020-08-15 00:27:39.608  - debug: iot.0 (8715) States create System PubSub Client
                      2020-08-15 00:27:39.615  - debug: iot.0 (8715) States connected to redis: 192.168.144.180:6379
                      2020-08-15 00:27:39.615  - debug: iot.0 (8715) statesDB connected
                      2020-08-15 00:27:39.741  - debug: iot.0 (8715) Plugin sentry Initialize Plugin (enabled=true)
                      2020-08-15 00:27:39.796  - info: iot.0 (8715) starting. Version 1.7.0 in /opt/iobroker/node_modules/iobroker.iot, node: v12.16.3, js-controller: 3.1.4
                      2020-08-15 00:27:39.816  - info: iot.0 (8715) Connecting with 1111111111vjdl22g.iot.eu-west-1.amazonaws.com
                      2020-08-15 00:27:39.831  - silly: iot.0 (8715) States system redis pmessage io.system.adapter.iot.0.logLevel/io.system.adapter.iot.0.logLevel:{"val":"silly","ack":true,"ts":1597444059819,"q":0,"from":"system.adapter.iot.0","lc":159741111111}
                      2020-08-15 00:27:39.838  - debug: iot.0 (8715) URL key is {"key":"<hab ich entfernt>"}, clientId: jr_iobroker_net_topofweb_de
                      2020-08-15 00:27:40.085  - info: iot.0 (8715) Connection changed: connect
                      2020-08-15 00:27:41.178  - debug: iot.0 (8715) [ALEXA] Name "Power" cannot be written and will be ignored
                      2020-08-15 00:27:41.179  - debug: iot.0 (8715) [ALEXA] Created ALEXA device: Wohnzimmer Stehlampe ["turnOn","turnOff"]
                      2020-08-15 00:27:41.179  - debug: iot.0 (8715) [ALEXA] Created ALEXA device: Wohnzimmer Licht ["setPercentage","incrementPercentage","decrementPercentage","turnOn","turnOff"]
                      2020-08-15 00:27:41.179  - debug: iot.0 (8715) [ALEXA] Created ALEXA device: Wohnen Licht ["setPercentage","incrementPercentage","decrementPercentage","turnOn","turnOff"]
                      2020-08-15 00:27:41.179  - debug: iot.0 (8715) [ALEXA] Created ALEXA device: Stehlampe ["turnOn","turnOff"]
                      2020-08-15 00:27:41.180  - debug: iot.0 (8715) [ALEXA] Created ALEXA device: Schlafzimmer ["turnOn","turnOff"]
                      2020-08-15 00:27:41.180  - debug: iot.0 (8715) [ALEXA] Created ALEXA device: Licht Wohnzimmer ["setPercentage","incrementPercentage","decrementPercentage","turnOn","turnOff"]
                      2020-08-15 00:27:41.181  - debug: iot.0 (8715) [ALEXA] Created ALEXA device: Licht Wohnen ["setPercentage","incrementPercentage","decrementPercentage","turnOn","turnOff"]
                      2020-08-15 00:27:41.181  - debug: iot.0 (8715) [ALEXA] Created ALEXA device: Licht Küche ["turnOn","turnOff","setPercentage","incrementPercentage","decrementPercentage"]
                      2020-08-15 00:27:41.181  - debug: iot.0 (8715) [ALEXA] Created ALEXA device: Licht Essen ["turnOn","turnOff"]
                      2020-08-15 00:27:41.181  - debug: iot.0 (8715) [ALEXA] Created ALEXA device: Licht Essecke ["turnOn","turnOff"]
                      2020-08-15 00:27:41.181  - debug: iot.0 (8715) [ALEXA] Created ALEXA device: Küchenlicht ["turnOn","turnOff","setPercentage","incrementPercentage","decrementPercentage"]
                      2020-08-15 00:27:41.181  - debug: iot.0 (8715) [ALEXA] Created ALEXA device: Küche Licht ["turnOn","turnOff","setPercentage","incrementPercentage","decrementPercentage"]
                      2020-08-15 00:27:41.182  - debug: iot.0 (8715) [ALEXA] Created ALEXA device: Essen Licht ["turnOn","turnOff"]
                      2020-08-15 00:27:41.182  - debug: iot.0 (8715) [ALEXA] Created ALEXA device: Essecke Licht ["turnOn","turnOff"]
                      

                      Dann wird mein Log mit sowas vollgespamt

                      2020-08-15 00:27:41.519  - debug: iot.0 (8715) [ALEX3] Invalid state "daswetter.0.NextHours2.Location_1.Day_3.sun_mid". Not exist or no native part.
                      2020-08-15 00:27:41.520  - debug: iot.0 (8715) [ALEX3] Invalid state "daswetter.0.NextHours.Location_1.Day_4.Hour_6.snowline_value". Not exist or no native part.
                      2020-08-15 00:27:41.520  - debug: iot.0 (8715) [ALEX3] Invalid state "daswetter.0.NextHours.Location_1.Day_2.Hour_6.windgusts_value". Not exist or no native part.
                      2020-08-15 00:27:41.520  - debug: iot.0 (8715) [ALEX3] Invalid state "daswetter.0.NextHours2.Location_1.Day_5.Hour_8.snowline". Not exist or no native part.
                      2020-08-15 00:27:41.520  - debug: iot.0 (8715) [ALEX3] Invalid state "daswetter.0.NextDaysDetailed.Location_1.Day_5.Hour_8.humidity_value". Not exist or no native part.
                      2020-08-15 00:27:41.520  - debug: iot.0 (8715) [ALEX3] Invalid state "daswetter.0.NextHours2.Location_1.Day_3.Hour_2.wind_speed". Not exist or no native part.
                      

                      Und zum Schluß noch paar "Created entertainment ALEXA device:" Meldungen

                      Glasfaser 1 Reply Last reply Reply Quote 0
                      • Glasfaser
                        Glasfaser @Zwer2k last edited by

                        @Zwer2k sagte in IoT Adapter: alle Geräte verschwunden:

                        Created ALEXA device: Essecke Licht ["turnOn","turnOff"]

                        Datenpunkt ist eigentlich da ...

                        Starte mal dein komplettes System mal neu , nicht nur ioBroker !

                        Z 1 Reply Last reply Reply Quote 0
                        • Z
                          Zwer2k @Glasfaser last edited by

                          Neustart hat leider nichts gebracht, hab Docker-Server inkl. Redis und der ersten ioBroker-Instanz neugestartet und auch zweite ioBroker-Instanz auf dem CubieTruck.
                          Hab anschließend ioBroker.iot Skill deaktiviert und wieder neu aktiviert und siehe da, zumindest kann ich wieder neue Geräte anlegen die auch wieder zu Alexa synchronisiert werden, die dann auch normal funktionieren.
                          Mich ärgert allerdings schon noch, dass ich alle Geräte neu anlegen muss.

                          @Glasfaser
                          Essecke Licht war ja eins davon wo wieder funktioniert hat. Das habe ich unter Alexa nicht gelöscht gehabt und konnte es daher im Adapter problemlos anlegen.

                          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

                          744
                          Online

                          32.0k
                          Users

                          80.4k
                          Topics

                          1.3m
                          Posts

                          alexa iot pro
                          3
                          12
                          663
                          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