Navigation

    Logo
    • Register
    • Login
    • Search
    • Recent
    • Tags
    • Unread
    • Categories
    • Unreplied
    • Popular
    • GitHub
    • Docu
    • Hilfe
    1. Home
    2. Deutsch
    3. Einsteigerfragen
    4. [gelöst] Zweiter Homematic-Adapter startet nicht

    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

    [gelöst] Zweiter Homematic-Adapter startet nicht

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

      Hallo zusammen,

      nach einigen Jahren Betrieb muss ich meine Installation erweitern. Es kommt eine zweite CCU3 dazu die momentan noch im selben Netz hängt. Der erste Adapter mit der Adresse xx.yy.zz.45 läuft fehlerfrei. der zweite Adapter mit der Adresse xx.yy.zz.46 startet nicht.

      69d4d274-4205-4024-89a1-32f89f064897-image.png

      Hier die Einstellung des zweiten Adapters:

      280ee05e-808b-4653-9e2d-835c9a880452-image.png

      c890c0bf-cbdc-486c-87eb-3c6d3b014452-image.png

      Was mache ich falsch?

      Codierknecht Samson71 2 Replies Last reply Reply Quote 0
      • Codierknecht
        Codierknecht Developer Most Active @automatix last edited by

        @automatix
        Callback-Adresse eingetragen?

        A 1 Reply Last reply Reply Quote 0
        • A
          automatix @Codierknecht last edited by

          @codierknecht: eine callback-Adresse habe ich nicht eingetragen. Welche wäre das? die IP-Adresse des Raspi wo der IOBROKER drauf läuft oder die der zweiten CCU?

          Codierknecht A 2 Replies Last reply Reply Quote 0
          • Codierknecht
            Codierknecht Developer Most Active @automatix last edited by

            @automatix
            Also bei mir steht da die IP des NUC drin, auf dem ioBroker läuft.
            10b4f4b9-8080-4273-9971-6cacc743e7b6-grafik.png

            1 Reply Last reply Reply Quote 0
            • A
              automatix @automatix last edited by

              @automatix said in Probleme bei der Einbindung eines zweiten Homematic Adapters:

              @codierknecht: eine callback-Adresse habe ich nicht eingetragen. Welche wäre das? die IP-Adresse des Raspi wo der IOBROKER drauf läuft oder die der zweiten CCU?

              Ich habe schon alle möglichen Adressen ausprobiert:
              8d12da27-a466-4b08-bef5-a40711cdde26-image.png

              9f1d3cae-dfb1-4b6b-abeb-0316dd936ae3-image.png

              1f72bfb1-cedb-4960-acb3-65c1e11adec0-image.png

              kein Erfolg

              1 Reply Last reply Reply Quote 0
              • Samson71
                Samson71 Global Moderator @automatix last edited by

                @automatix
                Warum überhaupt eine 2. CCU wenn es das gleiche Netz (gleicher Standort) ist?

                A 1 Reply Last reply Reply Quote 0
                • A
                  automatix @Samson71 last edited by

                  @samson71: zum testen, später wird die zweite CCU über VPN mit dem iobroker verknüpft

                  Samson71 1 Reply Last reply Reply Quote 0
                  • Samson71
                    Samson71 Global Moderator @automatix last edited by

                    @automatix
                    Danke für die Info. Trag mal die Callback Adresse wie von @Codierknecht beschrieben ein.

                    A 1 Reply Last reply Reply Quote 0
                    • A
                      automatix @Samson71 last edited by

                      @samson71 gemacht, keine Änderung

                      c353d777-5de6-4af9-8b08-7c5e76acfd34-image.png

                      02697799-aece-4656-9501-dbc1d0a1d12b-image.png

                      Homoran 1 Reply Last reply Reply Quote 0
                      • Homoran
                        Homoran Global Moderator Administrators @automatix last edited by

                        @automatix und was steht im log beim Neustart der Instanz?

                        A 1 Reply Last reply Reply Quote 0
                        • A
                          automatix last edited by

                          @homoran : steh gerade auf der leitung. Wo finde ich die?

                          A 2 Replies Last reply Reply Quote 0
                          • A
                            automatix @automatix last edited by

                            @automatix habe es gefunden, schau gerade mal nach und poste dann

                            1 Reply Last reply Reply Quote 0
                            • A
                              automatix @automatix last edited by Homoran

                              @automatix

                              Hier das Ende der Logdatei:

                              2023-12-08 20:15:28.439  - info: hm-rega.1 (4979) update favorites to enum.favorites
2023-12-08 20:15:33.653  - info: hm-rpc.1 (5009) starting. Version 1.15.19 in /opt/iobroker/node_modules/iobroker.hm-rpc, node: v18.19.0, js-controller: 5.0.16
2023-12-08 20:15:33.726  - info: hm-rega.0 (4964) ReGaHSS 192.168.178.46 up
2023-12-08 20:15:33.830  - error: hm-rega.0 (4964) post request error: connect ECONNREFUSED 192.168.178.46:8181
2023-12-08 20:15:33.832  - error: hm-rega.0 (4964) CCU 192.168.178.46 unreachable
2023-12-08 20:15:34.133  - info: hm-rpc.1 (5009) xmlrpc server is trying to listen on 192.168.178.108:8082
2023-12-08 20:15:34.135  - info: hm-rpc.1 (5009) xmlrpc client is trying to connect to 192.168.178.45:2001/ with ["http://192.168.178.108:8082","iobroker:hm-rpc.1:37a21bcd3bfcba027b7ff1f3ff99593f"]
2023-12-08 20:15:34.222  - info: hm-rpc.1 (5009) xmlrpc <- system.listMethods ["iobroker:hm-rpc.1:37a21bcd3bfcba027b7ff1f3ff99593f"]
2023-12-08 20:15:34.252  - info: hm-rpc.1 (5009) xmlrpc <- listDevices ["iobroker:hm-rpc.1:37a21bcd3bfcba027b7ff1f3ff99593f"]
2023-12-08 20:15:34.406  - info: hm-rpc.1 (5009) xmlrpc -> 189 devices
2023-12-08 20:15:34.507  - info: hm-rpc.1 (5009) Connected
2023-12-08 20:15:55.064  - error: hm-rpc.0 (4994) Init not possible, going to stop: connect ECONNREFUSED 192.168.178.46:2001
2023-12-08 20:15:55.082  - info: hm-rpc.0 (4994) xmlrpc -> 192.168.178.46:2001/ init ["http://192.168.178.108:2001",""]
2023-12-08 20:15:55.096  - error: hm-rpc.0 (4994) Cannot call init: [http://192.168.178.108:2001, ""] connect ECONNREFUSED 192.168.178.46:2001
2023-12-08 20:15:55.111  - info: hm-rpc.0 (4994) terminating
2023-12-08 20:15:55.115  - info: hm-rpc.0 (4994) Terminated (NO_ERROR): Without reason
2023-12-08 20:16:03.882  - info: hm-rega.0 (4964) ReGaHSS 192.168.178.46 up
2023-12-08 20:16:03.925  - error: hm-rega.0 (4964) post request error: connect ECONNREFUSED 192.168.178.46:8181
2023-12-08 20:16:03.926  - error: hm-rega.0 (4964) CCU 192.168.178.46 unreachable
2023-12-08 20:16:26.052  - info: hm-rega.0 (4964) Got terminate signal TERMINATE_YOURSELF
2023-12-08 20:16:26.177  - info: hm-rega.0 (4964) terminating
2023-12-08 20:16:26.181  - info: hm-rega.0 (4964) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
2023-12-08 20:16:26.556  - info: hm-rega.0 (4964) terminating
2023-12-08 20:16:29.858  - info: hm-rpc.0 (5024) starting. Version 1.15.19 in /opt/iobroker/node_modules/iobroker.hm-rpc, node: v18.19.0, js-controller: 5.0.16
2023-12-08 20:16:30.264  - info: hm-rpc.0 (5024) xmlrpc server is trying to listen on 0.0.0.0:2001
2023-12-08 20:16:30.267  - info: hm-rpc.0 (5024) xmlrpc client is trying to connect to 192.168.178.46:2001/ with ["http://192.168.178.108:2001","iobroker:hm-rpc.0:672a253d77e59472513d027b6e1395e7"]
2023-12-08 20:16:30.339  - error: hm-rpc.0 (5024) Init not possible, going to stop: connect ECONNREFUSED 192.168.178.46:2001
2023-12-08 20:16:33.363  - info: hm-rega.0 (5035) starting. Version 4.0.0 in /opt/iobroker/node_modules/iobroker.hm-rega, node: v18.19.0, js-controller: 5.0.16
2023-12-08 20:16:33.585  - info: hm-rega.0 (5035) subscribe hm-rpc.0.BidCoS-RF.50.PRESS_SHORT
2023-12-08 20:16:33.715  - info: hm-rega.0 (5035) ReGaHSS 192.168.178.46 up
2023-12-08 20:16:33.820  - error: hm-rega.0 (5035) post request error: connect ECONNREFUSED 192.168.178.46:8181
2023-12-08 20:16:33.822  - error: hm-rega.0 (5035) CCU 192.168.178.46 unreachable
2023-12-08 20:16:36.276  - info: hm-rpc.0 (5024) Got terminate signal TERMINATE_YOURSELF
2023-12-08 20:16:36.285  - info: hm-rpc.0 (5024) xmlrpc -> 192.168.178.46:2001/ init ["http://192.168.178.108:2001",""]
2023-12-08 20:16:36.303  - error: hm-rpc.0 (5024) Cannot call init: [http://192.168.178.108:2001, ""] connect ECONNREFUSED 192.168.178.46:2001
2023-12-08 20:16:36.306  - info: hm-rpc.0 (5024) terminating
2023-12-08 20:16:36.313  - info: hm-rpc.0 (5024) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
2023-12-08 20:16:43.781  - info: hm-rpc.0 (5054) starting. Version 1.15.19 in /opt/iobroker/node_modules/iobroker.hm-rpc, node: v18.19.0, js-controller: 5.0.16
2023-12-08 20:16:44.123  - info: hm-rpc.0 (5054) xmlrpc server is trying to listen on 0.0.0.0:2001
2023-12-08 20:16:44.124  - info: hm-rpc.0 (5054) xmlrpc client is trying to connect to 192.168.178.46:2001/ with ["http://192.168.178.108:2001","iobroker:hm-rpc.0:b12b2759017f42979ace9bd39aca4d0d"]
2023-12-08 20:16:44.173  - error: hm-rpc.0 (5054) Init not possible, going to stop: connect ECONNREFUSED 192.168.178.46:2001

                              MOD-EDIT: Code in code-tags gesetzt!

                              Homoran 1 Reply Last reply Reply Quote 0
                              • A
                                automatix @Homoran last edited by automatix

                                @homoran : Hier das Ende der Logdatei

                                2023-12-08 20:15:28.439  - info: hm-rega.1 (4979) update favorites to enum.favorites
2023-12-08 20:15:33.653  - info: hm-rpc.1 (5009) starting. Version 1.15.19 in /opt/iobroker/node_modules/iobroker.hm-rpc, node: v18.19.0, js-controller: 5.0.16
2023-12-08 20:15:33.726  - info: hm-rega.0 (4964) ReGaHSS 192.168.178.46 up
2023-12-08 20:15:33.830  - error: hm-rega.0 (4964) post request error: connect ECONNREFUSED 192.168.178.46:8181
2023-12-08 20:15:33.832  - error: hm-rega.0 (4964) CCU 192.168.178.46 unreachable
2023-12-08 20:15:34.133  - info: hm-rpc.1 (5009) xmlrpc server is trying to listen on 192.168.178.108:8082
2023-12-08 20:15:34.135  - info: hm-rpc.1 (5009) xmlrpc client is trying to connect to 192.168.178.45:2001/ with ["http://192.168.178.108:8082","iobroker:hm-rpc.1:37a21bcd3bfcba027b7ff1f3ff99593f"]
2023-12-08 20:15:34.222  - info: hm-rpc.1 (5009) xmlrpc <- system.listMethods ["iobroker:hm-rpc.1:37a21bcd3bfcba027b7ff1f3ff99593f"]
2023-12-08 20:15:34.252  - info: hm-rpc.1 (5009) xmlrpc <- listDevices ["iobroker:hm-rpc.1:37a21bcd3bfcba027b7ff1f3ff99593f"]
2023-12-08 20:15:34.406  - info: hm-rpc.1 (5009) xmlrpc -> 189 devices
2023-12-08 20:15:34.507  - info: hm-rpc.1 (5009) Connected
2023-12-08 20:15:55.064  - error: hm-rpc.0 (4994) Init not possible, going to stop: connect ECONNREFUSED 192.168.178.46:2001
2023-12-08 20:15:55.082  - info: hm-rpc.0 (4994) xmlrpc -> 192.168.178.46:2001/ init ["http://192.168.178.108:2001",""]
2023-12-08 20:15:55.096  - error: hm-rpc.0 (4994) Cannot call init: [http://192.168.178.108:2001, ""] connect ECONNREFUSED 192.168.178.46:2001
2023-12-08 20:15:55.111  - info: hm-rpc.0 (4994) terminating
2023-12-08 20:15:55.115  - info: hm-rpc.0 (4994) Terminated (NO_ERROR): Without reason
2023-12-08 20:16:03.882  - info: hm-rega.0 (4964) ReGaHSS 192.168.178.46 up
2023-12-08 20:16:03.925  - error: hm-rega.0 (4964) post request error: connect ECONNREFUSED 192.168.178.46:8181
2023-12-08 20:16:03.926  - error: hm-rega.0 (4964) CCU 192.168.178.46 unreachable
2023-12-08 20:16:26.052  - info: hm-rega.0 (4964) Got terminate signal TERMINATE_YOURSELF
2023-12-08 20:16:26.177  - info: hm-rega.0 (4964) terminating
2023-12-08 20:16:26.181  - info: hm-rega.0 (4964) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
2023-12-08 20:16:26.556  - info: hm-rega.0 (4964) terminating
2023-12-08 20:16:29.858  - info: hm-rpc.0 (5024) starting. Version 1.15.19 in /opt/iobroker/node_modules/iobroker.hm-rpc, node: v18.19.0, js-controller: 5.0.16
2023-12-08 20:16:30.264  - info: hm-rpc.0 (5024) xmlrpc server is trying to listen on 0.0.0.0:2001
2023-12-08 20:16:30.267  - info: hm-rpc.0 (5024) xmlrpc client is trying to connect to 192.168.178.46:2001/ with ["http://192.168.178.108:2001","iobroker:hm-rpc.0:672a253d77e59472513d027b6e1395e7"]
2023-12-08 20:16:30.339  - error: hm-rpc.0 (5024) Init not possible, going to stop: connect ECONNREFUSED 192.168.178.46:2001
2023-12-08 20:16:33.363  - info: hm-rega.0 (5035) starting. Version 4.0.0 in /opt/iobroker/node_modules/iobroker.hm-rega, node: v18.19.0, js-controller: 5.0.16
2023-12-08 20:16:33.585  - info: hm-rega.0 (5035) subscribe hm-rpc.0.BidCoS-RF.50.PRESS_SHORT
2023-12-08 20:16:33.715  - info: hm-rega.0 (5035) ReGaHSS 192.168.178.46 up
2023-12-08 20:16:33.820  - error: hm-rega.0 (5035) post request error: connect ECONNREFUSED 192.168.178.46:8181
2023-12-08 20:16:33.822  - error: hm-rega.0 (5035) CCU 192.168.178.46 unreachable
2023-12-08 20:16:36.276  - info: hm-rpc.0 (5024) Got terminate signal TERMINATE_YOURSELF
2023-12-08 20:16:36.285  - info: hm-rpc.0 (5024) xmlrpc -> 192.168.178.46:2001/ init ["http://192.168.178.108:2001",""]
2023-12-08 20:16:36.303  - error: hm-rpc.0 (5024) Cannot call init: [http://192.168.178.108:2001, ""] connect ECONNREFUSED 192.168.178.46:2001
2023-12-08 20:16:36.306  - info: hm-rpc.0 (5024) terminating
2023-12-08 20:16:36.313  - info: hm-rpc.0 (5024) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
2023-12-08 20:16:43.781  - info: hm-rpc.0 (5054) starting. Version 1.15.19 in /opt/iobroker/node_modules/iobroker.hm-rpc, node: v18.19.0, js-controller: 5.0.16
2023-12-08 20:16:44.123  - info: hm-rpc.0 (5054) xmlrpc server is trying to listen on 0.0.0.0:2001
2023-12-08 20:16:44.124  - info: hm-rpc.0 (5054) xmlrpc client is trying to connect to 192.168.178.46:2001/ with ["http://192.168.178.108:2001","iobroker:hm-rpc.0:b12b2759017f42979ace9bd39aca4d0d"]
2023-12-08 20:16:44.173  - error: hm-rpc.0 (5054) Init not possible, going to stop: connect ECONNREFUSED 192.168.178.46:2001
                                1 Reply Last reply Reply Quote 0
                                • Homoran
                                  Homoran Global Moderator Administrators @automatix last edited by

                                  @automatix sagte in Probleme bei der Einbindung eines zweiten Homematic Adapters:

                                  ECONNREFUSED 192.168.178.46:8181

                                  da musst du dir wohl mal due Firewall näher Ansehen

                                  A 1 Reply Last reply Reply Quote 0
                                  • A
                                    automatix @Homoran last edited by Homoran

                                    @homoran : habe jetzt in der Raspberrymatic die Ports 2001 und 8182 freigegeben. Läuft aber immer noch nicht. Hier der Log:

                                    2023-12-08 20:40:10.110  - info: hm-rpc.0 (5503) starting. Version 1.15.19 in /opt/iobroker/node_modules/iobroker.hm-rpc, node: v18.19.0, js-controller: 5.0.16
2023-12-08 20:40:10.506  - info: hm-rpc.0 (5503) xmlrpc server is trying to listen on 0.0.0.0:2001
2023-12-08 20:40:10.508  - info: hm-rpc.0 (5503) xmlrpc client is trying to connect to 192.168.178.46:2001/ with ["http://192.168.178.108:2001","iobroker:hm-rpc.0:aad9c8421ebcb8242ae91fe4458f8df1"]
2023-12-08 20:40:10.580  - error: hm-rpc.0 (5503) Init not possible, going to stop: Unknown XML-RPC tag 'TITLE'
2023-12-08 20:40:22.099  - info: hm-rpc.0 (5503) Got terminate signal TERMINATE_YOURSELF
2023-12-08 20:40:22.108  - info: hm-rpc.0 (5503) xmlrpc -> 192.168.178.46:2001/ init ["http://192.168.178.108:2001",""]
2023-12-08 20:40:22.135  - error: hm-rpc.0 (5503) Cannot call init: [http://192.168.178.108:2001, ""] Unknown XML-RPC tag 'TITLE'
2023-12-08 20:40:22.137  - info: hm-rpc.0 (5503) terminating
2023-12-08 20:40:22.140  - info: hm-rpc.0 (5503) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
2023-12-08 20:40:29.608  - info: hm-rpc.0 (5518) starting. Version 1.15.19 in /opt/iobroker/node_modules/iobroker.hm-rpc, node: v18.19.0, js-controller: 5.0.16
2023-12-08 20:40:29.947  - info: hm-rpc.0 (5518) xmlrpc server is trying to listen on 0.0.0.0:2001
2023-12-08 20:40:29.949  - info: hm-rpc.0 (5518) xmlrpc client is trying to connect to 192.168.178.46:2001/ with ["http://192.168.178.108:2001","iobroker:hm-rpc.0:837cd7bdb32389d29a5b6cf12e3f4e5c"]
2023-12-08 20:40:30.021  - error: hm-rpc.0 (5518) Init not possible, going to stop: Unknown XML-RPC tag 'TITLE'
2023-12-08 20:40:41.010  - info: hm-rega.0 (5534) starting. Version 4.0.0 in /opt/iobroker/node_modules/iobroker.hm-rega, node: v18.19.0, js-controller: 5.0.16
2023-12-08 20:40:41.231  - info: hm-rega.0 (5534) subscribe hm-rpc.0.BidCoS-RF.50.PRESS_SHORT
2023-12-08 20:40:41.359  - info: hm-rega.0 (5534) ReGaHSS 192.168.178.46 up
2023-12-08 20:40:41.485  - error: hm-rega.0 (5534) <-- invalid response: "<?xml version=\"1.0\" encoding=\"iso-8859-1\"?>\n<!DOCTYPE html PUBLIC \"-//W3C//DTD XHTML 1.0 Transitional//EN\"\n         \"http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd\">\n<html xmlns=\"http://www.w3.org/1999/xhtml\" xml:lang=\"en\" lang=\"en\">\n <head>\n  <title>401 Unauthorized</title>\n </head>\n <body>\n  <h1>401 Unauthorized</h1>\n </body>\n</html>\n"
2023-12-08 20:40:41.487  - error: hm-rega.0 (5534) ReGaHSS 192.168.178.46 down

                                    MOD-EDIT: Code in code-tags gesetzt!

                                    Homoran 1 Reply Last reply Reply Quote 0
                                    • Homoran
                                      Homoran Global Moderator Administrators @automatix last edited by

                                      @automatix sagte in Probleme bei der Einbindung eines zweiten Homematic Adapters:

                                      going to stop: Unknown XML-RPC tag 'TITLE'

                                      Immer noch die Firewall!

                                      @automatix sagte in Probleme bei der Einbindung eines zweiten Homematic Adapters:

                                      habe jetzt in der Raspberrymatic die Ports 2001 und 8182 freigegeben.

                                      warum die?

                                      A 1 Reply Last reply Reply Quote 0
                                      • A
                                        automatix @Homoran last edited by Homoran

                                        @homoran : Sorry, 2001 und 8181.

                                        Jetzt folgender log:

                                        2023-12-08 20:53:03.402  - info: hm-rpc.0 (5767) starting. Version 1.15.19 in /opt/iobroker/node_modules/iobroker.hm-rpc, node: v18.19.0, js-controller: 5.0.16
2023-12-08 20:53:03.740  - info: hm-rpc.0 (5767) xmlrpc server is trying to listen on 0.0.0.0:2001
2023-12-08 20:53:03.742  - info: hm-rpc.0 (5767) xmlrpc client is trying to connect to 192.168.178.46:2001/ with ["http://192.168.178.108:2001","iobroker:hm-rpc.0:8e301537134b939773d413fcfcd396ac"]
2023-12-08 20:53:03.826  - error: hm-rpc.0 (5767) Init not possible, going to stop: Unknown XML-RPC tag 'TITLE'
2023-12-08 20:53:08.532  - info: hm-rega.0 (5782) starting. Version 4.0.0 in /opt/iobroker/node_modules/iobroker.hm-rega, node: v18.19.0, js-controller: 5.0.16
2023-12-08 20:53:08.753  - info: hm-rega.0 (5782) subscribe hm-rpc.0.BidCoS-RF.50.PRESS_SHORT
2023-12-08 20:53:08.884  - info: hm-rega.0 (5782) ReGaHSS 192.168.178.46 up
2023-12-08 20:53:09.000  - error: hm-rega.0 (5782) <-- invalid response: "<?xml version=\"1.0\" encoding=\"iso-8859-1\"?>\n<!DOCTYPE html PUBLIC \"-//W3C//DTD XHTML 1.0 Transitional//EN\"\n         \"http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd\">\n<html xmlns=\"http://www.w3.org/1999/xhtml\" xml:lang=\"en\" lang=\"en\">\n <head>\n  <title>401 Unauthorized</title>\n </head>\n <body>\n  <h1>401 Unauthorized</h1>\n </body>\n</html>\n"
2023-12-08 20:53:09.001  - error: hm-rega.0 (5782) ReGaHSS 192.168.178.46 down

                                        MOD-EDIT: Code in code-tags gesetzt!

                                        Homoran 1 Reply Last reply Reply Quote 0
                                        • Homoran
                                          Homoran Global Moderator Administrators @automatix last edited by

                                          @automatix sagte in Probleme bei der Einbindung eines zweiten Homematic Adapters:

                                          , 2001 und 8181.

                                          https://www.iobroker.net/#de/adapters/adapterref/iobroker.hm-rpc/README.md?homematicport

                                          A 1 Reply Last reply Reply Quote 0
                                          • A
                                            automatix @Homoran last edited by

                                            @homoran Danke für den Link, ich schaue mir morgen mal die Firewall der Raspberrymatic noch mal genauer an.

                                            Homoran Samson71 2 Replies Last reply Reply Quote 0
                                            • First post
                                              Last post

                                            Support us

                                            ioBroker
                                            Community Adapters
                                            Donate

                                            666
                                            Online

                                            31.9k
                                            Users

                                            80.3k
                                            Topics

                                            1.3m
                                            Posts

                                            4
                                            27
                                            629
                                            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