Ich hab schon sehr lange einen eigenen Server in FHEM laufen, aber sowas hatte ich noch nie:
Hat sich "allein" auf "disable 1" gesetzt ???
[code]define myBroker MQTT2_SERVER 1883 global
attr myBroker disable 0
attr myBroker icon mqtt
attr myBroker room MQTT,MQTT2_DEVICE
attr myBroker verbose 2
# CONNECTS 20
# Clients :MQTT2_DEVICE:MQTT_GENERIC_BRIDGE:
# ClientsKeepOrder 1
# DEF 1883 global
# FD 52
# FUUID 5e2ac876-f33f-b5ae-8126-ff8288d0490ffad7
# NAME myBroker
# NR 520
# PORT 1883
# STATE Initialized
# TYPE MQTT2_SERVER
# connects 20
# eventCount 25
# MatchList:
# 1:MQTT2_DEVICE ^.
# 2:MQTT_GENERIC_BRIDGE ^.
# READINGS:
# 2023-01-15 10:49:15 RETAIN {"heating_system/ems-esp/boiler_data":"offline","heating_system/ems-esp/heartbeat":"offline","heating_system/ems-esp/heating_active":"offline","heating_system/ems-esp/shower_data":"offline","heating_system/ems-esp/start":"{\u0022version\u0022:\u00221.9.5\u0022,\u0022IP\u0022:\u0022192.168.178.79\u0022}","heating_system/ems-esp/status":"online","heating_system/ems-esp/thermostat_data":"offline"}
# 2020-10-10 09:56:09 lastPublish heating-system/ems-esp/status:
# 2026-10-13 15:46:44 nrclients 15
# 2026-10-13 15:49:23 state Initialized
# clients:
# myBroker_192.168.178.103_52390 1
# myBroker_192.168.178.109_18208 1
# myBroker_192.168.178.110_13284 1
# myBroker_192.168.178.114_4096 1
# myBroker_192.168.178.116_13132 1
# myBroker_192.168.178.124_25278 1
# myBroker_192.168.178.130_51209 1
# myBroker_192.168.178.132_62005 1
# myBroker_192.168.178.133_58719 1
# myBroker_192.168.178.134_63941 1
# myBroker_192.168.178.158_59844 1
# myBroker_192.168.178.159_60870 1
# myBroker_192.168.178.56_57632 1
# myBroker_192.168.178.79_61186 1
# myBroker_192.168.178.95_55295 1
# retain:
# heating_system/ems-esp/boiler_data:
# ts 1791894732.56392
# val offline
# heating_system/ems-esp/heartbeat:
# ts 1791894732.56392
# val offline
# heating_system/ems-esp/heating_active:
# ts 1791894732.56392
# val offline
# heating_system/ems-esp/shower_data:
# ts 1791894732.56392
# val offline
# heating_system/ems-esp/start:
# ts 1791894732.56392
# val {"version":"1.9.5","IP":"192.168.178.79"}
# heating_system/ems-esp/status:
# ts 1791894732.56392
# val online
# heating_system/ems-esp/thermostat_data:
# ts 1791894732.56392
# val offline
#
setstate myBroker 2023-01-15 10:49:15 RETAIN {"heating_system/ems-esp/boiler_data":"offline","heating_system/ems-esp/heartbeat":"offline","heating_system/ems-esp/heating_active":"offline","heating_system/ems-esp/shower_data":"offline","heating_system/ems-esp/start":"{\u0022version\u0022:\u00221.9.5\u0022,\u0022IP\u0022:\u0022192.168.178.79\u0022}","heating_system/ems-esp/status":"online","heating_system/ems-esp/thermostat_data":"offline"}
setstate myBroker 2020-10-10 09:56:09 lastPublish heating-system/ems-esp/status:
setstate myBroker 2026-10-13 15:46:44 nrclients 15
setstate myBroker 2026-10-13 15:49:23 state Initialized
[/code]
Da steht aber "disable 0" in der Liste :)
MQTT2_SERVER fummelt nicht an den eigenen Attributen herum, dass muss jemand sonst gewesen sein.
Als Erstes faellt mir einer der Frontends ein, mit menschlicher Hilfe.
ja, da steht JETZT wieder disable 0 ;)