Keine stabile FRITZBOX Verbindung

@tango · 23 Januar 2026, 14:51:55

Hallo,
ich bin mir nicht sicher, ob das ein neues Problem ist oder ein altes.
Betrifft

# $Id: 72_FRITZBOX.pm 30731 2026-01-12 13:35:18Z jowiemann $

Ich habe die Diskussionen mit der unsicheren Verbindung zur Fritzbox (bei mir 7590) und den Repeatern (bei mir 2x2400) bisher verfolgt und hatte gehofft, das mit dem letzten update Ruhe einkehrt.
Aber meine Logs sind weiter voll mit Fehlermeldungen.
Hier der anonymisierte Ausschnitt von heute morgen:

Code Auswählen

2026.01.23 00:21:11 2: [XX_FRITZBOX | 7590 | 154.08.21 | call_Lua_Query.15722] - SIGNIFICANT:500 Can't connect to 192.xxx.xxx.1:80 (Network is unreachable)
2026.01.23 00:21:11 2: [XX_FRITZBOX | 7590 | 154.08.21 | Readout_Response.8684] - SIGNIFICANT:500 Can't connect to 192.xxx.xxx.1:80 (Network is unreachable) - Readout_Run_Web_LuaQuery(5140)
2026.01.23 00:21:11 2: [XX_FRITZBOX | 7590 | 154.08.21 | Readout_Response.8684] - SIGNIFICANT:500 Can't connect to 192.xxx.xxx.1:80 (Network is unreachable) - Readout_Run_Web_LuaData(6091)
2026.01.23 00:21:11 3: XX_FBAHAHTTP: gethostbyname fritz.box failed
2026.01.23 00:21:11 3: [XX_FRITZBOX | 7590 | 154.08.21 | Readout_Run_Web_TR064.8460] - BASIC:wanpppconn1 - no GetInfoResponse getting TR064 data
2026.01.23 00:22:04 2: [XX_FritzRepeater1 | 2400 | 169.08.20 | call_Lua_Query.15722] - SIGNIFICANT:500 Can't connect to 192.xxx.xxx.2:80 (No route to host)
2026.01.23 00:22:04 2: [XX_FritzRepeater1 | 2400 | 169.08.20 | Readout_Response.8684] - SIGNIFICANT:500 Can't connect to 192.xxx.xxx.2:80 (No route to host) - Readout_Run_Web_LuaQuery(5140)
2026.01.23 00:22:09 2: [XX_FritzRepeater1 | 2400 | 169.08.20 | Readout_Response.8684] - SIGNIFICANT:500 Can't connect to 192.xxx.xxx.2:80 (Network is unreachable) - Readout_Run_Web_LuaData(6091)
2026.01.23 00:24:35 3: [XX_FRITZBOX | 7590 | 154.08.21 | Readout_API_Check.10025] - BASIC:Response -> luaQuery:200 luaData:200 TR064:200
2026.01.23 00:26:05 3: [XX_FritzRepeater1 | 2400 | 169.08.20 | Readout_API_Check.10025] - BASIC:Response -> luaQuery:200 luaData:200 TR064:200 boxModelJason:200
2026.01.23 00:26:21 2: XX_FBAHAHTTP ERROR: cannot get SID, check connection/hostname/fritzbox-user/password
2026.01.23 00:27:16 3: Timeout for FRITZBOX_Readout_Run_Web reached, terminated process 17112
2026.01.23 00:27:16 2: [XX_FritzRepeater2 | 2400 | 169.08.20 | Readout_Aborted.9123] - SIGNIFICANT:Error: [285 | BlockingKill] Timeout reading Fritz!Box data.
2026.01.23 00:34:05 2: [XX_FritzRepeater1 | 2400 | 169.08.20 | call_Lua_Query.15722] - SIGNIFICANT:500 Can't connect to 192.xxx.xxx.2:80 (Network is unreachable)
2026.01.23 00:34:05 2: [XX_FritzRepeater1 | 2400 | 169.08.20 | Readout_Response.8684] - SIGNIFICANT:500 Can't connect to 192.xxx.xxx.2:80 (Network is unreachable) - Readout_Run_Web_LuaQuery(5140)
2026.01.23 00:34:05 2: [XX_FritzRepeater1 | 2400 | 169.08.20 | Readout_Response.8684] - SIGNIFICANT:500 Can't connect to 192.xxx.xxx.2:80 (Network is unreachable) - Readout_Run_Web_LuaData(6091)
2026.01.23 00:38:13 3: [XX_FritzRepeater1 | 2400 | 169.08.20 | Readout_API_Check.10025] - BASIC:Response -> luaQuery:200 luaData:200 TR064:200 boxModelJason:200
2026.01.23 00:43:09 3: [XX_FRITZBOX | 7590 | 154.08.21 | Readout_Run_Web_TR064.8460] - BASIC:wanpppconn1 - no GetInfoResponse getting TR064 data
..
2026.01.23 00:57:28 3: XX_FBAHAHTTP: gethostbyname fritz.box failed
2026.01.23 00:57:40 2: [XX_FRITZBOX | 7590 | 154.08.21 | call_Lua_Query.15722] - SIGNIFICANT:500 Can't connect to 192.xxx.xxx.1:80 (Network is unreachable)
2026.01.23 00:57:40 2: [XX_FRITZBOX | 7590 | 154.08.21 | Readout_Response.8684] - SIGNIFICANT:500 Can't connect to 192.xxx.xxx.1:80 (Network is unreachable) - Readout_Run_Web_LuaQuery(5140)
2026.01.23 00:57:40 2: [XX_FRITZBOX | 7590 | 154.08.21 | Readout_Response.8684] - SIGNIFICANT:500 Can't connect to 192.xxx.xxx.1:80 (Network is unreachable) - Readout_Run_Web_LuaData(6091)
2026.01.23 00:57:41 3: [XX_FRITZBOX | 7590 | 154.08.21 | Readout_Run_Web_TR064.8460] - BASIC:wanpppconn1 - no GetInfoResponse getting TR064 data
..
2026.01.23 01:01:00 3: [XX_FRITZBOX | 7590 | 154.08.21 | Readout_API_Check.10025] - BASIC:Response -> luaQuery:200 luaData:200 TR064:200
2026.01.23 01:04:00 2: [XX_FRITZBOX | 7590 | 154.08.21 | call_Lua_Query.15722] - SIGNIFICANT:500 Can't connect to 192.xxx.xxx.1:80 (Network is unreachable)
2026.01.23 01:04:00 2: [XX_FRITZBOX | 7590 | 154.08.21 | Readout_Response.8684] - SIGNIFICANT:500 Can't connect to 192.xxx.xxx.1:80 (Network is unreachable) - Readout_Run_Web_LuaQuery(5140)
2026.01.23 01:04:00 2: [XX_FRITZBOX | 7590 | 154.08.21 | Readout_Response.8684] - SIGNIFICANT:500 Can't connect to 192.xxx.xxx.1:80 (Network is unreachable) - Readout_Run_Web_LuaData(6091)
2026.01.23 01:04:00 3: [XX_FRITZBOX | 7590 | 154.08.21 | Readout_Run_Web_TR064.8460] - BASIC:wanpppconn1 - no GetInfoResponse getting TR064 data
2026.01.23 01:07:24 3: [XX_FRITZBOX | 7590 | 154.08.21 | Readout_API_Check.10025] - BASIC:Response -> luaQuery:200 luaData:200 TR064:200
2026.01.23 01:10:21 2: [XX_FritzRepeater2 | 2400 | 169.08.20 | call_Lua_Query.15722] - SIGNIFICANT:500 Can't connect to 192.xxx.xxx.3:80 (Network is unreachable)
2026.01.23 01:10:21 2: [XX_FritzRepeater2 | 2400 | 169.08.20 | Readout_Response.8684] - SIGNIFICANT:500 Can't connect to 192.xxx.xxx.3:80 (Network is unreachable) - Readout_Run_Web_LuaQuery(5140)
2026.01.23 01:10:21 2: [XX_FritzRepeater2 | 2400 | 169.08.20 | Readout_Response.8684] - SIGNIFICANT:500 Can't connect to 192.xxx.xxx.3:80 (Network is unreachable) - Readout_Run_Web_LuaData(6091)
2026.01.23 01:10:24 2: [XX_FRITZBOX | 7590 | 154.08.21 | call_Lua_Query.15722] - SIGNIFICANT:500 Can't connect to 192.xxx.xxx.1:80 (Network is unreachable)
2026.01.23 01:10:24 2: [XX_FRITZBOX | 7590 | 154.08.21 | Readout_Response.8684] - SIGNIFICANT:500 Can't connect to 192.xxx.xxx.1:80 (Network is unreachable) - Readout_Run_Web_LuaQuery(5140)
2026.01.23 01:10:24 2: [XX_FRITZBOX | 7590 | 154.08.21 | Readout_Response.8684] - SIGNIFICANT:500 Can't connect to 192.xxx.xxx.1:80 (Network is unreachable) - Readout_Run_Web_LuaData(6091)
2026.01.23 01:10:24 3: [XX_FRITZBOX | 7590 | 154.08.21 | Readout_Run_Web_TR064.8460] - BASIC:wanpppconn1 - no GetInfoResponse getting TR064 data
2026.01.23 01:11:08 3: Timeout for FRITZBOX_Readout_Run_Web reached, terminated process 19432
2026.01.23 01:11:08 2: [XX_FritzRepeater1 | 2400 | 169.08.20 | Readout_Aborted.9123] - SIGNIFICANT:Error: [285 | BlockingKill] Timeout reading Fritz!Box data.
2026.01.23 01:13:39 2: [XX_FRITZBOX | 7590 | 154.08.21 | open_Web_Connection.15630] - SIGNIFICANT:Web connection could not be established. Please check your credentials (password, user).
2026.01.23 01:13:39 3: [XX_FRITZBOX | 7590 | 154.08.21 | Readout_API_Check.10025] - BASIC:Response -> luaQuery: empty sid error: Web connection could not be established
2026.01.23 01:13:40 3: [XX_FRITZBOX | 7590 | 154.08.21 | Readout_API_Check.10025] - BASIC:Response -> luaQuery:500 luaData:500 TR064:500
2026.01.23 01:13:40 3: [XX_FRITZBOX | 7590 | 154.08.21 | Readout_API_Check.10025] - BASIC:Response -> luaQuery:500 luaData:500 TR064:500
2026.01.23 01:13:40 3: [XX_FRITZBOX | 7590 | 154.08.21 | Readout_API_Check.10025] - BASIC:Response -> luaQuery:500 luaData:500 TR064:500
2026.01.23 01:13:40 3: [XX_FRITZBOX | 7590 | 154.08.21 | Readout_API_Check.10025] - BASIC:Response -> luaQuery:500 luaData:500 TR064:500
2026.01.23 01:13:40 3: [XX_FRITZBOX | 7590 | 154.08.21 | Readout_API_Check.10025] - BASIC:Response -> luaQuery:500 luaData:500 TR064:500
2026.01.23 01:13:40 2: [XX_FRITZBOX | 7590 | 154.08.21 | Readout_Start.4927] - SIGNIFICANT:stopped while to many network errors
2026.01.23 01:14:29 3: [XX_FritzRepeater2 | 2400 | 169.08.20 | Readout_API_Check.10025] - BASIC:Response -> luaQuery:200 luaData:200 TR064:200 boxModelJason:200
2026.01.23 01:46:20 2: [XX_FritzRepeater1 | 2400 | 169.08.20 | call_Lua_Query.15722] - SIGNIFICANT:500 Can't connect to 192.xxx.xxx.2:80 (No route to host)
2026.01.23 01:46:20 2: [XX_FritzRepeater1 | 2400 | 169.08.20 | Readout_Response.8684] - SIGNIFICANT:500 Can't connect to 192.xxx.xxx.2:80 (No route to host) - Readout_Run_Web_LuaQuery(5140)
2026.01.23 01:46:25 2: [XX_FritzRepeater1 | 2400 | 169.08.20 | Readout_Response.8684] - SIGNIFICANT:500 Can't connect to 192.xxx.xxx.2:80 (Network is unreachable) - Readout_Run_Web_LuaData(6091)
2026.01.23 01:46:30 2: [XX_FritzRepeater2 | 2400 | 169.08.20 | call_Lua_Query.15722] - SIGNIFICANT:500 Can't connect to 192.xxx.xxx.3:80 (Network is unreachable)
2026.01.23 01:46:30 2: [XX_FritzRepeater2 | 2400 | 169.08.20 | Readout_Response.8684] - SIGNIFICANT:500 Can't connect to 192.xxx.xxx.3:80 (Network is unreachable) - Readout_Run_Web_LuaQuery(5140)
2026.01.23 01:46:30 2: [XX_FritzRepeater2 | 2400 | 169.08.20 | Readout_Response.8684] - SIGNIFICANT:500 Can't connect to 192.xxx.xxx.3:80 (Network is unreachable) - Readout_Run_Web_LuaData(6091)
2026.01.23 01:50:22 3: [XX_FritzRepeater1 | 2400 | 169.08.20 | Readout_API_Check.10025] - BASIC:Response -> luaQuery:200 luaData:200 TR064:200 boxModelJason:200
2026.01.23 01:50:37 3: [XX_FritzRepeater2 | 2400 | 169.08.20 | Readout_API_Check.10025] - BASIC:Response -> luaQuery:200 luaData:200 TR064:200 boxModelJason:200
2026.01.23 01:58:27 2: [XX_FritzRepeater1 | 2400 | 169.08.20 | call_Lua_Query.15722] - SIGNIFICANT:500 Can't connect to 192.xxx.xxx.2:80 (Network is unreachable)
2026.01.23 01:58:27 2: [XX_FritzRepeater1 | 2400 | 169.08.20 | Readout_Response.8684] - SIGNIFICANT:500 Can't connect to 192.xxx.xxx.2:80 (Network is unreachable) - Readout_Run_Web_LuaQuery(5140)
2026.01.23 01:58:27 2: [XX_FritzRepeater1 | 2400 | 169.08.20 | Readout_Response.8684] - SIGNIFICANT:500 Can't connect to 192.xxx.xxx.2:80 (Network is unreachable) - Readout_Run_Web_LuaData(6091)
2026.01.23 01:58:43 2: [XX_FritzRepeater2 | 2400 | 169.08.20 | call_Lua_Query.15722] - SIGNIFICANT:500 Can't connect to 192.xxx.xxx.3:80 (Network is unreachable)
2026.01.23 01:58:43 2: [XX_FritzRepeater2 | 2400 | 169.08.20 | Readout_Response.8684] - SIGNIFICANT:500 Can't connect to 192.xxx.xxx.3:80 (Network is unreachable) - Readout_Run_Web_LuaQuery(5140)
2026.01.23 01:58:43 2: [XX_FritzRepeater2 | 2400 | 169.08.20 | Readout_Response.8684] - SIGNIFICANT:500 Can't connect to 192.xxx.xxx.3:80 (Network is unreachable) - Readout_Run_Web_LuaData(6091)
..
2026.01.23 02:02:30 3: [XX_FritzRepeater1 | 2400 | 169.08.20 | Readout_API_Check.10025] - BASIC:Response -> luaQuery:200 luaData:200 TR064:200 boxModelJason:200
2026.01.23 02:02:46 3: [XX_FritzRepeater2 | 2400 | 169.08.20 | Readout_API_Check.10025] - BASIC:Response -> luaQuery:200 luaData:200 TR064:200 boxModelJason:200
2026.01.23 02:17:37 3: XX_FBAHAHTTP: gethostbyname fritz.box failed
..
2026.01.23 03:02:30 2: [XX_FritzRepeater1 | 2400 | 169.08.20 | call_Lua_Query.15722] - SIGNIFICANT:500 Can't connect to 192.xxx.xxx.2:80 (Network is unreachable)
2026.01.23 03:02:30 2: [XX_FritzRepeater1 | 2400 | 169.08.20 | Readout_Response.8684] - SIGNIFICANT:500 Can't connect to 192.xxx.xxx.2:80 (Network is unreachable) - Readout_Run_Web_LuaQuery(5140)
2026.01.23 03:02:30 2: [XX_FritzRepeater1 | 2400 | 169.08.20 | Readout_Response.8684] - SIGNIFICANT:500 Can't connect to 192.xxx.xxx.2:80 (Network is unreachable) - Readout_Run_Web_LuaData(6091)
2026.01.23 03:02:38 3: XX_FBAHAHTTP: gethostbyname fritz.box failed
2026.01.23 03:02:56 2: [XX_FritzRepeater2 | 2400 | 169.08.20 | call_Lua_Query.15722] - SIGNIFICANT:500 Can't connect to 192.xxx.xxx.3:80 (No route to host)
2026.01.23 03:02:56 2: [XX_FritzRepeater2 | 2400 | 169.08.20 | Readout_Response.8684] - SIGNIFICANT:500 Can't connect to 192.xxx.xxx.3:80 (No route to host) - Readout_Run_Web_LuaQuery(5140)
2026.01.23 03:03:01 2: [XX_FritzRepeater2 | 2400 | 169.08.20 | Readout_Response.8684] - SIGNIFICANT:500 Can't connect to 192.xxx.xxx.3:80 (Network is unreachable) - Readout_Run_Web_LuaData(6091)
2026.01.23 03:06:30 3: [XX_FritzRepeater1 | 2400 | 169.08.20 | Readout_API_Check.10025] - BASIC:Response -> luaQuery:500 luaData:500 TR064:500
2026.01.23 03:06:30 3: [XX_FritzRepeater1 | 2400 | 169.08.20 | Readout_API_Check.10025] - BASIC:Response -> luaQuery:500 luaData:500 TR064:500
2026.01.23 03:06:30 3: [XX_FritzRepeater1 | 2400 | 169.08.20 | Readout_API_Check.10025] - BASIC:Response -> luaQuery:500 luaData:500 TR064:500
2026.01.23 03:06:31 3: [XX_FritzRepeater1 | 2400 | 169.08.20 | Readout_API_Check.10025] - BASIC:Response -> luaQuery:500 luaData:500 TR064:500
2026.01.23 03:06:31 3: [XX_FritzRepeater1 | 2400 | 169.08.20 | Readout_API_Check.10025] - BASIC:Response -> luaQuery:500 luaData:500 TR064:500
2026.01.23 03:06:31 2: [XX_FritzRepeater1 | 2400 | 169.08.20 | Readout_Start.4927] - SIGNIFICANT:stopped while to many network errors
2026.01.23 03:06:54 3: [XX_FritzRepeater2 | 2400 | 169.08.20 | Readout_API_Check.10025] - BASIC:Response -> luaQuery:200 luaData:200 TR064:200 boxModelJason:200
2026.01.23 03:14:54 2: [XX_FritzRepeater2 | 2400 | 169.08.20 | call_Lua_Query.15722] - SIGNIFICANT:500 Can't connect to 192.xxx.xxx.3:80 (Network is unreachable)
2026.01.23 03:14:54 2: [XX_FritzRepeater2 | 2400 | 169.08.20 | Readout_Response.8684] - SIGNIFICANT:500 Can't connect to 192.xxx.xxx.3:80 (Network is unreachable) - Readout_Run_Web_LuaQuery(5140)
2026.01.23 03:14:55 2: [XX_FritzRepeater2 | 2400 | 169.08.20 | Readout_Response.8684] - SIGNIFICANT:500 Can't connect to 192.xxx.xxx.3:80 (Network is unreachable) - Readout_Run_Web_LuaData(6091)
2026.01.23 03:19:02 3: [XX_FritzRepeater2 | 2400 | 169.08.20 | Readout_API_Check.10025] - BASIC:Response -> luaQuery:200 luaData:200 TR064:200 boxModelJason:200
2026.01.23 03:38:11 3: XX_FBAHAHTTP: gethostbyname fritz.box failed
2026.01.23 03:43:03 2: [XX_FritzRepeater2 | 2400 | 169.08.20 | call_Lua_Query.15722] - SIGNIFICANT:500 Can't connect to 192.xxx.xxx.3:80 (Network is unreachable)
2026.01.23 03:43:03 2: [XX_FritzRepeater2 | 2400 | 169.08.20 | Readout_Response.8684] - SIGNIFICANT:500 Can't connect to 192.xxx.xxx.3:80 (Network is unreachable) - Readout_Run_Web_LuaQuery(5140)
2026.01.23 03:43:03 2: [XX_FritzRepeater2 | 2400 | 169.08.20 | Readout_Response.8684] - SIGNIFICANT:500 Can't connect to 192.xxx.xxx.3:80 (Network is unreachable) - Readout_Run_Web_LuaData(6091)
2026.01.23 03:43:24 2: XX_FBAHAHTTP ERROR: cannot get SID, check connection/hostname/fritzbox-user/password
2026.01.23 03:47:10 3: [XX_FritzRepeater2 | 2400 | 169.08.20 | Readout_API_Check.10025] - BASIC:Response -> luaQuery:200 luaData:200 TR064:200 boxModelJason:200
2026.01.23 03:51:21 2: [XX_FritzRepeater2 | 2400 | 169.08.20 | call_Lua_Query.15722] - SIGNIFICANT:500 Can't connect to 192.xxx.xxx.3:80 (No route to host)
2026.01.23 03:51:21 2: [XX_FritzRepeater2 | 2400 | 169.08.20 | Readout_Response.8684] - SIGNIFICANT:500 Can't connect to 192.xxx.xxx.3:80 (No route to host) - Readout_Run_Web_LuaQuery(5140)
2026.01.23 03:55:18 3: [XX_FritzRepeater2 | 2400 | 169.08.20 | Readout_API_Check.10025] - BASIC:Response -> luaQuery:200 luaData:200 TR064:200 boxModelJason:200
..
2026.01.23 04:16:14 3: Timeout for FRITZBOX_Readout_Run_Web reached, terminated process 30061
2026.01.23 04:16:14 2: [XX_FritzRepeater2 | 2400 | 169.08.20 | Readout_Aborted.9123] - SIGNIFICANT:Error: [285 | BlockingKill] Timeout reading Fritz!Box data.
2026.01.23 04:19:19 2: [XX_FritzRepeater2 | 2400 | 169.08.20 | call_Lua_Query.15722] - SIGNIFICANT:500 Can't connect to 192.xxx.xxx.3:80 (Network is unreachable)
2026.01.23 04:19:19 2: [XX_FritzRepeater2 | 2400 | 169.08.20 | Readout_Response.8684] - SIGNIFICANT:500 Can't connect to 192.xxx.xxx.3:80 (Network is unreachable) - Readout_Run_Web_LuaQuery(5140)
2026.01.23 04:19:19 2: [XX_FritzRepeater2 | 2400 | 169.08.20 | Readout_Response.8684] - SIGNIFICANT:500 Can't connect to 192.xxx.xxx.3:80 (Network is unreachable) - Readout_Run_Web_LuaData(6091)
2026.01.23 04:23:28 3: [XX_FritzRepeater2 | 2400 | 169.08.20 | Readout_API_Check.10025] - BASIC:Response -> luaQuery:200 luaData:200 TR064:200 boxModelJason:200
2026.01.23 04:29:31 3: XX_FBAHAHTTP: gethostbyname fritz.box failed
..
2026.01.23 04:55:35 2: [XX_FritzRepeater2 | 2400 | 169.08.20 | call_Lua_Query.15722] - SIGNIFICANT:500 Can't connect to 192.xxx.xxx.3:80 (No route to host)
2026.01.23 04:55:35 2: [XX_FritzRepeater2 | 2400 | 169.08.20 | Readout_Response.8684] - SIGNIFICANT:500 Can't connect to 192.xxx.xxx.3:80 (No route to host) - Readout_Run_Web_LuaQuery(5140)
2026.01.23 04:55:40 2: [XX_FritzRepeater2 | 2400 | 169.08.20 | Readout_Response.8684] - SIGNIFICANT:500 Can't connect to 192.xxx.xxx.3:80 (Network is unreachable) - Readout_Run_Web_LuaData(6091)
..
2026.01.23 04:59:37 3: [XX_FritzRepeater2 | 2400 | 169.08.20 | Readout_API_Check.10025] - BASIC:Response -> luaQuery:200 luaData:200 TR064:200 boxModelJason:200
..
2026.01.23 05:09:37 3: XX_FBAHAHTTP: gethostbyname fritz.box failed
..
2026.01.23 05:56:03 2: [XX_FritzRepeater2 | 2400 | 169.08.20 | call_Lua_Query.15722] - SIGNIFICANT:500 Can't connect to 192.xxx.xxx.3:80 (No route to host)
2026.01.23 05:56:03 2: [XX_FritzRepeater2 | 2400 | 169.08.20 | Readout_Response.8684] - SIGNIFICANT:500 Can't connect to 192.xxx.xxx.3:80 (No route to host) - Readout_Run_Web_LuaQuery(5140)
2026.01.23 05:59:37 3: [XX_FritzRepeater2 | 2400 | 169.08.20 | Readout_API_Check.10025] - BASIC:Response -> luaQuery:500 luaData:500 TR064:500
2026.01.23 05:59:38 3: [XX_FritzRepeater2 | 2400 | 169.08.20 | Readout_API_Check.10025] - BASIC:Response -> luaQuery:500 luaData:500 TR064:500
2026.01.23 05:59:38 3: [XX_FritzRepeater2 | 2400 | 169.08.20 | Readout_API_Check.10025] - BASIC:Response -> luaQuery:500 luaData:500 TR064:500
2026.01.23 05:59:38 3: [XX_FritzRepeater2 | 2400 | 169.08.20 | Readout_API_Check.10025] - BASIC:Response -> luaQuery:500 luaData:500 TR064:500
2026.01.23 05:59:38 3: [XX_FritzRepeater2 | 2400 | 169.08.20 | Readout_API_Check.10025] - BASIC:Response -> luaQuery:500 luaData:500 TR064:500
2026.01.23 05:59:38 2: [XX_FritzRepeater2 | 2400 | 169.08.20 | Readout_Start.4927] - SIGNIFICANT:stopped while to many network errors
..
2026.01.23 07:20:00 3: FBDECT set EZ_Stehlampe on
2026.01.23 07:20:00 3: FBDECT set GA_Hase on
..
2026.01.23 07:20:01 3: FBDECT set WZ_Couchtischlampe on
..
2026.01.23 13:21:03 3: XX_FBAHAHTTP: gethostbyname fritz.box failed
2026.01.23 13:51:10 3: XX_FBAHAHTTP: gethostbyname fritz.box failed
2026.01.23 13:53:25 3: [XX_FRITZBOX | 7590 | 154.08.21 | Set.1932] - BASIC:set XX_FRITZBOX checkAPIs - full
2026.01.23 13:53:40 2: [XX_FRITZBOX | 7590 | 154.08.21 | open_Web_Connection.15630] - SIGNIFICANT:Web connection could not be established. Please check your credentials (password, user).
2026.01.23 13:53:40 3: [XX_FRITZBOX | 7590 | 154.08.21 | Readout_API_Check.10025] - BASIC:Response -> luaQuery: empty sid error: Web connection could not be established
2026.01.23 13:53:40 3: [XX_FRITZBOX | 7590 | 154.08.21 | Readout_API_Check.10025] - BASIC:Response -> luaQuery:500 luaData:500 TR064:500
2026.01.23 13:53:40 3: [XX_FRITZBOX | 7590 | 154.08.21 | Readout_API_Check.10025] - BASIC:Response -> luaQuery:500 luaData:500 TR064:500
2026.01.23 13:53:40 3: [XX_FRITZBOX | 7590 | 154.08.21 | Readout_API_Check.10025] - BASIC:Response -> luaQuery:500 luaData:500 TR064:500
2026.01.23 13:53:40 3: [XX_FRITZBOX | 7590 | 154.08.21 | Readout_API_Check.10025] - BASIC:Response -> luaQuery:500 luaData:500 TR064:500
2026.01.23 13:53:41 3: [XX_FRITZBOX | 7590 | 154.08.21 | Readout_API_Check.10025] - BASIC:Response -> luaQuery:500 luaData:500 TR064:500
2026.01.23 13:53:41 2: [XX_FRITZBOX | 7590 | 154.08.21 | Readout_Start.4927] - SIGNIFICANT:stopped while to many network errors
2026.01.23 13:54:32 2: [XX_FRITZBOX | 7590 | 154.08.21 | Readout_Start.4927] - SIGNIFICANT:stopped while to many network errors
2026.01.23 13:54:32 2: [XX_FRITZBOX | 7590 | 154.08.21 | Helper_retMsg.1903] - SIGNIFICANT:location: 2019 | Msg: ERROR: starting ReadOutTimer not possible: network error.
2026.01.23 13:54:48 3: [XX_FRITZBOX | 7590 | 154.08.21 | Set.1932] - BASIC:set XX_FRITZBOX checkAPIs - full
2026.01.23 13:54:56 3: [XX_FRITZBOX | 7590 | 154.08.21 | Readout_API_Check.10025] - BASIC:Response -> luaQuery:200 luaData:200 TR064:200
2026.01.23 13:55:01 3: [XX_FRITZBOX | 7590 | 154.08.21 | Readout_Start.4965] - BASIC:Old readout process still running. Killing old process HASH(0x559d3cd598)
2026.01.23 13:55:01 3: Timeout for FRITZBOX_Readout_Run_Web reached, terminated process 59878
2026.01.23 13:55:01 2: [XX_FRITZBOX | 7590 | 154.08.21 | Readout_Aborted.9123] - SIGNIFICANT:Error: [285 | BlockingKill] Timeout reading Fritz!Box data.
2026.01.23 13:55:59 3: [XX_FRITZBOX | 7590 | 154.08.21 | Set.1932] - BASIC:set XX_FRITZBOX guestWlan - on

Nach mehrfachem Aufruf von set checkAPIs bzw. set update scheint etwas Ruhe einzutreten!?

Das Attribute disableHostIPv4check ist eingeschaltet.
Andernfalls werden die Fehlermeldungen noch häufiger.
Fritzbox Einstellungen etwa "set guestWlan on" funktionieren trotzallem.

Meine FRITZBOX Definition:

Code Auswählen

define XX_FRITZBOX FRITZBOX 192.xxx.xxx.1
attr XX_FRITZBOX INTERVAL 180
attr XX_FRITZBOX alias Fritzbox
attr XX_FRITZBOX boxUser gg
attr XX_FRITZBOX devStateIcon Wlan.on:WLAN_Status.1:wOff Wlan.off:WLAN_Status.0:wOn\
Gast.on:WLAN_Status.1:gOff Gast.off:WLAN_Status.0:gOn
attr XX_FRITZBOX disableBoxReadings box_IPv6_Extern,box_IPv6_Prefix,box_IPv6_Valid,box_IPv6_Uptime
attr XX_FRITZBOX disableDectInfo 1
attr XX_FRITZBOX disableFonInfo 1
attr XX_FRITZBOX disableHostIPv4check 1
attr XX_FRITZBOX enableAlarmInfo 0
attr XX_FRITZBOX enableUserInfo 0
attr XX_FRITZBOX event-on-change-reading state,box_guestWlan,box_wlan_2.4GHz,box_wlan_5GHz
attr XX_FRITZBOX event-on-update-reading mac_.*
attr XX_FRITZBOX eventMap /Wlan on:wOn/Wlan off:wOff/guestWlan on:gOn/guestWlan off:gOff/
attr XX_FRITZBOX group Netzwerk
attr XX_FRITZBOX icon it_router
attr XX_FRITZBOX nonblockingTimeOut 125
attr XX_FRITZBOX retMsgbySet error
attr XX_FRITZBOX room Einstellungen,Server,Überblick
attr XX_FRITZBOX stateFormat Wlan:box_wlan_5GHz\
Gast:box_guestWlan
attr XX_FRITZBOX webCmd wOn:wOff:gOn:gOff
....

Eigentlich scheint alles zu funktionieren.
Aber das Log macht mich schon nervös.

Wie kann ich die Fehlersuche unterstützen?

JoWiemann · 23 Januar 2026, 15:08:33

Hallo Tango,

was hast Du denn für eine Netzwerkumgebung. In welcher Umgebung läuft Fhem. Das Modul meldet den Netzwerkfehler 500. Das ist ein allgemeiner Fehler, der auf eine Nichterreichbarkeit der FritzBox hindeutet.

Grüße Jörg

@tango · 23 Januar 2026, 16:05:56

Hi das ging ja schnell,
Netzwerk:
Fritzbox 7590
2 x Fritzrepeater 2400,
Fritz Dect Repeater
Div. Fritz DECT Geräte, Steckdosen, Taster, Termostat, Stromzähler
Raspi 4 mit HM-MOD-RPI-PCB und FHEM
Raspi 3 mit zweitem HM-MOD-RPI-PCB
Raspi 5 mit Nextcloud
Solakon PV Akku

Ab und zu mal Experimente mit weiteren Raspis (keine während des Logs).

Grüße Gerhard

JoWiemann · 23 Januar 2026, 19:35:24

Hallo Gerhard,

Code Auswählen

2026.01.23 00:21:11 2: [XX_FRITZBOX | 7590 | 154.08.21 | call_Lua_Query.15722] - SIGNIFICANT:500 Can't connect to 192.xxx.xxx.1:80 (Network is unreachable)
2026.01.23 00:21:11 2: [XX_FRITZBOX | 7590 | 154.08.21 | Readout_Response.8684] - SIGNIFICANT:500 Can't connect to 192.xxx.xxx.1:80 (Network is unreachable) - Readout_Run_Web_LuaQuery(5140)
2026.01.23 00:21:11 2: [XX_FRITZBOX | 7590 | 154.08.21 | Readout_Response.8684] - SIGNIFICANT:500 Can't connect to 192.xxx.xxx.1:80 (Network is unreachable) - Readout_Run_Web_LuaData(6091)
2026.01.23 00:21:11 3: XX_FBAHAHTTP: gethostbyname fritz.box failed

Hallo Gerhard,

da auch das XX_FBAHAHTTP Device zu den Zeitpunkten keine Verbindung bekommt, sieht es so aus, als wenn dann der RPi die Verbindung zum Netzwerk verliert.
- Wie ist der RPi auf dem Fhem läuft mit dem Netzwerk verbunden?
- Kannst Du in den Linux Log-Dateien etwas zu Netzwerkzustand finden?
- schau doch mal in den Ereignissen auf der FritzBox, die der Mesh Master ist, ob dort etwas hinterlegt ist.

Grüße Jörg

@tango · 23 Januar 2026, 20:29:57

Hi,
alle Raspis hängen per LAN-Kabel über einen kleinen Renkforce Switch an der Fritzbox.
Solakon über WLAN:

Als WLAN Ereignis finde ich als Besonderheit ca. 7 mal einen Eintrag wie

Code Auswählen

23.01.26 	17:49:28 	[RepeaterGabiszimmer] Eine sehr starke Störquelle wurde auf Kanal 1 (Frequenz 2.412 GHz) erkannt, automatischer Kanalwechsel ausgeführt. [2 Meldungen seit 23.01.26 17:49:28]

Die Zeiten passen eher nicht zu den Eiträgen im FHEM-Log.
Die Internetverbindung wurde wie üblich in der Nacht neu aufgebaut.

Code Auswählen

23.01.26 	04:43:15 	Internetverbindung wurde getrennt. 	
23.01.26 	04:43:15 	Internetverbindung IPv6 wurde getrennt, Präfix nicht mehr gültig.

Es erfolgen erheblich mehr als 100 erfolgreiche Anmeldungen vom FHEM Raspi an der Fritzbox mittels IP4 und IP6 unter verschiedenen user-Namen (abhängig vom device-type).
Keine Mißerfolge zu sehen.

Ich brauche einen Tip zu linux wo ich nachsehen soll.

Gerhard

JoWiemann · 23 Januar 2026, 20:38:13

Da hilft die KI

Übersicht mit KI

+3
Netzwerk-Logs auf einem Raspberry Pi (Linux/Raspberry Pi OS) werden primär über journalctl verwaltet. Die wichtigsten Befehle zur Analyse sind journalctl -u systemd-networkd (Netzwerkstatus) und journalctl -u wpa_supplicant (WLAN). Protokolldateien finden sich unter /var/log/, z.B. für SSH-Verbindungen in /var/log/auth.log. Mit journalctl -f können Logs in Echtzeit verfolgt werden.
Wichtige Befehle und Log-Speicherorte:
Netzwerkdienste: journalctl -u systemd-networkd zeigt Logs zum Netzwerkstart und IP-Vergabe.
WLAN (WiFi): journalctl -u wpa_supplicant protokolliert WLAN-Verbindungen, -Abbrüche und Authentifizierungsfehler.
Netzwerk-Schnittstellen: Mit dmesg oder cat /var/log/syslog können Ereignisse zu eth0 (Ethernet) oder wlan0 (WLAN) gefunden werden.
Authentifizierung (SSH): Die Datei /var/log/auth.log speichert Verbindungsversuche und Logins.
Echtzeit-Verfolgung: journalctl -f zeigt neue Einträge sofort an.
Hintergrund:
Log-Verwaltung: Moderne Raspberry Pi OS Versionen (Debian-basiert) nutzen systemd-journald, wodurch Logs im Binärformat gespeichert und über journalctl abgerufen werden.
Netzwerk-Identifikation: Zur Prüfung, ob das Gerät im Netzwerk aktiv ist, hilft ein Blick auf die Zuweisung von IP-Adressen in den Logs.
Die Protokolle helfen bei der Fehlersuche, wenn der Pi keine Verbindung zum Netzwerk aufbaut, das WLAN trennt oder Verbindungsanfragen abgewiesen werden.

@tango · 23 Januar 2026, 21:02:42

Hi danke
ich bin inzwischen auch bei

joutnalctl gelandet:

habe mittels

journalctl -S '2026-01-23 00:21:10' -U '2026-01-23 00:22:04'

das folgende erhalten:
Deinen Hinweis schaue ich mir noch genaujer an.

Code Auswählen

Jan 23 00:21:14 raspismart3 NetworkManager[586]: <info>  [1769124074.3233] device (eth0): carrier: link connected
Jan 23 00:21:14 raspismart3 NetworkManager[586]: <info>  [1769124074.3238] device (eth0): state change: unavailable -> disconnected (reason 'carrier-changed', sys-iface-state: 'managed')
Jan 23 00:21:14 raspismart3 NetworkManager[586]: <info>  [1769124074.3251] policy: auto-activating connection 'Kabelgebundene Verbindung 1' (9e280499-3410-300c-beae-87150b57522c)
Jan 23 00:21:14 raspismart3 NetworkManager[586]: <info>  [1769124074.3262] device (eth0): Activation: starting connection 'Kabelgebundene Verbindung 1' (9e280499-3410-300c-beae-87150b57522c)
Jan 23 00:21:14 raspismart3 kernel: bcmgenet fd580000.ethernet eth0: Link is Up - 100Mbps/Full - flow control rx/tx
Jan 23 00:21:14 raspismart3 NetworkManager[586]: <info>  [1769124074.3265] device (eth0): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed')
Jan 23 00:21:14 raspismart3 NetworkManager[586]: <info>  [1769124074.3272] manager: NetworkManager state is now CONNECTING
Jan 23 00:21:14 raspismart3 NetworkManager[586]: <info>  [1769124074.3276] device (eth0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
Jan 23 00:21:14 raspismart3 NetworkManager[586]: <info>  [1769124074.3285] device (eth0): state change: config -> ip-config (reason 'none', sys-iface-state: 'managed')
Jan 23 00:21:14 raspismart3 NetworkManager[586]: <info>  [1769124074.3295] dhcp4 (eth0): activation: beginning transaction (timeout in 45 seconds)
Jan 23 00:21:14 raspismart3 avahi-daemon[526]: Joining mDNS multicast group on interface eth0.IPv6 with address yyyy::yyyy:yyyy:yyyy:yyyy.
Jan 23 00:21:14 raspismart3 avahi-daemon[526]: New relevant interface eth0.IPv6 for mDNS.
Jan 23 00:21:14 raspismart3 avahi-daemon[526]: Registering new address record for yyyy::yyyy:yyyy:yyyy:yyyy on eth0.*.
Jan 23 00:21:14 raspismart3 NetworkManager[586]: <info>  [1769124074.3334] dhcp4 (eth0): state changed new lease, address=192.xxx.xxx.xx
Jan 23 00:21:14 raspismart3 NetworkManager[586]: <info>  [1769124074.3343] policy: set 'Kabelgebundene Verbindung 1' (eth0) as default for IPv4 routing and DNS
Jan 23 00:21:14 raspismart3 avahi-daemon[526]: Joining mDNS multicast group on interface eth0.IPv4 with address 192.xxx.xxx.xx.
Jan 23 00:21:14 raspismart3 avahi-daemon[526]: New relevant interface eth0.IPv4 for mDNS.
Jan 23 00:21:14 raspismart3 avahi-daemon[526]: Registering new address record for 192.xxx.xxx.xx on eth0.IPv4.
Jan 23 00:21:14 raspismart3 NetworkManager[586]: <info>  [1769124074.3461] device (eth0): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 'managed')
Jan 23 00:21:14 raspismart3 NetworkManager[586]: <info>  [1769124074.3506] device (eth0): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 'managed')
Jan 23 00:21:14 raspismart3 NetworkManager[586]: <info>  [1769124074.3511] device (eth0): state change: secondaries -> activated (reason 'none', sys-iface-state: 'managed')
Jan 23 00:21:14 raspismart3 NetworkManager[586]: <info>  [1769124074.3519] manager: NetworkManager state is now CONNECTED_SITE
Jan 23 00:21:14 raspismart3 NetworkManager[586]: <info>  [1769124074.3526] device (eth0): Activation: successful, device activated.
Jan 23 00:21:14 raspismart3 NetworkManager[586]: <info>  [1769124074.3536] manager: NetworkManager state is now CONNECTED_GLOBAL
Jan 23 00:21:15 raspismart3 kernel: bcmgenet fd580000.ethernet eth0: Link is Down
Jan 23 00:21:17 raspismart3 NetworkManager[586]: <info>  [1769124077.3954] device (eth0): carrier: link connected
Jan 23 00:21:17 raspismart3 kernel: bcmgenet fd580000.ethernet eth0: Link is Up - 100Mbps/Full - flow control rx/tx
Jan 23 00:21:18 raspismart3 kernel: bcmgenet fd580000.ethernet eth0: Link is Down
Jan 23 00:21:24 raspismart3 systemd[1]: NetworkManager-dispatcher.service: Deactivated successfully.
Jan 23 00:21:24 raspismart3 NetworkManager[586]: <info>  [1769124084.4230] device (eth0): state change: activated -> unavailable (reason 'carrier-changed', sys-iface-state: 'managed')
Jan 23 00:21:24 raspismart3 NetworkManager[586]: <info>  [1769124084.4385] dhcp4 (eth0): canceled DHCP transaction
Jan 23 00:21:24 raspismart3 NetworkManager[586]: <info>  [1769124084.4386] dhcp4 (eth0): activation: beginning transaction (timeout in 45 seconds)
Jan 23 00:21:24 raspismart3 NetworkManager[586]: <info>  [1769124084.4386] dhcp4 (eth0): state changed no lease
Jan 23 00:21:24 raspismart3 avahi-daemon[526]: Withdrawing address record for 192.xxx.xxx.xx on eth0.
Jan 23 00:21:24 raspismart3 avahi-daemon[526]: Leaving mDNS multicast group on interface eth0.IPv4 with address 192.xxx.xxx.xx.
Jan 23 00:21:24 raspismart3 avahi-daemon[526]: Interface eth0.IPv4 no longer relevant for mDNS.
Jan 23 00:21:24 raspismart3 avahi-daemon[526]: Withdrawing address record for yyyy::yyyy:yyyy:yyyy:yyyy on eth0.
Jan 23 00:21:24 raspismart3 avahi-daemon[526]: Leaving mDNS multicast group on interface eth0.IPv6 with address yyyy::yyyy:yyyy:yyyy:yyyy.
Jan 23 00:21:24 raspismart3 avahi-daemon[526]: Interface eth0.IPv6 no longer relevant for mDNS.
Jan 23 00:21:24 raspismart3 NetworkManager[586]: <info>  [1769124084.4839] manager: NetworkManager state is now DISCONNECTED
Jan 23 00:21:24 raspismart3 dbus-daemon[528]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service' requested by ':1.10' (uid=0 pid=586 comm="/usr/sbin/NetworkManager --no-daemon")
Jan 23 00:21:24 raspismart3 systemd[1]: Starting NetworkManager-dispatcher.service - Network Manager Script Dispatcher Service...
Jan 23 00:21:24 raspismart3 dbus-daemon[528]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
Jan 23 00:21:24 raspismart3 systemd[1]: Started NetworkManager-dispatcher.service - Network Manager Script Dispatcher Service.
Jan 23 00:21:32 raspismart3 kernel: bcmgenet fd580000.ethernet eth0: Link is Up - 100Mbps/Full - flow control rx/tx
Jan 23 00:21:32 raspismart3 NetworkManager[586]: <info>  [1769124092.7558] device (eth0): carrier: link connected
Jan 23 00:21:32 raspismart3 NetworkManager[586]: <info>  [1769124092.7567] device (eth0): state change: unavailable -> disconnected (reason 'carrier-changed', sys-iface-state: 'managed')
Jan 23 00:21:32 raspismart3 NetworkManager[586]: <info>  [1769124092.7598] policy: auto-activating connection 'Kabelgebundene Verbindung 1' (9e280499-3410-300c-beae-87150b57522c)
Jan 23 00:21:32 raspismart3 NetworkManager[586]: <info>  [1769124092.7628] device (eth0): Activation: starting connection 'Kabelgebundene Verbindung 1' (9e280499-3410-300c-beae-87150b57522c)
Jan 23 00:21:32 raspismart3 NetworkManager[586]: <info>  [1769124092.7633] device (eth0): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed')
Jan 23 00:21:32 raspismart3 NetworkManager[586]: <info>  [1769124092.7646] manager: NetworkManager state is now CONNECTING
Jan 23 00:21:32 raspismart3 NetworkManager[586]: <info>  [1769124092.7655] device (eth0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
Jan 23 00:21:32 raspismart3 NetworkManager[586]: <info>  [1769124092.7672] device (eth0): state change: config -> ip-config (reason 'none', sys-iface-state: 'managed')
Jan 23 00:21:32 raspismart3 NetworkManager[586]: <info>  [1769124092.7689] dhcp4 (eth0): activation: beginning transaction (timeout in 45 seconds)
Jan 23 00:21:32 raspismart3 avahi-daemon[526]: Joining mDNS multicast group on interface eth0.IPv6 with address yyyy::yyyy:yyyy:yyyy:yyyy.
Jan 23 00:21:32 raspismart3 NetworkManager[586]: <info>  [1769124092.7735] dhcp4 (eth0): state changed new lease, address=192.xxx.xxx.xx
Jan 23 00:21:32 raspismart3 avahi-daemon[526]: New relevant interface eth0.IPv6 for mDNS.
Jan 23 00:21:32 raspismart3 NetworkManager[586]: <info>  [1769124092.7754] policy: set 'Kabelgebundene Verbindung 1' (eth0) as default for IPv4 routing and DNS
Jan 23 00:21:32 raspismart3 avahi-daemon[526]: Registering new address record for yyyy::yyyy:yyyy:yyyy:yyyy on eth0.*.
Jan 23 00:21:32 raspismart3 avahi-daemon[526]: Joining mDNS multicast group on interface eth0.IPv4 with address 192.xxx.xxx.xx.
Jan 23 00:21:32 raspismart3 avahi-daemon[526]: New relevant interface eth0.IPv4 for mDNS.
Jan 23 00:21:32 raspismart3 avahi-daemon[526]: Registering new address record for 192.xxx.xxx.xx on eth0.IPv4.
Jan 23 00:21:32 raspismart3 NetworkManager[586]: <info>  [1769124092.7965] device (eth0): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 'managed')
Jan 23 00:21:32 raspismart3 NetworkManager[586]: <info>  [1769124092.8056] device (eth0): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 'managed')
Jan 23 00:21:32 raspismart3 NetworkManager[586]: <info>  [1769124092.8067] device (eth0): state change: secondaries -> activated (reason 'none', sys-iface-state: 'managed')
Jan 23 00:21:32 raspismart3 NetworkManager[586]: <info>  [1769124092.8084] manager: NetworkManager state is now CONNECTED_SITE
Jan 23 00:21:32 raspismart3 NetworkManager[586]: <info>  [1769124092.8098] device (eth0): Activation: successful, device activated.
Jan 23 00:21:32 raspismart3 NetworkManager[586]: <info>  [1769124092.8121] manager: NetworkManager state is now CONNECTED_GLOBAL
Jan 23 00:21:34 raspismart3 kernel: bcmgenet fd580000.ethernet eth0: Link is Down
Jan 23 00:21:40 raspismart3 NetworkManager[586]: <info>  [1769124100.8070] device (eth0): state change: activated -> unavailable (reason 'carrier-changed', sys-iface-state: 'managed')
Jan 23 00:21:40 raspismart3 NetworkManager[586]: <info>  [1769124100.8305] dhcp4 (eth0): canceled DHCP transaction
Jan 23 00:21:40 raspismart3 NetworkManager[586]: <info>  [1769124100.8306] dhcp4 (eth0): activation: beginning transaction (timeout in 45 seconds)
Jan 23 00:21:40 raspismart3 NetworkManager[586]: <info>  [1769124100.8307] dhcp4 (eth0): state changed no lease
Jan 23 00:21:40 raspismart3 avahi-daemon[526]: Withdrawing address record for 192.xxx.xxx.xx on eth0.
Jan 23 00:21:40 raspismart3 avahi-daemon[526]: Leaving mDNS multicast group on interface eth0.IPv4 with address 192.xxx.xxx.xx.
Jan 23 00:21:40 raspismart3 avahi-daemon[526]: Interface eth0.IPv4 no longer relevant for mDNS.
Jan 23 00:21:40 raspismart3 avahi-daemon[526]: Withdrawing address record for yyyy::yyyy:yyyy:yyyy:yyyy on eth0.
Jan 23 00:21:40 raspismart3 avahi-daemon[526]: Leaving mDNS multicast group on interface eth0.IPv6 with address yyyy::yyyy:yyyy:yyyy:yyyy.
Jan 23 00:21:40 raspismart3 avahi-daemon[526]: Interface eth0.IPv6 no longer relevant for mDNS.
Jan 23 00:21:40 raspismart3 NetworkManager[586]: <info>  [1769124100.8849] manager: NetworkManager state is now DISCONNECTED
Jan 23 00:21:46 raspismart3 NetworkManager[586]: <info>  [1769124106.0681] device (eth0): carrier: link connected
Jan 23 00:21:46 raspismart3 NetworkManager[586]: <info>  [1769124106.0696] device (eth0): state change: unavailable -> disconnected (reason 'carrier-changed', sys-iface-state: 'managed')
Jan 23 00:21:46 raspismart3 kernel: bcmgenet fd580000.ethernet eth0: Link is Up - 100Mbps/Full - flow control rx/tx
Jan 23 00:21:46 raspismart3 NetworkManager[586]: <info>  [1769124106.0721] policy: auto-activating connection 'Kabelgebundene Verbindung 1' (9e280499-3410-300c-beae-87150b57522c)
Jan 23 00:21:46 raspismart3 NetworkManager[586]: <info>  [1769124106.0742] device (eth0): Activation: starting connection 'Kabelgebundene Verbindung 1' (9e280499-3410-300c-beae-87150b57522c)
Jan 23 00:21:46 raspismart3 NetworkManager[586]: <info>  [1769124106.0747] device (eth0): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed')
Jan 23 00:21:46 raspismart3 NetworkManager[586]: <info>  [1769124106.0759] manager: NetworkManager state is now CONNECTING
Jan 23 00:21:46 raspismart3 NetworkManager[586]: <info>  [1769124106.0766] device (eth0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
Jan 23 00:21:46 raspismart3 NetworkManager[586]: <info>  [1769124106.0783] device (eth0): state change: config -> ip-config (reason 'none', sys-iface-state: 'managed')
Jan 23 00:21:46 raspismart3 NetworkManager[586]: <info>  [1769124106.0801] dhcp4 (eth0): activation: beginning transaction (timeout in 45 seconds)
Jan 23 00:21:46 raspismart3 avahi-daemon[526]: Joining mDNS multicast group on interface eth0.IPv6 with address yyyy::yyyy:yyyy:yyyy:yyyy.
Jan 23 00:21:46 raspismart3 NetworkManager[586]: <info>  [1769124106.0848] dhcp4 (eth0): state changed new lease, address=192.xxx.xxx.xx
Jan 23 00:21:46 raspismart3 avahi-daemon[526]: New relevant interface eth0.IPv6 for mDNS.
Jan 23 00:21:46 raspismart3 NetworkManager[586]: <info>  [1769124106.0866] policy: set 'Kabelgebundene Verbindung 1' (eth0) as default for IPv4 routing and DNS
Jan 23 00:21:46 raspismart3 avahi-daemon[526]: Registering new address record for yyyy::yyyy:yyyy:yyyy:yyyy on eth0.*.
Jan 23 00:21:46 raspismart3 avahi-daemon[526]: Joining mDNS multicast group on interface eth0.IPv4 with address 192.xxx.xxx.xx.
Jan 23 00:21:46 raspismart3 avahi-daemon[526]: New relevant interface eth0.IPv4 for mDNS.
Jan 23 00:21:46 raspismart3 avahi-daemon[526]: Registering new address record for 192.xxx.xxx.xx on eth0.IPv4.
Jan 23 00:21:46 raspismart3 NetworkManager[586]: <info>  [1769124106.1034] device (eth0): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 'managed')
Jan 23 00:21:46 raspismart3 NetworkManager[586]: <info>  [1769124106.1131] device (eth0): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 'managed')
Jan 23 00:21:46 raspismart3 NetworkManager[586]: <info>  [1769124106.1141] device (eth0): state change: secondaries -> activated (reason 'none', sys-iface-state: 'managed')
Jan 23 00:21:46 raspismart3 NetworkManager[586]: <info>  [1769124106.1160] manager: NetworkManager state is now CONNECTED_SITE
Jan 23 00:21:46 raspismart3 NetworkManager[586]: <info>  [1769124106.1174] device (eth0): Activation: successful, device activated.
Jan 23 00:21:46 raspismart3 NetworkManager[586]: <info>  [1769124106.1196] manager: NetworkManager state is now CONNECTED_GLOBAL
Jan 23 00:21:47 raspismart3 kernel: bcmgenet fd580000.ethernet eth0: Link is Down
Jan 23 00:21:53 raspismart3 NetworkManager[586]: <info>  [1769124113.0934] device (eth0): state change: activated -> unavailable (reason 'carrier-changed', sys-iface-state: 'managed')
Jan 23 00:21:53 raspismart3 NetworkManager[586]: <info>  [1769124113.1185] dhcp4 (eth0): canceled DHCP transaction
Jan 23 00:21:53 raspismart3 NetworkManager[586]: <info>  [1769124113.1185] dhcp4 (eth0): activation: beginning transaction (timeout in 45 seconds)
Jan 23 00:21:53 raspismart3 NetworkManager[586]: <info>  [1769124113.1186] dhcp4 (eth0): state changed no lease
Jan 23 00:21:53 raspismart3 avahi-daemon[526]: Withdrawing address record for 192.xxx.xxx.xx on eth0.
Jan 23 00:21:53 raspismart3 avahi-daemon[526]: Leaving mDNS multicast group on interface eth0.IPv4 with address 192.xxx.xxx.xx.
Jan 23 00:21:53 raspismart3 avahi-daemon[526]: Interface eth0.IPv4 no longer relevant for mDNS.
Jan 23 00:21:53 raspismart3 avahi-daemon[526]: Withdrawing address record for yyyy::yyyy:yyyy:yyyy:yyyy on eth0.
Jan 23 00:21:53 raspismart3 avahi-daemon[526]: Leaving mDNS multicast group on interface eth0.IPv6 with address yyyy::yyyy:yyyy:yyyy:yyyy.
Jan 23 00:21:53 raspismart3 avahi-daemon[526]: Interface eth0.IPv6 no longer relevant for mDNS.
Jan 23 00:21:53 raspismart3 NetworkManager[586]: <info>  [1769124113.1635] manager: NetworkManager state is now DISCONNECTED
Jan 23 00:21:53 raspismart3 NetworkManager[586]: <info>  [1769124113.2353] device (eth0): carrier: link connected
Jan 23 00:21:53 raspismart3 NetworkManager[586]: <info>  [1769124113.2359] device (eth0): state change: unavailable -> disconnected (reason 'carrier-changed', sys-iface-state: 'managed')
Jan 23 00:21:53 raspismart3 NetworkManager[586]: <info>  [1769124113.2372] policy: auto-activating connection 'Kabelgebundene Verbindung 1' (9e280499-3410-300c-beae-87150b57522c)
Jan 23 00:21:53 raspismart3 NetworkManager[586]: <info>  [1769124113.2383] device (eth0): Activation: starting connection 'Kabelgebundene Verbindung 1' (9e280499-3410-300c-beae-87150b57522c)
Jan 23 00:21:53 raspismart3 kernel: bcmgenet fd580000.ethernet eth0: Link is Up - 100Mbps/Full - flow control rx/tx
Jan 23 00:21:53 raspismart3 NetworkManager[586]: <info>  [1769124113.2386] device (eth0): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed')
Jan 23 00:21:53 raspismart3 NetworkManager[586]: <info>  [1769124113.2392] manager: NetworkManager state is now CONNECTING
Jan 23 00:21:53 raspismart3 NetworkManager[586]: <info>  [1769124113.2397] device (eth0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
Jan 23 00:21:53 raspismart3 NetworkManager[586]: <info>  [1769124113.2407] device (eth0): state change: config -> ip-config (reason 'none', sys-iface-state: 'managed')
Jan 23 00:21:53 raspismart3 NetworkManager[586]: <info>  [1769124113.2416] dhcp4 (eth0): activation: beginning transaction (timeout in 45 seconds)
Jan 23 00:21:53 raspismart3 avahi-daemon[526]: Joining mDNS multicast group on interface eth0.IPv6 with address yyyy::yyyy:yyyy:yyyy:yyyy.
Jan 23 00:21:53 raspismart3 avahi-daemon[526]: New relevant interface eth0.IPv6 for mDNS.
Jan 23 00:21:53 raspismart3 avahi-daemon[526]: Registering new address record for yyyy::yyyy:yyyy:yyyy:yyyy on eth0.*.
Jan 23 00:21:53 raspismart3 NetworkManager[586]: <info>  [1769124113.2452] dhcp4 (eth0): state changed new lease, address=192.xxx.xxx.xx
Jan 23 00:21:53 raspismart3 NetworkManager[586]: <info>  [1769124113.2462] policy: set 'Kabelgebundene Verbindung 1' (eth0) as default for IPv4 routing and DNS
Jan 23 00:21:53 raspismart3 avahi-daemon[526]: Joining mDNS multicast group on interface eth0.IPv4 with address 192.xxx.xxx.xx.
Jan 23 00:21:53 raspismart3 avahi-daemon[526]: New relevant interface eth0.IPv4 for mDNS.
Jan 23 00:21:53 raspismart3 avahi-daemon[526]: Registering new address record for 192.xxx.xxx.xx on eth0.IPv4.
Jan 23 00:21:53 raspismart3 NetworkManager[586]: <info>  [1769124113.2594] device (eth0): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 'managed')
Jan 23 00:21:53 raspismart3 NetworkManager[586]: <info>  [1769124113.2648] device (eth0): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 'managed')
Jan 23 00:21:53 raspismart3 NetworkManager[586]: <info>  [1769124113.2653] device (eth0): state change: secondaries -> activated (reason 'none', sys-iface-state: 'managed')
Jan 23 00:21:53 raspismart3 NetworkManager[586]: <info>  [1769124113.2662] manager: NetworkManager state is now CONNECTED_SITE
Jan 23 00:21:53 raspismart3 NetworkManager[586]: <info>  [1769124113.2669] device (eth0): Activation: successful, device activated.
Jan 23 00:21:53 raspismart3 NetworkManager[586]: <info>  [1769124113.2680] manager: NetworkManager state is now CONNECTED_GLOBAL
Jan 23 00:21:54 raspismart3 kernel: bcmgenet fd580000.ethernet eth0: Link is Down
Jan 23 00:22:00 raspismart3 NetworkManager[586]: <info>  [1769124120.2617] device (eth0): state change: activated -> unavailable (reason 'carrier-changed', sys-iface-state: 'managed')
Jan 23 00:22:00 raspismart3 NetworkManager[586]: <info>  [1769124120.2745] dhcp4 (eth0): canceled DHCP transaction
Jan 23 00:22:00 raspismart3 NetworkManager[586]: <info>  [1769124120.2746] dhcp4 (eth0): activation: beginning transaction (timeout in 45 seconds)
Jan 23 00:22:00 raspismart3 NetworkManager[586]: <info>  [1769124120.2746] dhcp4 (eth0): state changed no lease
Jan 23 00:22:00 raspismart3 avahi-daemon[526]: Withdrawing address record for 192.xxx.xxx.xx on eth0.
Jan 23 00:22:00 raspismart3 avahi-daemon[526]: Leaving mDNS multicast group on interface eth0.IPv4 with address 192.xxx.xxx.xx.
Jan 23 00:22:00 raspismart3 avahi-daemon[526]: Interface eth0.IPv4 no longer relevant for mDNS.
Jan 23 00:22:00 raspismart3 avahi-daemon[526]: Withdrawing address record for yyyy::yyyy:yyyy:yyyy:yyyy on eth0.
Jan 23 00:22:00 raspismart3 avahi-daemon[526]: Leaving mDNS multicast group on interface eth0.IPv6 with address yyyy::yyyy:yyyy:yyyy:yyyy.
Jan 23 00:22:00 raspismart3 avahi-daemon[526]: Interface eth0.IPv6 no longer relevant for mDNS.
Jan 23 00:22:00 raspismart3 NetworkManager[586]: <info>  [1769124120.3396] manager: NetworkManager state is now DISCONNECTED
Jan 23 00:22:00 raspismart3 NetworkManager[586]: <info>  [1769124120.4034] device (eth0): carrier: link connected
Jan 23 00:22:00 raspismart3 NetworkManager[586]: <info>  [1769124120.4042] device (eth0): state change: unavailable -> disconnected (reason 'carrier-changed', sys-iface-state: 'managed')
Jan 23 00:22:00 raspismart3 NetworkManager[586]: <info>  [1769124120.4055] policy: auto-activating connection 'Kabelgebundene Verbindung 1' (9e280499-3410-300c-beae-87150b57522c)
Jan 23 00:22:00 raspismart3 kernel: bcmgenet fd580000.ethernet eth0: Link is Up - 100Mbps/Full - flow control rx/tx
Jan 23 00:22:00 raspismart3 NetworkManager[586]: <info>  [1769124120.4066] device (eth0): Activation: starting connection 'Kabelgebundene Verbindung 1' (9e280499-3410-300c-beae-87150b57522c)
Jan 23 00:22:00 raspismart3 NetworkManager[586]: <info>  [1769124120.4068] device (eth0): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed')
Jan 23 00:22:00 raspismart3 NetworkManager[586]: <info>  [1769124120.4073] manager: NetworkManager state is now CONNECTING
Jan 23 00:22:00 raspismart3 NetworkManager[586]: <info>  [1769124120.4077] device (eth0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
Jan 23 00:22:00 raspismart3 NetworkManager[586]: <info>  [1769124120.4086] device (eth0): state change: config -> ip-config (reason 'none', sys-iface-state: 'managed')
Jan 23 00:22:00 raspismart3 NetworkManager[586]: <info>  [1769124120.4095] dhcp4 (eth0): activation: beginning transaction (timeout in 45 seconds)
Jan 23 00:22:00 raspismart3 avahi-daemon[526]: Joining mDNS multicast group on interface eth0.IPv6 with address yyyy::yyyy:yyyy:yyyy:yyyy.
Jan 23 00:22:00 raspismart3 avahi-daemon[526]: New relevant interface eth0.IPv6 for mDNS.
Jan 23 00:22:00 raspismart3 avahi-daemon[526]: Registering new address record for yyyy::yyyy:yyyy:yyyy:yyyy on eth0.*.
Jan 23 00:22:00 raspismart3 NetworkManager[586]: <info>  [1769124120.4147] dhcp4 (eth0): state changed new lease, address=192.xxx.xxx.xx
Jan 23 00:22:00 raspismart3 NetworkManager[586]: <info>  [1769124120.4156] policy: set 'Kabelgebundene Verbindung 1' (eth0) as default for IPv4 routing and DNS
Jan 23 00:22:00 raspismart3 avahi-daemon[526]: Joining mDNS multicast group on interface eth0.IPv4 with address 192.xxx.xxx.xx.
Jan 23 00:22:00 raspismart3 avahi-daemon[526]: New relevant interface eth0.IPv4 for mDNS.
Jan 23 00:22:00 raspismart3 avahi-daemon[526]: Registering new address record for 192.xxx.xxx.xx on eth0.IPv4.
Jan 23 00:22:00 raspismart3 NetworkManager[586]: <info>  [1769124120.4264] device (eth0): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 'managed')
Jan 23 00:22:00 raspismart3 NetworkManager[586]: <info>  [1769124120.4314] device (eth0): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 'managed')
Jan 23 00:22:00 raspismart3 NetworkManager[586]: <info>  [1769124120.4320] device (eth0): state change: secondaries -> activated (reason 'none', sys-iface-state: 'managed')
Jan 23 00:22:00 raspismart3 NetworkManager[586]: <info>  [1769124120.4329] manager: NetworkManager state is now CONNECTED_SITE
Jan 23 00:22:00 raspismart3 NetworkManager[586]: <info>  [1769124120.4335] device (eth0): Activation: successful, device activated.
Jan 23 00:22:00 raspismart3 NetworkManager[586]: <info>  [1769124120.4346] manager: NetworkManager state is now CONNECTED_GLOBAL
Jan 23 00:22:01 raspismart3 kernel: bcmgenet fd580000.ethernet eth0: Link is Down

JoWiemann · 23 Januar 2026, 21:13:38

Ich würde jetzt mal alle disconected Einträge filtern und schauen ob das mit den Log Einträgen von Fhem korreliert.

Tja, und dann vielleicht als einfachen Test den RPi austauschen. Sollte dann alles ok sein, dann war es die Hardware. Ansonsten geht leidiges Suchen weiter.

Grüße Jörg

LuckyDay · 23 Januar 2026, 21:42:25

Netzgerät vom Pi wechseln

passibe · 23 Januar 2026, 23:53:37

Erstmal ganz simpel anfangen und das LAN-Kabel vom Pi wechseln!

@tango · 24 Januar 2026, 12:34:32

Danke,
ran ans Werk.
Raspi direkt an die Fritz ohne switch dazwischen.
Abwarten.

@tango · 27 Januar 2026, 12:34:18

Hallo *,
langsam tritt Klarheit ein.
Der Switch war es nicht.
Stattdessen lief FHEM wieder stabil, wenn die PIUSV+ entfernt war.
Nach beheben eines Wackelkontaktes läuft der raspi wieder mit Switch und PIUSV+ stabil.

Der Ausgangspunkt der Probleme ist jetzt auch geklärt.
Meine neue PV Anlage hat Smart Home Unterstützung über HomeAssistant.
Ich habe daher auf einen alten Raspi HA installiert und in Betrieb genommen um das zu testen.
Der lief parallel zu FHEM.
Beim Trennen vom Netz habe ich wohl am FHEMRaspi den Wackelkontakt verursacht.

Mittlerweile kann ich reproduzierbar festellen:
1. HA mit abgeschalteten FHEMRaspi unterstützt PV wie es soll.
2. Geht bei eingeschaltetem FHEM HA ans Netz gibt es im FHEM Log danach die Einträge:

Code Auswählen

2026.01.27 12:08:51 2: [XX_FRITZBOX | 7590 | 154.08.21 | call_Lua_Query.15722] - SIGNIFICANT:500 Can't connect to 192.168.168.1:80 (Network is unreachable)
2026.01.27 12:08:51 2: [XX_FRITZBOX | 7590 | 154.08.21 | Readout_Response.8684] - SIGNIFICANT:500 Can't connect to 192.168.168.1:80 (Network is unreachable) - Readout_Run_Web_LuaQuery(5140)
2026.01.27 12:08:51 2: [XX_FRITZBOX | 7590 | 154.08.21 | Readout_Response.8684] - SIGNIFICANT:500 Can't connect to 192.168.168.1:80 (Network is unreachable) - Readout_Run_Web_LuaData(6091)
2026.01.27 12:08:52 3: [XX_FRITZBOX | 7590 | 154.08.21 | Readout_Run_Web_TR064.8460] - BASIC:wanpppconn1 - no GetInfoResponse getting TR064 data

und FHEM hängt sich auf.
Zieht man den LAN Stecker am HA läuft der FHEMRaspi korrekt weiter.

Aus diversen Foreneinträgen (auch bei AVM) habe ich allerdings (wohl fälschlicherweise) den Eindruck gewonnen, daß beide Systeme (nur theoretisch?) parallel laufen können.

Bei HA die Fritz Insertions zu deaktivieren hilft auch nicht.

Gibt es eine Möglichkeit für den Parallellauf?

Grüße Gerhard

passibe · 27 Januar 2026, 13:26:09

Zitat von: @tango am 27 Januar 2026, 12:34:18Fritz Insertions

Was ist das?

Vielleicht bei HA mal iregndwelches Autodiscovery Zeugs deaktivieren? Wobei auch das eigentlich keine Probleme verursachen sollte.

Um was für eine PV-Anlage handelt es sich denn?

Finde es aber komisch, dass sich da irgendwas beißt. Bei mir laufen auch Home Assistant und FHEM parallel und ich lese die Fritzbox mit FHEM aus und habe keine Probleme.

Im Zweifel mach mal ein packet capture über die FB (googeln wie das geht) und schau dir in Wireshark an, was da passiert. Alternativ bzw. parallel dazu vielleicht auch ein packet capture jeweils auf den beiden Pis.
Die Kenntnis des Netzwerktraffics dürfte einigermaßen schnelle Erkenntnis bringen, was da los ist. Ohne das stochert man viel im Dunkeln.

@tango · 27 Januar 2026, 14:05:23

Sorry
ich meine Fritzbox "Integration" (HA noch ungewohnt).
Bei Installation waren unter anderem Fritz SmartHome und Fritz Tools vorgegeben.
Die hatte ich zunächst auch per Klick geladen und jetzt deaktiviert.
Werde mal ein komplettes Löschen auf HA versuchen.
Die PV ist Solakon One.

RalfRog · 27 Januar 2026, 15:43:00

Nur mal so...
FHEM und HA haben nicht zufällig die gleiche IP Adresse?