UPDATE 31.10.: Amazon Alexa - ioBroker Skill läuft aus ?

[Asgothian]

@ente34 sagte in ZigBee neue Version 1.5.x:

Error while opening serialport 'Error: Error: No such file or directory, cannot open /dev/serial/by-id/usb-dresden_elektronik_ingenieurtechnik_GmbH_ConBee_II_DE2218746-if00'

Entweder fehlt am Anfang des Logs noch einiges oder der Zigbee Stick ist seit dem Stromausfall defekt:

Error while opening serialport 'Error: Error: No such file or directory, cannot open /dev/serial/by-id/usb-dresden_elektronik_ingenieurtechnik_GmbH_ConBee_II_DE2218746-if00'

Nebenbei hast du mindestens 2 unterschiedliche Zigbee Versionen in deinem Log.

• Welche version hattest du vor dem Stromausfall aktiv (und am laufen?)
• Warum hast du gedacht das nach einem Stromausfall ein Update / Downgrade des Zigbee Adapters irgend etwas bewirkt ?

A.

[ente34]

@asgothian
Habe versuchweise einen Downgrade durchgeführt.
Bin jetzt wieder bei 1.5.6

Nach reboot mit deaktiviertem Zigbee und dann nachdem alles hochgelaufen ist zigbee aktiviert:

zigbee.0	2021-06-09 19:41:24.425	warn	(1903) Read-only state "zigbee.0.info.connection" has been written without ack-flag with value "false"
zigbee.0	2021-06-09 19:41:24.423	error	(1903) Error: Error while opening serialport 'Error: Error: No such file or directory, cannot open /dev/serial/by-id/usb-dresden_elektronik_ingenieurtechnik_GmbH_ConBee_II_DE2218746-if00' at Drive
zigbee.0	2021-06-09 19:41:24.421	error	(1903) Failed to start Zigbee
zigbee.0	2021-06-09 19:41:24.264	info	(1903) Installed Version: iobroker.zigbee@1.5.6
zigbee.0	2021-06-09 19:41:24.258	warn	(1903) Read-only state "zigbee.0.info.connection" has been written without ack-flag with value "false"
zigbee.0	2021-06-09 19:41:24.053	info	(1903) Starting Zigbee npm ...
zigbee.0	2021-06-09 19:41:23.960	info	(1903) starting. Version 1.4.1 in /opt/iobroker/node_modules/iobroker.zigbee, node: v12.22.1, js-controller: 3.3.11
host.raspi-iobroker	2021-06-09 19:41:21.617	info	instance system.adapter.zigbee.0 started with pid 1903
host.raspi-iobroker	2021-06-09 19:40:51.545	info	Restart adapter system.adapter.zigbee.0 because enabled
host.raspi-iobroker	2021-06-09 19:40:51.544	error	instance system.adapter.zigbee.0 terminated with code 6 (UNCAUGHT_EXCEPTION)
zigbee.0	2021-06-09 19:40:50.950	warn	(1827) Read-only state "zigbee.0.info.pairingMessage" has been written without ack-flag with value "Error: Failed to stop zigbee (TypeError: Cannot read property 'getEntries' of null at Function.l
zigbee.0	2021-06-09 19:40:50.939	error	(1827) Cannot read property 'getEntries' of null
zigbee.0	2021-06-09 19:40:50.938	error	(1827) TypeError: Cannot read property 'getEntries' of null at Function.loadFromDatabaseIfNecessary (/opt/iobroker/node_modules/zigbee-herdsman/dist/controller/model/device.js:216:55) at Funct
zigbee.0	2021-06-09 19:40:50.931	error	(1827) unhandled promise rejection: Cannot read property 'getEntries' of null
zigbee.0	2021-06-09 19:40:50.928	error	(1827) Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch().
zigbee.0	2021-06-09 19:40:50.926	warn	(1827) Terminated (UNCAUGHT_EXCEPTION): Without reason
zigbee.0	2021-06-09 19:40:50.924	info	(1827) terminating
zigbee.0	2021-06-09 19:40:50.922	error	(1827) Failed to stop zigbee (TypeError: Cannot read property 'getEntries' of null at Function.loadFromDatabaseIfNecessary (/opt/iobroker/node_modules/zigbee-herdsman/dist/controller/model/group.j
zigbee.0	2021-06-09 19:40:50.918	info	(1827) Zigbee: disabling joining new devices.
zigbee.0	2021-06-09 19:40:50.912	info	(1827) cleaned everything up...
zigbee.0	2021-06-09 19:40:50.901	error	(1827) Error while opening serialport 'Error: Error: No such file or directory, cannot open /dev/serial/by-id/usb-dresden_elektronik_ingenieurtechnik_GmbH_ConBee_II_DE2218746-if00'
zigbee.0	2021-06-09 19:40:50.900	error	(1827) Error: Error while opening serialport 'Error: Error: No such file or directory, cannot open /dev/serial/by-id/usb-dresden_elektronik_ingenieurtechnik_GmbH_ConBee_II_DE2218746-if00' at Drive
zigbee.0	2021-06-09 19:40:50.899	error	(1827) unhandled promise rejection: Error while opening serialport 'Error: Error: No such file or directory, cannot open /dev/serial/by-id/usb-dresden_elektronik_ingenieurtechnik_GmbH_ConBee_II_DE2218
zigbee.0	2021-06-09 19:40:50.897	error	(1827) Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch().
zigbee.0	2021-06-09 19:40:30.083	warn	(1827) Read-only state "zigbee.0.info.connection" has been written without ack-flag with value "false"
zigbee.0	2021-06-09 19:40:30.078	error	(1827) Error: Error while opening serialport 'Error: Error: No such file or directory, cannot open /dev/serial/by-id/usb-dresden_elektronik_ingenieurtechnik_GmbH_ConBee_II_DE2218746-if00' at Drive
zigbee.0	2021-06-09 19:40:30.077	error	(1827) Failed to start Zigbee
zigbee.0	2021-06-09 19:40:29.922	info	(1827) Installed Version: iobroker.zigbee@1.5.6
zigbee.0	2021-06-09 19:40:29.893	info	(1827) Starting Zigbee npm ...
zigbee.0	2021-06-09 19:40:29.892	info	(1827) Try to reconnect. 1 attempts left
zigbee.0	2021-06-09 19:40:19.893	warn	(1827) Read-only state "zigbee.0.info.connection" has been written without ack-flag with value "false"
zigbee.0	2021-06-09 19:40:19.891	error	(1827) Error: Error while opening serialport 'Error: Error: No such file or directory, cannot open /dev/serial/by-id/usb-dresden_elektronik_ingenieurtechnik_GmbH_ConBee_II_DE2218746-if00' at Drive
zigbee.0	2021-06-09 19:40:19.890	error	(1827) Failed to start Zigbee
zigbee.0	2021-06-09 19:40:19.728	info	(1827) Installed Version: iobroker.zigbee@1.5.6
zigbee.0	2021-06-09 19:40:19.724	warn	(1827) Read-only state "zigbee.0.info.connection" has been written without ack-flag with value "false"
zigbee.0	2021-06-09 19:40:19.492	info	(1827) Starting Zigbee npm ...
zigbee.0	2021-06-09 19:40:19.377	info	(1827) starting. Version 1.4.1 in /opt/iobroker/node_modules/iobroker.zigbee, node: v12.22.1, js-controller: 3.3.11
host.raspi-iobroker	2021-06-09 19:40:16.846	info	instance system.adapter.zigbee.0 started with pid 1827
host.raspi-iobroker	2021-06-09 19:40:16.799	info	"system.adapter.zigbee.0" enabled

[Asgothian]

@ente34 sagte in ZigBee neue Version 1.5.x:

@asgothian
Habe versuchweise einen Downgrade durchgeführt.
Bin jetzt wieder bei 1.5.6

:face_palm:

Um dem Problem auf den Grund zu gehen musst du heraus bekommen warum der serielle Port nicht mehr verfügbar ist. Das Log sagt eindeutig das symlink nicht existiert.

Insbesondere bei Stromausfällen / RaspberryPi Abstürzen / Proxxmox Updates die plötzlich einen laufenden Zigbee Adapter zerlegen ist zu 95% ein Problem mit der Verbindung zum Koordinator die Ursache.

A.

Nachtrag: Oh Wunder, auch in diesem Log findet sich bei jedem Startversuch die gleiche Meldung:

Error: Error while opening serialport 'Error: Error: No such file or directory, cannot open /dev/serial/by-id/usb-dresden_elektronik_ingenieurtechnik_GmbH_ConBee_II_DE2218746-if00'

Der Stick wird also immer noch nicht erkannt.

[ente34]

@asgothian
Habe einen neuen link 'serial1'

pi@raspi-iobroker:~ $ ls -l /dev/serial1
lrwxrwxrwx 1 root root 7 Jun  9 19:36 /dev/serial1 -> ttyAMA0
pi@raspi-iobroker:~ $

[ente34]

@asgothian
Erst mal vielen Dank für den schnellen Support!

[gosund]

@asgothian
@artek

Schlechte Nachrichten: Das komplette löschen, installieren und neu Anlernen hat nichts gebracht.
Wie die letzten Tage auch hat sich der Adapter wieder innerhalb eines Tages aufgehängt. Ich mußte den Pi wieder komplett rebooten, damit es wieder geht.

Hilfe, ich weiß mir absolut nicht mehr zu helfen. Was kann ich noch versuchen?

[rewenode]

Ich weis echt nicht mehr weiter.
Bekomme einfach nicht das Update vom 1.5.5 auf 1.5.6 hin.
iob im Docker Container mit 4gb auf einem Rock64
node.js - v12.18.3
npm - 6.14.6
zigbee stick CC2538 + CC2592 von dimaiv

Bisher gab es nie die geringsten zigbee Updateprobleme. Nur die 1.5.6 bekomme ich nicht installiert.
Hier das Log:

Spoiler

 01:23:20.786 - info: zigbee.0 (3129) starting. Version 1.5.6 in /opt/iobroker/node_modules/iobroker.zigbee, node: v12.18.3, js-controller: 3.2.16
2021-06-11 01:23:21.151 - info: zigbee.0 (3129) Starting Zigbee npm ...
2021-06-11 01:23:22.084 - info: zigbee.0 (3129) Installed Version: iobroker.zigbee@1.5.6
2021-06-11 01:23:23.678 - error: zigbee.0 (3129) Configuration is not consistent with adapter state/backup!
2021-06-11 01:23:23.681 - error: zigbee.0 (3129) - PAN ID: configured=6754, adapter=65535
2021-06-11 01:23:23.683 - error: zigbee.0 (3129) - Extended PAN ID: configured=00124b001940c0ba, adapter=0000000000000000
2021-06-11 01:23:23.685 - error: zigbee.0 (3129) - Network Key: configured=01030507090b0d0f00020406080a0c0d, adapter=01030507090b0d0f00020406080a0c0d
2021-06-11 01:23:23.686 - error: zigbee.0 (3129) - Channel List: configured=11, adapter=
2021-06-11 01:23:23.688 - error: zigbee.0 (3129) Please update configuration to prevent further issues.
2021-06-11 01:23:23.689 - error: zigbee.0 (3129) If you wish to re-commission your network, please remove coordinator backup at /opt/iobroker/iobroker-data/zigbee_0/nvbackup.json.
2021-06-11 01:23:23.691 - error: zigbee.0 (3129) Re-commissioning your network will require re-pairing of all devices!
2021-06-11 01:23:23.694 - error: zigbee.0 (3129) Starting zigbee-herdsman problem : "startup failed - configuration-adapter mismatch - see logs above for more information"
2021-06-11 01:23:23.695 - error: zigbee.0 (3129) Failed to start Zigbee
2021-06-11 01:23:23.697 - error: zigbee.0 (3129) Error herdsman start
2021-06-11 01:23:33.700 - info: zigbee.0 (3129) Try to reconnect. 1 attempts left
2021-06-11 01:23:33.702 - info: zigbee.0 (3129) Starting Zigbee npm ...
2021-06-11 01:23:33.735 - info: zigbee.0 (3129) Installed Version: iobroker.zigbee@1.5.6
2021-06-11 01:23:33.980 - error: zigbee.0 (3129) Starting zigbee-herdsman problem : "Error while opening serialport 'Error: Error Resource temporarily unavailable Cannot lock port'"
2021-06-11 01:23:33.982 - error: zigbee.0 (3129) Failed to start Zigbee
2021-06-11 01:23:33.984 - error: zigbee.0 (3129) Error herdsman start
2021-06-11 01:25:09.693 - info: host.iobroker stopInstance system.adapter.zigbee.0 (force=false, process=true)
2021-06-11 01:25:09.717 - info: mqtt.0 (705) send2Server system.adapter.zigbee.0.sigKill[iob/system/adapter/zigbee/0/sigKill]
2021-06-11 01:25:09.718 - info: zigbee.0 (3129) Got terminate signal TERMINATE_YOURSELF
2021-06-11 01:25:09.723 - info: zigbee.0 (3129) cleaned everything up...
2021-06-11 01:25:09.730 - info: zigbee.0 (3129) Zigbee: disabling joining new devices.
2021-06-11 01:25:09.733 - warn: zigbee.0 (3129) Failed to stop zigbee during startup
2021-06-11 01:25:09.735 - info: zigbee.0 (3129) terminating
2021-06-11 01:25:09.737 - info: zigbee.0 (3129) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
2021-06-11 01:25:09.739 - error: zigbee.0 (3129) Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch().
2021-06-11 01:25:09.740 - error: zigbee.0 (3129) unhandled promise rejection: Cannot read property 'getEntries' of null
2021-06-11 01:25:09.743 - error: zigbee.0 (3129) TypeError: Cannot read property 'getEntries' of null
at Function.loadFromDatabaseIfNecessary (/opt/iobroker/node_modules/iobroker.zigbee/node_modules/zigbee-herdsman/dist/controller/model/device.js:220:55)
at Function.all (/opt/iobroker/node_modules/iobroker.zigbee/node_modules/zigbee-herdsman/dist/controller/model/device.js:240:16)
at Controller.getDevices (/opt/iobroker/node_modules/iobroker.zigbee/node_modules/zigbee-herdsman/dist/controller/controller.js:303:31)
at ZigbeeController.getClients (/opt/iobroker/node_modules/iobroker.zigbee/lib/zigbeecontroller.js:228:49)
at DeviceAvailability.stop (/opt/iobroker/node_modules/iobroker.zigbee/lib/zbDeviceAvailability.js:222:43)
at ZigbeeController.callExtensionMethod (/opt/iobroker/node_modules/iobroker.zigbee/lib/zigbeecontroller.js:214:42)
at ZigbeeController.stop (/opt/iobroker/node_modules/iobroker.zigbee/lib/zigbeecontroller.js:385:20)
at Zigbee.onUnload (/opt/iobroker/node_modules/iobroker.zigbee/main.js:696:41)
at processTicksAndRejections (internal/process/task_queues.js:97:5)

Was kann ich noch tun ?

[arteck]

@rewenode geh auf version 1.4.1 und dann wieder auf die 1.5.6 gehts dann ?

[rewenode]

@arteck Reicht da ein Downgrade adapter->Bestimmte version installieren -> 1.4.1 ?
Oder muss erst den Adapter (1.5.5) löschen?
Und falls löschen, wie kann ich alle meine Geräte behalten ohne alle neu anlernen zu müssen?

Sry wenn die Fragen etwas naiv sein sollten. Ich sag ja, bisher reichte ein Knopfdruck und alles neu anlernen wäre hier ziemlich mit Arbeit verbunden bei kleinem Zeitfenster.

Jedenfalls schonmal danke für deine Hilfe.

[gosund]

@arteck @Asgothian

FYI: Hatte gestern Abend auf die 1.5.5 herunter gegraded. Das Problem besteht immer noch: nach ziemlich genau 24 Stunden hängt sich der Adapter auf. Ich mußte den Pi gerade eben wieder booten.

Irgend eine Idee, was ich noch machen kann?

Und nochwas: Seit dem Downgrade bekomme ich ständig folgende Meldung im Log:

zigbee.0 (1671) Failed to DeviceConfigure.onZigbeeEvent (Error: 'LED1623G12' has no configure
    at Object.getConfigureKey (/opt/iobroker/node_modules/zigbee-herdsman-converters/lib/configureKey.js:20:15)
    at DeviceConfigure.shouldConfigure (/opt/iobroker/node_modules/iobroker.zigbee/lib/zbDeviceConfigure.js:33:38)
    at DeviceConfigure.onZigbeeEvent (/opt/iobroker/node_modules/iobroker.zigbee/lib/zbDeviceConfigure.js:76:22)
    at ZigbeeController.callExtensionMethod (/opt/iobroker/node_modules/iobroker.zigbee/lib/zigbeecontroller.js:196:42)
    at ZigbeeController.handleMessage (/opt/iobroker/node_modules/iobroker.zigbee/lib/zigbeecontroller.js:560:14))

Woher kommt LED1623G12? Ich habe alle Devices umbenannt, kann also nicht sagen, welches er meint. Irgend eine Idee?

[Rushmed]

Hallo,

ich komme gerade vom Ikea Einkauf und habe zwei kleine Probleme.
Die Fernbedienung STYRBAR wird vom Adapter als W2094 erkannt. Auf dem Gerät steht aber W2044 und in der Anleitung E2002. Das ist erstmal kein Problem für mich, allerdings funktionieren Druck und langer Druck nur bei den links/rechts Tasten. Die anderen beiden Tasten funktionieren garnicht.
Wenn ich STYRBAR direkt mit einer Lampe kopple geht alles.
Wenn ich den Adapter auf debug stelle kommen Tastendrücke an:

zigbee.0	2021-06-12 19:09:59.315	debug	(18506) Publish {"action":"brightness_stop","action_group":901} to "842e14fffe471ae1"
zigbee.0	2021-06-12 19:09:59.300	debug	(18506) Type commandStopWithOnOff device {"type":"device","device":{"ID":33,"_type":"EndDevice","_ieeeAddr":"0x842e14fffe471ae1","_networkAddress":24375,"_manufacturerID":4476,"_endpoints":[{"ID":1,"p
zigbee.0	2021-06-12 19:09:59.299	debug	(18506) Received Zigbee message from '0x842e14fffe471ae1', type 'commandStopWithOnOff', cluster 'genLevelCtrl', data '{}' from endpoint 1 with groupID 901
zigbee.0	2021-06-12 19:09:59.297	debug	(18506) handleMessage. {"type":"commandStopWithOnOff","device":{"ID":33,"_type":"EndDevice","_ieeeAddr":"0x842e14fffe471ae1","_networkAddress":24375,"_manufacturerID":4476,"_endpoints":[{"ID":1,"profi
zigbee.0	2021-06-12 19:09:58.939	debug	(18506) Publish {"action":"brightness_move_down","action_rate":83,"action_group":901} to "842e14fffe471ae1"
zigbee.0	2021-06-12 19:09:58.926	debug	(18506) Type commandMove device {"type":"device","device":{"ID":33,"_type":"EndDevice","_ieeeAddr":"0x842e14fffe471ae1","_networkAddress":24375,"_manufacturerID":4476,"_endpoints":[{"ID":1,"profileID"
zigbee.0	2021-06-12 19:09:58.926	debug	(18506) Received Zigbee message from '0x842e14fffe471ae1', type 'commandMove', cluster 'genLevelCtrl', data '{"movemode":1,"rate":83}' from endpoint 1 with groupID 901
zigbee.0	2021-06-12 19:09:58.924	debug	(18506) handleMessage. {"type":"commandMove","device":{"ID":33,"_type":"EndDevice","_ieeeAddr":"0x842e14fffe471ae1","_networkAddress":24375,"_manufacturerID":4476,"_endpoints":[{"ID":1,"profileID":260
zigbee.0	2021-06-12 19:09:57.127	debug	(18506) Publish {"action":"brightness_stop","action_group":901} to "842e14fffe471ae1"
zigbee.0	2021-06-12 19:09:57.116	debug	(18506) Type commandStopWithOnOff device {"type":"device","device":{"ID":33,"_type":"EndDevice","_ieeeAddr":"0x842e14fffe471ae1","_networkAddress":24375,"_manufacturerID":4476,"_endpoints":[{"ID":1,"p
zigbee.0	2021-06-12 19:09:57.114	debug	(18506) Received Zigbee message from '0x842e14fffe471ae1', type 'commandStopWithOnOff', cluster 'genLevelCtrl', data '{}' from endpoint 1 with groupID 901
zigbee.0	2021-06-12 19:09:57.113	debug	(18506) handleMessage. {"type":"commandStopWithOnOff","device":{"ID":33,"_type":"EndDevice","_ieeeAddr":"0x842e14fffe471ae1","_networkAddress":24375,"_manufacturerID":4476,"_endpoints":[{"ID":1,"profi
zigbee.0	2021-06-12 19:09:56.660	debug	(18506) Publish {"action":"brightness_move_up","action_rate":83,"action_group":901} to "842e14fffe471ae1"
zigbee.0	2021-06-12 19:09:56.644	debug	(18506) Type commandMoveWithOnOff device {"type":"device","device":{"ID":33,"_type":"EndDevice","_ieeeAddr":"0x842e14fffe471ae1","_networkAddress":24375,"_manufacturerID":4476,"_endpoints":[{"ID":1,"p
zigbee.0	2021-06-12 19:09:56.643	debug	(18506) Received Zigbee message from '0x842e14fffe471ae1', type 'commandMoveWithOnOff', cluster 'genLevelCtrl', data '{"movemode":0,"rate":83}' from endpoint 1 with groupID 901
zigbee.0	2021-06-12 19:09:56.640	debug	(18506) handleMessage. {"type":"commandMoveWithOnOff","device":{"ID":33,"_type":"EndDevice","_ieeeAddr":"0x842e14fffe471ae1","_networkAddress":24375,"_manufacturerID":4476,"_endpoints":[{"ID":1,"profi
zigbee.0	2021-06-12 19:09:54.926	debug	(18506) Publish {"action":"on","action_group":901} to "842e14fffe471ae1"
zigbee.0	2021-06-12 19:09:54.917	debug	(18506) Type commandOn device {"type":"device","device":{"ID":33,"_type":"EndDevice","_ieeeAddr":"0x842e14fffe471ae1","_networkAddress":24375,"_manufacturerID":4476,"_endpoints":[{"ID":1,"profileID":2
zigbee.0	2021-06-12 19:09:54.916	debug	(18506) Received Zigbee message from '0x842e14fffe471ae1', type 'commandOn', cluster 'genOnOff', data '{}' from endpoint 1 with groupID 901
zigbee.0	2021-06-12 19:09:54.915	debug	(18506) handleMessage. {"type":"commandOn","device":{"ID":33,"_type":"EndDevice","_ieeeAddr":"0x842e14fffe471ae1","_networkAddress":24375,"_manufacturerID":4476,"_endpoints":[{"ID":1,"profileID":260,"
zigbee.0	2021-06-12 19:09:53.737	debug	(18506) Publish {"action":"arrow_right_click"} to "842e14fffe471ae1"
zigbee.0	2021-06-12 19:09:53.720	debug	(18506) Type commandTradfriArrowSingle device {"type":"device","device":{"ID":33,"_type":"EndDevice","_ieeeAddr":"0x842e14fffe471ae1","_networkAddress":24375,"_manufacturerID":4476,"_endpoints":[{"ID"
zigbee.0	2021-06-12 19:09:53.719	debug	(18506) Received Zigbee message from '0x842e14fffe471ae1', type 'commandTradfriArrowSingle', cluster 'genScenes', data '{"value":256,"value2":13}' from endpoint 1 with groupID 901
zigbee.0	2021-06-12 19:09:53.715	debug	(18506) handleMessage. {"type":"commandTradfriArrowSingle","device":{"ID":33,"_type":"EndDevice","_ieeeAddr":"0x842e14fffe471ae1","_networkAddress":24375,"_manufacturerID":4476,"_endpoints":[{"ID":1,"
zigbee.0	2021-06-12 19:09:52.576	debug	(18506) Publish {"action":"off","action_group":901} to "842e14fffe471ae1"
zigbee.0	2021-06-12 19:09:52.563	debug	(18506) Type commandOff device {"type":"device","device":{"ID":33,"_type":"EndDevice","_ieeeAddr":"0x842e14fffe471ae1","_networkAddress":24375,"_manufacturerID":4476,"_endpoints":[{"ID":1,"profileID":
zigbee.0	2021-06-12 19:09:52.561	debug	(18506) Received Zigbee message from '0x842e14fffe471ae1', type 'commandOff', cluster 'genOnOff', data '{}' from endpoint 1 with groupID 901
zigbee.0	2021-06-12 19:09:52.558	debug	(18506) handleMessage. {"type":"commandOff","device":{"ID":33,"_type":"EndDevice","_ieeeAddr":"0x842e14fffe471ae1","_networkAddress":24375,"_manufacturerID":4476,"_endpoints":[{"ID":1,"profileID":260,
zigbee.0	2021-06-12 19:09:51.208	debug	(18506) Publish {"action":"arrow_left_click"} to "842e14fffe471ae1"
zigbee.0	2021-06-12 19:09:51.199	debug	(18506) Type commandTradfriArrowSingle device {"type":"device","device":{"ID":33,"_type":"EndDevice","_ieeeAddr":"0x842e14fffe471ae1","_networkAddress":24375,"_manufacturerID":4476,"_endpoints":[{"ID"
zigbee.0	2021-06-12 19:09:51.196	debug	(18506) Received Zigbee message from '0x842e14fffe471ae1', type 'commandTradfriArrowSingle', cluster 'genScenes', data '{"value":257,"value2":13}' from endpoint 1 with groupID 901
zigbee.0	2021-06-12 19:09:51.194	debug	(18506) handleMessage. {"type":"commandTradfriArrowSingle","device":{"ID":33,"_type":"EndDevice","_ieeeAddr":"0x842e14fffe471ae1","_networkAddress":24375,"_manufacturerID":4476,"_endpoints":[{"ID":1,"

Der Timeout für die Erkennung des langen Drucks ist mit ca. 3 s auch sehr lang, kann man das irgendwo verstellen? Das ist zum Beispiel bei E1743 nur ca. 1 s, was viel besser passt.

Dann habe ich noch eine LED1924G9, die funktioniert soweit, außer die Effekte. Da tut sich garnichts.

Hat da jemand einen Tipp für mich?

[locito09]

@rushmed
hast du probiert das Gerät auszuschliessen?

[Rushmed]

@locito09 Wie ausschließen? Im Adapter? Nein.

Edit: Habs probiert, geht nicht.

[arteck]

@gosund da sist der Technische name .. nicht dein umbenanntess.das kannst du in der Kachel sehen ..wenn du die umdrehst

[Frank579]

@Asgothian
Habe gerade mein bastelsystem hochgezogen auf Admin5.
Er spuckt mir jetzt für einige Geräte

zigbee.0
2021-06-13 09:52:06.290	warn	State value to set for "zigbee.0.0017880108279caf.link_quality" has value "255" greater than max "254"

ins Log.
Ist das schon bekannt?

[arteck]

@frank579 ohh Danke..habs korrigiert

[arteck]

@rushmed zeigma die Kachel

[Rushmed]

@arteck Prego!

[arteck]

@rushmed der Button meldet sich als W2049. ist so

https://github.com/Koenkk/zigbee2mqtt/issues/7655

[Rushmed]

@arteck Ja ok, stört mich auch nicht. Mein Problem ist dass nur die Hälfte der Tasten (als Objekte) gehen aber im debug LOG doch auch die anderen irgendwie ankommen wie in meinem Post geschrieben.
Im verlinkten Issue ist das Pairing das Problem, nicht dass die Tasten nur teilweise funktionieren.