GELÖST fhem - verschiedene Fehlermeldungen ohne Ende. So nicht mehr nutzbar.

Begonnen von Invers, 05 September 2021, 13:27:13

Vorheriges Thema - Nächstes Thema

Invers

Mein fhem arbeitet nur noch sehr fehlerhaft. Das Log füllt sich mit den verschiedendsten Fehlermeldungen, die nichts mit einander zu tun haben. Es kommen Melfungen zur Fritzbox (Netzwerk), Presencemodul, Signalduino, Bluetooth, HM u.s.w.
Nach einem Neustart des Pi läuft alles für etwa 5-10 Minuten, dann beginnt alles von vorne.
Ich habe entsprechend dem WIKI Fehlersuche betrieben, ohne Erfolg.
Ich habe weitere folgende Lösungsversuche unternommen:

Netzteil am Pi getauscht
ganzen Pi getauscht
Netzwerkkabel vom Pi zu FBox getauscht
SSD getauscht mit einer SSD vom Vormonat, also fhem aus Monat 07.
Fritzbox neu gestartet
alle Geräte neu gestartet
Pi mit fhem ohne weitere Hardware laufen lassen

Den Rest habe ich vergessen.

Kann jemand versuchen, mir bei der Lösung des Problems behilflich zu sein?
Wenn ich keine Lösung finden kann, muss ich die Hausautomatisierung aufgeben. Mir sind die Ideen ausgegangen.

Bis zum 31.08. lief alles perfekt.

Hier mal ein Stück des Log, gibt aber noch viel mehr verschiedene Fehler.
Ich hatte das Logfile löschen müssen, war schon zu gross.
a51 sind Handys.
Am Pi steckt ausschliesslich die SSD (eigenes Netzteil) und der Bluetoothdongle.

2021.09.05 12:58:12 1: Logfile gelöscht
2021.09.05 12:59:18 1: ▀ Schloss Status locked
2021.09.05 12:59:19 3: FBDECT set AlarmCam off
2021.09.05 12:59:19 3: FBDECT set Uhr on
2021.09.05 12:59:19 3: ▀ schalten bei Ankunft
2021.09.05 12:59:19 3: FBDECT set AlarmCam off
2021.09.05 12:59:19 3: ▀ Steckdose_H2 Ladegeräte on
2021.09.05 12:59:23 2: hue: http request failed: 192.168.178.66: Keine Route zum Zielrechner (113)
2021.09.05 12:59:28 1: ▀ Schloss Status unlocked
2021.09.05 12:59:29 3: ▀ Tab_A screen off
2021.09.05 12:59:30 3: ▀ Tab_b screen off
2021.09.05 12:59:31 3: CUL_HM set Schloss lock noArg
2021.09.05 12:59:40 1: ▀ Schloss Status locked
2021.09.05 13:00:21 3: FBDECT set Blumen off
2021.09.05 13:00:21 3: MQTT2_DEVICE set Steckdose_2 off
2021.09.05 13:00:25 2: hue: http request failed: 192.168.178.66: Keine Route zum Zielrechner (113)
2021.09.05 13:01:30 3: telnetForTvUpdateFn_1630839690: port 35581 opened
2021.09.05 13:02:01 1: ▀ Schloss Status locked
2021.09.05 13:02:02 2: PRESENCE (a51H) - device could not be checked (retrying in 10 seconds): Process died prematurely
Can't use an undefined value as a HASH reference at (eval 160) line 272.
2021.09.05 13:02:11 1: ▀ Schloss Status unlocked
2021.09.05 13:02:12 1: FRITZBOX Fritzbox: Readout_Aborted.1931 Error: Timeout when reading Fritz!Box data.
2021.09.05 13:02:12 2: PRESENCE (a51K) - device could not be checked (retrying in 10 seconds): Process died prematurely
2021.09.05 13:02:19 3: CUL_HM set Schloss lock noArg
2021.09.05 13:02:23 2: PRESENCE (a51H) - device could not be checked after 1 retry (retrying in 10 seconds): Process died prematurely
2021.09.05 13:02:28 1: ▀ Schloss Status locked
2021.09.05 13:02:33 2: PRESENCE (a51K) - device could not be checked after 1 retry (retrying in 10 seconds): Process died prematurely
2021.09.05 13:03:33 1: Timeout for PRESENCE_DoLocalBluetoothScan reached, terminated process 1553
2021.09.05 13:03:33 2: PRESENCE (a51H) - device could not be checked after 2 retries (retrying in 10 seconds): Timeout: process terminated
2021.09.05 13:03:33 2: PRESENCE (a51K) - device could not be checked after 2 retries (retrying in 10 seconds): Process died prematurely
2021.09.05 13:04:43 1: Timeout for PRESENCE_DoLocalBluetoothScan reached, terminated process 1571
2021.09.05 13:04:43 2: PRESENCE (a51H) - device could not be checked after 3 retries (resuming normal operation): Timeout: process terminated
2021.09.05 13:04:43 1: Timeout for PRESENCE_DoLocalBluetoothScan reached, terminated process 1572
2021.09.05 13:04:43 2: PRESENCE (a51K) - device could not be checked after 3 retries (resuming normal operation): Timeout: process terminated
2021.09.05 13:06:30 1: Timeout for DOIF::doParse reached, terminated process 1500
Can't use an undefined value as a HASH reference at (eval 160) line 272.
2021.09.05 13:06:47 2: PRESENCE (a51H) - device could not be checked (retrying in 10 seconds): Process died prematurely
2021.09.05 13:07:02 2: PRESENCE (a51K) - device could not be checked (retrying in 10 seconds): Process died prematurely
2021.09.05 13:07:12 2: PRESENCE (a51H) - device could not be checked after 1 retry (retrying in 10 seconds): Process died prematurely
2021.09.05 13:07:12 1: FRITZBOX Fritzbox: Readout_Aborted.1931 Error: Timeout when reading Fritz!Box data.
2021.09.05 13:07:22 1: 192.168.178.35:1000 disconnected, waiting to reappear (HMLAN1)
2021.09.05 13:07:22 1: HMLAN_Parse: HMLAN1 new condition disconnected
2021.09.05 13:08:12 1: Timeout for PRESENCE_DoLocalBluetoothScan reached, terminated process 1725
2021.09.05 13:08:12 2: PRESENCE (a51K) - device could not be checked after 1 retry (retrying in 10 seconds): Timeout: process terminated
2021.09.05 13:08:13 2: PRESENCE (a51H) - device could not be checked after 2 retries (retrying in 10 seconds): Process died prematurely
2021.09.05 13:08:22 1: HMLAN_Parse: HMLAN1 new condition init
2021.09.05 13:08:22 1: 192.168.178.35:1000 reappeared (HMLAN1)
2021.09.05 13:08:22 1: HMLAN_Parse: HMLAN1 new condition ok
2021.09.05 13:09:22 1: Timeout for PRESENCE_DoLocalBluetoothScan reached, terminated process 1746
2021.09.05 13:09:22 2: PRESENCE (a51K) - device could not be checked after 2 retries (retrying in 10 seconds): Timeout: process terminated
2021.09.05 13:09:23 2: PRESENCE (a51H) - device could not be checked after 3 retries (resuming normal operation): Process died prematurely
2021.09.05 13:10:32 2: PRESENCE (a51K) - device could not be checked after 3 retries (resuming normal operation): Process died prematurely
2021.09.05 13:11:30 1: Timeout for DOIF::doParse reached, terminated process 1656
Can't use an undefined value as a HASH reference at (eval 160) line 272.
2021.09.05 13:11:52 2: PRESENCE (a51H) - device could not be checked (retrying in 10 seconds): Process died prematurely
2021.09.05 13:12:02 2: PRESENCE (a51K) - device could not be checked (retrying in 10 seconds): Process died prematurely
2021.09.05 13:12:21 2: PRESENCE (a51H) - device could not be checked after 1 retry (retrying in 10 seconds): Process died prematurely
2021.09.05 13:12:31 2: PRESENCE (a51K) - device could not be checked after 1 retry (retrying in 10 seconds): Process died prematurely
2021.09.05 13:12:57 1: Timeout for FRITZBOX_Readout_Run_Web reached, terminated process 1954
2021.09.05 13:12:57 1: FRITZBOX Fritzbox: Readout_Aborted.1931 Error: Timeout when reading Fritz!Box data.
2021.09.05 13:12:58 2: PRESENCE (a51H) - device could not be checked after 2 retries (retrying in 10 seconds): Process died prematurely
2021.09.05 13:13:11 1: 192.168.178.35:1000 disconnected, waiting to reappear (HMLAN1)
2021.09.05 13:13:11 1: HMLAN_Parse: HMLAN1 new condition disconnected
2021.09.05 13:13:41 1: Timeout for PRESENCE_DoLocalBluetoothScan reached, terminated process 1975
2021.09.05 13:13:41 2: PRESENCE (a51K) - device could not be checked after 2 retries (retrying in 10 seconds): Timeout: process terminated
2021.09.05 13:13:41 2: PRESENCE (a51H) - device could not be checked after 3 retries (resuming normal operation): Process died prematurely
2021.09.05 13:14:11 1: HMLAN_Parse: HMLAN1 new condition init
2021.09.05 13:14:11 1: 192.168.178.35:1000 reappeared (HMLAN1)
2021.09.05 13:14:12 1: HMLAN_Parse: HMLAN1 new condition ok
2021.09.05 13:14:41 1: 192.168.178.35:1000 disconnected, waiting to reappear (HMLAN1)
2021.09.05 13:14:41 1: HMLAN_Parse: HMLAN1 new condition disconnected
2021.09.05 13:15:01 1: Timeout for PRESENCE_DoLocalBluetoothScan reached, terminated process 1997
2021.09.05 13:15:01 2: PRESENCE (a51K) - device could not be checked after 3 retries (resuming normal operation): Timeout: process terminated
2021.09.05 13:15:41 1: HMLAN_Parse: HMLAN1 new condition init
2021.09.05 13:15:41 1: 192.168.178.35:1000 reappeared (HMLAN1)
2021.09.05 13:15:42 1: HMLAN_Parse: HMLAN1 new condition ok
2021.09.05 13:16:30 1: Timeout for DOIF::doParse reached, terminated process 1919



Danke im Voraus.
Pi3B+ mit SSD/ Bullseye | FB7590 AX | 12 x Dect200 | CUL433+868 | SDuino | HM-LAN | 3 x Heizung FHT + FKontakte | KeyMatic + 4 FB | HM Wandtaster 2-fach m. LED | 6 x Türkont. TFK-TI | HM-Bew.-Melder innen | 3 x Smoked. HM-SEC-SD-2

Christoph Morrison


Invers

Hier noch ein Stück aus der Syslog
Blocking.pm 23268 2020-12-01 11:48:48Z rudolfkoenig

Ich hatte zusätzlich noch ein update force gemacht. Also sollte alles aktuell sein. Hatte ich vergessen zu erwähnen.

Systemauslastung ist bei etwa 15%, schwankend.

pi@fhem3:~ $ sudo grep -i fail -A1 -B1 /var/log/syslog
Sep  5 08:19:57 fhem3 kernel: [    0.257084] bcm2835-rng 3f104000.rng: hwrng registered
Sep  5 08:19:57 fhem3 systemd-udevd[179]: Process '/usr/sbin/th-cmd --socket /var/run/thd.socket --passfd --udev' failed with exit code 1.
Sep  5 08:19:57 fhem3 kernel: [    0.259828] vc-mem: phys_addr:0x00000000 mem_base=0x3ec00000 mem_size:0x40000000(1024 MiB)
--
Sep  5 09:42:41 fhem3 kernel: [    0.765686] Interrupt/Control Split Transaction hack enabled
Sep  5 09:42:41 fhem3 systemd-udevd[201]: Process '/usr/sbin/th-cmd --socket /var/run/thd.socket --passfd --udev' failed with exit code 1.
Sep  5 09:42:41 fhem3 kernel: [    0.776602] dwc_otg: Microframe scheduler enabled
--
Sep  5 09:42:41 fhem3 bluetoothd[364]: Bluetooth management interface 1.14 initialized
Sep  5 09:42:41 fhem3 bluetoothd[364]: Failed to obtain handles for "Service Changed" characteristic
Sep  5 09:42:41 fhem3 systemd[1]: Started System Logging Service.
--
Sep  5 09:42:41 fhem3 systemd[1]: Started Disable WiFi if country not set.
Sep  5 09:42:41 fhem3 bluetoothd[364]: Sap driver initialization failed.
Sep  5 09:42:41 fhem3 bluetoothd[364]: sap-server: Operation not permitted (1)
--
Sep  5 09:42:41 fhem3 kernel: [   11.653037] Bluetooth: RFCOMM ver 1.11
Sep  5 09:42:41 fhem3 bluetoothd[364]: Failed to set privacy: Rejected (0x0b)
Sep  5 09:42:41 fhem3 kernel: [   11.732131] Adding 102396k swap on /var/swap.  Priority:-2 extents:1 across:102396k FS
--
Sep  5 09:56:07 fhem3 systemd[1]: Reached target Local File Systems.
Sep  5 09:56:07 fhem3 systemd-udevd[206]: Process '/usr/sbin/th-cmd --socket /var/run/thd.socket --passfd --udev' failed with exit code 1.
Sep  5 09:56:07 fhem3 systemd[1]: Starting Create Volatile Files and Directories...
--
Sep  5 09:56:07 fhem3 systemd[1]: Starting Avahi mDNS/DNS-SD Stack...
Sep  5 09:56:07 fhem3 bluetoothd[356]: Failed to obtain handles for "Service Changed" characteristic
Sep  5 09:56:07 fhem3 dbus[375]: [system] Activating via systemd: service name='org.freedesktop.hostname1' unit='dbus-org.freedesktop.hostname1.service'
--
Sep  5 09:56:07 fhem3 cron[422]: (CRON) INFO (Running @reboot jobs)
Sep  5 09:56:07 fhem3 bluetoothd[356]: Sap driver initialization failed.
Sep  5 09:56:07 fhem3 bluetoothd[356]: sap-server: Operation not permitted (1)
--
Sep  5 09:56:07 fhem3 dphys-swapfile[354]: done.
Sep  5 09:56:07 fhem3 bluetoothd[356]: Failed to set privacy: Rejected (0x0b)
Sep  5 09:56:07 fhem3 kernel: [   11.538026] Bluetooth: RFCOMM TTY layer initialized
--
Sep  5 11:16:26 fhem3 systemd[1]: Started Preprocess NFS configuration.
Sep  5 11:16:26 fhem3 systemd-udevd[224]: Process '/usr/sbin/th-cmd --socket /var/run/thd.socket --passfd --udev' failed with exit code 1.
Sep  5 11:16:26 fhem3 systemd[1]: Reached target NFS client services.
--
Sep  5 11:16:26 fhem3 bluetoothd[387]: Bluetooth management interface 1.14 initialized
Sep  5 11:16:26 fhem3 bluetoothd[387]: Failed to obtain handles for "Service Changed" characteristic
Sep  5 11:16:26 fhem3 wpa_supplicant[394]: Successfully initialized wpa_supplicant
Sep  5 11:16:26 fhem3 dphys-swapfile[396]: want /var/swap=100MByte, checking existing: keeping it
Sep  5 11:16:26 fhem3 bluetoothd[387]: Sap driver initialization failed.
Sep  5 11:16:26 fhem3 bluetoothd[387]: sap-server: Operation not permitted (1)
--
Sep  5 11:16:26 fhem3 dhcpcd[406]: eth0: waiting for carrier
Sep  5 11:16:26 fhem3 bluetoothd[387]: Failed to set privacy: Rejected (0x0b)
Sep  5 11:16:26 fhem3 dhcpcd[406]: eth0: carrier acquired
--
Sep  5 11:43:20 fhem3 systemd[1]: Starting Create Volatile Files and Directories...
Sep  5 11:43:20 fhem3 systemd-udevd[209]: Process '/usr/sbin/th-cmd --socket /var/run/thd.socket --passfd --udev' failed with exit code 1.
Sep  5 11:43:20 fhem3 kernel: [    0.000000] Booting Linux on physical CPU 0x0
--
Sep  5 12:44:50 fhem3 systemd[1]: Reached target Local File Systems.
Sep  5 12:44:50 fhem3 systemd-udevd[186]: Process '/usr/sbin/th-cmd --socket /var/run/thd.socket --passfd --udev' failed with exit code 1.
Sep  5 12:44:50 fhem3 systemd[1]: Starting Tell Plymouth To Write Out Runtime Data...
--
Sep  5 12:44:51 fhem3 bluetoothd[354]: Bluetooth management interface 1.14 initialized
Sep  5 12:44:51 fhem3 bluetoothd[354]: Failed to obtain handles for "Service Changed" characteristic
Sep  5 12:44:51 fhem3 bluetoothd[354]: Sap driver initialization failed.
Sep  5 12:44:51 fhem3 bluetoothd[354]: sap-server: Operation not permitted (1)
--
Sep  5 12:44:51 fhem3 wpa_supplicant[430]: Successfully initialized wpa_supplicant
Sep  5 12:44:51 fhem3 bluetoothd[354]: Failed to set privacy: Rejected (0x0b)
Sep  5 12:44:51 fhem3 kernel: [   11.145413] Adding 102396k swap on /var/swap.  Priority:-2 extents:1 across:102396k FS
--
Sep  5 13:19:53 fhem3 systemd[1]: Mounted /boot.
Sep  5 13:19:53 fhem3 systemd-udevd[178]: Process '/usr/sbin/th-cmd --socket /var/run/thd.socket --passfd --udev' failed with exit code 1.
Sep  5 13:19:53 fhem3 systemd[1]: Reached target Local File Systems.
--
Sep  5 13:19:53 fhem3 dbus[336]: [system] Activating via systemd: service name='org.freedesktop.hostname1' unit='dbus-org.freedesktop.hostname1.service'
Sep  5 13:19:53 fhem3 bluetoothd[352]: Failed to obtain handles for "Service Changed" characteristic
Sep  5 13:19:53 fhem3 CRON[446]: (root) CMD (   PATH="$PATH:/usr/local/bin/" pihole updatechecker remote reboot)
--
Sep  5 13:19:53 fhem3 systemd[1]: Starting Hostname Service...
Sep  5 13:19:53 fhem3 bluetoothd[352]: Sap driver initialization failed.
Sep  5 13:19:53 fhem3 bluetoothd[352]: sap-server: Operation not permitted (1)
--
Sep  5 13:19:53 fhem3 systemd[1]: Started LSB: Autogenerate and use a swap file.
Sep  5 13:19:53 fhem3 bluetoothd[352]: Failed to set privacy: Rejected (0x0b)
Sep  5 13:19:53 fhem3 kernel: [   11.400836] Bluetooth: RFCOMM TTY layer initialized
--
Sep  5 14:04:13 fhem3 kernel: [    0.022275] futex hash table entries: 1024 (order: 4, 65536 bytes)
Sep  5 14:04:13 fhem3 systemd-udevd[188]: Process '/usr/sbin/th-cmd --socket /var/run/thd.socket --passfd --udev' failed with exit code 1.
Sep  5 14:04:13 fhem3 kernel: [    0.022890] pinctrl core: initialized pinctrl subsystem
--
Sep  5 14:04:14 fhem3 systemd[1]: Started Clean PHP session files every 30 mins.
Sep  5 14:04:14 fhem3 bluetoothd[358]: Failed to obtain handles for "Service Changed" characteristic
Sep  5 14:04:14 fhem3 systemd[1]: apt-daily.timer: Adding 9h 4min 30.399349s random time.
--
Sep  5 14:04:14 fhem3 systemd[1]: Started Disable WiFi if country not set.
Sep  5 14:04:14 fhem3 bluetoothd[358]: Sap driver initialization failed.
Sep  5 14:04:14 fhem3 bluetoothd[358]: sap-server: Operation not permitted (1)
--
Sep  5 14:04:14 fhem3 kernel: [   11.346236] Bluetooth: RFCOMM ver 1.11
Sep  5 14:04:14 fhem3 bluetoothd[358]: Failed to set privacy: Rejected (0x0b)
Sep  5 14:04:14 fhem3 dphys-swapfile[359]: want /var/swap=100MByte, checking existing: keeping it
--
Sep  5 14:05:29 fhem3 systemd[1]: Started Set console font and keymap.
Sep  5 14:05:29 fhem3 systemd-udevd[202]: Process '/usr/sbin/th-cmd --socket /var/run/thd.socket --passfd --udev' failed with exit code 1.
Sep  5 14:05:29 fhem3 systemd[1]: Started Create Volatile Files and Directories.
--
Sep  5 14:05:29 fhem3 kernel: [    0.000289] Console: colour dummy device 80x30
Sep  5 14:05:29 fhem3 bluetoothd[372]: Failed to obtain handles for "Service Changed" characteristic
Sep  5 14:05:29 fhem3 kernel: [    0.000914] console [tty1] enabled
--
Sep  5 14:05:29 fhem3 kernel: [    0.022254] futex hash table entries: 1024 (order: 4, 65536 bytes)
Sep  5 14:05:29 fhem3 bluetoothd[372]: Sap driver initialization failed.
Sep  5 14:05:29 fhem3 kernel: [    0.022872] pinctrl core: initialized pinctrl subsystem
--
Sep  5 14:05:29 fhem3 kernel: [   11.304665] Bluetooth: RFCOMM ver 1.11
Sep  5 14:05:29 fhem3 bluetoothd[372]: Failed to set privacy: Rejected (0x0b)
Sep  5 14:05:29 fhem3 kernel: [   11.345822] Adding 102396k swap on /var/swap.  Priority:-2 extents:1 across:102396k FS
pi@fhem3:~ $
Pi3B+ mit SSD/ Bullseye | FB7590 AX | 12 x Dect200 | CUL433+868 | SDuino | HM-LAN | 3 x Heizung FHT + FKontakte | KeyMatic + 4 FB | HM Wandtaster 2-fach m. LED | 6 x Türkont. TFK-TI | HM-Bew.-Melder innen | 3 x Smoked. HM-SEC-SD-2

Invers

Das Problem scheint ja wirklich eine Herausforderung zu sein.
Hat denn keiner eine Idee?
Ich hatte schon den Verdacht, die Fritzbox wäre defekt. Aber dazu passen ja die Meldungen für z.B. den Signalduino nicht.
Pi3B+ mit SSD/ Bullseye | FB7590 AX | 12 x Dect200 | CUL433+868 | SDuino | HM-LAN | 3 x Heizung FHT + FKontakte | KeyMatic + 4 FB | HM Wandtaster 2-fach m. LED | 6 x Türkont. TFK-TI | HM-Bew.-Melder innen | 3 x Smoked. HM-SEC-SD-2

Wernieman

Irgendwie hast Du ein Systemproblem....

- Hast Du es mal mit der "Debug"-Fhem-Config versucht?

Wie bootest Du Dein System? Du schreibst etwas von einer SSD? Wirklich SSD oder SD-Card?
- Bitte um Input für Output
- When there is a Shell, there is a Way
- Wann war Dein letztes Backup?

Wie man Fragen stellt: https://tty1.net/smart-questions_de.html

Invers

Ich arbeite mit SSD und Config.db. Ich habe nicht verstanden, was du meinst.

Ich kopiere monatlich die SSD auf eine andere SSD und tausche sie im Anschluss aus.
Merkwürdig ist ja,  dass beide (die alte und die neue SSD) die selben Fehler loggen.
Als ich im vorigen Monat gesichert hatte, war alles noch in Ordnung. Der Ärger begann etwa am 01.09.2021, aber mit allen Versionen. Selbst ohne angesteckte Hardware habe ich Ärger.
Pi3B+ mit SSD/ Bullseye | FB7590 AX | 12 x Dect200 | CUL433+868 | SDuino | HM-LAN | 3 x Heizung FHT + FKontakte | KeyMatic + 4 FB | HM Wandtaster 2-fach m. LED | 6 x Türkont. TFK-TI | HM-Bew.-Melder innen | 3 x Smoked. HM-SEC-SD-2

KölnSolar

ZitatIrgendwie hast Du ein Systemproblem....
Glaube ich auch. FHEM ist denk ich OK.
Hast Du ein altes Image, welches Du auf einem anderen Bootdatenträger installieren kannst ? Und wenn das läuft Dein aktuelles FHEM einspielen ?

nicht verzagen(auch wenns schwer fällt)
Markus
Edit:
ZitatIch kopiere monatlich die SSD auf eine andere SSD und tausche sie im Anschluss aus.
Wie und was kopierst Du ?
RPi3/2 buster/stretch-SamsungAV_E/N-RFXTRX-IT-RSL-NC5462-Oregon-CUL433-GT-TMBBQ-01e-CUL868-FS20-EMGZ-1W(GPIO)-DS18B20-CO2-USBRS232-USBRS422-Betty_Boop-EchoDot-OBIS(Easymeter-Q3/EMH-KW8)-PCA301(S'duino)-Deebot(mqtt2)-zigbee2mqtt

Invers

Hier noch einmal ein aktueller Auszug.
Wenn ich den Signalduino wechsle, kommen trotzdem diese Fehler.
HMUART lässt sich nicht deaktivieren (disable). Aber das Entfernen bringt auch nix.
2021.09.05 21:57:24 3: sduino: ResetDevice, nanoCC1101
2021.09.05 21:57:24 3: Opening sduino device /dev/serial/by-id/usb-SHK_SIGNALduino_433-if00-port0
2021.09.05 21:57:24 3: Setting sduino serial parameters to 57600,8,N,1
2021.09.05 21:57:24 1: sduino: DoInit, /dev/serial/by-id/usb-SHK_SIGNALduino_433-if00-port0@57600
2021.09.05 21:57:24 3: sduino device opened
2021.09.05 21:57:25 3: sduino: SimpleWrite_XQ, disable receiver (XQ)
2021.09.05 21:57:26 3: sduino: StartInit, get version, retry = 0
2021.09.05 21:57:26 2: sduino: CheckVersionResp, initialized v3.4.4
2021.09.05 21:57:26 3: sduino: CheckVersionResp, enable receiver (XE)
2021.09.05 21:57:28 3: sduino: CheckCcpatableResponse, patable: C8
2021.09.05 21:57:49 1: Timeout for PRESENCE_DoLocalBluetoothScan reached, terminated process 29935
2021.09.05 21:57:49 2: PRESENCE (a51H) - device could not be checked after 3 retries (resuming normal operation): Timeout: process terminated
2021.09.05 21:58:15 1: HMUARTLGW myHmUART did not respond for the 1. time, resending
2021.09.05 21:58:15 3: fb2: read from http://192.168.178.1:80 timed out
2021.09.05 21:58:15 1: Timeout for DOIF::doParse reached, terminated process 29682
2021.09.05 21:58:16 1: HMUARTLGW myHmUART failed to enter App!
2021.09.05 21:58:16 1: 192.168.178.35:1000 disconnected, waiting to reappear (HMLAN1)
2021.09.05 21:58:16 1: HMLAN_Parse: HMLAN1 new condition disconnected
2021.09.05 21:58:17 1: HMLAN_Parse: HMLAN1 new condition init
2021.09.05 21:58:17 1: 192.168.178.35:1000 reappeared (HMLAN1)
2021.09.05 21:58:17 1: HMLAN_Parse: HMLAN1 new condition ok
2021.09.05 21:58:18 1: HMUARTLGW myHmUART did not respond for the 2. time, resending
2021.09.05 21:59:25 2: hue: http request failed: connect to http://192.168.178.66:80 timed out
2021.09.05 22:00:00 3: Ufo_LED_Stange RGB LD382A dim 50 60
2021.09.05 22:00:00 3: Ufo_LED_Stange set HSV 118, 98, 50 with ramp: 60, flags:
2021.09.05 22:00:01 3: MQTT2_DEVICE set Steckdose_4 on
2021.09.05 22:00:34 3: Ufo_LED_Stange low level cmd queue send ERROR 312a6e0100000fd9, qlen 1 (reconnect giving up)
2021.09.05 22:00:37 3: Ufo_LED_Stange low level cmd queue send ERROR 31296b0100000fd5, qlen 1 (reconnect giving up)
2021.09.05 22:00:40 3: Ufo_LED_Stange low level cmd queue send ERROR 3128690100000fd2, qlen 1 (reconnect giving up)
2021.09.05 22:00:43 3: Ufo_LED_Stange low level cmd queue send ERROR 3127660100000fce, qlen 1 (reconnect giving up)
2021.09.05 22:02:25 2: hue: http request failed: connect to http://192.168.178.66:80 timed out
2021.09.05 22:03:25 2: hue: http request failed: connect to http://192.168.178.66:80 timed out
2021.09.05 22:07:53 1: HMUARTLGW myHmUART did not respond for the 1. time, resending
2021.09.05 22:07:56 1: HMUARTLGW myHmUART did not respond for the 2. time, resending
2021.09.05 22:07:59 1: HMUARTLGW myHmUART did not respond for the 3. time, resending
2021.09.05 22:08:02 1: HMUARTLGW myHmUART did not respond after all, reopening
2021.09.05 22:08:02 3: Setting myHmUART serial parameters to 115200,8,N,1
2021.09.05 22:08:02 1: /dev/ttyAMA0 reappeared (myHmUART)
2021.09.05 22:08:06 1: /dev/ttyAMA0 disconnected, waiting to reappear (myHmUART)
2021.09.05 22:08:07 3: Setting myHmUART serial parameters to 115200,8,N,1
2021.09.05 22:08:07 1: /dev/ttyAMA0 reappeared (myHmUART)
2021.09.05 22:08:15 2: PRESENCE (a51H) - device could not be checked (retrying in 10 seconds): Process died prematurely
2021.09.05 22:08:25 1: FRITZBOX Fritzbox: Readout_Aborted.1931 Error: Timeout when reading Fritz!Box data.
2021.09.05 22:08:32 2: PRESENCE (a51H) - device could not be checked after 1 retry (retrying in 10 seconds): Process died prematurely
2021.09.05 22:08:43 2: PRESENCE (a51K) - device could not be checked (retrying in 10 seconds): Process died prematurely
Can't use an undefined value as a HASH reference at (eval 160) line 272.
2021.09.05 22:08:54 1: /dev/ttyAMA0 disconnected, waiting to reappear (myHmUART)
2021.09.05 22:08:54 3: Setting myHmUART serial parameters to 115200,8,N,1
2021.09.05 22:08:54 1: /dev/ttyAMA0 reappeared (myHmUART)
2021.09.05 22:09:00 1: HMUARTLGW myHmUART did not respond for the 1. time, resending
2021.09.05 22:09:15 3: sduino: KeepAlive, not ok, retry = 2 -> get ping
2021.09.05 22:09:43 1: Timeout for PRESENCE_DoLocalBluetoothScan reached, terminated process 30577
2021.09.05 22:09:43 2: PRESENCE (a51H) - device could not be checked after 2 retries (retrying in 10 seconds): Timeout: process terminated
2021.09.05 22:09:43 2: PRESENCE (a51K) - device could not be checked after 1 retry (retrying in 10 seconds): Process died prematurely
2021.09.05 22:09:46 1: /dev/ttyAMA0 disconnected, waiting to reappear (myHmUART)
2021.09.05 22:09:47 3: Setting myHmUART serial parameters to 115200,8,N,1
2021.09.05 22:09:47 1: /dev/ttyAMA0 reappeared (myHmUART)
2021.09.05 22:09:52 1: HMUARTLGW myHmUART did not respond for the 1. time, resending
2021.09.05 22:09:55 1: HMUARTLGW myHmUART did not respond for the 2. time, resending
2021.09.05 22:09:58 1: HMUARTLGW myHmUART did not respond for the 3. time, resending
2021.09.05 22:09:59 1: HMUARTLGW myHmUART frame with wrong length received: 24, should: 18: FD000E00010402436F5F4350555F4170015F4350555F417070
2021.09.05 22:10:02 1: HMUARTLGW myHmUART did not respond for the 1. time, resending
2021.09.05 22:10:03 1: HMUARTLGW myHmUART failed to enter App!
2021.09.05 22:10:05 1: HMUARTLGW myHmUART frame with wrong length received: 24, should: 18: FD000E00010402436F5F4350555F4170015F4350555F417070
2021.09.05 22:10:05 1: HMUARTLGW myHmUART did not respond after all, reopening
2021.09.05 22:10:05 3: myHmUART device closed
2021.09.05 22:10:05 3: Setting myHmUART serial parameters to 115200,8,N,1
2021.09.05 22:10:05 1: /dev/ttyAMA0 reappeared (myHmUART)
2021.09.05 22:10:09 1: HMUARTLGW myHmUART did not respond for the 1. time, resending
2021.09.05 22:10:15 3: sduino: KeepAlive, not ok, retry = 3 -> get ping
2021.09.05 22:10:15 1: HMUARTLGW myHmUART invalid checksum received, dropping frame (FD000500100402001850)!
2021.09.05 22:10:42 1: /dev/ttyAMA0 disconnected, waiting to reappear (myHmUART)
2021.09.05 22:10:42 3: Setting myHmUART serial parameters to 115200,8,N,1
2021.09.05 22:10:42 1: /dev/ttyAMA0 reappeared (myHmUART)
2021.09.05 22:10:48 1: HMUARTLGW myHmUART did not respond after all, reopening
2021.09.05 22:10:48 3: myHmUART device closed
2021.09.05 22:10:48 3: Setting myHmUART serial parameters to 115200,8,N,1
2021.09.05 22:10:48 1: /dev/ttyAMA0 reappeared (myHmUART)
2021.09.05 22:10:51 1: /dev/ttyAMA0 disconnected, waiting to reappear (myHmUART)
2021.09.05 22:10:54 3: Setting myHmUART serial parameters to 115200,8,N,1
2021.09.05 22:10:54 1: /dev/ttyAMA0 reappeared (myHmUART)
2021.09.05 22:10:55 1: Timeout for PRESENCE_DoLocalBluetoothScan reached, terminated process 30677
2021.09.05 22:10:55 2: PRESENCE (a51H) - device could not be checked after 3 retries (resuming normal operation): Timeout: process terminated
2021.09.05 22:10:55 2: PRESENCE (a51K) - device could not be checked after 2 retries (retrying in 10 seconds): Process died prematurely
2021.09.05 22:10:58 1: HMUARTLGW myHmUART did not respond for the 1. time, resending
2021.09.05 22:11:01 1: /dev/ttyAMA0 disconnected, waiting to reappear (myHmUART)
2021.09.05 22:11:01 3: Setting myHmUART serial parameters to 115200,8,N,1
2021.09.05 22:11:01 1: /dev/ttyAMA0 reappeared (myHmUART)
2021.09.05 22:11:05 1: HMUARTLGW myHmUART did not respond for the 1. time, resending
2021.09.05 22:11:07 1: HMUARTLGW myHmUART unexpected info about Co_CPU_App received (module crashed?), reopening
2021.09.05 22:11:07 3: myHmUART device closed
2021.09.05 22:11:07 3: Setting myHmUART serial parameters to 115200,8,N,1
2021.09.05 22:11:07 1: /dev/ttyAMA0 reappeared (myHmUART)
2021.09.05 22:11:09 1: HMUARTLGW myHmUART did not respond for the 1. time, resending
2021.09.05 22:11:11 1: HMUARTLGW myHmUART did not respond after all, reopening
2021.09.05 22:11:11 3: myHmUART device closed
2021.09.05 22:11:11 3: Setting myHmUART serial parameters to 115200,8,N,1
2021.09.05 22:11:11 1: /dev/ttyAMA0 reappeared (myHmUART)
2021.09.05 22:11:13 1: HMUARTLGW myHmUART did not respond for the 2. time, resending
2021.09.05 22:11:15 3: sduino: KeepAlive, not ok, retry count reached. Reset
2021.09.05 22:11:15 3: sduino: ResetDevice, nanoCC1101
2021.09.05 22:11:15 3: Opening sduino device /dev/serial/by-id/usb-SHK_SIGNALduino_433-if00-port0
2021.09.05 22:11:15 3: Setting sduino serial parameters to 57600,8,N,1
2021.09.05 22:11:15 1: sduino: DoInit, /dev/serial/by-id/usb-SHK_SIGNALduino_433-if00-port0@57600
2021.09.05 22:11:15 3: sduino device opened
2021.09.05 22:11:17 1: HMUARTLGW myHmUART did not respond for the 3. time, resending
2021.09.05 22:11:17 3: sduino: SimpleWrite_XQ, disable receiver (XQ)
2021.09.05 22:11:17 3: sduino: StartInit, get version, retry = 0
2021.09.05 22:11:17 2: sduino: CheckVersionResp, initialized v3.4.4
2021.09.05 22:11:17 3: sduino: CheckVersionResp, enable receiver (XE)
2021.09.05 22:11:18 1: HMUARTLGW myHmUART did not respond for the 1. time, resending
2021.09.05 22:11:18 1: HMUARTLGW myHmUART unexpected info about Co_CPU_BL received (module crashed?), reopening
2021.09.05 22:11:18 3: myHmUART device closed
2021.09.05 22:11:18 3: Setting myHmUART serial parameters to 115200,8,N,1
2021.09.05 22:11:18 1: /dev/ttyAMA0 reappeared (myHmUART)
2021.09.05 22:11:19 3: sduino: CheckCcpatableResponse, patable: C8
2021.09.05 22:11:20 1: HMUARTLGW myHmUART did not respond after all, reopening
2021.09.05 22:11:20 3: myHmUART device closed
2021.09.05 22:11:20 3: Setting myHmUART serial parameters to 115200,8,N,1
2021.09.05 22:11:20 1: /dev/ttyAMA0 reappeared (myHmUART)
2021.09.05 22:11:22 1: HMUARTLGW myHmUART did not respond for the 1. time, resending
2021.09.05 22:11:23 1: HMUARTLGW myHmUART failed to enter App!
2021.09.05 22:11:25 1: HMUARTLGW myHmUART did not respond after all, reopening
2021.09.05 22:11:25 3: myHmUART device closed
2021.09.05 22:11:25 3: Setting myHmUART serial parameters to 115200,8,N,1
2021.09.05 22:11:25 1: /dev/ttyAMA0 reappeared (myHmUART)
2021.09.05 22:11:26 1: HMUARTLGW myHmUART did not respond for the 1. time, resending
2021.09.05 22:11:26 1: /dev/ttyAMA0 disconnected, waiting to reappear (myHmUART)
2021.09.05 22:11:29 1: HMUARTLGW myHmUART did not respond for the 2. time, resending
2021.09.05 22:11:29 1: HMUARTLGW myHmUART did not respond for the 1. time, resending
2021.09.05 22:11:31 3: Setting myHmUART serial parameters to 115200,8,N,1
2021.09.05 22:11:31 1: /dev/ttyAMA0 reappeared (myHmUART)
2021.09.05 22:11:33 1: HMUARTLGW myHmUART unexpected info about Co_CPU_BL received (module crashed?), reopening
2021.09.05 22:11:33 3: myHmUART device closed
2021.09.05 22:11:33 3: Setting myHmUART serial parameters to 115200,8,N,1
2021.09.05 22:11:33 1: /dev/ttyAMA0 reappeared (myHmUART)
2021.09.05 22:11:35 1: HMUARTLGW myHmUART did not respond after all, reopening
2021.09.05 22:11:35 3: myHmUART device closed
2021.09.05 22:11:35 3: Setting myHmUART serial parameters to 115200,8,N,1
2021.09.05 22:11:35 1: /dev/ttyAMA0 reappeared (myHmUART)
2021.09.05 22:11:37 1: HMUARTLGW myHmUART did not respond for the 1. time, resending
2021.09.05 22:11:37 1: /dev/ttyAMA0 disconnected, waiting to reappear (myHmUART)
2021.09.05 22:11:38 3: Setting myHmUART serial parameters to 115200,8,N,1
2021.09.05 22:11:38 1: /dev/ttyAMA0 reappeared (myHmUART)
2021.09.05 22:11:55 2: PRESENCE (a51K) - device could not be checked after 3 retries (resuming normal operation): Process died prematurely
2021.09.05 22:11:58 1: /dev/ttyAMA0 disconnected, waiting to reappear (myHmUART)
2021.09.05 22:11:58 3: Setting myHmUART serial parameters to 115200,8,N,1
2021.09.05 22:11:58 1: /dev/ttyAMA0 reappeared (myHmUART)
2021.09.05 22:12:26 1: /dev/ttyAMA0 disconnected, waiting to reappear (myHmUART)
2021.09.05 22:12:26 3: Setting myHmUART serial parameters to 115200,8,N,1
2021.09.05 22:12:26 1: /dev/ttyAMA0 reappeared (myHmUART)
2021.09.05 22:12:32 1: /dev/ttyAMA0 disconnected, waiting to reappear (myHmUART)
2021.09.05 22:12:32 3: Setting myHmUART serial parameters to 115200,8,N,1
2021.09.05 22:12:32 1: /dev/ttyAMA0 reappeared (myHmUART)
2021.09.05 22:12:34 1: Timeout for DOIF::doParse reached, terminated process 30509
2021.09.05 22:17:02 3: FBDECT set PC on
2021.09.05 22:17:02 3: ENIGMA2 set Giga on (wakeup)
2021.09.05 22:17:02 2: GigaMitComputerAn: set Giga on: wake-up command sent to MAC 90:98:64:00:90:13
2021.09.05 22:18:32 3: ENIGMA2 set Giga off
2021.09.05 22:22:53 1: HMUARTLGW myHmUART did not respond for the 1. time, resending
2021.09.05 22:22:56 1: HMUARTLGW myHmUART did not respond for the 2. time, resending
2021.09.05 22:22:59 1: HMUARTLGW myHmUART did not respond for the 3. time, resending
2021.09.05 22:23:02 1: HMUARTLGW myHmUART did not respond after all, reopening
2021.09.05 22:23:02 3: Setting myHmUART serial parameters to 115200,8,N,1
2021.09.05 22:23:02 1: /dev/ttyAMA0 reappeared (myHmUART)
2021.09.05 22:23:03 1: /dev/ttyAMA0 disconnected, waiting to reappear (myHmUART)
2021.09.05 22:23:03 3: Setting myHmUART serial parameters to 115200,8,N,1
2021.09.05 22:23:03 1: /dev/ttyAMA0 reappeared (myHmUART)
2021.09.05 22:23:09 1: HMUARTLGW myHmUART did not respond for the 1. time, resending
2021.09.05 22:23:13 1: HMUARTLGW myHmUART did not respond after all, reopening
2021.09.05 22:23:13 3: myHmUART device closed
2021.09.05 22:23:13 3: Setting myHmUART serial parameters to 115200,8,N,1
2021.09.05 22:23:13 1: /dev/ttyAMA0 reappeared (myHmUART)
2021.09.05 22:23:17 2: PRESENCE (a51H) - device could not be checked (retrying in 10 seconds): Process died prematurely
Can't use an undefined value as a HASH reference at (eval 160) line 272.
2021.09.05 22:23:22 1: FRITZBOX Fritzbox: Readout_Aborted.1931 Error: Timeout when reading Fritz!Box data.
2021.09.05 22:23:27 2: hue: http request failed: connect to http://192.168.178.66:80 timed out
2021.09.05 22:23:27 2: PRESENCE (a51K) - device could not be checked (retrying in 10 seconds): Process died prematurely
2021.09.05 22:23:27 2: hue: http request failed: connect to http://192.168.178.66:80 timed out
2021.09.05 22:23:37 2: PRESENCE (a51H) - device could not be checked after 1 retry (retrying in 10 seconds): Process died prematurely
2021.09.05 22:26:18 2: hue: http request failed: read from http://192.168.178.66:80 timed out
2021.09.05 22:26:18 1: Timeout for PRESENCE_DoLocalBluetoothScan reached, terminated process 31373
2021.09.05 22:26:18 2: PRESENCE (a51K) - device could not be checked after 1 retry (retrying in 10 seconds): Timeout: process terminated
2021.09.05 22:26:18 1: Timeout for PRESENCE_DoLocalBluetoothScan reached, terminated process 31394
2021.09.05 22:26:18 2: PRESENCE (a51H) - device could not be checked after 2 retries (retrying in 10 seconds): Timeout: process terminated
2021.09.05 22:26:18 3: sduino: KeepAlive, not ok, retry = 2 -> get ping

Pi3B+ mit SSD/ Bullseye | FB7590 AX | 12 x Dect200 | CUL433+868 | SDuino | HM-LAN | 3 x Heizung FHT + FKontakte | KeyMatic + 4 FB | HM Wandtaster 2-fach m. LED | 6 x Türkont. TFK-TI | HM-Bew.-Melder innen | 3 x Smoked. HM-SEC-SD-2

Invers

Zitat von: KölnSolar am 05 September 2021, 22:30:29
Glaube ich auch. FHEM ist denk ich OK.
Hast Du ein altes Image, welches Du auf einem anderen Bootdatenträger installieren kannst ? Und wenn das läuft Dein aktuelles FHEM einspielen ?

nicht verzagen(auch wenns schwer fällt)
Markus
Edit: Wie und was kopierst Du ?


Ich habe 2 SSDs. Jeden Monat kopiere ich die SSD auf eine andere (Image).
Dann tausche ich die SSDs aus. Eine bleibt dabnn halt als Reservebackup liegen.
Beide laufen nun nicht, wofür es keine Erklärung gibt.
Die aktuelle SSD baegann zu spinnen, da habe ich testweise einfach gegen die Vorgängerversion getauscht. Die zickt aber sofort ebenfalls.

Wenn ich mein System neu boote, dann funktioniert in den ersten 5 Minuten alles, dann geht es los.

Ich habe also somit ein funktionierendes Reserve-System, welches ab heute aber auch nicht funktioniert.


EDI'T:
Acuh mit einem anderen Pi mit anderer SSD - selbes Problem.
Pi3B+ mit SSD/ Bullseye | FB7590 AX | 12 x Dect200 | CUL433+868 | SDuino | HM-LAN | 3 x Heizung FHT + FKontakte | KeyMatic + 4 FB | HM Wandtaster 2-fach m. LED | 6 x Türkont. TFK-TI | HM-Bew.-Melder innen | 3 x Smoked. HM-SEC-SD-2

Christoph Morrison

Und du bist dir ganz sicher, dass das Networking ok ist? Kannst du 192.168.178.66 und a51H pingen?
Wie sieht die Load (Befehl uptime) auf dem System aus? Wie viel RAM ist frei (Befehl free -m)?

Invers

Ja, bin mir sicher.

PS C:\WINDOWS\system32> ping 192.168.178.66

Ping wird ausgeführt für 192.168.178.66 mit 32 Bytes Daten:
Antwort von 192.168.178.66: Bytes=32 Zeit=10ms TTL=64
Antwort von 192.168.178.66: Bytes=32 Zeit=7ms TTL=64
Antwort von 192.168.178.66: Bytes=32 Zeit=3ms TTL=64
Antwort von 192.168.178.66: Bytes=32 Zeit=9ms TTL=64

Ping-Statistik für 192.168.178.66:
    Pakete: Gesendet = 4, Empfangen = 4, Verloren = 0
    (0% Verlust),
Ca. Zeitangaben in Millisek.:
    Minimum = 3ms, Maximum = 10ms, Mittelwert = 7ms
PS C:\WINDOWS\system32>

Ich habe gerade auch die letzte Möglichkeit getestet, die mir einfiel: Ich habe die Stromadapter der SSD getauscht. Auch ohne Erfolg.

Hat denn das Netzwerk was mit HM Uart und Signalduino zu tun?
Ich könnte mir eine neue Fritzbox bestellen und testen, falls das Netzwerk infrage kommt. Der Pi hängt direkt per Kabel an der Fritte.
Pi3B+ mit SSD/ Bullseye | FB7590 AX | 12 x Dect200 | CUL433+868 | SDuino | HM-LAN | 3 x Heizung FHT + FKontakte | KeyMatic + 4 FB | HM Wandtaster 2-fach m. LED | 6 x Türkont. TFK-TI | HM-Bew.-Melder innen | 3 x Smoked. HM-SEC-SD-2

LuckyDay

Netzteil am Pi getauscht

Strom/Spannungsproblem. Kabel zum PI ebenfals getauscht,es sieht so aus als ob kein Netzwerk mehr vorhanden
Ich hatte das mal als nur noch 4,7Volt am PI ankamen! Pi lief noch, Netzwerkchip auf dem PI aber nicht mehr.

Hast du dich mal mit Bildschirmtastatur  direkt am PI angeschlossen?

hajo23

Zitat von: Invers am 05 September 2021, 23:28:12
Ja, bin mir sicher.

PS C:\WINDOWS\system32> ping 192.168.178.66

Ping wird ausgeführt für 192.168.178.66 mit 32 Bytes Daten:
Antwort von 192.168.178.66: Bytes=32 Zeit=10ms TTL=64
Antwort von 192.168.178.66: Bytes=32 Zeit=7ms TTL=64
Antwort von 192.168.178.66: Bytes=32 Zeit=3ms TTL=64
Antwort von 192.168.178.66: Bytes=32 Zeit=9ms TTL=64

Ping-Statistik für 192.168.178.66:
    Pakete: Gesendet = 4, Empfangen = 4, Verloren = 0
    (0% Verlust),
Ca. Zeitangaben in Millisek.:
    Minimum = 3ms, Maximum = 10ms, Mittelwert = 7ms
PS C:\WINDOWS\system32>

Ich habe gerade auch die letzte Möglichkeit getestet, die mir einfiel: Ich habe die Stromadapter der SSD getauscht. Auch ohne Erfolg.

Hat denn das Netzwerk was mit HM Uart und Signalduino zu tun?
Ich könnte mir eine neue Fritzbox bestellen und testen, falls das Netzwerk infrage kommt. Der Pi hängt direkt per Kabel an der Fritte.

den Signalduino hast du per /dev/serial/by-id konfiguriert, den HM Uart aber nicht und der flappt. Sind der Bluetoothdongel und die SSD auch noch USB Geräte? Du solltest alle deine USB-Geräte per /dev/serial/by-id konfigurieren um sicher zu gehen.

MadMax-FHEM

Zitat von: Invers am 05 September 2021, 23:28:12
Ja, bin mir sicher.

PS C:\WINDOWS\system32> ping 192.168.178.66

Ping wird ausgeführt für 192.168.178.66 mit 32 Bytes Daten:
Antwort von 192.168.178.66: Bytes=32 Zeit=10ms TTL=64
Antwort von 192.168.178.66: Bytes=32 Zeit=7ms TTL=64
Antwort von 192.168.178.66: Bytes=32 Zeit=3ms TTL=64
Antwort von 192.168.178.66: Bytes=32 Zeit=9ms TTL=64

Ping-Statistik für 192.168.178.66:
    Pakete: Gesendet = 4, Empfangen = 4, Verloren = 0
    (0% Verlust),
Ca. Zeitangaben in Millisek.:
    Minimum = 3ms, Maximum = 10ms, Mittelwert = 7ms
PS C:\WINDOWS\system32>

Ich habe gerade auch die letzte Möglichkeit getestet, die mir einfiel: Ich habe die Stromadapter der SSD getauscht. Auch ohne Erfolg.

Hat denn das Netzwerk was mit HM Uart und Signalduino zu tun?
Ich könnte mir eine neue Fritzbox bestellen und testen, falls das Netzwerk infrage kommt. Der Pi hängt direkt per Kabel an der Fritte.

Mit geht ping war aber (stark vermutend) gemeint vom PI aus, nicht generell (also z.B. von "irgendeinem" Windows PC aus)... ;)

Gruß, Joachim
FHEM PI3B+ Bullseye: HM-CFG-USB, 40x HM, ZWave-USB, 13x ZWave, EnOcean-PI, 15x EnOcean, HUE/deCONZ, CO2, ESP-Multisensor, Shelly, alexa-fhem, ...
FHEM PI2 Buster: HM-CFG-USB, 25x HM, ZWave-USB, 4x ZWave, EnOcean-PI, 3x EnOcean, Shelly, ha-bridge, ...
FHEM PI3 Buster (Test)

Invers

Ein Spannungsproblem schliesse ich aus. Das Kabel hängt ja am Netzteil und somit wurde beides getauscht. Sogar ein Ferritkern ist drum.
Auf den Pi greife ich nur mit Putty zu.


Der UART steckt nicht am USB. Der steckt auf den GPIOs. Aber auch, wenn ich ihn abziehe und deinstalliere, bekomme ich Fehlermeldungen pohne Ende.


Der Ping war nicht vom Pi aus, aber dieser hier schon:
pi@fhem3:~ $ ping 192.168.178.50
PING 192.168.178.50 (192.168.178.50) 56(84) bytes of data.
64 bytes from 192.168.178.50: icmp_seq=1 ttl=64 time=1253 ms
64 bytes from 192.168.178.50: icmp_seq=2 ttl=64 time=214 ms
64 bytes from 192.168.178.50: icmp_seq=3 ttl=64 time=172 ms
64 bytes from 192.168.178.50: icmp_seq=4 ttl=64 time=84.7 ms
64 bytes from 192.168.178.50: icmp_seq=5 ttl=64 time=672 ms
64 bytes from 192.168.178.50: icmp_seq=6 ttl=64 time=85.0 ms
64 bytes from 192.168.178.50: icmp_seq=7 ttl=64 time=157 ms
64 bytes from 192.168.178.50: icmp_seq=8 ttl=64 time=1004 ms
64 bytes from 192.168.178.50: icmp_seq=9 ttl=64 time=22.4 ms
64 bytes from 192.168.178.50: icmp_seq=10 ttl=64 time=346 ms
64 bytes from 192.168.178.50: icmp_seq=11 ttl=64 time=148 ms
64 bytes from 192.168.178.50: icmp_seq=12 ttl=64 time=715 ms
64 bytes from 192.168.178.50: icmp_seq=13 ttl=64 time=82.4 ms
64 bytes from 192.168.178.50: icmp_seq=14 ttl=64 time=103 ms
64 bytes from 192.168.178.50: icmp_seq=15 ttl=64 time=225 ms
64 bytes from 192.168.178.50: icmp_seq=16 ttl=64 time=49.6 ms
^X64 bytes from 192.168.178.50: icmp_seq=17 ttl=64 time=997 ms
64 bytes from 192.168.178.50: icmp_seq=18 ttl=64 time=5.60 ms



alles per /dev/serial/by-id konfiguriert.
Pi3B+ mit SSD/ Bullseye | FB7590 AX | 12 x Dect200 | CUL433+868 | SDuino | HM-LAN | 3 x Heizung FHT + FKontakte | KeyMatic + 4 FB | HM Wandtaster 2-fach m. LED | 6 x Türkont. TFK-TI | HM-Bew.-Melder innen | 3 x Smoked. HM-SEC-SD-2