Navigation

    Logo
    • Register
    • Login
    • Search
    • Recent
    • Tags
    • Unread
    • Categories
    • Unreplied
    • Popular
    • GitHub
    • Docu
    • Hilfe
    1. Home
    2. Deutsch
    3. ioBroker Allgemein
    4. Iobroker findet Tasmota 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 findet Tasmota nicht...

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

      @gerdnutzinger sagte in Iobroker findet Tasmota nicht...:

      @crunchip
      ich bin am Anfang und war heilfroh das ich IOBroker auf meinen Laptop gebracht habe 🥵
      Und jetzt bekomme ich die Basic nicht rein.
      ich werde später das System auf einen raspberry setzen.... Wenn alles so geht wie ich mir das vorgestelle

      hättest mal mit Raspi angefangen.
      die Installation geht da viel einfacher.

      kannst du mal iobroker list instances machen und das Ergebnis posten?

      G 2 Replies Last reply Reply Quote 0
      • Homoran
        Homoran Global Moderator Administrators @GerdNutzinger last edited by

        @gerdnutzinger sagte in Iobroker findet Tasmota nicht...:

        Sonoff habe ich neu gestartet und auch die Instanz (mehrmals)
        Negativ

        was steht jetzt im log?

        G 1 Reply Last reply Reply Quote 0
        • G
          GerdNutzinger @Homoran last edited by

          @homoran said in Iobroker findet Tasmota nicht...:

          instances

          meinst du: Geräte und Dienste finden?

          adb9b4b3-b67c-4fd2-9cd1-a3da32600686-grafik.png

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

            @gerdnutzinger sagte in Iobroker findet Tasmota nicht...:

            @homoran said in Iobroker findet Tasmota nicht...:

            instances

            meinst du: Geräte und Dienste finden?

            adb9b4b3-b67c-4fd2-9cd1-a3da32600686-grafik.png

            nein!

            in der Konsole den genannten Befehl eingeben

            1 Reply Last reply Reply Quote 0
            • G
              GerdNutzinger @Homoran last edited by Homoran

              @homoran

              2022-04-03 21:40:12.674 - error: sonoff.1 (15088) Can not start Server Error: listen EADDRINUSE: address already in use 0.0.0.0:1883
              2022-04-03 21:43:07.928 - info: host.Gerdprivat(Zuhause) stopInstance system.adapter.sonoff.1 (force=false, process=true)
              2022-04-03 21:43:07.929 - info: host.Gerdprivat(Zuhause) stopInstance system.adapter.sonoff.1 send kill signal
              2022-04-03 21:43:07.929 - info: sonoff.1 (15088) Got terminate signal TERMINATE_YOURSELF
              2022-04-03 21:43:07.934 - info: sonoff.1 (15088) terminating
              2022-04-03 21:43:07.935 - info: sonoff.1 (15088) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
              2022-04-03 21:43:08.474 - info: host.Gerdprivat(Zuhause) instance system.adapter.sonoff.1 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
              2022-04-03 21:43:10.317 - info: host.Gerdprivat(Zuhause) stopInstance system.adapter.sonoff.0 (force=false, process=true)
              2022-04-03 21:43:10.320 - info: host.Gerdprivat(Zuhause) stopInstance system.adapter.sonoff.0 send kill signal
              2022-04-03 21:43:10.319 - info: sonoff.0 (22364) Got terminate signal TERMINATE_YOURSELF
              2022-04-03 21:43:10.321 - info: sonoff.0 (22364) terminating
              2022-04-03 21:43:10.321 - info: sonoff.0 (22364) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
              2022-04-03 21:43:10.858 - info: host.Gerdprivat(Zuhause) instance system.adapter.sonoff.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
              2022-04-03 21:43:11.133 - info: host.Gerdprivat(Zuhause) instance system.adapter.sonoff.1 started with pid 4800
              2022-04-03 21:43:12.024 - info: sonoff.1 (4800) starting. Version 2.4.7 in C:/iobroker/Zuhause/node_modules/iobroker.sonoff, node: v14.19.0, js-controller: 4.0.18
              2022-04-03 21:43:12.055 - info: sonoff.1 (4800) Starting MQTT authenticated server on port 1883
              2022-04-03 21:43:13.528 - info: host.Gerdprivat(Zuhause) instance system.adapter.sonoff.0 started with pid 12396
              2022-04-03 21:43:14.436 - info: sonoff.0 (12396) starting. Version 2.4.7 in C:/iobroker/Zuhause/node_modules/iobroker.sonoff, node: v14.19.0, js-controller: 4.0.18
              2022-04-03 21:43:14.457 - error: sonoff.0 (12396) Can not start Server Error: listen EADDRINUSE: address already in use 0.0.0.0:1883
              2022-04-03 21:43:17.211 - info: host.Gerdprivat(Zuhause) stopInstance system.adapter.sonoff.0 (force=false, process=true)
              2022-04-03 21:43:17.212 - info: host.Gerdprivat(Zuhause) stopInstance system.adapter.sonoff.0 send kill signal
              2022-04-03 21:43:17.208 - info: sonoff.0 (12396) Got terminate signal TERMINATE_YOURSELF
              2022-04-03 21:43:17.212 - info: sonoff.0 (12396) terminating
              2022-04-03 21:43:17.213 - info: sonoff.0 (12396) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
              2022-04-03 21:43:17.739 - info: host.Gerdprivat(Zuhause) instance system.adapter.sonoff.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
              2022-04-03 21:43:20.419 - info: host.Gerdprivat(Zuhause) instance system.adapter.sonoff.0 started with pid 6728
              2022-04-03 21:43:21.242 - info: sonoff.0 (6728) starting. Version 2.4.7 in C:/iobroker/Zuhause/node_modules/iobroker.sonoff, node: v14.19.0, js-controller: 4.0.18
              2022-04-03 21:43:21.261 - error: sonoff.0 (6728) Can not start Server Error: listen EADDRINUSE: address already in use 0.0.0.0:1883
              2022-04-03 21:43:21.809 - info: host.Gerdprivat(Zuhause) stopInstance system.adapter.sonoff.1 (force=false, process=true)
              2022-04-03 21:43:21.811 - info: host.Gerdprivat(Zuhause) stopInstance system.adapter.sonoff.1 send kill signal
              2022-04-03 21:43:21.810 - info: sonoff.1 (4800) Got terminate signal TERMINATE_YOURSELF
              2022-04-03 21:43:21.811 - info: sonoff.1 (4800) terminating
              2022-04-03 21:43:21.812 - info: sonoff.1 (4800) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
              2022-04-03 21:43:22.338 - info: host.Gerdprivat(Zuhause) instance system.adapter.sonoff.1 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
              2022-04-03 21:43:25.015 - info: host.Gerdprivat(Zuhause) instance system.adapter.sonoff.1 started with pid 9660
              2022-04-03 21:43:25.936 - info: sonoff.1 (9660) starting. Version 2.4.7 in C:/iobroker/Zuhause/node_modules/iobroker.sonoff, node: v14.19.0, js-controller: 4.0.18
              2022-04-03 21:43:25.966 - info: sonoff.1 (9660) Starting MQTT authenticated server on port 1883
              2022-04-03 21:45:50.582 - info: host.Gerdprivat(Zuhause) stopInstance system.adapter.sonoff.0 (force=false, process=true)
              2022-04-03 21:45:50.595 - info: sonoff.0 (6728) Got terminate signal TERMINATE_YOURSELF
              2022-04-03 21:45:50.599 - info: host.Gerdprivat(Zuhause) stopInstance system.adapter.sonoff.0 send kill signal
              2022-04-03 21:45:50.601 - info: sonoff.0 (6728) terminating
              2022-04-03 21:45:50.602 - info: sonoff.0 (6728) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
              2022-04-03 21:45:51.136 - info: host.Gerdprivat(Zuhause) instance system.adapter.sonoff.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
              2022-04-03 21:45:53.860 - info: host.Gerdprivat(Zuhause) instance system.adapter.sonoff.0 started with pid 25176
              2022-04-03 21:45:54.342 - info: host.Gerdprivat(Zuhause) stopInstance system.adapter.sonoff.1 (force=false, process=true)
              2022-04-03 21:45:54.347 - info: host.Gerdprivat(Zuhause) stopInstance system.adapter.sonoff.1 send kill signal
              2022-04-03 21:45:54.346 - info: sonoff.1 (9660) Got terminate signal TERMINATE_YOURSELF
              2022-04-03 21:45:54.349 - info: sonoff.1 (9660) terminating
              2022-04-03 21:45:54.351 - info: sonoff.1 (9660) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
              2022-04-03 21:45:54.883 - info: host.Gerdprivat(Zuhause) instance system.adapter.sonoff.1 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
              2022-04-03 21:45:54.889 - info: sonoff.0 (25176) starting. Version 2.4.7 in C:/iobroker/Zuhause/node_modules/iobroker.sonoff, node: v14.19.0, js-controller: 4.0.18
              2022-04-03 21:45:54.917 - info: sonoff.0 (25176) Starting MQTT authenticated server on port 1883
              2022-04-03 21:45:57.572 - info: host.Gerdprivat(Zuhause) instance system.adapter.sonoff.1 started with pid 24384
              2022-04-03 21:45:58.428 - info: sonoff.1 (24384) starting. Version 2.4.7 in C:/iobroker/Zuhause/node_modules/iobroker.sonoff, node: v14.19.0, js-controller: 4.0.18
              2022-04-03 21:45:58.454 - error: sonoff.1 (24384) Can not start Server Error: listen EADDRINUSE: address already in use 0.0.0.0:1883
              2022-04-03 21:46:14.666 - info: discovery.0 (15140) Discovering devices with a HF-LPB100 chipset...
              2022-04-03 21:46:14.670 - info: discovery.0 (15140) Discovering mDNS devices...
              2022-04-03 21:46:14.678 - info: discovery.0 (15140) Discovering ping devices...
              2022-04-03 21:46:14.720 - info: discovery.0 (15140) Discovering UPnP devices...
              2022-04-03 21:46:14.730 - info: discovery.0 (15140) Discovering wifi-mi-light devices...
              2022-04-03 21:46:14.744 - info: discovery.0 (15140) Done discovering serial devices. 5 packages received
              2022-04-03 21:46:14.781 - info: discovery.0 (15140) Done discovering tr064 devices. 27 packages received
              2022-04-03 21:46:15.430 - warn: discovery.0 (15140) halt
              2022-04-03 21:46:15.430 - info: discovery.0 (15140) Done discovering ping devices. 2 packages received
              2022-04-03 21:46:16.741 - info: discovery.0 (15140) Done discovering wifi-mi-light devices. 0 packages received
              2022-04-03 21:46:19.714 - info: discovery.0 (15140) Done discovering udp devices. 1 packages received
              2022-04-03 21:46:24.682 - info: discovery.0 (15140) Done discovering HF-LPB100 devices. 0 packages received
              2022-04-03 21:46:29.684 - info: discovery.0 (15140) Done discovering mdns devices. 0 packages received
              2022-04-03 21:46:29.725 - info: discovery.0 (15140) Done discovering upnp devices. 107 packages received
              2022-04-03 21:46:29.774 - info: discovery.0 (15140) Found 40 addresses
              2022-04-03 21:46:29.892 - error: discovery.0 (15140) eky error Error: addMembership EHOSTUNREACH
              2022-04-03 21:46:29.893 - error: discovery.0 (15140) emby error Error: addMembership EHOSTUNREACH
              2022-04-03 21:46:29.897 - warn: discovery.0 (15140) Onkyo AVR discovery error Error: addMembership EHOSTUNREACH
              2022-04-03 21:46:29.898 - warn: discovery.0 (15140) Pioneer AVR discovery error Error: addMembership EHOSTUNREACH
              2022-04-03 21:46:31.929 - error: discovery.0 (15140) eky error Error: addMembership EHOSTUNREACH
              2022-04-03 21:46:31.930 - error: discovery.0 (15140) emby error Error: addMembership EHOSTUNREACH
              2022-04-03 21:46:31.933 - warn: discovery.0 (15140) Onkyo AVR discovery error Error: addMembership EHOSTUNREACH
              2022-04-03 21:46:31.934 - warn: discovery.0 (15140) Pioneer AVR discovery error Error: addMembership EHOSTUNREACH
              2022-04-03 21:46:33.965 - error: discovery.0 (15140) eky error Error: addMembership EHOSTUNREACH
              2022-04-03 21:46:33.966 - error: discovery.0 (15140) emby error Error: addMembership EHOSTUNREACH
              2022-04-03 21:46:33.969 - warn: discovery.0 (15140) Onkyo AVR discovery error Error: addMembership EHOSTUNREACH
              2022-04-03 21:46:33.970 - warn: discovery.0 (15140) Pioneer AVR discovery error Error: addMembership EHOSTUNREACH
              2022-04-03 21:46:36.493 - error: discovery.0 (15140) eky error Error: addMembership EHOSTUNREACH
              2022-04-03 21:46:36.494 - error: discovery.0 (15140) emby error Error: addMembership EHOSTUNREACH
              2022-04-03 21:46:36.497 - warn: discovery.0 (15140) Onkyo AVR discovery error Error: addMembership EHOSTUNREACH
              2022-04-03 21:46:36.498 - warn: discovery.0 (15140) Pioneer AVR discovery error Error: addMembership EHOSTUNREACH
              2022-04-03 21:46:39.006 - error: discovery.0 (15140) eky error Error: addMembership EHOSTUNREACH
              2022-04-03 21:46:39.006 - error: discovery.0 (15140) emby error Error: addMembership EHOSTUNREACH
              2022-04-03 21:46:39.009 - warn: discovery.0 (15140) Onkyo AVR discovery error Error: addMembership EHOSTUNREACH
              2022-04-03 21:46:39.010 - warn: discovery.0 (15140) Pioneer AVR discovery error Error: addMembership EHOSTUNREACH
              2022-04-03 21:46:41.542 - error: discovery.0 (15140) eky error Error: addMembership EHOSTUNREACH
              2022-04-03 21:46:41.542 - error: discovery.0 (15140) emby error Error: addMembership EHOSTUNREACH
              2022-04-03 21:46:41.545 - warn: discovery.0 (15140) Onkyo AVR discovery error Error: addMembership EHOSTUNREACH
              2022-04-03 21:46:41.545 - warn: discovery.0 (15140) Pioneer AVR discovery error Error: addMembership EHOSTUNREACH
              2022-04-03 21:46:44.082 - error: discovery.0 (15140) eky error Error: addMembership EHOSTUNREACH
              2022-04-03 21:46:44.083 - error: discovery.0 (15140) emby error Error: addMembership EHOSTUNREACH
              2022-04-03 21:46:44.085 - warn: discovery.0 (15140) Onkyo AVR discovery error Error: addMembership EHOSTUNREACH
              2022-04-03 21:46:44.086 - warn: discovery.0 (15140) Pioneer AVR discovery error Error: addMembership EHOSTUNREACH
              2022-04-03 21:46:46.635 - error: discovery.0 (15140) eky error Error: addMembership EHOSTUNREACH
              2022-04-03 21:46:46.637 - error: discovery.0 (15140) emby error Error: addMembership EHOSTUNREACH
              2022-04-03 21:46:46.643 - warn: discovery.0 (15140) Onkyo AVR discovery error Error: addMembership EHOSTUNREACH
              2022-04-03 21:46:46.648 - warn: discovery.0 (15140) Pioneer AVR discovery error Error: addMembership EHOSTUNREACH
              2022-04-03 21:46:49.176 - error: discovery.0 (15140) eky error Error: addMembership EHOSTUNREACH
              2022-04-03 21:46:49.179 - error: discovery.0 (15140) emby error Error: addMembership EHOSTUNREACH
              2022-04-03 21:46:49.182 - warn: discovery.0 (15140) Onkyo AVR discovery error Error: addMembership EHOSTUNREACH
              2022-04-03 21:46:49.182 - warn: discovery.0 (15140) Pioneer AVR discovery error Error: addMembership EHOSTUNREACH
              2022-04-03 21:46:51.738 - error: discovery.0 (15140) eky error Error: addMembership EHOSTUNREACH
              2022-04-03 21:46:51.739 - error: discovery.0 (15140) emby error Error: addMembership EHOSTUNREACH
              2022-04-03 21:46:51.745 - warn: discovery.0 (15140) Onkyo AVR discovery error Error: addMembership EHOSTUNREACH
              2022-04-03 21:46:51.747 - warn: discovery.0 (15140) Pioneer AVR discovery error Error: addMembership EHOSTUNREACH
              2022-04-03 21:46:54.280 - error: discovery.0 (15140) eky error Error: addMembership EHOSTUNREACH
              2022-04-03 21:46:54.281 - error: discovery.0 (15140) emby error Error: addMembership EHOSTUNREACH
              2022-04-03 21:46:54.283 - warn: discovery.0 (15140) Onkyo AVR discovery error Error: addMembership EHOSTUNREACH
              2022-04-03 21:46:54.284 - warn: discovery.0 (15140) Pioneer AVR discovery error Error: addMembership EHOSTUNREACH
              2022-04-03 21:46:56.818 - error: discovery.0 (15140) eky error Error: addMembership EHOSTUNREACH
              2022-04-03 21:46:56.819 - error: discovery.0 (15140) emby error Error: addMembership EHOSTUNREACH
              2022-04-03 21:46:56.821 - warn: discovery.0 (15140) Onkyo AVR discovery error Error: addMembership EHOSTUNREACH
              2022-04-03 21:46:56.822 - warn: discovery.0 (15140) Pioneer AVR discovery error Error: addMembership EHOSTUNREACH
              2022-04-03 21:46:59.347 - error: discovery.0 (15140) eky error Error: addMembership EHOSTUNREACH
              2022-04-03 21:46:59.348 - error: discovery.0 (15140) emby error Error: addMembership EHOSTUNREACH
              2022-04-03 21:46:59.355 - warn: discovery.0 (15140) Onkyo AVR discovery error Error: addMembership EHOSTUNREACH
              2022-04-03 21:46:59.356 - warn: discovery.0 (15140) Pioneer AVR discovery error Error: addMembership EHOSTUNREACH
              2022-04-03 21:47:01.876 - error: discovery.0 (15140) eky error Error: addMembership EHOSTUNREACH
              2022-04-03 21:47:01.878 - error: discovery.0 (15140) emby error Error: addMembership EHOSTUNREACH
              2022-04-03 21:47:01.880 - warn: discovery.0 (15140) Onkyo AVR discovery error Error: addMembership EHOSTUNREACH
              2022-04-03 21:47:01.881 - warn: discovery.0 (15140) Pioneer AVR discovery error Error: addMembership EHOSTUNREACH
              2022-04-03 21:47:04.429 - error: discovery.0 (15140) eky error Error: addMembership EHOSTUNREACH
              2022-04-03 21:47:04.430 - error: discovery.0 (15140) emby error Error: addMembership EHOSTUNREACH
              2022-04-03 21:47:04.433 - warn: discovery.0 (15140) Onkyo AVR discovery error Error: addMembership EHOSTUNREACH
              2022-04-03 21:47:04.435 - warn: discovery.0 (15140) Pioneer AVR discovery error Error: addMembership EHOSTUNREACH
              2022-04-03 21:47:06.959 - error: discovery.0 (15140) eky error Error: addMembership EHOSTUNREACH
              2022-04-03 21:47:06.960 - error: discovery.0 (15140) emby error Error: addMembership EHOSTUNREACH
              2022-04-03 21:47:06.965 - warn: discovery.0 (15140) Onkyo AVR discovery error Error: addMembership EHOSTUNREACH
              2022-04-03 21:47:06.966 - warn: discovery.0 (15140) Pioneer AVR discovery error Error: addMembership EHOSTUNREACH
              2022-04-03 21:47:09.510 - error: discovery.0 (15140) eky error Error: addMembership EHOSTUNREACH
              2022-04-03 21:47:09.512 - error: discovery.0 (15140) emby error Error: addMembership EHOSTUNREACH
              2022-04-03 21:47:09.520 - warn: discovery.0 (15140) Onkyo AVR discovery error Error: addMembership EHOSTUNREACH
              2022-04-03 21:47:09.522 - warn: discovery.0 (15140) Pioneer AVR discovery error Error: addMembership EHOSTUNREACH
              2022-04-03 21:47:12.032 - error: discovery.0 (15140) eky error Error: addMembership EHOSTUNREACH
              2022-04-03 21:47:12.033 - error: discovery.0 (15140) emby error Error: addMembership EHOSTUNREACH
              2022-04-03 21:47:12.036 - warn: discovery.0 (15140) Onkyo AVR discovery error Error: addMembership EHOSTUNREACH
              2022-04-03 21:47:12.037 - warn: discovery.0 (15140) Pioneer AVR discovery error Error: addMembership EHOSTUNREACH
              2022-04-03 21:47:14.562 - error: discovery.0 (15140) eky error Error: addMembership EHOSTUNREACH
              2022-04-03 21:47:14.564 - error: discovery.0 (15140) emby error Error: addMembership EHOSTUNREACH
              2022-04-03 21:47:14.571 - warn: discovery.0 (15140) Onkyo AVR discovery error Error: addMembership EHOSTUNREACH
              2022-04-03 21:47:14.571 - warn: discovery.0 (15140) Pioneer AVR discovery error Error: addMembership EHOSTUNREACH
              2022-04-03 21:47:17.085 - error: discovery.0 (15140) eky error Error: addMembership EHOSTUNREACH
              2022-04-03 21:47:17.086 - error: discovery.0 (15140) emby error Error: addMembership EHOSTUNREACH
              2022-04-03 21:47:17.089 - warn: discovery.0 (15140) Onkyo AVR discovery error Error: addMembership EHOSTUNREACH
              2022-04-03 21:47:17.090 - warn: discovery.0 (15140) Pioneer AVR discovery error Error: addMembership EHOSTUNREACH
              2022-04-03 21:47:19.643 - error: discovery.0 (15140) eky error Error: addMembership EHOSTUNREACH
              2022-04-03 21:47:19.645 - error: discovery.0 (15140) emby error Error: addMembership EHOSTUNREACH
              2022-04-03 21:47:19.652 - warn: discovery.0 (15140) Onkyo AVR discovery error Error: addMembership EHOSTUNREACH
              2022-04-03 21:47:19.654 - warn: discovery.0 (15140) Pioneer AVR discovery error Error: addMembership EHOSTUNREACH
              2022-04-03 21:47:22.196 - error: discovery.0 (15140) eky error Error: addMembership EHOSTUNREACH
              2022-04-03 21:47:22.197 - error: discovery.0 (15140) emby error Error: addMembership EHOSTUNREACH
              2022-04-03 21:47:22.199 - warn: discovery.0 (15140) Onkyo AVR discovery error Error: addMembership EHOSTUNREACH
              2022-04-03 21:47:22.201 - warn: discovery.0 (15140) Pioneer AVR discovery error Error: addMembership EHOSTUNREACH
              2022-04-03 21:47:24.728 - error: discovery.0 (15140) eky error Error: addMembership EHOSTUNREACH
              2022-04-03 21:47:24.729 - error: discovery.0 (15140) emby error Error: addMembership EHOSTUNREACH
              2022-04-03 21:47:24.732 - warn: discovery.0 (15140) Onkyo AVR discovery error Error: addMembership EHOSTUNREACH
              2022-04-03 21:47:24.733 - warn: discovery.0 (15140) Pioneer AVR discovery error Error: addMembership EHOSTUNREACH
              2022-04-03 21:47:27.280 - error: discovery.0 (15140) eky error Error: addMembership EHOSTUNREACH
              2022-04-03 21:47:27.282 - error: discovery.0 (15140) emby error Error: addMembership EHOSTUNREACH
              2022-04-03 21:47:27.287 - warn: discovery.0 (15140) Onkyo AVR discovery error Error: addMembership EHOSTUNREACH
              2022-04-03 21:47:27.288 - warn: discovery.0 (15140) Pioneer AVR discovery error Error: addMembership EHOSTUNREACH
              2022-04-03 21:47:29.827 - error: discovery.0 (15140) eky error Error: addMembership EHOSTUNREACH
              2022-04-03 21:47:29.828 - error: discovery.0 (15140) emby error Error: addMembership EHOSTUNREACH
              2022-04-03 21:47:29.833 - warn: discovery.0 (15140) Onkyo AVR discovery error Error: addMembership EHOSTUNREACH
              2022-04-03 21:47:29.833 - warn: discovery.0 (15140) Pioneer AVR discovery error Error: addMembership EHOSTUNREACH
              2022-04-03 21:47:30.605 - info: ham.0 (14104) stateChange ham.0.BASICR2.BASICR2-History.S2R1 {"val":"U80XAAAAAAAAZOInAQ4BewTADwAAAAAAAAAAAQE=","ack":true,"ts":1649015250603,"q":0,"from":"system.adapter.ham.0","user":"system.user.admin","lc":1649015250603}
              2022-04-03 21:47:30.605 - info: ham.0 (14104) stateChange ham.0.Warmwasser.Warmwasser-History.S2R1 {"val":"QHMjAAAAAAATvtYnAQ4BCQbADwAAAAAAAAAAAQE=","ack":true,"ts":1649015250604,"q":0,"from":"system.adapter.ham.0","user":"system.user.admin","lc":1649015250604}
              2022-04-03 21:47:30.606 - info: ham.0 (14104) stateChange ham.0.Heizung-.Heizung--History.S2R1 {"val":"QHMjAAAAAAATvtYnAgECDgEDBsAPAAAAAAAAAAABAQ==","ack":true,"ts":1649015250604,"q":0,"from":"system.adapter.ham.0","user":"system.user.admin","lc":1649015250604}
              2022-04-03 21:47:30.606 - info: ham.0 (14104) stateChange ham.0.Garagentoreantrieb-.Garagentoreantrieb--History.S2R1 {"val":"QHMjAAAAAAATvtYnAQ4BAwbADwAAAAAAAAAAAQE=","ack":true,"ts":1649015250604,"q":0,"from":"system.adapter.ham.0","user":"system.user.admin","lc":1649015250604}
              2022-04-03 21:47:30.606 - info: ham.0 (14104) stateChange ham.0.Hinterhof-Strahler.Hinterhof-Strahler-History.S2R1 {"val":"QHMjAAAAAAATvtYnAQ4BAwbADwAAAAAAAAAAAQE=","ack":true,"ts":1649015250604,"q":0,"from":"system.adapter.ham.0","user":"system.user.admin","lc":1649015250604}
              2022-04-03 21:47:30.607 - info: ham.0 (14104) stateChange ham.0.Kamera-Fitness-.Kamera-Fitness--History.S2R1 {"val":"QHMjAAAAAAATvtYnAQ4BBwbADwAAAAAAAAAAAQE=","ack":true,"ts":1649015250604,"q":0,"from":"system.adapter.ham.0","user":"system.user.admin","lc":1649015250604}
              2022-04-03 21:47:31.716 - debug: onvif.0 (9816) startCameras
              2022-04-03 21:47:31.718 - debug: onvif.0 (9816) getDevices: []
              2022-04-03 21:47:31.719 - debug: onvif.0 (9816) setCameras: []
              2022-04-03 21:47:31.719 - debug: onvif.0 (9816) startCameras. cameras: {}
              2022-04-03 21:47:31.719 - warn: onvif.0 (9816) startCameras: Cameras/NVT unavailables
              2022-04-03 21:47:32.373 - error: discovery.0 (15140) eky error Error: addMembership EHOSTUNREACH
              2022-04-03 21:47:32.374 - error: discovery.0 (15140) emby error Error: addMembership EHOSTUNREACH
              2022-04-03 21:47:32.377 - warn: discovery.0 (15140) Onkyo AVR discovery error Error: addMembership EHOSTUNREACH
              2022-04-03 21:47:32.377 - warn: discovery.0 (15140) Pioneer AVR discovery error Error: addMembership EHOSTUNREACH
              2022-04-03 21:47:38.992 - warn: discovery.0 (15140) write: 10;VERSION;
              2022-04-03 21:47:54.343 - warn: discovery.0 (15140) write: 10;VERSION;
              2022-04-03 21:47:59.122 - warn: discovery.0 (15140) write: 10;VERSION;
              2022-04-03 21:48:05.402 - info: discovery.0 (15140) Discovery finished. Found new or modified 16 instances
              2022-04-03 21:48:05.442 - info: discovery.0 (15140) Discovery finished
              2022-04-03 21:48:20.528 - info: host.Gerdprivat(Zuhause) stopInstance system.adapter.sonoff.0 (force=false, process=true)
              2022-04-03 21:48:20.530 - info: host.Gerdprivat(Zuhause) stopInstance system.adapter.sonoff.0 send kill signal
              2022-04-03 21:48:20.530 - info: sonoff.0 (25176) Got terminate signal TERMINATE_YOURSELF
              2022-04-03 21:48:20.532 - info: sonoff.0 (25176) terminating
              2022-04-03 21:48:20.532 - info: sonoff.0 (25176) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
              2022-04-03 21:48:21.059 - info: host.Gerdprivat(Zuhause) instance system.adapter.sonoff.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
              2022-04-03 21:48:21.403 - info: host.Gerdprivat(Zuhause) stopInstance system.adapter.sonoff.1 (force=false, process=true)
              2022-04-03 21:48:21.405 - info: host.Gerdprivat(Zuhause) stopInstance system.adapter.sonoff.1 send kill signal
              2022-04-03 21:48:21.405 - info: sonoff.1 (24384) Got terminate signal TERMINATE_YOURSELF
              2022-04-03 21:48:21.411 - info: sonoff.1 (24384) terminating
              2022-04-03 21:48:21.412 - info: sonoff.1 (24384) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
              2022-04-03 21:48:21.948 - info: host.Gerdprivat(Zuhause) instance system.adapter.sonoff.1 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
              2022-04-03 21:48:23.738 - info: host.Gerdprivat(Zuhause) instance system.adapter.sonoff.0 started with pid 21332
              2022-04-03 21:48:24.665 - info: host.Gerdprivat(Zuhause) instance system.adapter.sonoff.1 started with pid 5224
              2022-04-03 21:48:24.919 - info: sonoff.0 (21332) starting. Version 2.4.7 in C:/iobroker/Zuhause/node_modules/iobroker.sonoff, node: v14.19.0, js-controller: 4.0.18
              2022-04-03 21:48:24.944 - info: sonoff.0 (21332) Starting MQTT authenticated server on port 1883
              2022-04-03 21:48:25.635 - info: sonoff.1 (5224) starting. Version 2.4.7 in C:/iobroker/Zuhause/node_modules/iobroker.sonoff, node: v14.19.0, js-controller: 4.0.18
              2022-04-03 21:48:25.663 - error: sonoff.1 (5224) Can not start Server Error: listen EADDRINUSE: address already in use 0.0.0.0:1883
              2022-04-03 21:48:26.847 - error: host.Gerdprivat(Zuhause) cannot check file: C:\iobroker\Zuhause\log\iobroker.2022-03-17.log - EPERM: operation not permitted, lstat 'C:\iobroker\Zuhause\log\iobroker.2022-03-17.log'
              

              MOD-EDIT: Code in code-tags gesetzt

              crunchip 1 Reply Last reply Reply Quote 0
              • crunchip
                crunchip Forum Testing Most Active @GerdNutzinger last edited by crunchip

                @gerdnutzinger sagte in Iobroker findet Tasmota nicht...:

                already in use 0.0.0.0:1883

                schalte mal deine mqtt Instanz aus

                und dann die Frage, brauchst du mqtt, wenn ja, dann musst du den Port ändern
                standard verwendet mqtt Port 1883/1884, somt kannst du bei sonoff auf Port 1885 gehen
                das heisst in deiner sonoff Instanz, sowie auf deinen sonoff Geräten den Port 1885 eintragen, dann sollte es funktionieren

                Homoran G 3 Replies Last reply Reply Quote 1
                • Homoran
                  Homoran Global Moderator Administrators @crunchip last edited by

                  @crunchip sagte in Iobroker findet Tasmota nicht...:

                  @gerdnutzinger sagte in Iobroker findet Tasmota nicht...:

                  already in use 0.0.0.0:1883

                  schalte mal deine mqtt Instanz aus

                  wie ganz zu Beginn schon befürchtet

                  1 Reply Last reply Reply Quote 1
                  • G
                    GerdNutzinger @Homoran last edited by

                    @homoran said in Iobroker findet Tasmota nicht...:

                    iobroker list instances

                    dfb88958-e1bc-4db4-a4a5-55e3aec7e439-grafik.png

                    Homoran crunchip 2 Replies Last reply Reply Quote 0
                    • G
                      GerdNutzinger @crunchip last edited by

                      @crunchip

                      c1e5478f-1320-4bb1-ac4b-06779ce3e45c-grafik.png

                      gemacht

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

                        @gerdnutzinger da bin ich dann leider mangels Kenntnisse unter WIN raus.

                        G 1 Reply Last reply Reply Quote 0
                        • crunchip
                          crunchip Forum Testing Most Active @GerdNutzinger last edited by

                          @gerdnutzinger sagte in Iobroker findet Tasmota nicht...:

                          gemacht

                          falscher screen

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

                            ich klink mich aus, mein Akku ist auf 3%

                            1 Reply Last reply Reply Quote 0
                            • G
                              GerdNutzinger @Homoran last edited by

                              @homoran

                              Ich probier mal morgen noch etwas rum.

                              Trotzdem ganz herzlichen DANK und einen schönen Abend noch!

                              crunchip 1 Reply Last reply Reply Quote 0
                              • crunchip
                                crunchip Forum Testing Most Active @GerdNutzinger last edited by

                                @gerdnutzinger windows kenn ich auch nicht, aber dafür muss man denk ich in den Ordner iobroker wechseln

                                1 Reply Last reply Reply Quote 0
                                • crunchip
                                  crunchip Forum Testing Most Active @GerdNutzinger last edited by

                                  @gerdnutzinger hast du das gemacht, was ich geschrieben hab?

                                  1 Reply Last reply Reply Quote 0
                                  • G
                                    GerdNutzinger @crunchip last edited by

                                    @crunchip said in Iobroker findet Tasmota nicht...:

                                    @gerdnutzinger sagte in Iobroker findet Tasmota nicht...:

                                    already in use 0.0.0.0:1883

                                    schalte mal deine mqtt Instanz aus

                                    MQTT braucht man doch um es in IOBroker zubringen (habe ich gelesen in Netz)

                                    und dann die Frage, brauchst du mqtt, wenn ja, dann musst du den Port ändern
                                    standard verwendet mqtt Port 1883/1884, somt kannst du bei sonoff auf Port 1885 gehen
                                    das heisst in deiner sonoff Instanz, sowie auf deinen sonoff Geräten den Port 1885 eintragen, dann sollte es funktionieren

                                    Habe bei Sonoff - MQTT-Einstellungen und bei Instanzeinstellungen: sonoff.0 auch 1885 eingetragen.

                                    Ergebnis: negativ

                                    crunchip 1 Reply Last reply Reply Quote 0
                                    • crunchip
                                      crunchip Forum Testing Most Active @GerdNutzinger last edited by crunchip

                                      @gerdnutzinger sagte in Iobroker findet Tasmota nicht...:

                                      MQTT braucht man doch um es in IOBroker zubringen (habe ich gelesen in Netz)

                                      was?

                                      @gerdnutzinger sagte in Iobroker findet Tasmota nicht...:

                                      Habe bei Sonoff - MQTT-Einstellungen und bei Instanzeinstellungen: sonoff.0 auch 1885 eingetragen

                                      nein, es gibt den mqtt Adapter, dieser verwendet den Port 1883.
                                      es gibt aber auch den sonoff Adapter, der funktioniert "ähnlich" und nimmt dir eine Menge Arbeit ab.

                                      mit dem mqtt Adapter kannst du dir alle Geräte , die diese "Sprache sprechen" in den iobroker holen.
                                      der sonoff Adapter ist speziel, nur für sonoff/tasmota Geräte gedacht, dieser legt dir sämtliche benötigte Datenpunkte an, was dir die Arbeit erspart und ist leichter in der weiter Verarbeitung.

                                      Also entweder oder

                                      beide Adapter dürfen aber nicht auf dem selben Port laufen.

                                      • 1 Ist die mqtt Instanz ausgeschaltet?
                                      • 2 sonoff Instanz Port 1885 eingetragen?
                                      • 3 im sonoff, Port 1885 eingestellt?
                                      • 4 was zeigt das log, wenn du die Instanz startest?
                                      G 1 Reply Last reply Reply Quote 0
                                      • G
                                        GerdNutzinger @crunchip last edited by

                                        @crunchip said in Iobroker findet Tasmota nicht...:

                                        @gerdnutzinger sagte in Iobroker findet Tasmota nicht...:

                                        MQTT braucht man doch um es in IOBroker zubringen (habe ich gelesen in Netz)

                                        was?

                                        @gerdnutzinger sagte in Iobroker findet Tasmota nicht...:

                                        Habe bei Sonoff - MQTT-Einstellungen und bei Instanzeinstellungen: sonoff.0 auch 1885 eingetragen

                                        nein, es gibt den mqtt Adapter, dieser verwendet den Port 1883.
                                        es gibt aber auch den sonoff Adapter, der funktioniert "ähnlich" und nimmt dir eine Menge Arbeit ab.

                                        mit dem mqtt Adapter kannst du dir alle Geräte , die diese "Sprache sprechen" in den iobroker holen.
                                        der sonoff Adapter ist speziel, nur für sonoff/tasmota Geräte gedacht, dieser legt dir sämtliche benötigte Datenpunkte an, was dir die Arbeit erspart und ist leichter in der weiter Verarbeitung.

                                        Also entweder oder

                                        beide Adapter dürfen aber nicht auf dem selben Port laufen.

                                        • 1 Ist die mqtt Instanz ausgeschaltet? erledigt
                                        • 2 sonoff Instanz Port 1885 eingetragen? erledigt
                                        • 3 im sonoff, Port 1885 eingestellt? erledigt
                                        • 4 was zeigt das log, wenn du die Instanz startest?

                                        2022-04-04 11:43:21.648 - info: host.Gerdprivat(Zuhause) stopInstance system.adapter.sonoff.0 (force=false, process=true)
                                        2022-04-04 11:43:21.650 - info: host.Gerdprivat(Zuhause) stopInstance system.adapter.sonoff.0 send kill signal
                                        2022-04-04 11:43:21.650 - info: sonoff.0 (25340) Got terminate signal TERMINATE_YOURSELF
                                        2022-04-04 11:43:21.652 - info: sonoff.0 (25340) terminating
                                        2022-04-04 11:43:21.653 - info: sonoff.0 (25340) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
                                        2022-04-04 11:43:22.196 - info: host.Gerdprivat(Zuhause) instance system.adapter.sonoff.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
                                        2022-04-04 11:43:24.855 - info: host.Gerdprivat(Zuhause) instance system.adapter.sonoff.0 started with pid 26452
                                        2022-04-04 11:43:25.673 - info: sonoff.0 (26452) starting. Version 2.4.7 in C:/iobroker/Zuhause/node_modules/iobroker.sonoff, node: v14.19.0, js-controller: 4.0.18
                                        2022-04-04 11:43:25.695 - info: sonoff.0 (26452) Starting MQTT authenticated server on port 1885
                                        2022-04-04 11:43:29.772 - error: host.Gerdprivat(Zuhause) cannot check file: C:\iobroker\Zuhause\log\iobroker.2022-03-17.log - EPERM: operation not permitted, lstat 'C:\iobroker\Zuhause\log\iobroker.2022-03-17.log'

                                        crunchip 1 Reply Last reply Reply Quote 0
                                        • crunchip
                                          crunchip Forum Testing Most Active @GerdNutzinger last edited by crunchip

                                          @gerdnutzinger

                                          ok, das mit dem Port ist nun vom Tisch, jedoch hast du da noch ein anderes Problem, welches ich aber gerade nicht zuordnen kann

                                          @gerdnutzinger sagte in Iobroker findet Tasmota nicht...:

                                          2022-04-04 11:43:29.772 - error: host.Gerdprivat(Zuhause) cannot check file: C:\iobroker\Zuhause\log\iobroker.2022-03-17.log - EPERM: operation not permitted, lstat 'C:\iobroker\Zuhause\log\iobroker.2022-03-17.log'

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

                                            @GerdNutzinger
                                            hast du deinen zukünftigen Pi schon?

                                            Dann würde ich mal damit anfangen.

                                            G 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

                                            470
                                            Online

                                            31.7k
                                            Users

                                            79.9k
                                            Topics

                                            1.3m
                                            Posts

                                            9
                                            66
                                            4356
                                            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