Autor Thema: zigbee2mqtt mit MQTT2_SERVER und Homebridge  (Gelesen 429 mal)

Online Udomatic

  • Full Member
  • ***
  • Beiträge: 323
zigbee2mqtt mit MQTT2_SERVER und Homebridge
« am: 17 November 2021, 12:20:35 »
Hallo an die Experten,

ich nutze seit langem den MQTT2_SERVER. Überlege nun von deCONZ auf zigbee2mqtt umzusteigen. Habe soweit alles aufgesetzt incl. Anlernen neuer Geräte über das Frontend und habe anhand der Doku https://wiki.fhem.de/wiki/Zigbee2mqtt ein MQTT_Device angelegt. Lerne ich neue Geräte an werden diese per Autocreate auch in FHEM angelegt.

List zigbee_pi

nternals:
   CFGFN     
   CID        zigbee_pi
   DEF        zigbee_pi
   DEVICETOPIC zigbee2mqtt
   FUUID      619434cf-f33f-45fc-b3d6-5f549874ad5d39e4
   IODev      mqtt2s
   LASTInputDev mqtt2s
   MSGCNT     1160
   NAME       MQTT2_zigbee_pi
   NR         5960
   STATE      ON
   TYPE       MQTT2_DEVICE
   mqtt2s_MSGCNT 1160
   mqtt2s_TIME 2021-11-17 12:07:46
   .attraggr:
   .attrminint:
   OLDREADINGS:
   READINGS:
     2021-11-16 23:58:09   attrTemplateVersion 20211022
     2021-11-17 11:28:51   devices         [{"definition":null,"endpoints":{"1":{"bindings":[],"clusters":{"input":["genBasic","genTime","genOta"],"output":["genPowerCfg","genPollCtrl","ssIasZone"]},"configured_reportings":[],"scenes":[]},"242":{"bindings":[],"clusters":{"input":[],"output":["greenPower"]},"configured_reportings":[],"scenes":[]}},"friendly_name":"Coordinator","ieee_address":"0x00212effff04d542","interview_completed":true,"interviewing":false,"network_address":0,"supported":false,"type":"Coordinator"},{"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"},"endpoints":{"1":{"bindings":[],"clusters":{"input":["genBasic","genIdentify","genGroups","genScenes","genOnOff"],"output":["genOta","genTime"]},"configured_reportings":[],"scenes":[]},"11":{"bindings":[{"cluster":"genOnOff","target":{"endpoint":1,"ieee_address":"0x00212effff04d542","type":"endpoint"}}],"clusters":{"input":["genBasic","genIdentify","genGroups","genScenes","genOnOff"],"output":["genOta","genTime"]},"configured_reportings":[{"attribute":"onOff","cluster":"genOnOff","maximum_report_interval":3600,"minimum_report_interval":0,"reportable_change":0}],"scenes":[]},"242":{"bindings":[],"clusters":{"input":[],"output":["greenPower"]},"configured_reportings":[],"scenes":[]}},"friendly_name":"Lidl Steckdose","ieee_address":"0x60a423fffe0e3567","interview_completed":true,"interviewing":false,"manufacturer":"_TZ3000_kdi2o9m6","model_id":"TS011F","network_address":10279,"power_source":"Mains (single phase)","supported":true,"type":"Router"}]
     2021-11-17 00:00:11   graphviz        digraph G {
node[shape=record];
  "0x00212effff04d542" [style="bold, filled", fillcolor="#e04e5d", fontcolor="#ffffff", label="{Coordinator|0x00212effff04d542 (0x0000)|0 seconds ago}"];
  "0x00212effff04d542" -> "0x60a423fffe0e3567" [penwidth=0.5, weight=0, color="#994444", label="230"]
  "0x60a423fffe0e3567" [style="rounded, filled", fillcolor="#4ea3e0", fontcolor="#ffffff", label="{Lidl Steckdose|0x60a423fffe0e3567 (0x2827)|Lidl Silvercrest smart plug (EU, CH, FR, BS, DK) (HG06337)|6 minutes, 12 seconds ago}"];
  "0x60a423fffe0e3567" -> "0x00212effff04d542" [penwidth=0.5, weight=0, color="#994444", label="255"]
  "0xec1bbdfffee648f5" [style="rounded, dashed, filled", fillcolor="#fff8ce", fontcolor="#000000", label="{0xec1bbdfffee648f5|0xec1bbdfffee648f5 (0x0fa7)|Lidl Silvercrest smart motion sensor (HG06335)|5 minutes, 25 seconds ago}"];
}
     2021-11-17 11:55:59   info            {"commit":"945b72b9","config":{"advanced":{"adapter_concurrent":null,"adapter_delay":null,"availability_blacklist":[],"availability_blocklist":[],"availability_passlist":[],"availability_whitelist":[],"cache_state":true,"cache_state_persistent":true,"cache_state_send_on_startup":true,"channel":11,"elapsed":false,"ext_pan_id":[221,221,221,221,221,221,221,221],"homeassistant_discovery_topic":"homeassistant","homeassistant_legacy_entity_attributes":true,"homeassistant_legacy_triggers":true,"homeassistant_status_topic":"hass/status","last_seen":"disable","legacy_api":true,"log_directory":"/opt/zigbee2mqtt/data/log/%TIMESTAMP%","log_file":"log.txt","log_level":"info","log_output":["console","file"],"log_rotation":true,"log_symlink_current":false,"log_syslog":{},"pan_id":6754,"report":false,"soft_reset_timeout":0,"timestamp_format":"YYYY-MM-DD HH:mm:ss"},"ban":[],"blocklist":[],"device_options":{},"devices":{"0x60a423fffe0e3567":{"friendly_name":"Lidl Steckdose"}},"experimental":{"output":"json"},"external_converters":[],"frontend":{"host":"0.0.0.0","port":8181},"groups":{},"homeassistant":false,"map_options":{"graphviz":{"colors":{"fill":{"coordinator":"#e04e5d","enddevice":"#fff8ce","router":"#4ea3e0"},"font":{"coordinator":"#ffffff","enddevice":"#000000","router":"#ffffff"},"line":{"active":"#009900","inactive":"#994444"}}}},"mqtt":{"base_topic":"zigbee2mqtt","client_id":"zigbee_pi","force_disable_retain":false,"include_device_information":false,"server":"mqtt://192.168.178.55:1883"},"ota":{"disable_automatic_update_check":false,"update_check_interval":1440},"passlist":[],"permit_join":true,"serial":{"disable_led":false,"port":"/dev/ttyACM0"},"whitelist":[]},"config_schema":{"definitions":{"device":{"properties":{"debounce":{"description":"Debounces messages of this device","title":"Debounce","type":"number"},"debounce_ignore":{"description":"Protects unique payload values of specified payload properties from overriding within debounce time","examples":["action"],"items":{"type":"string"},"title":"Ignore debounce","type":"array"},"filtered_attributes":{"description":"Filter attributes from publish payload.","examples":["temperature","battery","action"],"items":{"type":"string"},"title":"Filtered publish attributes","type":"array"},"filtered_optimistic":{"description":"Filter attributes from optimistic publish payload when calling /set. (This has no effect if optimistic is set to false).","examples":["color_mode","color_temp","color"],"items":{"type":"string"},"title":"Filtered optimistic attributes","type":"array"},"friendly_name":{"description":"Used in the MQTT topic of a device. By default this is the device ID","readOnly":true,"title":"Friendly name","type":"string"},"icon":{"description":"The user-defined device icon for the frontend. It can be a link to an image (not a path to a file) or base64 encoded data URL like: image/svg+xml;base64,PHN2ZyB3aW....R0aD","title":"Icon","type":"string"},"optimistic":{"default":true,"description":"Publish optimistic state after set","title":"Optimistic","type":"boolean"},"qos":{"description":"QoS level for MQTT messages of this device","title":"QoS","type":"number"},"retain":{"description":"Retain MQTT messages of this device","title":"Retain","type":"boolean"},"retention":{"description":"Sets the MQTT Message Expiry in seconds, Make sure to set mqtt.version to 5","title":"Retention","type":"number"}},"required":["friendly_name"],"type":"object"},"group":{"properties":{"devices":{"items":{"type":"string"},"type":"array"},"filtered_attributes":{"items":{"type":"string"},"type":"array"},"friendly_name":{"type":"string"},"optimistic":{"type":"boolean"},"qos":{"type":"number"},"retain":{"type":"boolean"}},"required":["friendly_name"],"type":"object"}},"properties":{"advanced":{"properties":{"adapter_concurrent":{"description":"Adapter concurrency (e.g. 2 for CC2531 or 16 for CC26X2R1) (default: null, uses recommended value)","requiresRestart":true,"title":"Adapter concurrency","type":["number","null"]},"adapter_delay":{"description":"Adapter delay","requiresRestart":true,"title":"Adapter delay","type":["number","null"]},"baudrate":{"description":"Baud rate speed for serial port, this can be anything firmware support but default is 115200 for Z-Stack and EZSP, 38400 for Deconz, however note that some EZSP firmware need 57600","examples":[38400,57600,115200],"requiresRestart":true,"title":"Baudrate","type":"number"},"cache_state":{"default":true,"description":"MQTT message payload will contain all attributes, not only changed ones. Has to be true when integrating via Home Assistant","title":"Cache state","type":"boolean"},"cache_state_persistent":{"default":true,"description":"Persist cached state, only used when cache_state: true","title":"Persist cache state","type":"boolean"},"cache_state_send_on_startup":{"default":true,"description":"Send cached state on startup, only used when cache_state: true","title":"Send cached state on startup","type":"boolean"},"channel":{"default":11,"description":"Zigbee channel, changing requires repairing all devices! (Note: use a ZLL channel: 11, 15, 20, or 25 to avoid Problems)","examples":[15,20,25],"maximum":26,"minimum":11,"requiresRestart":true,"title":"ZigBee channel","type":"number"},"elapsed":{"default":false,"description":"Add an elapsed attribute to MQTT messages, contains milliseconds since the previous msg","title":"Elapsed","type":"boolean"},"ext_pan_id":{"description":"Zigbee extended pan ID, changing requires repairing all devices!","items":{"type":"number"},"requiresRestart":true,"title":"Ext Pan ID","type":"array"},"homeassistant_discovery_topic":{"description":"Home Assistant discovery topic","examples":["homeassistant"],"requiresRestart":true,"title":"Homeassistant discovery topic","type":"string"},"homeassistant_legacy_entity_attributes":{"default":true,"description":"Home Assistant legacy entity attributes, when enabled Zigbee2MQTT will add state attributes to each entity, additional to the separate entities and devices it already creates","title":"Home Assistant legacy entity attributes","type":"boolean"},"homeassistant_legacy_triggers":{"default":true,"description":"Home Assistant legacy triggers, when enabled Zigbee2mqt will send an empty 'action' or 'click' after one has been send. A 'sensor_action' and 'sensor_click' will be discoverd","title":"Home Assistant legacy triggers","type":"boolean"},"homeassistant_status_topic":{"description":"Home Assistant status topic","examples":["homeassistant/status"],"requiresRestart":true,"title":"Home Assistant status topic","type":"string"},"ikea_ota_use_test_url":{"default":false,"description":"Use IKEA TRADFRI OTA test server, see OTA updates documentation","requiresRestart":true,"title":"IKEA TRADFRI OTA use test url","type":"boolean"},"last_seen":{"default":"disable","description":"Add a last_seen attribute to MQTT messages, contains date/time of last Zigbee message","enum":["disable","ISO_8601","ISO_8601_local","epoch"],"title":"Last seen","type":"string"},"legacy_api":{"default":true,"description":"Disables the legacy api (false = disable)","requiresRestart":true,"title":"Legacy API","type":"boolean"},"log_directory":{"description":"Location of log directory","examples":["data/log/%TIMESTAMP%"],"requiresRestart":true,"title":"Log directory","type":"string"},"log_file":{"default":"log.txt","description":"Log file name, can also contain timestamp","examples":["zigbee2mqtt_%TIMESTAMP%.log"],"requiresRestart":true,"title":"Log file","type":"string"},"log_level":{"default":"info","description":"Logging level","enum":["info","warn","error","debug"],"title":"Log level","type":"string"},"log_output":{"description":"Output location of the log, leave empty to supress logging","items":{"enum":["console","file","syslog"],"type":"string"},"requiresRestart":true,"title":"Log output","type":"array"},"log_rotation":{"default":true,"description":"Log rotation","requiresRestart":true,"title":"Log rotation","type":"boolean"},"log_symlink_current":{"default":false,"description":"Create symlink to current logs in the log directory","requiresRestart":true,"title":"Log symlink current","type":"boolean"},"log_syslog":{"properties":{"app_name":{"default":"Zigbee2MQTT","description":"The name of the application (Default: Zigbee2MQTT).","title":"Localhost","type":"string"},"eol":{"default":"/n","description":"The end of line character to be added to the end of the message (Default: Message without modifications).","title":"eol","type":"string"},"host":{"default":"localhost","description":"The host running syslogd, defaults to localhost.","title":"Host","type":"string"},"localhost":{"default":"localhost","description":"Host to indicate that log messages are coming from (Default: localhost).","title":"Localhost","type":"string"},"path":{"default":"/dev/log","description":"The path to the syslog dgram socket (i.e. /dev/log or /var/run/syslog for OS X).","examples":["/var/run/syslog"],"title":"Path","type":"string"},"pid":{"default":"process.pid","description":"PID of the process that log messages are coming from (Default process.pid).","title":"PID","type":"string"},"port":{"default":123,"description":"The port on the host that syslog is running on, defaults to syslogd's default port.","title":"Port","type":"number"},"protocol":{"default":"tcp4","description":"The network protocol to log over (e.g. tcp4, udp4, tls4, unix, unix-connect, etc).","examples":["udp4","tls4","unix","unix-connect"],"title":"Protocol","type":"string"},"type":{"default":"5424","description":"The type of the syslog protocol to use (Default: BSD, also valid: 5424).","title":"Type","type":"string"}},"title":"syslog","type":"object"},"network_key":{"description":"Network encryption key, changing requires repairing all devices!","oneOf":[{"title":"Network key(string)","type":"string"},{"items":{"type":"number"},"title":"Network key(array)","type":"array"}],"requiresRestart":true,"title":"Network key"},"pan_id":{"description":"ZigBee pan ID, changing requires repairing all devices!","oneOf":[{"title":"Pan ID (string)","type":"string"},{"title":"Pan ID (number)","type":"number"}],"requiresRestart":true,"title":"Pan ID"},"report":{"description":"Enables report feature (deprecated)","readOnly":true,"requiresRestart":true,"title":"Reporting","type":"boolean"},"rtscts":{"description":"RTS / CTS Hardware Flow Control for serial port","requiresRestart":true,"title":"RTS / CTS","type":"boolean"},"soft_reset_timeout":{"description":"Soft reset ZNP after timeout","minimum":0,"readOnly":true,"requiresRestart":true,"title":"Soft reset timeout (deprecated)","type":"number"},"timestamp_format":{"description":"Log timestamp format","examples":["YYYY-MM-DD HH:mm:ss"],"requiresRestart":true,"title":"Timestamp format","type":"string"}},"title":"Advanced","type":"object"},"availability":{"description":"Checks wether devices are online/offline","oneOf":[{"title":"Availability (boolean)","type":"boolean"},{"properties":{"active":{"description":"Options for active devices (routers/mains powered)","properties":{"timeout":{"default":10,"description":"Time after which an active device will be marked as offline in minutes","requiresRestart":true,"title":"Timeout","type":"number"}},"requiresRestart":true,"title":"Active","type":"object"},"passive":{"description":"Options for passive devices (routers/mains powered)","properties":{"timeout":{"default":1500,"description":"Time after which an passive device will be marked as offline in minutes","requiresRestart":true,"title":"Timeout","type":"number"}},"requiresRestart":true,"title":"Active","type":"object"}},"title":"Availability (object)","type":"object"}],"requiresRestart":true,"title":"Availability"},"ban":{"items":{"type":"string"},"readOnly":true,"requiresRestart":true,"title":"Ban (deprecated, use blocklist)","type":"array"},"blocklist":{"description":"Block devices from the network (by ieeeAddr)","items":{"type":"string"},"requiresRestart":true,"title":"Blocklist","type":"array"},"device_options":{"type":"object"},"devices":{"patternProperties":{"^.*$":{"$ref":"#/definitions/device"}},"propertyNames":{"pattern":"^0x[\\d\\w]{16}$"},"type":"object"},"experimental":{"properties":{"output":{"description":"Examples when 'state' of a device is published json: topic: 'zigbee2mqtt/my_bulb' payload '{\"state\": \"ON\"}' attribute: topic 'zigbee2mqtt/my_bulb/state' payload 'ON' attribute_and_json: both json and attribute (see above)","enum":["attribute_and_json","attribute","json"],"title":"MQTT output type","type":"string"},"transmit_power":{"description":"Transmit power of adapter, only available for Z-Stack (CC253*/CC2652/CC1352) adapters, CC2652 = 5dbm, CC1352 max is = 20dbm (5dbm default)","requiresRestart":true,"title":"Transmit power","type":["number","null"]}},"title":"Experimental","type":"object"},"external_converters":{"description":"You can define external converters to e.g. add support for a DiY device","examples":["DIYRuZ_FreePad.js"],"items":{"type":"string"},"requiresRestart":true,"title":"External converters","type":"array"},"frontend":{"properties":{"auth_token":{"description":"Enables authentication, disabled by default","requiresRestart":true,"title":"Auth token","type":["string","null"]},"host":{"default":" 0.0.0.0","description":"Frontend binding host","requiresRestart":true,"title":"Bind host","type":"string"},"port":{"default":8080,"description":"Frontend binding port","requiresRestart":true,"title":"Port","type":"number"}},"title":"Frontend","type":"object"},"groups":{"patternProperties":{"^.*$":{"$ref":"#/definitions/group"}},"propertyNames":{"pattern":"^[\\w].*$"},"type":"object"},"homeassistant":{"default":false,"description":"Home Assistant integration (MQTT discovery)","title":"Home Assistant integration","type":"boolean"},"map_options":{"properties":{"graphviz":{"properties":{"colors":{"properties":{"fill":{"properties":{"coordinator":{"type":"string"},"enddevice":{"type":"string"},"router":{"type":"string"}},"type":"object"},"font":{"properties":{"coordinator":{"type":"string"},"enddevice":{"type":"string"},"router":{"type":"string"}},"type":"object"},"line":{"properties":{"active":{"type":"string"},"inactive":{"type":"string"}},"type":"object"}},"type":"object"}},"type":"object"}},"title":"Networkmap","type":"object"},"mqtt":{"properties":{"base_topic":{"description":"MQTT base topic for Zigbee2MQTT MQTT messages","examples":["zigbee2mqtt"],"requiresRestart":true,"title":"Base topic","type":"string"},"ca":{"description":"Absolute path to SSL/TLS certificate of CA used to sign server and client certificates","examples":["/etc/ssl/mqtt-ca.crt"],"requiresRestart":true,"title":"Certificate authority","type":"string"},"cert":{"description":"Absolute path to SSL/TLS certificate for client-authentication","examples":["/etc/ssl/mqtt-client.crt"],"requiresRestart":true,"title":"SSL/TLS certificate","type":"string"},"client_id":{"description":"MQTT client ID","examples":["MY_CLIENT_ID"],"requiresRestart":true,"title":"Client ID","type":"string"},"force_disable_retain":{"default":false,"description":"Disable retain for all send messages. ONLY enable if you MQTT broker doesn't support retained message (e.g. AWS IoT core, Azure IoT Hub, Google Cloud IoT core, IBM Watson IoT Platform). Enabling will break the Home Assistant integration","requiresRestart":true,"title":"Force disable retain","type":"boolean"},"include_device_information":{"default":false,"description":"Include device information to mqtt messages","title":"Include device information","type":"boolean"},"keepalive":{"default":60,"description":"MQTT keepalive in second","requiresRestart":true,"title":"Keepalive","type":"number"},"key":{"description":"Absolute path to SSL/TLS key for client-authentication","examples":["/etc/ssl/mqtt-client.key"],"requiresRestart":true,"title":"SSL/TLS key","type":"string"},"password":{"description":"MQTT server authentication password","examples":["ILOVEPELMENI"],"requiresRestart":true,"title":"Password","type":"string"},"reject_unauthorized":{"default":true,"description":"Disable self-signed SSL certificate","requiresRestart":true,"title":"Reject unauthorized","type":"boolean"},"server":{"description":"MQTT server URL (use mqtts:// for SSL/TLS connection)","examples":["mqtt://localhost:1883"],"requiresRestart":true,"title":"MQTT server","type":"string"},"user":{"description":"MQTT server authentication user","examples":["johnnysilverhand"],"requiresRestart":true,"title":"User","type":"string"},"version":{"default":4,"description":"MQTT protocol version","examples":[5],"requiresRestart":true,"title":"Version","type":["number","null"]}},"required":["base_topic","server"],"title":"MQTT","type":"object"},"ota":{"properties":{"disable_automatic_update_check":{"default":false,"description":"Zigbee devices may request a firmware update, and do so frequently, causing Zigbee2MQTT to reach out to third party servers. If you disable these device initiated checks, you can still initiate a firmware update check manually.","title":"Disable automatic update check","type":"boolean"},"update_check_interval":{"default":1440,"description":"Your device may request a check for a new firmware update. This value determines how frequently third party servers may actually be contacted to look for firmware updates. The value is set in minutes, and the default is 1 day.","title":"Update check interval","type":"number"}},"title":"OTA updates","type":"object"},"passlist":{"description":"Allow only certain devices to join the network (by ieeeAddr). Note that all devices not on the passlist will be removed from the network!","items":{"type":"string"},"requiresRestart":true,"title":"Passlist","type":"array"},"permit_join":{"default":false,"description":"Allow new devices to join (re-applied at restart)","title":"Permit join","type":"boolean"},"serial":{"properties":{"adapter":{"default":"auto","description":"Adapter type, not needed unless you are experiencing problems","enum":["deconz","zstack","zigate","ezsp","auto"],"requiresRestart":true,"title":"Adapter","type":["string"]},"disable_led":{"default":false,"description":"Disable LED of the adapter if supported","requiresRestart":true,"title":"Disable led","type":"boolean"},"port":{"description":"Location of the adapter. To autodetect the port, set null","examples":["/dev/ttyACM0"],"requiresRestart":true,"title":"Port","type":["string","null"]}},"title":"Serial","type":"object"},"whitelist":{"items":{"type":"string"},"readOnly":true,"requiresRestart":true,"title":"Whitelist (deprecated, use passlist)","type":"array"}},"required":["mqtt"],"type":"object"},"coordinator":{"meta":{"maintrel":0,"majorrel":38,"minorrel":103,"product":0,"revision":"0x26670700","transportrev":0},"type":"ConBee2/RaspBee2"},"log_level":"info","network":{"channel":11,"extended_pan_id":"0xdddddddddddddddd","pan_id":6754},"permit_join":true,"restart_required":false,"version":"1.22.0"}
     2021-11-17 11:53:07   log             {"message":[{"dateCode":"0x26670700","friendly_name":"Coordinator","ieeeAddr":"0x00212effff04d542","lastSeen":1637146387077,"networkAddress":0,"softwareBuildID":"ConBee2/RaspBee2","type":"Coordinator"},{"dateCode":"","description":"Silvercrest smart plug (EU, CH, FR, BS, DK)","friendly_name":"Lidl Steckdose","hardwareVersion":1,"ieeeAddr":"0x60a423fffe0e3567","lastSeen":1637146218875,"manufacturerID":4098,"manufacturerName":"_TZ3000_kdi2o9m6","model":"HG06337","modelID":"TS011F","networkAddress":10279,"powerSource":"Mains (single phase)","type":"Router","vendor":"Lidl"}],"type":"devices"}
     2021-11-17 12:07:46   log_level       info
     2021-11-17 12:07:46   log_message     MQTT publish: topic 'zigbee2mqtt/Lidl Steckdose', payload '{"linkquality":255,"state":"OFF"}'
     2021-11-17 12:05:18   subscriptions   zigbee2mqtt/#
Attributes:
   IODev      MQTT2_FHEM_Server
   bridgeRegexp zigbee2mqtt/([A-Za-z0-9._]+)[/]?.*:.* "zigbee_$1"
   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.
   devicetopic zigbee2mqtt
   getList    devicelist:noArg log $DEVICETOPIC/bridge/config/devices/get
  networkmap_raw:noArg raw $DEVICETOPIC/bridge/networkmap raw
  networkmap_graphviz:noArg graphviz $DEVICETOPIC/bridge/networkmap graphviz
   icon       mqtt
   model      zigbee2mqtt_bridge
   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/networkmap:.* {}
  $DEVICETOPIC/bridge/networkmap/graphviz:.* graphviz
  $DEVICETOPIC/bridge/networkmap/raw:.* raw
  $DEVICETOPIC/bridge/devices:.* devices
  $DEVICETOPIC/bridge/info:.* info
   room       MQTT
   setList    log_level:debug,info,warn,error $DEVICETOPIC/bridge/config/log_level $EVTPART1
  permit_join:true,false $DEVICETOPIC/bridge/config/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
   setStateList on off

Ich möchte die Geräte aber auch per Homebridge in Homekit nutzen und haben mir dieses Plugin installiert.https://z2m.dev
Dort habe ich dann entsprechend auch die MQTT Server Daten hinterlegt.

Homebridge Plugin Konfiguration
{
            "mqtt": {
                "base_topic": "zigbee2mqtt",
                "server": "mqtt://192.168.178.55:1883",
                "client_id": "zigbee_pi",
                "reject_unauthorized": false,
                "keepalive": 60,
                "version": 4,
                "disable_qos": false
            },
            "defaults": {
                "exclude": false
            },
            "platform": "zigbee2mqtt"
        }

Lerne ich nun ein neues Gerät an kommen diese doppelt nach FHEM. Einmal über das zigbee2mqqt Frontend und über die Homebridge. Und das verstehe ich nicht da nach meinem Verständnis zigbee2mqtt Frontend als auch Homebridge Plugin mit dem gleichen MQTT Server sprechen??

Ich verstehe wohl die Thematik noch nicht richtig. Wo ist mein Denkfehler?
« Letzte Änderung: 17 November 2021, 12:23:28 von Udomatic »
2x Raspberry 3B+, 1x Raspberry 4, Signalduino 433 (Somfy), CUL_HM (HM-MOD-RPI-PCB), MQTT, Hue, ConBee 2, Sonos, AVM DECT, Netatmo, eufy, Nuki,

Offline Beta-User

  • Developer
  • Hero Member
  • ****
  • Beiträge: 16324
Antw:zigbee2mqtt mit MQTT2_SERVER und Homebridge
« Antwort #1 am: 17 November 2021, 12:25:42 »
Leider habe ich keine Ahnung, wie das mit homebridge ist, aber nach meinem Verständnis ist das ein paralleler Prozess, der nichts mit MQTT zu tun hat, der dir weitere Geräte anlegt (was sind das für TYPE? Vermutlich: dummy?)

Meine Vermutung: dieser doppelte Weg über das plugin ist nicht erforderlich, einfach die genericDeviceType setzen und nach allgemeinen Regeln die (MQTT2_DEVICE-TYPE) FHEM-Geräte von der Sprachsteuerungssoftware erkennen lassen (z.B.: siriName setzen?) und gut ist.
Server: HP-T620@Debian 10, 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:MySensors, Weekday-&RandomTimer, Twilight,  AttrTemplate {u.a. mqtt2, mysensors, zwave}

Online Udomatic

  • Full Member
  • ***
  • Beiträge: 323
Antw:zigbee2mqtt mit MQTT2_SERVER und Homebridge
« Antwort #2 am: 17 November 2021, 14:14:31 »
Leider habe ich keine Ahnung, wie das mit homebridge ist, aber nach meinem Verständnis ist das ein paralleler Prozess, der nichts mit MQTT zu tun hat, der dir weitere Geräte anlegt (was sind das für TYPE? Vermutlich: dummy?)

Meine Vermutung: dieser doppelte Weg über das plugin ist nicht erforderlich, einfach die genericDeviceType setzen und nach allgemeinen Regeln die (MQTT2_DEVICE-TYPE) FHEM-Geräte von der Sprachsteuerungssoftware erkennen lassen (z.B.: siriName setzen?) und gut ist.

Hmm, ich weiss nicht. Im Homebridge Plugin habe ich lediglich die MQTT FHEM Server Adresse hinterlegt damit das Plugin weiss, wo es seine Geräte her bekommen soll. Das klappt ja auch. Damit spare ich mir die ganze Arbeit mit Siri Name anlegen und Homebridge Mappings, bei Sensoren etc..

Nur wird derzeit halt eben das gleiche Device noch mal angelegt.
2x Raspberry 3B+, 1x Raspberry 4, Signalduino 433 (Somfy), CUL_HM (HM-MOD-RPI-PCB), MQTT, Hue, ConBee 2, Sonos, AVM DECT, Netatmo, eufy, Nuki,

Offline Beta-User

  • Developer
  • Hero Member
  • ****
  • Beiträge: 16324
Antw:zigbee2mqtt mit MQTT2_SERVER und Homebridge
« Antwort #3 am: 17 November 2021, 14:19:36 »
Dann haben die MQTT2_DEVICE's keine Daseinsberechtigung. Die kann man verhindern, indem man den ganzen zigbee2mqtt-Zweig im SERVER per ignoreRegexp einfach nicht anlegen läßt.

Man kann auch statt des obigen Weges vermutlich zumindest für diesen Teil einen separaten (Mosquitto-) Server anlegen und in FHEM dann nur mit den homebridge-dummy arbeiten. Schafft halt deutlich mehr externe Abhängigkeiten, deswegen würde ich eher den Weg über "klassische mappings" von "normalen FHEM-Devices" gehen, aber das muss jeder selbst wissen...
Server: HP-T620@Debian 10, 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:MySensors, Weekday-&RandomTimer, Twilight,  AttrTemplate {u.a. mqtt2, mysensors, zwave}

Online Udomatic

  • Full Member
  • ***
  • Beiträge: 323
Antw:zigbee2mqtt mit MQTT2_SERVER und Homebridge
« Antwort #4 am: 18 November 2021, 17:57:45 »
Dann haben die MQTT2_DEVICE's keine Daseinsberechtigung. Die kann man verhindern, indem man den ganzen zigbee2mqtt-Zweig im SERVER per ignoreRegexp einfach nicht anlegen läßt.

Man kann auch statt des obigen Weges vermutlich zumindest für diesen Teil einen separaten (Mosquitto-) Server anlegen und in FHEM dann nur mit den homebridge-dummy arbeiten. Schafft halt deutlich mehr externe Abhängigkeiten, deswegen würde ich eher den Weg über "klassische mappings" von "normalen FHEM-Devices" gehen, aber das muss jeder selbst wissen...

Ok, ich probiere es über FHEM. Jetzt habe ich folgendes Problem. Ich habe 3 Lidl Geräte angelernt. 1 x Steckdose und 2x Bewegungsmelder. Allerdings werden die Readings nur in 1 Gerät in FHEM geschrieben. Ich habe also nicht 3 Geräte sondern nur 1 Gerät und abhängig welches Gerät Meldungen sendet ändern sich die Readings in dem einen Gerät.

Wie bekomme ich 3 Geräte?
2x Raspberry 3B+, 1x Raspberry 4, Signalduino 433 (Somfy), CUL_HM (HM-MOD-RPI-PCB), MQTT, Hue, ConBee 2, Sonos, AVM DECT, Netatmo, eufy, Nuki,

Offline Beta-User

  • Developer
  • Hero Member
  • ****
  • Beiträge: 16324
Antw:zigbee2mqtt mit MQTT2_SERVER und Homebridge
« Antwort #5 am: 18 November 2021, 18:12:01 »
Sprichst du jetzt von MQTT2_DEVICE oder von dummy oder was auch immer...?

Kannst du einfach je ein list der relevanten Devices liefern, dann müßte man nicht raten >:( . Was für MQTT zu liefern ist, steht im Link, der in einem der beiden angepinnten Beiträge zu finden ist, und falls es was anderes ist: mach bitte im passenden Forum einen neuen Thread auf, bei homebridge-irgendwas bin ich raus...
Server: HP-T620@Debian 10, 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:MySensors, Weekday-&RandomTimer, Twilight,  AttrTemplate {u.a. mqtt2, mysensors, zwave}

Online Udomatic

  • Full Member
  • ***
  • Beiträge: 323
Antw:zigbee2mqtt mit MQTT2_SERVER und Homebridge
« Antwort #6 am: 18 November 2021, 18:41:20 »
Sprichst du jetzt von MQTT2_DEVICE oder von dummy oder was auch immer...?

Kannst du einfach je ein list der relevanten Devices liefern, dann müßte man nicht raten >:( . Was für MQTT zu liefern ist, steht im Link, der in einem der beiden angepinnten Beiträge zu finden ist, und falls es was anderes ist: mach bitte im passenden Forum einen neuen Thread auf, bei homebridge-irgendwas bin ich raus...

Ich spreche jetzt nur noch von FHEM. Ich nutze den MQTT2_Server und FHEM Zigbee2mqtt

List zigbee_pi

Internals:
   CFGFN     
   CID        zigbee_pi
   DEF        zigbee_pi
   DEVICETOPIC zigbee2mqtt
   FUUID      61968cce-f33f-8bc1-12ca-ead655e3f1b12168
   IODev      z2m
   LASTInputDev z2m
   MSGCNT     5
   NAME       MQTT2_zigbee_pi
   NR         60627
   STATE      ???
   TYPE       MQTT2_DEVICE
   z2m_MSGCNT 5
   z2m_TIME   2021-11-18 18:28:45
   OLDREADINGS:
   READINGS:
     2021-11-18 18:28:00   attrTemplateVersion 20211022
     2021-11-18 18:28:45   log_level       info
     2021-11-18 18:28:45   log_message     MQTT publish: topic 'zigbee2mqtt/Lidl BWM WC', payload '{"battery":100,"battery_low":false,"device":{"applicationVersion":65,"dateCode":"2019.12.12","friendlyName":"Lidl BWM WC","hardwareVersion":1,"ieeeAddr":"0xec1bbdfffea259d9","manufacturerID":4619,"manufacturerName":"_TZ1800_fcdjzz3s","model":"HG06335","networkAddress":50435,"powerSource":"Battery","stackVersion":2,"type":"EndDevice","zclVersion":1},"linkquality":255,"occupancy":false,"tamper":false,"voltage":3000}'
     2021-11-18 18:28:22   subscriptions   zigbee2mqtt/#
Attributes:
   bridgeRegexp zigbee2mqtt/([A-Za-z0-9._]+)[/]?.*:.* "zigbee_$1"
   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.
   devicetopic zigbee2mqtt
   getList    devicelist:noArg log $DEVICETOPIC/bridge/config/devices/get
  networkmap_raw:noArg raw $DEVICETOPIC/bridge/networkmap raw
  networkmap_graphviz:noArg graphviz $DEVICETOPIC/bridge/networkmap graphviz
   icon       mqtt
   model      zigbee2mqtt_bridge
   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/networkmap:.* {}
  $DEVICETOPIC/bridge/networkmap/graphviz:.* graphviz
  $DEVICETOPIC/bridge/networkmap/raw:.* raw
  $DEVICETOPIC/bridge/devices:.* devices
  $DEVICETOPIC/bridge/info:.* info
   room       MQTT2_DEVICE
   setList    log_level:debug,info,warn,error $DEVICETOPIC/bridge/config/log_level $EVTPART1
  permit_join:true,false $DEVICETOPIC/bridge/config/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
   setStateList on off

list Lidl Steckdose

Internals:
   CFGFN     
   CID        zigbee_Lidl
   DEF        zigbee_Lidl
   DEVICETOPIC Lidl_Bewegunssensor
   FUUID      61968d36-f33f-8bc1-3455-fe13027b061d81de
   IODev      z2m
   LASTInputDev z2m
   MSGCNT     13
   NAME       Lidl_Bewegunssensor
   NR         60650
   STATE      OFF
   TYPE       MQTT2_DEVICE
   z2m_MSGCNT 13
   z2m_TIME   2021-11-18 18:36:54
   READINGS:
     2021-11-18 18:28:22   IODev           z2m
     2021-11-18 18:30:43   associatedWith  MQTT2_zigbee_pi
     2021-11-18 18:36:32   battery         100
     2021-11-18 18:36:32   battery_low     false
     2021-11-18 18:36:54   device_applicationVersion 66
     2021-11-18 18:36:54   device_dateCode
     2021-11-18 18:36:54   device_friendlyName Lidl Steckdose
     2021-11-18 18:36:54   device_hardwareVersion 1
     2021-11-18 18:36:54   device_ieeeAddr 0x60a423fffe0e3567
     2021-11-18 18:36:54   device_manufacturerID 4098
     2021-11-18 18:36:54   device_manufacturerName _TZ3000_kdi2o9m6
     2021-11-18 18:36:54   device_model    HG06337
     2021-11-18 18:36:54   device_networkAddress 59751
     2021-11-18 18:36:54   device_powerSource Mains (single phase)
     2021-11-18 18:36:54   device_stackVersion 0
     2021-11-18 18:36:54   device_type     Router
     2021-11-18 18:36:54   device_zclVersion 3
     2021-11-18 18:36:54   linkquality     255
     2021-11-18 18:36:32   occupancy       false
     2021-11-18 18:36:54   state           OFF
     2021-11-18 18:36:32   tamper          false
     2021-11-18 18:36:32   voltage         3000
Attributes:
   readingList zigbee2mqtt/Lidl\x20Steckdose:.* { json2nameValue($EVENT) }
zigbee2mqtt/Lidl\x20BWM\x20WC:.* { json2nameValue($EVENT) }
zigbee2mqtt/Lidl\x20Bewegunssensor:.* { json2nameValue($EVENT) }
   room       MQTT2_DEVICE

list Lidl Bewegungsmelder
Internals:
   CFGFN     
   CID        zigbee_Lidl
   DEF        zigbee_Lidl
   DEVICETOPIC Lidl_Bewegunssensor
   FUUID      61968d36-f33f-8bc1-3455-fe13027b061d81de
   IODev      z2m
   LASTInputDev z2m
   MSGCNT     10
   NAME       Lidl_Bewegunssensor
   NR         60650
   STATE      ON
   TYPE       MQTT2_DEVICE
   z2m_MSGCNT 10
   z2m_TIME   2021-11-18 18:35:26
   READINGS:
     2021-11-18 18:28:22   IODev           z2m
     2021-11-18 18:30:43   associatedWith  MQTT2_zigbee_pi
     2021-11-18 18:35:26   battery         100
     2021-11-18 18:35:26   battery_low     false
     2021-11-18 18:35:26   device_applicationVersion 65
     2021-11-18 18:35:26   device_dateCode 2019.12.12
     2021-11-18 18:35:26   device_friendlyName Lidl Bewegunssensor
     2021-11-18 18:35:26   device_hardwareVersion 1
     2021-11-18 18:35:26   device_ieeeAddr 0xec1bbdfffee648f5
     2021-11-18 18:35:26   device_manufacturerID 4619
     2021-11-18 18:35:26   device_manufacturerName _TZ1800_fcdjzz3s
     2021-11-18 18:35:26   device_model    HG06335
     2021-11-18 18:35:26   device_networkAddress 1711
     2021-11-18 18:35:26   device_powerSource Battery
     2021-11-18 18:35:26   device_stackVersion 2
     2021-11-18 18:35:26   device_type     EndDevice
     2021-11-18 18:35:26   device_zclVersion 1
     2021-11-18 18:35:26   linkquality     255
     2021-11-18 18:35:26   occupancy       true
     2021-11-18 18:34:48   state           ON
     2021-11-18 18:35:26   tamper          false
     2021-11-18 18:35:26   voltage         3000
Attributes:
   readingList zigbee2mqtt/Lidl\x20Steckdose:.* { json2nameValue($EVENT) }
zigbee2mqtt/Lidl\x20BWM\x20WC:.* { json2nameValue($EVENT) }
zigbee2mqtt/Lidl\x20Bewegunssensor:.* { json2nameValue($EVENT) }
   room       MQTT2_DEVICE

Statt das FHEM zwei einzelne Geräte angelegt hat werden einfach nur die Readings geändert im Gerät Lidl Bewegungssensor.

Was mache ich falsch oder habe ich vergessen?
2x Raspberry 3B+, 1x Raspberry 4, Signalduino 433 (Somfy), CUL_HM (HM-MOD-RPI-PCB), MQTT, Hue, ConBee 2, Sonos, AVM DECT, Netatmo, eufy, Nuki,

Offline Beta-User

  • Developer
  • Hero Member
  • ****
  • Beiträge: 16324
Antw:zigbee2mqtt mit MQTT2_SERVER und Homebridge
« Antwort #7 am: 18 November 2021, 18:51:49 »
Mobile Kurzfassung: zu kreative friendly names....
Server: HP-T620@Debian 10, 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:MySensors, Weekday-&RandomTimer, Twilight,  AttrTemplate {u.a. mqtt2, mysensors, zwave}

Online Udomatic

  • Full Member
  • ***
  • Beiträge: 323
Antw:zigbee2mqtt mit MQTT2_SERVER und Homebridge
« Antwort #8 am: 18 November 2021, 19:09:32 »
Mobile Kurzfassung: zu kreative friendly names....

 ::) Ok, Namen in weniger kreative geändert, works!
Danke schöne schon mal!

Wenn ich das Template (zigbee2mqtt_plug) für die Steckdose nehme lässt sich dieser nicht schalten aus FHEM heraus.

Noch ein Tipp bei den Templates, um das zu lösen?
« Letzte Änderung: 18 November 2021, 19:11:36 von Udomatic »
2x Raspberry 3B+, 1x Raspberry 4, Signalduino 433 (Somfy), CUL_HM (HM-MOD-RPI-PCB), MQTT, Hue, ConBee 2, Sonos, AVM DECT, Netatmo, eufy, Nuki,

Offline Beta-User

  • Developer
  • Hero Member
  • ****
  • Beiträge: 16324
Antw:zigbee2mqtt mit MQTT2_SERVER und Homebridge
« Antwort #9 am: 18 November 2021, 19:36:47 »
Kann sein, dass sich bei topic/payload was geändert hat. Hatte jüngst bei anderen devices ein paar Änderungen eingecheckt. Müsste man testen/ probieren...
Server: HP-T620@Debian 10, 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:MySensors, Weekday-&RandomTimer, Twilight,  AttrTemplate {u.a. mqtt2, mysensors, zwave}

Offline Beta-User

  • Developer
  • Hero Member
  • ****
  • Beiträge: 16324
Antw:zigbee2mqtt mit MQTT2_SERVER und Homebridge
« Antwort #10 am: 19 November 2021, 10:11:57 »
Noch ein Tipp bei den Templates, um das zu lösen?
Habe jetzt mal zum einen "zigbee2mqtt_plug" mal angesehen und mit dem verglichen, was in https://www.zigbee2mqtt.io/devices/HG06337.html zu finden ist. Fazit: "Eigentlich" sollte das passen.

Ergo: ein RAW-Listing mit dem aktuellen Stand wäre hilfreich, meine Glaskugel ist nicht in der Lage zu erkennen, was ggf. an Konfigurationsresten aus vergangenen Tagen da reinspielt und ob ggf. "new news" zu berücksichtigen sind gg. dem, was blakadder behauptet...
Server: HP-T620@Debian 10, 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:MySensors, Weekday-&RandomTimer, Twilight,  AttrTemplate {u.a. mqtt2, mysensors, zwave}

Online Udomatic

  • Full Member
  • ***
  • Beiträge: 323
Antw:zigbee2mqtt mit MQTT2_SERVER und Homebridge
« Antwort #11 am: Gestern um 20:24:55 »
Sorry für die späte Rückmeldung!

Ja es passt alles und er Plug funktioniert!
2x Raspberry 3B+, 1x Raspberry 4, Signalduino 433 (Somfy), CUL_HM (HM-MOD-RPI-PCB), MQTT, Hue, ConBee 2, Sonos, AVM DECT, Netatmo, eufy, Nuki,