Meine verschiedenen mqtt Anwendungen liefen bisher alle problemlos mit Anbindung an Mosquitto Server auf einer Synology.
Anbindung über MQTT2_CLIENT.
Nach Umstieg auf mqtt2 server auf meinem Beaglebone habe ich das Problem dass die Generic Bridge keine Subscribes mehr von meinen Gosunds erhält.
Anbei List des Device
Internals:
CFGFN ./config.d/Stromverbrauch.cfg
FUUID 5e2dcac9-f33f-8b9f-54b7-9df4fc3002b75052
NAME GosWM
NR 995
STATE off
TYPE dummy
READINGS:
2023-08-05 13:12:01 ENERGY_ApparentPower 0
2023-08-05 13:12:01 ENERGY_Current 0.000
2023-08-05 13:12:01 ENERGY_Factor 0.00
2023-08-05 13:12:01 ENERGY_Period 0
2023-08-05 13:12:01 ENERGY_Power 0
2023-08-05 13:12:01 ENERGY_ReactivePower 0
2023-08-05 13:12:01 ENERGY_Today 0.000
2023-08-05 13:12:01 ENERGY_Total 472.415
2023-08-05 13:12:01 ENERGY_TotalStartTime 2021-01-01T00:00:00
2023-08-05 13:12:01 ENERGY_Voltage 242
2023-08-05 13:12:01 ENERGY_Yesterday 0.348
2023-08-05 10:24:49 Status off
2023-08-05 13:12:01 Time 2023-08-05T13:12:01
2023-07-08 06:52:51 Zustand OFF
2023-08-05 10:24:49 state off
Attributes:
devStateIcon on:Diode_gruen stop:Diode_rot off:Diode_off
event-min-interval ENERGY_Power:600,ENERGY_Total:1800
event-on-change-reading state,ENERGY_Power,ENERGY_Total,Zustand,Status
group Verbrauch
icon scene_washing_machine
mqttSubscribe state:stopic=fhem/status/alarm/waschmaschine
Status:topic=fhem/status/alarm/waschmaschine
Zustand:topic=stat/GosWM/POWER
ENERGY_Power:topic=cmd/GosWM/Watt
ENERGY:topic=tele/GosWM/SENSOR ENERGY:expression={json2nameValue($message)}
room WK
sortby 1
userattr mqttAlias:textField-long mqttDefaults:textField-long mqttDisable:both,incoming,outgoing mqttForward:all,none mqttPublish:textField-long mqttSubscribe:textField-long
webCmd :
und list m2server
Internals:
CONNECTS 120
Clients :MQTT2_DEVICE:MQTT_GENERIC_BRIDGE:
ClientsKeepOrder 1
DEF 1883 global
FD 55
FUUID 64ce0f46-f33f-8b9f-8b9b-f660a72da56825e8
NAME m2server
NR 1235
PORT 1883
STATE Initialized
TYPE MQTT2_SERVER
eventCount 787
MatchList:
1:MQTT2_DEVICE ^.
2:MQTT_GENERIC_BRIDGE ^.
READINGS:
2023-08-11 20:39:03 lastPublish fhem/status/alarm/hz_brenner:off
2023-08-11 19:43:07 nrclients 22
2023-08-06 16:08:26 state Initialized
clients:
m2server_192.168.148.111_54591 1
m2server_192.168.148.118_56648 1
m2server_192.168.148.136_62269 1
m2server_192.168.148.140_51888 1
m2server_192.168.148.141_58458 1
m2server_192.168.148.142_53200 1
m2server_192.168.148.143_61793 1
m2server_192.168.148.17_40202 1
m2server_192.168.148.210_58927 1
m2server_192.168.148.211_54336 1
m2server_192.168.148.214_54040 1
m2server_192.168.148.216_62919 1
m2server_192.168.148.228_52800 1
m2server_192.168.148.231_53995 1
m2server_192.168.148.232_57882 1
m2server_192.168.148.37_57361 1
m2server_192.168.148.61_61862 1
m2server_192.168.148.62_53952 1
m2server_192.168.148.64_50794 1
m2server_192.168.148.65_61622 1
m2server_192.168.148.66_55716 1
m2server_192.168.148.83_54952 1
Attributes:
group 1_Gateway
icon mqtt
respectRetain 0
Hat jemand eine Idee wo ich da ansetzen kann?
Billy
Und wo ist das list von der generic bridge?
clientOrder dürfte auch nicht passen.
Danke für deine Antwort.
Ich habe heute Morgen einfach den MQTT2_CLIENT wieder installiert (Zusätzlich zum m2server) und der Generic Bridge wieder den MQTT2_CLIENT als IODev verpasst.
Seitdem läuft alles wieder wie gehabt.
Anbei auch das List der generic bridge in dieser Konfiguration.
Ich hatte eigentlich erwartet, dass ich die generic bridge direkt an m2server als IODev verwenden kann.
Internals:
DEF mqtt ZB_WZ_OG Wlan_Garten T1 T6 sp1_5 sp111_3 GosSM GosWM GosTR Pow1 Pow2 Zyklon Waermebedarf esagcom myZisterne FS_1BEAE8 Schalter_1BEA79 Licht_WaKue Brunnen_20C4F6 HM_69F161 BM_1A8215 HM_69F136 HM_69F07B HM_2D0D4F HM_Window_BadOG HM_Window_WK_UG HM_Window_WS_UG HM_Window_Gast_UG HM_Window_HZ_UG mySmP1 HM_68D27D_GarageV OG_WZ_Weather EG_WZ_Weather
FUUID 5d2a1c3f-f33f-8b9f-f82e-c60da4d17b037579
IODev MQTT2_CLIENT
NAME mGB11
NR 85
NTFY_ORDER 70-mGB11
STATE DeviceCount 28
TYPE MQTT_GENERIC_BRIDGE
devspec ZB_WZ_OG,Wlan_Garten,T1,T6,sp1_5,sp111_3,GosSM,GosWM,GosTR,Pow1,Pow2,Zyklon,Waermebedarf,esagcom,myZisterne,FS_1BEAE8,Schalter_1BEA79,Licht_WaKue,Brunnen_20C4F6,HM_69F161,BM_1A8215,HM_69F136,HM_69F07B,HM_2D0D4F,HM_Window_BadOG,HM_Window_WK_UG,HM_Window_WS_UG,HM_Window_Gast_UG,HM_Window_HZ_UG,mySmP1,HM_68D27D_GarageV,OG_WZ_Weather,EG_WZ_Weather
eventCount 18658
prefix mqtt
CHANGED:
incoming-count: 1594
updated-reading-count: 9474
updated-reading-count: 9475
updated-reading-count: 9476
updated-reading-count: 9477
updated-reading-count: 9478
updated-reading-count: 9479
updated-reading-count: 9480
updated-reading-count: 9481
updated-reading-count: 9482
updated-reading-count: 9483
updated-reading-count: 9484
updated-reading-count: 9485
READINGS:
2023-08-12 09:03:06 IODev MQTT2_CLIENT
2023-08-12 09:03:06 device-count 28
2023-08-12 17:16:30 incoming-count 1594
2023-08-12 17:15:48 outgoing-count 18646
2023-08-12 17:15:48 transmission-state outgoing publish sent
2023-08-12 17:16:30 updated-reading-count 9485
2023-08-12 09:03:04 updated-set-count 0
devices:
BM_1A8215:
:alias:
:publish:
brightness:
last 1691852126.56589
mode R
topic {"BBB11/BM_1A8215/$name"}
motion:
last 1691843122.01271
mode R
topic {"BBB11/BM_1A8215/$name"}
Brunnen_20C4F6:
:alias:
:defaults:
pub:base {"BBB11/$device"}
sub:base {"BBB11/$device"}
:publish:
state:
last 1691853116.93045
mode R
retain 1
topic fhem/status/alarm/Brunnen
:subscribe:
HASH(0x40d3538)
EG_WZ_Weather:
:alias:
:publish:
humidity:
last 1691853347.96577
mode R
topic {"BBB11/EG_WZ_Weather/$name"}
measured-temp:
last 1691853348.0356
mode R
topic {"BBB11/EG_WZ_Weather/$name"}
GosSM:
:subscribe:
HASH(0x3dd8220)
HASH(0x3fcb0f0)
GosTR:
:subscribe:
HASH(0x3f53c88)
HASH(0x3aaccc0)
HASH(0x40e5420)
HASH(0x3b22540)
HASH(0x3aacf00)
GosWM:
:subscribe:
HASH(0x3b22ba0)
HASH(0x3b26918)
HASH(0x3aad800)
HASH(0x3b26cf0)
HASH(0x3aadae8)
HM_2D0D4F:
:alias:
:publish:
brightness:
last 1691850861.26762
mode R
topic {"BBB11/HM_2D0D4F/$name"}
motion:
last 1691843191.23171
mode R
topic {"BBB11/HM_2D0D4F/$name"}
HM_68D27D_GarageV:
:alias:
:publish:
state:
last 1691830882.09477
mode R
retain 1
topic fhem/status/window/HM_68D27D_GarageV
HM_69F07B:
:alias:
:publish:
brightness:
last 1691853113.10891
mode R
topic {"BBB11/HM_69F07B/$name"}
motion:
last 1691848125.38337
mode R
topic {"BBB11/HM_69F07B/$name"}
HM_69F136:
:publish:
brightness:
mode R
topic {"BBB11/HM_69F136/$name"}
motion:
mode R
topic {"BBB11/HM_69F136/$name"}
HM_69F161:
:alias:
:publish:
brightness:
last 1691853343.05211
mode R
topic {"BBB11/HM_69F161/$name"}
motion:
last 1691839898.30495
mode R
topic {"BBB11/HM_69F161/$name"}
HM_Window_BadOG:
:alias:
:publish:
state:
last 1691826693.27032
mode R
retain 1
topic fhem/status/window/HM_Window_BadOG
HM_Window_Gast_UG:
:alias:
:publish:
state:
last 1691846199.72083
mode R
retain 1
topic fhem/status/window/HM_Window_Gast_UG
HM_Window_HZ_UG:
:publish:
state:
mode R
retain 1
topic fhem/status/window/HM_Window_HZ_UG
HM_Window_WK_UG:
:publish:
state:
mode R
retain 1
topic fhem/status/window/HM_Window_WK_UG
HM_Window_WS_UG:
:publish:
state:
mode R
retain 1
topic fhem/status/window/HM_Window_WS_UG
Licht_WaKue:
:alias:
:publish:
state:
last 1691842880.5753
mode R
retain 1
topic fhem/status/light/ug_alarm_waschk
OG_WZ_Weather:
:alias:
:publish:
humidity:
last 1691853339.94044
mode R
topic {"BBB11/OG_WZ_Weather/$name"}
measured-temp:
last 1691853340.01325
mode R
topic {"BBB11/OG_WZ_Weather/$name"}
Pow1:
:subscribe:
HASH(0x3b26ac8)
HASH(0x3b26b58)
HASH(0x3b22b88)
Pow2:
:subscribe:
HASH(0x40cfe58)
HASH(0x3ed9550)
HASH(0x3b21ad0)
T1:
:alias:
:publish:
state:
last 1691853123.44573
mode R
topic BBB11/ESAG/T1/state
T6:
:alias:
:publish:
state:
last 1691850603.51628
mode R
topic BBB11/ESAG/T6/state
Waermebedarf:
:publish:
state:
expression {($value eq 'off')?'stop':($value eq 'idle')?'off':'on'}
mode R
retain 1
topic fhem/status/alarm/hz_waermebedarf
Wlan_Garten:
:subscribe:
HASH(0x3aad008)
esagcom:
:alias:
:publish:
state:
expression {($value eq 'off')?'stop':'on'}
last 1691824099.46899
mode R
retain 1
topic fhem/status/alarm/hz_esag_com
myZisterne:
:publish:
G_Wasser:
expression {($value eq '1')?'druck':'off'}
mode R
retain 1
topic fhem/status/alarm/Gartenwasser
:subscribe:
HASH(0x417cf70)
HASH(0x3d5e818)
HASH(0x3fb1d38)
HASH(0x3dd4fb0)
sp111_3:
:subscribe:
HASH(0x3d704d0)
HASH(0x360bb08)
HASH(0x40d3268)
sp1_5:
:subscribe:
HASH(0x417d030)
HASH(0x3b221c0)
HASH(0x3f7d3c0)
globalDeviceExcludes:
globalReadingExcludes:
globalTypeExcludes:
pub:
FHEMWEB *
Global *
MQTT transmission-state
MQTT_BRIDGE transmission-state
MQTT_DEVICE transmission-state
MQTT_GENERIC_BRIDGE *
telnet *
sub:
FHEMWEB *
Global *
MQTT transmission-state
MQTT_BRIDGE transmission-state
MQTT_DEVICE transmission-state
MQTT_GENERIC_BRIDGE *
telnet *
subscribe:
Attributes:
IODev MQTT2_CLIENT
disable 0
group 1_Gateway
icon mqtt_bridge_1
stateFormat DeviceCount device-count
Billy
ZitatIch hatte eigentlich erwartet, dass ich die generic bridge direkt an m2server als IODev verwenden kann.
Das geht ja auch, wenn man es richtig macht => clientOrder an m2server muss u.a. passen....
Hast du mir einen Link der mir weiterhilft?
Müßte in der Attribut-Hilfe bei MQTT2_SERVER zu finden sein...
Ist aber doch kein Suchwort, das das forum nicht annimmt, oder?
Die Suche nach fhem clientorder an mqtt2server hat mir den Link zur https://wiki.fhem.de/wiki/MQTT gebracht! :)
Dort wird Einstellung attr <mqtt2_server> clientOrder MQTT_GENERIC_BRIDGE MQTT2_DEVICE vorgeschlagen.
Damit läuft es mit der Anbindung an m2server, MQTT2_CLIENT habe ich wieder gelöscht.
Danke für deinen Hinweis und schönes Wochenende.
Billy