openhabforum.de


https://openhabforum.de/

MQTT nicht erreichbar?

https://openhabforum.de/viewtopic.php?t=4115

Seite 1 von 1

MQTT nicht erreichbar?

Verfasst: 9. Okt 2020 12:17
von MagicBird
Hallo Forum,

ich habe regelmäßig das Problem meinen MQTT Server nicht zu erreichen.

System Raspberry PI3 mit Buster darauf habe ich dann openhab installiert (openHAB 2.5.7 Release Build)

Code: Alles auswählen

00:00:00 Projekt sonoff wohnzimmer_vitrine Version 6.4.1(sonoff)-2_4_2
00:00:00 WIF: verbinden mit AP1 Mit Sicherheit Fort Knox in Modus 11N wie wohnzimmer_vitrine-4232...
00:00:08 WIF: verbunden
00:00:08 DNS: initialisiert
00:00:08 HTP: Web-Server aktiv bei wohnzimmer_vitrine-4232.local mit IP-Adresse 192.168.5.110
12:06:30 MQT: Verbindungsversuch...
12:06:30 MQT: verbunden
12:06:30 MQT: tele/wohnzimmer_vitrine/LWT = Online (beibehalten)
12:06:30 MQT: cmnd/wohnzimmer_vitrine/POWER = 
12:06:30 MQT: tele/wohnzimmer_vitrine/INFO1 = {"Module":"Sonoff Basic","Version":"6.4.1(sonoff)","FallbackTopic":"cmnd/wohnzimmer_vitrine_fb/","GroupTopic":"sonoffs"}
12:06:30 MQT: tele/wohnzimmer_vitrine/INFO2 = {"WebServerMode":"Admin","Hostname":"wohnzimmer_vitrine-4232","IPAddress":"192.168.5.110"}
12:06:30 RSL: tele/wohnzimmer_vitrine/INFO3 = {"RestartReason":"Software/System restart"}
12:06:30 RSL: stat/wohnzimmer_vitrine/RESULT = {"POWER":"OFF"}
12:06:30 RSL: stat/wohnzimmer_vitrine/POWER = OFF
12:06:31 MQT: Verbindungsversuch...
12:06:31 MQT: verbunden
12:06:31 MQT: tele/wohnzimmer_vitrine/LWT = Online (beibehalten)
12:06:31 MQT: cmnd/wohnzimmer_vitrine/POWER = 
12:06:32 MQT: Verbindungsversuch...
12:06:32 MQT: verbunden
12:06:32 MQT: tele/wohnzimmer_vitrine/LWT = Online (beibehalten)
12:06:32 MQT: cmnd/wohnzimmer_vitrine/POWER = 
12:06:33 MQT: Verbindungsversuch...
12:06:33 MQT: verbunden
12:06:33 MQT: tele/wohnzimmer_vitrine/LWT = Online (beibehalten)
12:06:33 MQT: cmnd/wohnzimmer_vitrine/POWER = 
12:06:34 MQT: Verbindungsversuch...
12:06:34 MQT: verbunden
12:06:34 MQT: tele/wohnzimmer_vitrine/LWT = Online (beibehalten)
12:06:34 MQT: cmnd/wohnzimmer_vitrine/POWER = 







00:00:00 CFG: Loaded from flash at F7, Count 517
00:00:00 Project tasmota wohnzimmer_stehlampe Version 8.3.1(tasmota)-2_7_1
00:00:00 WIF: Connecting to AP1 Mit Sicherheit Fort Knox Channel 8 BSSId 58:D7:59:B2:9D:E7 in mode 11N as wohnzimmer_stehlampe-4147...
00:00:01 WIF: Connected
00:00:01 HTP: Web server active on wohnzimmer_stehlampe-4147 with IP address 192.168.5.112
12:07:33 MQT: Attempting connection...
12:07:33 MQT: Connected
12:07:33 MQT: tele/wohnzimmer_stehlampe/LWT = Online (retained)
12:07:33 MQT: cmnd/wohnzimmer_stehlampe/POWER = 
12:07:33 MQT: tele/wohnzimmer_stehlampe/INFO1 = {"Module":"Generic","Version":"8.3.1(tasmota)","FallbackTopic":"cmnd/wohnzimmer_stehlampe_fb/","GroupTopic":"cmnd/tasmotas/"}
12:07:33 MQT: tele/wohnzimmer_stehlampe/INFO2 = {"WebServerMode":"Admin","Hostname":"wohnzimmer_stehlampe-4147","IPAddress":"192.168.5.112"}
12:07:33 MQT: tele/wohnzimmer_stehlampe/INFO3 = {"RestartReason":"Software/System restart"}
12:07:33 RSL: stat/wohnzimmer_stehlampe/RESULT = {"POWER":"OFF"}
12:07:33 RSL: stat/wohnzimmer_stehlampe/POWER = OFF
12:07:34 MQT: Attempting connection...
12:07:34 MQT: Connected
12:07:34 MQT: tele/wohnzimmer_stehlampe/LWT = Online (retained)
12:07:34 MQT: cmnd/wohnzimmer_stehlampe/POWER = 
12:07:35 MQT: Attempting connection...
12:07:35 MQT: Connected
12:07:35 MQT: tele/wohnzimmer_stehlampe/LWT = Online (retained)
12:07:35 MQT: cmnd/wohnzimmer_stehlampe/POWER = 
12:07:36 MQT: Attempting connection...
12:07:36 MQT: Connected
12:07:36 MQT: tele/wohnzimmer_stehlampe/LWT = Online (retained)
12:07:36 MQT: cmnd/wohnzimmer_stehlampe/POWER = 
12:07:37 MQT: Attempting connection...
12:07:37 MQT: Connected
12:07:37 MQT: tele/wohnzimmer_stehlampe/LWT = Online (retained)
12:07:37 MQT: cmnd/wohnzimmer_stehlampe/POWER =
Nun habe ich den ganzen PI durch reboot neu gestartet.

Habt ihr eine Idee für das Problem. Danke Lars

Re: MQTT nicht erreichbar?

Verfasst: 9. Okt 2020 17:03
von udo1toni
Frage 1: Wo befindet sich der Broker?
Frage 2: Welcher Broker?
Frage 3: Da das Protokoll von einem Tasmota Device stammt: Hast Du noch andere MQTT Nodes? Falls ja: Haben die die gleichen Probleme? Hast Du Dir mal das WLAN angeschaut?

Re: MQTT nicht erreichbar?

Verfasst: 9. Okt 2020 22:53
von MagicBird
MQTT Broker - mqtt:systemBroker:embedded-mqtt-broker
MQTT Broker - mqtt:broker:mqttbroker

Wo befindet sich der Broker? Auf dem PI wo Buster und Openhab installiert ist.

Das Protokoll sind 2 Geräte.
Mein WLAN ist Top. 2 Access Point's in der Wohnung verteilt.

Lars

Re: MQTT nicht erreichbar?

Verfasst: 9. Okt 2020 23:13
von udo1toni
Moquette (das ist der embedded Broker) ist nicht zu empfehlen. Zum Einen gibt es keine aktive Weiterentwicklung und etliche bekannte Probleme, zum Anderen ist der Funktionsumfang recht eingeschränkt.
Falls Du openHABian zum Aufsetzen verwendet hast, kannst Du (nachdem Du Moquette deinstalliert hast) Mosquitto über openhabian-config installieren.
Solltest Du nicht über openHABian installiert haben, kannst Du mittels apt install mosquitto einfach die Repository Version installieren.

Es ist nicht zwingend notwendig, Mosquitto zu konfigurieren, dann verhält es sich wie Moquette, also ohne User und Passwort.

Re: MQTT nicht erreichbar?

Verfasst: 11. Okt 2020 12:44
von MagicBird
Hallo Udo,

Interessant, ja ich verwende Buster und habe dort einfach OH2 und co drauf gepackt. Genau , in der PaperUI unter Bindings und MQTT Broker steht Mosquette.
Nun wollte ich das Installieren und es kam zu einem Fehler.

Code: Alles auswählen

pi@openhab:~ $ sudo apt install mosquitto -y
Paketlisten werden gelesen... Fertig
Abhängigkeitsbaum wird aufgebaut.
Statusinformationen werden eingelesen.... Fertig
mosquitto ist schon die neueste Version (1.5.7-1+deb10u1).
Das folgende Paket wurde automatisch installiert und wird nicht mehr benötigt:
  rpi-eeprom-images
Verwenden Sie »sudo apt autoremove«, um es zu entfernen.
0 aktualisiert, 0 neu installiert, 0 zu entfernen und 0 nicht aktualisiert.
1 nicht vollständig installiert oder entfernt.
Nach dieser Operation werden 0 B Plattenplatz zusätzlich benutzt.
mosquitto (1.5.7-1+deb10u1) wird eingerichtet ...
Job for mosquitto.service failed because the control process exited with error code.
See "systemctl status mosquitto.service" and "journalctl -xe" for details.
invoke-rc.d: initscript mosquitto, action "start" failed.
● mosquitto.service - Mosquitto MQTT v3.1/v3.1.1 Broker
   Loaded: loaded (/lib/systemd/system/mosquitto.service; disabled; vendor preset: enabled)
   Active: activating (auto-restart) (Result: exit-code) since Sun 2020-10-11 12:27:07 CEST; 61ms ago
     Docs: man:mosquitto.conf(5)
           man:mosquitto(8)
  Process: 19401 ExecStart=/usr/sbin/mosquitto -c /etc/mosquitto/mosquitto.conf (code=exited, status=1/FAILURE)
 Main PID: 19401 (code=exited, status=1/FAILURE)
dpkg: Fehler beim Bearbeiten des Paketes mosquitto (--configure):
 »installiertes mosquitto-Skript des Paketes post-installation«-Unterprozess gab den Fehlerwert 1 zurück
Fehler traten auf beim Bearbeiten von:
 mosquitto
E: Sub-process /usr/bin/dpkg returned an error code (1)
pi@openhab:~ $

pi@openhab:~ $ systemctl status mosquitto.service
● mosquitto.service - Mosquitto MQTT v3.1/v3.1.1 Broker
   Loaded: loaded (/lib/systemd/system/mosquitto.service; disabled; vendor preset: enabled)
   Active: failed (Result: exit-code) since Sun 2020-10-11 12:27:55 CEST; 1min 38s ago
     Docs: man:mosquitto.conf(5)
           man:mosquitto(8)
  Process: 19512 ExecStart=/usr/sbin/mosquitto -c /etc/mosquitto/mosquitto.conf (code=exited, status=1/FAILURE)
 Main PID: 19512 (code=exited, status=1/FAILURE)

Okt 11 12:27:55 openhab systemd[1]: mosquitto.service: Main process exited, code=exited, status=1/FAILURE
Okt 11 12:27:55 openhab systemd[1]: mosquitto.service: Failed with result 'exit-code'.
Okt 11 12:27:55 openhab systemd[1]: Failed to start Mosquitto MQTT v3.1/v3.1.1 Broker.
Okt 11 12:27:55 openhab systemd[1]: mosquitto.service: Service RestartSec=100ms expired, scheduling restart.
Okt 11 12:27:55 openhab systemd[1]: mosquitto.service: Scheduled restart job, restart counter is at 5.
Okt 11 12:27:55 openhab systemd[1]: Stopped Mosquitto MQTT v3.1/v3.1.1 Broker.
Okt 11 12:27:55 openhab systemd[1]: mosquitto.service: Start request repeated too quickly.
Okt 11 12:27:55 openhab systemd[1]: mosquitto.service: Failed with result 'exit-code'.
Okt 11 12:27:55 openhab systemd[1]: Failed to start Mosquitto MQTT v3.1/v3.1.1 Broker.
pi@openhab:~ $

pi@openhab:~ $ journalctl -xe
-- Support: https://www.debian.org/support
--
-- The unit mosquitto.service has entered the 'failed' state with result 'exit-code'.
Okt 11 12:27:55 openhab systemd[1]: Failed to start Mosquitto MQTT v3.1/v3.1.1 Broker.
-- Subject: A start job for unit mosquitto.service has failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A start job for unit mosquitto.service has finished with a failure.
--
-- The job identifier is 3560 and the job result is failed.
Okt 11 12:27:55 openhab sudo[19435]: pam_unix(sudo:session): session closed for user root
Okt 11 12:27:55 openhab systemd[1]: mosquitto.service: Service RestartSec=100ms expired, scheduling restart.
Okt 11 12:27:55 openhab systemd[1]: mosquitto.service: Scheduled restart job, restart counter is at 5.
-- Subject: Automatic restarting of a unit has been scheduled
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- Automatic restarting of the unit mosquitto.service has been scheduled, as the result for
-- the configured Restart= setting for the unit.
Okt 11 12:27:55 openhab systemd[1]: Stopped Mosquitto MQTT v3.1/v3.1.1 Broker.
-- Subject: A stop job for unit mosquitto.service has finished
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A stop job for unit mosquitto.service has finished.
--
-- The job identifier is 3625 and the job result is done.
Okt 11 12:27:55 openhab systemd[1]: mosquitto.service: Start request repeated too quickly.
Okt 11 12:27:55 openhab systemd[1]: mosquitto.service: Failed with result 'exit-code'.
-- Subject: Unit failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- The unit mosquitto.service has entered the 'failed' state with result 'exit-code'.
Okt 11 12:27:55 openhab systemd[1]: Failed to start Mosquitto MQTT v3.1/v3.1.1 Broker.
-- Subject: A start job for unit mosquitto.service has failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A start job for unit mosquitto.service has finished with a failure.
--
-- The job identifier is 3625 and the job result is failed.
Okt 11 12:27:58 openhab kernel: Voltage normalised (0x00000000)
Okt 11 12:30:19 openhab kernel: Under-voltage detected! (0x00050005)
lines 2229-2273/2273 (END)
Mit mosquitto_sub -v -h 192.168.5.100 -p 1883 -t '#' kommt auch nichts, also ist der Broker irgendwie schonwieder Tod.
Dennoch senden die Dosen mit Erfolg.

Code: Alles auswählen

12:29:13 MQT: tele/kuechen_wlandose/STATE = {"Time":"2020-10-11T12:29:13","Uptime":"40T03:29:48","UptimeSec":3468588,"Heap":26,"SleepMode":"Dynamic","Sleep":50,"LoadAvg":19,"MqttCount":48711,"POWER":"ON","Wifi":{"AP":1,"SSId":"Mit Sicherheit Fort Knox","BSSId":"58:D7:59:B2:9D:E7","Channel":8,"RSSI":64,"Signal":-68,"LinkCount":6,"Downtime":"0T00:01:04"}}
12:34:13 MQT: tele/kuechen_wlandose/STATE = {"Time":"2020-10-11T12:34:13","Uptime":"40T03:34:48","UptimeSec":3468888,"Heap":26,"SleepMode":"Dynamic","Sleep":50,"LoadAvg":24,"MqttCount":48711,"POWER":"ON","Wifi":{"AP":1,"SSId":"Mit Sicherheit Fort Knox","BSSId":"58:D7:59:B2:9D:E7","Channel":8,"RSSI":62,"Signal":-69,"LinkCount":6,"Downtime":"0T00:01:04"}}
12:39:13 MQT: tele/kuechen_wlandose/STATE = {"Time":"2020-10-11T12:39:13","Uptime":"40T03:39:48","UptimeSec":3469188,"Heap":26,"SleepMode":"Dynamic","Sleep":50,"LoadAvg":19,"MqttCount":48711,"POWER":"ON","Wifi":{"AP":1,"SSId":"Mit Sicherheit Fort Knox","BSSId":"58:D7:59:B2:9D:E7","Channel":8,"RSSI":66,"Signal":-67,"LinkCount":6,"Downtime":"0T00:01:04"}}
So nun mal schauen wie ich Mosquitto drauf bekomme.

Danke Lars

Re: MQTT nicht erreichbar?

Verfasst: 11. Okt 2020 13:29
von MagicBird
Nun habe ich gelesen das ein Update Upgrade helfen könnte und habe entsprechend dieses ausgeführt.

Jetzt scheint erstmal wieder alles zu laufen.

Code: Alles auswählen

pi@triggerpi:~ $ mosquitto_sub -v -h 192.168.5.100 -p 1883 -t '#'
tele/kuechen_wlandose/LWT Online
tele/lennox_licht2/LWT Online
tele/schlafzimmer_tv/LWT Online
tele/colin_licht1/LWT Online
tele/bad_wlandose/LWT Online
tele/wohnzimmer_vitrine/LWT Online
tele/lennox_licht1/LWT Online
tele/balkon_wlandose/LWT Online
tele/wohnzimmer_stehlampe/LWT Online
tele/wohnzimmer_stehlampe/STATE {"Time":"2020-10-11T13:27:51","Uptime":"2T01:20:23","UptimeSec":177623,"Heap":27,"SleepMode":"Dynamic","Sleep":50,"LoadAvg":19,"MqttCount":127,"POWER":"OFF","Wifi":{"AP":1,"SSId":"Mit Sicherheit Fort Knox","BSSId":"58:D7:59:B2:9D:E7","Channel":8,"RSSI":100,"Signal":-48,"LinkCount":1,"Downtime":"0T00:00:03"}}
tele/schlafzimmer_tv/STATE {"Time":"2020-10-11T13:28:00","Uptime":"0T21:40:41","UptimeSec":78041,"Heap":27,"SleepMode":"Dynamic","Sleep":50,"LoadAvg":19,"MqttCount":10160,"POWER":"ON","Wifi":{"AP":1,"SSId":"Mit Sicherheit Fort Knox","BSSId":"48:EE:0C:64:6A:68","Channel":11,"RSSI":76,"Signal":-62,"LinkCount":1,"Downtime":"0T00:00:03"}}
tele/bad_wlandose/STATE {"Time":"2020-10-11T13:28:22","Uptime":"23T19:26:17","UptimeSec":2057177,"Heap":27,"SleepMode":"Dynamic","Sleep":50,"LoadAvg":19,"MqttCount":48753,"POWER":"OFF","Wifi":{"AP":1,"SSId":"Mit Sicherheit Fort Knox","BSSId":"58:D7:59:B2:9D:E7","Channel":8,"RSSI":74,"Signal":-63,"LinkCount":1,"Downtime":"0T00:00:09"}}
tele/bad_wlandose/SENSOR {"Time":"2020-10-11T13:28:22","AM2301":{"Temperature":24.0,"Humidity":74.3,"DewPoint":19.1},"TempUnit":"C"}
tele/lennox_licht2/STATE {"Time":"2020-10-11T13:28:43","Uptime":"17T01:55:59","UptimeSec":1475759,"Heap":26,"SleepMode":"Dynamic","Sleep":50,"LoadAvg":19,"MqttCount":11,"POWER":"OFF","Wifi":{"AP":1,"SSId":"Mit Sicherheit Fort Knox","BSSId":"48:EE:0C:64:6A:68","Channel":11,"RSSI":82,"Signal":-59,"LinkCount":2,"Downtime":"0T00:00:25"}}
Lars
Alle Zeiten sind UTC+02:00
Seite 1 von 1

Powered by phpBB® Forum Software © phpBB Limited

Deutsche Übersetzung durch phpBB.de