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

    • ioBroker 10-Jahres Community Treffen - ein kleiner ReCap

    • Tester für Responsive Initiative gesucht

    • 50€: Mach mit bei einer Smarthome Studie mit ioBroker!

    Anfrage Tahoma/Somfy IO Adapter

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

      @mike2712
      Hast du den Developer Mode, wenn du dich einloggst? Auf Github ist nur von TaHoma die Rede.
      Da könnte die Switch eigentlich darunter fallen.

      1 Reply Last reply Reply Quote 0
      • L
        Lucky 0 last edited by

        Moin,
        ich habe den Developer-Modus aktiviert,
        Adapter wie besprochen installiert,
        habe Usernamen, Passwort und PIN eingegeben.
        Die Instanz startete auch erfolgsversprechend:

        Got token for local api: 6274.......

        aber dann:

        
tahoma.0
2022-05-06 10:30:21.950	warn	error during request: Error: getaddrinfo ENOTFOUND gateway-1XXX-7XXX-6XXX.local, request path: setup/gateways with payload:{}

tahoma.0
2022-05-06 10:30:11.981	warn	{"error":{"errno":-3008,"code":"ENOTFOUND","syscall":"getaddrinfo","hostname":"gateway-1XXX-7XXX-6XXX.local"}}

tahoma.0
2022-05-06 10:30:11.981	warn	setup failed!

tahoma.0
2022-05-06 10:30:11.981	warn	error during request: Error: getaddrinfo ENOTFOUND gateway-1XXX-7XXX-6XXX.local, request path: setup with payload:{}

        Die URL https://gateway-1XXX-7XXX-6XXX.local:8443/enduser-mobile-web/1/enduserAPI/
        ist im Browser erreichbar.

        User, Passwort, PIN und aktivierten Entwicklermodus habe ich mehrfach überprüft.
        Firmware der Tahoma Box Premium ist aktuell

        Kann mir jemand weiterhelfen?
        Danke

        StrathCole W 2 Replies Last reply Reply Quote 0
        • StrathCole
          StrathCole @Lucky 0 last edited by

          @lucky-0 Hi. Scheinbar kann dann deine ioBroker Box (raspi?) nicht auf die URL zugreifen. Kannst Du über die Konsole der Box zum Beispiel mit "curl" prüfen.

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

            @lucky-0

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

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

              Danke für die schnellen Antworten.
              Ja, Raspi und ja, gleiches Netz.

              Getestet:
              URL mit curl aufrufen,
              ohne '.local'
              SSL ignoriert

              root@iobroker:~# curl https://gateway-1XXX-7XXX-6XXX.local:8443/enduser-mobile-web/1/enduserAPI/
curl: (6) Could not resolve host: gateway-1XXX-XXX-6XXX.local
root@iobroker:~# 
root@iobroker:~# 
root@iobroker:~# curl https://gateway-1XXX-7XXX-6XXX:8443/enduser-mobile-web/1/enduserAPI/
curl: (60) SSL certificate problem: unable to get local issuer certificate
More details here: https://curl.se/docs/sslcerts.html

curl failed to verify the legitimacy of the server and therefore could not
establish a secure connection to it. To learn more about this situation and
how to fix it, please visit the web page mentioned above.
root@iobroker:~# 
root@iobroker:~# 
root@iobroker:~# 
root@iobroker:~# curl -k  https://gateway-1XXX-7XXX-6XXX:8443/enduser-mobile-web/1/enduserAPI/
{"error":"Missing authorization token.","errorCode":"RESOURCE_ACCESS_DENIED"}root@iobroker:~# 
root@iobroker:~#
              StrathCole 2 Replies Last reply Reply Quote 0
              • StrathCole
                StrathCole @Lucky 0 last edited by StrathCole

                @lucky-0 Kann sein, dass die Namensauflösung ein Problem hat auf dem Host.
                In dem Fall könntest du den Hostname mit der korrekten IP noch in /etc/hosts eintragen.

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

                  @lucky-0 Also ich meine, wenn du in /etc/hosts einen neuen Eintrag machst mit:

                  1.2.3.4 gateway-1XXX-7XXX-6XXX.local wobei 1.2.3.4 die IP im Netzwerk ist, die die Tahoma Box hat.

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

                    @strathcole Das war's. Mit dem Hosteintrag hat es geklappt. 👍
                    Vielen Dank!!

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

                      @StrathCole

                      Finde ich super, wenn das nun lokal läuft.

                      Ich habe gestern umgestellt und bekomme folgende warn Meldungen im Log.

                      
tahoma.0
2022-05-13 08:22:12.860	warn	Could not state-data for channel devices.Dachfenster_Winterg_.states.core:ManufacturerSettingsState Raw-data: [object Object]

tahoma.0
2022-05-13 08:21:47.876	warn	Could not state-data for channel devices.Dachfenster_Winterg_.states.core:ManufacturerSettingsState Raw-data: [object Object]

tahoma.0
2022-05-13 08:21:37.862	warn	Could not state-data for channel devices.Eltern_rechts.states.core:ManufacturerSettingsState Raw-data: [object Object]

tahoma.0
2022-05-13 08:21:37.862	warn	Could not state-data for channel devices.Eltern_links.states.core:ManufacturerSettingsState Raw-data: [object Object]

tahoma.0
2022-05-13 08:21:37.861	warn	Could not state-data for channel devices.Laura_rechts.states.core:ManufacturerSettingsState Raw-data: [object Object]

tahoma.0
2022-05-13 08:21:37.860	warn	Could not state-data for channel devices.Anna_Mitte.states.core:ManufacturerSettingsState Raw-data: [object Object]

tahoma.0
2022-05-13 08:21:37.859	warn	Could not state-data for channel devices.Anna_rechts.states.core:ManufacturerSettingsState Raw-data: [object Object]

tahoma.0
2022-05-13 08:21:37.858	warn	Could not state-data for channel devices.Laura_links.states.core:ManufacturerSettingsState Raw-data: [object Object]

tahoma.0
2022-05-13 08:21:37.857	warn	Could not state-data for channel devices.Laura_Mitte.states.core:ManufacturerSettingsState Raw-data: [object Object]

tahoma.0
2022-05-13 08:21:32.886	warn	Could not state-data for channel devices.Anna_links.states.core:ManufacturerSettingsState Raw-data: [object Object]

tahoma.0
2022-05-13 08:21:27.868	warn	Could not state-data for channel devices.Dachfenster_Winterg_.states.core:ManufacturerSettingsState Raw-data: [object Object]

tahoma.0
2022-05-13 08:21:17.845	warn	Could not state-data for channel devices.Bad_Eltern.states.core:ManufacturerSettingsState Raw-data: [object Object]

tahoma.0
2022-05-13 08:21:17.844	warn	Could not state-data for channel devices.Bad_Kinder_rechts.states.core:ManufacturerSettingsState Raw-data: [object Object]

tahoma.0
2022-05-13 08:21:17.843	warn	Could not state-data for channel devices.Bad_Kinder_links.states.core:ManufacturerSettingsState Raw-data: [object Object]
                      1 Reply Last reply Reply Quote 0
                      • 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
                                            • First post
                                              Last post

                                            Support us

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

                                            686
                                            Online

                                            30.5k
                                            Users

                                            76.7k
                                            Topics

                                            1.2m
                                            Posts

                                            96
                                            570
                                            72272
                                            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