Zigbee CC2531 USB-Stick

[accessburn]

Hallöchen,

ich habe mir folgenden USB-Stick geholt um die Ikea-Tradfri-Dinger zu steuern.

https://www.ebay.de/itm/CC2531-ZigBee-USB-Sick-zigbee2mqtt-ioBroker-FHEM-Magnet-Antenne-8dbi-Firmware/372671349323

Kann mir jemand eine gescheite Anleitung empfehlen? Denn beim suchen danach finde ich diverse, vor allem unterschiedliche Anleitungen, bin da leicht verwirrt was ich nehmen soll.


Grüße aus Ffm,
Toby

[supernova1963]

Bei mir hatte damals diese Anleitung mit dem fhem MQTT2_SERVER als Broker funktioniert.

lg, Gernot

[accessburn]

Okay, dann bin ich wohl auf dem richtigen weg. Aktuell scheitere ich nur dran das ich nicht zuhause bin und das 'install' sagt das ick de knöppje drücken soll

Ich hoffe das klappt alles... Aber Danke schon mal.

[accessburn]

Okay, ich hänge entgültig...

Ich habe aus dem Wiki die Bridge angelegt und eine Bulb angelegt wie im beispiel. Jedoch weiß ich jetzt nicht weiter.
unter "get devicelist" kommt nur "Timeout reading answer for zigbee2mqtt/bridge/config/devices".

"zigbee2mqtt:info 2019-8-14 11:21:59 AM Successfully reenabled joining"
scheint zu laufen, aber was mach ich denn nun? Mir fehlt da irgendwie ein Schritt.

[supernova1963]

1. Der MQTT Broker in fhem ist aktiviert und ggf. mit basicauth abgesichert und "initialUsbCheck" ist deaktiviert?

Code Auswählen Erweitern

defmod MQTT2 MQTT2_SERVER 1883 global

defmod allowed_MQTT2 allowed
attr allowed_MQTT2 validFor MQTT2

set allowed_MQTT2 basicAuth <username> <password>

attr initialUsbCheck disable 1

2. Die Installation von zigbee2mqtt ist erfolgreich abgeschlossen und die "mqtt: client_id" in der configuration.yaml ist gesetzt?
3. Das / die Zigbee Gerät(e) ist/sind mit zigbee2mqtt erfolgreich gepairt (Logs) und wurden ggf. in der configuration.yaml benannt?
z.B.:

Code Auswählen Erweitern

homeassistant: true
permit_join: true
mqtt:
  base_topic: zigbee2mqtt
  server: '<IP fhem Server oder localhost>'
  user: <username>
  password: '<password>'
  client_id: 'zigbeeStick'
  include_device_information: true
serial:
  port: /dev/serial/by-id/<id des CC2531 USB Sticks>
advanced:
  log_level: info
devices:
  '0x00158d000276e175':
    friendly_name: 'Bewegungsmelder_01'
    retain: false
  '0x00158d00023256f8':
    friendly_name: 'Raumklima_01'
    retain: true

4. Die Verbindung von zigbee2mqtt zum MQTT Broker (MQTT2_SERVER) steht (entsprechende Topics sind vorhanden und werden aktualisiert? Das Gerät reagiert auf ein ggf. benötigten publish command?, der Test mit dem MQTT Explorer funktioniert?
5. Wenn alles funktioniert und autocreate aktiv (Standard) sollte bereits ein Device im Raum MQTT2_Devices angelegt sein. Diesem MQTT2_DEVICE wurde das Bridge template zugeordnet und das Attribut bridgeRegexpr setzt?
Z.B.:

Code Auswählen Erweitern


set <Name des MQTT2_DEVICE> attrTemplate L_01_zigbee2mqtt_bridge
attr <Name des MQTT2_DEVICE> bridgeRegexp zigbee2mqtt/([A-Za-z0-9]*)[/]?.*:.* "zigbee_$1"

6. Wenn bis hier alles funktioniert, sollte noch in der configuration.yaml  "permit_join: false" und "homeassistant: false" setzt werden.

Wo hängst du?

lg, Gernot

[accessburn]

Na geil ...
da muss ich mich erst mal durcharbeiten... Denn das hab ich nirgends gefunden.

Hast du da ne Quelle von?

[stratege-0815]

Na geil ...
da muss ich mich erst mal durcharbeiten... Denn das hab ich nirgends gefunden.

Hast du da ne Quelle von?

Hast du das am Ende zum laufen gebraucht? ich habe im Prinzip genau das gleiche vor, es geht um Tradfri Bewegungsmelder. Alternativ wird es vielleicht ein Xiaomi Bewegungsmelder.

[CatWeazle]

Hi Leutz,

warum ist die ZigBee Einbindung in FHEM nur so Kompliziert / Aufwendig ?!?!
Ich habe mich auch vergeblich durch die Anleitung gearbeitet, bin froh, dass ich zuvor ein IMG der SD erstellt hatte, so konnte ich wenigstens zurück.

Ein Bekannter nutzt HomeAssist ist total davon angetan, da soll es total simpel sein ZigBee mit einem CC2531 einzubinden.
Ich habe auf meinem Test-Raspi mal ioBroker installiert, ja geht es noch, mit wenigen Klicks war der CC2531 erkannt eingebunden und das erste Gerät gepaart.
Ohne das ich eine Zeile Text eingeben musste!
Das ist ja mal vorbildlich.

Vielleicht lasse ich die ZigBee Sachen einfach auf dem ioBroker weiter Laufen, es gibt ja eine Schnittstelle, ioBroker <-> FHEM
Und ioBroker kann auf dem gleichen Raspi installiert werden auf dem FHEM schon läuft.

Ich schlaf mal drüber .....

Grüße
Mike

[ch.eick]

warum ist die ZigBee Einbindung in FHEM nur so Kompliziert / Aufwendig ?!?!

Ich habe den Stick mit dem Docker zigbee2mqtt Image ohne Problem erkannt.
Im Docker FHEM muss er natürlich vorher als USB Port gesperrt werden.

Mein Problem ist nur leider, dass ich alles wieder neu anlernen muss und das ich es nicht schaffe die alte Konfiguration einfach zu übernehmen

Gruß
   Christian

[CatWeazle]

Hi Christian,

das ist mir alles viel zu aufwändig.
Würde die Einbindung in FHEM genauso einfach gehen wie die eines NanoCul für HM oder Signalduino, wäre alles gut.

Aber so .... och nee, ich fahre ZigBee über den ioBroker parallel, und der kann sich mit FHEM verständigen, zumal der ioBroker noch weitere interessante gimmigs hat ... Das WebFrontend ist nett und einfacher als bei FHEM zu editieren, kann aber FHEM bedienen .... da geht was ...

Muss ich mir weiter ansehen, gefällt mir aber schon ....

[Müller]

Ich kann es empfehlen über MQTT2_SERVER https://wiki.fhem.de/wiki/Zigbee2mqtt und zigbee2mqtt https://www.zigbee2mqtt.io/ zu gehen.

Manche Devices werden erst in Fhem "erscheinen" wenn sie geschaltet werden. Hierkann ich das frontend von zigbee2mqtt2 empfehlen https://www.zigbee2mqtt.io/information/frontend.html

Grüße & viel Erfolg

Jochen

[ch.eick]

Ich kann es empfehlen über MQTT2_SERVER https://wiki.fhem.de/wiki/Zigbee2mqtt und zigbee2mqtt https://www.zigbee2mqtt.io/ zu gehen.

Manche Devices werden erst in Fhem "erscheinen" wenn sie geschaltet werden. Hierkann ich das frontend von zigbee2mqtt2 empfehlen https://www.zigbee2mqtt.io/information/frontend.html

Vielen Dank Jochen,
das Frontend kannte ich noch gar nicht. Ich habe den Port im Docker konfiguriert und im configuration.yaml das fontend eingetragen. Nach einem Container Neustart  konnte ich mich verbinden, jedoch wird noch nichts von der Konfiguration angezeigt. Da such ich dann mal weiter.

Gruß
   Christian

[ch.eick]

Sooo, ich habe mir mal wieder ein Herz genommen und versuche auch Zigbee ans laufen zu bekommen.

Jede Hilfe wäre willkommen

Zur Information, die jetzige Konfiguration mit Docker hat nach dem Umzug noch nicht funktioniert. Ich habe versucht das alte Umfeld in den Container zu übernehmen.

Status:
- Der Container erreicht den CC2531 Stick
- Die Verbindung vom Container auf Port 1883 scheint zu klappen
- Die Gruppen waren der letzte Test bevor der Wechsel zum Docker kam. Ob das richtig ist weiß ich nicht

- Im Frontend von zigbee2mqtt wird mir nichts angezeigt.
  Mit "Download state" bekomme ich ein .json File

Wenn ich im FHEM eins der Lampen devices auf On klicke habe ich folgende Meldungen im Log

Code Auswählen Erweitern


2021.03.01 13:23:53.653 3: MQTT2_DEVICE set MQTT2_zigbee_0x90fd9ffffed8dee7 off
2021.03.01 13:23:53.654 5: MQTT2_FHEM_Server: PUBLISH zigbee2mqtt/0x90fd9ffffed8dee7/set {"state":"OFF"}
2021.03.01 13:23:53.666 5:   MQTT2_FHEM_Server_172.18.0.3_37338 zigbee_pi => zigbee2mqtt/0x90fd9ffffed8dee7/set:{"state":"OFF"}
2021.03.01 13:23:53.666 5: out: PUBLISH: 03(0)"zigbee2mqtt/0x90fd9ffffed8dee7/set{"state":"OFF"}
2021.03.01 13:23:54.718 5: in:  PUBLISH: 0(254)(3)(0)(22)zigbee2mqtt/bridge/log{"message":"Publish 'set' 'state' to '0x90fd9ffffed8dee7' failed: 'Error: Command 0x90fd9ffffed8dee7/1 genOnOff.on({}, {\"timeout\":10000,\"disableResponse\":false,\"disableRecovery\":false,\"disableDefaultResponse\":false,\"direction\":0,\"srcEndpoint\":null,\"reservedBits\":0,\"manufacturerCode\":null,\"transactionSequenceNumber\":null}) failed (Data request failed with error: 'No network route' (205))'","meta":{"friendly_name":"0x90fd9ffffed8dee7"},"type":"zigbee_publish_error"}
2021.03.01 13:23:54.719 4:   MQTT2_FHEM_Server_172.18.0.3_37338 zigbee_pi PUBLISH zigbee2mqtt/bridge/log:{"message":"Publish 'set' 'state' to '0x90fd9ffffed8dee7' failed: 'Error: Command 0x90fd9ffffed8dee7/1 genOnOff.on({}, {\"timeout\":10000,\"disableResponse\":false,\"disableRecovery\":false,\"disableDefaultResponse\":false,\"direction\":0,\"srcEndpoint\":null,\"reservedBits\":0,\"manufacturerCode\":null,\"transactionSequenceNumber\":null}) failed (Data request failed with error: 'No network route' (205))'","meta":{"friendly_name":"0x90fd9ffffed8dee7"},"type":"zigbee_publish_error"}
2021.03.01 13:23:54.760 5: MQTT2_FHEM_Server: dispatch autocreate=simple\000zigbee_pi\000zigbee2mqtt/bridge/log\000{"message":"Publish 'set' 'state' to '0x90fd9ffffed8dee7' failed: 'Error: Command 0x90fd9ffffed8dee7/1 genOnOff.on({}, {\\"timeout\\":10000,\\"disableResponse\\":false,\\"disableRecovery\\":false,\\"disableDefaultResponse\\":false,\\"direction\\":0,\\"srcEndpoint\\":null,\\"reservedBits\\":0,\\"manufacturerCode\\":null,\\"transactionSequenceNumber\\":null}) failed (Data request failed with error: 'No network route' (205))'","meta":{"friendly_name":"0x90fd9ffffed8dee7"},"type":"zigbee_publish_error"}
2021.03.01 13:23:54.761 4: MQTT2_DEVICE_Parse: MQTT2_zigbee_pi zigbee2mqtt/bridge/log => log
2021.03.01 13:24:00.016 2: PV_1_Speicher_1_ExternControl: get PV_1_Speicher_1 BatteryInformation: BatteryInformation requested, watch readings
2021.03.01 13:24:00.042 2: PV_1_Speicher_1_ExternControl: get PV_1_Speicher_1 StatisticInformation: StatisticInformation requested, watch readings
2021.03.01 13:24:15.040 5: in:  PUBLISH: 0(255)(3)(0)(22)zigbee2mqtt/bridge/log{"message":"Publish 'set' 'state' to '0x90fd9ffffed8dee7' failed: 'Error: Command 0x90fd9ffffed8dee7/1 genOnOff.off({}, {\"timeout\":10000,\"disableResponse\":false,\"disableRecovery\":false,\"disableDefaultResponse\":false,\"direction\":0,\"srcEndpoint\":null,\"reservedBits\":0,\"manufacturerCode\":null,\"transactionSequenceNumber\":null}) failed (Data request failed with error: 'No network route' (205))'","meta":{"friendly_name":"0x90fd9ffffed8dee7"},"type":"zigbee_publish_error"}
2021.03.01 13:24:15.040 4:   MQTT2_FHEM_Server_172.18.0.3_37338 zigbee_pi PUBLISH zigbee2mqtt/bridge/log:{"message":"Publish 'set' 'state' to '0x90fd9ffffed8dee7' failed: 'Error: Command 0x90fd9ffffed8dee7/1 genOnOff.off({}, {\"timeout\":10000,\"disableResponse\":false,\"disableRecovery\":false,\"disableDefaultResponse\":false,\"direction\":0,\"srcEndpoint\":null,\"reservedBits\":0,\"manufacturerCode\":null,\"transactionSequenceNumber\":null}) failed (Data request failed with error: 'No network route' (205))'","meta":{"friendly_name":"0x90fd9ffffed8dee7"},"type":"zigbee_publish_error"}
2021.03.01 13:24:15.077 5: MQTT2_FHEM_Server: dispatch autocreate=simple\000zigbee_pi\000zigbee2mqtt/bridge/log\000{"message":"Publish 'set' 'state' to '0x90fd9ffffed8dee7' failed: 'Error: Command 0x90fd9ffffed8dee7/1 genOnOff.off({}, {\\"timeout\\":10000,\\"disableResponse\\":false,\\"disableRecovery\\":false,\\"disableDefaultResponse\\":false,\\"direction\\":0,\\"srcEndpoint\\":null,\\"reservedBits\\":0,\\"manufacturerCode\\":null,\\"transactionSequenceNumber\\":null}) failed (Data request failed with error: 'No network route' (205))'","meta":{"friendly_name":"0x90fd9ffffed8dee7"},"type":"zigbee_publish_error"}
2021.03.01 13:24:15.078 4: MQTT2_DEVICE_Parse: MQTT2_zigbee_pi zigbee2mqtt/bridge/log => log
2021.03.01 13:25:15.043 5: in:  PINGREQ: (192)(0)
2021.03.01 13:25:15.043 4:   MQTT2_FHEM_Server_172.18.0.3_37338 zigbee_pi PINGREQ
2021.03.01 13:25:15.043 5: out: PINGRESP: (208)(0)



zigbee2mqtt Log

Code Auswählen Erweitern


info  2021-03-01 13:07:23: Logging to console and directory: '/app/data/log/2021-03-01.13-07-22' filename: log.txt
info  2021-03-01 13:07:23: Starting Zigbee2MQTT version 1.16.1 (commit #6b32f30)
info  2021-03-01 13:07:23: Starting zigbee-herdsman...
info  2021-03-01 13:07:25: zigbee-herdsman started
info  2021-03-01 13:07:25: Coordinator firmware version: '{"meta":{"maintrel":3,"majorrel":2,"minorrel":6,"product":0,"revision":20190608,"transportrev":2},"type":"zStack12"}'
info  2021-03-01 13:07:25: Currently 13 devices are joined:
info  2021-03-01 13:07:25: 0x90fd9ffffee7e93a (0x90fd9ffffee7e93a): E1524/E1810 - IKEA TRADFRI remote control (EndDevice)
info  2021-03-01 13:07:25: 0x90fd9ffffe9e4880 (0x90fd9ffffe9e4880): E1524/E1810 - IKEA TRADFRI remote control (EndDevice)
info  2021-03-01 13:07:25: 0x90fd9ffffed8dee7 (0x90fd9ffffed8dee7): L1528 - IKEA FLOALT LED light panel, dimmable, white spectrum (30x90 cm) (Router)
info  2021-03-01 13:07:25: 0x90fd9ffffee0cb7b (0x90fd9ffffee0cb7b): L1528 - IKEA FLOALT LED light panel, dimmable, white spectrum (30x90 cm) (Router)
info  2021-03-01 13:07:25: 0x086bd7fffe4bf85d (0x086bd7fffe4bf85d): LED1649C5 - IKEA TRADFRI LED bulb E12/E14/E17 400 lumen, dimmable warm white, chandelier opal (Router)
info  2021-03-01 13:07:25: 0xd0cf5efffeda5ead (0xd0cf5efffeda5ead): LED1649C5 - IKEA TRADFRI LED bulb E12/E14/E17 400 lumen, dimmable warm white, chandelier opal (Router)
info  2021-03-01 13:07:25: 0x086bd7fffe218062 (0x086bd7fffe218062): LED1649C5 - IKEA TRADFRI LED bulb E12/E14/E17 400 lumen, dimmable warm white, chandelier opal (Router)
info  2021-03-01 13:07:25: 0x086bd7fffe616d8c (0x086bd7fffe616d8c): LED1649C5 - IKEA TRADFRI LED bulb E12/E14/E17 400 lumen, dimmable warm white, chandelier opal (Router)
info  2021-03-01 13:07:25: 0x086bd7fffe53e6ee (0x086bd7fffe53e6ee): LED1649C5 - IKEA TRADFRI LED bulb E12/E14/E17 400 lumen, dimmable warm white, chandelier opal (Router)
info  2021-03-01 13:07:25: 0x086bd7fffe228986 (0x086bd7fffe228986): LED1649C5 - IKEA TRADFRI LED bulb E12/E14/E17 400 lumen, dimmable warm white, chandelier opal (Router)
info  2021-03-01 13:07:25: 0x086bd7fffe5ccc0b (0x086bd7fffe5ccc0b): LED1649C5 - IKEA TRADFRI LED bulb E12/E14/E17 400 lumen, dimmable warm white, chandelier opal (Router)
info  2021-03-01 13:07:25: 0x086bd7fffe6177c7 (0x086bd7fffe6177c7): LED1649C5 - IKEA TRADFRI LED bulb E12/E14/E17 400 lumen, dimmable warm white, chandelier opal (Router)
info  2021-03-01 13:07:25: 0x086bd7fffe5c96dc (0x086bd7fffe5c96dc): LED1649C5 - IKEA TRADFRI LED bulb E12/E14/E17 400 lumen, dimmable warm white, chandelier opal (Router)
warn  2021-03-01 13:07:25: `permit_join` set to  `true` in configuration.yaml.
warn  2021-03-01 13:07:25: Allowing new devices to join.
warn  2021-03-01 13:07:25: Set `permit_join` to `false` once you joined all devices.
info  2021-03-01 13:07:25: Zigbee: allowing new devices to join.
info  2021-03-01 13:07:25: Configuring '0x90fd9ffffee7e93a'
info  2021-03-01 13:07:26: Connecting to MQTT server at mqtt://192.168.178.40:1883
info  2021-03-01 13:07:26: Connected to MQTT server
info  2021-03-01 13:07:26: MQTT publish: topic 'zigbee2mqtt/bridge/state', payload 'online'
info  2021-03-01 13:07:26: MQTT publish: topic 'zigbee2mqtt/bridge/config', payload '{"commit":"6b32f30","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.16.1"}'
error 2021-03-01 13:07:35: Failed to configure '0x90fd9ffffee7e93a', attempt 1 (Error: Bind 0x90fd9ffffee7e93a/1 genOnOff from '901' failed (AREQ - ZDO - bindRsp after 10000ms)
    at Timeout._onTimeout (/app/node_modules/zigbee-herdsman/dist/utils/waitress.js:46:35)
    at listOnTimeout (internal/timers.js:554:17)
    at processTimers (internal/timers.js:497:7))
info  2021-03-01 13:07:35: Configuring '0x90fd9ffffe9e4880'
error 2021-03-01 13:07:45: Failed to configure '0x90fd9ffffe9e4880', attempt 1 (Error: Bind 0x90fd9ffffe9e4880/1 genOnOff from '901' failed (AREQ - ZDO - bindRsp after 10000ms)
    at Timeout._onTimeout (/app/node_modules/zigbee-herdsman/dist/utils/waitress.js:46:35)
    at listOnTimeout (internal/timers.js:554:17)
    at processTimers (internal/timers.js:497:7))
info  2021-03-01 13:07:45: Adding '0x086bd7fffe218062' to group 'WzTisch'
info  2021-03-01 13:07:45: Adding '0x086bd7fffe5c96dc' to group 'WzTisch'
info  2021-03-01 13:07:45: Adding '0x086bd7fffe228986' to group 'WzTisch'
info  2021-03-01 13:07:45: Adding '0x086bd7fffe4bf85d' to group 'WzTisch'
info  2021-03-01 13:07:45: Adding '0x086bd7fffe53e6ee' to group 'WzTisch'
info  2021-03-01 13:07:45: Adding '0x086bd7fffe5ccc0b' to group 'WzTisch'
info  2021-03-01 13:07:45: Adding '0x086bd7fffe616d8c' to group 'WzTisch'
info  2021-03-01 13:07:45: Adding '0x086bd7fffe6177c7' to group 'WzTisch'
info  2021-03-01 13:07:45: Adding '0xd0cf5efffeda5ead' to group 'WzTisch'
info  2021-03-01 13:07:45: Adding '0x90fd9ffffee0cb7b' to group 'KuSchrank'
info  2021-03-01 13:07:45: Adding '0x90fd9ffffed8dee7' to group 'KuSchrank'
info  2021-03-01 13:07:45: Started frontend on port 8080
error 2021-03-01 13:08:05: Failed to add '0x086bd7fffe218062' from 'WzTisch'
error 2021-03-01 13:08:06: Failed to add '0x086bd7fffe5c96dc' from 'WzTisch'
error 2021-03-01 13:08:25: Failed to add '0x086bd7fffe228986' from 'WzTisch'
error 2021-03-01 13:08:26: Failed to add '0x086bd7fffe4bf85d' from 'WzTisch'
error 2021-03-01 13:08:45: Failed to add '0x086bd7fffe5ccc0b' from 'WzTisch'
error 2021-03-01 13:08:45: Failed to add '0x086bd7fffe53e6ee' from 'WzTisch'
error 2021-03-01 13:09:05: Failed to add '0x086bd7fffe6177c7' from 'WzTisch'
error 2021-03-01 13:09:05: Failed to add '0x086bd7fffe616d8c' from 'WzTisch'
error 2021-03-01 13:09:25: Failed to add '0xd0cf5efffeda5ead' from 'WzTisch'
error 2021-03-01 13:09:25: Failed to add '0x90fd9ffffee0cb7b' from 'KuSchrank'
error 2021-03-01 13:09:46: Failed to add '0x90fd9ffffed8dee7' from 'KuSchrank'

error 2021-03-01 13:23:54: Publish 'set' 'state' to '0x90fd9ffffed8dee7' failed: 'Error: Command 0x90fd9ffffed8dee7/1 genOnOff.on({}, {"timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":false,"direction":0,"srcEndpoint":null,"reservedBits":0,"manufacturerCode":null,"transactionSequenceNumber":null}) failed (Data request failed with error: 'No network route' (205))'
info  2021-03-01 13:23:54: MQTT publish: topic 'zigbee2mqtt/bridge/log', payload '{"message":"Publish 'set' 'state' to '0x90fd9ffffed8dee7' failed: 'Error: Command 0x90fd9ffffed8dee7/1 genOnOff.on({}, {\"timeout\":10000,\"disableResponse\":false,\"disableRecovery\":false,\"disableDefaultResponse\":false,\"direction\":0,\"srcEndpoint\":null,\"reservedBits\":0,\"manufacturerCode\":null,\"transactionSequenceNumber\":null}) failed (Data request failed with error: 'No network route' (205))'","meta":{"friendly_name":"0x90fd9ffffed8dee7"},"type":"zigbee_publish_error"}'
error 2021-03-01 13:24:15: Publish 'set' 'state' to '0x90fd9ffffed8dee7' failed: 'Error: Command 0x90fd9ffffed8dee7/1 genOnOff.off({}, {"timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":false,"direction":0,"srcEndpoint":null,"reservedBits":0,"manufacturerCode":null,"transactionSequenceNumber":null}) failed (Data request failed with error: 'No network route' (205))'
info  2021-03-01 13:24:15: MQTT publish: topic 'zigbee2mqtt/bridge/log', payload '{"message":"Publish 'set' 'state' to '0x90fd9ffffed8dee7' failed: 'Error: Command 0x90fd9ffffed8dee7/1 genOnOff.off({}, {\"timeout\":10000,\"disableResponse\":false,\"disableRecovery\":false,\"disableDefaultResponse\":false,\"direction\":0,\"srcEndpoint\":null,\"reservedBits\":0,\"manufacturerCode\":null,\"transactionSequenceNumber\":null}) failed (Data request failed with error: 'No network route' (205))'","meta":{"friendly_name":"0x90fd9ffffed8dee7"},"type":"zigbee_publish_error"}


mqtt2 Server

Code Auswählen Erweitern


Internals:
   CONNECTS   1
   Clients    :MQTT2_DEVICE:MQTT_GENERIC_BRIDGE:
   ClientsKeepOrder 1
   DEF        1883 global
   FD         21
   FUUID      5d751c78-f33f-81e9-291a-1d62334721ed96af
   FVERSION   00_MQTT2_SERVER.pm:0.238430/2021-02-27
   NAME       MQTT2_FHEM_Server
   NR         371
   PORT       1883
   STATE      Initialized
   TYPE       MQTT2_SERVER
   MatchList:
     1:MQTT2_DEVICE ^.
     2:MQTT_GENERIC_BRIDGE ^.
   READINGS:
     2021-03-01 13:07:26   RETAIN          {"zigbee2mqtt/bridge/config":"{\u0022commit\u0022:\u00226b32f30\u0022,\u0022coordinator\u0022:{\u0022meta\u0022:{\u0022maintrel\u0022:3,\u0022majorrel\u0022:2,\u0022minorrel\u0022:6,\u0022product\u0022:0,\u0022revision\u0022:20190608,\u0022transportrev\u0022:2},\u0022type\u0022:\u0022zStack12\u0022},\u0022log_level\u0022:\u0022info\u0022,\u0022network\u0022:{\u0022channel\u0022:11,\u0022extendedPanID\u0022:\u00220xdddddddddddddddd\u0022,\u0022panID\u0022:6754},\u0022permit_join\u0022:true,\u0022version\u0022:\u00221.16.1\u0022}","zigbee2mqtt/bridge/state":"online"}
     2021-03-01 13:07:26   nrclients       1
     2021-03-01 12:31:05   state           Initialized
   clients:
     MQTT2_FHEM_Server_172.18.0.3_37338 1
   retain:
     zigbee2mqtt/bridge/config:
       ts         1614600446.51008
       val        {"commit":"6b32f30","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.16.1"}
     zigbee2mqtt/bridge/state:
       ts         1614600446.36484
       val        online
Attributes:
   DbLogExclude .*
   alias      MQTT2_FHEM_Server
   autocreate simple
   disable    0
   room       MQTT2
   verbose    5


mqtt2 Device

Code Auswählen Erweitern


Internals:
   CID        zigbee_pi
   DEF        zigbee_pi
   DEVICETOPIC MQTT2_zigbee_pi
   FUUID      5d763393-f33f-81e9-b187-fa1c3d1eae39d1bd
   FVERSION   10_MQTT2_DEVICE.pm:0.238430/2021-02-27
   IODev      MQTT2_FHEM_Server
   LASTInputDev MQTT2_FHEM_Server
   MQTT2_FHEM_Server_MSGCNT 2
   MQTT2_FHEM_Server_TIME 2021-03-01 13:07:26
   MSGCNT     2
   NAME       MQTT2_zigbee_pi
   NR         372
   STATE      online
   TYPE       MQTT2_DEVICE
   READINGS:
     2021-03-01 13:07:26   commit          6b32f30
     2019-12-21 14:33:40   coordinator     20190608
     2021-03-01 13:07:26   coordinator_meta_maintrel 3
     2021-03-01 13:07:26   coordinator_meta_majorrel 2
     2021-03-01 13:07:26   coordinator_meta_minorrel 6
     2021-03-01 13:07:26   coordinator_meta_product 0
     2021-03-01 13:07:26   coordinator_meta_revision 20190608
     2021-03-01 13:07:26   coordinator_meta_transportrev 2
     2021-03-01 13:07:26   coordinator_type zStack12
     2019-11-30 14:42:13   devices         {"type":"devices","message":[{"ieeeAddr":"0x00124b0018e1e960","type":"Coordinator"},{"ieeeAddr":"0x90fd9ffffee7e93a","type":"EndDevice","model":"E1524","friendly_name":"0x90fd9ffffee7e93a","nwkAddr":13378,"manufId":4476,"manufName":"IKEA of Sweden","powerSource":"Battery","modelId":"TRADFRI remote control","hwVersion":1,"swBuildId":"1.2.214","dateCode":"20170302"},{"ieeeAddr":"0x90fd9ffffe9e4880","type":"EndDevice","model":"E1524","friendly_name":"0x90fd9ffffe9e4880","nwkAddr":33498,"manufId":4476,"manufName":"IKEA of Sweden","powerSource":"Battery","modelId":"TRADFRI remote control","hwVersion":1,"swBuildId":"1.2.214","dateCode":"20170302"},{"ieeeAddr":"0x90fd9ffffed8dee7","type":"Router","model":"L1528","friendly_name":"0x90fd9ffffed8dee7","nwkAddr":14042,"manufId":4476,"manufName":"IKEA of Sweden","powerSource":"Mains (single phase)","modelId":"FLOALT panel WS 30x90","hwVersion":1,"swBuildId":"1.2.217","dateCode":"20170331"},{"ieeeAddr":"0x90fd9ffffee0cb7b","type":"Router","model":"L1528","friendly_name":"0x90fd9ffffee0cb7b","nwkAddr":59017,"manufId":4476,"manufName":"IKEA of Sweden","powerSource":"Mains (single phase)","modelId":"FLOALT panel WS 30x90","hwVersion":1,"swBuildId":"1.2.217","dateCode":"20170331"},{"ieeeAddr":"0x086bd7fffe4bf85d","type":"Router","model":"LED1649C5","friendly_name":"0x086bd7fffe4bf85d","nwkAddr":11270,"manufId":4476,"manufName":"IKEA of Sweden","powerSource":"Mains (single phase)","modelId":"TRADFRI bulb E14 W op/ch 400lm","hwVersion":1,"swBuildId":"1.2.214","dateCode":"20170302"},{"ieeeAddr":"0xd0cf5efffeda5ead","type":"Router","model":"LED1649C5","friendly_name":"0xd0cf5efffeda5ead","nwkAddr":8250,"manufId":4476,"manufName":"IKEA of Sweden","powerSource":"Mains (single phase)","modelId":"TRADFRI bulb E14 W op/ch 400lm","hwVersion":1,"swBuildId":"1.2.214","dateCode":"20170302"},{"ieeeAddr":"0x086bd7fffe218062","type":"Router","model":"LED1649C5","friendly_name":"0x086bd7fffe218062","nwkAddr":12799,"manufId":4476,"manufName":"IKEA of Sweden","powerSource":"Mains (single phase)","modelId":"TRADFRI bulb E14 W op/ch 400lm","hwVersion":1,"swBuildId":"1.2.214","dateCode":"20170302"},{"ieeeAddr":"0x086bd7fffe616d8c","type":"Router","model":"LED1649C5","friendly_name":"0x086bd7fffe616d8c","nwkAddr":38328,"manufId":4476,"manufName":"IKEA of Sweden","powerSource":"Mains (single phase)","modelId":"TRADFRI bulb E14 W op/ch 400lm","hwVersion":1,"swBuildId":"1.2.214","dateCode":"20170302"},{"ieeeAddr":"0x086bd7fffe53e6ee","type":"Router","model":"LED1649C5","friendly_name":"0x086bd7fffe53e6ee","nwkAddr":13952,"manufId":4476,"manufName":"IKEA of Sweden","powerSource":"Mains (single phase)","modelId":"TRADFRI bulb E14 W op/ch 400lm","hwVersion":1,"swBuildId":"1.2.214","dateCode":"20170302"},{"ieeeAddr":"0x086bd7fffe228986","type":"Router","model":"LED1649C5","friendly_name":"0x086bd7fffe228986","nwkAddr":36500,"manufId":4476,"manufName":"IKEA of Sweden","powerSource":"Mains (single phase)","modelId":"TRADFRI bulb E14 W op/ch 400lm","hwVersion":1,"swBuildId":"1.2.214","dateCode":"20170302"},{"ieeeAddr":"0x086bd7fffe5ccc0b","type":"Router","model":"LED1649C5","friendly_name":"0x086bd7fffe5ccc0b","nwkAddr":5806,"manufId":4476,"manufName":"IKEA of Sweden","powerSource":"Mains (single phase)","modelId":"TRADFRI bulb E14 W op/ch 400lm","hwVersion":1,"swBuildId":"1.2.214","dateCode":"20170302"},{"ieeeAddr":"0x086bd7fffe6177c7","type":"Router","model":"LED1649C5","friendly_name":"0x086bd7fffe6177c7","nwkAddr":22557,"manufId":4476,"manufName":"IKEA of Sweden","powerSource":"Mains (single phase)","modelId":"TRADFRI bulb E14 W op/ch 400lm","hwVersion":1,"swBuildId":"1.2.214","dateCode":"20170302"},{"ieeeAddr":"0x086bd7fffe5c96dc","type":"Router","model":"LED1649C5","friendly_name":"0x086bd7fffe5c96dc","nwkAddr":62517,"manufId":4476,"manufName":"IKEA of Sweden","powerSource":"Mains (single phase)","modelId":"TRADFRI bulb E14 W op/ch 400lm","hwVersion":1,"swBuildId":"1.2.214","dateCode":"20170302"}]}
     2019-11-11 13:54:55   graphviz        digraph G {
node[shape=record];
  "0x00124b0018e1e960" [style="bold, filled", fillcolor="#e04e5d", fontcolor="#ffffff", label="{0x00124b0018e1e960|0x0 |No model information available|online (2019-11-11T13:54:55+01:00)}"];
  "0x90fd9ffffee7e93a" [style="rounded, dashed, filled", fillcolor="#fff8ce", fontcolor="#000000", label="{0x90fd9ffffee7e93a|0x3442 |IKEA TRADFRI remote control (E1524)|offline (unknown)}"];
  "0x90fd9ffffee7e93a" -> "0x00124b0018e1e960" [penwidth=1, weight=0, color="#994444", label="170"]
}
     2020-11-09 18:05:41   log             {"type":"device_announced","message":"announce","meta":{"friendly_name":"0x086bd7fffe4bf85d"}}
     2021-03-01 13:07:26   log_level       info
     2021-03-01 13:07:26   network_channel 11
     2021-03-01 13:07:26   network_extendedPanID 0xdddddddddddddddd
     2021-03-01 13:07:26   network_panID   6754
     2021-03-01 13:07:26   permit_join     true
     2019-11-11 13:56:30   raw             {"nodes":[{"ieeeAddr":"0x00124b0018e1e960","friendlyName":"0x00124b0018e1e960","type":"Coordinator","nwkAddr":0,"status":"online","scanfailed":[]},{"ieeeAddr":"0x90fd9ffffee7e93a","friendlyName":"0x90fd9ffffee7e93a","type":"EndDevice","nwkAddr":13378,"manufName":"IKEA of Sweden","modelId":"TRADFRI remote control","status":"offline","scanfailed":[]}],"links":[{"sourceIeeeAddr":"0x90fd9ffffee7e93a","targetIeeeAddr":"0x00124b0018e1e960","sourceNwkAddr":13378,"lqi":170,"depth":1,"relationship":1,"routes":[]}]}
     2021-03-01 13:07:26   state           online
     2020-11-10 11:01:40   subscriptions   zigbee2mqtt/+/+/+/+/+/+/+/+/+/+/+/+/+/+/+/+/+/+/+/get zigbee2mqtt/+/+/+/+/+/+/+/+/+/+/+/+/+/+/+/+/+/+/+/get/+ zigbee2mqtt/+/+/+/+/+/+/+/+/+/+/+/+/+/+/+/+/+/+/+/set zigbee2mqtt/+/+/+/+/+/+/+/+/+/+/+/+/+/+/+/+/+/+/+/set/+ zigbee2mqtt/+/+/+/+/+/+/+/+/+/+/+/+/+/+/+/+/+/+/get zigbee2mqtt/+/+/+/+/+/+/+/+/+/+/+/+/+/+/+/+/+/+/get/+ zigbee2mqtt/+/+/+/+/+/+/+/+/+/+/+/+/+/+/+/+/+/+/set zigbee2mqtt/+/+/+/+/+/+/+/+/+/+/+/+/+/+/+/+/+/+/set/+ zigbee2mqtt/+/+/+/+/+/+/+/+/+/+/+/+/+/+/+/+/+/get zigbee2mqtt/+/+/+/+/+/+/+/+/+/+/+/+/+/+/+/+/+/get/+ zigbee2mqtt/+/+/+/+/+/+/+/+/+/+/+/+/+/+/+/+/+/set zigbee2mqtt/+/+/+/+/+/+/+/+/+/+/+/+/+/+/+/+/+/set/+ zigbee2mqtt/+/+/+/+/+/+/+/+/+/+/+/+/+/+/+/+/get zigbee2mqtt/+/+/+/+/+/+/+/+/+/+/+/+/+/+/+/+/get/+ zigbee2mqtt/+/+/+/+/+/+/+/+/+/+/+/+/+/+/+/+/set zigbee2mqtt/+/+/+/+/+/+/+/+/+/+/+/+/+/+/+/+/set/+ zigbee2mqtt/+/+/+/+/+/+/+/+/+/+/+/+/+/+/+/get zigbee2mqtt/+/+/+/+/+/+/+/+/+/+/+/+/+/+/+/get/+ zigbee2mqtt/+/+/+/+/+/+/+/+/+/+/+/+/+/+/+/set zigbee2mqtt/+/+/+/+/+/+/+/+/+/+/+/+/+/+/+/set/+ zigbee2mqtt/+/+/+/+/+/+/+/+/+/+/+/+/+/+/get zigbee2mqtt/+/+/+/+/+/+/+/+/+/+/+/+/+/+/get/+ zigbee2mqtt/+/+/+/+/+/+/+/+/+/+/+/+/+/+/set zigbee2mqtt/+/+/+/+/+/+/+/+/+/+/+/+/+/+/set/+ zigbee2mqtt/+/+/+/+/+/+/+/+/+/+/+/+/+/get zigbee2mqtt/+/+/+/+/+/+/+/+/+/+/+/+/+/get/+ zigbee2mqtt/+/+/+/+/+/+/+/+/+/+/+/+/+/set zigbee2mqtt/+/+/+/+/+/+/+/+/+/+/+/+/+/set/+ zigbee2mqtt/+/+/+/+/+/+/+/+/+/+/+/+/get zigbee2mqtt/+/+/+/+/+/+/+/+/+/+/+/+/get/+ zigbee2mqtt/+/+/+/+/+/+/+/+/+/+/+/+/set zigbee2mqtt/+/+/+/+/+/+/+/+/+/+/+/+/set/+ zigbee2mqtt/+/+/+/+/+/+/+/+/+/+/+/get zigbee2mqtt/+/+/+/+/+/+/+/+/+/+/+/get/+ zigbee2mqtt/+/+/+/+/+/+/+/+/+/+/+/set zigbee2mqtt/+/+/+/+/+/+/+/+/+/+/+/set/+ zigbee2mqtt/+/+/+/+/+/+/+/+/+/+/get zigbee2mqtt/+/+/+/+/+/+/+/+/+/+/get/+ zigbee2mqtt/+/+/+/+/+/+/+/+/+/+/set zigbee2mqtt/+/+/+/+/+/+/+/+/+/+/set/+ zigbee2mqtt/+/+/+/+/+/+/+/+/+/get zigbee2mqtt/+/+/+/+/+/+/+/+/+/get/+ zigbee2mqtt/+/+/+/+/+/+/+/+/+/set zigbee2mqtt/+/+/+/+/+/+/+/+/+/set/+ zigbee2mqtt/+/+/+/+/+/+/+/+/get zigbee2mqtt/+/+/+/+/+/+/+/+/get/+ zigbee2mqtt/+/+/+/+/+/+/+/+/set zigbee2mqtt/+/+/+/+/+/+/+/+/set/+ zigbee2mqtt/+/+/+/+/+/+/+/get zigbee2mqtt/+/+/+/+/+/+/+/get/+ zigbee2mqtt/+/+/+/+/+/+/+/set zigbee2mqtt/+/+/+/+/+/+/+/set/+ zigbee2mqtt/+/+/+/+/+/+/get zigbee2mqtt/+/+/+/+/+/+/get/+ zigbee2mqtt/+/+/+/+/+/+/set zigbee2mqtt/+/+/+/+/+/+/set/+ zigbee2mqtt/+/+/+/+/+/get zigbee2mqtt/+/+/+/+/+/get/+ zigbee2mqtt/+/+/+/+/+/set zigbee2mqtt/+/+/+/+/+/set/+ zigbee2mqtt/+/+/+/+/get zigbee2mqtt/+/+/+/+/get/+ zigbee2mqtt/+/+/+/+/set zigbee2mqtt/+/+/+/+/set/+ zigbee2mqtt/+/+/+/get zigbee2mqtt/+/+/+/get/+ zigbee2mqtt/+/+/+/set zigbee2mqtt/+/+/+/set/+ zigbee2mqtt/+/+/get zigbee2mqtt/+/+/get/+ zigbee2mqtt/+/+/set zigbee2mqtt/+/+/set/+ zigbee2mqtt/+/get zigbee2mqtt/+/get/+ zigbee2mqtt/+/set zigbee2mqtt/+/set/+ zigbee2mqtt/bridge/bind/# zigbee2mqtt/bridge/config/+ zigbee2mqtt/bridge/config/+/+ zigbee2mqtt/bridge/configure zigbee2mqtt/bridge/device/+/+/+/+/+/+/+/+/+/+/+/+/+/+/+/+/+/+/+/get_group_membership zigbee2mqtt/bridge/device/+/+/+/+/+/+/+/+/+/+/+/+/+/+/+/+/+/+/get_group_membership zigbee2mqtt/bridge/device/+/+/+/+/+/+/+/+/+/+/+/+/+/+/+/+/+/get_group_membership zigbee2mqtt/bridge/device/+/+/+/+/+/+/+/+/+/+/+/+/+/+/+/+/get_group_membership zigbee2mqtt/bridge/device/+/+/+/+/+/+/+/+/+/+/+/+/+/+/+/get_group_membership zigbee2mqtt/bridge/device/+/+/+/+/+/+/+/+/+/+/+/+/+/+/get_group_membership zigbee2mqtt/bridge/device/+/+/+/+/+/+/+/+/+/+/+/+/+/get_group_membership zigbee2mqtt/bridge/device/+/+/+/+/+/+/+/+/+/+/+/+/get_group_membership zigbee2mqtt/bridge/device/+/+/+/+/+/+/+/+/+/+/+/get_group_membership zigbee2mqtt/bridge/device/+/+/+/+/+/+/+/+/+/+/get_group_membership zigbee2mqtt/bridge/device/+/+/+/+/+/+/+/+/+/get_group_membership zigbee2mqtt/bridge/device/+/+/+/+/+/+/+/+/get_group_membership zigbee2mqtt/bridge/device/+/+/+/+/+/+/+/get_group_membership zigbee2mqtt/bridge/device/+/+/+/+/+/+/get_group_membership zigbee2mqtt/bridge/device/+/+/+/+/+/get_group_membership zigbee2mqtt/bridge/device/+/+/+/+/get_group_membership zigbee2mqtt/bridge/device/+/+/+/get_group_membership zigbee2mqtt/bridge/device/+/+/get_group_membership zigbee2mqtt/bridge/device/+/get_group_membership zigbee2mqtt/bridge/group/+/+/+/+/+/+/+/+/+/+/+/+/+/+/+/+/+/+/+/add zigbee2mqtt/bridge/group/+/+/+/+/+/+/+/+/+/+/+/+/+/+/+/+/+/+/+/remove zigbee2mqtt/bridge/group/+/+/+/+/+/+/+/+/+/+/+/+/+/+/+/+/+/+/+/remove_all zigbee2mqtt/bridge/group/+/+/+/+/+/+/+/+/+/+/+/+/+/+/+/+/+/+/add zigbee2mqtt/bridge/group/+/+/+/+/+/+/+/+/+/+/+/+/+/+/+/+/+/+/remove zigbee2mqtt/bridge/group/+/+/+/+/+/+/+/+/+/+/+/+/+/+/+/+/+/+/remove_all zigbee2mqtt/bridge/group/+/+/+/+/+/+/+/+/+/+/+/+/+/+/+/+/+/add zigbee2mqtt/bridge/group/+/+/+/+/+/+/+/+/+/+/+/+/+/+/+/+/+/remove zigbee2mqtt/bridge/group/+/+/+/+/+/+/+/+/+/+/+/+/+/+/+/+/+/remove_all zigbee2mqtt/bridge/group/+/+/+/+/+/+/+/+/+/+/+/+/+/+/+/+/add zigbee2mqtt/bridge/group/+/+/+/+/+/+/+/+/+/+/+/+/+/+/+/+/remove zigbee2mqtt/bridge/group/+/+/+/+/+/+/+/+/+/+/+/+/+/+/+/+/remove_all zigbee2mqtt/bridge/group/+/+/+/+/+/+/+/+/+/+/+/+/+/+/+/add zigbee2mqtt/bridge/group/+/+/+/+/+/+/+/+/+/+/+/+/+/+/+/remove zigbee2mqtt/bridge/group/+/+/+/+/+/+/+/+/+/+/+/+/+/+/+/remove_all zigbee2mqtt/bridge/group/+/+/+/+/+/+/+/+/+/+/+/+/+/+/add zigbee2mqtt/bridge/group/+/+/+/+/+/+/+/+/+/+/+/+/+/+/remove zigbee2mqtt/bridge/group/+/+/+/+/+/+/+/+/+/+/+/+/+/+/remove_all zigbee2mqtt/bridge/group/+/+/+/+/+/+/+/+/+/+/+/+/+/add zigbee2mqtt/bridge/group/+/+/+/+/+/+/+/+/+/+/+/+/+/remove zigbee2mqtt/bridge/group/+/+/+/+/+/+/+/+/+/+/+/+/+/remove_all zigbee2mqtt/bridge/group/+/+/+/+/+/+/+/+/+/+/+/+/add zigbee2mqtt/bridge/group/+/+/+/+/+/+/+/+/+/+/+/+/remove zigbee2mqtt/bridge/group/+/+/+/+/+/+/+/+/+/+/+/+/remove_all zigbee2mqtt/bridge/group/+/+/+/+/+/+/+/+/+/+/+/add zigbee2mqtt/bridge/group/+/+/+/+/+/+/+/+/+/+/+/remove zigbee2mqtt/bridge/group/+/+/+/+/+/+/+/+/+/+/+/remove_all zigbee2mqtt/bridge/group/+/+/+/+/+/+/+/+/+/+/add zigbee2mqtt/bridge/group/+/+/+/+/+/+/+/+/+/+/remove zigbee2mqtt/bridge/group/+/+/+/+/+/+/+/+/+/+/remove_all zigbee2mqtt/bridge/group/+/+/+/+/+/+/+/+/+/add zigbee2mqtt/bridge/group/+/+/+/+/+/+/+/+/+/remove zigbee2mqtt/bridge/group/+/+/+/+/+/+/+/+/+/remove_all zigbee2mqtt/bridge/group/+/+/+/+/+/+/+/+/add zigbee2mqtt/bridge/group/+/+/+/+/+/+/+/+/remove zigbee2mqtt/bridge/group/+/+/+/+/+/+/+/+/remove_all zigbee2mqtt/bridge/group/+/+/+/+/+/+/+/add zigbee2mqtt/bridge/group/+/+/+/+/+/+/+/remove zigbee2mqtt/bridge/group/+/+/+/+/+/+/+/remove_all zigbee2mqtt/bridge/group/+/+/+/+/+/+/add zigbee2mqtt/bridge/group/+/+/+/+/+/+/remove zigbee2mqtt/bridge/group/+/+/+/+/+/+/remove_all zigbee2mqtt/bridge/group/+/+/+/+/+/add zigbee2mqtt/bridge/group/+/+/+/+/+/remove zigbee2mqtt/bridge/group/+/+/+/+/+/remove_all zigbee2mqtt/bridge/group/+/+/+/+/add zigbee2mqtt/bridge/group/+/+/+/+/remove zigbee2mqtt/bridge/group/+/+/+/+/remove_all zigbee2mqtt/bridge/group/+/+/+/add zigbee2mqtt/bridge/group/+/+/+/remove zigbee2mqtt/bridge/group/+/+/+/remove_all zigbee2mqtt/bridge/group/+/+/add zigbee2mqtt/bridge/group/+/+/remove zigbee2mqtt/bridge/group/+/+/remove_all zigbee2mqtt/bridge/group/+/add zigbee2mqtt/bridge/group/+/remove zigbee2mqtt/bridge/group/+/remove_all zigbee2mqtt/bridge/group/remove_all zigbee2mqtt/bridge/networkmap zigbee2mqtt/bridge/networkmap/routes zigbee2mqtt/bridge/ota_update/check zigbee2mqtt/bridge/ota_update/update zigbee2mqtt/bridge/unbind/#
     2021-03-01 13:07:26   version         1.16.1
     2019-09-12 17:38:16   x_group_add_group set RemoteControl
     2019-09-12 17:40:54   x_group_add_to  set RemoteControl 0x90fd9ffffee7e93a
     2019-09-12 17:35:27   x_group_rm_group set 'RemoteControl'
Attributes:
   DbLogExclude .*
   IODev      MQTT2_FHEM_Server
   alias      MQTT2_zigbee_pi
   autocreate 1
   bridgeRegexp zigbee2mqtt/([A-Za-z0-9._]*)[/]?.*:.* "zigbee_$1"
   disable    0
   getList    devicelist:noArg log zigbee2mqtt/bridge/config/devices
  networkmap_raw:noArg raw zigbee2mqtt/bridge/networkmap raw
  networkmap_graphviz:noArg graphviz zigbee2mqtt/bridge/networkmap graphviz
   model      L_01_zigbee2mqtt_bridge
   readingList zigbee2mqtt/bridge/state:.* state
  zigbee2mqtt/bridge/config/devices:.* {}
  zigbee2mqtt/bridge/config/log_level:.* log_level
  zigbee2mqtt/bridge/config/permit_join:.* permit_join
  zigbee2mqtt/bridge/config/rename:.* { json2nameValue($EVENT, 'rename_') }
  zigbee2mqtt/bridge/log:.*\"type\".\"devices\".\"message\".* devices
  zigbee2mqtt/bridge/log:.* log
  zigbee2mqtt/bridge/networkmap:.* {}
  zigbee2mqtt/bridge/networkmap/graphviz:.* graphviz
  zigbee2mqtt/bridge/networkmap/raw:.* raw
  zigbee2mqtt/bridge/config:.* { json2nameValue($EVENT) }
   room       MQTT2
   setList    log_level:debug,info,warn,error zigbee2mqtt/bridge/config/log_level $EVTPART1
  permit_join:true,false zigbee2mqtt/bridge/config/permit_join $EVTPART1
  remove:textField zigbee2mqtt/bridge/config/remove $EVTPART1
  y_device_setting:textField zigbee2mqtt/$EVTPART1/set {"$EVTPART2": "$EVTPART3"}
  x_bind:textField zigbee2mqtt/bridge/bind/$EVTPART1 $EVTPART2
  x_bind_unbind:textField zigbee2mqtt/bridge/unbind/$EVTPART1 $EVTPART2
  x_device_options:textField zigbee2mqtt/bridge/config/device_options {"friendly_name":"$EVTPART1",""options": {"$EVTPART2": "$EVTPART3"}}
  x_group_add_to:textField zigbee2mqtt/bridge/group/$EVTPART1/add $EVTPART2
  x_group_rm_from:textField zigbee2mqtt/bridge/group/$EVTPART1/remove $EVTPART2
  x_group_rm_from_all:textField zigbee2mqtt/bridge/group/$EVTPART1/remove_all $EVTPART2
  x_group_add_group:textField zigbee2mqtt/bridge/config/add_group $EVTPART1
  x_group_rm_group:textField zigbee2mqtt/bridge/config/remove_group $EVTPART1
  z_elapsed:textField zigbee2mqtt/bridge/config/elapsed $EVTPART1
  z_last_seen:textField zigbee2mqtt/bridge/config/last_seen $EVTPART1
  z_ban:textField zigbee2mqtt/bridge/config/ban $EVTPART1
  z_rename:textField zigbee2mqtt/bridge/config/rename  {"old":"$EVTPART1","new":"$EVTPART2"}
  z_reset_CC:noArg zigbee2mqtt/bridge/config/reset
   setStateList on off
   verbose    5


[Beta-User]

@ch.eick: Das sieht mir danach aus, als wäre das auf dem Weg zwischen Dongle und Leuchtmittel (n) "kaputt". Die sind anscheinend alle nicht erreichbar, warum, kann vermutlich nur jemand beantworten, der eher z2m-Experte ist. Ich vermute ein Pairing zum "alten Dongle" (=> irgendwie unvollständiger Umzug).


Generelle Anmerkung: CC2531 ist nicht mehr zeitgemäß, das ist wie wenn man

NanoCul für HM

einsetzt: Geht, ist aber nicht optimal und mit vielen Problemen behaftet.

Dafür ist zigbee2mqtt iVm. MQTT2_SERVER und den attrTemplate für MQTT2_DEVICE eigentlich kaum weniger aufwändig als die Ermittlung des korrekten Codes für IT-Geräte... (das einzige, was fehlt, ist diese Art "Autodiscovery", die manche andere Lösungen (mit sehr viel mehr Rechenaufwand/Ressourcenverbrauch!) bieten...).
Aber jeder wie er kann und mag .

[ch.eick]

Generelle Anmerkung: CC2531 ist nicht mehr zeitgemäß, das ist wie wenn man einsetzt: Geht, ist aber nicht optimal und mit vielen Problemen behaftet.

Was wäre denn für 5€ zeitgemäß