ZitatWhat do you think about that? Could it be enough to trigger the watchdog?I think it will not help. FHEM is still running, I assume.
Zitat von: KölnSolar am 03 Juni 2026, 15:46:41I had a lot of problems setting up a rpi3 with Trixie, which worked with older debian.
ZitatMain Problem were the USBs which are connected to the ethernet port. Thats possibly the cause not rebooting by the watchdog, because the system is still Running but network isn't working.
With a new rpi5 my problems were gone. The network is separated from the USBs !
Regards
Markus
Zitat von: Kai-Alfonso am 03 Juni 2026, 15:45:02Habe jetzt alle Kommandos getestet. Scheint alles zu gehen, wie es soll - nur wenn Rollingcode auf 5 steht, kommt kein Befehl an. Bei allen anderen Rolling Codes geht es.
Internals:
DEF CREATE_6601L FB684
FUUID 6a202e80-f33f-ce3b-3c5f-9f48595b71b5f8fe
FVERSION 14_SD_UT.pm:v1.0.11-s0/2026-02-18
IODev SIGNALesp
NAME CREATE_6601L_FB684
NR 559
STATE beeper_on_off
TYPE SD_UT
bitMSG no data
eventCount 42
lastMSG no data
READINGS:
2026-06-03 15:39:12 IODev SIGNALesp
2026-06-03 15:44:35 LastAction send
2026-06-03 15:44:35 rollingCode 2
2026-06-03 15:44:35 state beeper_on_off
Attributes:
model CREATE_6601L
room Geräte-Inbox