Navigation

    Logo
    • Register
    • Login
    • Search
    • Recent
    • Tags
    • Unread
    • Categories
    • Unreplied
    • Popular
    • GitHub
    • Docu
    • Hilfe
    1. Home
    2. Deutsch
    3. ioBroker Allgemein
    4. Anfrage Tahoma/Somfy IO Adapter

    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

    Anfrage Tahoma/Somfy IO Adapter

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

      Ich habe zwar gestern nicht umgestellt, aber gestern kam ein Update von Somfy für Tahoma selbst. Ich glaube, dass es damit zusammen hängt.

      Ich bekomme nämlich auch diese Meldungen:

      Could not state-data for channel devices.Wohnzimmer.states.core:ManufacturerSettingsState Raw-data: [object Object]
      

      Vor dem Update von Somfy für Tahoma, lief es mit der lokalen API nämlich ohne Meldungen.

      StrathCole 1 Reply Last reply Reply Quote 0
      • StrathCole
        StrathCole @wusa last edited by StrathCole

        Das hat damit zu tun, dass Somfy im neuen Update der Box (Firmware) die Events nun gefixt hat und diese funktionieren. Allerdings konnte ich sie im Update vorher nicht testen, kann also sein, dass sie etwas anders funktionieren als in der Cloud.
        Weiß nicht, ob sich @Excodibur das anschaut?

        Zur Info dazu: https://github.com/Somfy-Developer/Somfy-TaHoma-Developer-Mode/issues/4

        iMicknl created this issue in Somfy-Developer/Somfy-TaHoma-Developer-Mode

        closed Cannot register (local) event listener #4

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

          Sollte hiermit behoben werden: https://github.com/Excodibur/ioBroker.tahoma/pull/136

          StrathCole created this issue in Excodibur/ioBroker.tahoma

          closed Json variable type fixed #136

          Excodibur 1 Reply Last reply Reply Quote 2
          • Excodibur
            Excodibur Developer @StrathCole last edited by

            @strathcole Da muss ich ja gar nichts mehr machen. 😉

            https://github.com/Excodibur/ioBroker.tahoma/releases/tag/v0.7.1 (Zeitnah im BETA-Repo verfügbar).

            StrathCole 1 Reply Last reply Reply Quote 1
            • StrathCole
              StrathCole @Excodibur last edited by

              @excodibur Ja durch den Post von @wusa, dass es ein Firmware-Update von Tahoma gab, dachte ich mir dann, woran es liegen wird. Vorher waren die lokalen Events ja noch inaktiv.

              P 1 Reply Last reply Reply Quote 1
              • P
                pfahlenbauer @StrathCole last edited by

                @strathcole

                Danke für's fixen.

                Ich bekomme leider immer noch eine warn Meldung, die sieht jetzt so aus:

                2022-05-20 07:51:05.558 - warn: tahoma.0 (1772) error during request: null, request path: history/executions/6132bd05-xxxx-484c-b62d-b040942e22ef with payload:{}
                2022-05-20 07:51:05.572 - warn: tahoma.0 (1772) Response: {"statusCode":400,"body":"{\"error\":\"Unknown object.\",\"errorCode\":\"UNSPECIFIED_ERROR\"}","headers":{"content-type":"application/json","access-control-allow-origin":"*","access-control-allow-headers":"Authorization","content-length":"59","connection":"close","date":"Fri, 20 May 2022 05:51:05 GMT","server":"KizOs"},"request":{"uri":{"protocol":"https:","slashes":true,"auth":null,"host":"gateway-1XXX-0XXX-XXXX:8443","port":"8443","hostname":"gateway-1XXX-0XXX-XXXX","hash":null,"search":null,"query":null,"pathname":"/enduser-mobile-web/1/enduserAPI/history/executions/6132bd05-xxxx-484c-b62d-b040942e22ef","path":"/enduser-mobile-web/1/enduserAPI/history/executions/6132bd05-xxxx-484c-b62d-b040942e22ef","href":"https://gateway-1XXX-0XXX-XXXX:8443/enduser-mobile-web/1/enduserAPI/history/executions/6132bd05-xxxx-484c-b62d-b040942e22ef"},"method":"GET","headers":{"User-Agent":"Mozilla/5.0 (X11; Linux x86_64; rv:79.0) Gecko/20100101 Firefox/79.0","Authorization":"Bearer 627dXXXX1cd8e68d8c4e","Content-type":"application/json"}}}2022-05-20 07:51:05.573 - warn: tahoma.0 (1772) Body: "{\"error\":\"Unknown object.\",\"errorCode\":\"UNSPECIFIED_ERROR\"}"
                2022-05-20 07:51:05.573 - warn: tahoma.0 (1772) Failed getting execution state for 6132bd05-xxxx-484c-b62d-b040942e22ef
                
                
                W 1 Reply Last reply Reply Quote 0
                • W
                  wusa @pfahlenbauer last edited by

                  @StrathCole

                  Ich habe auch gerade das Update gemacht.
                  Leider habe ich auch weiterhin einen Fehler:

                  
                  tahoma.0
                  2022-05-23 11:10:32.115	warn	error during request: Error: getaddrinfo ENOTFOUND gateway-1xxx-1xxx-7xxx, request path: setup/gateways with payload:{}
                  
                  StrathCole 1 Reply Last reply Reply Quote 0
                  • StrathCole
                    StrathCole @wusa last edited by

                    @wusa In der Konfig mal versuchen, mDNS zu aktivieren.

                    W 1 Reply Last reply Reply Quote 1
                    • D
                      Dakusk last edited by Dakusk

                      Hallo Zusammen,

                      Hatte mit dem Adapter diverse andere Schwierigkeiten (keine Reaktion nachdem ein Befehl gesendet wurde), die dazu geführt haben, dass ich meinen Iobroker neu aufgesetzt habe. Nun habe ich die gleiche Fehlermeldung wie @wusa

                      Habe bisher die etc/Hosts erweitert.
                      mDNS aktiviert und deaktiviert

                      Hier ist der Log nach dem Start des Adapters... "Setup Failed" sehe ich nun auch zum ersten Mal.

                      2022-05-23 20:52:48.599 - info: tahoma.0 (570) [START] Starting adapter tahoma v0.7.1.3
                      2022-05-23 20:52:48.600 - info: tahoma.0 (570) Configured polling interval: 20000
                      2022-05-23 20:52:48.600 - info: tahoma.0 (570) Adapter will connect to Tahoma Box via local API.
                      2022-05-23 20:52:48.601 - info: tahoma.0 (570) Using stored bearer token 628bf3f2dddeae56b219
                      2022-05-23 20:52:48.657 - warn: tahoma.0 (570) error during request: Error: getaddrinfo ENOTFOUND gateway-1XXX-2XXX-9XXX.local, request path: setup with payload:{}
                      2022-05-23 20:52:48.658 - warn: tahoma.0 (570) setup failed!
                      2022-05-23 20:52:48.658 - warn: tahoma.0 (570) {"error":{"errno":-3008,"code":"ENOTFOUND","syscall":"getaddrinfo","hostname":"gateway-1XXX-2XXX-9XXX.local"}}
                      2022-05-23 20:52:58.620 - warn: tahoma.0 (570) error during request: Error: getaddrinfo ENOTFOUND gateway-1XXX-2XXX-9XXX.local, request path: setup/gateways with payload:{}
                      2022-05-23 20:53:28.640 - warn: tahoma.0 (570) error during request: Error: getaddrinfo ENOTFOUND gateway-1XXX-2XXX-9XXX.local, request path: setup/gateways with payload:{}
                      2022-05-23 20:53:58.659 - warn: tahoma.0 (570) error during request: Error: getaddrinfo ENOTFOUND gateway-1XXX-2XXX-9XXX.local, request path: setup/gateways with payload:{}
                      
                      D 1 Reply Last reply Reply Quote 0
                      • D
                        Dakusk @Dakusk last edited by

                        @dakusk

                        Okay Problem selber gelöst bekommen. Tatsächlich hat mein System die etc/hosts nach jedem reboot überschrieben.

                        Jetzt tauchen wieder die Fehler wie vor der Neuinstallation auf.

                        2022-05-23 21:57:01.002 - warn: tahoma.1 (464) error during request: null, request path: history/executions/82cdf30b-51e7-497b-9116-03438574b3a2 with payload:{}
                        2022-05-23 21:57:01.003 - warn: tahoma.1 (464) Response: {"statusCode":400,"body":"{\"error\":\"Unknown object.\",\"errorCode\":\"UNSPECIFIED_ERROR\"}","headers":{"content-type":"application/json","access-control-allow-origin":"*","access-control-allow-headers":"Authorization","content-length":"59","connection":"close","date":"Mon, 23 May 2022 21:57:00 GMT","server":"KizOs"},"request":{"uri":{"protocol":"https:","slashes":true,"auth":null,"host":"gateway-1208-2847-9785.local:8443","port":"8443","hostname":"gateway-1208-2847-9785.local","hash":null,"search":null,"query":null,"pathname":"/enduser-mobile-web/1/enduserAPI/history/executions/82cdf30b-51e7-497b-9116-03438574b3a2","path":"/enduser-mobile-web/1/enduserAPI/history/executions/82cdf30b-51e7-497b-9116-03438574b3a2","href":"https://gateway-1XXX-2XXX-9XXX.local:8443/enduser-mobile-web/1/enduserAPI/history/executions/82cdf30b-51e7-497b-9116-03438574b3a2"},"method":"GET","headers":{"User-Agent":"Mozilla/5.0 (X11; Linux x86_64; rv:79.0) Gecko/20100101 Firefox/79.0","Authorization":"Bearer 627788a7e67b661cc13a","Content-type":"application/json"}}}
                        2022-05-23 21:57:01.003 - warn: tahoma.1 (464) Body: "{\"error\":\"Unknown object.\",\"errorCode\":\"UNSPECIFIED_ERROR\"}"
                        2022-05-23 21:57:01.003 - warn: tahoma.1 (464) Failed getting execution state for 82cdf30b-51e7-497b-9116-03438574b3a2
                        2022-05-23 21:57:01.016 - warn: tahoma.1 (464) error during request: null, request path: history/executions/65fba7f7-33a6-4d47-9704-b353af2fed38 with payload:{}
                        2022-05-23 21:57:01.016 - warn: tahoma.1 (464) Response: {"statusCode":400,"body":"{\"error\":\"Unknown object.\",\"errorCode\":\"UNSPECIFIED_ERROR\"}","headers":{"content-type":"application/json","access-control-allow-origin":"*","access-control-allow-headers":"Authorization","content-length":"59","connection":"close","date":"Mon, 23 May 2022 21:57:00 GMT","server":"KizOs"},"request":{"uri":{"protocol":"https:","slashes":true,"auth":null,"host":"gateway-1XXX-2XXX-9XXX.local:8443","port":"8443","hostname":"gateway-1XXX-2XXX-9XXX.local","hash":null,"search":null,"query":null,"pathname":"/enduser-mobile-web/1/enduserAPI/history/executions/65fba7f7-33a6-4d47-9704-b353af2fed38","path":"/enduser-mobile-web/1/enduserAPI/history/executions/65fba7f7-33a6-4d47-9704-b353af2fed38","href":"https://gateway-1XXX-2XXX-9XXX.local:8443/enduser-mobile-web/1/enduserAPI/history/executions/65fba7f7-33a6-4d47-9704-b353af2fed38"},"method":"GET","headers":{"User-Agent":"Mozilla/5.0 (X11; Linux x86_64; rv:79.0) Gecko/20100101 Firefox/79.0","Authorization":"Bearer 627788a7e67b661cc13a","Content-type":"application/json"}}}
                        2022-05-23 21:57:01.016 - warn: tahoma.1 (464) Body: "{\"error\":\"Unknown object.\",\"errorCode\":\"UNSPECIFIED_ERROR\"}"
                        2022-05-23 21:57:01.016 - warn: tahoma.1 (464) Failed getting execution state for 65fba7f7-33a6-4d47-9704-b353af2fed38
                        2022-05-23 21:57:01.031 - warn: tahoma.1 (464) error during request: null, request path: history/executions/b41a285c-0a9b-4a6d-8b66-c7f0c1420fc3 with payload:{}
                        2022-05-23 21:57:01.032 - warn: tahoma.1 (464) Response: {"statusCode":400,"body":"{\"error\":\"Unknown object.\",\"errorCode\":\"UNSPECIFIED_ERROR\"}","headers":{"content-type":"application/json","access-control-allow-origin":"*","access-control-allow-headers":"Authorization","content-length":"59","connection":"close","date":"Mon, 23 May 2022 21:57:01 GMT","server":"KizOs"},"request":{"uri":{"protocol":"https:","slashes":true,"auth":null,"host":"gateway-1XXX-2XXX-9XXX.local:8443","port":"8443","hostname":"gateway-1XXX-2XXX-9XXX.local","hash":null,"search":null,"query":null,"pathname":"/enduser-mobile-web/1/enduserAPI/history/executions/b41a285c-0a9b-4a6d-8b66-c7f0c1420fc3","path":"/enduser-mobile-web/1/enduserAPI/history/executions/b41a285c-0a9b-4a6d-8b66-c7f0c1420fc3","href":"https://gateway-1XXX-2XXX-9XXX.local:8443/enduser-mobile-web/1/enduserAPI/history/executions/b41a285c-0a9b-4a6d-8b66-c7f0c1420fc3"},"method":"GET","headers":{"User-Agent":"Mozilla/5.0 (X11; Linux x86_64; rv:79.0) Gecko/20100101 Firefox/79.0","Authorization":"Bearer 627788a7e67b661cc13a","Content-type":"application/json"}}}
                        2022-05-23 21:57:01.032 - warn: tahoma.1 (464) Body: "{\"error\":\"Unknown object.\",\"errorCode\":\"UNSPECIFIED_ERROR\"}"
                        2022-05-23 21:57:01.032 - warn: tahoma.1 (464) Failed getting execution state for b41a285c-0a9b-4a6d-8b66-c7f0c1420fc3
                        2022-05-23 21:57:15.963 - warn: tahoma.1 (464) error during request: null, request path: history/executions/5787ffbb-1245-408b-b093-e962a0dd9d15 with payload:{}
                        2022-05-23 21:57:15.963 - warn: tahoma.1 (464) Response: {"statusCode":400,"body":"{\"error\":\"Unknown object.\",\"errorCode\":\"UNSPECIFIED_ERROR\"}","headers":{"content-type":"application/json","access-control-allow-origin":"*","access-control-allow-headers":"Authorization","content-length":"59","connection":"close","date":"Mon, 23 May 2022 21:57:15 GMT","server":"KizOs"},"request":{"uri":{"protocol":"https:","slashes":true,"auth":null,"host":"gateway-1XXX-2XXX-9XXX.local:8443","port":"8443","hostname":"gateway-1XXX-2XXX-9XXX.local","hash":null,"search":null,"query":null,"pathname":"/enduser-mobile-web/1/enduserAPI/history/executions/5787ffbb-1245-408b-b093-e962a0dd9d15","path":"/enduser-mobile-web/1/enduserAPI/history/executions/5787ffbb-1245-408b-b093-e962a0dd9d15","href":"https://gateway-1XXX-2XXX-9XXX.local:8443/enduser-mobile-web/1/enduserAPI/history/executions/5787ffbb-1245-408b-b093-e962a0dd9d15"},"method":"GET","headers":{"User-Agent":"Mozilla/5.0 (X11; Linux x86_64; rv:79.0) Gecko/20100101 Firefox/79.0","Authorization":"Bearer 627788a7e67b661cc13a","Content-type":"application/json"}}}
                        2022-05-23 21:57:15.963 - warn: tahoma.1 (464) Body: "{\"error\":\"Unknown object.\",\"errorCode\":\"UNSPECIFIED_ERROR\"}"
                        2022-05-23 21:57:15.963 - warn: tahoma.1 (464) Failed getting execution state for 5787ffbb-1245-408b-b093-e962a0dd9d15
                        
                        StrathCole W S 3 Replies Last reply Reply Quote 0
                        • StrathCole
                          StrathCole @Dakusk last edited by

                          @dakusk Zu welchen Zeitpunkten treten diese auf? Nach einem Befehl oder einfach so?

                          1 Reply Last reply Reply Quote 0
                          • W
                            wusa @StrathCole last edited by

                            @strathcole
                            Perfekt, Danke.
                            Das hat mein Problem gelöst.

                            1 Reply Last reply Reply Quote 0
                            • W
                              wusa @Dakusk last edited by

                              @dakusk sagte in Anfrage Tahoma/Somfy IO Adapter:

                              @dakusk

                              Okay Problem selber gelöst bekommen. Tatsächlich hat mein System die etc/hosts nach jedem reboot überschrieben.

                              Jetzt tauchen wieder die Fehler wie vor der Neuinstallation auf.

                              2022-05-23 21:57:01.002 - warn: tahoma.1 (464) error during request: null, request path: history/executions/82cdf30b-51e7-497b-9116-03438574b3a2 with payload:{}
                              2022-05-23 21:57:01.003 - warn: tahoma.1 (464) Response: {"statusCode":400,"body":"{\"error\":\"Unknown object.\",\"errorCode\":\"UNSPECIFIED_ERROR\"}","headers":{"content-type":"application/json","access-control-allow-origin":"*","access-control-allow-headers":"Authorization","content-length":"59","connection":"close","date":"Mon, 23 May 2022 21:57:00 GMT","server":"KizOs"},"request":{"uri":{"protocol":"https:","slashes":true,"auth":null,"host":"gateway-1208-2847-9785.local:8443","port":"8443","hostname":"gateway-1208-2847-9785.local","hash":null,"search":null,"query":null,"pathname":"/enduser-mobile-web/1/enduserAPI/history/executions/82cdf30b-51e7-497b-9116-03438574b3a2","path":"/enduser-mobile-web/1/enduserAPI/history/executions/82cdf30b-51e7-497b-9116-03438574b3a2","href":"https://gateway-1XXX-2XXX-9XXX.local:8443/enduser-mobile-web/1/enduserAPI/history/executions/82cdf30b-51e7-497b-9116-03438574b3a2"},"method":"GET","headers":{"User-Agent":"Mozilla/5.0 (X11; Linux x86_64; rv:79.0) Gecko/20100101 Firefox/79.0","Authorization":"Bearer 627788a7e67b661cc13a","Content-type":"application/json"}}}
                              2022-05-23 21:57:01.003 - warn: tahoma.1 (464) Body: "{\"error\":\"Unknown object.\",\"errorCode\":\"UNSPECIFIED_ERROR\"}"
                              2022-05-23 21:57:01.003 - warn: tahoma.1 (464) Failed getting execution state for 82cdf30b-51e7-497b-9116-03438574b3a2
                              2022-05-23 21:57:01.016 - warn: tahoma.1 (464) error during request: null, request path: history/executions/65fba7f7-33a6-4d47-9704-b353af2fed38 with payload:{}
                              2022-05-23 21:57:01.016 - warn: tahoma.1 (464) Response: {"statusCode":400,"body":"{\"error\":\"Unknown object.\",\"errorCode\":\"UNSPECIFIED_ERROR\"}","headers":{"content-type":"application/json","access-control-allow-origin":"*","access-control-allow-headers":"Authorization","content-length":"59","connection":"close","date":"Mon, 23 May 2022 21:57:00 GMT","server":"KizOs"},"request":{"uri":{"protocol":"https:","slashes":true,"auth":null,"host":"gateway-1XXX-2XXX-9XXX.local:8443","port":"8443","hostname":"gateway-1XXX-2XXX-9XXX.local","hash":null,"search":null,"query":null,"pathname":"/enduser-mobile-web/1/enduserAPI/history/executions/65fba7f7-33a6-4d47-9704-b353af2fed38","path":"/enduser-mobile-web/1/enduserAPI/history/executions/65fba7f7-33a6-4d47-9704-b353af2fed38","href":"https://gateway-1XXX-2XXX-9XXX.local:8443/enduser-mobile-web/1/enduserAPI/history/executions/65fba7f7-33a6-4d47-9704-b353af2fed38"},"method":"GET","headers":{"User-Agent":"Mozilla/5.0 (X11; Linux x86_64; rv:79.0) Gecko/20100101 Firefox/79.0","Authorization":"Bearer 627788a7e67b661cc13a","Content-type":"application/json"}}}
                              2022-05-23 21:57:01.016 - warn: tahoma.1 (464) Body: "{\"error\":\"Unknown object.\",\"errorCode\":\"UNSPECIFIED_ERROR\"}"
                              2022-05-23 21:57:01.016 - warn: tahoma.1 (464) Failed getting execution state for 65fba7f7-33a6-4d47-9704-b353af2fed38
                              2022-05-23 21:57:01.031 - warn: tahoma.1 (464) error during request: null, request path: history/executions/b41a285c-0a9b-4a6d-8b66-c7f0c1420fc3 with payload:{}
                              2022-05-23 21:57:01.032 - warn: tahoma.1 (464) Response: {"statusCode":400,"body":"{\"error\":\"Unknown object.\",\"errorCode\":\"UNSPECIFIED_ERROR\"}","headers":{"content-type":"application/json","access-control-allow-origin":"*","access-control-allow-headers":"Authorization","content-length":"59","connection":"close","date":"Mon, 23 May 2022 21:57:01 GMT","server":"KizOs"},"request":{"uri":{"protocol":"https:","slashes":true,"auth":null,"host":"gateway-1XXX-2XXX-9XXX.local:8443","port":"8443","hostname":"gateway-1XXX-2XXX-9XXX.local","hash":null,"search":null,"query":null,"pathname":"/enduser-mobile-web/1/enduserAPI/history/executions/b41a285c-0a9b-4a6d-8b66-c7f0c1420fc3","path":"/enduser-mobile-web/1/enduserAPI/history/executions/b41a285c-0a9b-4a6d-8b66-c7f0c1420fc3","href":"https://gateway-1XXX-2XXX-9XXX.local:8443/enduser-mobile-web/1/enduserAPI/history/executions/b41a285c-0a9b-4a6d-8b66-c7f0c1420fc3"},"method":"GET","headers":{"User-Agent":"Mozilla/5.0 (X11; Linux x86_64; rv:79.0) Gecko/20100101 Firefox/79.0","Authorization":"Bearer 627788a7e67b661cc13a","Content-type":"application/json"}}}
                              2022-05-23 21:57:01.032 - warn: tahoma.1 (464) Body: "{\"error\":\"Unknown object.\",\"errorCode\":\"UNSPECIFIED_ERROR\"}"
                              2022-05-23 21:57:01.032 - warn: tahoma.1 (464) Failed getting execution state for b41a285c-0a9b-4a6d-8b66-c7f0c1420fc3
                              2022-05-23 21:57:15.963 - warn: tahoma.1 (464) error during request: null, request path: history/executions/5787ffbb-1245-408b-b093-e962a0dd9d15 with payload:{}
                              2022-05-23 21:57:15.963 - warn: tahoma.1 (464) Response: {"statusCode":400,"body":"{\"error\":\"Unknown object.\",\"errorCode\":\"UNSPECIFIED_ERROR\"}","headers":{"content-type":"application/json","access-control-allow-origin":"*","access-control-allow-headers":"Authorization","content-length":"59","connection":"close","date":"Mon, 23 May 2022 21:57:15 GMT","server":"KizOs"},"request":{"uri":{"protocol":"https:","slashes":true,"auth":null,"host":"gateway-1XXX-2XXX-9XXX.local:8443","port":"8443","hostname":"gateway-1XXX-2XXX-9XXX.local","hash":null,"search":null,"query":null,"pathname":"/enduser-mobile-web/1/enduserAPI/history/executions/5787ffbb-1245-408b-b093-e962a0dd9d15","path":"/enduser-mobile-web/1/enduserAPI/history/executions/5787ffbb-1245-408b-b093-e962a0dd9d15","href":"https://gateway-1XXX-2XXX-9XXX.local:8443/enduser-mobile-web/1/enduserAPI/history/executions/5787ffbb-1245-408b-b093-e962a0dd9d15"},"method":"GET","headers":{"User-Agent":"Mozilla/5.0 (X11; Linux x86_64; rv:79.0) Gecko/20100101 Firefox/79.0","Authorization":"Bearer 627788a7e67b661cc13a","Content-type":"application/json"}}}
                              2022-05-23 21:57:15.963 - warn: tahoma.1 (464) Body: "{\"error\":\"Unknown object.\",\"errorCode\":\"UNSPECIFIED_ERROR\"}"
                              2022-05-23 21:57:15.963 - warn: tahoma.1 (464) Failed getting execution state for 5787ffbb-1245-408b-b093-e962a0dd9d15
                              

                              @StrathCole

                              Genau die selben Fehler treten jetzt bei mir doch auch auf.
                              Bei mir passiert das, wenn ein Rollladen gefahren wird.

                              Also wenn keine Bewegung ist, dann kein Logeintrag.
                              Fahre ich aber einen Rollladen kommen 4 Logeinträge.

                              tahoma.0
                              2022-05-24 12:51:09.918 Failed getting execution state for 8da08f3b-e144-xxxx-xxxx-d5b8858f9b5a
                              
                              tahoma.0
                              2022-05-24 12:51:09.917	warn	 Body: "{\"error\":\"Unknown object.\",\"errorCode\":\"UNSPECIFIED_ERROR\"}"
                              
                              tahoma.0
                              2022-05-24 12:51:09.916	warn	 Response: {"statusCode":400,"body":"{\"error\":\"Unknown object.\",\"errorCode\":\"UNSPECIFIED_ERROR\"}","headers":{"content-type":"application/json","access-control-allow-origin":"*","access-control-allow-headers":"Authorization","content-length":"59","connection":"close","date":"Tue, 24 May 2022 10:51:09 GMT","server":"KizOs"},"request":{"uri":{"protocol":"https:","slashes":true,"auth":null,"host":"gateway-1xxx-1xxx-7xxx.local:8443","port":"8443","hostname":"gateway-1xxx-1xxx-7xxx.local","hash":null,"search":null,"query":null,"pathname":"/enduser-mobile-web/1/enduserAPI/history/executions/8da08f3b-e144-xxxx-xxxx-d5b8858f9b5a","path":"/enduser-mobile-web/1/enduserAPI/history/executions/8da08f3b-e144-xxxx-xxxx-d5b8858f9b5a","href":"https://gateway-1xxx-1xxx-7xxx.local:8443/enduser-mobile-web/1/enduserAPI/history/executions/8da08f3b-e144-xxxx-xxxx-d5b8858f9b5a"},"method":"GET","headers":{"User-Agent":"Mozilla/5.0 (X11; Linux x86_64; rv:79.0) Gecko/20100101 Firefox/79.0","Authorization":"Bearer 62627697f0xxxx5b66360","Content-type":"application/json"}}}
                              
                              tahoma.0
                              2022-05-24 12:51:09.915	warn	 error during request: null, request path: history/executions/8da08f3b-e144-xxxx-xxxx-d5b8858f9b5a with payload:{}
                              
                              1 Reply Last reply Reply Quote 0
                              • M
                                mike2712 last edited by

                                Hallo,

                                ständig ist die Box gesperrt von Somfy, die Hotline von Somfy erklärte das die Abfrage Zeiten von ioBroker das Problem sind, die habe ich jetzt auf 1 Stunde erhöht, weiterhin das selbe Problem, aktiviere ich den Adpater, ist die Box nach kurze Zeit gesperrt.
                                Ich habe hier gelesen das einige ähnliche Probleme damit haben, leider aber keine Lösung gefunden, mich wundert das es ja doch bei einigen offensichtlich funktioniert.
                                Der Abrufintervall wird offensichtlich in ms eingegeben, gibt es hier Grenzen?

                                3932ed04-269a-4550-b36b-e5121fee7ffa-image.png

                                Jemand eine Idee was bei mir falsch läuft, ich möchte ja nicht täglich bei Somfy anrufen, allerdings würde ich aber auch gerne die ioBroker Anbindung haben wollen.

                                W 1 Reply Last reply Reply Quote 0
                                • W
                                  wusa @mike2712 last edited by

                                  @mike2712
                                  Welche Box hast du?
                                  Du könntest auf die lokale API umstellen, dann sollte das ganze Spiel ein Ende haben.
                                  Ich selbst habe wegen dem auch schon 3x bei Somfy angerufen.

                                  Hatte zum Schluss das Intervall auf 12 Stunden stehen.
                                  Seit der Umstellung auf die lokale API habe ich Ruhe.

                                  M 1 Reply Last reply Reply Quote 0
                                  • T
                                    Tom37 last edited by Tom37

                                    Hallo,

                                    ich habe die Beta-Version 0.7.1 im Einsatz und verwende den Adapter, um ein Tor mit einer Somfy-Steuerung über eine Tahoma-Box zu steuern. Das funktioniert seit der Verwendung des Local API ohne Probleme, vorher hatte ich immer wieder die bekannten Verbindungsprobleme. Ich wollte aber lediglich mal melden, dass ich im Log immer wieder Warnings bekomme. Die Funktion scheint hierdurch aber nicht beeinträchtigt zu sein. Vielen Dank an den/die Entwickler für die hervorragende Arbeit!

                                    2022-05-26 19:17:28.268 - warn: tahoma.0 (4314) error during request: null, request path: history/executions/xxx with payload:{}
                                    2022-05-26 19:17:28.271 - warn: tahoma.0 (4314) Response: {"statusCode":400,"body":"{\"error\":\"Unknown object.\",\"errorCode\":\"UNSPECIFIED_ERROR\"}","headers":{"content-type":"application/json","access-control-allow-origin":"*","access-control-allow-headers":"Authorization","content-length":"59","connection":"close","date":"Thu, 26 May 2022 17:17:28 GMT","server":"KizOs"},"request":{"uri":{"protocol":"https:","slashes":true,"auth":null,"host":"gateway-xxx","port":"xxx","hostname":"gateway-xxx","hash":null,"search":null,"query":null,"pathname":"/enduser-mobile-web/1/enduserAPI/history/executions/xxx","path":"/enduser-mobile-web/1/enduserAPI/history/executions/xxx","href":"https://gateway-xxx/enduser-mobile-web/1/enduserAPI/history/executions/xxx"},"method":"GET","headers":{"User-Agent":"Mozilla/5.0 (X11; Linux x86_64; rv:79.0) Gecko/20100101 Firefox/79.0","Authorization":"Bearer xxx","Content-type":"application/json"}}}
                                    2022-05-26 19:17:28.272 - warn: tahoma.0 (4314) Body: "{\"error\":\"Unknown object.\",\"errorCode\":\"UNSPECIFIED_ERROR\"}"
                                    2022-05-26 19:17:28.273 - warn: tahoma.0 (4314) Failed getting execution state for xxx
                                    

                                    (Ein paar Daten habe ich durch "xxx" ersetzt, da ich mir nicht sicher war, ob ich das teilen sollte ...)

                                    Viele Grüße,
                                    Tom

                                    1 Reply Last reply Reply Quote 0
                                    • M
                                      mike2712 @wusa last edited by

                                      @wusa
                                      ich habe die Tahoma Switch.
                                      Wie sind den die Einstellungen für den Abrufintervall ? Ich hatte schon versucht damit zu testen, vermutlich ging es nicht da die Box gesperrt war.
                                      Weiterhin habe ich das Problem das sie nicht in exakt dem selben Netz liegen, da gab es offensichtlich auch Probleme.

                                      Die Fritz Box liegt im 172.16.10.xx , Die Tahoma Switch liegt bei 172.16.20.xx.

                                      Wie kann ich Testen ob das Lokal API wirklich funktioniert?

                                      1 Reply Last reply Reply Quote 0
                                      • W
                                        wusa @wusa last edited by

                                        @wusa sagte in Anfrage Tahoma/Somfy IO Adapter:

                                        Ist der iobroker und Tahoma im selben Netz?
                                        Habe bei mir festgestellt, über 2 Subnetze hinweg geht es leider nicht.

                                        @mike2712
                                        Ich zitiere mich mal schnell selbst.
                                        Über 2 Subnetze hinweg geht es leider nicht.

                                        Ich musste meine Tahoma Box auch in das selbe Netz wie den ioBroker bringen. Dann lief es mit mDNS ohne Probleme.

                                        Excodibur 1 Reply Last reply Reply Quote 0
                                        • Excodibur
                                          Excodibur Developer @wusa last edited by

                                          @wusa @mike2712

                                          Oder ihr deaktiviert "Use MDNS" in den Adapter Einstellungen, dann müsste es auch über mehrere Netze gehen, solange der Name aufgelöst werden kann. Im Härtefall können man die Names-Auflösung in der hosts-Datei auch manuell eintragen.

                                          1 Reply Last reply Reply Quote 0
                                          • G
                                            gammler2003 @StrathCole last edited by

                                            @strathcole Hi,
                                            dachte gestern ich probiere mal wieder, ob auf dem lokalen Wege mittlerweile auch die Szenarien unterstützt werden - habe gelernt, dass dies noch nicht implementiert ist.

                                            Dann wollte ich wieder von lokal weg und die "klassische" Funktion nutzen und habe die Pin entfernt. Seitdem bekomme ich den folgenden Fehler.

                                            tahoma.0
                                            2022-06-14 07:20:03.627	warn	error during request: ->401 retry actionGroups
                                            
                                            tahoma.0
                                            2022-06-14 07:20:03.621	warn	error during request: ->401 retry setup
                                            
                                            tahoma.0
                                            2022-06-14 07:20:03.248	info	Using stored bearer token xxx
                                            
                                            tahoma.0
                                            2022-06-14 07:20:03.241	info	Configured polling interval: 20000
                                            
                                            tahoma.0
                                            2022-06-14 07:20:03.239	info	[START] Starting adapter tahoma v0.7.1.3
                                            
                                            tahoma.0
                                            2022-06-14 07:20:03.197	info	starting. Version 0.7.1 in /opt/iobroker/node_modules/iobroker.tahoma, node: v16.15.0, js-controller: 4.0.23
                                            

                                            Ist dieses Verhalten bekannt? Kann ich dem Adapter irgendwie sagen, dass er sich ab sofort wieder mit UserID und Passwort einloggen soll? Oder den Adapter einmal löschen und neu installieren?

                                            Vielen Dank & viele Grüße

                                            StrathCole 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

                                            429
                                            Online

                                            31.9k
                                            Users

                                            80.1k
                                            Topics

                                            1.3m
                                            Posts

                                            102
                                            605
                                            155968
                                            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