Mnóstwo błędnych logów Z2M

Widmotm · 26 Grudzień 2024 20:25

Może ktoś się spotkał i wie z czego mogąa pochodzic błędy w z2m odnośnie state urządzeń. Co kilka sekund dostaje mnóstwo takich logów jak poniżej co powoduje że sieć staje się niestabilna i nie zawsze wszystko dziala. Używam koordynatora conbee2. Z góry dzięki za pomoc
Przykładowy log

2024-12-26 21:18:24 z2m: Publish 'set' 'state' to 'Przełącznik Przedpokój 2' failed: 'Error: ZCL command 0xa4c138d2caf20c6c/3 genOnOff.off({}, {"timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":false,"direction":0,"reservedBits":0,"writeUndiv":false}) failed (no response received (211) Error: waiting for response TIMEOUT)'`

szopen · 26 Grudzień 2024 21:06

google na to

github.com/Koenkk/zigbee2mqtt

Conbee II response failed - no response received

otwarty 10:28AM - 28 Feb 22 UTC

zamknięte 12:02AM - 20 Jun 23 UTC

Jtef

problem stale

### What happened? Tested 4 Tuya module switches on a HA Blue (core-2022.2.6,… supervisor-2022.01.1). Each module has 2 gangs and they are configured to work 2 way: Front 1 1 <-> Front 2 1 Front 1 2 <-> Front 2 2 Back 1 1 <-> Back 2 1 Back 1 2 <-> Back 2 2 In HA when I turn on Front 1 1, Front 1 2, Back 1 1, and Back 1 2 the corresponding switch should turn on but in 80% of cases I get errors with "no response received" from one or more switches. I got this error on the main HA device and I moved to a HA installed in a virtual machine with only the switches paired to zigbee network. I used an extension USB cable and I was in the same room with the switches (2 meters between Conbee 2 and the switches). I also noticed the same error, from time to time, to the relays (Zonoff zbmini) that I use for heating, and also for Ikea Tradfri sockets. I easily reproduce the error on multiple actions on/off. Also tested Conbee II with deconz and the error couldn't be reproduced but I noticed a delay instead of an error (max 1 sec delay for some switches but no error). Additional info: Tested also with CC2531 as coordinator and the problem doesn't reproduce. Tested with Sonoff 3.0 USB dongle plus and the same problem. ### What did you expect to happen? I expect the switches/relays to turn on/off instead receiving an error or at least a small delay instead of an error. ### How to reproduce it (minimal and precise) Pair 4 relays (Zonoff zbmini) or tradfri sockets using Conbee 2 and turn on/off all of them from HA. At some point you'll get this error: `Publish 'set' 'state' to 'Back 1 Bedroom 1' failed: 'Error: Command 0xa4c1386d10db1302/2 genOnOff.on({}, {"sendWhenActive":false,"timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":false,"direction":0,"srcEndpoint":null,"reservedBits":0,"manufacturerCode":null,"transactionSequenceNumber":null,"writeUndiv":false}) failed (no response received)'` I assume it can be reproduced with other devices too, it doesn't seem brand related. ### Zigbee2MQTT version 1.23.0-1 ### Adapter firmware version deCONZ_ConBeeII_0x26720700.bin.GCF 19-Aug-2021 22:20 ### Adapter Conbee II ### Debug log `Debug: Received MQTT message on 'zigbee2mqtt/Front 1 Bedroom 1/l1/set' with data 'ON' Debug: Publishing 'set' 'state' to 'Front 1 Bedroom 1' Debug: Received MQTT message on 'zigbee2mqtt/Front 1 Bedroom 1/l2/set' with data 'ON' Debug: Publishing 'set' 'state' to 'Front 1 Bedroom 1' Debug: Received MQTT message on 'zigbee2mqtt/Back 1 Bedroom 1/l1/set' with data 'ON' Debug: Received MQTT message on 'zigbee2mqtt/Back 1 Bedroom 1/l2/set' with data 'ON' Debug: Publishing 'set' 'state' to 'Back 1 Bedroom 1' Debug: Publishing 'set' 'state' to 'Back 1 Bedroom 1' Info: MQTT publish: topic 'zigbee2mqtt/Front 1 Bedroom 1', payload '{"linkquality":255,"state_l1":"ON","state_l2":null}' Debug: Received Zigbee message from 'Front 1 Bedroom 1', type 'attributeReport', cluster 'genOnOff', data '{"onOff":1}' from endpoint 1 with groupID null Info: MQTT publish: topic 'zigbee2mqtt/Front 1 Bedroom 1', payload '{"linkquality":255,"state_l1":"ON","state_l2":null}' Debug: Received MQTT message on 'zigbee2mqtt/Front 2 Bedroom 1/l1/set' with data 'ON' Debug: Publishing 'set' 'state' to 'Front 2 Bedroom 1' Debug: Received Zigbee message from 'Front 1 Bedroom 1', type 'attributeReport', cluster 'genOnOff', data '{"onOff":1}' from endpoint 2 with groupID null Info: MQTT publish: topic 'zigbee2mqtt/Front 1 Bedroom 1', payload '{"linkquality":255,"state_l1":"ON","state_l2":"ON"}' Info: MQTT publish: topic 'zigbee2mqtt/Front 1 Bedroom 1', payload '{"linkquality":255,"state_l1":"ON","state_l2":"ON"}' Info: MQTT publish: topic 'zigbee2mqtt/Back 1 Bedroom 1', payload '{"linkquality":255,"state_l1":"ON","state_l2":"OFF"}' Info: MQTT publish: topic 'zigbee2mqtt/Front 2 Bedroom 1', payload '{"linkquality":255,"state_l1":"ON","state_l2":"OFF"}' Debug: Received Zigbee message from 'Front 2 Bedroom 1', type 'attributeReport', cluster 'genOnOff', data '{"onOff":1}' from endpoint 1 with groupID null Info: MQTT publish: topic 'zigbee2mqtt/Front 2 Bedroom 1', payload '{"linkquality":255,"state_l1":"ON","state_l2":"OFF"}' Debug: Received Zigbee message from 'Back 1 Bedroom 1', type 'attributeReport', cluster 'genOnOff', data '{"onOff":1}' from endpoint 1 with groupID null Info: MQTT publish: topic 'zigbee2mqtt/Back 1 Bedroom 1', payload '{"linkquality":255,"state_l1":"ON","state_l2":"OFF"}' Debug: Received MQTT message on 'zigbee2mqtt/Front 2 Bedroom 1/l2/set' with data 'ON' Debug: Publishing 'set' 'state' to 'Front 2 Bedroom 1' Debug: Received MQTT message on 'zigbee2mqtt/Back 2 Bedroom 1/l1/set' with data 'ON' Debug: Publishing 'set' 'state' to 'Back 2 Bedroom 1' Info: MQTT publish: topic 'zigbee2mqtt/Front 2 Bedroom 1', payload '{"linkquality":255,"state_l1":"ON","state_l2":"ON"}' Debug: Received Zigbee message from 'Front 2 Bedroom 1', type 'attributeReport', cluster 'genOnOff', data '{"onOff":1}' from endpoint 2 with groupID null Info: MQTT publish: topic 'zigbee2mqtt/Front 2 Bedroom 1', payload '{"linkquality":255,"state_l1":"ON","state_l2":"ON"}' Info: MQTT publish: topic 'zigbee2mqtt/Back 2 Bedroom 1', payload '{"linkquality":255,"state_l1":"ON","state_l2":"OFF"}' Debug: Received Zigbee message from 'Back 2 Bedroom 1', type 'attributeReport', cluster 'genOnOff', data '{"onOff":1}' from endpoint 1 with groupID null Info: MQTT publish: topic 'zigbee2mqtt/Back 2 Bedroom 1', payload '{"linkquality":255,"state_l1":"ON","state_l2":"OFF"}' **Error: Publish 'set' 'state' to 'Back 1 Bedroom 1' failed: 'Error: Command 0xa4c1386d10db1302/2 genOnOff.on({}, {"sendWhenActive":false,"timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":false,"direction":0,"srcEndpoint":null,"reservedBits":0,"manufacturerCode":null,"transactionSequenceNumber":null,"writeUndiv":false}) failed (no response received)' Debug Error: Command 0xa4c1386d10db1302/2 genOnOff.on({}, {"sendWhenActive":false,"timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":false,"direction":0,"srcEndpoint":null,"reservedBits":0,"manufacturerCode":null,"transactionSequenceNumber":null,"writeUndiv":false}) failed (no response received) at DeconzAdapter.<anonymous> (/app/node_modules/zigbee-herdsman/dist/adapter/deconz/adapter/deconzAdapter.js:608:23) at Generator.throw (<anonymous>) at rejected (/app/node_modules/zigbee-herdsman/dist/adapter/deconz/adapter/deconzAdapter.js:25:65)** Info: MQTT publish: topic 'zigbee2mqtt/bridge/log', payload '{"message":"Publish 'set' 'state' to 'Back 1 Bedroom 1' failed: 'Error: Command 0xa4c1386d10db1302/2 genOnOff.on({}, {\"sendWhenActive\":false,\"timeout\":10000,\"disableResponse\":false,\"disableRecovery\":false,\"disableDefaultResponse\":false,\"direction\":0,\"srcEndpoint\":null,\"reservedBits\":0,\"manufacturerCode\":null,\"transactionSequenceNumber\":null,\"writeUndiv\":false}) failed (no response received)'","meta":{"friendly_name":"Back 1 Bedroom 1"},"type":"zigbee_publish_error"}' Debug: Saving state to file /config/zigbee2mqtt/state.json`

GSzabados · 26 Grudzień 2024 21:06

When you are trying to turn off Przełącznik Przedpokój 2, it is not responding, no response received. So, it is timing out as default. Either the device you are trying to control is not powered on, or its firmware has crashed, or something similar. I guess you should just power cycle and it will start to work, respond again, as normal.