Closed Sonic62 closed 2 days ago
ryanm352
commented
9 months ago I had to downgrade. In my case I downgraded to 1.34 because I wasn't sure what version of 1.35.x I upgraded from. This happened to me for multiple zigbee devices. They wouldn't even pair when removed. Once I downgraded, everything worked again.
cipry85
commented
9 months ago I'm having the same problem. I have now tried downloading the version 1.34
sjorge
commented
9 months ago Just tried with my unused one on dev (well from yesterday somewhere when I last updated) I update and paired again.
Zigbee2MQTT:debug 2024-02-11 13:41:07: Received MQTT message on 'zigbee2mqtt/bridge/request/permit_join' with data '{"device":null,"time":254,"transaction":"z8l47-1","value":true}'
Zigbee2MQTT:info 2024-02-11 13:41:07: Zigbee: allowing new devices to join.
Zigbee2MQTT:info 2024-02-11 13:41:08: MQTT publish: topic 'zigbee2mqtt/bridge/response/permit_join', payload '{"data":{"time":254,"value":true},"status":"ok","transaction":"z8l47-1"}'
Zigbee2MQTT:info 2024-02-11 13:41:22: Device '0x54ef441000684c5c' joined
Zigbee2MQTT:info 2024-02-11 13:41:22: MQTT publish: topic 'zigbee2mqtt/bridge/event', payload '{"data":{"friendly_name":"0x54ef441000684c5c","ieee_address":"0x54ef441000684c5c"},"type":"device_joined"}'
Zigbee2MQTT:info 2024-02-11 13:41:22: Starting interview of '0x54ef441000684c5c'
Zigbee2MQTT:info 2024-02-11 13:41:22: MQTT publish: topic 'zigbee2mqtt/bridge/event', payload '{"data":{"friendly_name":"0x54ef441000684c5c","ieee_address":"0x54ef441000684c5c","status":"started"},"type":"device_interview"}'
Zigbee2MQTT:debug 2024-02-11 13:41:22: Device '0x54ef441000684c5c' announced itself
Zigbee2MQTT:info 2024-02-11 13:41:22: MQTT publish: topic 'zigbee2mqtt/bridge/event', payload '{"data":{"friendly_name":"0x54ef441000684c5c","ieee_address":"0x54ef441000684c5c"},"type":"device_announce"}'
Zigbee2MQTT:debug 2024-02-11 13:41:24: Received Zigbee message from '0x54ef441000684c5c', type 'readResponse', cluster 'genBasic', data '{"modelId":"lumi.airmonitor.acn01"}' from endpoint 1 with groupID 0
Zigbee2MQTT:debug 2024-02-11 13:41:24: Skipping message, still interviewing
Zigbee2MQTT:debug 2024-02-11 13:41:24: Received Zigbee message from '0x54ef441000684c5c', type 'readResponse', cluster 'genBasic', data '{"manufacturerName":"LUMI"}' from endpoint 1 with groupID 0
Zigbee2MQTT:debug 2024-02-11 13:41:24: Skipping message, still interviewing
Zigbee2MQTT:debug 2024-02-11 13:41:25: Received Zigbee message from '0x54ef441000684c5c', type 'readResponse', cluster 'genBasic', data '{"powerSource":3}' from endpoint 1 with groupID 0
Zigbee2MQTT:debug 2024-02-11 13:41:25: Skipping message, still interviewing
Zigbee2MQTT:debug 2024-02-11 13:41:26: Received Zigbee message from '0x54ef441000684c5c', type 'readResponse', cluster 'genBasic', data '{"zclVersion":3}' from endpoint 1 with groupID 0
Zigbee2MQTT:debug 2024-02-11 13:41:26: Skipping message, still interviewing
Zigbee2MQTT:debug 2024-02-11 13:41:28: Received Zigbee message from '0x54ef441000684c5c', type 'attributeReport', cluster 'genBasic', data '{"appVersion":29,"modelId":"lumi.airmonitor.acn01"}' from endpoint 1 with groupID 0
Zigbee2MQTT:debug 2024-02-11 13:41:28: Skipping message, still interviewing
Zigbee2MQTT:debug 2024-02-11 13:41:28: Received Zigbee message from '0x54ef441000684c5c', type 'attributeReport', cluster 'msTemperatureMeasurement', data '{"measuredValue":2071}' from endpoint 1 with groupID 0
Zigbee2MQTT:debug 2024-02-11 13:41:28: Skipping message, still interviewing
Zigbee2MQTT:debug 2024-02-11 13:41:28: Received Zigbee message from '0x54ef441000684c5c', type 'attributeReport', cluster 'msRelativeHumidity', data '{"measuredValue":5230}' from endpoint 1 with groupID 0
Zigbee2MQTT:debug 2024-02-11 13:41:28: Skipping message, still interviewing
Zigbee2MQTT:debug 2024-02-11 13:41:29: Received Zigbee message from '0x54ef441000684c5c', type 'readResponse', cluster 'genBasic', data '{"appVersion":29}' from endpoint 1 with groupID 0
Zigbee2MQTT:debug 2024-02-11 13:41:29: Skipping message, still interviewing
Zigbee2MQTT:debug 2024-02-11 13:41:30: Received Zigbee message from '0x54ef441000684c5c', type 'readResponse', cluster 'genBasic', data '{"stackVersion":2}' from endpoint 1 with groupID 0
Zigbee2MQTT:debug 2024-02-11 13:41:30: Skipping message, still interviewing
Zigbee2MQTT:debug 2024-02-11 13:41:31: Received Zigbee message from '0x54ef441000684c5c', type 'attributeReport', cluster 'genPowerCfg', data '{"batteryVoltage":29}' from endpoint 1 with groupID 0
Zigbee2MQTT:debug 2024-02-11 13:41:31: Skipping message, still interviewing
Zigbee2MQTT:debug 2024-02-11 13:41:31: Received Zigbee message from '0x54ef441000684c5c', type 'attributeReport', cluster 'manuSpecificLumi', data '{"247":{"data":[1,33,123,11,3,40,20,4,33,168,1,5,33,95,0,6,36,12,0,0,0,0,8,33,29,1,10,33,0,0,12,32,1,100,41,27,8,101,33,90,20,102,33,6,0,103,32,1],"type":"Buffer"}}' from endpoint 1 with groupID 0
Zigbee2MQTT:debug 2024-02-11 13:41:31: Skipping message, still interviewing
Zigbee2MQTT:debug 2024-02-11 13:41:31: Received Zigbee message from '0x54ef441000684c5c', type 'readResponse', cluster 'genBasic', data '{"hwVersion":1}' from endpoint 1 with groupID 0
Zigbee2MQTT:debug 2024-02-11 13:41:31: Skipping message, still interviewing
Zigbee2MQTT:debug 2024-02-11 13:41:32: Received Zigbee message from '0x54ef441000684c5c', type 'readResponse', cluster 'genBasic', data '{"dateCode":"20220222"}' from endpoint 1 with groupID 0
Zigbee2MQTT:debug 2024-02-11 13:41:32: Skipping message, still interviewing
Zigbee2MQTT:debug 2024-02-11 13:41:33: Received Zigbee message from '0x54ef441000684c5c', type 'readResponse', cluster 'genBasic', data '{"swBuildId":"2020\u0000www."}' from endpoint 1 with groupID 0
Zigbee2MQTT:debug 2024-02-11 13:41:33: Skipping message, still interviewing
Zigbee2MQTT:debug 2024-02-11 13:41:34: Received Zigbee message from '0x54ef441000684c5c', type 'attributeReport', cluster 'manuSpecificLumi', data '{"247":{"data":[1,33,116,11,3,40,20,4,33,168,1,5,33,95,0,6,36,5,0,0,0,0,8,33,29,1,10,33,0,0,12,32,1,100,41,25,8,101,33,97,20,102,33,6,0,103,32,1],"type":"Buffer"}}' from endpoint 1 with groupID 0
Zigbee2MQTT:debug 2024-02-11 13:41:34: Skipping message, still interviewing
Zigbee2MQTT:debug 2024-02-11 13:41:40: Received Zigbee message from '0x54ef441000684c5c', type 'attributeReport', cluster 'genBasic', data '{"modelId":"lumi.airmonitor.acn01"}' from endpoint 1 with groupID 0
Zigbee2MQTT:debug 2024-02-11 13:41:40: Skipping message, still interviewing
Zigbee2MQTT:debug 2024-02-11 13:41:40: Received Zigbee message from '0x54ef441000684c5c', type 'attributeReport', cluster 'manuSpecificLumi', data '{"247":{"data":[1,33,116,11,3,40,20,4,33,168,1,5,33,95,0,6,36,2,0,0,0,0,8,33,29,1,10,33,0,0,12,32,1,100,41,34,8,101,33,63,20,102,33,6,0,103,32,1],"type":"Buffer"}}' from endpoint 1 with groupID 0
Zigbee2MQTT:debug 2024-02-11 13:41:40: Skipping message, still interviewing
Zigbee2MQTT:debug 2024-02-11 13:41:44: Received Zigbee message from '0x54ef441000684c5c', type 'attributeReport', cluster 'genBasic', data '{"modelId":"lumi.airmonitor.acn01"}' from endpoint 1 with groupID 0
Zigbee2MQTT:debug 2024-02-11 13:41:44: Skipping message, still interviewing
Zigbee2MQTT:debug 2024-02-11 13:41:44: Received Zigbee message from '0x54ef441000684c5c', type 'attributeReport', cluster 'manuSpecificLumi', data '{"247":{"data":[1,33,116,11,3,40,20,4,33,168,1,5,33,95,0,6,36,2,0,0,0,0,8,33,29,1,10,33,0,0,12,32,1,100,41,27,8,101,33,70,20,102,33,6,0,103,32,1],"type":"Buffer"}}' from endpoint 1 with groupID 0
Zigbee2MQTT:debug 2024-02-11 13:41:44: Skipping message, still interviewing
Zigbee2MQTT:debug 2024-02-11 13:41:48: Received Zigbee message from '0x54ef441000684c5c', type 'attributeReport', cluster 'genBasic', data '{"modelId":"lumi.airmonitor.acn01"}' from endpoint 1 with groupID 0
Zigbee2MQTT:debug 2024-02-11 13:41:48: Skipping message, still interviewing
Zigbee2MQTT:debug 2024-02-11 13:41:48: Received Zigbee message from '0x54ef441000684c5c', type 'attributeReport', cluster 'manuSpecificLumi', data '{"247":{"data":[1,33,116,11,3,40,20,4,33,168,1,5,33,95,0,6,36,3,0,0,0,0,8,33,29,1,10,33,0,0,12,32,1,100,41,27,8,101,33,80,20,102,33,6,0,103,32,1],"type":"Buffer"}}' from endpoint 1 with groupID 0
Zigbee2MQTT:debug 2024-02-11 13:41:48: Skipping message, still interviewing
Zigbee2MQTT:debug 2024-02-11 13:41:52: Received Zigbee message from '0x54ef441000684c5c', type 'attributeReport', cluster 'genBasic', data '{"modelId":"lumi.airmonitor.acn01"}' from endpoint 1 with groupID 0
Zigbee2MQTT:debug 2024-02-11 13:41:52: Skipping message, still interviewing
Zigbee2MQTT:debug 2024-02-11 13:41:52: Received Zigbee message from '0x54ef441000684c5c', type 'attributeReport', cluster 'manuSpecificLumi', data '{"247":{"data":[1,33,116,11,3,40,20,4,33,168,1,5,33,95,0,6,36,2,0,0,0,0,8,33,29,1,10,33,0,0,12,32,1,100,41,27,8,101,33,102,20,102,33,6,0,103,32,1],"type":"Buffer"}}' from endpoint 1 with groupID 0
Zigbee2MQTT:debug 2024-02-11 13:41:52: Skipping message, still interviewing
Zigbee2MQTT:debug 2024-02-11 13:41:55: Received Zigbee message from '0x54ef441000684c5c', type 'attributeReport', cluster 'genBasic', data '{"modelId":"lumi.airmonitor.acn01"}' from endpoint 1 with groupID 0
Zigbee2MQTT:debug 2024-02-11 13:41:55: Skipping message, still interviewing
Zigbee2MQTT:debug 2024-02-11 13:41:55: Received Zigbee message from '0x54ef441000684c5c', type 'attributeReport', cluster 'manuSpecificLumi', data '{"247":{"data":[1,33,116,11,3,40,20,4,33,168,1,5,33,95,0,6,36,2,0,0,0,0,8,33,29,1,10,33,0,0,12,32,1,100,41,29,8,101,33,92,20,102,33,6,0,103,32,1],"type":"Buffer"}}' from endpoint 1 with groupID 0
Zigbee2MQTT:debug 2024-02-11 13:41:55: Skipping message, still interviewing
Zigbee2MQTT:info 2024-02-11 13:41:58: Successfully interviewed '0x54ef441000684c5c', device has successfully been paired
Zigbee2MQTT:info 2024-02-11 13:41:58: Device '0x54ef441000684c5c' is supported, identified as: Aqara TVOC air quality monitor (VOCKQJK11LM)
Zigbee2MQTT:info 2024-02-11 13:41:58: MQTT publish: topic 'zigbee2mqtt/bridge/event', payload '{"data":{"definition":{"description":"TVOC air quality monitor","exposes":[{"access":1,"category":"diagnostic","description":"Temperature of the device","label":"Device temperature","name":"device_temperature","property":"device_temperature","type":"numeric","unit":"°C"},{"access":1,"category":"diagnostic","description":"Remaining battery in %, can take up to 24 hours before reported","label":"Battery","name":"battery","property":"battery","type":"numeric","unit":"%","value_max":100,"value_min":0},{"access":1,"category":"diagnostic","description":"Voltage of the battery in millivolts","label":"Voltage","name":"voltage","property":"voltage","type":"numeric","unit":"mV"},{"access":5,"description":"Measured air quality","label":"Air quality","name":"air_quality","property":"air_quality","type":"enum","values":["excellent","good","moderate","poor","unhealthy","unknown"]},{"access":5,"description":"Measured VOC value","label":"Voc","name":"voc","property":"voc","type":"numeric","unit":"ppb"},{"access":5,"description":"Measured temperature value","label":"Temperature","name":"temperature","property":"temperature","type":"numeric","unit":"°C"},{"access":5,"description":"Measured relative humidity","label":"Humidity","name":"humidity","property":"humidity","type":"numeric","unit":"%"},{"access":7,"description":"Units to show on the display","label":"Display unit","name":"display_unit","property":"display_unit","type":"enum","values":["mgm3_celsius","ppb_celsius","mgm3_fahrenheit","ppb_fahrenheit"]},{"access":1,"category":"diagnostic","description":"Link quality (signal strength)","label":"Linkquality","name":"linkquality","property":"linkquality","type":"numeric","unit":"lqi","value_max":255,"value_min":0}],"model":"VOCKQJK11LM","options":[{"access":2,"description":"Calibrates the device_temperature value (absolute offset), takes into effect on next report of device.","label":"Device temperature calibration","name":"device_temperature_calibration","property":"device_temperature_calibration","type":"numeric"},{"access":2,"description":"Calibrates the voc value (absolute offset), takes into effect on next report of device.","label":"Voc calibration","name":"voc_calibration","property":"voc_calibration","type":"numeric"},{"access":2,"description":"Calibrates the temperature value (absolute offset), takes into effect on next report of device.","label":"Temperature calibration","name":"temperature_calibration","property":"temperature_calibration","type":"numeric"},{"access":2,"description":"Number of digits after decimal point for temperature, takes into effect on next report of device. This option can only decrease the precision, not increase it.","label":"Temperature precision","name":"temperature_precision","property":"temperature_precision","type":"numeric","value_max":3,"value_min":0},{"access":2,"description":"Calibrates the humidity value (absolute offset), takes into effect on next report of device.","label":"Humidity calibration","name":"humidity_calibration","property":"humidity_calibration","type":"numeric"},{"access":2,"description":"Number of digits after decimal point for humidity, takes into effect on next report of device. This option can only decrease the precision, not increase it.","label":"Humidity precision","name":"humidity_precision","property":"humidity_precision","type":"numeric","value_max":3,"value_min":0}],"supports_ota":true,"vendor":"Aqara"},"friendly_name":"0x54ef441000684c5c","ieee_address":"0x54ef441000684c5c","status":"successful","supported":true},"type":"device_interview"}'
Zigbee2MQTT:info 2024-02-11 13:41:58: Configuring '0x54ef441000684c5c'
Zigbee2MQTT:debug 2024-02-11 13:41:58: Received Zigbee message from '0x54ef441000684c5c', type 'attributeReport', cluster 'genBasic', data '{"modelId":"lumi.airmonitor.acn01"}' from endpoint 1 with groupID 0
Zigbee2MQTT:debug 2024-02-11 13:41:58: Received Zigbee message from '0x54ef441000684c5c', type 'attributeReport', cluster 'manuSpecificLumi', data '{"247":{"data":[1,33,116,11,3,40,20,4,33,168,1,5,33,95,0,6,36,3,0,0,0,0,8,33,29,1,10,33,0,0,12,32,1,100,41,28,8,101,33,101,20,102,33,6,0,103,32,1],"type":"Buffer"}}' from endpoint 1 with groupID 0
Zigbee2MQTT:debug 2024-02-11 13:41:58: VOCKQJK11LM: Processed buffer into data {"1":2932,"3":20,"4":424,"5":95,"6":3,"8":285,"10":0,"12":1,"100":2076,"101":5221,"102":6,"103":1}
Zigbee2MQTT:debug 2024-02-11 13:41:58: VOCKQJK11LM: unknown key 6 with value 3
Zigbee2MQTT:debug 2024-02-11 13:41:58: VOCKQJK11LM: Processed data into payload {"voltage":2932,"battery":55,"device_temperature":20,"power_outage_count":94,"temperature":20.76,"humidity":52.21}
Zigbee2MQTT:debug 2024-02-11 13:41:58: VOCKQJK11LM: Processed data into payload {"voltage":2932,"battery":55,"device_temperature":20,"power_outage_count":94,"temperature":20.76,"humidity":52.21}
Zigbee2MQTT:debug 2024-02-11 13:41:58: VOCKQJK11LM: Processed buffer into data {"1":2932,"3":20,"4":424,"5":95,"6":3,"8":285,"10":0,"12":1,"100":2076,"101":5221,"102":6,"103":1}
Zigbee2MQTT:debug 2024-02-11 13:41:58: Restoring binding and reporting, device came back after losing power.
Zigbee2MQTT:info 2024-02-11 13:41:58: MQTT publish: topic 'zigbee2mqtt/0x54ef441000684c5c', payload '{"battery":55,"device_temperature":20,"humidity":52.21,"linkquality":193,"power_outage_count":94,"temperature":20.76,"voltage":2932}'
Zigbee2MQTT:debug 2024-02-11 13:42:00: Received Zigbee message from '0x54ef441000684c5c', type 'attributeReport', cluster 'genPowerCfg', data '{"batteryVoltage":29}' from endpoint 1 with groupID 0
Zigbee2MQTT:info 2024-02-11 13:42:00: MQTT publish: topic 'zigbee2mqtt/0x54ef441000684c5c', payload '{"battery":33,"device_temperature":20,"humidity":52.21,"linkquality":189,"power_outage_count":94,"temperature":20.76,"voltage":2900}'
Zigbee2MQTT:debug 2024-02-11 13:42:02: Received Zigbee message from '0x54ef441000684c5c', type 'readResponse', cluster 'genPowerCfg', data '{"batteryVoltage":29}' from endpoint 1 with groupID 0
Zigbee2MQTT:info 2024-02-11 13:42:02: MQTT publish: topic 'zigbee2mqtt/0x54ef441000684c5c', payload '{"battery":33,"device_temperature":20,"humidity":52.21,"linkquality":193,"power_outage_count":94,"temperature":20.76,"voltage":2900}'
Zigbee2MQTT:debug 2024-02-11 13:42:02: Quirk: adding input cluster 1026 to endpoint 1.
Zigbee2MQTT:debug 2024-02-11 13:42:02: Quirk: adding input cluster 1029 to endpoint 1.
Zigbee2MQTT:debug 2024-02-11 13:42:02: Quirk: adding input cluster 12 to endpoint 1.
Zigbee2MQTT:debug 2024-02-11 13:42:02: Quirk: adding input cluster 64704 to endpoint 1.
Zigbee2MQTT:debug 2024-02-11 13:42:02: Configure reporting: false, read: true for 0x54ef441000684c5c/1 manuSpecificLumi [{"attribute":"airQuality","min":-1,"max":-1,"change":-1}]
Zigbee2MQTT:debug 2024-02-11 13:42:03: Received Zigbee message from '0x54ef441000684c5c', type 'readResponse', cluster 'manuSpecificLumi', data '{"airQuality":1}' from endpoint 1 with groupID 0
Zigbee2MQTT:debug 2024-02-11 13:42:03: VOCKQJK11LM: Processed data into payload {}
Zigbee2MQTT:info 2024-02-11 13:42:03: MQTT publish: topic 'zigbee2mqtt/0x54ef441000684c5c', payload '{"air_quality":"excellent","battery":33,"device_temperature":20,"humidity":52.21,"linkquality":193,"power_outage_count":94,"temperature":20.76,"voltage":2900}'
Zigbee2MQTT:debug 2024-02-11 13:42:03: Configure reporting: true, read: true for 0x54ef441000684c5c/1 genAnalogInput [{"min":"10_SECONDS","max":"1_HOUR","change":5,"attribute":"presentValue"}]
Zigbee2MQTT:debug 2024-02-11 13:42:06: Received Zigbee message from '0x54ef441000684c5c', type 'readResponse', cluster 'genAnalogInput', data '{"presentValue":0}' from endpoint 1 with groupID 0
Zigbee2MQTT:info 2024-02-11 13:42:06: MQTT publish: topic 'zigbee2mqtt/0x54ef441000684c5c', payload '{"air_quality":"excellent","battery":33,"device_temperature":20,"humidity":52.21,"linkquality":193,"power_outage_count":94,"temperature":20.76,"voc":0,"voltage":2900}'
Zigbee2MQTT:debug 2024-02-11 13:42:06: Configure reporting: true, read: true for 0x54ef441000684c5c/1 msTemperatureMeasurement [{"min":"10_SECONDS","max":"1_HOUR","change":100,"attribute":"measuredValue"}]
Zigbee2MQTT:debug 2024-02-11 13:42:09: Received Zigbee message from '0x54ef441000684c5c', type 'attributeReport', cluster 'msTemperatureMeasurement', data '{"measuredValue":2073}' from endpoint 1 with groupID 0
Zigbee2MQTT:info 2024-02-11 13:42:09: MQTT publish: topic 'zigbee2mqtt/0x54ef441000684c5c', payload '{"air_quality":"excellent","battery":33,"device_temperature":20,"humidity":52.21,"linkquality":193,"power_outage_count":94,"temperature":20.73,"voc":0,"voltage":2900}'
Zigbee2MQTT:debug 2024-02-11 13:42:09: Received Zigbee message from '0x54ef441000684c5c', type 'attributeReport', cluster 'manuSpecificLumi', data '{"airQuality":1}' from endpoint 1 with groupID 0
Zigbee2MQTT:debug 2024-02-11 13:42:09: VOCKQJK11LM: Processed data into payload {}
Zigbee2MQTT:info 2024-02-11 13:42:09: MQTT publish: topic 'zigbee2mqtt/0x54ef441000684c5c', payload '{"air_quality":"excellent","battery":33,"device_temperature":20,"humidity":52.21,"linkquality":193,"power_outage_count":94,"temperature":20.73,"voc":0,"voltage":2900}'
Zigbee2MQTT:debug 2024-02-11 13:42:09: Received Zigbee message from '0x54ef441000684c5c', type 'attributeReport', cluster 'genAnalogInput', data '{"presentValue":8}' from endpoint 1 with groupID 0
Zigbee2MQTT:info 2024-02-11 13:42:09: MQTT publish: topic 'zigbee2mqtt/0x54ef441000684c5c', payload '{"air_quality":"excellent","battery":33,"device_temperature":20,"humidity":52.21,"linkquality":193,"power_outage_count":94,"temperature":20.73,"voc":8,"voltage":2900}'
Zigbee2MQTT:debug 2024-02-11 13:42:10: Received Zigbee message from '0x54ef441000684c5c', type 'readResponse', cluster 'msTemperatureMeasurement', data '{"measuredValue":2078}' from endpoint 1 with groupID 0
Zigbee2MQTT:info 2024-02-11 13:42:10: MQTT publish: topic 'zigbee2mqtt/0x54ef441000684c5c', payload '{"air_quality":"excellent","battery":33,"device_temperature":20,"humidity":52.21,"linkquality":193,"power_outage_count":94,"temperature":20.78,"voc":8,"voltage":2900}'
Zigbee2MQTT:debug 2024-02-11 13:42:10: Configure reporting: true, read: true for 0x54ef441000684c5c/1 msRelativeHumidity [{"min":"10_SECONDS","max":"1_HOUR","change":100,"attribute":"measuredValue"}]
Zigbee2MQTT:debug 2024-02-11 13:42:12: Received Zigbee message from '0x54ef441000684c5c', type 'attributeReport', cluster 'msRelativeHumidity', data '{"measuredValue":5211}' from endpoint 1 with groupID 0
Zigbee2MQTT:info 2024-02-11 13:42:12: MQTT publish: topic 'zigbee2mqtt/0x54ef441000684c5c', payload '{"air_quality":"excellent","battery":33,"device_temperature":20,"humidity":52.11,"linkquality":204,"power_outage_count":94,"temperature":20.78,"voc":8,"voltage":2900}'
Zigbee2MQTT:debug 2024-02-11 13:42:13: Received Zigbee message from '0x54ef441000684c5c', type 'readResponse', cluster 'msRelativeHumidity', data '{"measuredValue":5211}' from endpoint 1 with groupID 0
Zigbee2MQTT:info 2024-02-11 13:42:13: MQTT publish: topic 'zigbee2mqtt/0x54ef441000684c5c', payload '{"air_quality":"excellent","battery":33,"device_temperature":20,"humidity":52.11,"linkquality":207,"power_outage_count":94,"temperature":20.78,"voc":8,"voltage":2900}'
Zigbee2MQTT:debug 2024-02-11 13:42:13: Configure reporting: false, read: true for 0x54ef441000684c5c/1 manuSpecificLumi [{"attribute":"displayUnit","min":-1,"max":-1,"change":-1}]
Zigbee2MQTT:debug 2024-02-11 13:42:14: Received Zigbee message from '0x54ef441000684c5c', type 'readResponse', cluster 'manuSpecificLumi', data '{"displayUnit":1}' from endpoint 1 with groupID 0
Zigbee2MQTT:debug 2024-02-11 13:42:14: VOCKQJK11LM: Processed data into payload {}
Zigbee2MQTT:info 2024-02-11 13:42:14: MQTT publish: topic 'zigbee2mqtt/0x54ef441000684c5c', payload '{"air_quality":"excellent","battery":33,"device_temperature":20,"display_unit":"ppb_celsius","humidity":52.11,"linkquality":211,"power_outage_count":94,"temperature":20.78,"voc":8,"voltage":2900}'
Zigbee2MQTT:info 2024-02-11 13:42:14: Successfully configured '0x54ef441000684c5c'
Zigbee2MQTT:debug 2024-02-11 13:42:16: Received Zigbee message from '0x54ef441000684c5c', type 'attributeReport', cluster 'genAnalogInput', data '{"presentValue":8}' from endpoint 1 with groupID 0
Zigbee2MQTT:info 2024-02-11 13:42:16: MQTT publish: topic 'zigbee2mqtt/0x54ef441000684c5c', payload '{"air_quality":"excellent","battery":33,"device_temperature":20,"display_unit":"ppb_celsius","humidity":52.11,"linkquality":200,"power_outage_count":94,"temperature":20.78,"voc":8,"voltage":2900}'Still seems to work fine, I'm using a zzh adaptor with 20220928 fw release.
You do have to occasionally use the button to keep it awake until it finishes everything.
sjorge
commented
9 months ago Actually I noticed you're not pairing but z2m is probably trying to trigger a reconfigure at startup.
zh also got this change https://github.com/Koenkk/zigbee-herdsman/commit/2d3a5d1d25f45360e253946d26f4e8b95ea75e26 this release, I only have this specific device but it is missing a genPollCtrl cluster (shame) which means it z2m will now try to immediately send the messages. Before it would only do it when we got a message from the device.
The device is probably not 'awake' which explains the lack of response to the bind on genPowerCfg. I added a quirk that restores the old behavior here https://github.com/Koenkk/zigbee-herdsman-converters/pull/6840, this later got refactored a few time to end up with this https://github.com/Koenkk/zigbee-herdsman-converters/blob/36a31e8bab8ce6b9cba29698f1ae1df4a5a734b8/src/devices/lumi.ts#L2904. Without this quirk I was no longer able to pair after the herdman change landed.
Of course this required configure to have run at least once for the extra database entry to be present. You could try keeping the device awake by pressing the top button every 2-3 seconds and hitting the reconfigure button in the UI.
satter
commented
8 months ago My Aqara VOCKQJK11LM sensor is being reconfigured each time after Z2M upgrade generating bunch of errors in logs:
Mar 09 08:51:09 homie1 npm[1921529]: Zigbee2MQTT:error 2024-03-09 08:51:09: Publish 'get' 'humidity' to 'kitchen/aqara_tvoc1' failed: 'Error: Read 0x54ef441000106dca/1 msRelativeHumidity(["measuredValue"], {"timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":true,"direction":0,"srcEndpoint":null,"reservedBits":0,"manufacturerCode":null,"transactionSequenceNumber":null,"writeUndiv":false}) failed (Timeout - 54748 - 1 - 12 - 1029 - 1 after 10000ms)'
Mar 09 08:51:32 homie1 npm[1921529]: Zigbee2MQTT:error 2024-03-09 08:51:32: Publish 'get' 'temperature' to 'kitchen/aqara_tvoc1' failed: 'Error: Read 0x54ef441000106dca/1 msTemperatureMeasurement(["measuredValue"], {"timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":true,"direction":0,"srcEndpoint":null,"reservedBits":0,"manufacturerCode":null,"transactionSequenceNumber":null,"writeUndiv":false}) failed (Timeout - 54748 - 1 - 26 - 1026 - 1 after 10000ms)'
Mar 09 08:51:55 homie1 npm[1921529]: Zigbee2MQTT:error 2024-03-09 08:51:55: Publish 'get' 'voc' to 'kitchen/aqara_tvoc1' failed: 'Error: Read 0x54ef441000106dca/1 genAnalogInput(["presentValue"], {"timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":true,"direction":0,"srcEndpoint":null,"reservedBits":0,"manufacturerCode":null,"transactionSequenceNumber":null,"writeUndiv":false}) failed (Timeout - 54748 - 1 - 27 - 12 - 1 after 10000ms)'
Mar 09 09:26:47 homie1 npm[1921529]: Zigbee2MQTT:error 2024-03-09 09:26:47: Failed to configure 'kitchen/aqara_tvoc1', attempt 1 (Error: Bind 0x54ef441000106dca/1 msTemperatureMeasurement from '0x00124b00258d3c29/1' failed (AREQ - ZDO - bindRsp after 10000ms)
Mar 09 09:30:35 homie1 npm[1921529]: Zigbee2MQTT:error 2024-03-09 09:30:35: Failed to configure 'kitchen/aqara_tvoc1', attempt 2 (Error: Bind 0x54ef441000106dca/1 msTemperatureMeasurement from '0x00124b00258d3c29/1' failed (AREQ - ZDO - bindRsp after 10000ms)Manual reconfiguration works after I wake up the sensor with button. After that no more errors until next Z2M upgrade
sjorge
commented
8 months ago Wake up the device so it can finish a reconfigure. It never completes due to a timeout.
So z2m will try again later.
satter
commented
8 months ago Yes, wake up and reconfigure works fine
Is it OK for this device to be reconfigured after each Z2M upgrade?
satter
commented
8 months ago I've also noticed missing sensors data from dashboard tile:
I'm not sure when this changed, but some time before there was other sensors like humidity and VOC
The 'exposes' tab seems to be fine:
sjorge
commented
8 months ago The last 3 updates there were some changes to the device, so if there are no updates it should no reconfigure. But there were a few recently so that is probably why it tries to on the last few release. Some of changes:
All of those would have triggered a reconfigure. The latest stable added some changes where it doesn't try to reconfigure battery devices on startup. So if there are further changes that trigger a reconfigure it should not immediately result in errors at startup. That was not a Aqara specifc problem, it was causing issues for all devices that are battery powered and lacking the genPollCtrl cluster.
satter
commented
8 months ago @sjorge thanks for the detailed explanation! I've seen my sensors, including this one from Aqara, reconfiguring after an upgrade before, but there were no errors during this process.
I've also noticed weird battery readings on version 1.35.3, which seem to have stopped on version 1.36.0 today.
I will replace the batteries anyway and check for errors during the next upgrade
satter
commented
7 months ago I upgraded to version 1.36.1 today, and the dashboard still lacks every sensor except for the device temperature There were several one-time errors shortly after startup:
debug 2024-04-29 13:38:44: Received MQTT message on 'zigbee2mqtt/0x54ef441000106dca/get' with data '{"humidity":0,"temperature":0,"voc":0}'
debug 2024-04-29 13:38:44: Publishing get 'get' 'humidity' to 'kitchen/aqara_tvoc1'
error 2024-04-29 13:39:07: Publish 'get' 'humidity' to 'kitchen/aqara_tvoc1' failed: 'Error: ZCL command 0x54ef441000106dca/1 msRelativeHumidity.read(["measuredValue"], {"timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":true,"direction":0,"srcEndpoint":null,"reservedBits":0,"manufacturerCode":null,"transactionSequenceNumber":null,"writeUndiv":false}) failed (Timeout - 54748 - 1 - 30 - 1029 - 1 after 10000ms)'
debug 2024-04-29 13:39:07: Error: ZCL command 0x54ef441000106dca/1 msRelativeHumidity.read(["measuredValue"], {"timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":true,"direction":0,"srcEndpoint":null,"reservedBits":0,"manufacturerCode":null,"transactionSequenceNumber":null,"writeUndiv":false}) failed (Timeout - 54748 - 1 - 30 - 1029 - 1 after 10000ms)
debug 2024-04-29 13:39:07: Publishing get 'get' 'temperature' to 'kitchen/aqara_tvoc1'
error 2024-04-29 13:39:30: Publish 'get' 'temperature' to 'kitchen/aqara_tvoc1' failed: 'Error: ZCL command 0x54ef441000106dca/1 msTemperatureMeasurement.read(["measuredValue"], {"timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":true,"direction":0,"srcEndpoint":null,"reservedBits":0,"manufacturerCode":null,"transactionSequenceNumber":null,"writeUndiv":false}) failed (Timeout - 54748 - 1 - 44 - 1026 - 1 after 10000ms)'
debug 2024-04-29 13:39:30: Error: ZCL command 0x54ef441000106dca/1 msTemperatureMeasurement.read(["measuredValue"], {"timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":true,"direction":0,"srcEndpoint":null,"reservedBits":0,"manufacturerCode":null,"transactionSequenceNumber":null,"writeUndiv":false}) failed (Timeout - 54748 - 1 - 44 - 1026 - 1 after 10000ms)
debug 2024-04-29 13:39:30: Publishing get 'get' 'voc' to 'kitchen/aqara_tvoc1'
error 2024-04-29 13:39:53: Publish 'get' 'voc' to 'kitchen/aqara_tvoc1' failed: 'Error: ZCL command 0x54ef441000106dca/1 genAnalogInput.read(["presentValue"], {"timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":true,"direction":0,"srcEndpoint":null,"reservedBits":0,"manufacturerCode":null,"transactionSequenceNumber":null,"writeUndiv":false}) failed (Timeout - 54748 - 1 - 45 - 12 - 1 after 10000ms)'
debug 2024-04-29 13:39:53: Error: ZCL command 0x54ef441000106dca/1 genAnalogInput.read(["presentValue"], {"timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":true,"direction":0,"srcEndpoint":null,"reservedBits":0,"manufacturerCode":null,"transactionSequenceNumber":null,"writeUndiv":false}) failed (Timeout - 54748 - 1 - 45 - 12 - 1 after 10000ms)
Koenkk
commented
7 months ago The next z2m release will fix the dashboard issues.
github-actions[bot]
commented
1 month ago This issue is stale because it has been open 180 days with no activity. Remove stale label or comment or this will be closed in 30 days
What happened?
Failed to configure
What did you expect to happen?
No response
How to reproduce it (minimal and precise)
No response
Zigbee2MQTT version
1.35.2-1
Adapter firmware version
20221226
Adapter
Sonoff P
Setup
ADDONS HOME ASSISTANT
Debug log
Error 2024-02-05 02:27:59Failed to configure 'Thermomètre Salon', attempt 3 (Error: Bind 0x54ef441000357ab6/1 genPowerCfg from '0x00124b002a2ec244/1' failed (AREQ - ZDO - bindRsp after 10000ms) at Object.start (/app/node_modules/zigbee-herdsman/src/utils/waitress.ts:63:23) at /app/node_modules/zigbee-herdsman/src/adapter/z-stack/adapter/zStackAdapter.ts:692:28 at Queue.execute (/app/node_modules/zigbee-herdsman/src/utils/queue.ts:35:20) at Endpoint.bind (/app/node_modules/zigbee-herdsman/src/controller/model/endpoint.ts:551:13) at Object.bind (/app/node_modules/zigbee-herdsman-converters/src/lib/reporting.ts:43:9) at configure (/app/node_modules/zigbee-herdsman-converters/src/devices/lumi.ts:2924:13) at Object.configure (/app/node_modules/zigbee-herdsman-converters/src/index.ts:140:25) at Configure.configure (/app/lib/extension/configure.ts:120:13) at EventEmitter.wrappedCallback (/app/lib/eventBus.ts:174:17))