cc2531 MQTT2 Ikea Lampen Docker

[ch.eick]

Hallo zusammen,
auch wenn Ihr mich jetzt steinigt, weil ich es immer noch nicht gebacken bekomme. Meine alten Threads dazu habe ich auch schon versucht nochmal aufzuarbeiten, aber es hat immer nur in kleinen Teilen funktioniert.

Folgendes ist jetzt mein aktuelles Umfeld, nach dem ich vieles hin und her umgezogen haben.

FHEM auf einem RPI4 in Docker, das Device "/dev/ttyACM0:/dev/ttyACM0" ist auskommentiert, da hier der cc2531 angeschlossen ist.

Hier der zigbee2mqtt Container mit dem "/dev/ttyACM0:/dev/ttyACM0" Device, den ich ganz frisch aufgesetzt habe.

Code Auswählen Erweitern


zigbee2mqtt:
    image: koenkk/zigbee2mqtt:latest
    volumes:
      - ./zigbee2mqtt/data:/app/data
      - /run/udev:/run/udev:ro
    devices:
      - /dev/ttyACM0:/dev/ttyACM0
    restart: always
    ports:
        - '8084:8080'
    privileged: true
    environment:
      - TZ=Europe/Berlin
    depends_on:
      - "fhem"

Hier das MQTT2 Device, das auch ein Filelog hat, in das bereits Meldungen rein laufen

Code Auswählen Erweitern


defmod MQTT2_zigbee_bridge MQTT2_DEVICE zigbee_bridge
attr MQTT2_zigbee_bridge DbLogExclude .*
attr MQTT2_zigbee_bridge IODev MQTT2_FHEM_Server
attr MQTT2_zigbee_bridge disable 0
attr MQTT2_zigbee_bridge readingList zigbee2mqtt/bridge/logging:.* { json2nameValue($EVENT) }\
zigbee2mqtt/bridge/info:.* info\
zigbee2mqtt/bridge/devices:.* devices\
zigbee2mqtt/bridge/groups:.* { json2nameValue($EVENT) }\
zigbee2mqtt/bridge/extensions:.* extensions\
zigbee2mqtt/bridge/event:.* { json2nameValue($EVENT) }
attr MQTT2_zigbee_bridge room MQTT2

Vom zigbee2mqtt Container kommen bereits folgende Meldungen

Code Auswählen Erweitern


2022-01-14_17:42:23 MQTT2_zigbee_bridge info: {"commit":"414c51f","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":"/app/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":{},"experimental":{"output":"json"},"external_converters":[],"frontend":{"host":"0.0.0.0","port":8080},"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.40: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 whether 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 (mostly battery 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":"Passive","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":{"ieee_address":"0x00124b0018e1e960","meta":{"maintrel":3,"majorrel":2,"minorrel":6,"product":0,"revision":20190608,"transportrev":2},"type":"zStack12"},"log_level":"info","network":{"channel":11,"extended_pan_id":"0xdddddddddddddddd","pan_id":6754},"permit_join":true,"restart_required":false,"version":"1.22.2"}
2022-01-14_17:42:23 MQTT2_zigbee_bridge devices: [{"definition":null,"endpoints":{"1":{"bindings":[],"clusters":{"input":[],"output":[]},"configured_reportings":[],"scenes":[]},"10":{"bindings":[],"clusters":{"input":[],"output":[]},"configured_reportings":[],"scenes":[]},"11":{"bindings":[],"clusters":{"input":["ssIasAce"],"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":"0x00124b0018e1e960","interview_completed":true,"interviewing":false,"network_address":0,"supported":false,"type":"Coordinator"}]
2022-01-14_17:42:23 MQTT2_zigbee_bridge extensions: []
2022-01-14_17:42:23 MQTT2_zigbee_bridge message: Started frontend on port 0.0.0.0:8080
2022-01-14_17:42:23 MQTT2_zigbee_bridge level: info
2022-01-14_17:42:23 MQTT2_zigbee_bridge message: MQTT publish: topic 'zigbee2mqtt/bridge/config', payload '{"commit":"414c51f","coordinator":{"meta":{"maintrel":3,"majorrel":2,"minorrel":6,"product":0,"revision":20190608,"transportrev":2},"type":"zStack12"},"log_level":"info","network":{"channel":11,"extendedPanID":"0xdddddddddddddddd","panID":6754},"permit_join":true,"version":"1.22.2"}'
2022-01-14_17:42:23 MQTT2_zigbee_bridge level: info


Am cc2531 läuchtet dauerhaft die grüne LED.
Nun habe ich eine IKEA Lampe bereits versucht zurück zu setzen, um sie neu anzulernen.
Dann habe ich die S2 Taste neben der LED am cc2531 mehr als 5 Sekunden gedrückt, aber die LED beginnt nicht zu blinken!
Dann wurde die Lampe eingeschaltet, aber es passiert nichts weiter.

Der Stick wurde bereits vor über einem Jahr mal verwendet und hat da auch alle Lampen und auch 2 Floatpannel mit Fernbedienung verbunden gehabt. Das war allerdings noch native auf einem RP3 .
Die alten Devices habe ich vorher natürlich alle umbenannt, möchte sie aber zuerst mal noch zum abgucken behalten.

Ich hätte auch noch einen zweiten cc2531, weiß jedoch nicht welcher eventuell noch eine alte Konfiguration hält. Ich meine gehört zu haben, dass da was drauf gespeichert wird.

Wer könnte mir jetzt bitte mal beim Anlernen der ersten Lampe helfen.
Das liegt jetzt wegen der PV-Anlage schon sooo lange herum und ich möchte jetzt auch mal Lichtszenarien laufen lassen

VG
  Christian

[Otto123]

Hallo Christian,

als erstes brauchst Du eine Bridge -> https://wiki.fhem.de/wiki/Zigbee2mqtt

Aber! Es läuft derzeit nicht unbedingt wirklich einfach mit zigbee2mqtt. Ich schlage vor Du verschiebst den Thread nach mqtt. Dort gibt es auch schon ein paar aktuelle Themen zu zigbee2mqtt.
Das Thema ist bezüglich der Templates alles sehr am Anfang, aber es sind natürlich immer Mitwirkende gesucht

Gruß Otto

[TomLee]

Aber! Es läuft derzeit nicht

Was läuft den derzeit nicht rund ? Hab ich nix von mitgekriegt !?



Ich hatte auch mal so einen cc2531-Stick und musste zum pairen nie irgendeinen Button am Stick selbst drücken (wüsste gar nicht das einen gibt), da komm och nicht ganz mit.

[Otto123]

Ich habe nicht gesagt es läuft nicht, ich habe nur gesagt es ist eventuell nicht ganz einfach für den Beginner
ich beziehe mich auf den Thread https://forum.fhem.de/index.php/topic,91394.msg1198499.html#msg1198499
Wo ich irgendwann nicht mehr mitgekommen bin.
Wenn das ein falscher Eindruck war nehme ich alles zurück

[TomLee]

Abgesehen von Odfhem seinem Vorschlag das anders anzugehen (das wäre bspw. bei der Sonos.-/MiLight-Bridge genau der gleiche Sachverhalt und halt ich mich erstmal raus (weil schon verstanden, aber nicht begriffen)), bin ich der Meinung das im Template einfach nur der von mir erwähnte event-Topic erweitert gehört, was isy "beim einrichten" da am Ende gemacht hat sieht man  ja nicht wegen fehlender Lists, ich hab bisher nur die Erklärung dass das zweite Bridge-Device dann halt nur diesen event-Topic in der rL list beinhalten sollte, alles andere sollte von der rL im Bridge-Template " nach deinem letzten Fix und meinem Verständnis erfasst werden.

[ch.eick]

als erstes brauchst Du eine Bridge -> https://wiki.fhem.de/wiki/Zigbee2mqtt

Aber! Es läuft derzeit nicht unbedingt wirklich einfach mit zigbee2mqtt. Ich schlage vor Du verschiebst den Thread nach mqtt. Dort gibt es auch schon ein paar aktuelle Themen zu zigbee2mqtt.
Das Thema ist bezüglich der Templates alles sehr am Anfang, aber es sind natürlich immer Mitwirkende gesucht

Hallo Otto,
die zigbee2mqtt Bridge ist doch in dem Docker Container und hat den Stick ja bereits erkannt.
Die MQTT2 Devinition bekommt im FHEM ebenfalls aus dem Container Meldungen.
Das ist im ersten Post in den Logs bereits zu sehen.
Im FHEM Wiki steht quasi das drin, was ich bereits erledigt habe, aber auch das arbeite ich morgen dann nochmal durch.
Es geht erstmal um das Pairen der Lampe mit dem Stick, was anscheinend so nicht funktioniert.

[Otto123]

Irgendwie löse ich hier komplettes Missverständnis aus. Ich meinte nicht, dass die Hardware nicht läuft... 

Das erste MQTT2_DEVICE was entsteht musst Du zu einem Bridgedevice machen, dies ist dafür da, die anderen Zigbbee Geräte quasi zu erzeugen.
Du hast zwar ein Device so benannt, ich sehe aber nicht, dass Du das Template angewendet hast. So landen jetzt alle Nachrichten in dem einen Device.

[ch.eick]

Irgendwie löse ich hier komplettes Missverständnis aus. Ich meinte nicht, dass die Hardware nicht läuft... 

Das erste MQTT2_DEVICE was entsteht musst Du zu einem Bridgedevice machen, dies ist dafür da, die anderen Zigbbee Geräte quasi zu erzeugen.
Du hast zwar ein Device so benannt, ich sehe aber nicht, dass Du das Template angewendet hast. So landen jetzt alle Nachrichten in dem einen Device.

Okay, da weiß ich zwar noch nicht, was ich da machen muss, aber das ist sicher Schritt 2.

Momentan kann ich nicht mal die erste Lampe Pairen
Ich meine mich zu erinnern, dass der cc2531 nach 5 sec drücken von S2 mit der led geblinkt hätte. Das kommt schon mal nicht.
Auch habe ich im Netz mal nach IKEA E14 LED Lampe gesucht und einen Reset mit 6x Ein/Aus durchgeführt, aber ich erkenne nicht ob die Lampe jetzt zurück gesetzt wurde.

Da die Konfiguration in FHEM übernommen wurde und es damals automatisch die Lampen eingerichtet hatte gehe ich mal davon aus, dass es jetzt auch noch gehen würde.

Eventuell hat der cc2531 ja auch noch teile von der alten Konfig auf dem Stick gespeichert???

EDIT: Hier noch ein Ausschnitt aus der früheren Installation. Da hatten die Lampen bereits funktioniert.
Da ich jetzt neu den Docker Container installiert habe und diesen auch ganz neu eingerichtet habe, habe ich vorher alle alten Devices umbenannt, damit sie neu angelegt werden können, Zusätzlich stehen sie natürlich auch auf disable 1.

[TomLee]

Und vor dem anwenden des Template noch ein update von FHEM machen, das gabs gestern Abend noch ne kleine Änderung.



Das Pairen ist doch bei so gut wie alllen IKEA-Lampen gleich, zumindest macht es den Eindruck, als ich hier kurz über die Anleitungen geflogen bin.

Code Auswählen Erweitern

Pairing
Factory reset the light bulb (video). After resetting the bulb will automatically connect.

While pairing, keep the bulb close to the coordinator (adapter).

What works is to use (very) short "on's" and a little bit longer "off's", where you kill the light as soon as the bulb shows signs of turning on. Start with bulb on, then off, and then 6 "on's", wait in the 6th ON state. (If you try play safe and go for 7 "on's" the reset sometimes fails

[ch.eick]

Und vor dem anwenden des Template noch ein update von FHEM machen, das gabs gestern Abend noch ne kleine Änderung.



Das Pairen ist doch bei so gut wie alllen IKEA-Lampen gleich, zumindest macht es den Eindruck, als ich hier kurz über die Anleitungen geflogen bin.

Code Auswählen Erweitern

Pairing
Factory reset the light bulb (video). After resetting the bulb will automatically connect.

While pairing, keep the bulb close to the coordinator (adapter).

What works is to use (very) short "on's" and a little bit longer "off's", where you kill the light as soon as the bulb shows signs of turning on. Start with bulb on, then off, and then 6 "on's", wait in the 6th ON state. (If you try play safe and go for 7 "on's" the reset sometimes fails

Okay, so hatte ich es mit der Lampe auch mehrfach gemacht, aber wie gesagt, das Blinken der cc2531 LED kommt irgendwie nicht.

[Otto123]

Okay, da weiß ich zwar noch nicht, was ich da machen muss, aber das ist sicher Schritt 2.

Schritt 2 im Wiki, kein großes Ding. Kein neues Device anlegen einfach das Template auf Deines anwenden:

Code Auswählen Erweitern

set MQTT2_zigbee_bridge attrTemplate zigbee2mqtt_bridge

[ch.eick]

Der erste Fortschritt,
beim Lampen Reset ist das Timing besonders wichtig!
Jetzt hat es funktioniert und die Lampe signalisiert es mit einem 100% leuchten. Vorher war sie in einem alten Zustand von gedimmter Leuchtkraft.

[ch.eick]

Schritt 2 im Wiki, kein großes Ding. Kein neues Device anlegen einfach das Template auf Deines anwenden:

Code Auswählen Erweitern

set MQTT2_zigbee_bridge attrTemplate zigbee2mqtt_bridge

Das hat auch funktioniert. Das mache ich fast jede Woche, oder bevor ich auf Fehler Suche gehe

Code Auswählen Erweitern


update all
shutdown restart

Beim MQTT und den Templates gab es wieder updates.

Das Template ist jetzt ebenfalls zugeordnet

Code Auswählen Erweitern


Internals:
   CID        zigbee_bridge
   DEF        zigbee_bridge
   DEVICETOPIC zigbee2mqtt
   FUUID      61e19dcd-f33f-61a8-3132-ddad58e09b35f0a5
   FVERSION   10_MQTT2_DEVICE.pm:0.254240/2022-01-05
   IODev      MQTT2_FHEM_Server
   LASTInputDev MQTT2_FHEM_Server
   MQTT2_FHEM_Server_CONN MQTT2_FHEM_Server_172.18.0.5_34798
   MQTT2_FHEM_Server_MSGCNT 2
   MQTT2_FHEM_Server_TIME 2022-01-15 11:16:17
   MSGCNT     2
   NAME       MQTT2_zigbee_bridge
   NR         543
   STATE      ???
   TYPE       MQTT2_DEVICE
   OLDREADINGS:
   READINGS:
     2022-01-15 11:16:44   attrTemplateVersion 2022014
Attributes:
   DbLogExclude .*
   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
   disable    0
   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
  $DEVICETOPIC/bridge/groups:.* groups
  $DEVICETOPIC/bridge/event:.* { json2nameValue($EVENT) }
  $DEVICETOPIC/bridge/extensions:.* extensions
   room       MQTT2
   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


[ch.eick]

Jetzt wäre dann das Pairen des cc2531 dran. Irgend eine Idee, was ich da schon wieder falsch gemacht habe?

[TomLee]

Ich weiß das es eine grüne LED bei dem Stick gab, das die aber geblinkt hat wenn man ein Device angelernt hat kann ich mich nicht erinnern, kann aber sein will ich nicht behaupten das es nicht so ist.

Ich kenn mich mit Docker nicht aus, als ich den z2m-Dienst mit systemd gestartet hatte, bin ich zur Kontrolle immer mit

Code Auswählen Erweitern

sudo journalctl -u zigbee2mqtt.service -f dem Pairingvorgang gefolgt, mit pm2 geht das mit pm2 monit.
Das war bisher immer nützlich, auch um zu sehen ob was schief lief beim pairen.

[TomLee]

Jetzt wäre dann das Pairen des cc2531 dran. Irgend eine Idee, was ich da schon wieder falsch gemacht habe?

Was genau meinst du damit ? Du meinst das pairen der LED mit dem Stick ? Wie genau hast du es denn jetzt versucht ?

[ch.eick]

Was genau meinst du damit ? Du meinst das pairen der LED mit dem Stick ? Wie genau hast du es denn jetzt versucht ?

Um ein Gerät mit dem cc2531 zu Pairen  soll man die Taste S2 (neben der LED) am Stick für 5 Sekunden gedrückt halten.
Dann die Lampe in der nähe des Sticks einschalten, damit sie sich verbindet.

Dabei sollte die LED des cc2531 blinken, was ich so auch in Erinnerung hatte, aber gestern so nicht gewesen ist. Da blnkt noch nichts.

[ch.eick]

Ich habe jetzt im Log bereits Meldungen, auch von heute Nacht

Code Auswählen Erweitern


2022-01-15_04:02:45 MQTT2_zigbee_bridge message: MQTT publish: topic 'zigbee2mqtt/bridge/event', payload '{"data":{"friendly_name":"0x90fd9ffffe9e4880","ieee_address":"0x90fd9ffffe9e4880","status":"failed"},"type":"device_interview"}'
2022-01-15_04:02:45 MQTT2_zigbee_bridge level: info
2022-01-15_04:02:45 MQTT2_zigbee_bridge data_ieee_address: 0x90fd9ffffe9e4880
2022-01-15_04:02:45 MQTT2_zigbee_bridge data_friendly_name: 0x90fd9ffffe9e4880
2022-01-15_04:02:45 MQTT2_zigbee_bridge data_status: failed
2022-01-15_04:02:45 MQTT2_zigbee_bridge type: device_interview
2022-01-15_04:02:45 MQTT2_zigbee_bridge level: info
2022-01-15_04:02:45 MQTT2_zigbee_bridge message: MQTT publish: topic 'zigbee2mqtt/bridge/log', payload '{"message":"interview_failed","meta":{"friendly_name":"0x90fd9ffffe9e4880"},"type":"pairing"}'
2022-01-15_09:10:39 MQTT2_zigbee_bridge message: Received message from unsupported device with Zigbee model 'undefined' and manufacturer name 'undefined'
2022-01-15_09:10:39 MQTT2_zigbee_bridge level: warning
2022-01-15_09:10:39 MQTT2_zigbee_bridge message: Please see: https://www.zigbee2mqtt.io/advanced/support-new-devices/01_support_new_devices.html
2022-01-15_09:10:39 MQTT2_zigbee_bridge level: warning
2022-01-15_09:20:12 MQTT2_zigbee_bridge message: Received message from unsupported device with Zigbee model 'undefined' and manufacturer name 'undefined'
2022-01-15_09:20:12 MQTT2_zigbee_bridge level: warning
2022-01-15_09:20:13 MQTT2_zigbee_bridge message: Please see: https://www.zigbee2mqtt.io/advanced/support-new-devices/01_support_new_devices.html
2022-01-15_09:20:13 MQTT2_zigbee_bridge level: warning
2022-01-15_11:13:51 MQTT2_zigbee_bridge attrTemplate do_general_mqtt_cleanup
2022-01-15_11:13:51 MQTT2_zigbee_bridge attrTemplateVersion: 20211022
2022-01-15_11:16:17 MQTT2_zigbee_bridge level: info
2022-01-15_11:16:17 MQTT2_zigbee_bridge message: Connected to MQTT server
2022-01-15_11:16:17 MQTT2_zigbee_bridge level: info
2022-01-15_11:16:17 MQTT2_zigbee_bridge message: MQTT publish: topic 'zigbee2mqtt/bridge/state', payload 'online'
2022-01-15_11:16:44 MQTT2_zigbee_bridge attrTemplate do_general_mqtt_cleanup
2022-01-15_11:16:44 MQTT2_zigbee_bridge attrTemplateVersion: 2022014


Aber das versuchte Pairen von gerade ist noch nicht dabei.

[Otto123]

Aus dem Wiki

Ist dieses angelegt, kann zigbee2mqtt mit

Code Auswählen Erweitern

set MQTT2_zigbee_bridge permit_join true
in den Anlernmodus versetzt werden, anzulernende Geräte müssen anschließend jeweils nach Bedienungsanleitung in den Anlernmodus gebracht werden.

[ch.eick]

Aus dem Wiki
Ist dieses angelegt, kann zigbee2mqtt mit

Code Auswählen Erweitern

set MQTT2_zigbee_bridge permit_join true
in den Anlernmodus versetzt werden, anzulernende Geräte müssen anschließend jeweils nach Bedienungsanleitung in den Anlernmodus gebracht werden.

Das permit_join true habe ich bereits in der zigbee2mqtt Konfiguration gesetzt, da ich ja noch einige Geräte anlernen möchte. Später kommt es dann natürlich wieder raus.

[TomLee]

Keine Ahnung wo das steht, hab ich noch nie gelesen.

Versuchs mal so wie ich in #8 verlinkt habe.

Resetet ist ja jetzt hast du geschrieben, jetzt im AUS-Zustand sehr kurz ein und gleich wieder ausschalten, kurz warten und wieder sehr kurz an und wieder aus. Das ganze fünf mal wiederholen, beim 6. mal nur noch einschalten.

So versteh ich es, wenns nicht beim ersten mal klappt, dann halt wiederholen und wie gesagt im "Log" schauen was genau passiert.

[ch.eick]

Keine Ahnung wo das steht, hab ich noch nie gelesen.

Versuchs mal so wie ich in #8 verlinkt habe.

Resetet ist ja jetzt hast du geschrieben, jetzt im AUS-Zustand sehr kurz ein und gleich wieder ausschalten, kurz warten und wieder sehr kurz an und wieder aus. Das ganze fünf mal wiederholen, beim 6. mal nur noch einschalten.

So versteh ich es, wenns nicht beim ersten mal klappt, dann halt wiederholen und wie gesagt im "Log" schauen was genau passiert.

Für den Reset der  Lampe klappt das jetzt. Es wird dann mit einem kurzen Blinken der Lampe quittiert.

set MQTT2_zigbee_bridge permit_join true

Das habe ich jetzt auch gemacht, was auch im Log zu sehen ist

Code Auswählen Erweitern


2022-01-15_11:44:51 MQTT2_zigbee_bridge permit_join: set true
2022-01-15_11:44:52 MQTT2_zigbee_bridge log_message: Zigbee: allowing new devices to join.
2022-01-15_11:44:52 MQTT2_zigbee_bridge log_level: info
2022-01-15_11:44:52 MQTT2_zigbee_bridge info: {"commit":"414c51f","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":"/app/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":{"0x90fd9ffffe9e4880":{"friendly_name":"0x90fd9ffffe9e4880"}},"experimental":{"output":"json"},"external_converters":[],"frontend":{"host":"0.0.0.0","port":8080},"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.40: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 whether 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 (mostly battery 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":"Passive","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":{"ieee_address":"0x00124b0018e1e960","meta":{"maintrel":3,"majorrel":2,"minorrel":6,"product":0,"revision":20190608,"transportrev":2},"type":"zStack12"},"log_level":"info","network":{"channel":11,"extended_pan_id":"0xdddddddddddddddd","pan_id":6754},"permit_join":true,"restart_required":false,"version":"1.22.2"}
2022-01-15_11:44:52 MQTT2_zigbee_bridge log_message: MQTT publish: topic 'zigbee2mqtt/bridge/config', payload '{"commit":"414c51f","coordinator":{"meta":{"maintrel":3,"majorrel":2,"minorrel":6,"product":0,"revision":20190608,"transportrev":2},"type":"zStack12"},"log_level":"info","network":{"channel":11,"extendedPanID":"0xdddddddddddddddd","panID":6754},"permit_join":true,"version":"1.22.2"}'
2022-01-15_11:44:52 MQTT2_zigbee_bridge log_level: info
2022-01-15_11:44:52 MQTT2_zigbee_bridge coordinator_meta_minorrel: 6
2022-01-15_11:44:52 MQTT2_zigbee_bridge log_level: info
2022-01-15_11:44:52 MQTT2_zigbee_bridge version: 1.22.2
2022-01-15_11:44:52 MQTT2_zigbee_bridge coordinator_meta_product: 0
2022-01-15_11:44:52 MQTT2_zigbee_bridge coordinator_meta_maintrel: 3
2022-01-15_11:44:52 MQTT2_zigbee_bridge network_panID: 6754
2022-01-15_11:44:52 MQTT2_zigbee_bridge permit_join: true
2022-01-15_11:44:52 MQTT2_zigbee_bridge coordinator_type: zStack12
2022-01-15_11:44:52 MQTT2_zigbee_bridge coordinator_meta_transportrev: 2
2022-01-15_11:44:52 MQTT2_zigbee_bridge coordinator_meta_revision: 20190608
2022-01-15_11:44:52 MQTT2_zigbee_bridge commit: 414c51f
2022-01-15_11:44:52 MQTT2_zigbee_bridge network_extendedPanID: 0xdddddddddddddddd
2022-01-15_11:44:52 MQTT2_zigbee_bridge coordinator_meta_majorrel: 2
2022-01-15_11:44:52 MQTT2_zigbee_bridge network_channel: 11


[TomLee]

Wenn du im "Log" diese Meldung hast beim pairen der Lampe

Received message from unsupported device with Zigbee model 'undefined' and manufacturer name 'undefined'

Dann gehts hier weiter
Please see: https://www.zigbee2mqtt.io/advanced/support-new-devices/01_support_new_devices.html

[ch.eick]

Wenn du im "Log" diese Meldung hast beim pairen der Lampe

Dann gehts hier weiter
Please see: https://www.zigbee2mqtt.io/advanced/support-new-devices/01_support_new_devices.html

Dazu ist es bisher noch nicht gekommen.
Das Pairen des cc2531 scheint nicht zu starten.
Ich habe mit einem zweiten cc2531 bereits auch mal getestet, das ging auch nicht.

[TomLee]

Dazu ist es bisher noch nicht gekommen.
Das Pairen des cc2531 scheint nicht zu starten.

Doch offensichtlich schon, 0x90fd9ffffe9e4880 scheint deine Lampe zu sein, ausser dein Nachbar hat zu diesem Zeitpunkt auch gerade versucht ein Gerät anzulernen:

Code Auswählen Erweitern

2022-01-15_04:02:45 MQTT2_zigbee_bridge message: MQTT publish: topic 'zigbee2mqtt/bridge/log', payload '{"message":"interview_failed","meta":{"friendly_name":"0x90fd9ffffe9e4880"},"type":"pairing"}'
2022-01-15_09:10:39 MQTT2_zigbee_bridge message: Received message from unsupported device with Zigbee model 'undefined' and manufacturer name 'undefined'
2022-01-15_09:10:39 MQTT2_zigbee_bridge level: warning
2022-01-15_09:10:39 MQTT2_zigbee_bridge message: Please see: https://www.zigbee2mqtt.io/advanced/support-new-devices/01_support_new_devices.html
2022-01-15_09:10:39 MQTT2_zigbee_bridge level: warning
2022-01-15_09:20:12 MQTT2_zigbee_bridge message: Received message from unsupported device with Zigbee model 'undefined' and manufacturer name 'undefined'
2022-01-15_09:20:12 MQTT2_zigbee_bridge level: warning
2022-01-15_09:20:13 MQTT2_zigbee_bridge message: Please see: https://www.zigbee2mqtt.io/advanced/support-new-devices/01_support_new_devices.html
2022-01-15_09:20:13 MQTT2_zigbee_bridge level: warning

[Otto123]

Mal nebenbei: den conbee Stick musste ich mit einem ca 30 cm langem USB Kabel an den Conputer stecken. Wenn der Stick direkt in der USB Buchse steckte, sah zwar alles gut aus aber pairen und damit Funk ging überhaupt nicht. Auch nicht im kurzen Abstand zum Stick.

[ch.eick]

Mal nebenbei: den conbee Stick musste ich mit einem ca 30 cm langem USB Kabel an den Conputer stecken. Wenn der Stick direkt in der USB Buchse steckte, sah zwar alles gut aus aber pairen und damit Funk ging überhaupt nicht. Auch nicht im kurzen Abstand zum Stick.

Das check ich dann später, jetzt muss ich mal eben weg, sorry

[ch.eick]

Doch offensichtlich schon, 0x90fd9ffffe9e4880 scheint deine Lampe zu sein, ausser dein Nachbar hat zu diesem Zeitpunkt auch gerade versucht ein Gerät anzulernen:

Code Auswählen Erweitern

2022-01-15_04:02:45 MQTT2_zigbee_bridge message: MQTT publish: topic 'zigbee2mqtt/bridge/log', payload '{"message":"interview_failed","meta":{"friendly_name":"0x90fd9ffffe9e4880"},"type":"pairing"}'
2022-01-15_09:10:39 MQTT2_zigbee_bridge message: Received message from unsupported device with Zigbee model 'undefined' and manufacturer name 'undefined'
2022-01-15_09:10:39 MQTT2_zigbee_bridge level: warning
2022-01-15_09:10:39 MQTT2_zigbee_bridge message: Please see: https://www.zigbee2mqtt.io/advanced/support-new-devices/01_support_new_devices.html
2022-01-15_09:10:39 MQTT2_zigbee_bridge level: warning
2022-01-15_09:20:12 MQTT2_zigbee_bridge message: Received message from unsupported device with Zigbee model 'undefined' and manufacturer name 'undefined'
2022-01-15_09:20:12 MQTT2_zigbee_bridge level: warning
2022-01-15_09:20:13 MQTT2_zigbee_bridge message: Please see: https://www.zigbee2mqtt.io/advanced/support-new-devices/01_support_new_devices.html
2022-01-15_09:20:13 MQTT2_zigbee_bridge level: warning

Das könnte eventuell der Stick selber sein.

Auf der Lampe hatte ich mir vor Jahren schon "6EE" mit Edding drauf geschrieben, das sind die letzten drei Stellen des friendly_name .

[TomLee]

Ich hätt auch noch was, der Phantasie sind ja keine Grenzen gesetzt, ohne List mit Readings des jetzigen Bridge-Device.

EDIT: Hier noch ein Ausschnitt aus der früheren Installation. Da hatten die Lampen bereits funktioniert.
Da ich jetzt neu den Docker Container installiert habe und diesen auch ganz neu eingerichtet habe, habe ich vorher alle alten Devices umbenannt, damit sie neu angelegt werden können, Zusätzlich stehen sie natürlich auch auf disable 1.

Ich vermute (habs aber nicht ausprobiert) das klappt so nicht, auch wenn die Devices disabled sind ist der Inhalt der rL entscheidend und ein neues Device wird deswegen nicht angelegt, rename bringt dabei nix.

[Beta-User]

Nicht vergessen: eine Leuchte muss man idR. erst schalten, bevor Infos kommen.

Und: An Knopfdücken kann ich mich beim pairen nicht entsinnen...

[ch.eick]

Nicht vergessen: eine Leuchte muss man idR. erst schalten, bevor Infos kommen.

Und: An Knopfdücken kann ich mich beim pairen nicht entsinnen...

Das hatte ich so im Netz gefunden, mit einem Bild vom cc2531 und der Position der Taste.
Da steht 5 Sekunden drücken und dann soll die LED grün blinken.

Ich habe bereits beide Sticks ausprobiert und bei beiden geht es nicht. Leider hatte ein Arbeitskollege die FW drauf geschrieben, jetzt müsste ich dann die Post bemühen.
Kommt zufällig aus dem Raum 645** und könnte mir die Sticks neu fashen?

[ch.eick]

Ich hätt auch noch was, der Phantasie sind ja keine Grenzen gesetzt, ohne List mit Readings des jetzigen Bridge-Device.

Ich vermute (habs aber nicht ausprobiert) das klappt so nicht, auch wenn die Devices disabled sind ist der Inhalt der rL entscheidend und ein neues Device wird deswegen nicht angelegt, rename bringt dabei nix.

Was ist den "rL" ?

Hier ein List

Code Auswählen Erweitern


Internals:
   CID        zigbee_bridge
   DEF        zigbee_bridge
   DEVICETOPIC zigbee2mqtt
   FUUID      61e19dcd-f33f-61a8-3132-ddad58e09b35f0a5
   FVERSION   10_MQTT2_DEVICE.pm:0.254240/2022-01-05
   IODev      MQTT2_FHEM_Server
   LASTInputDev MQTT2_FHEM_Server
   MQTT2_FHEM_Server_CONN MQTT2_FHEM_Server_172.18.0.5_44788
   MQTT2_FHEM_Server_MSGCNT 54
   MQTT2_FHEM_Server_TIME 2022-01-15 14:29:46
   MSGCNT     54
   NAME       MQTT2_zigbee_bridge
   NR         543
   STATE      online
   TYPE       MQTT2_DEVICE
   OLDREADINGS:
   READINGS:
     2022-01-15 11:16:44   attrTemplateVersion 2022014
     2022-01-15 12:26:42   commit          414c51f
     2022-01-15 12:26:42   coordinator_meta_maintrel 3
     2022-01-15 12:26:42   coordinator_meta_majorrel 2
     2022-01-15 12:26:42   coordinator_meta_minorrel 6
     2022-01-15 12:26:42   coordinator_meta_product 0
     2022-01-15 12:26:42   coordinator_meta_revision 20190608
     2022-01-15 12:26:42   coordinator_meta_transportrev 2
     2022-01-15 12:26:42   coordinator_type zStack12
     2022-01-15 14:29:46   data_friendly_name 0x90fd9ffffe9e4880
     2022-01-15 14:29:46   data_ieee_address 0x90fd9ffffe9e4880
     2022-01-15 14:29:46   data_status     failed
     2022-01-15 14:29:46   devices         [{"definition":null,"endpoints":{"1":{"bindings":[],"clusters":{"input":[],"output":[]},"configured_reportings":[],"scenes":[]},"10":{"bindings":[],"clusters":{"input":[],"output":[]},"configured_reportings":[],"scenes":[]},"11":{"bindings":[],"clusters":{"input":["ssIasAce"],"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":"0x00124b0018e1e960","interview_completed":true,"interviewing":false,"network_address":0,"supported":false,"type":"Coordinator"},{"definition":null,"endpoints":{"1":{"bindings":[],"clusters":{"input":[],"output":[]},"configured_reportings":[],"scenes":[]}},"friendly_name":"0x90fd9ffffe9e4880","ieee_address":"0x90fd9ffffe9e4880","interview_completed":false,"interviewing":false,"network_address":33498,"supported":false,"type":"Unknown"}]
     2022-01-15 12:26:42   extensions      []
     2022-01-15 12:26:42   groups          []
     2022-01-15 12:26:41   info            {"commit":"414c51f","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":"/app/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":{"0x90fd9ffffe9e4880":{"friendly_name":"0x90fd9ffffe9e4880"}},"experimental":{"output":"json"},"external_converters":[],"frontend":{"host":"0.0.0.0","port":8080},"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.40: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 whether 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 (mostly battery 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":"Passive","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":{"ieee_address":"0x00124b0018e1e960","meta":{"maintrel":3,"majorrel":2,"minorrel":6,"product":0,"revision":20190608,"transportrev":2},"type":"zStack12"},"log_level":"info","network":{"channel":11,"extended_pan_id":"0xdddddddddddddddd","pan_id":6754},"permit_join":true,"restart_required":false,"version":"1.22.2"}
     2022-01-15 14:29:46   log             {"message":"interview_failed","meta":{"friendly_name":"0x90fd9ffffe9e4880"},"type":"pairing"}
     2022-01-15 14:29:46   log_level       info
     2022-01-15 14:29:46   log_message     MQTT publish: topic 'zigbee2mqtt/bridge/log', payload '{"message":"interview_failed","meta":{"friendly_name":"0x90fd9ffffe9e4880"},"type":"pairing"}'
     2022-01-15 12:26:42   network_channel 11
     2022-01-15 12:26:42   network_extendedPanID 0xdddddddddddddddd
     2022-01-15 12:26:42   network_panID   6754
     2022-01-15 12:26:42   permit_join     true
     2022-01-15 12:26:41   state           online
     2022-01-15 14:29:46   type            device_interview
     2022-01-15 12:26:42   version         1.22.2
     2022-01-15 12:21:36   z_reset_CC      set
Attributes:
   DbLogExclude .*
   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
   disable    0
   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
  $DEVICETOPIC/bridge/groups:.* groups
  $DEVICETOPIC/bridge/event:.* { json2nameValue($EVENT) }
  $DEVICETOPIC/bridge/extensions:.* extensions
   room       MQTT2
   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


Und hier die letzten Meldungen aus der Log Datei

Code Auswählen Erweitern


2022-01-15_14:29:46 MQTT2_zigbee_bridge log_level: info
2022-01-15_14:29:46 MQTT2_zigbee_bridge log_message: MQTT publish: topic 'zigbee2mqtt/bridge/event', payload '{"data":{"friendly_name":"0x90fd9ffffe9e4880","ieee_address":"0x90fd9ffffe9e4880","status":"failed"},"type":"device_interview"}'
2022-01-15_14:29:46 MQTT2_zigbee_bridge type: device_interview
2022-01-15_14:29:46 MQTT2_zigbee_bridge data_friendly_name: 0x90fd9ffffe9e4880
2022-01-15_14:29:46 MQTT2_zigbee_bridge data_status: failed
2022-01-15_14:29:46 MQTT2_zigbee_bridge data_ieee_address: 0x90fd9ffffe9e4880
2022-01-15_14:29:46 MQTT2_zigbee_bridge log_level: info
2022-01-15_14:29:46 MQTT2_zigbee_bridge log_message: MQTT publish: topic 'zigbee2mqtt/bridge/log', payload '{"message":"interview_failed","meta":{"friendly_name":"0x90fd9ffffe9e4880"},"type":"pairing"}'
2022-01-15_14:29:46 MQTT2_zigbee_bridge log: {"message":"interview_failed","meta":{"friendly_name":"0x90fd9ffffe9e4880"},"type":"pairing"}


[ch.eick]

Nicht vergessen: eine Leuchte muss man idR. erst schalten, bevor Infos kommen.

Und: An Knopfdücken kann ich mich beim pairen nicht entsinnen...

Wann startet die Lampe denn das Pairen?
Direkt nach dem Reset? Der wird mit einem kurzen Blinken quittiert.
Oder direkt nach dem Einschalten?

Ein Soft Reset des cc2531 über das  MQTT2_zigbee_bridge Device scheint auch zu klappen. Dabei geht die grüne LED aus und nach einiger Zeit wieder an.

Ein get MQTT2_zigbee_bridge devicelist bring das hier.

Code Auswählen Erweitern


log {"message":[{"dateCode":"20190608","friendly_name":"Coordinator","ieeeAddr":"0x00124b0018e1e960","lastSeen":1642265392965,"networkAddress":0,"softwareBuildID":"zStack12","type":"Coordinator"},{"description":"-","friendly_name":"0x90fd9ffffe9e4880","ieeeAddr":"0x90fd9ffffe9e4880","lastSeen":1642253247759,"networkAddress":33498,"type":"Unknown","vendor":"-"}],"type":"devices"}

Ich gehe davon aus, dass friendly_name":"0x90fd9ffffe9e4880 der Coordinator ist, da die Lampe nach meiner Notiz mit "6EE" enden sollte.

[rob]

rL - readingList

...habe ich vorher alle alten Devices umbenannt, damit sie neu angelegt werden können...

Wenn ich gepairte Devices direkt im z2m-WebIF einfach umbenenne (z.B. statt "0x14b457fffe74c00e" in "Tradfri_WoZi_Bulb1"), wird sogleich das so lautende m2d in FHEM angelegt. Das mit dem zuvor kryptischen Namen hatte ich danach immer gelöscht.

Den Schilderungen nach scheint das Problem zunächst beim Stick zu liegen, weniger FHEM-seitig. Dieses Issue liest sich recht passend dazu: https://github.com/Koenkk/zigbee2mqtt/issues/2761#issuecomment-576046090.
Hier werden alternative Methoden zum flashen beschrieben: https://www.zigbee2mqtt.io/guide/adapters/flashing/alternative_flashing_methods.html

Zum initialen Start hatte ich ein Test-FHEM in Docker gestartet und z2m darauf eingestellt und geschaut, wie sich das so verhält. Für Dich ggf. auch nützlich, weil Deine Prod-Instanz unangetastet bleibt, bis alles wie gewünscht läuft. Docker hast ja eh am Start

Ein Tradfri Motion Sensor war bei mir zickig. Im WebIF konnte ich das Pairing verfolgen: erst erkannt, dann als unbekannt, dann wieder ganz weg und von vorn. Die 5 Min. Pairing-Zeit reichten einfach nicht. Erst nach mehrmaligem Pairing war er dauerhaft drin. Nur fehlte Battery. Nach OTA-Update d. Sensors das ganze wieder von vorn. Nu passt es. Birnen und Taster waren allesamt problemlos.

Das Pairing startet sofort. Ich aktiviere es immer im WebIF.

[rob]

Ich gehe davon aus, dass friendly_name":"0x90fd9ffffe9e4880 der Coordinator ist, da die Lampe nach meiner Notiz mit "6EE" enden sollte.

Würde ich auch so sehen. Meiner taucht auch so ähnlich im Bridge-Device auf.

[TomLee]

log {"message":[{"dateCode":"20190608","friendly_name":"Coordinator","ieeeAddr":"0x00124b0018e1e960","lastSeen":1642265392965,"networkAddress":0,"softwareBuildID":"zStack12","type":"Coordinator"},{"description":"-","friendly_name":"0x90fd9ffffe9e4880","ieeeAddr":"0x90fd9ffffe9e4880","lastSeen":1642253247759,"networkAddress":33498,"type":"Unknown","vendor":"-"}],"type":"devices"}

Ich meine 0x00124b0018e1e960 wurde jetzt als  Coordinator erkannt und das 0x90fd9ffffe9e4880-Device ist ein Gerät welches nicht angelernt werden konnte, es ist aber auch keines der vier Leuchten aus der "alten Installation" wie dem Bild in #7 zu entnehmen ist.

Wann startet die Lampe denn das Pairen?
Direkt nach dem Reset? Der wird mit einem kurzen Blinken quittiert.

Nach der Anleitung die ich verlinkt hatte:

After resetting the bulb will automatically connect.

Hast du es auch mehrfach versucht ? In den Logauszügen die du bisher gezeigt hast war halt bisher kein Anlernversuch eines Geräts dessen friendly_name auf 6ee endete zu sehen.

Um auszuschliessen das es nur am Pairvorgang der Leuchten liegt, hast du nicht vlt. auch andere Geräte die sich evtl. ganz einfach anlernen lassen ?

[ch.eick]

Ich meine 0x00124b0018e1e960 wurde jetzt als  Coordinator erkannt und das 0x90fd9ffffe9e4880-Device ist ein Gerät welches nicht angelernt werden konnte, es ist aber auch keines der vier Leuchten aus der "alten Installation" wie dem Bild in #7 zu entnehmen ist.

Der Snapshot war nur ein Beispiel, dass es auf dem alten RPI3 native mal funktioniert hatte. Damit es kein durcheinander gibt werden ich die Devices mal als RAW in einem Txt File wegsichern und dann komplett löschen. Die wurden ja einfach bei dem Umzug zu FHEM im Docker wieder hergestellt, haben dort aber nie funktioniert.

Nach der Anleitung die ich verlinkt hatte:
Hast du es auch mehrfach versucht ? In den Logauszügen die du bisher gezeigt hast war halt bisher kein Anlernversuch eines Geräts dessen friendly_name auf 6ee endete zu sehen.

Um auszuschliessen das es nur am Pairvorgang der Leuchten liegt, hast du nicht vlt. auch andere Geräte die sich evtl. ganz einfach anlernen lassen ?

Ich habe noch mehr von den Lampen, denke aber weiterhin, dass es am cc2531 liegt, da er ja beim Pairen blinken sollte, was er nicht tut und das ich mich aber noch erinnern kann.

[ch.eick]

rL - readingList
Wenn ich gepairte Devices direkt im z2m-WebIF einfach umbenenne (z.B. statt "0x14b457fffe74c00e" in "Tradfri_WoZi_Bulb1"), wird sogleich das so lautende m2d in FHEM angelegt. Das mit dem zuvor kryptischen Namen hatte ich danach immer gelöscht.

Es wird ja noch kein Device angelegt.
Wie komme ich an das WEBIF ? Ist das in dem Docker Container?

Den Schilderungen nach scheint das Problem zunächst beim Stick zu liegen, weniger FHEM-seitig. Dieses Issue liest sich recht passend dazu: https://github.com/Koenkk/zigbee2mqtt/issues/2761#issuecomment-576046090.
Hier werden alternative Methoden zum flashen beschrieben: https://www.zigbee2mqtt.io/guide/adapters/flashing/alternative_flashing_methods.html

Das lese ich dann morgen mal mit klarem Kopf

Zum initialen Start hatte ich ein Test-FHEM in Docker gestartet und z2m darauf eingestellt und geschaut, wie sich das so verhält. Für Dich ggf. auch nützlich, weil Deine Prod-Instanz unangetastet bleibt, bis alles wie gewünscht läuft. Docker hast ja eh am Start

Es gibt noch keine Prod Instanz, der alte RPI3 besteht schon lange nicht mehr. Später würde ich das auch so testen, dafür ist dann auch der zweite Stick.

[rob]

Wie komme ich an das WEBIF ? Ist das in dem Docker Container?

Ja, über den Docker-Container. Laut Deinem Post #1 hast Du das WebIF über Port 8084 nach außen erreichbar gemacht.

Code Auswählen Erweitern


...
ports:
        - '8084:8080'
...

Schau mal bitte bei Gelegenheit, ob Du drauf kommst. Ich finde es macht alles leichter (Debug ist dort auch verfügbar).
Du kannst dann das Pairing beobachten und siehst hoffentlich was es so treibt 

[Beta-User]

Das sieht mir nach einem nicht abgeschlossenen pairing der Leuchte aus.

Denn: meine ersten Test-Tradfri begannen alle mit "0x90fd"...
Großschreibung bei den HEX-Werten sieht mir eher nach einem Versuch mit Tasmota aus, und da ist eh' alles anders (und nicht statisch).

[ch.eick]

Ja, über den Docker-Container. Laut Deinem Post #1 hast Du das WebIF über Port 8084 nach außen erreichbar gemacht.

Code Auswählen Erweitern


...
ports:
        - '8084:8080'
...

Schau mal bitte bei Gelegenheit, ob Du drauf kommst. Ich finde es macht alles leichter (Debug ist dort auch verfügbar).
Du kannst dann das Pairing beobachten und siehst hoffentlich was es so treibt 

Das ist ja cool, was ich alles habe
Ich hatte nur den Container Eingerichtet und das war's.

Da bin ich mal gespannt, was das wohl für ein Gerät ist.

EDIT: in den alten Devices habe ich das Gerät mit der Nummer jetzt gefunden, es ist eine IKEA Tradfri Remote, die in der Küche für die zwei Flood Panel hängt.

Die alte RAW definition ist diese hier

Code Auswählen Erweitern


defmod MQTT2_zigbee_0x90fd9ffffe9e4880_x MQTT2_DEVICE zigbee_0x90fd9ffffe9e4880
attr MQTT2_zigbee_0x90fd9ffffe9e4880_x DbLogExclude .*
attr MQTT2_zigbee_0x90fd9ffffe9e4880_x IODev MQTT2_FHEM_Server
attr MQTT2_zigbee_0x90fd9ffffe9e4880_x disable 1
attr MQTT2_zigbee_0x90fd9ffffe9e4880_x group Kueche
attr MQTT2_zigbee_0x90fd9ffffe9e4880_x icon it_remote
attr MQTT2_zigbee_0x90fd9ffffe9e4880_x model zigbee2mqtt_Wireless_Button
attr MQTT2_zigbee_0x90fd9ffffe9e4880_x readingList zigbee2mqtt/0x90fd9ffffe9e4880:.* { json2nameValue($EVENT) }
attr MQTT2_zigbee_0x90fd9ffffe9e4880_x room save_MQTT2_DEVICE
attr MQTT2_zigbee_0x90fd9ffffe9e4880_x stateFormat Click: click Action: action

setstate MQTT2_zigbee_0x90fd9ffffe9e4880_x Click: click Action: toggle
setstate MQTT2_zigbee_0x90fd9ffffe9e4880_x 2022-01-15 11:15:37 IODev MQTT2_FHEM_Server                      <<<< Das Datum ist von der Neudefinition des MQTT2 Servers
setstate MQTT2_zigbee_0x90fd9ffffe9e4880_x 2021-11-16 09:57:50 action toggle
setstate MQTT2_zigbee_0x90fd9ffffe9e4880_x 2019-11-11 16:54:36 associatedWith MQTT2_zigbee_pi
setstate MQTT2_zigbee_0x90fd9ffffe9e4880_x 2020-11-10 11:01:25 battery 34
setstate MQTT2_zigbee_0x90fd9ffffe9e4880_x 2020-09-25 19:05:07 duration 0.853
setstate MQTT2_zigbee_0x90fd9ffffe9e4880_x 2021-11-16 09:57:50 linkquality 65


[ch.eick]

Das sieht mir nach einem nicht abgeschlossenen pairing der Leuchte aus.

Denn: meine ersten Test-Tradfri begannen alle mit "0x90fd"...
Großschreibung bei den HEX-Werten sieht mir eher nach einem Versuch mit Tasmota aus, und da ist eh' alles anders (und nicht statisch).

Tasmota verwende ich bisher nicht. Ich habe überall nur den Hersteller Standard drauf. Jetzt zum Testen ist die eine LED Lampe in einer Fassung mit Schalter auf meinem Schreibtisch, in der Nähe des Sticks.
Ich habe alles zurück gesetzt und wollte ja neu anfangen. Also zigbee2mqtt Container neu und von Hand die Konfig eingetragen. LED Lampe zurück gesetzt. cc2531 mit Soft Reset und die MQTT2 Devices im FHEM gelöscht und anschließend wieder mit der RAW Devinition neu eingerichtet.

[Beta-User]

Wenn da eine FB gepairt war, braucht es vermutlich einen factory reset (10x ein-aus?).

[rob]

... und bevor Du doch am Stick Hand anlegst: Was passiert, wenn Du im WebIF auf "Anlernen aktivieren (Alle)" klickst und ein simples Gerät (z.B. Bulb) versuchst zu pairen? Also ohne am Stick etw. zu drücken, aber Gerät recht nah am Stick mit Reset-Prozedur in Pairingmodus bringen.
Mit etwas Glück tut er doch, wie er soll

Wenn das Pairing erfolgreich sein sollte, müsste das Gerät entspr. in der Liste auftauchen und über dessen Detailseite schaltbar sein.

[ch.eick]

Wenn da eine FB gepairt war, braucht es vermutlich einen factory reset (10x ein-aus?).

Ich habe jetzt erstmal noch aufgeräumt.

- Im FHEM sind nun alte Geräte entfernt
- Es gab auch noch ein altes FHEM MQTT2_Device mit doppelter DEF <name>  Konfiguration, was jetzt auch raus ist.

zigbee2MQTT Container
- Die FB ist jetzt gelöscht, da ich sie nicht bewust gepaired hatte.

- Base-Topic ist "zigbee2mqtt"
- MQTT Client ID ist "zigbee_bridge"
- Die LED am cc2531 kann man über die GUI Ein/Aus schalten (somit sollte der Container den cc2531 korrekt bedienen können)
- Es ist nun kein zigbee Device mehr konfiguriert
- permit_join ist auf true

FHEM
MQTT2_Device
DEF ist zigbee_bridge
DeviceTopic ist zigbee2mqtt
Im Log sieht man noch den remove der FB ( also steht die Kommunikation zum FHEM Device )
Gestern wurde das aktuell attrTemplate aktiviert

Code Auswählen Erweitern


Internals:
   CID        zigbee_bridge
   DEF        zigbee_bridge
   DEVICETOPIC zigbee2mqtt
   FUUID      61e19dcd-f33f-61a8-3132-ddad58e09b35f0a5
   FVERSION   10_MQTT2_DEVICE.pm:0.254240/2022-01-05
   IODev      MQTT2_FHEM_Server
   LASTInputDev MQTT2_FHEM_Server
   MQTT2_FHEM_Server_CONN MQTT2_FHEM_Server_172.18.0.5_50382
   MQTT2_FHEM_Server_MSGCNT 139
   MQTT2_FHEM_Server_TIME 2022-01-16 12:22:13
   MSGCNT     139
   NAME       MQTT2_zigbee_bridge
   NR         543
   STATE      online
   TYPE       MQTT2_DEVICE
   OLDREADINGS:
   READINGS:
     2022-01-16 12:20:04   associatedWith  MQTT2_zigbee_pi
     2022-01-15 11:16:44   attrTemplateVersion 2022014
     2022-01-16 12:20:30   commit          414c51f
     2022-01-16 12:20:30   coordinator_meta_maintrel 3
     2022-01-16 12:20:30   coordinator_meta_majorrel 2
     2022-01-16 12:20:30   coordinator_meta_minorrel 6
     2022-01-16 12:20:30   coordinator_meta_product 0
     2022-01-16 12:20:30   coordinator_meta_revision 20190608
     2022-01-16 12:20:30   coordinator_meta_transportrev 2
     2022-01-16 12:20:30   coordinator_type zStack12
     2022-01-16 12:22:13   data_block      false
     2022-01-16 12:22:13   data_force      true
     2022-01-15 20:40:12   data_friendly_name 0x90fd9ffffe9e4880
     2022-01-16 12:22:13   data_id         0x90fd9ffffe9e4880
     2022-01-15 20:40:12   data_ieee_address 0x90fd9ffffe9e4880
     2022-01-16 12:20:19   data_restart_required true
     2022-01-15 14:29:46   data_status     failed
     2022-01-16 12:22:12   devices         [{"definition":null,"endpoints":{"1":{"bindings":[],"clusters":{"input":[],"output":[]},"configured_reportings":[],"scenes":[]},"10":{"bindings":[],"clusters":{"input":[],"output":[]},"configured_reportings":[],"scenes":[]},"11":{"bindings":[],"clusters":{"input":["ssIasAce"],"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":"0x00124b0018e1e960","interview_completed":true,"interviewing":false,"network_address":0,"supported":false,"type":"Coordinator"}]
     2022-01-16 12:03:35   error           Failed to remove device '0x90fd9ffffe9e4880' (block: false, force: false) (Error: AREQ - ZDO - mgmtLeaveRsp after 10000ms)
     2022-01-16 12:20:30   extensions      []
     2022-01-16 12:22:12   groups          []
     2022-01-16 12:20:30   info            {"commit":"414c51f","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":"/app/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":{"0x90fd9ffffe9e4880":{"friendly_name":"0x90fd9ffffe9e4880"}},"experimental":{"output":"json"},"external_converters":[],"frontend":{"host":"0.0.0.0","port":8080},"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_bridge","force_disable_retain":false,"include_device_information":false,"keepalive":60,"reject_unauthorized":true,"server":"mqtt://192.168.178.40:1883","version":4},"ota":{"disable_automatic_update_check":false,"update_check_interval":1440},"passlist":[],"permit_join":true,"serial":{"adapter":"auto","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 whether 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 (mostly battery 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":"Passive","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":{"ieee_address":"0x00124b0018e1e960","meta":{"maintrel":3,"majorrel":2,"minorrel":6,"product":0,"revision":20190608,"transportrev":2},"type":"zStack12"},"log_level":"info","network":{"channel":11,"extended_pan_id":"0xdddddddddddddddd","pan_id":6754},"permit_join":true,"restart_required":false,"version":"1.22.2"}
     2022-01-15 20:40:12   log             {"message":"announce","meta":{"friendly_name":"0x90fd9ffffe9e4880"},"type":"device_announced"}
     2022-01-16 12:22:12   log_level       info
     2022-01-16 12:22:12   log_message     MQTT publish: topic 'zigbee2mqtt/bridge/response/device/remove', payload '{"data":{"block":false,"force":true,"id":"0x90fd9ffffe9e4880"},"status":"ok","transaction":"ylr3q-5"}'
     2022-01-16 12:20:30   network_channel 11
     2022-01-16 12:20:30   network_extendedPanID 0xdddddddddddddddd
     2022-01-16 12:20:30   network_panID   6754
     2022-01-16 12:20:30   permit_join     true
     2022-01-16 12:20:30   state           online
     2022-01-16 12:22:13   status          ok
     2022-01-16 12:22:12   subscriptions   zigbee2mqtt/#
     2022-01-16 12:22:13   transaction     ylr3q-5
     2022-01-15 20:40:12   type            device_announce
     2022-01-16 12:20:30   version         1.22.2
     2022-01-15 12:21:36   z_reset_CC      set
Attributes:
   DbLogExclude .*
   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
   disable    0
   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
  $DEVICETOPIC/bridge/groups:.* groups
  $DEVICETOPIC/bridge/event:.* { json2nameValue($EVENT) }
  $DEVICETOPIC/bridge/extensions:.* extensions
zigbee2mqtt/bridge/response/device/remove:.* { json2nameValue($EVENT) }
zigbee2mqtt/bridge/response/touchlink/scan:.* { json2nameValue($EVENT) }
zigbee2mqtt/bridge/response/options:.* { json2nameValue($EVENT) }
zigbee_bridge:zigbee2mqtt/bridge/response/restart:.* { json2nameValue($EVENT) }
   room       MQTT2
   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


Somit sollte es jetzt eine saubere leere Umgebung sein, an die ich das erste zigbee Device anlernen kann.

Gibt es eine Möglichkeit den cc2531 auch komplett zurück zu setzen, damit er nicht mehr alte Teiler der Konfiguration hat. Nach meiner Erinnerung ist der cc2531 ja ein coordinator und merkt sich seine gepairten Geräten.

Die FB ist wohl etwas schwierig bei der Konfiguration, weshalb ich sie erstmal nach hinten schiebe.

Die LED Lampe ist frisch zurück gesetzt.

[TomLee]

LED Lampe zurück gesetzt. cc2531 mit Soft Reset und die MQTT2 Devices im FHEM gelöscht und anschließend wieder mit der RAW Devinition neu eingerichtet.

Ich meine der Ablauf passt so nicht, warum setzt du die Lampe zurück und machst danach ein Soft Reset des Stick (wozu auch immer der gut sein soll)? Nach dem zurücksetzen der Leuchte geht sie doch in den Anlernvorgang und du setzt dann den Stick zurück ?

Vlt mal klein anfangen, das auch jeder folgen kann und Tipps geben:
Kannst du bitte mal alle Devices in Fhem die du da von Hand eingerichtet hast (auch das Bridge-Device) löschen und den Container/z2m (wie auch immer, kenn mich mit Docker nicht aus) neu starten ?
Daraufhin sollte dir automatisch ein MQTT2-Device mit dem Namen MQTT2_zigbee_bridge angelegt werden auf welches das zigbee2mqtt_bridge-Template angewendet wird. Vorsichtshalber machst du ein get MQTT2_zigbee_bridge devicelist.
Von diesem Device zeigst du dann bitte ein (Raw)-List (mit Readings).
Meine Vermutung ist wir sehen dann (wieder) in dem Reading Devices entweder nur den Coordinator 0x00124b0018e1e960 oder den Coordinator und die (nicht vollständig gepairte) Fernbedienung 0x90fd9ffffe9e4880.

[ch.eick]

... und bevor Du doch am Stick Hand anlegst: Was passiert, wenn Du im WebIF auf "Anlernen aktivieren (Alle)" klickst und ein simples Gerät (z.B. Bulb) versuchst zu pairen? Also ohne am Stick etw. zu drücken, aber Gerät recht nah am Stick mit Reset-Prozedur in Pairingmodus bringen.
Mit etwas Glück tut er doch, wie er soll

Wenn das Pairing erfolgreich sein sollte, müsste das Gerät entspr. in der Liste auftauchen und über dessen Detailseite schaltbar sein.

Im WebIF steht es in der Konfig mit permit_join true und es wird "Anlernen Deaktivieren (alle)" angezeigt.

- Die Lampe ist max 5 cm vom cc2531
- Der reset der Lampe wird beim 6ten Einschalten mit einem kurzen Blinken quittiert
- Die Lampe bleibt mit dem 6sten Einschalten Eingeschaltet neben dem Stick liegen

- Ein Klick auf "Geräte" im WebIF zeigt keine Geräte an.

- Im FHEM habe ich jetzt gerade die FB als neues Gerät gefunden, von der Zeit wo sie gelöscht würde.
==> Somit funktioniert das automatische Anlegen im FHEM auch schon mal.
Ich werde das Device im FHEM jetzt wieder löschen, da es im zigbee2MQTT ja nicht mehr existent ist.

[TomLee]

2022-01-16 12:03:35   error           Failed to remove device '0x90fd9ffffe9e4880' (block: false, force: false) (Error: AREQ - ZDO - mgmtLeaveRsp after 10000ms)

Klick mal im Frontend im Reiter Geräte auf den Eimer zum löschen, wähle vor dem löschen den Schalter Erzwinge Entfernen.
Ist die Fernbedienung dann endgültig gelöscht ?



OT

Wenn ja wird dann ein zweites "Bridge"-Device angelegt in dessen rL dieser Topic steht ?

Code Auswählen Erweitern

zigbee2mqtt/bridge/response/device/remove:.* { json2nameValue($EVENT) }

[ch.eick]

Klick mal im Frontend im Reiter Geräte auf den Eimer zum löschen, wähle vor dem löschen den Schalter Erzwinge Entfernen.
Ist die Fernbedienung dann endgültig gelöscht ?



OT

Wenn ja wird dann ein zweites Bridge-Device angelegt in dessen rL dieser Topic steht ?

Code Auswählen Erweitern

zigbee2mqtt/bridge/response/device/remove:.* { json2nameValue($EVENT) }

Genau das ist jetzt bereits alles erledigt. Im List vom Bridge-Device konnte man das "remove" ja bereits sehen.

Es ist nun wirklich alles sauber und inklusieve zigbee2MQTT Container frisch durchgestartet.
Die Kommunikation vom cc2531 über zigbee2MQTT bis ins FHEM ist durch die verschiedensten Meldungen überprüft.

Es hakt jetzt wirklich beim Anlernen.

[ch.eick]

Vlt mal klein anfangen, das auch jeder folgen kann und Tipps geben:
Kannst du bitte mal alle Devices in Fhem die du da von Hand eingerichtet hast (auch das Bridge-Device) löschen und den Container/z2m (wie auch immer, kenn mich mit Docker nicht aus) neu starten ?

Ist erledigt

Daraufhin sollte dir automatisch ein MQTT2-Device mit dem Namen MQTT2_zigbee_bridge angelegt werden auf welches das zigbee2mqtt_bridge-Template angewendet wird.

Ist ebenfalls erledigt und das Device wurde wieder angelegt.

Vorsichtshalber machst du ein get MQTT2_zigbee_bridge devicelist.

Das wurde mit einem Timeout beantwortet

Von diesem Device zeigst du dann bitte ein (Raw)-List (mit Readings).

Code Auswählen Erweitern


Internals:
   CFGFN     
   CID        zigbee_bridge
   DEF        zigbee_bridge
   DEVICETOPIC zigbee2mqtt
   FUUID      61e40970-f33f-61a8-3cbb-ae029322bcac30da
   IODev      MQTT2_FHEM_Server
   LASTInputDev MQTT2_FHEM_Server
   MQTT2_FHEM_Server_CONN MQTT2_FHEM_Server_172.18.0.5_56188
   MQTT2_FHEM_Server_MSGCNT 7
   MQTT2_FHEM_Server_TIME 2022-01-16 13:15:59
   MSGCNT     7
   NAME       MQTT2_zigbee_bridge
   NR         27477
   STATE      online
   TYPE       MQTT2_DEVICE
   OLDREADINGS:
   READINGS:
     2022-01-16 13:08:30   attrTemplateVersion 2022014
     2022-01-16 13:15:59   log_level       info
     2022-01-16 13:15:59   log_message     MQTT publish: topic 'zigbee2mqtt/bridge/config/devices', payload '[{"dateCode":"20190608","friendly_name":"Coordinator","ieeeAddr":"0x00124b0018e1e960","lastSeen":1642335359289,"networkAddress":0,"softwareBuildID":"zStack12","type":"Coordinator"}]'
Attributes:
   DbLogExclude .*
   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
  $DEVICETOPIC/bridge/groups:.* groups
  $DEVICETOPIC/bridge/event:.* { json2nameValue($EVENT) }
  $DEVICETOPIC/bridge/extensions:.* extensions
   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


Meine Vermutung ist wir sehen dann (wieder) in dem Reading Devices entweder nur den Coordinator 0x00124b0018e1e960 oder den Coordinator und die (nicht vollständig gepairte) Fernbedienung 0x90fd9ffffe9e4880.

Die Fernbedienung wurde ja bereits im zigbee2MQTT entfernt. Es sind somit keinerlei Geräte im WebIF zu sehen.

[TomLee]

Nur der/dem Vollständigkeit/Verständnis wegen:

Beim letzten List hast du zuvor entweder keinen Neustart von z2m gemacht oder FHEMWEB nach dem Neustart nicht aktualisiert.



Hast du denn jetzt mal andere Lampen probiert anzulernen ?

Und vor allem wie dann ?
Das anlernen sollte doch jetzt eigentlich klappen und man müsste mal was von einer Erfolgsmeldung hören, auch wenns nur ein misslungener Anlernversuch ist 

[ch.eick]

Nur der/dem Vollständigkeit/Verständnis wegen:

Beim letzten List hast du zuvor entweder keinen Neustart von z2m gemacht oder FHEMWEB nach dem Neustart nicht aktualisiert.

Den Neustart hatte ich gemacht, als das FHEM Device gelöscht war. Danach wurde es ja wieder neu angelegt ...

Jetzt hab eich nochmals den Container neu gestartet und hier ist das List

Code Auswählen Erweitern


Internals:
   CFGFN     
   CID        zigbee_bridge
   DEF        zigbee_bridge
   DEVICETOPIC zigbee2mqtt
   FUUID      61e40970-f33f-61a8-3cbb-ae029322bcac30da
   IODev      MQTT2_FHEM_Server
   LASTInputDev MQTT2_FHEM_Server
   MQTT2_FHEM_Server_CONN MQTT2_FHEM_Server_172.18.0.5_34652
   MQTT2_FHEM_Server_MSGCNT 18
   MQTT2_FHEM_Server_TIME 2022-01-16 13:50:53
   MSGCNT     18
   NAME       MQTT2_zigbee_bridge
   NR         27477
   STATE      online
   TYPE       MQTT2_DEVICE
   OLDREADINGS:
   READINGS:
     2022-01-16 13:08:30   attrTemplateVersion 2022014
     2022-01-16 13:50:53   commit          414c51f
     2022-01-16 13:50:53   coordinator_meta_maintrel 3
     2022-01-16 13:50:53   coordinator_meta_majorrel 2
     2022-01-16 13:50:53   coordinator_meta_minorrel 6
     2022-01-16 13:50:53   coordinator_meta_product 0
     2022-01-16 13:50:53   coordinator_meta_revision 20190608
     2022-01-16 13:50:53   coordinator_meta_transportrev 2
     2022-01-16 13:50:53   coordinator_type zStack12
     2022-01-16 13:50:53   devices         [{"definition":null,"endpoints":{"1":{"bindings":[],"clusters":{"input":[],"output":[]},"configured_reportings":[],"scenes":[]},"10":{"bindings":[],"clusters":{"input":[],"output":[]},"configured_reportings":[],"scenes":[]},"11":{"bindings":[],"clusters":{"input":["ssIasAce"],"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":"0x00124b0018e1e960","interview_completed":true,"interviewing":false,"network_address":0,"supported":false,"type":"Coordinator"}]
     2022-01-16 13:50:53   extensions      []
     2022-01-16 13:50:53   groups          []
     2022-01-16 13:50:53   info            {"commit":"414c51f","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":"/app/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":{},"experimental":{"output":"json"},"external_converters":[],"frontend":{"host":"0.0.0.0","port":8080},"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_bridge","force_disable_retain":false,"include_device_information":false,"keepalive":60,"reject_unauthorized":true,"server":"mqtt://192.168.178.40:1883","version":4},"ota":{"disable_automatic_update_check":false,"update_check_interval":1440},"passlist":[],"permit_join":true,"serial":{"adapter":"auto","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 whether 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 (mostly battery 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":"Passive","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":{"ieee_address":"0x00124b0018e1e960","meta":{"maintrel":3,"majorrel":2,"minorrel":6,"product":0,"revision":20190608,"transportrev":2},"type":"zStack12"},"log_level":"info","network":{"channel":11,"extended_pan_id":"0xdddddddddddddddd","pan_id":6754},"permit_join":true,"restart_required":false,"version":"1.22.2"}
     2022-01-16 13:50:53   log_level       info
     2022-01-16 13:50:53   log_message     MQTT publish: topic 'zigbee2mqtt/bridge/config', payload '{"commit":"414c51f","coordinator":{"meta":{"maintrel":3,"majorrel":2,"minorrel":6,"product":0,"revision":20190608,"transportrev":2},"type":"zStack12"},"log_level":"info","network":{"channel":11,"extendedPanID":"0xdddddddddddddddd","panID":6754},"permit_join":true,"version":"1.22.2"}'
     2022-01-16 13:50:53   network_channel 11
     2022-01-16 13:50:53   network_extendedPanID 0xdddddddddddddddd
     2022-01-16 13:50:53   network_panID   6754
     2022-01-16 13:50:53   permit_join     true
     2022-01-16 13:50:51   state           online
     2022-01-16 13:50:53   version         1.22.2
Attributes:
   DbLogExclude .*
   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
  $DEVICETOPIC/bridge/groups:.* groups
  $DEVICETOPIC/bridge/event:.* { json2nameValue($EVENT) }
  $DEVICETOPIC/bridge/extensions:.* extensions
   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


Hast du denn jetzt mal andere Lampen probiert anzulernen ?

Und vor allem wie dann ?

Wie bereits mehrfach beschrieben, beginnend mit einem Reste der Lampe in nächster Nähe des cc2531.

Das anlernen sollte doch jetzt eigentlich klappen und man müsste mal was von einer Erfolgsmeldung hören, auch wenns nur ein misslungener Anlernversuch ist 

Genau das ist ja das Problem, es wird nichts angelernt und es kommen dazu auch keine Meldungen.

Nach wie vor vermute ich, dass der cc2531 zuerst mit s2 zum pairen aktiviert werden muss, was aber bisher nicht klappt. Ich lese dazu parallel im WEB, finde aber bisher keine Lösung.
Dort steht nur was von 5 Sekunden S2 drücken, dann soll es blinken.... aber nichts passiert.

[ch.eick]

Ich schmeiß mich weg
Vielen Dank für all Eure tollen Tipps und auch den jetzt umgesetzten, zu dem ich gerade erst gekommen bin.
Ich glaube ich habe sehr viel in den letzten zwei Tagen gelernt und mache mich dann jetzt daran die ganzen anderen Geräte anzulernen.

Es liegt wohl an der Strahlung des RPI4, durch eine USB Verlängerung ist der cc2531 jetzt weiter vom Gerät weg.
Ein weiteres bloßes Einschalten der Lampe und schon ist das Gerät im zigbee2MQTT erfolgreich zu sehen.
Nach einiger Zeit wurde auch das FHEM Device passend zur Lampe eingerichtet.

Ich mach jetzt erstmal Pause

Das war ja einfach
    Christian

[ch.eick]

Sooo, jetzt wäre ich bei den Floalt Panel mit der Fernbedienung.

zigbee2MQTT
- ein connect der remote control hat funktioniert => in FHEM wurde ein Device angelegt, es gibt jedoch anscheinend kein Template dafür. Unter Action werden die tasten bereits angezeigt
- das erste Floalt Panel wurde auch erkannt und angelernt => das Template wurde in FHEM angewendet und auch der Farbwechsel funktioniert
- das zweite Foalt Panel wird leider als "nicht unterstützt" angezeigt, obwohl beide zusammen gekauft wurden
EDIT: es ist schon lustig. jetzt habe ich zuerst die "nicht unterstützte" angelernt und sie wurde erkannt. Danach das zweite Floalt Panel und das ging auch.
     Jetzt sind beide in einer Gruppe und laufen darüber auch synchron. Die FW updates laufen bereits und bei der FB warte ich noch auf ne neue Batterie


- Leider lässt sich die remote control auch nicht in eine Gruppe mit dem ersten Floalt Panel zusammen fassen. Es kommt ein Timeout für die FB.

Nun wieder meine Erinnerung:
Ich meine das Anlernen wäre auch anders gewesen. Bisher hatte ich die FB erst mit dem einen, dann mit dem anderen Floalt Panel angelernt.
Dadurch wurde wohl direkt in der FB eine Gruppe angelegt und beide ließen sich synchron bedienen.
Jetzt besteht die Verbindung der FB zu den Lampen nicht mehr direkt.

Ich muss aber jetzt erstmal ne neue Batterie kaufen gehen, die in der FB macht bald schlapp.

[rob]

- Leider lässt sich die remote control auch nicht in eine Gruppe mit dem ersten Flood Panel zusammen fassen. Es kommt ein Timeout für die FB.

Bin nicht sicher, ob ich Dir folgen kann. Mit Gruppe meinst Du die Gruppen im WebIF?
Falls ja, bei meinen Tradfris lief das so: die Bindungs werden dort zunächst nur für die Lampen gesetzt; also z.B. Bulb1 bis 3 in eine Gruppe "Wohnzimmer" mit beliebiger Gruppen-ID. Danach in die Detailseite gehen zur FB und dort unter "Bindungen" die zuvor definierte Gruppe "Wohnzimmer" zuordnen - KURZ VOR dem Klick auf "verbinden" irgeneine Taste auf der FB drücken, sonst kommt timeout.
Je nach Firmwarestand hatten meine Tradfri-FBs feste Gruppen-IDs. Erst nach OTA-Update konnten sie die neue GID übernehmen (bis dahin musste die fixe GID ermittelt und diese für die Gruppe verwendet werden).

Vielleicht klappt das bei Deinen Gerätschaften ganz ähnlich.

[ch.eick]

Bin nicht sicher, ob ich Dir folgen kann. Mit Gruppe meinst Du die Gruppen im WebIF?
Falls ja, bei meinen Tradfris lief das so: die Bindungs werden dort zunächst nur für die Lampen gesetzt; also z.B. Bulb1 bis 3 in eine Gruppe "Wohnzimmer" mit beliebiger Gruppen-ID. Danach in die Detailseite gehen zur FB und dort unter "Bindungen" die zuvor definierte Gruppe "Wohnzimmer" zuordnen - KURZ VOR dem Klick auf "verbinden" irgendeine Taste auf der FB drücken, sonst kommt timeout.
Je nach Firmwarestand hatten meine Tradfri-FBs feste Gruppen-IDs. Erst nach OTA-Update konnten sie die neue GID übernehmen (bis dahin musste die fixe GID ermittelt und diese für die Gruppe verwendet werden).

Vielleicht klappt das bei Deinen Gerätschaften ganz ähnlich.

Das hört sich schon mal super an.
Ja, es ist alles im WebIF.
Ich habe bereits bei allen Lampen einen FW Update gemacht, die Fernbedienung hat noch keine neue Batterie
Ich erinnere mich aber auch an die Situation mit der festen GruppenID bei der FB, also mache ich zuerst mal ein Update. Den Tip mit dem Tastendruck finde ich auch plausiebel, dann ist die FB ja wieder wach.

Dann habe ich noch ein anderes Problem mit einer Lampe, da hat meine Frau den FW update ausversehen kurz vor 100% abgebrochen. Auch ein reset der Lampe und neues Anlernen zeigt leider immer die alte Version an und beim "Prüfen auf neues Update" sagt er es wäre kein neues da. Haste da auch eine Idee? Funktionieren tut die Lampe aber noch.

Im WebIF gibt es einen Tab mit Erweiterungen, was kann man denn da noch Erweitern? Im Netz habe ich bisher nichts  gefunden.
Gibt es eventuell eine Erweiterung für eine Handy App als Fernbedienung? Oder muss ich da besser den Weg über FHEM nehmen?

[rob]

Haste da auch eine Idee? Funktionieren tut die Lampe aber noch.

Die Versionsanzeige zu den OTA-Update finde ich tatsächlich strange. Zumindest bei mir zeigt er vorher und nachher immer die selbe Version an. Die Updates waren aber erfolgreich und auch das GID-Thema war gelöst. Könnte also gut sein, dass das Update doch geklappt hat.
Oder bietet er Dir noch immer den roten Button an "Update Geräte Firmware"?

Die Erweiterungen verstehe ich so wie unter FHEM die MyUtils. Dort kann man eigenes JavaScripts einpflegen (https://www.zigbee2mqtt.io/advanced/more/user_extensions.html#user-extensions-list). Weil ich aber nix vermisse, hab ich da noch nicht geforscht 
Und ja, FHEM-seitig lässt sich ja eh (fast) alles lösen

[ch.eick]

Die Versionsanzeige zu den OTA-Update finde ich tatsächlich strange. Zumindest bei mir zeigt er vorher und nachher immer die selbe Version an.

Bei 8 von 9 Lampen ist die Versionsnummer jetzt aktueller.

Die Updates waren aber erfolgreich und auch das GID-Thema war gelöst. Könnte also gut sein, dass das Update doch geklappt hat.
Oder bietet er Dir noch immer den roten Button an "Update Geräte Firmware"?

Bei der letzten Lampe ist im WebIF noch die alte Versionsnummer, es wird aber auch kein Update mehr angeboten. So ist es dann halt. Vieleicht beim nächsten mal

Die Erweiterungen verstehe ich so wie unter FHEM die MyUtils. Dort kann man eigenes JavaScripts einpflegen (https://www.zigbee2mqtt.io/advanced/more/user_extensions.html#user-extensions-list). Weil ich aber nix vermisse, hab ich da noch nicht geforscht 

Das muster hatte ich auch gefunden, aber wie gesagt keine lauffähigen Umsetzungen, noch nicht einmal, dass es jemand versucht hätte.

Und ja, FHEM-seitig lässt sich ja eh (fast) alles lösen

Was denn nicht

Ich habe bei den Lampen auch mal das Availability Bit getestet. Online war gut, nach dem Ausschalten ging es auch auf Offline, das war auch okay, aber nach dem Einschalten ging es dann leider nicht wieder zum Online. Dadurch wird dann wohl auch die Kommunikation gestoppt und die Lampen ließen sich nicht mehr schalten. Ikea Lampen antworten wohl nicht auf den Ping, habe ich in einem englischen Forum gelesen. Nach dem Abschalten des Availablility Check konnte man jedoch die Lampen wieder steuern.

Manchmal scheint sich der Docker Container auch irgend wie aufzuhängen, dann ist der Port 8084 (8080) nicht mehr erreichbar. Nach dem Container Stop, anschließendem ziehen und stecken des cc2531 und erneutem Start des Containers geht es dann wieder weiter.

Ich denke, ich muss das Power Off bei den Lampen unterbinden und sie fest mit 230V verdraten, dann kann es kein Offline und erneutes suchen/verbinden mehr geben. Leider gibt es für mein Schalterprogram keinen Einbausender für zigbee. Aber ich kann die Wechselschaltung noch über einen Shelly einbinden, für die anderen Lampen, die meine Frau dann noch schalten kann. In FHEM wird dann der Shelly mit dem zigbee verklöppelt und alles wird gut. Dann wird sicher auch Dimmen und vereinzelte Lampen ein/aus funktionieren. Schauen wir mal.

[rob]

Bei 8 von 9 Lampen ist die Versionsnummer jetzt aktueller.

Also bei der Beweislage ziehe ich mein Tradfri-Beispiel zurück  Deine Lampen verhalten sich offenkundig vorbildlich, sofern sie nicht gestört werden 
Vielleicht lohnt sich das Repairing? Einfach in z2m aktivieren und Reset-Prozedur starten, es erkennt ja selber, dass das Gerät bekannt ist und aktualisiert es. Könnte ja sein der Update-Schluckauf löst sich mit. Ansonsten wär ich da überfragt und ggf. kann wer anderes mehr sagen.

Ikea Lampen antworten wohl nicht auf den Ping, habe ich in einem englischen Forum gelesen. Nach dem Abschalten des Availablility Check konnte man jedoch die Lampen wieder steuern.

Ah, gut zu wissen. Dann lass ich dort auch die Finger von.

Manchmal scheint sich der Docker Container auch irgend wie aufzuhängen, dann ist der Port 8084 (8080) nicht mehr erreichbar. Nach dem Container Stop, anschließendem ziehen und stecken des cc2531 und erneutem Start des Containers geht es dann wieder weiter.

Ja, sobald das GW entschwindet (z.B. weil ich es reboote), beendet sich z2m augenblicklich. Wegen der Option "restart: always", kommt es aber sofort wieder hoch - dauert ein paar Sekunden, bis der Port wieder zugreifbar ist. Vielleicht auch das Phänomen bei Dir. Ein "docker logs <containername>" gibt evtl. Aufschluss.
Vorsorglich: Möchstest Du die Stick-Anbindung bei /dev/ttyACM0 belassen?
Erinner mich noch, dass mein Cobee2 und der Aeotec sich gegenseitig in die Waden bissen, weil beide vom ACM0-Topf naschen wollten. Mit serial /dev/serial/by-id/... war Ruhe.
Wenn es keine Verbesserung bringt, so ist es ggf. eine Fehlerquelle weniger, wenn Du doch mal andere USB-Sachen hinzufügst 
Btw. "privileged: true" - es sollte auch ohne laufen. Oder zickt der Stick sonst?

[ch.eick]

Ja, sobald das GW entschwindet (z.B. weil ich es reboote), beendet sich z2m augenblicklich. Wegen der Option "restart: always", kommt es aber sofort wieder hoch - dauert ein paar Sekunden, bis der Port wieder zugreifbar ist. Vielleicht auch das Phänomen bei Dir. Ein "docker logs <containername>" gibt evtl. Aufschluss.
Vorsorglich: Möchstest Du die Stick-Anbindung bei /dev/ttyACM0 belassen?
Erinner mich noch, dass mein Cobee2 und der Aeotec sich gegenseitig in die Waden bissen, weil beide vom ACM0-Topf naschen wollten. Mit serial /dev/serial/by-id/... war Ruhe.
Wenn es keine Verbesserung bringt, so ist es ggf. eine Fehlerquelle weniger, wenn Du doch mal andere USB-Sachen hinzufügst 
Btw. "privileged: true" - es sollte auch ohne laufen. Oder zickt der Stick sonst?

Das schau ich  mir die Tage mal an.
An USB ist ein Keyboard, der cc2531 Stick, jetzt mit Verlängerung und eine SSD über USB3

Jetzt schau ich erstmal wie ich die Floodpanel wieder mit der Fernbedienung verbunden bekomme, das zickt noch rum.
Der Update der FBs hat wohl nicht funktioniert. Da kommt die Meldung, dass keine Packages abgeholt worden sind.

Die FBs sind bereits in FHEM und man sieht die Tasten, die gedrückt werden. Leider fehlt ein Template, um das schön zu machen.