Verschiedene Homebridge Probleme
-
-
Also bei mir ist immer noch der Wurm drin und weiß nicht warum...
Die Homebridge stürzt ständig ab...
In config-ui-x seh ich das ja und wenn ich syslog auslese kommt nur das...
tail -f /var/log/syslog
Oct 31 16:39:00 hbridge2 systemd[10203]: Listening on GnuPG cryptographic agent (ssh-agent emulation).
Oct 31 16:39:00 hbridge2 systemd[10203]: Listening on GnuPG cryptographic agent (access for web browsers).
Oct 31 16:39:00 hbridge2 systemd[10203]: Listening on GnuPG cryptographic agent and passphrase cache (restricted).
Oct 31 16:39:00 hbridge2 systemd[10203]: Reached target Paths.
Oct 31 16:39:00 hbridge2 systemd[10203]: Listening on GnuPG cryptographic agent and passphrase cache.
Oct 31 16:39:00 hbridge2 systemd[10203]: Reached target Sockets.
Oct 31 16:39:00 hbridge2 systemd[10203]: Reached target Basic System.
Oct 31 16:39:00 hbridge2 systemd[10203]: Reached target Default.
Oct 31 16:39:00 hbridge2 systemd[10203]: Startup finished in 40ms.
Oct 31 16:39:00 hbridge2 systemd[1]: Started User Manager for UID 1000.
Hat jemand eine Idee?
Mit freundlichen Grüßen
Das log ist zu kurz, da isr ja nix zu sehen
Hallo zusammen,
kann mir jemand sagen warum mein mosquito service nicht mehr ausgeführt wird?
pi@raspberrypi:~ $ sudo systemctl status mosquitto.service
? mosquitto.service - Mosquitto MQTT Broker daemon
Loaded: loaded (/etc/systemd/system/mosquitto.service; enabled)
Active: activating (auto-restart) (Result: exit-code) since Thu 2018-11-01 11:31:13 CET; 649ms ago
Process: 8903 ExecStart=/usr/local/sbin/mosquitto -c /usr/local/etc/mosquitto/mosquitto.conf -d (code=exited, status=203/EXEC)
Nov 01 11:31:13 raspberrypi systemd[1]: Failed to start Mosquitto MQTT Broker daemon.
Nov 01 11:31:13 raspberrypi systemd[1]: Unit mosquitto.service entered failed state.
Warning: Unit file changed on disk, 'systemctl daemon-reload' recommended.
Hier noch die Config von meinem Service:
[Unit]
Description=Mosquitto MQTT Broker daemon
After=network.target
Requires=network.target
[Service]
Type=forking
RemainAfterExit=no
StartLimitInterval=0
PIDFile=/var/run/mosquitto.pid
# Note: The following paths may be different on your system.
ExecStart=/usr/local/sbin/sudo mosquitto -c /usr/local/etc/mosquitto/mosquitto.conf -d
ExecReload=/bin/kill -HUP $MAINPID
Restart=on-failure
RestartSec=2
[Install]
WantedBy=multi-user.target
mit diesem Befehl kann ich manuell starten
sudo mosquitto -v
ExecStart=/usr/local/sbin/sudo mosquitto -c /usr/local/etc/mosquitto/mosquitto.conf -d
Nö, so nicht. Es heißt
Das sudo muss raus, und es hätte an der Stelle eh nix zu suchen gehabt. Wenn schon: sudo /usr/local/sbin/mosquitto -c /usr/local/etc/mosquitto/mosquitto.conf -d. Aber du brauchst das sudo eh nicht, weil du den Service startest mit sudo systemctl start mosquitto.
Wenn du die Änderung vorgenommen hast, musst du sie noch dem systemd bekanntgeben mit
sudo systemctl daemon-reload und dann
sudo systemctl restart mosquitto
Mich wundert der Pfad /usr/local/sbin/mosquitto. Falls du weiterhin Probleme hast, stelle bitte fest, wo mosquitto liegt mit dem Befehl
which mosquitto
und passe deine mosquitto.service dementsprechend an.
Stefan
Nö, so nicht. Es heißt
Das sudo muss raus, und es hätte an der Stelle eh nix zu suchen gehabt. Wenn schon: sudo /usr/local/sbin/mosquitto -c /usr/local/etc/mosquitto/mosquitto.conf -d. Aber du brauchst das sudo eh nicht, weil du den Service startest mit sudo systemctl start mosquitto.
Wenn du die Änderung vorgenommen hast, musst du sie noch dem systemd bekanntgeben mit
sudo systemctl daemon-reload und dann
sudo systemctl restart mosquitto
Mich wundert der Pfad /usr/local/sbin/mosquitto. Falls du weiterhin Probleme hast, stelle bitte fest, wo mosquitto liegt mit dem Befehl
which mosquitto
und passe deine mosquitto.service dementsprechend an.
Stefan
Hi Stefan,
vielen Dank für Deine schnelle Antwort.
Das sudo habe ich mal eingefügt weil ich es besser nicht wusste.
Problem liegt beim Pfad.
mosquito liegt hier:
/usr/sbin/mosquitto
Ist dieser Befehl dann richtig? was führt mosquitto.conf aus?
ExecStart=/usr/sbin/mosquitto/mosquitto -c /usr/local/etc/mosquitto/mosquitto.conf -d
Danke vorab.
Nikolai
Etwas stimmt an meiner Anpassung immer noch nicht:
? mosquitto.service - Mosquitto MQTT Broker daemon
Loaded: loaded (/etc/systemd/system/mosquitto.service; enabled)
Active: activating (auto-restart) (Result: exit-code) since Thu 2018-11-01 14:40:06 CET; 1s ago
Process: 25189 ExecStart=/usr/sbin/mosquitto -c /etc/mosquitto/mosquitto.conf -d (code=exited, status=3)
Nov 01 14:40:06 raspberrypi mosquitto[25189]: Error: Unable to open configuration file.
Nov 01 14:40:06 raspberrypi systemd[1]: mosquitto.service: control process exited, code=exited status=3
Nov 01 14:40:06 raspberrypi systemd[1]: Failed to start Mosquitto MQTT Broker daemon.
Nov 01 14:40:06 raspberrypi systemd[1]: Unit mosquitto.service entered failed state.
ich würde denken, er kann
/etc/mosquitto/mosquitto.conf nicht lesen.
ich würde denken, er kann
/etc/mosquitto/mosquitto.conf nicht lesen.
? mosquitto.service - Mosquitto MQTT Broker daemon
Loaded: loaded (/etc/systemd/system/mosquitto.service; enabled)
Active: activating (auto-restart) (Result: exit-code) since Thu 2018-11-01 15:19:22 CET; 64ms ago
Process: 28875 ExecStart=/usr/sbin/mosquitto -c (code=exited, status=3)
Nov 01 15:19:22 raspberrypi systemd[1]: Failed to start Mosquitto MQTT Broker daemon.
Nov 01 15:19:22 raspberrypi systemd[1]: Unit mosquitto.service entered failed state.
Das log ist zu kurz, da isr ja nix zu sehen
Ja das ist es ja...
Er zeigt ja auch nicht mehr an. Das ist das kuriose dabei...
Und was soll ich sagen. Die Homebridge läuft wieder nicht. Ist wieder abgeschmiert.
Könnte echt Kotzen...
PS: was bedeutet das den hier?
[2018-11-1 16:05:29] [Config] You are using a depreciated log config format, please update your config.json to use this new format:
[2018-11-1 16:05:29] [Config] {"method":"systemd","service":"homebridge"}
? mosquitto.service - Mosquitto MQTT Broker daemon
Loaded: loaded (/etc/systemd/system/mosquitto.service; enabled)
Active: activating (auto-restart) (Result: exit-code) since Thu 2018-11-01 15:19:22 CET; 64ms ago
Process: 28875 ExecStart=/usr/sbin/mosquitto -c (code=exited, status=3)
Nov 01 15:19:22 raspberrypi systemd[1]: Failed to start Mosquitto MQTT Broker daemon.
Nov 01 15:19:22 raspberrypi systemd[1]: Unit mosquitto.service entered failed state.
so jetzt läuft es wieder...
? mosquitto.service - Mosquitto MQTT Broker daemon
Loaded: loaded (/etc/systemd/system/mosquitto.service; enabled)
Active: activating (start) since Thu 2018-11-01 16:04:55 CET; 1min 36s ago
Control: 516 (mosquitto)
CGroup: /system.slice/mosquitto.service
??516 /usr/sbin/mosquitto -v
Ist dieser Befehl dann richtig? was führt mosquitto.conf aus?
ExecStart=/usr/sbin/mosquitto/mosquitto -c /usr/local/etc/mosquitto/mosquitto.conf -d
Nichts führt mosquitto.conf aus. Das ist eine unausführbare Konfigurationsdatei. Mosquitto lädt sie während seines Starts.
which mosquitto hat also /usr/sbin/mosquitto ergeben. Dann schreib das auch so in deine mosquitto.service, bei dir steht nämlich mosquitto doppelt da.
Wo kommt diese Konfigurationsdatei /usr/local/etc/mosquitto/mosquitto.conf her? Was passiert wenn du
sudo /usr/sbin/mosquitto -c /usr/local/etc/mosquitto/mosquitto.conf -d
auf der Shell eingibst?
Stefan
Wo kommt diese Konfigurationsdatei /usr/local/etc/mosquitto/mosquitto.conf her? Was passiert wenn du
sudo /usr/sbin/mosquitto -c /usr/local/etc/mosquitto/mosquitto.conf -d
auf der Shell eingibst?
Stefan
Datei stammt aus dieser Anleitung: [Anleitung] Sonoff RF + Funkschalter in HomeKit
Shelleingabe:
pi@raspberrypi:~ $ sudo /usr/sbin/mosquitto -c /usr/local/etc/mosquitto/mosquitto.conf -d
Error: Unable to open config file /usr/local/etc/mosquitto/mosquitto.conf
Error found at /usr/local/etc/mosquitto/mosquitto.conf:0.
Error: Unable to open configuration file.
Kann ich auch löschen? /usr/local/etc/mosquitto/mosquitto.conf
Danke & Gruß
noch eine Frage hätte ich...
Wieso connected er nicht beim ersten Anlauf?
Nov 01 21:08:44 raspberrypi homebridge[581]: [11/1/2018, 9:08:44 PM] [MQTT Bridge] on.offline <to analyze>
Nov 01 21:08:44 raspberrypi homebridge[581]: [11/1/2018, 9:08:44 PM] [MQTT Bridge] on.close <to analyze>
Nov 01 21:08:45 raspberrypi homebridge[581]: [11/1/2018, 9:08:45 PM] [MQTT Bridge] on.reconnect <to analyze>
Nov 01 21:08:45 raspberrypi homebridge[581]: [11/1/2018, 9:08:45 PM] [MQTT Bridge] on.close <to analyze>
Nov 01 21:08:46 raspberrypi homebridge[581]: [11/1/2018, 9:08:46 PM] [MQTT Bridge] on.reconnect <to analyze>
Nov 01 21:08:46 raspberrypi homebridge[581]: [11/1/2018, 9:08:46 PM] [MQTT Bridge] on.close <to analyze>
Nov 01 21:08:47 raspberrypi homebridge[581]: [11/1/2018, 9:08:47 PM] [MQTT Bridge] on.reconnect <to analyze>
Nov 01 21:08:47 raspberrypi homebridge[581]: [11/1/2018, 9:08:47 PM] [MQTT Bridge] connected (url = mqtt://192.168.178.99)
Genau das selbe habe ich auch...
Hinzu kommt das meine HB einmal am Tag abstürzt und ich weis nicht warum...
Das habe ich im Daemon log gefunden:
Nov 1 16:04:42 hbridge2 homebridge[538]: Or enter this code with your HomeKit app on your iOS device to pair with Homebridge:
Nov 1 16:04:42 hbridge2 homebridge[538]:
Nov 1 16:04:42 hbridge2 homebridge[538]: ââââââââââââââ
Nov 1 16:04:42 hbridge2 homebridge[538]: â XXX-xx-XXX â
Nov 1 16:04:42 hbridge2 homebridge[538]: ââââââââââââââ
Nov 1 16:04:42 hbridge2 homebridge[538]:
Nov 1 16:04:42 hbridge2 homebridge[538]: [2018-11-1 16:04:42] Homebridge is running on port 12345.
Nov 1 16:04:48 hbridge2 homebridge[538]: [2018-11-1 16:04:48] [People] Changed occupancy state for Hariphone7 to true. Last successful ping 2018-11-01T16:04:48+01:00 , last webhook none .
Nov 1 16:05:27 hbridge2 systemd[1]: Created slice User Slice of pi.
Nov 1 16:05:27 hbridge2 systemd[1]: Starting User Manager for UID 1000...
Nov 1 16:05:27 hbridge2 systemd[1]: Started Session c1 of user pi.
Nov 1 16:05:27 hbridge2 systemd[1032]: Reached target Paths.
Nov 1 16:05:27 hbridge2 systemd[1032]: Listening on GnuPG cryptographic agent and passphrase cache.
Nov 1 16:05:27 hbridge2 systemd[1032]: Listening on GnuPG cryptographic agent (ssh-agent emulation).
Nov 1 16:05:27 hbridge2 systemd[1032]: Reached target Timers.
Nov 1 16:05:27 hbridge2 systemd[1032]: Listening on GnuPG cryptographic agent (access for web browsers).
Nov 1 16:05:27 hbridge2 systemd[1032]: Listening on GnuPG cryptographic agent and passphrase cache (restricted).
Nov 1 16:05:27 hbridge2 systemd[1032]: Reached target Sockets.
Nov 1 16:05:27 hbridge2 systemd[1032]: Reached target Basic System.
Nov 1 16:05:27 hbridge2 systemd[1032]: Reached target Default.
Nov 1 16:05:27 hbridge2 systemd[1032]: Startup finished in 59ms.
Nov 1 16:05:27 hbridge2 systemd[1]: Started User Manager for UID 1000.
Nov 1 16:05:29 hbridge2 homebridge[538]: #033[0;37m[2018-11-1 16:05:29]#033[0m #033[0;36m[Config]#033[0m #033[0;33mYou are using a depreciated log config format, please update your config.json to use this new format:#033[0m
Nov 1 16:05:29 hbridge2 homebridge[538]: #033[0;37m[2018-11-1 16:05:29]#033[0m #033[0;36m[Config]#033[0m #033[0;33m{"method":"systemd","service":"homebridge"}#033[0m
Nov 1 16:07:43 hbridge2 systemd[1]: Stopping User Manager for UID 1000...
Nov 1 16:07:43 hbridge2 systemd[1032]: Stopped target Default.
Nov 1 16:07:43 hbridge2 systemd[1032]: Stopped target Basic System.
Nov 1 16:07:43 hbridge2 systemd[1032]: Stopped target Timers.
Nov 1 16:07:43 hbridge2 systemd[1032]: Stopped target Sockets.
Nov 1 16:07:43 hbridge2 systemd[1032]: Closed GnuPG cryptographic agent and passphrase cache (restricted).
Nov 1 16:07:43 hbridge2 systemd[1032]: Closed GnuPG cryptographic agent (access for web browsers).
Nov 1 16:07:43 hbridge2 systemd[1032]: Closed GnuPG cryptographic agent (ssh-agent emulation).
Nov 1 16:07:43 hbridge2 systemd[1032]: Closed GnuPG cryptographic agent and passphrase cache.
Nov 1 16:07:43 hbridge2 systemd[1032]: Reached target Shutdown.
Nov 1 16:07:43 hbridge2 systemd[1032]: Starting Exit the Session...
Nov 1 16:07:43 hbridge2 systemd[1032]: Stopped target Paths.
Nov 1 16:07:43 hbridge2 systemd[1032]: Received SIGRTMIN+24 from PID 1123 (kill).
Nov 1 16:07:43 hbridge2 systemd[1]: Stopped User Manager for UID 1000.
Nov 1 16:07:43 hbridge2 systemd[1]: Removed slice User Slice of pi.
Nov 1 16:10:33 hbridge2 homebridge[538]: [2018-11-1 16:10:33] [hue] Drucker: set homekit status fault from 0 to 1
Nov 1 16:13:39 hbridge2 ntpd[567]: 212.227.158.163 local addr 192.168.2.76 -> <null>
Nov 1 16:14:40 hbridge2 ntpd[567]: 107.191.50.162 local addr 192.168.2.76 -> <null>
Nov 1 16:14:41 hbridge2 ntpd[567]: 119.28.206.193 local addr 192.168.2.76 -> <null>
Nov 1 16:15:39 hbridge2 homebridge[538]: [2018-11-1 16:15:39] [hue] Drucker: set homekit status fault from 1 to 0
Nov 1 16:15:44 hbridge2 ntpd[567]: 85.25.210.112 local addr 192.168.2.76 -> <null>
Nov 1 16:15:46 hbridge2 ntpd[567]: 185.207.104.70 local addr 192.168.2.76 -> <null>
Nov 1 16:15:48 hbridge2 ntpd[567]: 94.130.183.105 local addr 192.168.2.76 -> <null>
Nov 1 16:15:48 hbridge2 ntpd[567]: 80.241.208.120 local addr 192.168.2.76 -> <null>
Nov 1 16:15:50 hbridge2 ntpd[567]: 139.112.153.36 local addr 192.168.2.76 -> <null>
Nov 1 16:15:53 hbridge2 ntpd[567]: 185.194.140.199 local addr 192.168.2.76 -> <null>
Nov 1 16:15:54 hbridge2 ntpd[567]: 188.93.104.2 local addr 192.168.2.76 -> <null>
Nov 1 16:19:34 hbridge2 homebridge[538]: [2018-11-1 16:19:34] [hue] Drucker: set homekit status fault from 0 to 1
Nov 1 16:19:34 hbridge2 systemd[1]: Starting Cleanup of Temporary Directories...
Nov 1 16:19:34 hbridge2 systemd[1]: Started Cleanup of Temporary Directories.
Nov 1 16:21:24 hbridge2 ntpd[567]: 185.11.138.90 local addr 192.168.2.76 -> <null>
Nov 1 16:27:15 hbridge2 homebridge[538]: [2018-11-1 16:27:15] [hue] Drucker: set homekit status fault from 1 to 0
Nov 1 16:28:30 hbridge2 homebridge[538]: [2018-11-1 16:28:30] [hue] Drucker: set homekit status fault from 0 to 1
Nov 1 16:29:50 hbridge2 homebridge[538]: [2018-11-1 16:29:50] [hue] Drucker: set homekit status fault from 1 to 0
Nov 1 16:32:26 hbridge2 homebridge[538]: [2018-11-1 16:32:26] [hue] Drucker: set homekit status fault from 0 to 1
Nov 1 16:39:07 hbridge2 homebridge[538]: [2018-11-1 16:39:07] [hue] Drucker: set homekit status fault from 1 to 0
Nov 1 16:40:27 hbridge2 homebridge[538]: [2018-11-1 16:40:27] [hue] Schlafzimmer1: set homekit status fault from 1 to 0
Nov 1 16:40:27 hbridge2 homebridge[538]: [2018-11-1 16:40:27] [hue] Schlafzimmer 2: set homekit status fault from 1 to 0
Nov 1 16:40:32 hbridge2 homebridge[538]: [2018-11-1 16:40:32] [hue] Drucker: set homekit status fault from 0 to 1
Nov 1 16:40:47 hbridge2 homebridge[538]: [2018-11-1 16:40:47] [hue] Schlafzimmer1: set homekit status fault from 0 to 1
Nov 1 16:42:07 hbridge2 homebridge[538]: [2018-11-1 16:42:07] [hue] Schlafzimmer 2: set homekit status fault from 0 to 1
Nov 1 16:46:02 hbridge2 homebridge[538]: [2018-11-1 16:46:02] [hue] Hauseingang: set homekit status fault from 1 to 0
Nov 1 16:46:12 hbridge2 homebridge[538]: [2018-11-1 16:46:12] [hue] Hauseingang: set homekit status fault from 0 to 1
Nov 1 16:47:23 hbridge2 homebridge[538]: [2018-11-1 16:47:23] [hue] Drucker: set homekit status fault from 1 to 0
Nov 1 16:47:33 hbridge2 homebridge[538]: [2018-11-1 16:47:33] [hue] Hauseingang: set homekit status fault from 1 to 0
Nov 1 16:50:18 hbridge2 homebridge[538]: [2018-11-1 16:50:18] [hue] Drucker: set homekit status fault from 0 to 1
Nov 1 17:08:31 hbridge2 homebridge[538]: [2018-11-1 17:08:31] [hue] Hauseingang: set homekit status fault from 0 to 1
Nov 1 17:17:52 hbridge2 homebridge[538]: [2018-11-1 17:17:52] [hue] Hauseingang: set homekit status fault from 1 to 0
Nov 1 17:18:37 hbridge2 homebridge[538]: [2018-11-1 17:18:37] [hue] Drucker: set homekit status fault from 1 to 0
Nov 1 17:20:02 hbridge2 homebridge[538]: [2018-11-1 17:20:02] [hue] Drucker: set homekit status fault from 0 to 1
Nov 1 17:20:32 hbridge2 homebridge[538]: [2018-11-1 17:20:32] [hue] Hauseingang: set homekit status fault from 0 to 1
Nov 1 17:21:17 hbridge2 homebridge[538]: [2018-11-1 17:21:17] [hue] Drucker: set homekit status fault from 1 to 0
Nov 1 17:27:43 hbridge2 homebridge[538]: [2018-11-1 17:27:43] [hue] Drucker: set homekit status fault from 0 to 1
Nov 1 17:28:58 hbridge2 homebridge[538]: [2018-11-1 17:28:58] [hue] Drucker: set homekit status fault from 1 to 0
Nov 1 17:31:34 hbridge2 homebridge[538]: [2018-11-1 17:31:34] [hue] Drucker: set homekit status fault from 0 to 1
Nov 1 17:35:24 hbridge2 homebridge[538]: [2018-11-1 17:35:24] [hue] Drucker: set homekit status fault from 1 to 0
Nov 1 17:38:49 hbridge2 homebridge[538]: [2018-11-1 17:38:49] [hue] Schlafzimmer1: set homekit status fault from 1 to 0
Nov 1 17:38:49 hbridge2 homebridge[538]: [2018-11-1 17:38:49] [hue] Schlafzimmer 2: set homekit status fault from 1 to 0
Nov 1 17:38:59 hbridge2 homebridge[538]: [2018-11-1 17:38:59] [hue] Schlafzimmer 2: set homekit status fault from 0 to 1
Nov 1 17:40:25 hbridge2 homebridge[538]: [2018-11-1 17:40:25] [hue] Schlafzimmer1: set homekit status fault from 0 to 1
Nov 1 17:52:16 hbridge2 homebridge[538]: [2018-11-1 17:52:16] [hue] Drucker: set homekit status fault from 0 to 1
Nov 1 17:53:41 hbridge2 homebridge[538]: [2018-11-1 17:53:41] [hue] Drucker: set homekit status fault from 1 to 0
Nov 1 17:57:23 hbridge2 homebridge[538]: [2018-11-1 17:57:23] [hue] Couch Lampe: homekit on changed from 0 to 1
Nov 1 17:57:47 hbridge2 homebridge[538]: [2018-11-1 17:57:47] [hue] Drucker: set homekit status fault from 0 to 1
Nov 1 17:57:56 hbridge2 homebridge[538]: [2018-11-1 17:57:56] [hue] Couch Lampe: homekit on changed from 1 to 0
Nov 1 18:00:17 hbridge2 homebridge[538]: [2018-11-1 18:00:17] [hue] Drucker: set homekit status fault from 1 to 0
Nov 1 18:06:43 hbridge2 homebridge[538]: [2018-11-1 18:06:43] [hue] Drucker: set homekit status fault from 0 to 1
Nov 1 18:07:58 hbridge2 homebridge[538]: [2018-11-1 18:07:58] [hue] Drucker: set homekit status fault from 1 to 0
Nov 1 18:18:24 hbridge2 homebridge[538]: [2018-11-1 18:18:24] [hue] Drucker: set homekit status fault from 0 to 1
Nov 1 18:19:45 hbridge2 homebridge[538]: [2018-11-1 18:19:45] [hue] Drucker: set homekit status fault from 1 to 0
Nov 1 18:28:36 hbridge2 homebridge[538]: [2018-11-1 18:28:36] [hue] Hauseingang: set homekit status fault from 1 to 0
Nov 1 18:28:46 hbridge2 homebridge[538]: [2018-11-1 18:28:46] [hue] Hauseingang: set homekit status fault from 0 to 1
Nov 1 18:28:51 hbridge2 homebridge[538]: [2018-11-1 18:28:51] [hue] Hauseingang: set homekit status fault from 1 to 0
Nov 1 18:32:06 hbridge2 homebridge[538]: [2018-11-1 18:32:06] [hue] Schlafzimmer1: set homekit status fault from 1 to 0
Nov 1 18:32:06 hbridge2 homebridge[538]: [2018-11-1 18:32:06] [hue] Schlafzimmer 2: set homekit status fault from 1 to 0
Nov 1 18:33:26 hbridge2 homebridge[538]: [2018-11-1 18:33:26] [hue] Schlafzimmer 2: set homekit status fault from 0 to 1
Nov 1 18:33:36 hbridge2 homebridge[538]: [2018-11-1 18:33:36] [hue] Schlafzimmer1: set homekit status fault from 0 to 1
Nov 1 18:43:25 hbridge2 homebridge[538]: [2018-11-1 18:43:25] [hue] Schlafzimmer1: homekit on changed from 1 to 0
Nov 1 18:43:25 hbridge2 homebridge[538]: [2018-11-1 18:43:25] [hue] Schlafzimmer 2: homekit on changed from 1 to 0
Nov 1 18:43:25 hbridge2 homebridge[538]: [2018-11-1 18:43:25] [hue] Hauseingang: homekit on changed from 1 to 0
Nov 1 18:43:31 hbridge2 homebridge[538]: [2018-11-1 18:43:31] [hue] Couch Lampe: homekit on changed from 0 to 1
Nov 1 18:44:18 hbridge2 homebridge[538]: [2018-11-1 18:44:18] [hue] Hauseingang: set homekit status fault from 0 to 1
Nov 1 19:06:40 hbridge2 homebridge[538]: [2018-11-1 19:06:40] [hue] Couch Lampe: homekit on changed from 1 to 0
Nov 1 19:09:51 hbridge2 homebridge[538]: [2018-11-1 19:09:51] [hue] Drucker: set homekit status fault from 0 to 1
Nov 1 19:12:17 hbridge2 homebridge[538]: [2018-11-1 19:12:17] [hue] Drucker: set homekit status fault from 1 to 0
Nov 1 19:13:42 hbridge2 homebridge[538]: [2018-11-1 19:13:42] [hue] Drucker: set homekit status fault from 0 to 1
Nov 1 19:14:57 hbridge2 homebridge[538]: [2018-11-1 19:14:57] [hue] Drucker: set homekit status fault from 1 to 0
Nov 1 19:17:42 hbridge2 homebridge[538]: [2018-11-1 19:17:42] [hue] muh: set homekit status fault from 1 to 0
Nov 1 19:20:18 hbridge2 homebridge[538]: [2018-11-1 19:20:18] [hue] muh: set homekit status fault from 0 to 1
Nov 1 19:21:23 hbridge2 homebridge[538]: [2018-11-1 19:21:23] [hue] muh: set homekit status fault from 1 to 0
Nov 1 19:22:48 hbridge2 homebridge[538]: [2018-11-1 19:22:48] [hue] muh: set homekit status fault from 0 to 1
Nov 1 19:39:05 hbridge2 homebridge[538]: [2018-11-1 19:39:05] [hue] muh: set homekit status fault from 1 to 0
Nov 1 19:40:35 hbridge2 homebridge[538]: [2018-11-1 19:40:35] [hue] muh: set homekit status fault from 0 to 1
Nov 1 19:40:50 hbridge2 homebridge[538]: [2018-11-1 19:40:50] [hue] Hauseingang: set homekit status fault from 1 to 0
Nov 1 19:40:55 hbridge2 homebridge[538]: [2018-11-1 19:40:55] [hue] Hauseingang: set homekit on from 0 to 1
Nov 1 19:50:11 hbridge2 homebridge[538]: [2018-11-1 19:50:11] [hue] Hauseingang: set homekit status fault from 0 to 1
Nov 1 19:53:51 hbridge2 homebridge[538]: [2018-11-1 19:53:51] [hue] Philips hue: bridge request 5497: get /config
Nov 1 19:53:51 hbridge2 homebridge[538]: [2018-11-1 19:53:51] [hue] Philips hue: bridge communication error ETIMEDOUT on 192.***.***.14
Nov 1 19:53:56 hbridge2 homebridge[538]: [2018-11-1 19:53:56] [hue] Philips hue: bridge request 5498: get /config
Nov 1 19:53:56 hbridge2 homebridge[538]: [2018-11-1 19:53:56] [hue] Philips hue: bridge communication error ETIMEDOUT on 192.***.***.14
Nov 1 20:08:34 hbridge2 systemd[1]: Starting Daily apt download activities...
Nov 1 20:08:37 hbridge2 systemd[1]: Started Daily apt download activities.
Nov 1 20:08:37 hbridge2 systemd[1]: apt-daily.timer: Adding 11h 41min 27.543278s random time.
Nov 1 20:08:37 hbridge2 systemd[1]: apt-daily.timer: Adding 6h 24min 7.461413s random time.
Nov 1 20:08:48 hbridge2 homebridge[538]: [2018-11-1 20:08:48] [hue] Drucker: set homekit status fault from 0 to 1
Nov 1 20:09:58 hbridge2 homebridge[538]: [2018-11-1 20:09:58] [hue] Drucker: set homekit status fault from 1 to 0
Nov 1 20:42:07 hbridge2 homebridge[538]: [2018-11-1 20:42:07] [mqtt] on.offline <to analyze>
Nov 1 20:42:07 hbridge2 homebridge[538]: [2018-11-1 20:42:07] [mqtt] on.close <to analyze>
Nov 1 20:42:08 hbridge2 homebridge[538]: [2018-11-1 20:42:08] [mqtt] on.reconnect <to analyze>
Nov 1 20:42:08 hbridge2 homebridge[538]: [2018-11-1 20:42:08] [mqtt] connected (url = mqtt://192.168.2.27)
Nov 2 06:16:34 hbridge2 systemd[1]: Starting Daily apt upgrade and clean activities...
Nov 2 06:16:35 hbridge2 systemd[1]: Started Daily apt upgrade and clean activities.
Nov 2 06:16:35 hbridge2 systemd[1]: apt-daily-upgrade.timer: Adding 16min 17.162379s random time.
Nov 2 06:16:35 hbridge2 systemd[1]: apt-daily-upgrade.timer: Adding 33.330370s random time.
Nov 2 12:24:34 hbridge2 systemd[1]: Starting Daily apt download activities...
Nov 2 12:24:35 hbridge2 systemd[1]: Started Daily apt download activities.
Nov 2 12:24:35 hbridge2 systemd[1]: apt-daily.timer: Adding 11h 44min 47.912364s random time.
Nov 2 12:24:35 hbridge2 systemd[1]: apt-daily.timer: Adding 9h 28min 12.453777s random time.
Nov 2 16:19:40 hbridge2 systemd[1]: Starting Cleanup of Temporary Directories...
Nov 2 16:19:40 hbridge2 systemd[1]: Started Cleanup of Temporary Directories.
Error found at /usr/local/etc/mosquitto/mosquitto.conf:0.
Error: Unable to open configuration file.
Das steht, dass die Datei /usr/local/etc/mosquitto/mosquitto.conf nicht geöffnet werden konnte. Das wird sicherlich daran liegen, dass die Datei nicht an dieser Stelle existiert.
Kann ich auch löschen? /usr/local/etc/mosquitto/mosquitto.conf
Es ist so wie auf allen Computern: man kann nichts löschen, das nicht existiert.
Die von dir erwähnte Anleitung beschreibt zwar, dass du eine Datei namens /etc/mosquitto/mosquitto.conf anlegen sollst, sagt aber auch gleichzeitig, dass du da was Falsches reinschreiben sollst (es muss natürlich bind_address mit dd heißen). An dieser Stelle muss ich zugeben, dass ich mosquitto nicht einsetze, aber ich hab's mir gerade mal installiert.
Nachdem man mosquitto installiert hat, befindet sich das Programm in /usr/sbin. Es wird also mit /usr/sbin/mosquitto aufgerufen.
Die Konfigurationsdatei ist noch nicht vorhanden. Man kann sie anlegen, wo man will, aber eigentlich gehört sie nach /etc/mosquitto/conf.d/mosquitto.conf. Dort habe ich sie angelegt mit
sudo nano /etc/mosquitto/conf.d/mosquitto.conf
Dort habe ich hineingeschrieben:
und dann die Datei gespeichert. Wer das nachmachen will, kann die obige Zeile kritiklos übernehmen. Ich würde allerdings empfehlen, die IP-Adresse hineinzuschreiben, die der eigene Raspi hat. Ist besser, echt jetzt.
Dann habe ich das vorhandene Startscript für mosquitto verschwinden lassen. Es wurde bei der Installation von mosquitto angelegt. Ich will das weghaben, weil es sonst beim Booten den Service starten würde. Ich möchte aber den Service auf eine andere Art und Weise beim Booten starten, und zwar per systemd. Solange das mitgelieferte Startscript also existiert, würde mosquitto beim Booten zweimal gestartet, was aber nicht geht und was daher blöde Fehlermeldung in den Logs hinterlässt. Also:
sudo mv /etc/init.d/mosquitto . (ja, da steht tatsächlich ein einsamer Punkt am Ende)
sudo rm /etc/rc3.d/*mosquitto*
Dann habe ich das systemd-Startscript erstellt:
sudo nano /etc/systemd/system/mosquitto.service
und dort hineingeschrieben:
Code
Alles anzeigen[Unit] Description=Mosquitto MQTT Broker daemon After=syslog.target network-online.target Requires=network-online.target [Service] Type=forking ExecStart=/usr/sbin/mosquitto -c /etc/mosquitto/conf.d/mosquitto.conf -d ExecReload=/bin/kill -HUP $MAINPID Restart=on-failure [Install] WantedBy=multi-user.target
Abgespeichert und dann:
sudo systemctl daemon-reload
sudo systemctl enable mosquito
sudo systemctl start mosquito
Ein Blick ins Log:
sudo journalctl -fau mosquitto
Und siehe:
Cool. Wenn man soweit gekommen ist, dann geht's an die Installation des homebridge-Moduls. Nur nicht bei mir, weil ich kein MQTT einsetze und daher die Geschichte nicht weiterfolgen kann und will.
Du bist daran gescheitert, weil du sämtliche Pfade, die falsch zu setzen waren falsch gesetzt hast. Du hast keinen ausgelassen. Das ist immerhin konsequent. Aber es ist nicht deine Schuld. Es liegt eher an nicht ganz so präzisen Anleitungen. Möglicherweise hilft dir der Sermon da oben weiter. Ich hab den jetzt aus dem Kopf dahin geschrieben und er hat hoffentlich keine Teppfihler und ich hab hoffentlich nix vergessen.
Gruß,
Stefan
Hinzu kommt das meine HB einmal am Tag abstürzt und ich weis nicht warum..
Ich auch nicht.
Nov 1 19:53:51 hbridge2 homebridge[538]: [2018-11-1 19:53:51] [hue] Philips hue: bridge request 5497: get /config
Nov 1 19:53:51 hbridge2 homebridge[538]: [2018-11-1 19:53:51] [hue] Philips hue: bridge communication error ETIMEDOUT on 192.***.***.14
Nov 1 19:53:56 hbridge2 homebridge[538]: [2018-11-1 19:53:56] [hue] Philips hue: bridge request 5498: get /config
Nov 1 19:53:56 hbridge2 homebridge[538]: [2018-11-1 19:53:56] [hue] Philips hue: bridge communication error ETIMEDOUT on 192.***.***.14
Da steht nur, dass deine HUE-Bridge nicht zu erreichen ist (timeout). Die IP-Adresse sieht ja auch komisch aus.
Stefan
Ich hab jetzt mal der Bridge eine feste IP in der Hue App zugewiesen.
Homebridge läuft noch... In HomeKit: Keine Geräte antworten...
Starte ich Homebridge Dienst neu klappt das manchmal und manchmal muss ich den kompletten raspebrry Neustarten
Was mich auch wundert ist, wieso er soviel die Geräte schaltet...
Obwohl ich sie gar nicht schalte... Man beachte auch die Zeit...Stella ist eine Osram Lighstrip + und der Drucker( Osram Plug ) schalte ich auch nicht alle paar Minuten an und aus...
[2018-11-3 02:02:04] [hue] Stella: set homekit status fault from 0 to 1
[2018-11-3 02:04:34] [hue] Stella: set homekit status fault from 1 to 0
[2018-11-3 05:16:01] [mqtt] on.offline <to analyze>
[2018-11-3 05:16:01] [mqtt] on.close <to analyze>
[2018-11-3 05:16:02] [mqtt] on.reconnect <to analyze>
[2018-11-3 05:16:02] [mqtt] connected (url = mqtt://192.168.2.27)
[2018-11-3 08:33:39] [hue] Stella: set homekit status fault from 0 to 1
[2018-11-3 08:34:54] [hue] Stella: set homekit status fault from 1 to 0
[2018-11-3 08:40:05] [hue] Stella: set homekit status fault from 0 to 1
[2018-11-3 08:45:00] [hue] Stella: set homekit status fault from 1 to 0
[2018-11-3 08:56:07] [hue] Drucker: set homekit status fault from 0 to 1
[2018-11-3 08:57:23] [hue] Drucker: set homekit status fault from 1 to 0
[2018-11-3 09:16:30] [hue] Stella: set homekit status fault from 0 to 1
[2018-11-3 09:17:46] [hue] Stella: set homekit status fault from 1 to 0
[2018-11-3 09:21:31] [hue] Stella: set homekit status fault from 0 to 1
[2018-11-3 09:25:17] [hue] Stella: set homekit status fault from 1 to 0
[2018-11-3 09:33:48] [hue] Soundbar: set homekit on from 0 to 1
[2018-11-3 09:34:18] [hue] Stella: set homekit status fault from 0 to 1
[2018-11-3 09:38:03] [hue] Stella: set homekit status fault from 1 to 0
[2018-11-3 09:40:19] [hue] Drucker: set homekit status fault from 0 to 1
[2018-11-3 09:40:44] [hue] Stella: set homekit status fault from 0 to 1
[2018-11-3 09:41:59] [hue] Stella: set homekit status fault from 1 to 0
[2018-11-3 09:46:45] [hue] Drucker: set homekit status fault from 1 to 0
[2018-11-3 09:48:05] [hue] Drucker: set homekit status fault from 0 to 1
[2018-11-3 09:48:25] [hue] Stella: set homekit status fault from 0 to 1
[2018-11-3 09:49:25] [hue] Drucker: set homekit status fault from 1 to 0
[2018-11-3 09:49:35] [hue] Stella: set homekit status fault from 1 to 0
[2018-11-3 09:50:40] [hue] Drucker: set homekit status fault from 0 to 1
[2018-11-3 09:52:25] [hue] Stella: set homekit status fault from 0 to 1
[2018-11-3 09:57:16] [hue] Stella: set homekit status fault from 1 to 0
[2018-11-3 10:02:07] [hue] Drucker: set homekit status fault from 1 to 0
[2018-11-3 10:06:02] [hue] Drucker: set homekit status fault from 0 to 1
[2018-11-3 10:07:18] [hue] Drucker: set homekit status fault from 1 to 0
[2018-11-3 10:07:38] [hue] Stella: set homekit status fault from 0 to 1
[2018-11-3 10:08:43] [hue] Drucker: set homekit status fault from 0 to 1
[2018-11-3 10:08:58] [hue] Stella: set homekit status fault from 1 to 0
[2018-11-3 10:10:23] [hue] Stella: set homekit status fault from 0 to 1
[2018-11-3 10:12:49] [hue] Stella: set homekit status fault from 1 to 0
[2018-11-3 10:14:14] [hue] Stella: set homekit status fault from 0 to 1
[2018-11-3 10:15:14] [hue] Drucker: set homekit status fault from 1 to 0
[2018-11-3 10:16:34] [hue] Drucker: set homekit status fault from 0 to 1
[2018-11-3 10:16:49] [hue] Stella: set homekit status fault from 1 to 0
[2018-11-3 10:18:20] [hue] Stella: set homekit status fault from 0 to 1
[2018-11-3 10:19:25] [hue] Stella: set homekit status fault from 1 to 0
[2018-11-3 10:20:10] [hue] Philips hue: bridge request 23236: get /config
[2018-11-3 10:20:10] [hue] Philips hue: bridge communication error ETIMEDOUT on 192.***.***.14
[2018-11-3 10:20:15] [hue] Philips hue: bridge request 23237: get /config
[2018-11-3 10:20:15] [hue] Philips hue: bridge communication error ETIMEDOUT on 192.***.***.14
[2018-11-3 10:20:50] [hue] Stella: set homekit status fault from 0 to 1
[2018-11-3 10:24:35] [hue] Stella: set homekit status fault from 1 to 0
[2018-11-3 10:25:00] [hue] Philips hue: bridge request 23350: get /config
[2018-11-3 10:25:00] [hue] Philips hue: bridge communication error ETIMEDOUT on 192.***.***.14
[2018-11-3 10:25:05] [hue] Philips hue: bridge request 23351: get /config
[2018-11-3 10:25:05] [hue] Philips hue: bridge communication error ETIMEDOUT on 192.***.***.14
[2018-11-3 10:25:10] [hue] Philips hue: bridge request 23352: get /config
[2018-11-3 10:25:10] [hue] Philips hue: bridge communication error ETIMEDOUT on 192.***.***.14
[2018-11-3 10:26:00] [hue] Stella: set homekit status fault from 0 to 1
[2018-11-3 10:29:46] [hue] Stella: set homekit status fault from 1 to 0
[2018-11-3 10:32:27] [hue] Stella: set homekit status fault from 0 to 1
[2018-11-3 10:34:52] [hue] Stella: set homekit status fault from 1 to 0
[2018-11-3 10:36:17] [hue] Stella: set homekit status fault from 0 to 1
[2018-11-3 10:37:28] [hue] Stella: set homekit status fault from 1 to 0
[2018-11-3 10:39:48] [hue] Drucker: set homekit status fault from 1 to 0
[2018-11-3 10:39:51] [People] Changed occupancy state for Stellafon to false. Last successful ping 2018-11-03T10:24:49+01:00 , last webhook none .
[2018-11-3 10:40:14] [People] Changed occupancy state for Hariphone7 to false. Last successful ping 2018-11-03T10:25:12+01:00 , last webhook none .
[2018-11-3 10:42:23] [hue] Drucker: set homekit status fault from 0 to 1
[2018-11-3 10:42:48] [hue] Stella: set homekit status fault from 0 to 1
[2018-11-3 10:43:44] [hue] Drucker: set homekit status fault from 1 to 0
[2018-11-3 10:44:04] [hue] Stella: set homekit status fault from 1 to 0
[2018-11-3 10:46:24] [hue] Drucker: set homekit status fault from 0 to 1
[2018-11-3 10:47:39] [hue] Drucker: set homekit status fault from 1 to 0
[2018-11-3 10:50:10] [hue] Drucker: set homekit status fault from 0 to 1
[2018-11-3 10:54:00] [hue] Drucker: set homekit status fault from 1 to 0
[2018-11-3 10:57:51] [hue] Drucker: set homekit status fault from 0 to 1
[2018-11-3 10:59:06] [hue] Drucker: set homekit status fault from 1 to 0
[2018-11-3 11:28:01] [hue] Drucker: set homekit status fault from 0 to 1
[2018-11-3 11:30:32] [hue] Drucker: set homekit status fault from 1 to 0
[2018-11-3 11:34:43] [hue] Stella: set homekit status fault from 0 to 1
[2018-11-3 11:35:48] [hue] Drucker: set homekit status fault from 0 to 1
[2018-11-3 11:36:08] [hue] Stella: set homekit status fault from 1 to 0
[2018-11-3 11:37:03] [hue] Drucker: set homekit status fault from 1 to 0
[2018-11-3 11:45:55] [hue] Drucker: set homekit status fault from 0 to 1
[2018-11-3 11:47:10] [hue] Drucker: set homekit status fault from 1 to 0
[2018-11-3 11:48:25] [hue] Drucker: set homekit status fault from 0 to 1
[2018-11-3 11:49:45] [hue] Drucker: set homekit status fault from 1 to 0
[2018-11-3 11:53:51] [hue] Stella: set homekit status fault from 0 to 1
[2018-11-3 11:55:01] [hue] Stella: set homekit status fault from 1 to 0
[2018-11-3 12:12:19] [hue] Drucker: set homekit status fault from 0 to 1
[2018-11-3 12:13:40] [hue] Drucker: set homekit status fault from 1 to 0
[2018-11-3 12:26:12] [hue] Drucker: set homekit status fault from 0 to 1
[2018-11-3 12:27:27] [hue] Drucker: set homekit status fault from 1 to 0
[2018-11-3 12:34:18] [hue] Stella: set homekit status fault from 0 to 1
[2018-11-3 12:36:44] [hue] Stella: set homekit status fault from 1 to 0
[2018-11-3 12:38:09] [hue] Stella: set homekit status fault from 0 to 1
[2018-11-3 12:40:34] [hue] Stella: set homekit status fault from 1 to 0
[2018-11-3 12:41:45] [hue] Drucker: set homekit status fault from 0 to 1
[2018-11-3 12:42:10] [hue] Stella: set homekit status fault from 0 to 1
[2018-11-3 12:43:05] [hue] Drucker: set homekit status fault from 1 to 0
[2018-11-3 12:45:50] [hue] Stella: set homekit status fault from 1 to 0
[2018-11-3 13:04:23] [hue] Drucker: set homekit status fault from 0 to 1
[2018-11-3 13:05:38] [hue] Drucker: set homekit status fault from 1 to 0
[2018-11-3 13:12:00] [hue] Drucker: set homekit status fault from 0 to 1
[2018-11-3 13:13:20] [hue] Drucker: set homekit status fault from 1 to 0
[2018-11-3 13:22:27] [hue] Stella: set homekit status fault from 0 to 1
[2018-11-3 13:23:32] [hue] Stella: set homekit status fault from 1 to 0
[2018-11-3 13:25:57] [hue] Drucker: set homekit status fault from 0 to 1
[2018-11-3 13:27:12] [hue] Drucker: set homekit status fault from 1 to 0
[2018-11-3 13:32:18] [hue] Drucker: set homekit status fault from 0 to 1
[2018-11-3 13:33:34] [hue] Drucker: set homekit status fault from 1 to 0
[2018-11-3 13:42:45] [hue] Stella: set homekit status fault from 0 to 1
[2018-11-3 13:44:01] [hue] Stella: set homekit status fault from 1 to 0
[2018-11-3 13:49:25] [People] Changed occupancy state for Stellafon to true. Last successful ping 2018-11-03T13:49:25+01:00 , last webhook none .
[2018-11-3 13:51:01] [People] Changed occupancy state for Hariphone7 to true. Last successful ping 2018-11-03T13:51:01+01:00 , last webhook none .
[2018-11-3 13:52:32] [hue] Drucker: set homekit status fault from 0 to 1
[2018-11-3 13:53:47] [hue] Drucker: set homekit status fault from 1 to 0
[2018-11-3 13:54:17] [hue] Stella: set homekit status fault from 0 to 1
[2018-11-3 13:55:23] [hue] Stella: set homekit status fault from 1 to 0
[2018-11-3 14:12:50] [hue] Drucker: set homekit status fault from 0 to 1
[2018-11-3 14:14:01] [hue] Drucker: set homekit status fault from 1 to 0
[2018-11-3 14:14:26] [hue] Stella: set homekit status fault from 0 to 1
[2018-11-3 14:16:36] [hue] Drucker: set homekit status fault from 0 to 1
[2018-11-3 14:17:56] [hue] Drucker: set homekit status fault from 1 to 0
[2018-11-3 14:20:42] [hue] Stella: set homekit status fault from 1 to 0
[2018-11-3 14:21:52] [hue] Drucker: set homekit status fault from 0 to 1
[2018-11-3 14:23:07] [hue] Drucker: set homekit status fault from 1 to 0
[2018-11-3 14:26:03] [hue] Stella: set homekit status fault from 0 to 1
[2018-11-3 14:27:08] [hue] Stella: set homekit status fault from 1 to 0
[2018-11-3 14:28:33] [hue] Stella: set homekit status fault from 0 to 1
[2018-11-3 14:32:19] [hue] Stella: set homekit status fault from 1 to 0
[2018-11-3 14:36:10] [hue] Stella: set homekit status fault from 0 to 1
[2018-11-3 14:38:35] [hue] Stella: set homekit status fault from 1 to 0
[2018-11-3 15:59:55] [hue] Stella: set homekit status fault from 0 to 1
[2018-11-3 16:01:05] [hue] Stella: set homekit status fault from 1 to 0
Irgendwie hab ich das Gefühl das es an dem letzten Homebridge-hue plugin liegt, ich hatte ja zuvor nicht die Probleme...
Mit freundlichen Grüßen
habe gerade node 11.1.0 installiert. Nach dem Reboot habe ich eine Warnung in der Console
Zitat[2018-11-3 22:45:11] Homebridge is running on port 51826.
[2018-11-3 22:45:14] [Config] Using Form Authentication
[2018-11-3 22:45:14] [Config] Console v3.9.0 is listening on port 8080.
(node:1354) Warning: Setting the NODE_TLS_REJECT_UNAUTHORIZED environment variable to '0' makes TLS connections and HTTPS requests insecure by disabling certificate verification.
kann mir einer was dazu sagen oder helfen wie ich das beheben kann?