[2026-01-10 16:09:40] info: z2m: Connecting to MQTT server at mqtt://192.168.31.60:1883
[2026-01-10 16:09:40] info: z2m: Connected to MQTT server
[2026-01-10 16:09:40] info: z2m:mqtt: MQTT publish: topic 'esperanto2023/bridge/state', payload '{"state":"online"}'
[2026-01-10 16:09:40] info: z2m: Started frontend on port 8080
[2026-01-10 16:09:40] info: z2m: Zigbee2MQTT started!
[2026-01-10 16:09:42] info: z2m:mqtt: MQTT publish: topic 'esperanto2023/bridge/state', payload '{"state":"online"}'
[2026-01-10 16:11:10] error: z2m: MQTT error: Keepalive timeout
[2026-01-10 16:11:10] error: z2m: Not connected to MQTT server!
[2026-01-10 16:11:20] error: z2m: Not connected to MQTT server!
[2026-01-10 16:11:30] error: z2m: Not connected to MQTT server!
[2026-01-10 16:11:40] error: z2m: Not connected to MQTT server!
[2026-01-10 16:11:41] error: z2m: MQTT error: connack timeout
[2026-01-10 16:14:30] error: z2m: Not connected to MQTT server!
[2026-01-10 16:14:30] error: z2m: MQTT error: connect ECONNREFUSED 192.168.31.60:1883
[2026-01-10 16:14:31] error: z2m: MQTT error: connect ECONNREFUSED 192.168.31.60:1883
[2026-01-10 16:14:36] info: z2m: Connected to MQTT server
[2026-01-10 16:14:36] info: z2m:mqtt: MQTT publish: topic 'esperanto2023/bridge/state', payload '{"state":"online"}'
[2026-01-10 16:16:06] error: z2m: MQTT error: Keepalive timeout
[2026-01-10 16:16:10] error: z2m: Not connected to MQTT server!
[2026-01-10 16:16:20] error: z2m: Not connected to MQTT server!
[2026-01-10 16:16:30] error: z2m: Not connected to MQTT server!
[2026-01-10 16:16:37] error: z2m: MQTT error: connack timeout
[2026-01-10 16:16:39] error: z2m: Not connected to MQTT server!
defmod MQTT2Broker MQTT2_SERVER 1883 global
attr MQTT2Broker autocreate simple
attr MQTT2Broker keepaliveFactor 0
attr MQTT2Broker respectRetain 1Das Log von FHEM enthält nur die Neustarts.Jan 10 15:14:05 fhem signal-cli[1713]: Envelope from: "Name" 47c9b287-30f4-4342-b783-0f260e016c21 (device: 1) to +491712345678
Jan 10 15:14:05 fhem signal-cli[1713]: Timestamp: 1768054443837 (2026-01-10T14:14:03.837Z)
Jan 10 15:14:05 fhem signal-cli[1713]: Server timestamps: received: 1768054445381 (2026-01-10T14:14:05.381Z) delivered: 1768054445383 (2026-01-10T14:14:05.383Z)
Jan 10 15:14:05 fhem signal-cli[1713]: Sent by unidentified/sealed sender
Jan 10 15:14:05 fhem signal-cli[1713]: Received a receipt message
Jan 10 15:14:05 fhem signal-cli[1713]: When: 1768054443837 (2026-01-10T14:14:03.837Z)
Jan 10 15:14:05 fhem signal-cli[1713]: Is delivery receipt
Jan 10 15:14:05 fhem signal-cli[1713]: Timestamps:
Jan 10 15:14:05 fhem signal-cli[1713]: - 1768054442695 (2026-01-10T14:14:02.695Z)
Zitat von: tgv_boost am 10 Januar 2026, 13:06:23Hier mal ein Baustein der Kommunikation auf Raspberry SeiteSuper, danke dir!
z2m:
image: koenkk/zigbee2mqtt:latest
container_name: zigbee2mqtt
restart: unless-stopped
depends_on:
fhem:
condition: service_healthy
ports:
- "8089:8080"
volumes:
- ./data:/app/data
- /run/udev:/run/udev:ro
devices:
- /dev/serial/by-id/usb-ITead_Sonoff_Zigbee_3.0_USB_Dongle_Plus_48d17ff1cb8aef118f9e24ccef8776e9-if00-port0:/dev/ttyACM0
privileged: false
environment:
TZ: Europe/BerlinZitat von: rabehd am 10 Januar 2026, 15:21:34hängt der FHEM-ContainerWie kommt das? Steht was im FHEM-Log? Was sagt das Z2M-Log jetzt? Welchen MQTT-Broker benutzt du? MQTT2_SERVER direkt in FHEM?