Navigation

    Logo
    • Register
    • Login
    • Search
    • Recent
    • Tags
    • Unread
    • Categories
    • Unreplied
    • Popular
    • GitHub
    • Docu
    • Hilfe
    1. Home
    2. Deutsch
    3. ioBroker Allgemein
    4. Namensauflösung Homematic -> iobroker?

    NEWS

    • Wir empfehlen: Node.js 22.x

    • Neuer Blog: Fotos und Eindrücke aus Solingen

    • ioBroker goes Matter ... Matter Adapter in Stable

    Namensauflösung Homematic -> iobroker?

    This topic has been deleted. Only users with topic management privileges can see it.
    • Homoran
      Homoran Global Moderator Administrators @Thomas Braun last edited by

      @thomas-braun sagte in Namensauflösung Homematic -> iobroker?:

      npm@7 wäre aber falsch.

      eben -das zerschiesst sogar das System

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

        @thomas-braun sagte in Namensauflösung Homematic -> iobroker?:

        Eine ungünstige Entscheidung aber dennoch...

        Das wäre ja noch die offene Frage an @Brainjourney

        1 Reply Last reply Reply Quote 0
        • B
          Brainjourney @Homoran last edited by

          @homoran said in Namensauflösung Homematic -> iobroker?:

          @brainjourney sagte in Namensauflösung Homematic -> iobroker?:

          ich nehme an du meinst hm-rpc.0

          ich meinte eigentlich alle, aber das ist ein Anfang, da das Problem ja überall auftritt, oder?

          Das ist aber nicht das debug log.
          Dazu bitte unter der Instanz die Logstufe von Info auf debaug stellen

          Ich glaube das wars.

          hm-rpc.0

          hm-rpc.0
	2021-10-13 19:32:12.857	info	new HMIP devices/channels after filter: 0
hm-rpc.0
	2021-10-13 19:32:12.821	info	xmlrpc <- newDevices 332
hm-rpc.0
	2021-10-13 19:32:12.615	info	xmlrpc -> 0 devices
hm-rpc.0
	2021-10-13 19:32:12.568	info	xmlrpc <- listDevices ["ubuntu:hm-rpc.0"]
hm-rpc.0
	2021-10-13 19:32:12.564	info	Connected
hm-rpc.0
	2021-10-13 19:32:12.548	info	xmlrpc client is trying to connect to 192.168.0.72:2010/ with ["http://192.168.0.71:2010","ubuntu:hm-rpc.0"]
hm-rpc.0
	2021-10-13 19:32:12.548	info	xmlrpc server is trying to listen on 192.168.0.71:2010
hm-rpc.0
	2021-10-13 19:32:12.436	info	starting. Version 1.14.45 in /opt/iobroker/node_modules/iobroker.hm-rpc, node: v16.11.1, js-controller: 3.3.18
hm-rpc.0
	2021-10-13 19:32:08.355	info	Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
hm-rpc.0
	2021-10-13 19:32:08.354	info	terminating
hm-rpc.0
	2021-10-13 19:32:08.354	info	Disconnected
hm-rpc.0
	2021-10-13 19:32:08.349	info	xmlrpc -> 192.168.0.72:2010/ init ["http://192.168.0.71:2010",""]
hm-rpc.0
	2021-10-13 19:32:08.349	info	Got terminate signal TERMINATE_YOURSELF
hm-rpc.0
	2021-10-13 19:31:46.619	warn	State value to set for "hm-rpc.0.000A1709AF4928.1.ACTIVE_PROFILE" has value "8" greater than max "3"
hm-rpc.0
	2021-10-13 19:28:58.878	warn	State value to set for "hm-rpc.0.000A1709AF4928.1.ACTIVE_PROFILE" has value "8" greater than max "3"
hm-rpc.0
	2021-10-13 19:27:12.986	warn	State value to set for "hm-rpc.0.000A1A499B93FF.1.ACTIVE_PROFILE" has value "8" greater than max "3"

          hm-rpc.1

          hm-rpc.1
	2021-10-13 19:20:29.977	error	Init not possible, going to stop: write EPROTO 140390935717824:error:1408F10B:SSL routines:ssl3_get_record:wrong version number:../deps/openssl/openssl/ssl/record/ssl3_record.c:332:
hm-rpc.1
	2021-10-13 19:19:28.768	error	Cannot call init: [http://192.168.0.71:2001, ""] write EPROTO 140392379709376:error:1408F10B:SSL routines:ssl3_get_record:wrong version number:../deps/openssl/openssl/ssl/record/ssl3_record.c:332:
hm-rpc.1
	2021-10-13 19:19:28.753	error	Init not possible, going to stop: write EPROTO 140392379709376:error:1408F10B:SSL routines:ssl3_get_record:wrong version number:../deps/openssl/openssl/ssl/record/ssl3_record.c:332:
hm-rpc.1
	2021-10-13 19:18:58.765	error	Init not possible, going to stop: write EPROTO 140392379709376:error:1408F10B:SSL routines:ssl3_get_record:wrong version number:../deps/openssl/openssl/ssl/record/ssl3_record.c:332:
hm-rpc.1
	2021-10-13 19:17:57.470	error	Cannot call init: [http://192.168.0.71:2001, ""] write EPROTO 140452453590976:error:1408F10B:SSL routines:ssl3_get_record:wrong version number:../deps/openssl/openssl/ssl/record/ssl3_record.c:332:
hm-rpc.1
	2021-10-13 19:17:57.455	error	Init not possible, going to stop: write EPROTO 140452453590976:error:1408F10B:SSL routines:ssl3_get_record:wrong version number:../deps/openssl/openssl/ssl/record/ssl3_record.c:332:
hm-rpc.1
	2021-10-13 19:17:27.466	error	Init not possible, going to stop: write EPROTO 140452453590976:error:1408F10B:SSL routines:ssl3_get_record:wrong version number:../deps/openssl/openssl/ssl/record/ssl3_record.c:332:
hm-rpc.1
	2021-10-13 19:16:26.247	error	Cannot call init: [http://192.168.0.71:2001, ""] write EPROTO 139973341562816:error:1408F10B:SSL routines:ssl3_get_record:wrong version number:../deps/openssl/openssl/ssl/record/ssl3_record.c:332:
hm-rpc.1
	2021-10-13 19:16:26.232	error	Init not possible, going to stop: write EPROTO 139973341562816:error:1408F10B:SSL routines:ssl3_get_record:wrong version number:../deps/openssl/openssl/ssl/record/ssl3_record.c:332:
hm-rpc.1
	2021-10-13 19:15:56.243	error	Init not possible, going to stop: write EPROTO 139973341562816:error:1408F10B:SSL routines:ssl3_get_record:wrong version number:../deps/openssl/openssl/ssl/record/ssl3_record.c:332:
hm-rpc.1
	2021-10-13 19:14:54.955	error	Cannot call init: [http://192.168.0.71:2001, ""] write EPROTO 140246586849216:error:1408F10B:SSL routines:ssl3_get_record:wrong version number:../deps/openssl/openssl/ssl/record/ssl3_record.c:332:
hm-rpc.1
	2021-10-13 19:14:54.940	error	Init not possible, going to stop: write EPROTO 140246586849216:error:1408F10B:SSL routines:ssl3_get_record:wrong version number:../deps/openssl/openssl/ssl/record/ssl3_record.c:332:
hm-rpc.1
	2021-10-13 19:14:24.951	error	Init not possible, going to stop: write EPROTO 140246586849216:error:1408F10B:SSL routines:ssl3_get_record:wrong version number:../deps/openssl/openssl/ssl/record/ssl3_record.c:332:
hm-rpc.1
	2021-10-13 19:13:23.782	error	Cannot call init: [http://192.168.0.71:2001, ""] write EPROTO 140392389863360:error:1408F10B:SSL routines:ssl3_get_record:wrong version number:../deps/openssl/openssl/ssl/record/ssl3_record.c:332:
hm-rpc.1
	2021-10-13 19:13:23.767	error	Init not possible, going to stop: write EPROTO 140392389863360:error:1408F10B:SSL routines:ssl3_get_record:wrong version number:../deps/openssl/openssl/ssl/record/ssl3_record.c:332:
hm-rpc.1
	2021-10-13 19:12:53.778	error	Init not possible, going to stop: write EPROTO 140392389863360:error:1408F10B:SSL routines:ssl3_get_record:wrong version number:../deps/openssl/openssl/ssl/record/ssl3_record.c:332:
hm-rpc.1
	2021-10-13 19:11:52.558	error	Cannot call init: [http://192.168.0.71:2001, ""] write EPROTO 140149473163200:error:1408F10B:SSL routines:ssl3_get_record:wrong version number:../deps/openssl/openssl/ssl/record/ssl3_record.c:332:
hm-rpc.1
	2021-10-13 19:11:52.544	error	Init not possible, going to stop: write EPROTO 140149473163200:error:1408F10B:SSL routines:ssl3_get_record:wrong version number:../deps/openssl/openssl/ssl/record/ssl3_record.c:332:
hm-rpc.1
	2021-10-13 19:11:22.554	error	Init not possible, going to stop: write EPROTO 140149473163200:error:1408F10B:SSL routines:ssl3_get_record:wrong version number:../deps/openssl/openssl/ssl/record/ssl3_record.c:332:
hm-rpc.1
	2021-10-13 19:10:21.340	error	Cannot call init: [http://192.168.0.71:2001, ""] write EPROTO 139896671037376:error:1408F10B:SSL routines:ssl3_get_record:wrong version number:../deps/openssl/openssl/ssl/record/ssl3_record.c:332:
hm-rpc.1
	2021-10-13 19:10:21.325	error	Init not possible, going to stop: write EPROTO 139896671037376:error:1408F10B:SSL routines:ssl3_get_record:wrong version number:../deps/openssl/openssl/ssl/record/ssl3_record.c:332:
hm-rpc.1
	2021-10-13 19:09:51.336	error	Init not possible, going to stop: write EPROTO 139896671037376:error:1408F10B:SSL routines:ssl3_get_record:wrong version number:../deps/openssl/openssl/ssl/record/ssl3_record.c:332:

          hm-rpc.2

          hm-rpc.2
	2021-10-13 19:26:34.548	info	Connected
hm-rpc.2
	2021-10-13 19:26:34.548	info	new CUxD devices/channels after filter: 0
hm-rpc.2
	2021-10-13 19:26:34.504	info	binrpc -> listDevices 108
hm-rpc.2
	2021-10-13 19:26:34.402	info	binrpc client is trying to connect to 192.168.0.72:8701/ with ["xmlrpc_bin://192.168.0.71:8701","ubuntu:hm-rpc.2"]
hm-rpc.2
	2021-10-13 19:26:34.402	info	binrpc server is trying to listen on 192.168.0.71:8701
hm-rpc.2
	2021-10-13 19:26:34.285	info	starting. Version 1.14.45 in /opt/iobroker/node_modules/iobroker.hm-rpc, node: v16.11.1, js-controller: 3.3.18
hm-rpc.2
	2021-10-13 19:26:30.227	info	Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
hm-rpc.2
	2021-10-13 19:26:30.227	info	terminating
hm-rpc.2
	2021-10-13 19:26:30.226	info	Disconnected
hm-rpc.2
	2021-10-13 19:26:30.225	info	binrpc -> 192.168.0.72:8701/ init ["xmlrpc_bin://192.168.0.71:8701",""]
hm-rpc.2
	2021-10-13 19:26:30.224	info	Got terminate signal TERMINATE_YOURSELF

          hm-rps.3

          hm-rpc.3
	2021-10-13 19:25:25.301	info	Connected
hm-rpc.3
	2021-10-13 19:25:15.323	info	xmlrpc -> 0 devices
hm-rpc.3
	2021-10-13 19:25:15.304	info	xmlrpc <- listDevices ["ubuntu:hm-rpc.3"]
hm-rpc.3
	2021-10-13 19:24:45.281	info	xmlrpc client is trying to connect to 192.168.0.72:49292/groups/ with ["http://192.168.0.71:49292","ubuntu:hm-rpc.3"]
hm-rpc.3
	2021-10-13 19:24:45.281	info	xmlrpc server is trying to listen on 192.168.0.71:49292
hm-rpc.3
	2021-10-13 19:24:45.194	info	starting. Version 1.14.45 in /opt/iobroker/node_modules/iobroker.hm-rpc, node: v16.11.1, js-controller: 3.3.18
hm-rpc.3
	2021-10-13 19:24:41.097	info	Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
hm-rpc.3
	2021-10-13 19:24:41.096	info	terminating
hm-rpc.3
	2021-10-13 19:24:41.096	info	Disconnected
hm-rpc.3
	2021-10-13 19:24:41.091	info	xmlrpc -> 192.168.0.72:49292/groups/ init ["http://192.168.0.71:49292",""]
hm-rpc.3
	2021-10-13 19:24:41.091	info	Got terminate signal TERMINATE_YOURSELF
hm-rpc.3
	2021-10-13 19:24:06.884	info	Connected
hm-rpc.3
	2021-10-13 19:23:56.891	info	xmlrpc -> 0 devices
hm-rpc.3
	2021-10-13 19:23:56.887	info	xmlrpc <- listDevices ["ubuntu:hm-rpc.3"]
hm-rpc.3
	2021-10-13 19:23:26.864	info	xmlrpc client is trying to connect to 192.168.0.72:49292/groups/ with ["http://192.168.0.71:49292","ubuntu:hm-rpc.3"]
hm-rpc.3
	2021-10-13 19:23:26.863	info	xmlrpc server is trying to listen on 192.168.0.71:49292
hm-rpc.3
	2021-10-13 19:23:26.782	info	starting. Version 1.14.45 in /opt/iobroker/node_modules/iobroker.hm-rpc, node: v16.11.1, js-controller: 3.3.18
hm-rpc.3
	2021-10-13 19:23:22.709	info	Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
hm-rpc.3
	2021-10-13 19:23:22.708	info	terminating
hm-rpc.3
	2021-10-13 19:23:22.708	info	Disconnected
hm-rpc.3
	2021-10-13 19:23:22.703	info	xmlrpc -> 192.168.0.72:49292/groups/ init ["http://192.168.0.71:49292",""]
hm-rpc.3
	2021-10-13 19:23:22.702	info	Got terminate signal TERMINATE_YOURSELF

          hm-rpc.2

          B 1 Reply Last reply Reply Quote 0
          • B
            Brainjourney @Brainjourney last edited by Brainjourney

            Der Adapter 1 Läuft nicht, ich habe dort noch einen Adapter Stromzähler von ELV den ich nicht aus der Konfiguratiom bekomme um den neu Anzulernen aber in der Kopie der Homatickonfieruragtion mit dabei stand.Ich nehme an daran liegt das wohl. Aso nicht im iobroker Auftaucht

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

              @brainjourney

              Hast du unsere Fragen / Andeutung oben nicht gelesen !?

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

                @glasfaser said in Namensauflösung Homematic -> iobroker?:

                @brainjourney

                Hast du unsere Fragen / Andeutung oben nicht gelesen !?

                npm 8.0.0
                node v16.11.1

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

                  @brainjourney

                  Gebe mal alles :

                  which nodejs && nodejs -v && which node && node -v && which npm && npm -v && apt policy nodejs
                  B 1 Reply Last reply Reply Quote 0
                  • B
                    Brainjourney @Glasfaser last edited by

                    @glasfaser said in Namensauflösung Homematic -> iobroker?:

                    which nodejs && nodejs -v && which node && node -v && which npm && npm -v && apt policy nodejs

                    /usr/bin/nodejs
                    v16.11.1
                    /usr/bin/node
                    v16.11.1
                    /usr/bin/npm
                    8.0.0
                    nodejs:
                    Installiert: 16.11.1-1nodesource1
                    Installationskandidat: 16.11.1-1nodesource1
                    Versionstabelle:
                    *** 16.11.1-1nodesource1 500
                    500 https://deb.nodesource.com/node_16.x bionic/main amd64 Packages
                    100 /var/lib/dpkg/status
                    8.10.0~dfsg-2ubuntu0.4 500
                    500 http://de.archive.ubuntu.com/ubuntu bionic-updates/universe amd64 Pa ckages
                    8.10.0~dfsg-2ubuntu0.2 500
                    500 http://security.ubuntu.com/ubuntu bionic-security/universe amd64 Pac kages
                    8.10.0~dfsg-2 500
                    500 http://de.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages

                    Thomas Braun 1 Reply Last reply Reply Quote 0
                    • Glasfaser
                      Glasfaser last edited by Glasfaser

                      @brainjourney sagte in Namensauflösung Homematic -> iobroker?:

                      ssl3_get_record:wrong version number

                      Ich kenne den Fehler nicht , kann aber eventuell mit deiner installierten Version zusammenhängen .

                      EDIT:

                      Falls jemand bereits mit Node.js 16.x arbeiten möchte, dann bitte im Moment AUSSCHLIESSLICH mit npm 6 !!

                      https://forum.iobroker.net/topic/46758/js-controller-3-3-jetzt-im-stable

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

                        @brainjourney

                        Ich würde da auch auf node12, maximal node14 gehen.

                        B 1 Reply Last reply Reply Quote 0
                        • B
                          Brainjourney @Thomas Braun last edited by Brainjourney

                          @thomas-braun said in Namensauflösung Homematic -> iobroker?:

                          @brainjourney

                          Ich würde da auch auf node12, maximal node14 gehen.

                          Sorry wenn ich das jetzt wiederholt schreibe.
                          Das alles läuft auf einem anderen Rechner pi4 mit VCCU also (iobroker und Homematic) alles bestens und ohne Fehler.

                          Thomas Braun 1 Reply Last reply Reply Quote 0
                          • Glasfaser
                            Glasfaser @Brainjourney last edited by

                            @brainjourney sagte in Namensauflösung Homematic -> iobroker?:

                            @homoran said in Namensauflösung Homematic -> iobroker?:

                            @brainjourney was steht jeweils in den Zusätzlichen Einstellungen?
                            insbesondere als Callback-Adresse?

                            Da habe ich nichts drin

                            Dann trage mal dort die IP Adresse ein .

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

                              @brainjourney sagte in Namensauflösung Homematic -> iobroker?:

                              Sorry wenn ich das jetzt wiederholt schreibe.

                              Auch wiederholt:
                              node16 und insbesondere npm>6 läuft noch nicht ganz rund zusammen mit dem ioBroker. Diese Konstellationen sollte man nur zum Testen verwenden.

                              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

                              646
                              Online

                              32.0k
                              Users

                              80.5k
                              Topics

                              1.3m
                              Posts

                              5
                              32
                              888
                              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