Navigation

    Logo
    • Register
    • Login
    • Search
    • Recent
    • Tags
    • Unread
    • Categories
    • Unreplied
    • Popular
    • GitHub
    • Docu
    • Hilfe
    1. Home
    2. Deutsch
    3. ioBroker Allgemein
    4. Alexa2 Adapter 3.13/3.14/3.15/3.16/3.17 (Beta)

    NEWS

    • js-controller Lucy (Version 7.0) jetzt im Stable Repository

    • ioBroker 10-Jahres Community Treffen - ein kleiner ReCap

    • Tester für Responsive Initiative gesucht

    Alexa2 Adapter 3.13/3.14/3.15/3.16/3.17 (Beta)

    This topic has been deleted. Only users with topic management privileges can see it.
    • Palm_Maniac
      Palm_Maniac @apollon77 last edited by

      @apollon77 sagte in Alexa2 Adapter 3.13/3.14/3.15/3.16/3.17 (Beta):

      Dann mach das doch mal 🙂 Der Entwickler freut sich

      Stimmt, da hast du recht, das hätte ich gleich machen sollen. 🙂

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

        @apollon77 sagte in Alexa2 Adapter 3.13/3.14/3.15/3.16/3.17 (Beta):

        @palm_maniac sagte in Alexa2 Adapter 3.13/3.14/3.15/3.16/3.17 (Beta):

        Außerdem habe ich wohl den Auslöser für das Eigenleben des Lichts gefunden. Mir ist aufgefallen, dass das Treppenlicht 2mal unter Smart-Devices auftauchte mit allen Datenpunkten für RGB Beleuchtung. Das hätte so aber nicht sein dürfen, denn ich hatte dieses Licht garnicht per IOT-Adapter an Alexa übergeben. Also habe ich mir nochmal die Konfig in WLED angeschaut und gesehen, dass dort die Alexa-Unterstützung aktiviert war. Problem erkannt, Problem gebannt.

        Warum es plötzlich was tut wenn nichts gesteuert wird ist dennoch strange

        Ja, zumal diese Datenpunkte in keinem Skript Verwendung finden.

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

          @diginix Den hab ich auf Sentry gesehen. Fix kommt heute abend

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

            @sigi234 Hab schon ne vermutung. Fix heute abend

            Thomas Braun sigi234 2 Replies Last reply Reply Quote 0
            • Thomas Braun
              Thomas Braun Most Active @apollon77 last edited by

              @apollon77

              Das muss aber im Diff von

              alexa2.git#0fd8690ca77e16285030ebbcdbce49b4c56f99a8 ist wieder leise im Log.

              zum Release 3.17.2 zu finden sein.
              Die quasselt mich nämlich auch im Log zu:

              2022-07-12 18:15:30.770  - info: alexa2.0 (74962) State value to set for "alexa2.0.Smart-Home-Devices.4acc0e22-bfb9-4e3e-bdfe-bea4f3912910.connectivity-reason" has to be type "string" but received type "object"
2022-07-12 18:15:30.771  - info: alexa2.0 (74962) State value to set for "alexa2.0.Smart-Home-Devices.d7d81c77-a50c-41cb-9c3a-0450992ae160.connectivity-reason" has to be type "string" but received type "object"
2022-07-12 18:15:30.773  - info: alexa2.0 (74962) State value to set for "alexa2.0.Smart-Home-Devices.f3c8b652-2523-4cd9-b7da-2b125e973bb6.connectivity-reason" has to be type "string" but received type "object"
2022-07-12 18:15:30.773  - info: alexa2.0 (74962) State value to set for "alexa2.0.Smart-Home-Devices.4e18554e-e6fe-4771-8f4e-12fc640761db.connectivity-reason" has to be type "string" but received type "object"
2022-07-12 18:15:30.774  - info: alexa2.0 (74962) State value to set for "alexa2.0.Smart-Home-Devices.d359aeb1-03f5-4cde-9071-179a5924f7fa.connectivity-reason" has to be type "string" but received type "object"
2022-07-12 18:15:30.775  - info: alexa2.0 (74962) State value to set for "alexa2.0.Smart-Home-Devices.0f9cec35-b064-4598-923d-963b29af18b8.connectivity-reason" has to be type "string" but received type "object"
2022-07-12 18:15:30.776  - info: alexa2.0 (74962) State value to set for "alexa2.0.Smart-Home-Devices.7cd146f6-aac1-4b01-98e6-3167447f9e70.connectivity-reason" has to be type "string" but received type "object"
2022-07-12 18:15:30.777  - info: alexa2.0 (74962) State value to set for "alexa2.0.Smart-Home-Devices.ca41d22b-884b-4be1-aa28-ced702d9f694.connectivity-reason" has to be type "string" but received type "object"
2022-07-12 18:15:30.778  - info: alexa2.0 (74962) State value to set for "alexa2.0.Smart-Home-Devices.98257657-55fe-4a59-96ee-bcbb24ee9bc8.colorRgb" has to be type "string" but received type "object"
2022-07-12 18:15:30.814  - info: alexa2.0 (74962) State value to set for "alexa2.0.Smart-Home-Devices.98257657-55fe-4a59-96ee-bcbb24ee9bc8.connectivity-reason" has to be type "string" but received type "object"
2022-07-12 18:15:30.815  - info: alexa2.0 (74962) State value to set for "alexa2.0.Smart-Home-Devices.3c24ecd2-b792-4d5f-9c25-75d7cf57a574.connectivity-reason" has to be type "string" but received type "object"
2022-07-12 18:15:30.816  - info: alexa2.0 (74962) State value to set for "alexa2.0.Smart-Home-Devices.fb3ea3ff-cbdf-423a-9186-11da242e2947.connectivity-reason" has to be type "string" but received type "object"
2022-07-12 18:15:30.816  - info: alexa2.0 (74962) State value to set for "alexa2.0.Smart-Home-Devices.dff78664-0a39-4ee4-aa2b-a9a8e0d7ba31.connectivity-reason" has to be type "string" but received type "object"
2022-07-12 18:15:30.817  - info: alexa2.0 (74962) State value to set for "alexa2.0.Smart-Home-Devices.8bc3f37a-58a8-4d46-82e8-4d84dd10121c.connectivity-reason" has to be type "string" but received type "object"
2022-07-12 18:15:30.817  - info: alexa2.0 (74962) State value to set for "alexa2.0.Smart-Home-Devices.39be3920-5d21-4742-9453-25790bcc07f5.connectivity-reason" has to be type "string" but received type "object"
2022-07-12 18:15:30.818  - info: alexa2.0 (74962) State value to set for "alexa2.0.Smart-Home-Devices.e134e20d-ae41-4394-b4c7-1504ae3e4831.connectivity-reason" has to be type "string" but received type "object"
2022-07-12 18:15:30.818  - info: alexa2.0 (74962) State value to set for "alexa2.0.Smart-Home-Devices.10d02cfd-be52-46a6-84ed-fcaae8db99b7.colorRgb" has to be type "string" but received type "object"
2022-07-12 18:15:30.819  - info: alexa2.0 (74962) State value to set for "alexa2.0.Smart-Home-Devices.10d02cfd-be52-46a6-84ed-fcaae8db99b7.connectivity-reason" has to be type "string" but received type "object"
2022-07-12 18:15:30.820  - info: alexa2.0 (74962) State value to set for "alexa2.0.Smart-Home-Devices.5144a434-eee6-42db-a91b-3b5df7b712e5.connectivity-reason" has to be type "string" but received type "object"
2022-07-12 18:15:30.820  - info: alexa2.0 (74962) State value to set for "alexa2.0.Smart-Home-Devices.3a8fa5bf-7037-4806-aecf-fea3af6070a4.connectivity-reason" has to be type "string" but received type "object"
2022-07-12 18:15:30.821  - info: alexa2.0 (74962) State value to set for "alexa2.0.Smart-Home-Devices.c77e7be4-86da-4595-8223-5ceb6b50254b.connectivity-reason" has to be type "string" but received type "object"
2022-07-12 18:15:30.821  - info: alexa2.0 (74962) State value to set for "alexa2.0.Smart-Home-Devices.4967049f-b2b6-42a5-a0fc-825172dad02a.connectivity-reason" has to be type "string" but received type "object"
2022-07-12 18:15:30.822  - info: alexa2.0 (74962) State value to set for "alexa2.0.Smart-Home-Devices.e7ea8a09-6582-480b-a6a6-935cbbe3275e.connectivity-reason" has to be type "string" but received type "object"
2022-07-12 18:15:30.823  - info: alexa2.0 (74962) State value to set for "alexa2.0.Smart-Home-Devices.81de86f1-23b0-49f6-b5d0-402c197dcba0.connectivity-reason" has to be type "string" but received type "object"
2022-07-12 18:15:30.823  - info: alexa2.0 (74962) State value to set for "alexa2.0.Smart-Home-Devices.6c714265-c3e0-450a-b7e0-5acf25326e57.connectivity-reason" has to be type "string" but received type "object"
2022-07-12 18:15:30.824  - info: alexa2.0 (74962) State value to set for "alexa2.0.Smart-Home-Devices.48f3f6f6-a74c-4daa-97a3-32766f03e5b1.connectivity-reason" has to be type "string" but received type "object"
2022-07-12 18:15:30.824  - info: alexa2.0 (74962) State value to set for "alexa2.0.Smart-Home-Devices.141b1d14-9591-4d28-bd03-698cd0cfd970.batteryLevel" has to be type "number" but received type "object"
2022-07-12 18:15:30.825  - info: alexa2.0 (74962) State value to set for "alexa2.0.Smart-Home-Devices.141b1d14-9591-4d28-bd03-698cd0cfd970.connectivity-reason" has to be type "string" but received type "object"
2022-07-12 18:15:30.825  - info: alexa2.0 (74962) State value to set for "alexa2.0.Smart-Home-Devices.60099b70-c2d2-46b7-b14d-77acc53e04f9.connectivity-reason" has to be type "string" but received type "object"
2022-07-12 18:15:30.827  - info: alexa2.0 (74962) State value to set for "alexa2.0.Smart-Home-Devices.a3ab3c77-6751-458f-a7d5-0871e996c700.connectivity-reason" has to be type "string" but received type "object"
2022-07-12 18:15:30.828  - info: alexa2.0 (74962) State value to set for "alexa2.0.Smart-Home-Devices.5d479e97-6965-4780-98d1-5438ccbc2371.colorRgb" has to be type "string" but received type "object"
2022-07-12 18:15:30.829  - info: alexa2.0 (74962) State value to set for "alexa2.0.Smart-Home-Devices.5d479e97-6965-4780-98d1-5438ccbc2371.connectivity-reason" has to be type "string" but received type "object"
2022-07-12 18:15:30.829  - info: alexa2.0 (74962) State value to set for "alexa2.0.Smart-Home-Devices.30d44a62-ba23-4a51-a417-d4215f8e6336.connectivity-reason" has to be type "string" but received type "object"
              M 1 Reply Last reply Reply Quote 0
              • M
                Megawaldi @Thomas Braun last edited by

                @apollon77
                Hier das selbe Problem mit dem zugespamtem Log.

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

                  @megawaldi Setz das LogLevel auf 'Warning / Hinweis'.

                  M 1 Reply Last reply Reply Quote 0
                  • M
                    Megawaldi @Thomas Braun last edited by

                    @thomas-braun
                    schon erledigt. Aber trotzdem Danke für den Tip. 😉

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

                      @megawaldi Danke für den #metoo-Beitrag. 😄

                      M 1 Reply Last reply Reply Quote 0
                      • M
                        Megawaldi @Thomas Braun last edited by

                        @thomas-braun
                        Wollte nur nicht da jemand denkt es liegt an dir Thomas...

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

                          @Diginix @sigi234 Version 3.17.3 mit Fix ist auf dem Weg

                          1 Reply Last reply Reply Quote 3
                          • sigi234
                            sigi234 Forum Testing Most Active @apollon77 last edited by

                            @apollon77 sagte in Alexa2 Adapter 3.13/3.14/3.15/3.16/3.17 (Beta):

                            @sigi234 Hab schon ne vermutung. Fix heute abend

                            Log wieder Ok, Danke für den Fix. 👍

                            apollon77 1 Reply Last reply Reply Quote 1
                            • apollon77
                              apollon77 @sigi234 last edited by

                              @sigi234 danke für die Bestätigung. Die Werte sind auch korrekt?! Vor allem bei den States die vorher angemeckert wurden?

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

                                3.17.4 ist auf dem Weg mit einem weiteren Bugfix:

                                Es war nicht möglich die Query Intervalle für Smart-Home Devices, generellen State und Configuration auf 0 zu setzen aka zu deaktivieren.

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

                                  @apollon77 Aus der iob Facebook Gruppe:

                                  5d824679-9601-4b55-a3c0-e5190c20dece-image.png

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

                                    Naja ich sags mal so ... es gab einen Bug ... Alle schnellstens auf die 3.17.4 updaten!!!

                                    Admin-Notify ist geschaltet um alle user daraf hinzuweisen. Im Forum ist auch ab gleich eine Headline

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

                                      @apollon77 Der Facebook User ist aber auf 3.14.0.

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

                                        @diginix Ok, da hats wohl mein changelog zerbröselt ... ab 3.14 ist "böse". Fixe kommunikatoon

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

                                          @apollon77

                                          habe seit heute selbiges problem, habe dann auf 3.17.4 update gemacht und seither bekomme ich keine smart home devices unter objekte mehr angezeigt

                                          1841ee1d-feb5-47f8-aad5-56ecbbe48d06-grafik.png

                                          habe schon alles durch an tipps was ich gefunden habe.

                                          Instanz komplett gelöscht
                                          iobrokeriot skill in der handy app de und wieder aktiviert
                                          mehrere neustarts

                                          1 Reply Last reply Reply Quote 0
                                          • ilovegym
                                            ilovegym Forum Testing last edited by ilovegym

                                            @myzerat Hast du in der Config des Adapters ( Achtung hat sich einiges geaendert! ) auch das Sync der Smarthome Devices aktiviert?

                                            MyzerAT 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

                                            732
                                            Online

                                            30.5k
                                            Users

                                            76.9k
                                            Topics

                                            1.2m
                                            Posts

                                            39
                                            391
                                            21634
                                            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