Navigation

    Logo
    • Register
    • Login
    • Search
    • Recent
    • Tags
    • Unread
    • Categories
    • Unreplied
    • Popular
    • GitHub
    • Docu
    • Hilfe
    1. Home
    2. Deutsch
    3. Einsteigerfragen
    4. Einbindung von Geräten
    5. ioBroker und FHEM verbinden klappt 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

    ioBroker und FHEM verbinden klappt nicht.

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

      Hallo ihr Lieben,
      ich bin ganz frisch hier und habe ioBroker ganz neu installiert.

      Ich nutze bisher noch FHEM will aber nach und nach auf Broker umsteigen.

      Leider bekomme ich die Verbindung zu FHEM nicht aufgebaut.

      FHEM läuft in einer Debian VM, dort ist auch Docker installiert und ioBroker läuft im Docker im Netzwerkmodus Host.

      Hier ist der Log von ioBroker:

      2023-07-16 01:53:51.161 - info: fhem.0 (5205) starting. Version 2.0.3 in /opt/iobroker/node_modules/iobroker.fhem, node: v18.16.1, js-controller: 4.0.24
      2023-07-16 01:54:16.028 - info: admin.0 (505) <== Disconnect system.user.admin from ::ffff:192.168.1.71 admin
      2023-07-16 01:54:21.206 - error: fhem.0 (5205) Error: read ECONNRESET (telnetIn)
      2023-07-16 01:54:21.208 - error: fhem.0 (5205) Error: read ECONNRESET (telnetOut)
      2023-07-16 01:54:51.212 - error: fhem.0 (5205) Error: read ECONNRESET (telnetIn)
      2023-07-16 01:54:51.214 - error: fhem.0 (5205) Error: read ECONNRESET (telnetOut)
      2023-07-16 01:55:21.216 - error: fhem.0 (5205) Error: read ECONNRESET (telnetIn)
      2023-07-16 01:55:21.225 - error: fhem.0 (5205) Error: read ECONNRESET (telnetOut)
      2023-07-16 01:55:51.221 - error: fhem.0 (5205) Error: read ECONNRESET (telnetIn)
      2023-07-16 01:55:51.228 - error: fhem.0 (5205) Error: read ECONNRESET (telnetOut)
      2023-07-16 01:56:21.229 - error: fhem.0 (5205) Error: read ECONNRESET (telnetIn)
      2023-07-16 01:56:21.240 - error: fhem.0 (5205) Error: read ECONNRESET (telnetOut)
      2023-07-16 01:56:51.235 - error: fhem.0 (5205) Error: read ECONNRESET (telnetIn)
      2023-07-16 01:56:51.245 - error: fhem.0 (5205) Error: read ECONNRESET (telnetOut)
      2023-07-16 01:57:21.239 - error: fhem.0 (5205) Error: read ECONNRESET (telnetIn)
      2023-07-16 01:57:21.248 - error: fhem.0 (5205) Error: read ECONNRESET (telnetOut)
      2023-07-16 01:57:51.241 - error: fhem.0 (5205) Error: read ECONNRESET (telnetIn)
      2023-07-16 01:57:51.251 - error: fhem.0 (5205) Error: read ECONNRESET (telnetOut)
      2023-07-16 01:58:21.247 - error: fhem.0 (5205) Error: read ECONNRESET (telnetIn)
      2023-07-16 01:58:21.262 - error: fhem.0 (5205) Error: read ECONNRESET (telnetOut)
      2023-07-16 01:58:51.254 - error: fhem.0 (5205) Error: read ECONNRESET (telnetIn)
      2023-07-16 01:58:51.265 - error: fhem.0 (5205) Error: read ECONNRESET (telnetOut)
      2023-07-16 01:59:21.258 - error: fhem.0 (5205) Error: read ECONNRESET (telnetIn)
      2023-07-16 01:59:21.268 - error: fhem.0 (5205) Error: read ECONNRESET (telnetOut)
      2023-07-16 01:59:51.262 - error: fhem.0 (5205) Error: read ECONNRESET (telnetIn)
      2023-07-16 01:59:51.269 - error: fhem.0 (5205) Error: read ECONNRESET (telnetOut)
      2023-07-16 02:00:15.456 - info: admin.0 (505) ==> Connected system.user.admin from ::ffff:100.107.56.50
      2023-07-16 02:00:21.265 - error: fhem.0 (5205) Error: read ECONNRESET (telnetIn)
      2023-07-16 02:00:21.273 - error: fhem.0 (5205) Error: read ECONNRESET (telnetOut)
      2023-07-16 02:00:33.482 - info: host.iobroker "system.adapter.fhem.0" disabled
      2023-07-16 02:00:33.483 - info: host.iobroker stopInstance system.adapter.fhem.0 (force=false, process=true)
      2023-07-16 02:00:33.490 - info: fhem.0 (5205) Got terminate signal TERMINATE_YOURSELF
      2023-07-16 02:00:33.493 - info: fhem.0 (5205) terminating
      2023-07-16 02:00:33.493 - info: fhem.0 (5205) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
      2023-07-16 02:00:33.508 - warn: fhem.0 (5205) State "fhem.0.info.Info.alive" has no existing object, this might lead to an error in future versions
      2023-07-16 02:00:33.531 - info: host.iobroker stopInstance system.adapter.fhem.0 send kill signal
      2023-07-16 02:00:34.064 - info: host.iobroker instance system.adapter.fhem.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
      2023-07-16 02:04:06.104 - error: host.iobroker Invalid request getRepository. "callback" or "from" is null
      2023-07-16 02:12:54.579 - info: admin.0 (505) <== Disconnect system.user.admin from ::ffff:100.107.56.50 admin
      2023-07-16 03:18:43.360 - info: wifilight.0 (3440) State value to set for "wifilight.0.192_168_1_180.reachable" has to be type "number" but received type "boolean"
      2023-07-16 03:19:09.506 - info: wifilight.0 (3440) State value to set for "wifilight.0.192_168_1_180.reachable" has to be type "number" but received type "boolean"
      2023-07-16 13:20:42.523 - info: admin.0 (505) ==> Connected system.user.admin from ::ffff:100.107.56.50
      2023-07-16 13:24:08.421 - info: host.iobroker "system.adapter.fhem.0" enabled
      2023-07-16 13:24:08.562 - info: host.iobroker instance system.adapter.fhem.0 started with pid 5664
      2023-07-16 13:24:10.848 - info: fhem.0 (5664) starting. Version 2.0.3 in /opt/iobroker/node_modules/iobroker.fhem, node: v18.16.1, js-controller: 4.0.24
      2023-07-16 13:24:37.466 - info: host.iobroker "system.adapter.fhem.0" disabled
      2023-07-16 13:24:37.468 - info: host.iobroker stopInstance system.adapter.fhem.0 (force=false, process=true)
      2023-07-16 13:24:37.473 - info: fhem.0 (5664) Got terminate signal TERMINATE_YOURSELF
      2023-07-16 13:24:37.477 - info: fhem.0 (5664) terminating
      2023-07-16 13:24:37.478 - info: fhem.0 (5664) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
      2023-07-16 13:24:37.491 - warn: fhem.0 (5664) State "fhem.0.info.Info.alive" has no existing object, this might lead to an error in future versions
      2023-07-16 13:24:37.530 - info: host.iobroker stopInstance system.adapter.fhem.0 send kill signal
      2023-07-16 13:24:38.026 - info: host.iobroker instance system.adapter.fhem.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
      2023-07-16 13:25:07.962 - info: host.iobroker "system.adapter.fhem.0" enabled
      2023-07-16 13:25:07.996 - info: host.iobroker instance system.adapter.fhem.0 started with pid 5728
      2023-07-16 13:25:09.467 - info: fhem.0 (5728) starting. Version 2.0.3 in /opt/iobroker/node_modules/iobroker.fhem, node: v18.16.1, js-controller: 4.0.24
      2023-07-16 13:25:39.519 - error: fhem.0 (5728) Error: read ECONNRESET (telnetIn)
      2023-07-16 13:25:39.522 - error: fhem.0 (5728) Error: read ECONNRESET (telnetOut)
      2023-07-16 13:26:09.524 - error: fhem.0 (5728) Error: read ECONNRESET (telnetIn)
      2023-07-16 13:26:30.441 - info: host.iobroker "system.adapter.fhem.0" disabled
      2023-07-16 13:26:30.441 - info: host.iobroker stopInstance system.adapter.fhem.0 (force=false, process=true)
      2023-07-16 13:26:30.448 - info: fhem.0 (5728) Got terminate signal TERMINATE_YOURSELF
      2023-07-16 13:26:30.452 - info: fhem.0 (5728) terminating
      2023-07-16 13:26:30.453 - info: fhem.0 (5728) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
      2023-07-16 13:26:30.461 - warn: fhem.0 (5728) State "fhem.0.info.Info.alive" has no existing object, this might lead to an error in future versions
      2023-07-16 13:26:30.490 - info: host.iobroker stopInstance system.adapter.fhem.0 send kill signal
      2023-07-16 13:26:31.008 - info: host.iobroker instance system.adapter.fhem.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
      2023-07-16 15:07:51.050 - info: admin.0 (505) ==> Connected system.user.admin from ::ffff:100.107.56.50
      2023-07-16 15:34:17.893 - info: host.iobroker "system.adapter.fhem.0" enabled
      2023-07-16 15:34:17.985 - info: host.iobroker instance system.adapter.fhem.0 started with pid 11892
      2023-07-16 15:34:20.246 - info: fhem.0 (11892) starting. Version 2.0.3 in /opt/iobroker/node_modules/iobroker.fhem, node: v18.16.1, js-controller: 4.0.24
      2023-07-16 15:34:40.381 - info: host.iobroker stopInstance system.adapter.fhem.0 (force=false, process=true)
      2023-07-16 15:34:40.386 - info: fhem.0 (11892) Got terminate signal TERMINATE_YOURSELF
      2023-07-16 15:34:40.398 - info: fhem.0 (11892) terminating
      2023-07-16 15:34:40.399 - info: fhem.0 (11892) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
      2023-07-16 15:34:40.408 - warn: fhem.0 (11892) State "fhem.0.info.Info.alive" has no existing object, this might lead to an error in future versions
      2023-07-16 15:34:40.430 - info: host.iobroker stopInstance system.adapter.fhem.0 send kill signal
      2023-07-16 15:34:40.939 - info: host.iobroker instance system.adapter.fhem.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
      2023-07-16 15:34:43.358 - info: host.iobroker instance system.adapter.fhem.0 started with pid 11919
      2023-07-16 15:34:44.688 - info: fhem.0 (11919) starting. Version 2.0.3 in /opt/iobroker/node_modules/iobroker.fhem, node: v18.16.1, js-controller: 4.0.24
      2023-07-16 15:35:10.035 - info: host.iobroker "system.adapter.fhem.0" disabled
      2023-07-16 15:35:10.035 - info: host.iobroker stopInstance system.adapter.fhem.0 (force=false, process=true)
      2023-07-16 15:35:10.039 - info: fhem.0 (11919) Got terminate signal TERMINATE_YOURSELF
      2023-07-16 15:35:10.043 - info: fhem.0 (11919) terminating
      2023-07-16 15:35:10.044 - info: fhem.0 (11919) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
      2023-07-16 15:35:10.049 - warn: fhem.0 (11919) State "fhem.0.info.Info.alive" has no existing object, this might lead to an error in future versions
      2023-07-16 15:35:10.086 - info: host.iobroker stopInstance system.adapter.fhem.0 send kill signal
      2023-07-16 15:35:10.578 - info: host.iobroker instance system.adapter.fhem.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
      2023-07-16 15:44:23.315 - info: host.iobroker "system.adapter.fhem.0" enabled
      2023-07-16 15:44:23.344 - info: host.iobroker instance system.adapter.fhem.0 started with pid 12402
      2023-07-16 15:44:24.707 - info: fhem.0 (12402) starting. Version 2.0.3 in /opt/iobroker/node_modules/iobroker.fhem, node: v18.16.1, js-controller: 4.0.24
      2023-07-16 15:53:03.363 - info: host.iobroker stopInstance system.adapter.fhem.0 (force=false, process=true)
      2023-07-16 15:53:03.369 - info: fhem.0 (12402) Got terminate signal TERMINATE_YOURSELF
      2023-07-16 15:53:03.383 - info: fhem.0 (12402) terminating
      2023-07-16 15:53:03.385 - info: fhem.0 (12402) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
      2023-07-16 15:53:03.396 - warn: fhem.0 (12402) State "fhem.0.info.Info.alive" has no existing object, this might lead to an error in future versions
      2023-07-16 15:53:03.422 - info: host.iobroker stopInstance system.adapter.fhem.0 send kill signal
      2023-07-16 15:53:03.928 - info: host.iobroker instance system.adapter.fhem.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
      2023-07-16 15:53:06.455 - info: host.iobroker instance system.adapter.fhem.0 started with pid 12826
      2023-07-16 15:53:07.928 - info: fhem.0 (12826) starting. Version 2.0.3 in /opt/iobroker/node_modules/iobroker.fhem, node: v18.16.1, js-controller: 4.0.24
      

      Bei FHEM sieht das Ganze so aus:

      defmod tPort_iobroker telnet 7073
      attr tPort_iobroker prompt fhem>
      attr tPort_iobroker room System
      

      ioBroker scheint sich auch zu verbinden, da telnet Verbindungen angezeigt werden:
      4d83cb5b-6286-4e32-be1a-3c62136c06b5-Screenshot_2023-07-16_16.04.36s.png

      f9c4dfeb-f521-4d04-b7b4-08a9b18bd713-Screenshot_2023-07-16_16.05.01s.png

      Bin für jede Hilfe oder jeden Tipp dankbar 🙂

      1 Reply Last reply Reply Quote 0
      • Marc Berg
        Marc Berg Most Active last edited by

        @rudow90
        Wenn du aus einem anderen Netz kommst (und das ist bei einer Verwendung einer VM/Container wahrscheinlich), musst du im FHEM mit dem Modul "allowed" arbeiten, soviel ich weiß. Ich hatte mir seinerzeit folgende Sequenz mitgeschrieben, die für den Zugriff aus ioBroker notwendig war:

        delete telnetPort
        save config
        define telnetPort telnet 7072 global
        define allowed_telnetPort allowed
        attr allowed_telnetPort validFor telnetPort
        set allowed_telnetPort password <password>
        

        Kannst du denn von deinem PC auf den Telnet Port zugreifen? Das sollte im Vorfeld auf jeden Fall funktionieren, bevor du es mit ioBroker versuchst.

        R 1 Reply Last reply Reply Quote 0
        • R
          Rudow90 @Marc Berg last edited by

          Sorry für die späte Antwort @marc-berg

          Also am Mac im Terminal komme ich per Telnet rauf.
          Habe im FHEM kein PW für Telnet gesetzt
          ee92672d-4e0b-4f3e-925c-5b9c10cfdb9b-Screenshot_2023-07-22_17.23.48s.png

          Das zeigt der Log an:
          757988ef-d041-413f-a21a-51d83da9934b-Screenshot_2023-07-22_17.25.35s.png

          c86773f3-ddd7-433c-9ae7-4e469a2047cc-Screenshot_2023-07-22_17.26.07s.png

          Hast du noch ne Idee ?

          Dankeee

          1 Reply Last reply Reply Quote 0
          • R
            Rudow90 last edited by

            Fehler gefunden

            a0295bad-c777-462f-b425-0e91b77e0aaa-Screenshot_2023-07-22_17.44.33s.png

            1 Reply Last reply Reply Quote 0
            • First post
              Last post

            Support us

            ioBroker
            Community Adapters
            Donate

            732
            Online

            31.9k
            Users

            80.1k
            Topics

            1.3m
            Posts

            2
            4
            164
            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