Skip to content
  • Home
  • Aktuell
  • Tags
  • 0 Ungelesen 0
  • Kategorien
  • Unreplied
  • Beliebt
  • GitHub
  • Docu
  • Hilfe
Skins
  • Light
  • Brite
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Standard: (Kein Skin)
  • Kein Skin
Einklappen
ioBroker Logo

Community Forum

donate donate
  1. ioBroker Community Home
  2. Deutsch
  3. ioBroker Allgemein
  4. Owntracks läuft nicht mehr richtig nach Fritzbox tausch

NEWS

  • Jahresrückblick 2025 – unser neuer Blogbeitrag ist online! ✨
    BluefoxB
    Bluefox
    14
    1
    133

  • Neuer Blogbeitrag: Monatsrückblick - Dezember 2025 🎄
    BluefoxB
    Bluefox
    12
    1
    563

  • Weihnachtsangebot 2025! 🎄
    BluefoxB
    Bluefox
    24
    1
    1.7k

Owntracks läuft nicht mehr richtig nach Fritzbox tausch

Geplant Angeheftet Gesperrt Verschoben ioBroker Allgemein
dyndnsfritzbox 7590owntracks adapter
65 Beiträge 3 Kommentatoren 7.3k Aufrufe 1 Watching
  • Älteste zuerst
  • Neuste zuerst
  • Meiste Stimmen
Antworten
  • In einem neuen Thema antworten
Anmelden zum Antworten
Dieses Thema wurde gelöscht. Nur Nutzer mit entsprechenden Rechten können es sehen.
  • R rebel85

    @ro75

    ja habe ich angepasst,
    klappt aber noch nicht, bekomme immer noch Fehlermeldungen.

    2024-11-10 10:32:35.424	error	TypeError: Cannot set properties of null (setting 'encryption')
    2024-11-10 10:32:35.423	error	Cannot parse payload: {"_type":"encrypted","_id":"80059e21","data":"xyz"}
    2024-11-10 10:32:35.423	warn	Error: wrong secret key for the given ciphertext
    2024-11-10 10:32:32.337	error	TypeError: Cannot set properties of null (setting 'encryption')
    2024-11-10 10:32:32.337	error	Cannot parse payload: {"_type":"encrypted","_id":"93d0cb9e","data":"xyz"}
    2024-11-10 10:32:32.336	warn	Error: wrong secret key for the given ciphertext
    2024-11-10 10:32:29.064	error	TypeError: Cannot set properties of null (setting 'encryption')
    2024-11-10 10:32:29.064	error	Cannot parse payload: {"_type":"encrypted","_id":"38855c14","data":"xyz"}
    2024-11-10 10:32:29.064	warn	Error: wrong secret key for the given ciphertext
    2024-11-10 10:32:28.283	error	TypeError: Cannot set properties of null (setting 'encryption')
    

    Ist das rote so richtig?
    Screenshot_2024-11-10-10-33-38-041_org.owntracks.android.jpg
    iobroker_neu_angepasst.JPG

    Ro75R Online
    Ro75R Online
    Ro75
    schrieb am zuletzt editiert von Ro75
    #34

    @rebel85 sagte in Owntracks läuft nicht mehr richtig nach Fritzbox tausch:

    Error: wrong secret key for the given ciphertext

    Prüfe die Passphrase (damit ist nicht das Kennwort gemeint).

    Ro75.

    SERVER = Beelink U59 16GB DDR4 RAM 512GB SSD, FB 7490, FritzDect 200+301+440, ConBee II, Zigbee Aqara Sensoren + NOUS A1Z, NOUS A1T, Philips Hue ** ioBroker, REDIS, influxdb2, Grafana, PiHole, Plex-Mediaserver, paperless-ngx (Docker), MariaDB + phpmyadmin *** VIS-Runtime = Intel NUC 8GB RAM 128GB SSD + 24" Touchscreen

    R 1 Antwort Letzte Antwort
    0
    • Ro75R Ro75

      @rebel85 sagte in Owntracks läuft nicht mehr richtig nach Fritzbox tausch:

      Error: wrong secret key for the given ciphertext

      Prüfe die Passphrase (damit ist nicht das Kennwort gemeint).

      Ro75.

      R Offline
      R Offline
      rebel85
      schrieb am zuletzt editiert von
      #35

      @ro75
      Die setzte ich ja selber im Adapter oder?
      und trage die dann in der App unter: Verschlüsselung ein
      Foto
      Screenshot_2024-11-10-10-54-12-306_org.owntracks.android.jpg

      Ro75R 1 Antwort Letzte Antwort
      0
      • R rebel85

        @ro75
        Die setzte ich ja selber im Adapter oder?
        und trage die dann in der App unter: Verschlüsselung ein
        Foto
        Screenshot_2024-11-10-10-54-12-306_org.owntracks.android.jpg

        Ro75R Online
        Ro75R Online
        Ro75
        schrieb am zuletzt editiert von
        #36

        @rebel85 korrekt

        Ro75.

        SERVER = Beelink U59 16GB DDR4 RAM 512GB SSD, FB 7490, FritzDect 200+301+440, ConBee II, Zigbee Aqara Sensoren + NOUS A1Z, NOUS A1T, Philips Hue ** ioBroker, REDIS, influxdb2, Grafana, PiHole, Plex-Mediaserver, paperless-ngx (Docker), MariaDB + phpmyadmin *** VIS-Runtime = Intel NUC 8GB RAM 128GB SSD + 24" Touchscreen

        R 1 Antwort Letzte Antwort
        0
        • Ro75R Ro75

          @rebel85 korrekt

          Ro75.

          R Offline
          R Offline
          rebel85
          schrieb am zuletzt editiert von rebel85
          #37

          @ro75 sorry das wars nicht, habe ein neues vergeben, Zahlen und Buchstaben, in der App dann auch an der Stelle gesetzt und bekomme noch Fehler Meldungen.

          2024-11-10 10:58:23.483	error	TypeError: Cannot set properties of null (setting 'encryption')
          2024-11-10 10:58:23.482	error	Cannot parse payload: {"_type":"encrypted","_id":"3fe0b9f7","data":"wert"}
          2024-11-10 10:58:23.482	warn	Error: wrong secret key for the given ciphertext
          2024-11-10 10:58:15.177	error	TypeError: Cannot set properties of null (setting 'encryption')
          2024-11-10 10:58:15.177	error	Cannot parse payload: {"_type":"encrypted","_id":"37b9ec90","data":"wert"}
          2024-11-10 10:58:15.176	warn	Error: wrong secret key for the given ciphertext
          2024-11-10 10:58:11.324	warn	[iobroker] Error [ERR_STREAM_WRITE_AFTER_END]: write after end
          2024-11-10 10:56:05.966	warn	[iobroker] Error [ERR_STREAM_WRITE_AFTER_END]: write after end
          

          was ist mit Client ID , Geräte ID und Benutzername ?

          Client und Benutzername sind der gleiche wie im Adapter der Benutzer unter Verbindungseinstellungen

          Ro75R 2 Antworten Letzte Antwort
          0
          • R rebel85

            @ro75 sorry das wars nicht, habe ein neues vergeben, Zahlen und Buchstaben, in der App dann auch an der Stelle gesetzt und bekomme noch Fehler Meldungen.

            2024-11-10 10:58:23.483	error	TypeError: Cannot set properties of null (setting 'encryption')
            2024-11-10 10:58:23.482	error	Cannot parse payload: {"_type":"encrypted","_id":"3fe0b9f7","data":"wert"}
            2024-11-10 10:58:23.482	warn	Error: wrong secret key for the given ciphertext
            2024-11-10 10:58:15.177	error	TypeError: Cannot set properties of null (setting 'encryption')
            2024-11-10 10:58:15.177	error	Cannot parse payload: {"_type":"encrypted","_id":"37b9ec90","data":"wert"}
            2024-11-10 10:58:15.176	warn	Error: wrong secret key for the given ciphertext
            2024-11-10 10:58:11.324	warn	[iobroker] Error [ERR_STREAM_WRITE_AFTER_END]: write after end
            2024-11-10 10:56:05.966	warn	[iobroker] Error [ERR_STREAM_WRITE_AFTER_END]: write after end
            

            was ist mit Client ID , Geräte ID und Benutzername ?

            Client und Benutzername sind der gleiche wie im Adapter der Benutzer unter Verbindungseinstellungen

            Ro75R Online
            Ro75R Online
            Ro75
            schrieb am zuletzt editiert von
            #38

            @rebel85 sagte in Owntracks läuft nicht mehr richtig nach Fritzbox tausch:

            was ist mit Client ID , Geräte ID und Benutzername ?

            die müssen auch stimmen
            Ro75.

            SERVER = Beelink U59 16GB DDR4 RAM 512GB SSD, FB 7490, FritzDect 200+301+440, ConBee II, Zigbee Aqara Sensoren + NOUS A1Z, NOUS A1T, Philips Hue ** ioBroker, REDIS, influxdb2, Grafana, PiHole, Plex-Mediaserver, paperless-ngx (Docker), MariaDB + phpmyadmin *** VIS-Runtime = Intel NUC 8GB RAM 128GB SSD + 24" Touchscreen

            R 1 Antwort Letzte Antwort
            0
            • R rebel85

              @ro75 sorry das wars nicht, habe ein neues vergeben, Zahlen und Buchstaben, in der App dann auch an der Stelle gesetzt und bekomme noch Fehler Meldungen.

              2024-11-10 10:58:23.483	error	TypeError: Cannot set properties of null (setting 'encryption')
              2024-11-10 10:58:23.482	error	Cannot parse payload: {"_type":"encrypted","_id":"3fe0b9f7","data":"wert"}
              2024-11-10 10:58:23.482	warn	Error: wrong secret key for the given ciphertext
              2024-11-10 10:58:15.177	error	TypeError: Cannot set properties of null (setting 'encryption')
              2024-11-10 10:58:15.177	error	Cannot parse payload: {"_type":"encrypted","_id":"37b9ec90","data":"wert"}
              2024-11-10 10:58:15.176	warn	Error: wrong secret key for the given ciphertext
              2024-11-10 10:58:11.324	warn	[iobroker] Error [ERR_STREAM_WRITE_AFTER_END]: write after end
              2024-11-10 10:56:05.966	warn	[iobroker] Error [ERR_STREAM_WRITE_AFTER_END]: write after end
              

              was ist mit Client ID , Geräte ID und Benutzername ?

              Client und Benutzername sind der gleiche wie im Adapter der Benutzer unter Verbindungseinstellungen

              Ro75R Online
              Ro75R Online
              Ro75
              schrieb am zuletzt editiert von
              #39

              @rebel85 sagte in Owntracks läuft nicht mehr richtig nach Fritzbox tausch:

              Cannot set properties of null (setting 'encryption')

              Da ist etwas nicht gesetz. Prüfe alle Angaben und Einträge.

              Ro75.

              SERVER = Beelink U59 16GB DDR4 RAM 512GB SSD, FB 7490, FritzDect 200+301+440, ConBee II, Zigbee Aqara Sensoren + NOUS A1Z, NOUS A1T, Philips Hue ** ioBroker, REDIS, influxdb2, Grafana, PiHole, Plex-Mediaserver, paperless-ngx (Docker), MariaDB + phpmyadmin *** VIS-Runtime = Intel NUC 8GB RAM 128GB SSD + 24" Touchscreen

              1 Antwort Letzte Antwort
              0
              • Ro75R Ro75

                @rebel85 sagte in Owntracks läuft nicht mehr richtig nach Fritzbox tausch:

                was ist mit Client ID , Geräte ID und Benutzername ?

                die müssen auch stimmen
                Ro75.

                R Offline
                R Offline
                rebel85
                schrieb am zuletzt editiert von
                #40

                @ro75 was ist mit Client ID , Geräte ID und Benutzername ?

                Client und Benutzername sind der gleiche wie im Adapter der Benutzer unter Verbindungseinstellungen

                die Info auf der GitHub Seite ist gerade nicht wirklich hilfreich das alles zu finden.

                1 Antwort Letzte Antwort
                0
                • R Offline
                  R Offline
                  rebel85
                  schrieb am zuletzt editiert von
                  #41

                  Gerade im LOG gesehen.

                  2024-11-10 11:07:21.455	warn	[iobroker] Error [ERR_STREAM_WRITE_AFTER_END]: write after end
                  

                  Hilft vllt. die Konfigurationsverwaltung als Text - Datei?

                  github Link, Link

                  ... dort ist nichts mit Client ID erwähnt, nur Benutzer und Geräte ID

                  Ro75R 1 Antwort Letzte Antwort
                  0
                  • R rebel85

                    Gerade im LOG gesehen.

                    2024-11-10 11:07:21.455	warn	[iobroker] Error [ERR_STREAM_WRITE_AFTER_END]: write after end
                    

                    Hilft vllt. die Konfigurationsverwaltung als Text - Datei?

                    github Link, Link

                    ... dort ist nichts mit Client ID erwähnt, nur Benutzer und Geräte ID

                    Ro75R Online
                    Ro75R Online
                    Ro75
                    schrieb am zuletzt editiert von
                    #42

                    @rebel85 Etwas stimmt nicht. Ich habe keine Ideen mehr. Kann aber sagen, dass bei mir alles läuft. Vielleicht hat ein anderer ja noch Ideen.

                    Ro75.

                    SERVER = Beelink U59 16GB DDR4 RAM 512GB SSD, FB 7490, FritzDect 200+301+440, ConBee II, Zigbee Aqara Sensoren + NOUS A1Z, NOUS A1T, Philips Hue ** ioBroker, REDIS, influxdb2, Grafana, PiHole, Plex-Mediaserver, paperless-ngx (Docker), MariaDB + phpmyadmin *** VIS-Runtime = Intel NUC 8GB RAM 128GB SSD + 24" Touchscreen

                    R 1 Antwort Letzte Antwort
                    0
                    • Ro75R Ro75

                      @rebel85 Etwas stimmt nicht. Ich habe keine Ideen mehr. Kann aber sagen, dass bei mir alles läuft. Vielleicht hat ein anderer ja noch Ideen.

                      Ro75.

                      R Offline
                      R Offline
                      rebel85
                      schrieb am zuletzt editiert von
                      #43

                      @ro75 wie ist denn deine Konfiguration in Iobroker und in der App?
                      vllt hilft mir das den Fehler zu finden...

                      nach einmaligem App beenden und Neustarten gibt es aktuell keine Fehlermeldungen im Iobroker. aber auch bei
                      Letztes Standort Update vom Standortservice steht _ nicht verfügbar

                      Screenshot_2024-11-10-11-23-24-070_org.owntracks.android.jpg

                      Ro75R 1 Antwort Letzte Antwort
                      0
                      • R rebel85

                        @ro75 wie ist denn deine Konfiguration in Iobroker und in der App?
                        vllt hilft mir das den Fehler zu finden...

                        nach einmaligem App beenden und Neustarten gibt es aktuell keine Fehlermeldungen im Iobroker. aber auch bei
                        Letztes Standort Update vom Standortservice steht _ nicht verfügbar

                        Screenshot_2024-11-10-11-23-24-070_org.owntracks.android.jpg

                        Ro75R Online
                        Ro75R Online
                        Ro75
                        schrieb am zuletzt editiert von
                        #44

                        @rebel85 Screenshot_2024-11-10-11-38-42-625_org.owntracks.android.jpg Screenshot_2024-11-10-11-37-38-755_org.owntracks.android.jpg Screenshot_2024-11-10-11-36-03-560_org.owntracks.android.jpg Screenshot_2024-11-10-11-34-36-186_org.owntracks.android.jpg Screenshot_2024-11-10-11-33-43-773_org.owntracks.android.jpg Adapter.png

                        Schaue ggfs. in die Konfigurationsverwaltung in der APP. Da siehst du alles im Klartext und stellst ggfs. Abweichungen zum Adapter fest.

                        Ro75.

                        SERVER = Beelink U59 16GB DDR4 RAM 512GB SSD, FB 7490, FritzDect 200+301+440, ConBee II, Zigbee Aqara Sensoren + NOUS A1Z, NOUS A1T, Philips Hue ** ioBroker, REDIS, influxdb2, Grafana, PiHole, Plex-Mediaserver, paperless-ngx (Docker), MariaDB + phpmyadmin *** VIS-Runtime = Intel NUC 8GB RAM 128GB SSD + 24" Touchscreen

                        1 Antwort Letzte Antwort
                        1
                        • R Offline
                          R Offline
                          rebel85
                          schrieb am zuletzt editiert von
                          #45

                          Moin, heute habe ich nochmal die Adapter Werte neu eingegeben und im LOG Festgestellt das irgend was anderes Meldungen rausgibt.
                          Siehe da, mein ECOvacs Adapter macht Error Meldungen, WTF ich versuch mal den Port zu ändern und dann Erneut zu Verbinden.

                          Owntrack_Ecovacs.JPG

                          Ro75R 1 Antwort Letzte Antwort
                          0
                          • R rebel85

                            Moin, heute habe ich nochmal die Adapter Werte neu eingegeben und im LOG Festgestellt das irgend was anderes Meldungen rausgibt.
                            Siehe da, mein ECOvacs Adapter macht Error Meldungen, WTF ich versuch mal den Port zu ändern und dann Erneut zu Verbinden.

                            Owntrack_Ecovacs.JPG

                            Ro75R Online
                            Ro75R Online
                            Ro75
                            schrieb am zuletzt editiert von
                            #46

                            @rebel85 was hat das mit Owntracks zu tun?

                            Ro75

                            SERVER = Beelink U59 16GB DDR4 RAM 512GB SSD, FB 7490, FritzDect 200+301+440, ConBee II, Zigbee Aqara Sensoren + NOUS A1Z, NOUS A1T, Philips Hue ** ioBroker, REDIS, influxdb2, Grafana, PiHole, Plex-Mediaserver, paperless-ngx (Docker), MariaDB + phpmyadmin *** VIS-Runtime = Intel NUC 8GB RAM 128GB SSD + 24" Touchscreen

                            R 1 Antwort Letzte Antwort
                            0
                            • Ro75R Ro75

                              @rebel85 was hat das mit Owntracks zu tun?

                              Ro75

                              R Offline
                              R Offline
                              rebel85
                              schrieb am zuletzt editiert von
                              #47

                              @ro75 ist beim wechsel des Freigabe Ports auf einmal in den logs aufgetaucht, nach erneutem wechseln wars wieder weg.
                              leider alles ohne erfolg, ich bin aber noch am probieren bzw rauskriegen was die owntracks handy meldung ztu sagen hat.Screenshot_2024-11-14-17-35-49-719_org.owntracks.android.jpg

                              Ro75R 1 Antwort Letzte Antwort
                              0
                              • R rebel85

                                @ro75 ist beim wechsel des Freigabe Ports auf einmal in den logs aufgetaucht, nach erneutem wechseln wars wieder weg.
                                leider alles ohne erfolg, ich bin aber noch am probieren bzw rauskriegen was die owntracks handy meldung ztu sagen hat.Screenshot_2024-11-14-17-35-49-719_org.owntracks.android.jpg

                                Ro75R Online
                                Ro75R Online
                                Ro75
                                schrieb am zuletzt editiert von
                                #48

                                @rebel85 ja was sagt bzw. steht denn im Log?

                                Ro75

                                SERVER = Beelink U59 16GB DDR4 RAM 512GB SSD, FB 7490, FritzDect 200+301+440, ConBee II, Zigbee Aqara Sensoren + NOUS A1Z, NOUS A1T, Philips Hue ** ioBroker, REDIS, influxdb2, Grafana, PiHole, Plex-Mediaserver, paperless-ngx (Docker), MariaDB + phpmyadmin *** VIS-Runtime = Intel NUC 8GB RAM 128GB SSD + 24" Touchscreen

                                R 1 Antwort Letzte Antwort
                                0
                                • Ro75R Ro75

                                  @rebel85 ja was sagt bzw. steht denn im Log?

                                  Ro75

                                  R Offline
                                  R Offline
                                  rebel85
                                  schrieb am zuletzt editiert von
                                  #49

                                  @ro75 lade ich morgen hoch, muss ich erst noch prüfen und dann copy paste hier rein

                                  1 Antwort Letzte Antwort
                                  0
                                  • R Offline
                                    R Offline
                                    rebel85
                                    schrieb am zuletzt editiert von
                                    #50

                                    hier der letzte uszug aus dem log

                                    2024-11-14 17:40:29.691 I [DefaultDispatcher-worker-3] MQTTMessageProcessorEndpoint$connectToBroker: Connecting to tcp://mqttowntracks.ddns.net:1886?# timeout = 30s
                                    2024-11-14 17:40:30.115 I [DefaultDispatcher-worker-3] MQTTMessageProcessorEndpoint$connectToBroker: MQTT Connected. Subscribing to [owntracks/+/+, owntracks/+/+/event, owntracks/+/+/info, owntracks/+/+/status, owntracks/iobroker/Marco/cmd]
                                    2024-11-14 17:40:30.156 I [DefaultDispatcher-worker-3] MQTTMessageProcessorEndpoint$connectToBroker: MQTT Subscribed
                                    2024-11-14 17:40:30.362 I [MQTT Call: iobroker] MessageProcessor: Received incoming message: MessageCard on owntracks/iobroker/Marco/info with id=xyz
                                    2024-11-14 17:40:30.400 I [MQTT Call: iobroker] MessageProcessor: Received incoming message: MessageCard on owntracks/iobroker/Melli/info with id=xyz
                                    2024-11-14 17:40:31.280 I [DefaultDispatcher-worker-3] MQTTReconnectWorker: MQTT reconnect worker job started
                                    2024-11-14 17:40:31.291 I [DefaultDispatcher-worker-3] MQTTMessageProcessorEndpoint$connectToBroker: Connecting to tcp://mqttowntracks.ddns.net:1886?# timeout = 30s
                                    2024-11-14 17:40:31.686 I [DefaultDispatcher-worker-3] MQTTMessageProcessorEndpoint$connectToBroker: MQTT Connected. Subscribing to [owntracks/+/+, owntracks/+/+/event, owntracks/+/+/info, owntracks/+/+/status, owntracks/iobroker/Marco/cmd]
                                    2024-11-14 17:40:31.729 I [DefaultDispatcher-worker-3] MQTTMessageProcessorEndpoint$connectToBroker: MQTT Subscribed
                                    2024-11-14 17:40:31.730 I [DefaultDispatcher-worker-3] MQTTReconnectWorker: MQTT reconnect worker job completed, status Success {mOutputData=Data {}}
                                    2024-11-14 17:40:31.934 I [MQTT Call: iobroker] MessageProcessor: Received incoming message: MessageCard on owntracks/iobroker/Marco/info with id=xyz
                                    2024-11-14 17:40:31.972 I [MQTT Call: iobroker] MessageProcessor: Received incoming message: MessageCard on owntracks/iobroker/Melli/info with id=xyz
                                    2024-11-14 17:41:13.741 E [MQTT Rec: iobroker] MQTTMessageProcessorEndpoint$mqttCallback: Connection Lost
                                    Verbindung wurde getrennt (32109) - java.net.SocketException: Software caused connection abort
                                    	at org.eclipse.paho.client.mqttv3.internal.CommsSender.run(SourceFile:261)
                                    	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:487)
                                    	at java.util.concurrent.FutureTask.run(FutureTask.java:264)
                                    	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:307)
                                    	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
                                    	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:644)
                                    	at java.lang.Thread.run(Thread.java:1012)
                                    Caused by: java.net.SocketException: Software caused connection abort
                                    	at java.net.SocketInputStream.socketRead0(Native Method)
                                    	at java.net.SocketInputStream.socketRead(SocketInputStream.java:118)
                                    	at java.net.SocketInputStream.read(SocketInputStream.java:173)
                                    	at java.net.SocketInputStream.read(SocketInputStream.java:143)
                                    	at java.net.SocketInputStream.read(SocketInputStream.java:205)
                                    	at java.io.DataInputStream.readByte(DataInputStream.java:273)
                                    	at org.eclipse.paho.client.mqttv3.internal.wire.MqttInputStream.readMqttWireMessage(SourceFile:14)
                                    	at org.eclipse.paho.client.mqttv3.internal.CommsSender.run(SourceFile:88)
                                    	... 6 more
                                    
                                    2024-11-14 17:41:13.839 I [DefaultDispatcher-worker-5] MQTTMessageProcessorEndpoint$connectToBroker: Connecting to tcp://mqttowntracks.ddns.net:1886?# timeout = 30s
                                    2024-11-14 17:41:14.372 I [DefaultDispatcher-worker-5] MQTTMessageProcessorEndpoint$connectToBroker: MQTT Connected. Subscribing to [owntracks/+/+, owntracks/+/+/event, owntracks/+/+/info, owntracks/+/+/status, owntracks/iobroker/Marco/cmd]
                                    2024-11-14 17:41:14.419 I [DefaultDispatcher-worker-5] MQTTMessageProcessorEndpoint$connectToBroker: MQTT Subscribed
                                    2024-11-14 17:41:14.633 I [MQTT Call: iobroker] MessageProcessor: Received incoming message: MessageCard on owntracks/iobroker/Marco/info with id=xyz
                                    2024-11-14 17:41:14.670 I [MQTT Call: iobroker] MessageProcessor: Received incoming message: MessageCard on owntracks/iobroker/Melli/info with id=xyz
                                    2024-11-14 18:23:10.427 E [MQTT Rec: iobroker] MQTTMessageProcessorEndpoint$mqttCallback: Connection Lost
                                    Verbindung wurde getrennt (32109) - java.net.SocketException: Software caused connection abort
                                    	at org.eclipse.paho.client.mqttv3.internal.CommsSender.run(SourceFile:261)
                                    	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:487)
                                    	at java.util.concurrent.FutureTask.run(FutureTask.java:264)
                                    	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:307)
                                    	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
                                    	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:644)
                                    	at java.lang.Thread.run(Thread.java:1012)
                                    Caused by: java.net.SocketException: Software caused connection abort
                                    	at java.net.SocketInputStream.socketRead0(Native Method)
                                    	at java.net.SocketInputStream.socketRead(SocketInputStream.java:118)
                                    	at java.net.SocketInputStream.read(SocketInputStream.java:173)
                                    	at java.net.SocketInputStream.read(SocketInputStream.java:143)
                                    	at java.net.SocketInputStream.read(SocketInputStream.java:205)
                                    	at java.io.DataInputStream.readByte(DataInputStream.java:273)
                                    	at org.eclipse.paho.client.mqttv3.internal.wire.MqttInputStream.readMqttWireMessage(SourceFile:14)
                                    	at org.eclipse.paho.client.mqttv3.internal.CommsSender.run(SourceFile:88)
                                    	... 6 more
                                    
                                    2024-11-14 18:23:38.940 I [DefaultDispatcher-worker-5] MQTTReconnectWorker: MQTT reconnect worker job started
                                    2024-11-14 18:23:38.957 I [DefaultDispatcher-worker-5] MQTTMessageProcessorEndpoint$connectToBroker: Connecting to tcp://mqttowntracks.ddns.net:1886?# timeout = 30s
                                    2024-11-14 18:24:00.659 I [DefaultDispatcher-worker-3] MQTTReconnectWorker: MQTT reconnect worker job started
                                    2024-11-14 18:24:04.646 E [DefaultDispatcher-worker-5] MQTTMessageProcessorEndpoint$connectToBroker: MQTT client unable to connect to endpoint
                                    MqttException (0) - java.net.UnknownHostException: mqttowntracks.ddns.net
                                    	at androidx.work.impl.utils.WorkForegroundUpdater$1.run(SourceFile:233)
                                    	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:487)
                                    	at java.util.concurrent.FutureTask.run(FutureTask.java:264)
                                    	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:307)
                                    	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
                                    	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:644)
                                    	at java.lang.Thread.run(Thread.java:1012)
                                    Caused by: java.net.UnknownHostException: mqttowntracks.ddns.net
                                    	at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:208)
                                    	at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:436)
                                    	at java.net.Socket.connect(Socket.java:646)
                                    	at org.eclipse.paho.client.mqttv3.internal.TCPNetworkModule.start(SourceFile:50)
                                    	at androidx.work.impl.utils.WorkForegroundUpdater$1.run(SourceFile:66)
                                    	... 6 more
                                    
                                    2024-11-14 18:24:04.654 E [DefaultDispatcher-worker-3] MQTTMessageProcessorEndpointKt: BOO
                                    kotlinx.coroutines.JobCancellationException: Job was cancelled; job=JobImpl{Cancelling}@xyz
                                    
                                    2024-11-14 18:24:04.655 I [DefaultDispatcher-worker-3] MQTTReconnectWorker: MQTT reconnect worker job completed, status Retry
                                    2024-11-14 18:24:04.669 I [DefaultDispatcher-worker-5] MQTTMessageProcessorEndpoint$connectToBroker: Connecting to tcp://mqttowntracks.ddns.net:1886?# timeout = 30s
                                    2024-11-14 18:24:04.671 E [DefaultDispatcher-worker-5] MQTTMessageProcessorEndpoint$connectToBroker: MQTT client unable to connect to endpoint
                                    MqttException (0) - java.net.UnknownHostException: mqttowntracks.ddns.net
                                    	at androidx.work.impl.utils.WorkForegroundUpdater$1.run(SourceFile:233)
                                    	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:487)
                                    	at java.util.concurrent.FutureTask.run(FutureTask.java:264)
                                    	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:307)
                                    	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
                                    	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:644)
                                    	at java.lang.Thread.run(Thread.java:1012)
                                    Caused by: java.net.UnknownHostException: mqttowntracks.ddns.net
                                    	at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:208)
                                    	at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:436)
                                    	at java.net.Socket.connect(Socket.java:646)
                                    	at org.eclipse.paho.client.mqttv3.internal.TCPNetworkModule.start(SourceFile:50)
                                    	at androidx.work.impl.utils.WorkForegroundUpdater$1.run(SourceFile:66)
                                    	... 6 more
                                    
                                    2024-11-14 18:24:04.672 E [DefaultDispatcher-worker-5] MQTTMessageProcessorEndpointKt: BOO
                                    kotlinx.coroutines.JobCancellationException: Job was cancelled; job=JobImpl{Cancelling}@xyz
                                    
                                    2024-11-14 18:24:04.672 I [DefaultDispatcher-worker-5] MQTTReconnectWorker: MQTT reconnect worker job completed, status Retry
                                    2024-11-14 18:24:16.494 I [DefaultDispatcher-worker-3] MQTTReconnectWorker: MQTT reconnect worker job started
                                    2024-11-14 18:24:16.498 I [DefaultDispatcher-worker-3] MQTTMessageProcessorEndpoint$connectToBroker: Connecting to tcp://mqttowntracks.ddns.net:1886?# timeout = 30s
                                    2024-11-14 18:24:16.883 I [DefaultDispatcher-worker-3] MQTTMessageProcessorEndpoint$connectToBroker: MQTT Connected. Subscribing to [owntracks/+/+, owntracks/+/+/event, owntracks/+/+/info, owntracks/+/+/status, owntracks/iobroker/Marco/cmd]
                                    2024-11-14 18:24:16.889 I [DefaultDispatcher-worker-3] MQTTMessageProcessorEndpoint$connectToBroker: MQTT Subscribed
                                    2024-11-14 18:24:16.890 I [DefaultDispatcher-worker-3] MQTTReconnectWorker: MQTT reconnect worker job completed, status Success {mOutputData=Data {}}
                                    2024-11-14 18:24:17.127 I [MQTT Call: iobroker] MessageProcessor: Received incoming message: MessageCard on owntracks/iobroker/Marco/info with id=xyz
                                    2024-11-14 18:24:17.130 I [MQTT Call: iobroker] MessageProcessor: Received incoming message: MessageCard on owntracks/iobroker/Melli/info with id=xyz
                                    2024-11-14 19:27:42.963 E [MQTT Rec: iobroker] MQTTMessageProcessorEndpoint$mqttCallback: Connection Lost
                                    Verbindung wurde getrennt (32109) - java.net.SocketException: Connection reset
                                    	at org.eclipse.paho.client.mqttv3.internal.CommsSender.run(SourceFile:261)
                                    	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:487)
                                    	at java.util.concurrent.FutureTask.run(FutureTask.java:264)
                                    	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:307)
                                    	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
                                    	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:644)
                                    	at java.lang.Thread.run(Thread.java:1012)
                                    Caused by: java.net.SocketException: Connection reset
                                    	at java.net.SocketInputStream.read(SocketInputStream.java:191)
                                    	at java.net.SocketInputStream.read(SocketInputStream.java:143)
                                    	at java.net.SocketInputStream.read(SocketInputStream.java:205)
                                    	at java.io.DataInputStream.readByte(DataInputStream.java:273)
                                    	at org.eclipse.paho.client.mqttv3.internal.wire.MqttInputStream.readMqttWireMessage(SourceFile:14)
                                    	at org.eclipse.paho.client.mqttv3.internal.CommsSender.run(SourceFile:88)
                                    	... 6 more
                                    
                                    2024-11-14 19:29:18.016 I [DefaultDispatcher-worker-3] MQTTReconnectWorker: MQTT reconnect worker job started
                                    2024-11-14 19:29:18.038 I [DefaultDispatcher-worker-3] MQTTMessageProcessorEndpoint$connectToBroker: Connecting to tcp://mqttowntracks.ddns.net:1886?# timeout = 30s
                                    2024-11-14 19:29:18.544 I [DefaultDispatcher-worker-3] MQTTMessageProcessorEndpoint$connectToBroker: MQTT Connected. Subscribing to [owntracks/+/+, owntracks/+/+/event, owntracks/+/+/info, owntracks/+/+/status, owntracks/iobroker/Marco/cmd]
                                    2024-11-14 19:29:18.552 I [DefaultDispatcher-worker-3] MQTTMessageProcessorEndpoint$connectToBroker: MQTT Subscribed
                                    2024-11-14 19:29:18.555 I [DefaultDispatcher-worker-3] MQTTReconnectWorker: MQTT reconnect worker job completed, status Success {mOutputData=Data {}}
                                    2024-11-14 19:29:18.782 I [MQTT Call: iobroker] MessageProcessor: Received incoming message: MessageCard on owntracks/iobroker/Marco/info with id=xyz
                                    2024-11-14 19:29:18.797 I [MQTT Call: iobroker] MessageProcessor: Received incoming message: MessageCard on owntracks/iobroker/Melli/info with id=xyz
                                    2024-11-14 19:34:47.810 W [main] MapFragment: unable to update marker for Contact owntracks/iobroker/Marco (Marco). no location
                                    2024-11-14 19:34:47.810 W [main] MapFragment: unable to update marker for Contact owntracks/iobroker/Melli (Melli). no location
                                    2024-11-14 19:34:47.872 W [main] MapFragment: unable to update marker for Contact owntracks/iobroker/Marco (Marco). no location
                                    2024-11-14 19:34:47.872 W [main] MapFragment: unable to update marker for Contact owntracks/iobroker/Melli (Melli). no location
                                    2024-11-14 19:34:49.031 I [DefaultDispatcher-worker-8] MQTTMessageProcessorEndpoint: Sending message [MessageStatus android=org.owntracks.android.model.messages.AddMessageStatus@xyz]
                                    2024-11-14 19:34:49.033 I [DefaultDispatcher-worker-5] MQTTMessageProcessorEndpoint$sendMessage$2$1$job: Message [MessageStatus android=org.owntracks.android.model.messages.AddMessageStatus@xyz] dispatched in 2.055834ms
                                    2024-11-14 19:34:49.067 I [MQTT Call: iobroker] MessageProcessor: Received incoming message: MessageStatus on owntracks/iobroker/Marco/status with id=xyz
                                    2024-11-14 19:34:50.207 I [DefaultDispatcher-worker-8] MQTTMessageProcessorEndpoint: Sending message [MessageStatus android=org.owntracks.android.model.messages.AddMessageStatus@xyz]
                                    2024-11-14 19:34:50.210 I [DefaultDispatcher-worker-5] MQTTMessageProcessorEndpoint$sendMessage$2$1$job: Message [MessageStatus android=org.owntracks.android.model.messages.AddMessageStatus@xyz] dispatched in 710.052us
                                    2024-11-14 19:34:50.234 I [MQTT Call: iobroker] MessageProcessor: Received incoming message: MessageStatus on owntracks/iobroker/Marco/status with id=xyz
                                    
                                    Ro75R 1 Antwort Letzte Antwort
                                    0
                                    • R rebel85

                                      hier der letzte uszug aus dem log

                                      2024-11-14 17:40:29.691 I [DefaultDispatcher-worker-3] MQTTMessageProcessorEndpoint$connectToBroker: Connecting to tcp://mqttowntracks.ddns.net:1886?# timeout = 30s
                                      2024-11-14 17:40:30.115 I [DefaultDispatcher-worker-3] MQTTMessageProcessorEndpoint$connectToBroker: MQTT Connected. Subscribing to [owntracks/+/+, owntracks/+/+/event, owntracks/+/+/info, owntracks/+/+/status, owntracks/iobroker/Marco/cmd]
                                      2024-11-14 17:40:30.156 I [DefaultDispatcher-worker-3] MQTTMessageProcessorEndpoint$connectToBroker: MQTT Subscribed
                                      2024-11-14 17:40:30.362 I [MQTT Call: iobroker] MessageProcessor: Received incoming message: MessageCard on owntracks/iobroker/Marco/info with id=xyz
                                      2024-11-14 17:40:30.400 I [MQTT Call: iobroker] MessageProcessor: Received incoming message: MessageCard on owntracks/iobroker/Melli/info with id=xyz
                                      2024-11-14 17:40:31.280 I [DefaultDispatcher-worker-3] MQTTReconnectWorker: MQTT reconnect worker job started
                                      2024-11-14 17:40:31.291 I [DefaultDispatcher-worker-3] MQTTMessageProcessorEndpoint$connectToBroker: Connecting to tcp://mqttowntracks.ddns.net:1886?# timeout = 30s
                                      2024-11-14 17:40:31.686 I [DefaultDispatcher-worker-3] MQTTMessageProcessorEndpoint$connectToBroker: MQTT Connected. Subscribing to [owntracks/+/+, owntracks/+/+/event, owntracks/+/+/info, owntracks/+/+/status, owntracks/iobroker/Marco/cmd]
                                      2024-11-14 17:40:31.729 I [DefaultDispatcher-worker-3] MQTTMessageProcessorEndpoint$connectToBroker: MQTT Subscribed
                                      2024-11-14 17:40:31.730 I [DefaultDispatcher-worker-3] MQTTReconnectWorker: MQTT reconnect worker job completed, status Success {mOutputData=Data {}}
                                      2024-11-14 17:40:31.934 I [MQTT Call: iobroker] MessageProcessor: Received incoming message: MessageCard on owntracks/iobroker/Marco/info with id=xyz
                                      2024-11-14 17:40:31.972 I [MQTT Call: iobroker] MessageProcessor: Received incoming message: MessageCard on owntracks/iobroker/Melli/info with id=xyz
                                      2024-11-14 17:41:13.741 E [MQTT Rec: iobroker] MQTTMessageProcessorEndpoint$mqttCallback: Connection Lost
                                      Verbindung wurde getrennt (32109) - java.net.SocketException: Software caused connection abort
                                      	at org.eclipse.paho.client.mqttv3.internal.CommsSender.run(SourceFile:261)
                                      	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:487)
                                      	at java.util.concurrent.FutureTask.run(FutureTask.java:264)
                                      	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:307)
                                      	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
                                      	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:644)
                                      	at java.lang.Thread.run(Thread.java:1012)
                                      Caused by: java.net.SocketException: Software caused connection abort
                                      	at java.net.SocketInputStream.socketRead0(Native Method)
                                      	at java.net.SocketInputStream.socketRead(SocketInputStream.java:118)
                                      	at java.net.SocketInputStream.read(SocketInputStream.java:173)
                                      	at java.net.SocketInputStream.read(SocketInputStream.java:143)
                                      	at java.net.SocketInputStream.read(SocketInputStream.java:205)
                                      	at java.io.DataInputStream.readByte(DataInputStream.java:273)
                                      	at org.eclipse.paho.client.mqttv3.internal.wire.MqttInputStream.readMqttWireMessage(SourceFile:14)
                                      	at org.eclipse.paho.client.mqttv3.internal.CommsSender.run(SourceFile:88)
                                      	... 6 more
                                      
                                      2024-11-14 17:41:13.839 I [DefaultDispatcher-worker-5] MQTTMessageProcessorEndpoint$connectToBroker: Connecting to tcp://mqttowntracks.ddns.net:1886?# timeout = 30s
                                      2024-11-14 17:41:14.372 I [DefaultDispatcher-worker-5] MQTTMessageProcessorEndpoint$connectToBroker: MQTT Connected. Subscribing to [owntracks/+/+, owntracks/+/+/event, owntracks/+/+/info, owntracks/+/+/status, owntracks/iobroker/Marco/cmd]
                                      2024-11-14 17:41:14.419 I [DefaultDispatcher-worker-5] MQTTMessageProcessorEndpoint$connectToBroker: MQTT Subscribed
                                      2024-11-14 17:41:14.633 I [MQTT Call: iobroker] MessageProcessor: Received incoming message: MessageCard on owntracks/iobroker/Marco/info with id=xyz
                                      2024-11-14 17:41:14.670 I [MQTT Call: iobroker] MessageProcessor: Received incoming message: MessageCard on owntracks/iobroker/Melli/info with id=xyz
                                      2024-11-14 18:23:10.427 E [MQTT Rec: iobroker] MQTTMessageProcessorEndpoint$mqttCallback: Connection Lost
                                      Verbindung wurde getrennt (32109) - java.net.SocketException: Software caused connection abort
                                      	at org.eclipse.paho.client.mqttv3.internal.CommsSender.run(SourceFile:261)
                                      	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:487)
                                      	at java.util.concurrent.FutureTask.run(FutureTask.java:264)
                                      	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:307)
                                      	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
                                      	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:644)
                                      	at java.lang.Thread.run(Thread.java:1012)
                                      Caused by: java.net.SocketException: Software caused connection abort
                                      	at java.net.SocketInputStream.socketRead0(Native Method)
                                      	at java.net.SocketInputStream.socketRead(SocketInputStream.java:118)
                                      	at java.net.SocketInputStream.read(SocketInputStream.java:173)
                                      	at java.net.SocketInputStream.read(SocketInputStream.java:143)
                                      	at java.net.SocketInputStream.read(SocketInputStream.java:205)
                                      	at java.io.DataInputStream.readByte(DataInputStream.java:273)
                                      	at org.eclipse.paho.client.mqttv3.internal.wire.MqttInputStream.readMqttWireMessage(SourceFile:14)
                                      	at org.eclipse.paho.client.mqttv3.internal.CommsSender.run(SourceFile:88)
                                      	... 6 more
                                      
                                      2024-11-14 18:23:38.940 I [DefaultDispatcher-worker-5] MQTTReconnectWorker: MQTT reconnect worker job started
                                      2024-11-14 18:23:38.957 I [DefaultDispatcher-worker-5] MQTTMessageProcessorEndpoint$connectToBroker: Connecting to tcp://mqttowntracks.ddns.net:1886?# timeout = 30s
                                      2024-11-14 18:24:00.659 I [DefaultDispatcher-worker-3] MQTTReconnectWorker: MQTT reconnect worker job started
                                      2024-11-14 18:24:04.646 E [DefaultDispatcher-worker-5] MQTTMessageProcessorEndpoint$connectToBroker: MQTT client unable to connect to endpoint
                                      MqttException (0) - java.net.UnknownHostException: mqttowntracks.ddns.net
                                      	at androidx.work.impl.utils.WorkForegroundUpdater$1.run(SourceFile:233)
                                      	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:487)
                                      	at java.util.concurrent.FutureTask.run(FutureTask.java:264)
                                      	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:307)
                                      	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
                                      	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:644)
                                      	at java.lang.Thread.run(Thread.java:1012)
                                      Caused by: java.net.UnknownHostException: mqttowntracks.ddns.net
                                      	at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:208)
                                      	at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:436)
                                      	at java.net.Socket.connect(Socket.java:646)
                                      	at org.eclipse.paho.client.mqttv3.internal.TCPNetworkModule.start(SourceFile:50)
                                      	at androidx.work.impl.utils.WorkForegroundUpdater$1.run(SourceFile:66)
                                      	... 6 more
                                      
                                      2024-11-14 18:24:04.654 E [DefaultDispatcher-worker-3] MQTTMessageProcessorEndpointKt: BOO
                                      kotlinx.coroutines.JobCancellationException: Job was cancelled; job=JobImpl{Cancelling}@xyz
                                      
                                      2024-11-14 18:24:04.655 I [DefaultDispatcher-worker-3] MQTTReconnectWorker: MQTT reconnect worker job completed, status Retry
                                      2024-11-14 18:24:04.669 I [DefaultDispatcher-worker-5] MQTTMessageProcessorEndpoint$connectToBroker: Connecting to tcp://mqttowntracks.ddns.net:1886?# timeout = 30s
                                      2024-11-14 18:24:04.671 E [DefaultDispatcher-worker-5] MQTTMessageProcessorEndpoint$connectToBroker: MQTT client unable to connect to endpoint
                                      MqttException (0) - java.net.UnknownHostException: mqttowntracks.ddns.net
                                      	at androidx.work.impl.utils.WorkForegroundUpdater$1.run(SourceFile:233)
                                      	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:487)
                                      	at java.util.concurrent.FutureTask.run(FutureTask.java:264)
                                      	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:307)
                                      	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
                                      	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:644)
                                      	at java.lang.Thread.run(Thread.java:1012)
                                      Caused by: java.net.UnknownHostException: mqttowntracks.ddns.net
                                      	at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:208)
                                      	at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:436)
                                      	at java.net.Socket.connect(Socket.java:646)
                                      	at org.eclipse.paho.client.mqttv3.internal.TCPNetworkModule.start(SourceFile:50)
                                      	at androidx.work.impl.utils.WorkForegroundUpdater$1.run(SourceFile:66)
                                      	... 6 more
                                      
                                      2024-11-14 18:24:04.672 E [DefaultDispatcher-worker-5] MQTTMessageProcessorEndpointKt: BOO
                                      kotlinx.coroutines.JobCancellationException: Job was cancelled; job=JobImpl{Cancelling}@xyz
                                      
                                      2024-11-14 18:24:04.672 I [DefaultDispatcher-worker-5] MQTTReconnectWorker: MQTT reconnect worker job completed, status Retry
                                      2024-11-14 18:24:16.494 I [DefaultDispatcher-worker-3] MQTTReconnectWorker: MQTT reconnect worker job started
                                      2024-11-14 18:24:16.498 I [DefaultDispatcher-worker-3] MQTTMessageProcessorEndpoint$connectToBroker: Connecting to tcp://mqttowntracks.ddns.net:1886?# timeout = 30s
                                      2024-11-14 18:24:16.883 I [DefaultDispatcher-worker-3] MQTTMessageProcessorEndpoint$connectToBroker: MQTT Connected. Subscribing to [owntracks/+/+, owntracks/+/+/event, owntracks/+/+/info, owntracks/+/+/status, owntracks/iobroker/Marco/cmd]
                                      2024-11-14 18:24:16.889 I [DefaultDispatcher-worker-3] MQTTMessageProcessorEndpoint$connectToBroker: MQTT Subscribed
                                      2024-11-14 18:24:16.890 I [DefaultDispatcher-worker-3] MQTTReconnectWorker: MQTT reconnect worker job completed, status Success {mOutputData=Data {}}
                                      2024-11-14 18:24:17.127 I [MQTT Call: iobroker] MessageProcessor: Received incoming message: MessageCard on owntracks/iobroker/Marco/info with id=xyz
                                      2024-11-14 18:24:17.130 I [MQTT Call: iobroker] MessageProcessor: Received incoming message: MessageCard on owntracks/iobroker/Melli/info with id=xyz
                                      2024-11-14 19:27:42.963 E [MQTT Rec: iobroker] MQTTMessageProcessorEndpoint$mqttCallback: Connection Lost
                                      Verbindung wurde getrennt (32109) - java.net.SocketException: Connection reset
                                      	at org.eclipse.paho.client.mqttv3.internal.CommsSender.run(SourceFile:261)
                                      	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:487)
                                      	at java.util.concurrent.FutureTask.run(FutureTask.java:264)
                                      	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:307)
                                      	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
                                      	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:644)
                                      	at java.lang.Thread.run(Thread.java:1012)
                                      Caused by: java.net.SocketException: Connection reset
                                      	at java.net.SocketInputStream.read(SocketInputStream.java:191)
                                      	at java.net.SocketInputStream.read(SocketInputStream.java:143)
                                      	at java.net.SocketInputStream.read(SocketInputStream.java:205)
                                      	at java.io.DataInputStream.readByte(DataInputStream.java:273)
                                      	at org.eclipse.paho.client.mqttv3.internal.wire.MqttInputStream.readMqttWireMessage(SourceFile:14)
                                      	at org.eclipse.paho.client.mqttv3.internal.CommsSender.run(SourceFile:88)
                                      	... 6 more
                                      
                                      2024-11-14 19:29:18.016 I [DefaultDispatcher-worker-3] MQTTReconnectWorker: MQTT reconnect worker job started
                                      2024-11-14 19:29:18.038 I [DefaultDispatcher-worker-3] MQTTMessageProcessorEndpoint$connectToBroker: Connecting to tcp://mqttowntracks.ddns.net:1886?# timeout = 30s
                                      2024-11-14 19:29:18.544 I [DefaultDispatcher-worker-3] MQTTMessageProcessorEndpoint$connectToBroker: MQTT Connected. Subscribing to [owntracks/+/+, owntracks/+/+/event, owntracks/+/+/info, owntracks/+/+/status, owntracks/iobroker/Marco/cmd]
                                      2024-11-14 19:29:18.552 I [DefaultDispatcher-worker-3] MQTTMessageProcessorEndpoint$connectToBroker: MQTT Subscribed
                                      2024-11-14 19:29:18.555 I [DefaultDispatcher-worker-3] MQTTReconnectWorker: MQTT reconnect worker job completed, status Success {mOutputData=Data {}}
                                      2024-11-14 19:29:18.782 I [MQTT Call: iobroker] MessageProcessor: Received incoming message: MessageCard on owntracks/iobroker/Marco/info with id=xyz
                                      2024-11-14 19:29:18.797 I [MQTT Call: iobroker] MessageProcessor: Received incoming message: MessageCard on owntracks/iobroker/Melli/info with id=xyz
                                      2024-11-14 19:34:47.810 W [main] MapFragment: unable to update marker for Contact owntracks/iobroker/Marco (Marco). no location
                                      2024-11-14 19:34:47.810 W [main] MapFragment: unable to update marker for Contact owntracks/iobroker/Melli (Melli). no location
                                      2024-11-14 19:34:47.872 W [main] MapFragment: unable to update marker for Contact owntracks/iobroker/Marco (Marco). no location
                                      2024-11-14 19:34:47.872 W [main] MapFragment: unable to update marker for Contact owntracks/iobroker/Melli (Melli). no location
                                      2024-11-14 19:34:49.031 I [DefaultDispatcher-worker-8] MQTTMessageProcessorEndpoint: Sending message [MessageStatus android=org.owntracks.android.model.messages.AddMessageStatus@xyz]
                                      2024-11-14 19:34:49.033 I [DefaultDispatcher-worker-5] MQTTMessageProcessorEndpoint$sendMessage$2$1$job: Message [MessageStatus android=org.owntracks.android.model.messages.AddMessageStatus@xyz] dispatched in 2.055834ms
                                      2024-11-14 19:34:49.067 I [MQTT Call: iobroker] MessageProcessor: Received incoming message: MessageStatus on owntracks/iobroker/Marco/status with id=xyz
                                      2024-11-14 19:34:50.207 I [DefaultDispatcher-worker-8] MQTTMessageProcessorEndpoint: Sending message [MessageStatus android=org.owntracks.android.model.messages.AddMessageStatus@xyz]
                                      2024-11-14 19:34:50.210 I [DefaultDispatcher-worker-5] MQTTMessageProcessorEndpoint$sendMessage$2$1$job: Message [MessageStatus android=org.owntracks.android.model.messages.AddMessageStatus@xyz] dispatched in 710.052us
                                      2024-11-14 19:34:50.234 I [MQTT Call: iobroker] MessageProcessor: Received incoming message: MessageStatus on owntracks/iobroker/Marco/status with id=xyz
                                      
                                      Ro75R Online
                                      Ro75R Online
                                      Ro75
                                      schrieb am zuletzt editiert von Ro75
                                      #51

                                      @rebel85 als Port 1886? Im Adapter steht 1884, in der App 1886 und welchen Port schleifst du in der Fritzbox durch? So klappt das nicht.

                                      Ro75

                                      SERVER = Beelink U59 16GB DDR4 RAM 512GB SSD, FB 7490, FritzDect 200+301+440, ConBee II, Zigbee Aqara Sensoren + NOUS A1Z, NOUS A1T, Philips Hue ** ioBroker, REDIS, influxdb2, Grafana, PiHole, Plex-Mediaserver, paperless-ngx (Docker), MariaDB + phpmyadmin *** VIS-Runtime = Intel NUC 8GB RAM 128GB SSD + 24" Touchscreen

                                      R 1 Antwort Letzte Antwort
                                      0
                                      • Ro75R Ro75

                                        @rebel85 als Port 1886? Im Adapter steht 1884, in der App 1886 und welchen Port schleifst du in der Fritzbox durch? So klappt das nicht.

                                        Ro75

                                        R Offline
                                        R Offline
                                        rebel85
                                        schrieb am zuletzt editiert von
                                        #52

                                        @ro75 Moin, doch so klappt das, weil im Adapter und in der Fritzbox auch der Selbe Port freigegeben ist. nur leider die App oder irgendwas noch den weg versperrt. hatte doch gesagt das ich die Ports mal gewechselt habe, es dann zu der ecovacs meldung kahm und dann habe ich den nächsten genommen.
                                        aktuell alle ports 1886...
                                        brauchst du dazu auch Bilder?

                                        Ro75R 1 Antwort Letzte Antwort
                                        0
                                        • R rebel85

                                          @ro75 Moin, doch so klappt das, weil im Adapter und in der Fritzbox auch der Selbe Port freigegeben ist. nur leider die App oder irgendwas noch den weg versperrt. hatte doch gesagt das ich die Ports mal gewechselt habe, es dann zu der ecovacs meldung kahm und dann habe ich den nächsten genommen.
                                          aktuell alle ports 1886...
                                          brauchst du dazu auch Bilder?

                                          Ro75R Online
                                          Ro75R Online
                                          Ro75
                                          schrieb am zuletzt editiert von
                                          #53

                                          @rebel85 nein, keine Bilder. Nur der Port darf dann nicht von mehreren Adaptern genutzt werden. Laut Log klappt mit dem Port 1886 etwas nicht.

                                          Ro75.

                                          SERVER = Beelink U59 16GB DDR4 RAM 512GB SSD, FB 7490, FritzDect 200+301+440, ConBee II, Zigbee Aqara Sensoren + NOUS A1Z, NOUS A1T, Philips Hue ** ioBroker, REDIS, influxdb2, Grafana, PiHole, Plex-Mediaserver, paperless-ngx (Docker), MariaDB + phpmyadmin *** VIS-Runtime = Intel NUC 8GB RAM 128GB SSD + 24" Touchscreen

                                          R 1 Antwort Letzte Antwort
                                          0
                                          Antworten
                                          • In einem neuen Thema antworten
                                          Anmelden zum Antworten
                                          • Älteste zuerst
                                          • Neuste zuerst
                                          • Meiste Stimmen


                                          Support us

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

                                          847

                                          Online

                                          32.5k

                                          Benutzer

                                          81.8k

                                          Themen

                                          1.3m

                                          Beiträge
                                          Community
                                          Impressum | Datenschutz-Bestimmungen | Nutzungsbedingungen | Einwilligungseinstellungen
                                          ioBroker Community 2014-2025
                                          logo
                                          • Anmelden

                                          • Du hast noch kein Konto? Registrieren

                                          • Anmelden oder registrieren, um zu suchen
                                          • Erster Beitrag
                                            Letzter Beitrag
                                          0
                                          • Home
                                          • Aktuell
                                          • Tags
                                          • Ungelesen 0
                                          • Kategorien
                                          • Unreplied
                                          • Beliebt
                                          • GitHub
                                          • Docu
                                          • Hilfe