Frage zu zigbee2mqtt und autocreate

Begonnen von ronzo, 20 Februar 2023, 18:48:35

Vorheriges Thema - Nächstes Thema

ronzo

Ich habe mir laut Wiki für zigbee2mqtt eine "Bridge" eingerichtet. (https://wiki.fhem.de/wiki/Zigbee2mqtt#Define_eines_MQTT2-Devices_als_.22Bridge.22) Auch das attrTemplate habe ich - wie im Wiki beschrieben - angewandt.

Ich sehe auch das derzeit einzige zigbee2mqtt device:

2023-02-20 18:23:18 MQTT2_DEVICE MQTT2_zigbee2mqtt log_message: MQTT publish: topic 'zigbee2mqtt/0xf0d1b800001b0193', payload '{"color_mode":"xy","linkquality":163,"power_on_behavior":null,"state":"ON","update":{"installed_version":1061121,"latest_version":17196032,"state":"available"},"update_available":null}'
2023-02-20 18:23:18 MQTT2_DEVICE MQTT2_zigbee2mqtt log_level: info
2023-02-20 18:23:19 MQTT2_DEVICE MQTT2_zigbee2mqtt log_level: info
2023-02-20 18:23:19 MQTT2_DEVICE MQTT2_zigbee2mqtt log_message: MQTT publish: topic 'zigbee2mqtt/0xf0d1b800001b0193', payload '{"color_mode":"xy","linkquality":167,"power_on_behavior":null,"state":"OFF","update":{"installed_version":1061121,"latest_version":17196032,"state":"available"},"update_available":null}'


Aber das device wird mir per autocreate offenbar nicht angelegt. Was ist mir hier entgangen bzw. was mache ich vermutlich falsch?

ronzo

#1
Habe schon einen Verdacht. Im Beispiel aus dem Wiki steht:

defmod MQTT2_zigbee_pi MQTT2_DEVICE zigbee_pi
attr MQTT2_zigbee_pi IODev MQTT2_FHEM_Server
attr MQTT2_zigbee_pi readingList zigbee_pi:zigbee2mqtt/bridge/state:.* state\
  zigbee_pi:zigbee2mqtt/0x90fd9ffffe65db16:.* { json2nameValue($EVENT, ) }\
  zigbee_pi:zigbee2mqtt/0x90fd9ffffe0bcd51:.* { json2nameValue($EVENT, ) }\
  zigbee_pi:zigbee2mqtt/bridge/log:.* { json2nameValue($EVENT, 'log_') }
attr MQTT2_zigbee_pi room MQTT2_DEVICE


Wofür steht hier "0x90fd9ffffe65db16" und "0x90fd9ffffe0bcd51"? Wenn ich Mosquitto zusehe, sehe ich nur "0xf0d1b800001b0194".

Nach obiger Definition der Bridge habe ich das attrTempl angewandt. Danach steht im Attribut ReadingList ohnehin nichts mehr von

zigbee_pi:zigbee2mqtt/bridge/state:.* state\
  zigbee_pi:zigbee2mqtt/0x90fd9ffffe65db16:.* { json2nameValue($EVENT, ) }\
  zigbee_pi:zigbee2mqtt/0x90fd9ffffe0bcd51:.* { json2nameValue($EVENT, ) }\
  zigbee_pi:zigbee2mqtt/bridge/log:.* { json2nameValue($EVENT, 'log_') }


Vielleicht kann hier ein Wissender hier kurz ein paar Worte darüber verlieren! Ich wäre echt dankbar!

vbs

Ich würde mich jetzt nicht als Wissenden bezeichnen, aber ich versuch mal...

Also auf jeden Fall solltest du mal alle lists von deinen MQTT-Devices (MQTT2_CLIENT, MQTT2_SERVER, MQTT2_DEVICE) posten. Das würden Profis auch verlangen...

Vermutung:
Noch bevor du das zigbeeBridge-Device angelegt hast, wurde schon (unbemerkt) ein MQTT2_DEVICE angelegt, welches jetzt die Nachrichten "absorbiert" bevor deine neue zigbee-Bridge das autocreate ausführen kann. Also guck doch mal mit "list TYPE=MQTT2_DEVICE", ob nicht doch schon was angelegt wurde.

vbs

Zitat von: ronzo am 20 Februar 2023, 19:46:40
Wofür steht hier "0x90fd9ffffe65db16" und "0x90fd9ffffe0bcd51"? Wenn ich Mosquitto zusehe, sehe ich nur "0xf0d1b800001b0194".
Das sind die internen IDs, die z2m den Geräten vergibt. Die siehst du, solange du in z2m keine lesbaren Namen vergeben hast.

ronzo

Zitat von: vbs am 20 Februar 2023, 23:07:12
Ich würde mich jetzt nicht als Wissenden bezeichnen, aber ich versuch mal...

Also auf jeden Fall solltest du mal alle lists von deinen MQTT-Devices (MQTT2_CLIENT, MQTT2_SERVER, MQTT2_DEVICE) posten. Das würden Profis auch verlangen...

Vermutung:
Noch bevor du das zigbeeBridge-Device angelegt hast, wurde schon (unbemerkt) ein MQTT2_DEVICE angelegt, welches jetzt die Nachrichten "absorbiert" bevor deine neue zigbee-Bridge das autocreate ausführen kann. Also guck doch mal mit "list TYPE=MQTT2_DEVICE", ob nicht doch schon was angelegt wurde.

OK. Ich fang mal mit ein paar Details an. Der MQTT-Server ist Mosquitto und somit extern. In FHEM sprech ich den über ein MQTT2_CLIENT-Device an. Ansonsten hab ich noch eine MQTT_GENERIC_BRIDGE im Einsatz um einzelne Homematic-Devices für ein Drittsystem sicht- und schaltbar zu machen. Das zigbee2mqtt Bridge-Device (MQTT2_DEVICE) ist FHEM-weit das einzige seiner Art.

vbs

Also das MQTT_GENERIC_BRIDGE kenn ich nicht. Kann nicht ausschließen, dass es damit zusammen hängt bzw. dass das irgendwas "wegfängt". Falls möglich einfach mal löschen - um sicher zu gehen.

Ansonsten: autocreate ist aktiv? Also sowohl global als auch im MQTT2_CLIENT und in der z2m-Bridge?

Ich geh mal davon aus, dass MQTT2_CLIENT connectet ist, da man ja die MQTT-Nachrichten im Log sieht?

Vielleicht hast du ja doch nochmal Lust, die Listing zu posten.

ronzo

#6
Funktioniert schon. Am mqtt_io device (MQTT2_CLIENT) war das Autocreate nicht aktiv. Dort gibt es simple und complex. Da mir das fürs Erste bis hier mal schon fast zu "complex" war, hab ich es mal auf simple gestellt.  ???

Ich bilde mir aber ein gelesen zu haben, dass sich das Autocreate bei diesem Device nicht mit der MQTT_GENERIC_BRIDGE verträgt, die es ebenfalls als IO-Device verwendet. (Deshalb deaktiviere ich das Autocreate auf dem IO-Device vorsichtshalber nochmal, bis ich das hier restlos klären konnte...)

ronzo

#7
Eigentlich würde dieser Thread wohl eher in MQTT reingehören als hier her... vielleicht kann ein Admin ihn dort hin verschieben?

Ich sehe schon. Lasse ich am IO-Device (MQTT2_CLIENT) das Autocreate auf "simple", dann wird mir bei jeder Aktion, die über die MQTT_GENERIC_BRIDGE passiert am IO-Device die ReadingList erweitert. Das stört zwar nicht sonderlich, nur wirklich brauchen kann ich es da auch nicht.

Wie kann ich dem entgegnen? Je ein eigenes IO-Device für zigbee2mqtt und mqtt_generic_bridge? Filtern der Topics? Etwas ganz anderes?

Beta-User

clientOrder?Verschieben kannst du selbst.
Server: HP-elitedesk@Debian 12, aktuelles FHEM@ConfigDB | CUL_HM (VCCU) | MQTT2: MiLight@ESP-GW, BT@OpenMQTTGw | MySensors: seriell, v.a. 2.3.1@RS485 | ZWave | ZigBee@deCONZ | SIGNALduino | MapleCUN | RHASSPY
svn: u.a MySensors, Weekday-&RandomTimer, Twilight,  div. attrTemplate-files

ronzo

Besten Dank!
(Hier sind alle mit Magen-Darm-Virus und Fieber zu Hause. Nicht ganz leicht nebenbei konzentriert etwas zu schaffen...  ;D)

juergs

#10
Hallo Zusammen,
das mit dem Virus kenne ich auch vom letzten WoE. Gute Besserung!

Dank dem Hinweis von ronzo auf den Wiki-Eintrag, konnte ich meine brachliegende ZigBee-Konstellation ohne größeres Zutun (vorher x-Mal gescheitert)
zum Laufen bringen. Die "Komplexität" bzw. der (mangelnde?) Abstraktionsgrad, besonders als Newbie, ist nicht zu unterschätzen.
Siehe auch: https://forum.fhem.de/index.php/topic,91394.0.html

Meine Konstellation: ZigBee2MQTT (Docker-Instanz) - Mosquitto (Installation,lokal) - FHEM (Installation,lokal)
Ich weiß, dass diese Konstellation laut Wiki nicht zu favorisieren ist.
ZigBee-Devices: 1 Aquara Tür-Sensor, 2 Lidl-Steckdosen, 1 Osram Steckdose.

Hatte vorher auch Konstellationen  mit der "MQTT_GENERIC_BRIDGE" erfolglos herumexperimentiert.

Hier die Definition für eine Steckdose:
defmod MQTT2_zigbee_Lidl_Silvercrest_smart_plug_1 MQTT2_DEVICE zigbee_Lidl_Silvercrest_smart_plug_1
attr MQTT2_zigbee_Lidl_Silvercrest_smart_plug_1 devicetopic zigbee2mqtt/Lidl_Silvercrest_smart_plug_1
attr MQTT2_zigbee_Lidl_Silvercrest_smart_plug_1 icon message_socket
attr MQTT2_zigbee_Lidl_Silvercrest_smart_plug_1 model zigbee2mqtt_plug
attr MQTT2_zigbee_Lidl_Silvercrest_smart_plug_1 readingList $DEVICETOPIC:.* { my $ret=json2nameValue($EVENT);; $ret->{state}=lc($ret->{state}) if defined $ret->{state};; return $ret }\
zigbee2mqtt/Lidl_Silvercrest_smart_plug_1/set:.* { json2nameValue($EVENT) }
attr MQTT2_zigbee_Lidl_Silvercrest_smart_plug_1 room MQTT2_DEVICE
attr MQTT2_zigbee_Lidl_Silvercrest_smart_plug_1 setList on:noArg $DEVICETOPIC/set {"state":"ON"}\
  off:noArg $DEVICETOPIC/set {"state":"OFF"}\
  toggle:noArg $DEVICETOPIC/set {"state":"TOGGLE"}
attr MQTT2_zigbee_Lidl_Silvercrest_smart_plug_1 setStateList on off toggle

setstate MQTT2_zigbee_Lidl_Silvercrest_smart_plug_1 on
setstate MQTT2_zigbee_Lidl_Silvercrest_smart_plug_1 2023-02-16 16:12:18 IODev mqttclient
setstate MQTT2_zigbee_Lidl_Silvercrest_smart_plug_1 2023-02-22 15:58:47 associatedWith MQTT2_zigbee2mqtt
setstate MQTT2_zigbee_Lidl_Silvercrest_smart_plug_1 2023-02-22 15:58:40 attrTemplateVersion 20220909
setstate MQTT2_zigbee_Lidl_Silvercrest_smart_plug_1 2023-02-22 16:07:28 json2nameValueErrorText error parsing (#2) 'ON'
setstate MQTT2_zigbee_Lidl_Silvercrest_smart_plug_1 2023-02-22 16:07:28 json2nameValueInput ON
setstate MQTT2_zigbee_Lidl_Silvercrest_smart_plug_1 2023-02-22 17:03:28 linkquality 107
setstate MQTT2_zigbee_Lidl_Silvercrest_smart_plug_1 2023-02-22 15:54:52 set ON
setstate MQTT2_zigbee_Lidl_Silvercrest_smart_plug_1 2023-02-22 17:03:28 state on


defmod MQTT2_zigbee_Eingangst MQTT2_DEVICE zigbee_Eingangst
attr MQTT2_zigbee_Eingangst devStateIcon open:fts_door_open@red closed:fts_door@green
attr MQTT2_zigbee_Eingangst devicetopic zigbee2mqtt/Eingangst\xc3\xbcr-Sensor
attr MQTT2_zigbee_Eingangst icon fts_door
attr MQTT2_zigbee_Eingangst jsonMap contact:state
attr MQTT2_zigbee_Eingangst model zigbee2mqtt_ContactSensor
attr MQTT2_zigbee_Eingangst readingList $DEVICETOPIC:.* { my $ret=json2nameValue($EVENT,'',$JSONMAP);; $ret->{state}=$ret->{state} eq 'true' ? 'closed' : 'open';; return $ret }
attr MQTT2_zigbee_Eingangst room MQTT2_DEVICE

setstate MQTT2_zigbee_Eingangst closed
setstate MQTT2_zigbee_Eingangst 2023-02-16 16:12:18 IODev mqttclient
setstate MQTT2_zigbee_Eingangst 2023-02-02 23:35:17 associatedWith MQTT2_mqttclient
setstate MQTT2_zigbee_Eingangst 2023-02-22 15:59:34 attrTemplateVersion 20220622
setstate MQTT2_zigbee_Eingangst 2023-02-22 17:04:12 battery 100
setstate MQTT2_zigbee_Eingangst 2023-02-22 17:04:12 device_temperature 25
setstate MQTT2_zigbee_Eingangst 2023-02-22 17:04:12 linkquality 86
setstate MQTT2_zigbee_Eingangst 2023-02-22 17:04:12 power_outage_count 85
setstate MQTT2_zigbee_Eingangst 2023-02-22 17:04:12 state closed
setstate MQTT2_zigbee_Eingangst 2023-02-22 17:04:12 voltage 3015


Hier das Device mit richtig gesetztem DeviceTopic:
Zitatdefmod MQTT2_zigbee2mqtt MQTT2_DEVICE zigbee2mqtt
attr MQTT2_zigbee2mqtt bridgeRegexp zigbee2mqtt/([A-Za-z0-9._]+)[/]?.*:.* "zigbee_$1"
attr MQTT2_zigbee2mqtt comment To check for new updates of the deamon software, you might want to use a separate HTTPMOD device. See HTTPMOD template zigbee2mqtt_daemon_updates for further details.
attr MQTT2_zigbee2mqtt devicetopic zigbee2mqtt
attr MQTT2_zigbee2mqtt getList networkmap_raw:noArg raw $DEVICETOPIC/bridge/request/networkmap raw\
  networkmap_graphviz:noArg graphviz $DEVICETOPIC/bridge/request/networkmap graphviz
attr MQTT2_zigbee2mqtt icon mqtt
attr MQTT2_zigbee2mqtt model zigbee2mqtt_bridge
attr MQTT2_zigbee2mqtt readingList $DEVICETOPIC/bridge/state:.* state\
  $DEVICETOPIC/bridge/config/devices:.* {}\
  $DEVICETOPIC/bridge/config/log_level:.* log_level\
  $DEVICETOPIC/bridge/config/permit_join:.* permit_join\
  $DEVICETOPIC/bridge/config/rename:.* { json2nameValue($EVENT, 'rename_') }\
  $DEVICETOPIC/bridge/config:.* { json2nameValue($EVENT) }\
  $DEVICETOPIC/bridge/log:.*\"type\".\"devices\".\"message\".* devices\
  $DEVICETOPIC/bridge/log:.* log\
  $DEVICETOPIC/bridge/logging:.* { json2nameValue($EVENT,'log_') }\
  $DEVICETOPIC/bridge/response/networkmap:.* { my $type = $EVENT =~ m/.*,"type":"(raw|graphviz)",.*/ ? $1 : 'networkmap';; $EVENT =~ m/{"data":\{.*"value":"?(.*[^"])"?\},"status":"ok"\}/ ? { $type=>$1 } : {} }\
  $DEVICETOPIC/bridge/devices:.* devices\
  $DEVICETOPIC/bridge/info:.* info\
  $DEVICETOPIC/bridge/groups:.* groups\
  $DEVICETOPIC/bridge/event:.* { json2nameValue($EVENT) }\
  $DEVICETOPIC/bridge/extensions:.* extensions
attr MQTT2_zigbee2mqtt room MQTT,MQTT2_DEVICE
attr MQTT2_zigbee2mqtt setList log_level:debug,info,warn,error $DEVICETOPIC/bridge/config/log_level $EVTPART1\
  permit_join:true,false $DEVICETOPIC/bridge/request/permit_join $EVTPART1\
  remove:textField $DEVICETOPIC/bridge/config/remove $EVTPART1\
  ota_update:textField $DEVICETOPIC/bridge/ota_update/update $EVTPART1\
  ota_update_check:textField $DEVICETOPIC/bridge/ota_update/check $EVTPART1\
  y_device_setting:textField $DEVICETOPIC/$EVTPART1/set {"$EVTPART2": "$EVTPART3"}\
  x_bind:textField $DEVICETOPIC/bridge/bind/$EVTPART1 $EVTPART2\
  x_bind_unbind:textField $DEVICETOPIC/bridge/unbind/$EVTPART1 $EVTPART2\
  x_device_options:textField $DEVICETOPIC/bridge/config/device_options {"friendly_name":"$EVTPART1","options": {"$EVTPART2": "$EVTPART3"}}\
  x_group_add_to:textField $DEVICETOPIC/bridge/group/$EVTPART1/add $EVTPART2\
  x_group_rm_from:textField $DEVICETOPIC/bridge/group/$EVTPART1/remove $EVTPART2\
  x_group_rm_from_all:textField $DEVICETOPIC/bridge/group/$EVTPART1/remove_all $EVTPART2\
  x_group_add_group:textField $DEVICETOPIC/bridge/config/add_group $EVTPART1\
  x_group_rm_group:textField $DEVICETOPIC/bridge/config/remove_group $EVTPART1\
  z_elapsed:textField $DEVICETOPIC/bridge/config/elapsed $EVTPART1\
  z_last_seen:disable,ISO_8601,epoch,ISO_8601_local $DEVICETOPIC/bridge/config/last_seen $EVTPART1\
  z_ban:textField $DEVICETOPIC/bridge/config/ban $EVTPART1\
  z_rename:textField $DEVICETOPIC/bridge/config/rename  {"old":"$EVTPART1","new":"$EVTPART2"}\
  z_reset_CC:noArg $DEVICETOPIC/bridge/config/reset
attr MQTT2_zigbee2mqtt setStateList on off

setstate MQTT2_zigbee2mqtt online
setstate MQTT2_zigbee2mqtt 2023-02-22 15:51:52 attrTemplateVersion 20220328
setstate MQTT2_zigbee2mqtt 2023-02-22 16:05:19 data_friendly_name Steckdose_Osram
setstate MQTT2_zigbee2mqtt 2023-02-22 16:05:19 data_ieee_address 0x7cb03eaa0a0673a7
setstate MQTT2_zigbee2mqtt 2023-02-22 16:05:19 devices [{"definition":null,"disabled":false,"endpoints":{"1":{"bindings":[],"clusters":{"input":[],"output":[]},"configured_reportings":[],"scenes":[]},"10":{"bindings":[],"clusters":{"input":[],"output":[]},"configured_reportings":[],"scenes":[]},"11":{"bindings":[],"clusters":{"input":["ssIasAce","genTime"],"output":["ssIasZone","ssIasWd"]},"configured_reportings":[],"scenes":[]},"110":{"bindings":[],"clusters":{"input":[],"output":[]},"configured_reportings":[],"scenes":[]},"12":{"bindings":[],"clusters":{"input":[],"output":[]},"configured_reportings":[],"scenes":[]},"13":{"bindings":[],"clusters":{"input":["genOta"],"output":[]},"configured_reportings":[],"scenes":[]},"2":{"bindings":[],"clusters":{"input":[],"output":[]},"configured_reportings":[],"scenes":[]},"242":{"bindings":[],"clusters":{"input":[],"output":[]},"configured_reportings":[],"scenes":[]},"3":{"bindings":[],"clusters":{"input":[],"output":[]},"configured_reportings":[],"scenes":[]},"4":{"bindings":[],"clusters":{"input":[],"output":[]},"configured_reportings":[],"scenes":[]},"47":{"bindings":[],"clusters":{"input":[],"output":[]},"configured_reportings":[],"scenes":[]},"5":{"bindings":[],"clusters":{"input":[],"output":[]},"configured_reportings":[],"scenes":[]},"6":{"bindings":[],"clusters":{"input":[],"output":[]},"configured_reportings":[],"scenes":[]},"8":{"bindings":[],"clusters":{"input":[],"output":[]},"configured_reportings":[],"scenes":[]}},"friendly_name":"Coordinator","ieee_address":"0x00124b001cdd3274","interview_completed":true,"interviewing":false,"network_address":0,"supported":false,"type":"Coordinator"},{"date_code":"20161128","definition":{"description":"Aqara door & window contact sensor","exposes":[{"access":1,"description":"Remaining battery in %","name":"battery","property":"battery","type":"numeric","unit":"%","value_max":100,"value_min":0},{"access":1,"description":"Indicates if the contact is closed (= true) or open (= false)","name":"contact","property":"contact","type":"binary","value_off":true,"value_on":false},{"access":1,"description":"Temperature of the device","name":"device_temperature","property":"device_temperature","type":"numeric","unit":"°C"},{"access":1,"description":"Voltage of the battery in millivolts","name":"voltage","property":"voltage","type":"numeric","unit":"mV"},{"access":1,"description":"Number of power outages","name":"power_outage_count","property":"power_outage_count","type":"numeric"},{"access":1,"description":"Link quality (signal strength)","name":"linkquality","property":"linkquality","type":"numeric","unit":"lqi","value_max":255,"value_min":0}],"model":"MCCGQ11LM","options":[{"access":2,"description":"Calibrates the device_temperature value (absolute offset), takes into effect on next report of device.","name":"device_temperature_calibration","property":"device_temperature_calibration","type":"numeric"}],"supports_ota":false,"vendor":"Xiaomi"},"disabled":false,"endpoints":{"1":{"bindings":[],"clusters":{"input":["genBasic","genIdentify","65535","genOnOff"],"output":["genBasic","genGroups","65535"]},"configured_reportings":[],"scenes":[]}},"friendly_name":"Eingangstür-Sensor","ieee_address":"0x00158d0008e0fac7","interview_completed":true,"interviewing":false,"manufacturer":"LUMI","model_id":"lumi.sensor_magnet.aq2","network_address":49633,"power_source":"Battery","software_build_id":"3000-0001","supported":true,"type":"EndDevice"},{"date_code":"20140331DEOS****","definition":{"description":"Smart+ plug","exposes":[{"features":[{"access":7,"description":"On/off state of the switch","name":"state","property":"state","type":"binary","value_off":"OFF","value_on":"ON","value_toggle":"TOGGLE"}],"type":"switch"},{"access":1,"description":"Link quality (signal strength)","name":"linkquality","property":"linkquality","type":"numeric","unit":"lqi","value_max":255,"value_min":0}],"model":"AB3257001NJ","options":[],"supports_ota":true,"vendor":"OSRAM"},"disabled":false,"endpoints":{"3":{"bindings":[{"cluster":"genOnOff","target":{"endpoint":1,"ieee_address":"0x00124b001cdd3274","type":"endpoint"}}],"clusters":{"input":["touchlink","genBasic","genIdentify","genGroups","genScenes","genOnOff","haElectricalMeasurement","manuSpecificOsram"],"output":["genOta"]},"configured_reportings":[{"attribute":"onOff","cluster":"genOnOff","maximum_report_interval":3600,"minimum_report_interval":0,"reportable_change":0}],"scenes":[]}},"friendly_name":"Steckdose_Osram","ieee_address":"0x7cb03eaa0a0673a7","interview_completed":true,"interviewing":false,"manufacturer":"OSRAM","model_id":"Plug 01","network_address":31579,"power_source":"Mains (single phase)","software_build_id":"V1.04.90","supported":true,"type":"Router"},{"date_code":"","definition":{"description":"Silvercrest smart plug (EU, CH, FR, BS, DK)","exposes":[{"features":[{"access":7,"description":"On/off state of the switch","name":"state","property":"state","type":"binary","value_off":"OFF","value_on":"ON","value_toggle":"TOGGLE"}],"type":"switch"},{"access":1,"description":"Link quality (signal strength)","name":"linkquality","property":"linkquality","type":"numeric","unit":"lqi","value_max":255,"value_min":0}],"model":"HG06337","options":[],"supports_ota":false,"vendor":"Lidl"},"disabled":false,"endpoints":{"1":{"bindings":[],"clusters":{"input":[],"output":[]},"configured_reportings":[],"scenes":[]},"11":{"bindings":[{"cluster":"genOnOff","target":{"endpoint":1,"ieee_address":"0x00124b001cdd3274","type":"endpoint"}}],"clusters":{"input":["genBasic","genIdentify","genGroups","genScenes","genOnOff"],"output":["genOta","genTime"]},"configured_reportings":[],"scenes":[]},"242":{"bindings":[],"clusters":{"input":[],"output":["greenPower"]},"configured_reportings":[],"scenes":[]}},"friendly_name":"Lidl_Silvercrest_smart_plug_1","ieee_address":"0x0c4314fffe37dd0a","interview_completed":true,"interviewing":false,"manufacturer":"_TZ3000_kdi2o9m6","model_id":"TS011F","network_address":46540,"power_source":"Mains (single phase)","supported":true,"type":"Router"}]
setstate MQTT2_zigbee2mqtt 2023-02-22 15:54:33 graphviz digraph G {\nnode[shape=record];;\n  \"0x00124b001cdd3274\" [style=\"bold, filled\", fillcolor=\"#e04e5d\", fontcolor=\"#ffffff\", label=\"{Coordinator|0x00124b001cdd3274 (0x0000)|0 seconds ago}\"];;\n  \"0x00124b001cdd3274\" -> \"0x0c4314fffe37dd0a\" [penwidth=0.5, weight=0, color=\"#994444\", label=\"200\"]\n  \"0x00158d0008e0fac7\" [style=\"rounded, dashed, filled\", fillcolor=\"#fff8ce\", fontcolor=\"#000000\", label=\"{Eingangstür-Sensor|0x00158d0008e0fac7 (0xc1e1)|Xiaomi Aqara door & window contact sensor (MCCGQ11LM)|3 minutes, 14 seconds ago}\"];;\n  \"0x00158d0008e0fac7\" -> \"0x00124b001cdd3274\" [penwidth=1, weight=0, color=\"#994444\", label=\"121\"]\n  \"0x7cb03eaa0a0673a7\" [style=\"rounded, filled\", fillcolor=\"#4ea3e0\", fontcolor=\"#ffffff\", label=\"{Steckdose_Osram|0x7cb03eaa0a0673a7 (0x7b5b)failed: lqi|OSRAM Smart+ plug (AB3257001NJ)|2 weeks, 5 days ago}\"];;\n  \"0x7cb03eaa0a0673a7\" -> \"0x00124b001cdd3274\" [penwidth=0.5, weight=0, color=\"#994444\", label=\"0\"]\n  \"0x0c4314fffe37dd0a\" [style=\"rounded, filled\", fillcolor=\"#4ea3e0\", fontcolor=\"#ffffff\", label=\"{Lidl_Silvercrest_smart_plug_1|0x0c4314fffe37dd0a (0xb5cc)|Lidl Silvercrest smart plug (EU, CH, FR, BS, DK) (HG06337)|1 minute, 38 seconds ago}\"];;\n  \"0x0c4314fffe37dd0a\" -> \"0x00124b001cdd3274\" [penwidth=0.5, weight=0, color=\"#994444\", label=\"107\"]\n}
setstate MQTT2_zigbee2mqtt 2023-02-22 16:05:19 log {"message":"announce","meta":{"friendly_name":"Steckdose_Osram"},"type":"device_announced"}
setstate MQTT2_zigbee2mqtt 2023-02-22 17:22:11 log_level info
setstate MQTT2_zigbee2mqtt 2023-02-22 17:22:11 log_message MQTT publish: topic 'zigbee2mqtt/Steckdose_Osram', payload '{"linkquality":78,"state":"OFF"}'
setstate MQTT2_zigbee2mqtt 2023-02-22 15:54:43 raw {"links":[{"depth":1,"linkquality":121,"lqi":121,"relationship":1,"routes":[],"source":{"ieeeAddr":"0x00158d0008e0fac7","networkAddress":49633},"sourceIeeeAddr":"0x00158d0008e0fac7","sourceNwkAddr":49633,"target":{"ieeeAddr":"0x00124b001cdd3274","networkAddress":0},"targetIeeeAddr":"0x00124b001cdd3274"},{"depth":1,"linkquality":0,"lqi":0,"relationship":1,"routes":[],"source":{"ieeeAddr":"0x7cb03eaa0a0673a7","networkAddress":31579},"sourceIeeeAddr":"0x7cb03eaa0a0673a7","sourceNwkAddr":31579,"target":{"ieeeAddr":"0x00124b001cdd3274","networkAddress":0},"targetIeeeAddr":"0x00124b001cdd3274"},{"depth":1,"linkquality":106,"lqi":106,"relationship":1,"routes":[],"source":{"ieeeAddr":"0x0c4314fffe37dd0a","networkAddress":46540},"sourceIeeeAddr":"0x0c4314fffe37dd0a","sourceNwkAddr":46540,"target":{"ieeeAddr":"0x00124b001cdd3274","networkAddress":0},"targetIeeeAddr":"0x00124b001cdd3274"},{"depth":0,"linkquality":200,"lqi":200,"relationship":0,"routes":[],"source":{"ieeeAddr":"0x00124b001cdd3274","networkAddress":0},"sourceIeeeAddr":"0x00124b001cdd3274","sourceNwkAddr":0,"target":{"ieeeAddr":"0x0c4314fffe37dd0a","networkAddress":46540},"targetIeeeAddr":"0x0c4314fffe37dd0a"}],"nodes":[{"definition":null,"failed":[],"friendlyName":"Coordinator","ieeeAddr":"0x00124b001cdd3274","lastSeen":1674143401938,"networkAddress":0,"type":"Coordinator"},{"definition":{"description":"Aqara door & window contact sensor","model":"MCCGQ11LM","supports":"battery, contact, device_temperature, voltage, power_outage_count, linkquality","vendor":"Xiaomi"},"friendlyName":"Eingangstür-Sensor","ieeeAddr":"0x00158d0008e0fac7","lastSeen":1677077479274,"manufacturerName":"LUMI","modelID":"lumi.sensor_magnet.aq2","networkAddress":49633,"type":"EndDevice"},{"definition":{"description":"Smart+ plug","model":"AB3257001NJ","supports":"switch (state), linkquality","vendor":"OSRAM"},"failed":["lqi"],"friendlyName":"Steckdose_Osram","ieeeAddr":"0x7cb03eaa0a0673a7","lastSeen":1675441104165,"manufacturerName":"OSRAM","modelID":"Plug 01","networkAddress":31579,"type":"Router"},{"definition":{"description":"Silvercrest smart plug (EU, CH, FR, BS, DK)","model":"HG06337","supports":"switch (state), linkquality","vendor":"Lidl"},"failed":[],"friendlyName":"Lidl_Silvercrest_smart_plug_1","ieeeAddr":"0x0c4314fffe37dd0a","lastSeen":1677077574607,"manufacturerName":"_TZ3000_kdi2o9m6","modelID":"TS011F","networkAddress":46540,"type":"Router"}]}
setstate MQTT2_zigbee2mqtt 2023-02-22 16:05:19 type device_announce

Ich glaube ein Grundproblem ist es im zigBee-Umfeld erst mal ein Verständnis für die "Templates" zu entwickeln.
Beim Zuweisen des passenden Templates (zigbee2mqtt_plug) und betätigen des Schalters haben sich die Devices automatisch erzeugt.
Ebenso für den Türsensor mit dem Template  zigbee2mqtt_ContactSensor-Template.
Hatte also kein Problem mit autocreate etc.  Alle vorher definierten Bridges + Devices habe ich gelöscht.

Die Kommunikation + Konfiguration lässt sich prima mit mqtt.fx oder jedem anderen MQTT-Explorer verifizieren...

Grüße,
Jürgen


ronzo

Was ich noch nicht checke ist, warum mir zu meinem IO-Device (namens "mqtt_io") nun noch ein MQTT2_DEVICE namens "MQTT2_mqtt_io" neben den eigentlichen zigbee2mqtt-Devices angelegt wurde.

Dort landen als readingList-Attribut beispielsweise folgende Einträge:

mqtt_io:mqttGenericBridge/MarkiseUnten:.* MarkiseUnten
mqtt_io:homeassistant/sensor/0x0017880106050d00/battery/config:.* { json2nameValue($EVENT) }



Beta-User

clientOrder und ignoreRegexp anpassen...
Server: HP-elitedesk@Debian 12, aktuelles FHEM@ConfigDB | CUL_HM (VCCU) | MQTT2: MiLight@ESP-GW, BT@OpenMQTTGw | MySensors: seriell, v.a. 2.3.1@RS485 | ZWave | ZigBee@deCONZ | SIGNALduino | MapleCUN | RHASSPY
svn: u.a MySensors, Weekday-&RandomTimer, Twilight,  div. attrTemplate-files

ronzo