Die Hue Bridge ist jetzt kompl. entfernt?
Ich habe die Logs eben nur mal kurz überflogen, aber da tauchen schon einige Fehler auf. Z.B.:
[04.08.2024 16:02:51] info: z2m:mqtt: MQTT publish: topic 'homeassistant/binary_sensor/1221051039810110150109113116116_0x00124b00258cdd3d/connection_state/config', payload '{"device":{"hw_version":"zStack3x0 20240716","identifiers":["zigbee2mqtt_bridge_0x00124b00258cdd3d"],"manufacturer":"Zigbee2MQTT","model":"Bridge","name":"Zigbee2MQTT Bridge","sw_version":"1.39.1"},"device_class":"connectivity","entity_category":"diagnostic","name":"Connection state","object_id":"zigbee2mqtt_bridge_connection_state","origin":{"name":"Zigbee2MQTT","sw":"1.39.1","url":"https://www.zigbee2mqtt.io"},"payload_off":"offline","payload_on":"online","state_topic":"zigbee2mqtt/bridge/state","unique_id":"bridge_0x00124b00258cdd3d_connection_state_zigbee2mqtt","value_template":"{{ value_json.state }}"}'
[04.08.2024 16:03:04] error: zh:zstack:znp: Error while parsing to ZpiObject 'Error: CommandID '159' from subsystem '5' not found
at Function.fromUnpiFrame (/app/node_modules/zigbee-herdsman/src/adapter/z-stack/znp/zpiObject.ts:66:19)
at Znp.onUnpiParsed (/app/node_modules/zigbee-herdsman/src/adapter/z-stack/znp/znp.ts:88:38)
at Parser.emit (node:events:517:28)
at Parser.parseNext (/app/node_modules/zigbee-herdsman/src/adapter/z-stack/unpi/parser.ts:46:26)
at Parser._transform (/app/node_modules/zigbee-herdsman/src/adapter/z-stack/unpi/parser.ts:20:14)
at Parser.Transform._write (node:internal/streams/transform:175:8)
at writeOrBuffer (node:internal/streams/writable:392:12)
at _write (node:internal/streams/writable:333:10)
at Parser.Writable.write (node:internal/streams/writable:337:10)
at Socket.ondata (node:internal/streams/readable:809:22)'
[04.08.2024 16:03:04] error: zh:zstack:znp: Error while parsing to ZpiObject 'Error: CommandID '159' from subsystem '5' not found
at Function.fromUnpiFrame (/app/node_modules/zigbee-herdsman/src/adapter/z-stack/znp/zpiObject.ts:66:19)
at Znp.onUnpiParsed (/app/node_modules/zigbee-herdsman/src/adapter/z-stack/znp/znp.ts:88:38)
at Parser.emit (node:events:517:28)
at Parser.parseNext (/app/node_modules/zigbee-herdsman/src/adapter/z-stack/unpi/parser.ts:46:26)
at Parser._transform (/app/node_modules/zigbee-herdsman/src/adapter/z-stack/unpi/parser.ts:20:14)
at Parser.Transform._write (node:internal/streams/transform:175:8)
at writeOrBuffer (node:internal/streams/writable:392:12)
at _write (node:internal/streams/writable:333:10)
at Parser.Writable.write (node:internal/streams/writable:337:10)
at Socket.ondata (node:internal/streams/readable:809:22)'
[04.08.2024 16:03:04] error: zh:zstack:znp: Error while parsing to ZpiObject 'Error: CommandID '159' from subsystem '5' not found
at Function.fromUnpiFrame (/app/node_modules/zigbee-herdsman/src/adapter/z-stack/znp/zpiObject.ts:66:19)
at Znp.onUnpiParsed (/app/node_modules/zigbee-herdsman/src/adapter/z-stack/znp/znp.ts:88:38)
at Parser.emit (node:events:517:28)
at Parser.parseNext (/app/node_modules/zigbee-herdsman/src/adapter/z-stack/unpi/parser.ts:46:26)
at Parser._transform (/app/node_modules/zigbee-herdsman/src/adapter/z-stack/unpi/parser.ts:20:14)
at Parser.Transform._write (node:internal/streams/transform:175:8)
at writeOrBuffer (node:internal/streams/writable:392:12)
at _write (node:internal/streams/writable:333:10)
at Parser.Writable.write (node:internal/streams/writable:337:10)
at Socket.ondata (node:internal/streams/readable:809:22)'
Oder
05.08.2024 10:30:30] info: z2m: Restarting Zigbee2MQTT
[05.08.2024 10:30:30] info: z2m:mqtt: MQTT publish: topic 'zigbee2mqtt/bridge/response/restart', payload '{"data":{},"status":"ok"}'
[05.08.2024 10:30:31] info: z2m:mqtt: MQTT publish: topic 'zigbee2mqtt/bridge/state', payload '{"state":"offline"}'
[05.08.2024 10:30:31] info: z2m: Disconnecting from MQTT server
[05.08.2024 10:30:31] info: z2m: Stopping zigbee-herdsman...
[05.08.2024 10:30:31] error: zh:controller: Failed to disable join on stop: Error: SREQ '--> AF - dataRequestExt - {"dstaddrmode":2,"dstaddr":"0x000000000000fffd","destendpoint":242,"dstpanid":0,"srcendpoint":242,"clusterid":33,"transid":146,"options":0,"radius":30,"len":6,"data":{"type":"Buffer","data":[25,142,2,10,0,0]}}' failed with status '(0x11: BUFFER_FULL)' (expected '(0x00: SUCCESS)')
[05.08.2024 10:30:40] info: zh:controller: Wrote coordinator backup to '/config/zigbee2mqtt/coordinator_backup.json'
Oder
[06.08.2024 10:32:28] info: zh:zstack:znp: Socket error
[06.08.2024 10:32:28] info: zh:zstack:znp: Port closed
[06.08.2024 10:32:28] info: zh:zstack:znp: closing
[06.08.2024 10:32:28] error: z2m: Adapter disconnected, stopping
[06.08.2024 10:32:28] info: z2m:mqtt: MQTT publish: topic 'zigbee2mqtt/bridge/state', payload '{"state":"offline"}'
[06.08.2024 10:32:28] info: z2m: Disconnecting from MQTT server
[06.08.2024 10:32:28] info: z2m: Stopping zigbee-herdsman...
[06.08.2024 10:32:28] info: z2m: Stopped zigbee-herdsman
[06.08.2024 10:32:28] info: z2m: Stopped Zigbee2MQTT
06.08.2024 10:48:57] info: zh:zstack:znp: Socket error
[06.08.2024 10:48:57] info: zh:zstack:znp: Port closed
[06.08.2024 10:48:57] info: zh:zstack:znp: closing
[06.08.2024 10:48:57] error: z2m: Adapter disconnected, stopping
[06.08.2024 10:48:57] info: z2m:mqtt: MQTT publish: topic 'zigbee2mqtt/bridge/state', payload '{"state":"offline"}'
[06.08.2024 10:48:57] info: z2m: Disconnecting from MQTT server
[06.08.2024 10:48:57] info: z2m: Stopping zigbee-herdsman...
[06.08.2024 10:48:57] info: z2m: Stopped zigbee-herdsman
[06.08.2024 10:48:57] info: z2m: Stopped Zigbee2MQTT
Wobei die letzten Socket error Fehler natürlich auch durch einen Z2M Neustart durch Dich kommen können.
Was es für die div. Fehlermeldungen jetzt genau für mögliche Ursachen gibt kann ich Dir leider auch nicht sagen. Da musst Du selber mal nachforschen.
Wie ich gesehen habe hast Du bei Dir die Zigbee Firmware 20240716 installiert, wozu ich noch nicht wirklich Infos und Erfahrungswerte finden konnte. Ich habe gerade heute morgen, nachdem ich ein paar Infos dazu gelesen habe, die Zigbee Firmware 20240710 installiert, weil etliche User geschrieben haben das diese Version bei ihnen fehlerfrei funktioniert. Vielleicht könntest Du ja auch mal ein Downgrade auf die Version 20240710 machen. Wobei ich eigentlich nicht glaube das es an der Firmware-Version liegt sondern es andere Ursachen dafür gibt.
VG Jim