Data request failed with error mac channel access failure

Today I restarted from scratch, with the zigbee2mqtt network setup. Currenty stable release, with HA on Raspi4 Now I get the error below "MAC channel acces.." Everything worked so far (I ...

Today I restarted from scratch, with the zigbee2mqtt network setup.

  • Currenty stable release, with HA on Raspi4

Now I get the error below «MAC channel acces..»

Everything worked so far (I setup 4 lights, one motion sensor and a switch), then I need to hard reset HomeAssistant,
after that i see that everything which needs «writing» to the zigbee stick seems stopped working.

  • the switch works, which means the log file shows that they are pressed
  • the lights announce themself,

Thus reading from the slaesh stick (current fw) works.

As soon if I want to write something for example :

  • Light «Wohn1_GU10» on/off I get this MAC error.

If I put the stick into another computer and start a standalone instance «npm start» switching the lights work.
So its not the stick.

Here is the log from power on «Wohn1_GU10» and then issue an power on/off from the zeigbee webgui.

MQTT publish: topic ‘zigbee2mqtt/bridge/event’, payload ‘{«data»:
{«friendly_name»:»Wohn1_GU10″,»ieee_address»:»0x000b57fffea6e9f1″},»type»:»device_announce»}’
info MQTT publish: topic ‘zigbee2mqtt/bridge/log’, payload ‘{«message»:»announce»,»meta»:
{«friendly_name»:»Wohn1_GU10″},»type»:»device_announced»}’
debug Device ‘0x0017880102139444’ announced itself
MQTT publish: topic ‘zigbee2mqtt/bridge/log’, payload ‘{«message»:»announce»,»meta»:{«friendly_name»:»0x0017880102139444″},»type»:»device_announced»}’
debug Received MQTT message on ‘zigbee2mqtt/Wohn1_GU10/set’ with data ‘{«state»:»OFF»}’
debug Publishing ‘set’ ‘state’ to ‘Wohn1_GU10’
error Publish ‘set’ ‘state’ to ‘Wohn1_GU10’ failed: ‘Error: Command 0x000b57fffea6e9f1/1 genOnOff.off({},
{«timeout»:10000,»disableResponse»:false,»disableRecovery»:false,»disableDefaultResponse»:false,»direction»:0,»srcEndpoint»:null,»reservedBits»:0,»manufacturerCode»:null,»transactionSequenc
failed (** Data request failed with error: ‘MAC channel access failure’ (225)) **

Источник

Bug Report

What happened

This problem repeated twice by now, reinstalling Home Assistant from scratch.
When trying to change state on any switch/ligth I am getting this error:

Publish ‘set’ ‘state’ to ‘0x7cb03eaa0a01b20d’ failed: ‘Error: Data request failed with error: ‘MAC channel access failure’ (225)’

Seems like it is affecting all router devices, all battery operated devices keep operating.

What did you expect to happen

Switch should work, light should shine

How to reproduce it (minimal and precise)

I have setup hassio over Open Media Valult with installation script.
I have paired my devices — xiaomi sensors (battery operated) such as temperature, door opening, movement.
I have paired lights — Gledopto controllers.
I have paired Osram Smart + plug
I have paired Philips plug

Waited 2 days (few restarts in middle)

Now only battery operating devices are alived.

THis happened 2 times already.
I have moved stick from one port to another in raspberry — would be strange if related (Xiaomi devices work happilly)

Debug Info

zigbee2mqtt version:
1.7.1
CC253X firmware version:
20190608, here is initializing line:
zigbee2mqtt:info 2019-11-29T12:42:42: MQTT publish: topic ‘zigbee2mqtt/bridge/config’, payload ‘{«version»:»1.7.1″,»commit»:»unknown»,»coordinator»:{«type»:»zStack12″,»meta»:{«transportrev»:2,»product»:0,»majorrel»:2,»minorrel»:6,»maintrel»:3,»revision»:20190608}},»log_level»:»debug»,»permit_join»:true}’

Here is my startup log:

zigbee2mqtt:warn 2019-11-29T12:42:41: Allowing new devices to join.
zigbee2mqtt:warn 2019-11-29T12:42:41: Set permit_join to false once you joined all devices.
zigbee2mqtt:info 2019-11-29T12:42:41: Zigbee: allowing new devices to join.
zigbee2mqtt:info 2019-11-29T12:42:41: Connecting to MQTT server at mqtt://core-mosquitto
zigbee2mqtt:info 2019-11-29T12:42:42: Connected to MQTT server
zigbee2mqtt:info 2019-11-29T12:42:42: MQTT publish: topic ‘zigbee2mqtt/bridge/state’, payload ‘online’
zigbee2mqtt:info 2019-11-29T12:42:42: MQTT publish: topic ‘zigbee2mqtt/0x00158d0003cb1567’, payload ‘{«battery»:91,»voltage»:2985,»temperature»:22.87,»humidity»:58.7,»linkquality»:110}’
zigbee2mqtt:info 2019-11-29T12:42:42: MQTT publish: topic ‘zigbee2mqtt/0x00158d0003d49fa5’, payload ‘{«battery»:80,»voltage»:2965,»linkquality»:47,»contact»:false}’
zigbee2mqtt:info 2019-11-29T12:42:42: MQTT publish: topic ‘zigbee2mqtt/0x001788010804158f’, payload ‘{«state»:»ON»,»linkquality»:78}’
zigbee2mqtt:info 2019-11-29T12:42:42: MQTT publish: topic ‘zigbee2mqtt/0x7cb03eaa0a01b20d’, payload ‘{«state»:»ON»,»linkquality»:68}’
zigbee2mqtt:info 2019-11-29T12:42:42: MQTT publish: topic ‘zigbee2mqtt/0x00124b001ead90e9’, payload ‘{«state»:»OFF»}’
zigbee2mqtt:info 2019-11-29T12:42:42: MQTT publish: topic ‘zigbee2mqtt/0x00158d00044d5e6b’, payload ‘{«battery»:100,»voltage»:3015,»linkquality»:76,»contact»:false}’
zigbee2mqtt:info 2019-11-29T12:42:42: MQTT publish: topic ‘zigbee2mqtt/0x00124b001d43cbed’, payload ‘{«state»:»OFF»,»brightness»:67,»color»:{«x»:0.581,»y»:0.388},»color_temp»:162}’
zigbee2mqtt:info 2019-11-29T12:42:42: MQTT publish: topic ‘zigbee2mqtt/0x00158d00044db511’, payload ‘{«battery»:100,»voltage»:3035,»temperature»:23.45,»humidity»:55.02,»pressure»:1014,»linkquality»:68}’
zigbee2mqtt:info 2019-11-29T12:42:42: MQTT publish: topic ‘zigbee2mqtt/bridge/config’, payload ‘{«version»:»1.7.1″,»commit»:»unknown»,»coordinator»:{«type»:»zStack12″,»meta»:{«transportrev»:2,»product»:0,»majorrel»:2,»minorrel»:6,»maintrel»:3,»revision»:20190608}},»log_level»:»debug»,»permit_join»:true}’
zigbee2mqtt:info 2019-11-29T12:42:42: MQTT publish: topic ‘homeassistant/sensor/0x00158d0003cb1567/temperature/config’, payload ‘{«unit_of_measurement»:»°C»,»device_class»:»temperature»,»value_template»:»{{ value_json.temperature }}»,»state_topic»:»zigbee2mqtt/0x00158d0003cb1567″,»json_attributes_topic»:»zigbee2mqtt/0x00158d0003cb1567″,»name»:»0x00158d0003cb1567_temperature»,»unique_id»:»0x00158d0003cb1567_temperature_zigbee2mqtt»,»device»:{«identifiers»:[«zigbee2mqtt_0x00158d0003cb1567″],»name»:»0x00158d0003cb1567″,»sw_version»:»Zigbee2mqtt 1.7.1″,»model»:»MiJia temperature & humidity sensor (WSDCGQ01LM)»,»manufacturer»:»Xiaomi»},»availability_topic»:»zigbee2mqtt/bridge/state»}’
zigbee2mqtt:info 2019-11-29T12:42:42: MQTT publish: topic ‘homeassistant/sensor/0x00158d0003cb1567/humidity/config’, payload ‘{«unit_of_measurement»:»%»,»device_class»:»humidity»,»value_template»:»{{ value_json.humidity }}»,»state_topic»:»zigbee2mqtt/0x00158d0003cb1567″,»json_attributes_topic»:»zigbee2mqtt/0x00158d0003cb1567″,»name»:»0x00158d0003cb1567_humidity»,»unique_id»:»0x00158d0003cb1567_humidity_zigbee2mqtt»,»device»:{«identifiers»:[«zigbee2mqtt_0x00158d0003cb1567″],»name»:»0x00158d0003cb1567″,»sw_version»:»Zigbee2mqtt 1.7.1″,»model»:»MiJia temperature & humidity sensor (WSDCGQ01LM)»,»manufacturer»:»Xiaomi»},»availability_topic»:»zigbee2mqtt/bridge/state»}’
zigbee2mqtt:info 2019-11-29T12:42:42: MQTT publish: topic ‘homeassistant/sensor/0x00158d0003cb1567/battery/config’, payload ‘{«unit_of_measurement»:»%»,»device_class»:»battery»,»value_template»:»{{ value_json.battery }}»,»state_topic»:»zigbee2mqtt/0x00158d0003cb1567″,»json_attributes_topic»:»zigbee2mqtt/0x00158d0003cb1567″,»name»:»0x00158d0003cb1567_battery»,»unique_id»:»0x00158d0003cb1567_battery_zigbee2mqtt»,»device»:{«identifiers»:[«zigbee2mqtt_0x00158d0003cb1567″],»name»:»0x00158d0003cb1567″,»sw_version»:»Zigbee2mqtt 1.7.1″,»model»:»MiJia temperature & humidity sensor (WSDCGQ01LM)»,»manufacturer»:»Xiaomi»},»availability_topic»:»zigbee2mqtt/bridge/state»}’
zigbee2mqtt:info 2019-11-29T12:42:42: MQTT publish: topic ‘homeassistant/sensor/0x00158d0003cb1567/linkquality/config’, payload ‘{«unit_of_measurement»:»-«,»value_template»:»{{ value_json.linkquality }}»,»state_topic»:»zigbee2mqtt/0x00158d0003cb1567″,»json_attributes_topic»:»zigbee2mqtt/0x00158d0003cb1567″,»name»:»0x00158d0003cb1567_linkquality»,»unique_id»:»0x00158d0003cb1567_linkquality_zigbee2mqtt»,»device»:{«identifiers»:[«zigbee2mqtt_0x00158d0003cb1567″],»name»:»0x00158d0003cb1567″,»sw_version»:»Zigbee2mqtt 1.7.1″,»model»:»MiJia temperature & humidity sensor (WSDCGQ01LM)»,»manufacturer»:»Xiaomi»},»availability_topic»:»zigbee2mqtt/bridge/state»}’
zigbee2mqtt:info 2019-11-29T12:42:42: MQTT publish: topic ‘homeassistant/binary_sensor/0x00158d0003d49fa5/contact/config’, payload ‘{«payload_on»:false,»payload_off»:true,»value_template»:»{{ value_json.contact }}»,»device_class»:»door»,»state_topic»:»zigbee2mqtt/0x00158d0003d49fa5″,»json_attributes_topic»:»zigbee2mqtt/0x00158d0003d49fa5″,»name»:»0x00158d0003d49fa5_contact»,»unique_id»:»0x00158d0003d49fa5_contact_zigbee2mqtt»,»device»:{«identifiers»:[«zigbee2mqtt_0x00158d0003d49fa5″],»name»:»0x00158d0003d49fa5″,»sw_version»:»Zigbee2mqtt 1.7.1″,»model»:»MiJia door & window contact sensor (MCCGQ01LM)»,»manufacturer»:»Xiaomi»},»availability_topic»:»zigbee2mqtt/bridge/state»}’
zigbee2mqtt:info 2019-11-29T12:42:42: MQTT publish: topic ‘homeassistant/sensor/0x00158d0003d49fa5/battery/config’, payload ‘{«unit_of_measurement»:»%»,»device_class»:»battery»,»value_template»:»{{ value_json.battery }}»,»state_topic»:»zigbee2mqtt/0x00158d0003d49fa5″,»json_attributes_topic»:»zigbee2mqtt/0x00158d0003d49fa5″,»name»:»0x00158d0003d49fa5_battery»,»unique_id»:»0x00158d0003d49fa5_battery_zigbee2mqtt»,»device»:{«identifiers»:[«zigbee2mqtt_0x00158d0003d49fa5″],»name»:»0x00158d0003d49fa5″,»sw_version»:»Zigbee2mqtt 1.7.1″,»model»:»MiJia door & window contact sensor (MCCGQ01LM)»,»manufacturer»:»Xiaomi»},»availability_topic»:»zigbee2mqtt/bridge/state»}’
zigbee2mqtt:info 2019-11-29T12:42:42: MQTT publish: topic ‘homeassistant/sensor/0x00158d0003d49fa5/linkquality/config’, payload ‘{«unit_of_measurement»:»-«,»value_template»:»{{ value_json.linkquality }}»,»state_topic»:»zigbee2mqtt/0x00158d0003d49fa5″,»json_attributes_topic»:»zigbee2mqtt/0x00158d0003d49fa5″,»name»:»0x00158d0003d49fa5_linkquality»,»unique_id»:»0x00158d0003d49fa5_linkquality_zigbee2mqtt»,»device»:{«identifiers»:[«zigbee2mqtt_0x00158d0003d49fa5″],»name»:»0x00158d0003d49fa5″,»sw_version»:»Zigbee2mqtt 1.7.1″,»model»:»MiJia door & window contact sensor (MCCGQ01LM)»,»manufacturer»:»Xiaomi»},»availability_topic»:»zigbee2mqtt/bridge/state»}’
zigbee2mqtt:info 2019-11-29T12:42:42: MQTT publish: topic ‘homeassistant/switch/0x001788010804158f/switch/config’, payload ‘{«payload_off»:»OFF»,»payload_on»:»ON»,»value_template»:»{{ value_json.state }}»,»command_topic»:»zigbee2mqtt/0x001788010804158f/set»,»state_topic»:»zigbee2mqtt/0x001788010804158f»,»name»:»0x001788010804158f_switch»,»unique_id»:»0x001788010804158f_switch_zigbee2mqtt»,»device»:{«identifiers»:[«zigbee2mqtt_0x001788010804158f»],»name»:»0x001788010804158f»,»sw_version»:»Zigbee2mqtt 1.7.1″,»model»:»Hue smart plug — EU (929002240401)»,»manufacturer»:»Philips»},»availability_topic»:»zigbee2mqtt/bridge/state»}’
zigbee2mqtt:info 2019-11-29T12:42:42: MQTT publish: topic ‘homeassistant/sensor/0x001788010804158f/linkquality/config’, payload ‘{«unit_of_measurement»:»-«,»value_template»:»{{ value_json.linkquality }}»,»state_topic»:»zigbee2mqtt/0x001788010804158f»,»json_attributes_topic»:»zigbee2mqtt/0x001788010804158f»,»name»:»0x001788010804158f_linkquality»,»unique_id»:»0x001788010804158f_linkquality_zigbee2mqtt»,»device»:{«identifiers»:[«zigbee2mqtt_0x001788010804158f»],»name»:»0x001788010804158f»,»sw_version»:»Zigbee2mqtt 1.7.1″,»model»:»Hue smart plug — EU (929002240401)»,»manufacturer»:»Philips»},»availability_topic»:»zigbee2mqtt/bridge/state»}’
zigbee2mqtt:info 2019-11-29T12:42:42: MQTT publish: topic ‘homeassistant/switch/0x7cb03eaa0a01b20d/switch/config’, payload ‘{«payload_off»:»OFF»,»payload_on»:»ON»,»value_template»:»{{ value_json.state }}»,»command_topic»:»zigbee2mqtt/0x7cb03eaa0a01b20d/set»,»state_topic»:»zigbee2mqtt/0x7cb03eaa0a01b20d»,»name»:»0x7cb03eaa0a01b20d_switch»,»unique_id»:»0x7cb03eaa0a01b20d_switch_zigbee2mqtt»,»device»:{«identifiers»:[«zigbee2mqtt_0x7cb03eaa0a01b20d»],»name»:»0x7cb03eaa0a01b20d»,»sw_version»:»Zigbee2mqtt 1.7.1″,»model»:»Smart+ plug (AB3257001NJ)»,»manufacturer»:»OSRAM»},»availability_topic»:»zigbee2mqtt/bridge/state»}’
zigbee2mqtt:info 2019-11-29T12:42:42: MQTT publish: topic ‘homeassistant/sensor/0x7cb03eaa0a01b20d/linkquality/config’, payload ‘{«unit_of_measurement»:»-«,»value_template»:»{{ value_json.linkquality }}»,»state_topic»:»zigbee2mqtt/0x7cb03eaa0a01b20d»,»json_attributes_topic»:»zigbee2mqtt/0x7cb03eaa0a01b20d»,»name»:»0x7cb03eaa0a01b20d_linkquality»,»unique_id»:»0x7cb03eaa0a01b20d_linkquality_zigbee2mqtt»,»device»:{«identifiers»:[«zigbee2mqtt_0x7cb03eaa0a01b20d»],»name»:»0x7cb03eaa0a01b20d»,»sw_version»:»Zigbee2mqtt 1.7.1″,»model»:»Smart+ plug (AB3257001NJ)»,»manufacturer»:»OSRAM»},»availability_topic»:»zigbee2mqtt/bridge/state»}’
zigbee2mqtt:info 2019-11-29T12:42:42: MQTT publish: topic ‘homeassistant/light/0x00124b001ead90e9/light/config’, payload ‘{«brightness»:true,»color_temp»:true,»xy»:true,»schema»:»json»,»command_topic»:»zigbee2mqtt/0x00124b001ead90e9/set»,»state_topic»:»zigbee2mqtt/0x00124b001ead90e9″,»name»:»0x00124b001ead90e9_light»,»unique_id»:»0x00124b001ead90e9_light_zigbee2mqtt»,»device»:{«identifiers»:[«zigbee2mqtt_0x00124b001ead90e9″],»name»:»0x00124b001ead90e9″,»sw_version»:»Zigbee2mqtt 1.7.1″,»model»:»Zigbee USB mini LED controller RGB + CCT (GL-MC-001)»,»manufacturer»:»Gledopto»},»availability_topic»:»zigbee2mqtt/bridge/state»}’
zigbee2mqtt:info 2019-11-29T12:42:42: MQTT publish: topic ‘homeassistant/sensor/0x00124b001ead90e9/linkquality/config’, payload ‘{«unit_of_measurement»:»-«,»value_template»:»{{ value_json.linkquality }}»,»state_topic»:»zigbee2mqtt/0x00124b001ead90e9″,»json_attributes_topic»:»zigbee2mqtt/0x00124b001ead90e9″,»name»:»0x00124b001ead90e9_linkquality»,»unique_id»:»0x00124b001ead90e9_linkquality_zigbee2mqtt»,»device»:{«identifiers»:[«zigbee2mqtt_0x00124b001ead90e9″],»name»:»0x00124b001ead90e9″,»sw_version»:»Zigbee2mqtt 1.7.1″,»model»:»Zigbee USB mini LED controller RGB + CCT (GL-MC-001)»,»manufacturer»:»Gledopto»},»availability_topic»:»zigbee2mqtt/bridge/state»}’
zigbee2mqtt:info 2019-11-29T12:42:42: MQTT publish: topic ‘homeassistant/binary_sensor/0x00158d00044d5e6b/contact/config’, payload ‘{«payload_on»:false,»payload_off»:true,»value_template»:»{{ value_json.contact }}»,»device_class»:»door»,»state_topic»:»zigbee2mqtt/0x00158d00044d5e6b»,»json_attributes_topic»:»zigbee2mqtt/0x00158d00044d5e6b»,»name»:»0x00158d00044d5e6b_contact»,»unique_id»:»0x00158d00044d5e6b_contact_zigbee2mqtt»,»device»:{«identifiers»:[«zigbee2mqtt_0x00158d00044d5e6b»],»name»:»0x00158d00044d5e6b»,»sw_version»:»Zigbee2mqtt 1.7.1″,»model»:»MiJia door & window contact sensor (MCCGQ01LM)»,»manufacturer»:»Xiaomi»},»availability_topic»:»zigbee2mqtt/bridge/state»}’
zigbee2mqtt:info 2019-11-29T12:42:42: MQTT publish: topic ‘homeassistant/sensor/0x00158d00044d5e6b/battery/config’, payload ‘{«unit_of_measurement»:»%»,»device_class»:»battery»,»value_template»:»{{ value_json.battery }}»,»state_topic»:»zigbee2mqtt/0x00158d00044d5e6b»,»json_attributes_topic»:»zigbee2mqtt/0x00158d00044d5e6b»,»name»:»0x00158d00044d5e6b_battery»,»unique_id»:»0x00158d00044d5e6b_battery_zigbee2mqtt»,»device»:{«identifiers»:[«zigbee2mqtt_0x00158d00044d5e6b»],»name»:»0x00158d00044d5e6b»,»sw_version»:»Zigbee2mqtt 1.7.1″,»model»:»MiJia door & window contact sensor (MCCGQ01LM)»,»manufacturer»:»Xiaomi»},»availability_topic»:»zigbee2mqtt/bridge/state»}’
zigbee2mqtt:info 2019-11-29T12:42:42: MQTT publish: topic ‘homeassistant/sensor/0x00158d00044d5e6b/linkquality/config’, payload ‘{«unit_of_measurement»:»-«,»value_template»:»{{ value_json.linkquality }}»,»state_topic»:»zigbee2mqtt/0x00158d00044d5e6b»,»json_attributes_topic»:»zigbee2mqtt/0x00158d00044d5e6b»,»name»:»0x00158d00044d5e6b_linkquality»,»unique_id»:»0x00158d00044d5e6b_linkquality_zigbee2mqtt»,»device»:{«identifiers»:[«zigbee2mqtt_0x00158d00044d5e6b»],»name»:»0x00158d00044d5e6b»,»sw_version»:»Zigbee2mqtt 1.7.1″,»model»:»MiJia door & window contact sensor (MCCGQ01LM)»,»manufacturer»:»Xiaomi»},»availability_topic»:»zigbee2mqtt/bridge/state»}’
zigbee2mqtt:info 2019-11-29T12:42:42: MQTT publish: topic ‘homeassistant/light/0x00124b001d43cbed/light/config’, payload ‘{«brightness»:true,»color_temp»:true,»xy»:true,»schema»:»json»,»command_topic»:»zigbee2mqtt/0x00124b001d43cbed/set»,»state_topic»:»zigbee2mqtt/0x00124b001d43cbed»,»name»:»0x00124b001d43cbed_light»,»unique_id»:»0x00124b001d43cbed_light_zigbee2mqtt»,»device»:{«identifiers»:[«zigbee2mqtt_0x00124b001d43cbed»],»name»:»0x00124b001d43cbed»,»sw_version»:»Zigbee2mqtt 1.7.1″,»model»:»Zigbee LED controller RGB + CCT plus model (GL-C-008S)»,»manufacturer»:»Gledopto»},»availability_topic»:»zigbee2mqtt/bridge/state»}’
zigbee2mqtt:info 2019-11-29T12:42:42: MQTT publish: topic ‘homeassistant/sensor/0x00124b001d43cbed/linkquality/config’, payload ‘{«unit_of_measurement»:»-«,»value_template»:»{{ value_json.linkquality }}»,»state_topic»:»zigbee2mqtt/0x00124b001d43cbed»,»json_attributes_topic»:»zigbee2mqtt/0x00124b001d43cbed»,»name»:»0x00124b001d43cbed_linkquality»,»unique_id»:»0x00124b001d43cbed_linkquality_zigbee2mqtt»,»device»:{«identifiers»:[«zigbee2mqtt_0x00124b001d43cbed»],»name»:»0x00124b001d43cbed»,»sw_version»:»Zigbee2mqtt 1.7.1″,»model»:»Zigbee LED controller RGB + CCT plus model (GL-C-008S)»,»manufacturer»:»Gledopto»},»availability_topic»:»zigbee2mqtt/bridge/state»}’
zigbee2mqtt:info 2019-11-29T12:42:42: MQTT publish: topic ‘homeassistant/sensor/0x00158d00044db511/temperature/config’, payload ‘{«unit_of_measurement»:»°C»,»device_class»:»temperature»,»value_template»:»{{ value_json.temperature }}»,»state_topic»:»zigbee2mqtt/0x00158d00044db511″,»json_attributes_topic»:»zigbee2mqtt/0x00158d00044db511″,»name»:»0x00158d00044db511_temperature»,»unique_id»:»0x00158d00044db511_temperature_zigbee2mqtt»,»device»:{«identifiers»:[«zigbee2mqtt_0x00158d00044db511″],»name»:»0x00158d00044db511″,»sw_version»:»Zigbee2mqtt 1.7.1″,»model»:»Aqara temperature, humidity and pressure sensor (WSDCGQ11LM)»,»manufacturer»:»Xiaomi»},»availability_topic»:»zigbee2mqtt/bridge/state»}’
zigbee2mqtt:info 2019-11-29T12:42:42: MQTT publish: topic ‘homeassistant/sensor/0x00158d00044db511/humidity/config’, payload ‘{«unit_of_measurement»:»%»,»device_class»:»humidity»,»value_template»:»{{ value_json.humidity }}»,»state_topic»:»zigbee2mqtt/0x00158d00044db511″,»json_attributes_topic»:»zigbee2mqtt/0x00158d00044db511″,»name»:»0x00158d00044db511_humidity»,»unique_id»:»0x00158d00044db511_humidity_zigbee2mqtt»,»device»:{«identifiers»:[«zigbee2mqtt_0x00158d00044db511″],»name»:»0x00158d00044db511″,»sw_version»:»Zigbee2mqtt 1.7.1″,»model»:»Aqara temperature, humidity and pressure sensor (WSDCGQ11LM)»,»manufacturer»:»Xiaomi»},»availability_topic»:»zigbee2mqtt/bridge/state»}’
zigbee2mqtt:info 2019-11-29T12:42:42: MQTT publish: topic ‘homeassistant/sensor/0x00158d00044db511/pressure/config’, payload ‘{«unit_of_measurement»:»hPa»,»device_class»:»pressure»,»value_template»:»{{ value_json.pressure }}»,»state_topic»:»zigbee2mqtt/0x00158d00044db511″,»json_attributes_topic»:»zigbee2mqtt/0x00158d00044db511″,»name»:»0x00158d00044db511_pressure»,»unique_id»:»0x00158d00044db511_pressure_zigbee2mqtt»,»device»:{«identifiers»:[«zigbee2mqtt_0x00158d00044db511″],»name»:»0x00158d00044db511″,»sw_version»:»Zigbee2mqtt 1.7.1″,»model»:»Aqara temperature, humidity and pressure sensor (WSDCGQ11LM)»,»manufacturer»:»Xiaomi»},»availability_topic»:»zigbee2mqtt/bridge/state»}’
zigbee2mqtt:info 2019-11-29T12:42:42: MQTT publish: topic ‘homeassistant/sensor/0x00158d00044db511/battery/config’, payload ‘{«unit_of_measurement»:»%»,»device_class»:»battery»,»value_template»:»{{ value_json.battery }}»,»state_topic»:»zigbee2mqtt/0x00158d00044db511″,»json_attributes_topic»:»zigbee2mqtt/0x00158d00044db511″,»name»:»0x00158d00044db511_battery»,»unique_id»:»0x00158d00044db511_battery_zigbee2mqtt»,»device»:{«identifiers»:[«zigbee2mqtt_0x00158d00044db511″],»name»:»0x00158d00044db511″,»sw_version»:»Zigbee2mqtt 1.7.1″,»model»:»Aqara temperature, humidity and pressure sensor (WSDCGQ11LM)»,»manufacturer»:»Xiaomi»},»availability_topic»:»zigbee2mqtt/bridge/state»}’
zigbee2mqtt:info 2019-11-29T12:42:42: MQTT publish: topic ‘homeassistant/sensor/0x00158d00044db511/linkquality/config’, payload ‘{«unit_of_measurement»:»-«,»value_template»:»{{ value_json.linkquality }}»,»state_topic»:»zigbee2mqtt/0x00158d00044db511″,»json_attributes_topic»:»zigbee2mqtt/0x00158d00044db511″,»name»:»0x00158d00044db511_linkquality»,»unique_id»:»0x00158d00044db511_linkquality_zigbee2mqtt»,»device»:{«identifiers»:[«zigbee2mqtt_0x00158d00044db511″],»name»:»0x00158d00044db511″,»sw_version»:»Zigbee2mqtt 1.7.1″,»model»:»Aqara temperature, humidity and pressure sensor (WSDCGQ11LM)»,»manufacturer»:»Xiaomi»},»availability_topic»:»zigbee2mqtt/bridge/state»}’
zigbee2mqtt:debug 2019-11-29T12:43:36: Received Zigbee message from ‘0x00158d00044db511’, type ‘attributeReport’, cluster ‘genBasic’, data ‘{«65281»:{«1″:3025,»4″:5032,»5″:7,»6″:[0,0],»10″:11002,»100″:2263,»101″:5797,»102»:101408}}’ from endpoint 1 with groupID 0
zigbee2mqtt:info 2019-11-29T12:43:36: MQTT publish: topic ‘zigbee2mqtt/0x00158d00044db511’, payload ‘{«battery»:100,»voltage»:3025,»temperature»:22.63,»humidity»:57.97,»pressure»:1014.1,»linkquality»:65}’
zigbee2mqtt:debug 2019-11-29T12:43:36: Received Zigbee message from ‘0x00158d00044db511’, type ‘attributeReport’, cluster ‘genBasic’, data ‘{«modelId»:»lumi.weather»}’ from endpoint 1 with groupID 0
zigbee2mqtt:debug 2019-11-29T12:43:39: Received Zigbee message from ‘0x00158d0003cb1567’, type ‘attributeReport’, cluster ‘genBasic’, data ‘{«65281»:{«1″:2985,»4″:5032,»5″:19,»6″:[0,1],»10″:0,»100″:2268,»101»:5913}}’ from endpoint 1 with groupID 0
zigbee2mqtt:info 2019-11-29T12:43:39: MQTT publish: topic ‘zigbee2mqtt/0x00158d0003cb1567’, payload ‘{«battery»:91,»voltage»:2985,»temperature»:22.68,»humidity»:59.13,»linkquality»:110}’
zigbee2mqtt:debug 2019-11-29T12:43:39: Received Zigbee message from ‘0x00158d0003cb1567’, type ‘attributeReport’, cluster ‘genBasic’, data ‘{«modelId»:»lumi.sensor_ht»}’ from endpoint 1 with groupID 0
zigbee2mqtt:debug 2019-11-29T12:44:06: Received MQTT message on ‘zigbee2mqtt/0x00124b001ead90e9/set’ with data ‘{«state»: «ON»}’
zigbee2mqtt:debug 2019-11-29T12:44:06: Publishing ‘set’ ‘state’ to ‘0x00124b001ead90e9’
zigbee2mqtt:error 2019-11-29T12:44:07: Publish ‘set’ ‘state’ to ‘0x00124b001ead90e9’ failed: ‘Error: Data request failed with error: ‘MAC channel access failure’ (225)’
zigbee2mqtt:info 2019-11-29T12:44:07: MQTT publish: topic ‘zigbee2mqtt/bridge/log’, payload ‘{«type»:»zigbee_publish_error»,»message»:»Publish ‘set’ ‘state’ to ‘0x00124b001ead90e9’ failed: ‘Error: Data request failed with error: ‘MAC channel access failure’ (225)'»,»meta»:{«friendly_name»:»0x00124b001ead90e9″}}’
zigbee2mqtt:debug 2019-11-29T12:44:07: Received MQTT message on ‘zigbee2mqtt/0x00124b001d43cbed/set’ with data ‘{«state»: «ON»}’
zigbee2mqtt:debug 2019-11-29T12:44:07: Publishing ‘set’ ‘state’ to ‘0x00124b001d43cbed’
zigbee2mqtt:error 2019-11-29T12:44:08: Publish ‘set’ ‘state’ to ‘0x00124b001d43cbed’ failed: ‘Error: Data request failed with error: ‘No network route’ (205)’
zigbee2mqtt:info 2019-11-29T12:44:08: MQTT publish: topic ‘zigbee2mqtt/bridge/log’, payload ‘{«type»:»zigbee_publish_error»,»message»:»Publish ‘set’ ‘state’ to ‘0x00124b001d43cbed’ failed: ‘Error: Data request failed with error: ‘No network route’ (205)'»,»meta»:{«friendly_name»:»0x00124b001d43cbed»}}’
zigbee2mqtt:debug 2019-11-29T12:44:10: Received MQTT message on ‘zigbee2mqtt/0x00124b001ead90e9/set’ with data ‘{«state»: «ON»}’
zigbee2mqtt:debug 2019-11-29T12:44:10: Publishing ‘set’ ‘state’ to ‘0x00124b001ead90e9’
zigbee2mqtt:debug 2019-11-29T12:44:10: Received MQTT message on ‘zigbee2mqtt/0x00124b001d43cbed/set’ with data ‘{«state»: «ON»}’
zigbee2mqtt:debug 2019-11-29T12:44:10: Publishing ‘set’ ‘state’ to ‘0x00124b001d43cbed’
zigbee2mqtt:error 2019-11-29T12:44:11: Publish ‘set’ ‘state’ to ‘0x00124b001d43cbed’ failed: ‘Error: Data request failed with error: ‘No network route’ (205)’
zigbee2mqtt:info 2019-11-29T12:44:11: MQTT publish: topic ‘zigbee2mqtt/bridge/log’, payload ‘{«type»:»zigbee_publish_error»,»message»:»Publish ‘set’ ‘state’ to ‘0x00124b001d43cbed’ failed: ‘Error: Data request failed with error: ‘No network route’ (205)'»,»meta»:{«friendly_name»:»0x00124b001d43cbed»}}’
zigbee2mqtt:error 2019-11-29T12:44:11: Publish ‘set’ ‘state’ to ‘0x00124b001ead90e9’ failed: ‘Error: Data request failed with error: ‘MAC channel access failure’ (225)’
zigbee2mqtt:info 2019-11-29T12:44:11: MQTT publish: topic ‘zigbee2mqtt/bridge/log’, payload ‘{«type»:»zigbee_publish_error»,»message»:»Publish ‘set’ ‘state’ to ‘0x00124b001ead90e9’ failed: ‘Error: Data request failed with error: ‘MAC channel access failure’ (225)'»,»meta»:{«friendly_name»:»0x00124b001ead90e9″}}’
zigbee2mqtt:debug 2019-11-29T12:44:15: Received MQTT message on ‘zigbee2mqtt/0x00124b001ead90e9/set’ with data ‘{«state»: «ON»}’
zigbee2mqtt:debug 2019-11-29T12:44:15: Publishing ‘set’ ‘state’ to ‘0x00124b001ead90e9’
zigbee2mqtt:debug 2019-11-29T12:44:15: Received MQTT message on ‘zigbee2mqtt/0x00124b001d43cbed/set’ with data ‘{«state»: «ON»}’
zigbee2mqtt:debug 2019-11-29T12:44:15: Publishing ‘set’ ‘state’ to ‘0x00124b001d43cbed’
zigbee2mqtt:error 2019-11-29T12:44:15: Publish ‘set’ ‘state’ to ‘0x00124b001ead90e9’ failed: ‘Error: Data request failed with error: ‘MAC channel access failure’ (225)’
zigbee2mqtt:info 2019-11-29T12:44:15: MQTT publish: topic ‘zigbee2mqtt/bridge/log’, payload ‘{«type»:»zigbee_publish_error»,»message»:»Publish ‘set’ ‘state’ to ‘0x00124b001ead90e9’ failed: ‘Error: Data request failed with error: ‘MAC channel access failure’ (225)'»,»meta»:{«friendly_name»:»0x00124b001ead90e9″}}’
zigbee2mqtt:debug 2019-11-29T12:44:16: Received MQTT message on ‘zigbee2mqtt/0x00124b001d43cbed/set’ with data ‘{«state»: «OFF»}’
zigbee2mqtt:debug 2019-11-29T12:44:16: Publishing ‘set’ ‘state’ to ‘0x00124b001d43cbed’
zigbee2mqtt:error 2019-11-29T12:44:16: Publish ‘set’ ‘state’ to ‘0x00124b001d43cbed’ failed: ‘Error: Data request failed with error: ‘No network route’ (205)’
zigbee2mqtt:info 2019-11-29T12:44:16: MQTT publish: topic ‘zigbee2mqtt/bridge/log’, payload ‘{«type»:»zigbee_publish_error»,»message»:»Publish ‘set’ ‘state’ to ‘0x00124b001d43cbed’ failed: ‘Error: Data request failed with error: ‘No network route’ (205)'»,»meta»:{«friendly_name»:»0x00124b001d43cbed»}}’
zigbee2mqtt:debug 2019-11-29T12:44:16: Received MQTT message on ‘zigbee2mqtt/0x00124b001ead90e9/set’ with data ‘{«state»: «OFF»}’
zigbee2mqtt:debug 2019-11-29T12:44:16: Publishing ‘set’ ‘state’ to ‘0x00124b001ead90e9’
zigbee2mqtt:error 2019-11-29T12:44:16: Publish ‘set’ ‘state’ to ‘0x00124b001d43cbed’ failed: ‘Error: Data request failed with error: ‘No network route’ (205)’
zigbee2mqtt:info 2019-11-29T12:44:16: MQTT publish: topic ‘zigbee2mqtt/bridge/log’, payload ‘{«type»:»zigbee_publish_error»,»message»:»Publish ‘set’ ‘state’ to ‘0x00124b001d43cbed’ failed: ‘Error: Data request failed with error: ‘No network route’ (205)'»,»meta»:{«friendly_name»:»0x00124b001d43cbed»}}’
zigbee2mqtt:debug 2019-11-29T12:44:16: Received MQTT message on ‘zigbee2mqtt/0x00124b001d43cbed/set’ with data ‘{«state»: «ON»}’
zigbee2mqtt:debug 2019-11-29T12:44:16: Publishing ‘set’ ‘state’ to ‘0x00124b001d43cbed’
zigbee2mqtt:debug 2019-11-29T12:44:16: Received MQTT message on ‘zigbee2mqtt/0x00124b001ead90e9/set’ with data ‘{«state»: «ON»}’
zigbee2mqtt:debug 2019-11-29T12:44:16: Publishing ‘set’ ‘state’ to ‘0x00124b001ead90e9’
zigbee2mqtt:error 2019-11-29T12:44:17: Publish ‘set’ ‘state’ to ‘0x00124b001ead90e9’ failed: ‘Error: Data request failed with error: ‘MAC channel access failure’ (225)’
zigbee2mqtt:info 2019-11-29T12:44:17: MQTT publish: topic ‘zigbee2mqtt/bridge/log’, payload ‘{«type»:»zigbee_publish_error»,»message»:»Publish ‘set’ ‘state’ to ‘0x00124b001ead90e9’ failed: ‘Error: Data request failed with error: ‘MAC channel access failure’ (225)'»,»meta»:{«friendly_name»:»0x00124b001ead90e9″}}’
zigbee2mqtt:error 2019-11-29T12:44:17: Publish ‘set’ ‘state’ to ‘0x00124b001d43cbed’ failed: ‘Error: Data request failed with error: ‘No network route’ (205)’
zigbee2mqtt:info 2019-11-29T12:44:17: MQTT publish: topic ‘zigbee2mqtt/bridge/log’, payload ‘{«type»:»zigbee_publish_error»,»message»:»Publish ‘set’ ‘state’ to ‘0x00124b001d43cbed’ failed: ‘Error: Data request failed with error: ‘No network route’ (205)'»,»meta»:{«friendly_name»:»0x00124b001d43cbed»}}’
zigbee2mqtt:error 2019-11-29T12:44:17: Publish ‘set’ ‘state’ to ‘0x00124b001ead90e9’ failed: ‘Error: Data request failed with error: ‘MAC channel access failure’ (225)’
zigbee2mqtt:info 2019-11-29T12:44:17: MQTT publish: topic ‘zigbee2mqtt/bridge/log’, payload ‘{«type»:»zigbee_publish_error»,»message»:»Publish ‘set’ ‘state’ to ‘0x00124b001ead90e9’ failed: ‘Error: Data request failed with error: ‘MAC channel access failure’ (225)'»,»meta»:{«friendly_name»:»0x00124b001ead90e9″}}’
zigbee2mqtt:debug 2019-11-29T12:44:18: Received MQTT message on ‘zigbee2mqtt/0x7cb03eaa0a01b20d/set’ with data ‘OFF’
zigbee2mqtt:debug 2019-11-29T12:44:18: Publishing ‘set’ ‘state’ to ‘0x7cb03eaa0a01b20d’
zigbee2mqtt:error 2019-11-29T12:44:19: Publish ‘set’ ‘state’ to ‘0x7cb03eaa0a01b20d’ failed: ‘Error: Data request failed with error: ‘MAC channel access failure’ (225)’
zigbee2mqtt:info 2019-11-29T12:44:19: MQTT publish: topic ‘zigbee2mqtt/bridge/log’, payload ‘{«type»:»zigbee_publish_error»,»message»:»Publish ‘set’ ‘state’ to ‘0x7cb03eaa0a01b20d’ failed: ‘Error: Data request failed with error: ‘MAC channel access failure’ (225)'»,»meta»:{«friendly_name»:»0x7cb03eaa0a01b20d»}}’
zigbee2mqtt:debug 2019-11-29T12:44:19: Received MQTT message on ‘zigbee2mqtt/0x001788010804158f/set’ with data ‘OFF’
zigbee2mqtt:debug 2019-11-29T12:44:19: Publishing ‘set’ ‘state’ to ‘0x001788010804158f’
zigbee2mqtt:debug 2019-11-29T12:44:19: Received MQTT message on ‘zigbee2mqtt/0x001788010804158f/set’ with data ‘OFF’
zigbee2mqtt:debug 2019-11-29T12:44:19: Publishing ‘set’ ‘state’ to ‘0x001788010804158f’
zigbee2mqtt:debug 2019-11-29T12:44:19: Received MQTT message on ‘zigbee2mqtt/0x7cb03eaa0a01b20d/set’ with data ‘OFF’
zigbee2mqtt:debug 2019-11-29T12:44:19: Publishing ‘set’ ‘state’ to ‘0x7cb03eaa0a01b20d’
zigbee2mqtt:error 2019-11-29T12:44:20: Publish ‘set’ ‘state’ to ‘0x7cb03eaa0a01b20d’ failed: ‘Error: Data request failed with error: ‘MAC channel access failure’ (225)’
zigbee2mqtt:info 2019-11-29T12:44:20: MQTT publish: topic ‘zigbee2mqtt/bridge/log’, payload ‘{«type»:»zigbee_publish_error»,»message»:»Publish ‘set’ ‘state’ to ‘0x7cb03eaa0a01b20d’ failed: ‘Error: Data request failed with error: ‘MAC channel access failure’ (225)'»,»meta»:{«friendly_name»:»0x7cb03eaa0a01b20d»}}’
zigbee2mqtt:error 2019-11-29T12:44:20: Publish ‘set’ ‘state’ to ‘0x001788010804158f’ failed: ‘Error: Data request failed with error: ‘MAC channel access failure’ (225)’
zigbee2mqtt:info 2019-11-29T12:44:20: MQTT publish: topic ‘zigbee2mqtt/bridge/log’, payload ‘{«type»:»zigbee_publish_error»,»message»:»Publish ‘set’ ‘state’ to ‘0x001788010804158f’ failed: ‘Error: Data request failed with error: ‘MAC channel access failure’ (225)'»,»meta»:{«friendly_name»:»0x001788010804158f»}}’
zigbee2mqtt:error 2019-11-29T12:44:20: Publish ‘set’ ‘state’ to ‘0x001788010804158f’ failed: ‘Error: Data request failed with error: ‘MAC channel access failure’ (225)’
zigbee2mqtt:info 2019-11-29T12:44:20: MQTT publish: topic ‘zigbee2mqtt/bridge/log’, payload ‘{«type»:»zigbee_publish_error»,»message»:»Publish ‘set’ ‘state’ to ‘0x001788010804158f’ failed: ‘Error: Data request failed with error: ‘MAC channel access failure’ (225)'»,»meta»:{«friendly_name»:»0x001788010804158f»}}’

Источник

заново.
⏺ первый добавился, но постоянно валит ошибки:
Zigbee2MQTT:error 2021-12-16 10:02:10: Publish ‘set’ ‘state’ to ‘light_switch_corridor’ failed: ‘Error: Command 0x00158d000460d062/1 genOnOff.on({}, {«timeout»:10000,»disableResponse»:false,»disableRecovery»:false,»disableDefaultResponse»:false,»direction»:0,»srcEndpoint»:null,»reservedBits»:0,»manufacturerCode»:null,»transactionSequenceNumber»:null,»writeUndiv»:false}) failed (Data request failed with error: ‘MAC channel access failure’ (225))’
⏺ второй, вообще, пишет «Не поддерживается» при добавлении.
Zigbee2MQTT:error 2021-12-16 10:11:11: Failed to interview ‘0x00158d00042b2021’, device has not successfully been paired

Как прошить свисток CC2652P ? есть инструкция?
Заранее благодарен за материал.

russian

software

it

zigbee

Источник
Zigbee2MQTTZigbee2MQTT

My network is unstable and/or performs poorly, what can I do?

Read Improve network range and stability

Why does my device not or fail to pair?

This problem can be divided in 2 categories; no logging is shown at all OR interview fails.

No logging is shown at all

  • Make sure joining is enabled.
  • There can be too much interference, try connecting the coordinator USB through an USB extension cable. This problem occurs a lot when used in combination with a Raspberry Pi 3 and 4.
  • If you are using a Raspberry Pi, try disconnecting any other USB devices. If after that pairing works, try connecting the USB devices via a powered USB hub.
  • Make sure that any other Zigbee networks/hubs are powered down. When you e.g. want to pair an IKEA bulb which was first paired to the IKEA gateway make sure to power down the IKEA gateway. If that doesn’t help also try powering down all devices that are connected to the IKEA hub.
  • If it’s a battery powered device, try replacing the battery.
  • You’ve hit the device limit of the coordinator, especially occurs when using the CC2531 or CC2530 in combination with the source routing firmware. Try reflashing the coordinator and immediately pair the device after starting Zigbee2MQTT.
  • Try pairing the device closer to the coordinator.
  • CC2531/CC2530 coordinator only:
    • Stop Zigbee2MQTT, unplug the coordinator, wait 10 seconds, plug the coordinator, start Zigbee2MQTT and try to pair the device again.
    • If none of the above helps, try to reflash the coordinator (does not require re-pairing of already paired devices).

Interview fails

  • Try pairing the device closer to the coordinator.
  • There can be too much interference, try connecting the coordinator USB through an USB extension cable. This problem occurs a lot when used in combination with a Raspberry Pi 4.
  • If it’s a battery powered device, try replacing the battery. Try to keep the device awake by pressing the button of the device (if any) every 3 seconds.
  • Try re-pairing the device again for 2 or 3 times.
  • This might be a Zigbee2MQTT bug, Create a new issueopen in new window with the zigbee-herdsman debug logging attached to it. How to enable zigbee-herdsman debug logging.
  • If device joins with 0x000000000000000 as ieeeAddress (you will see: Starting interview of '0x0000000000000000' in the Zigbee2MQTT log) your CC253X might be broken. See issue #2761open in new window.
  • In case the device is a bulb, try resetting it through Touchlink
  • Try pairing close to a bulb (light) router instead of the coordinator.

How do I migrate from one adapter to another?

Want to migrate from e.g. a CC2531 to a more powerful adapter (e.g. ZZH)? Then follow these instructions:

  1. First make sure you are running the latest version of Zigbee2MQTT
  2. Stop Zigbee2MQTT
  3. Determine whether migrating requires re-pairing of your devices
    • If re-pairing is required: remove data/coordinator_backup.json (if it exists) and data/database.db
    • If re-pairing is not required: copy the ieee address of the old adpter into the new one
  4. Update the serial -> port in your configuration.yaml
  5. Start Zigbee2MQTT
  • If re-pairing was required:
    1. Disconnect power of all mains powered devices
    2. Start re-pairing devices 1 by 1
  • If re-pairing was not required and your devices do not respond; restart some routers by removing them from the mains power for a few seconds.

How do I move my Zigbee2MQTT instance to a different environment?

Details about your network are stored in both the coordinator and files under the data/ directory. To move your instance to another environment move the contents of the data directory and update the path to your coordinator in your configuration.yaml. Now you can start Zigbee2MQTT.

What does and does not require repairing of all devices?

Requires repairing

You need to re-pair all you devices when:

  • Changing the network key (network_key), Zigbee channel (channel) or panID (pan_id) in configuration.yaml.
  • Switching between adapters requires repairing, except when:
    • When adapters are the same repairing is not required (e.g. CC2531 -> CC2531)
    • Switching from a CC2530 or CC2531 based adapter to a CC2538/CC2652/CC1352 based adapter does not require repairing (e.g. CC2531 -> CC2652)
    • Switching between CC2538, CC2652 and CC1352 based adapters does not require repairing (e.g. CC2538 -> CC2652)

Doesn’t require repairing

You don’t need to re-pair your devices when:

  • Updating or downgrading Zigbee2MQTT to a different version.
  • Updating the coordinator firmware.
    • If after flashing you fail to control your devices it helps to:
      • Wait a few minutes so that the Zigbee network can settle.
      • Send Zigbee commands (e.g. turn on/off) to the device.
      • Reboot the device (unplug and plug power).
  • Switching the system running Zigbee2MQTT.
    • When doing this, make sure to copy over the contents of the data directory.

Why are some links missing from my networkmap?

No worry, in case it happens with end devices (battery powered) it most of the times does not mean the devices aren’t connected to the network map anymore. Some end devices (e.g. Xiaomi door sensor) sleep for a too long time which causes the parent (router child ageing) to remove it from it from its child table. This is what causes the missing link. Even while its not in the child table anymore, the end device can still communicate via the router. This does not always happen since not all routers use child ageing (this is a Zigbee 3.0 feature).

Why is the action property always empty?

When the Home Assistant integration is enabled (homeassistant: true in your configuration.yaml) the action property of your e.g. buttons will almost always be empty. Whenever an action is published e.g. {"action": "single"} it will be immediately followed up by a {"action": ""}. This is to trigger a state change in the Home Assistant action sensor (so that it can be used in e.g. automations).

I read that Zigbee2MQTT has a limit of 20 devices (when using a CC2530/CC2531 adapter), is this true?

Definitely not! Example given: the default Zigbee2MQTT CC2531 firmware indeed supports 20 devices connected directly to the coordinator. However, by having routers in your network the network size can be extended. Probably all AC powered devices e.g. bulbs serve as a router, you can even use another CC2530/CC2531 as a router (which has a limit of 21 devices).

Example

When using the default Zigbee2MQTT CC2531 coordinator firmware + 2 CC2531 routers your device limit will be:

  • Coordinator: 15 — 2 routers = 13
  • Router 1: 21
  • Router 2: 21
  • Device limit of 55 devices

Common error codes

A list of common error codes and what to do in case of them:

  • MAC_CHANNEL_ACCESS_FAILURE: this happens when the wireless spectrum is too occupied. Mostly happens when a microwave is on or when there are WiFi networks on the same channel. See Reduce Wifi interference by changing the Zigbee channel how to fix this.
  • NWK_TABLE_FULL: reportedopen in new window to have same root cause as the above MAC_CHANNEL_ACCESS_FAILURE

How do I run multiple instances of Zigbee2MQTT?

In case you setup multiple instances of Zigbee2MQTT it’s important to use a different base_topic and channel. This can be configured in the configuration.yaml.

Zigbee2MQTT crashes after some time

If after some uptime Zigbee2MQTT crashes with errors like: SRSP - AF - dataRequest after 6000ms or SRSP - ZDO - mgmtPermitJoinReq after 6000ms it means the adapter has crashed.

  • Normally this can be fixed by replugging the adapter and restarting Zigbee2MQTT
  • If you are using a CC2530 or CC2531 adapter consider upgrading to one of the recommended adapters. The CC2530/CC2531 is considered legacy hardware and runs into memory corruption easily.
  • Make sure you are using the latest firmware on your adapter, see the adapter page for a link to the latest firmware.
  • If using a Raspberry Pi; this problem can occur if you are using a bad power supply or when other USB devices are connected direclty to the Pi (especially occurs with external SSD), try connecting other USB devices through a powered USB hub.
  • Disable the USB autosuspend feature, if cat /sys/module/usbcore/parameters/autosuspend returns 1 or 2 it is enabled; to disable execute:
sed -i 's/GRUB_CMDLINE_LINUX_DEFAULT="/&usbcore.autosuspend=-1 /' /etc/default/grub
update-grub
systemctl reboot

Источник

Things got even worse. A lot of errors, and the well-known Aqara Wall Switch devices (H1 EU, QBKG04LM, SP-EUC01) began to fall off the network.

Error 2022-05-02 19:05:42Failed to read state of ‘0x00158d00045f20ab’ after reconnect (Read 0x00158d00045f20ab/2 genOnOff([«onOff»], {«sendWhen»:»immediate»,»timeout»:10000,»disableResponse»:false,»disableRecovery»:false,»disableDefaultResponse»:true,»direction»:0,»srcEndpoint»:null,»reservedBits»:0,»manufacturerCode»:null,»transactionSequenceNumber»:null,»writeUndiv»:false}) failed (Data request failed with error: ‘No network route’ (205)))
Error 2022-05-02 19:05:45Failed to interview ‘0x54ef4410001c649b’, device has not successfully been paired
Error 2022-05-02 19:05:51Failed to read state of ‘0x00158d00053eef8f’ after reconnect (Read 0x00158d00053eef8f/2 genOnOff([«onOff»], {«sendWhen»:»immediate»,»timeout»:10000,»disableResponse»:false,»disableRecovery»:false,»disableDefaultResponse»:true,»direction»:0,»srcEndpoint»:null,»reservedBits»:0,»manufacturerCode»:null,»transactionSequenceNumber»:null,»writeUndiv»:false}) failed (Data request failed with error: ‘No network route’ (205)))
Error 2022-05-02 19:06:34Failed to read state of ‘0x00158d00053f2af0’ after reconnect (Read 0x00158d00053f2af0/2 genOnOff([«onOff»], {«sendWhen»:»immediate»,»timeout»:10000,»disableResponse»:false,»disableRecovery»:false,»disableDefaultResponse»:true,»direction»:0,»srcEndpoint»:null,»reservedBits»:0,»manufacturerCode»:null,»transactionSequenceNumber»:null,»writeUndiv»:false}) failed (Data request failed with error: ‘No network route’ (205)))
Error 2022-05-02 19:07:24Failed to read state of ‘0x00158d00045e30ff’ after reconnect (Read 0x00158d00045e30ff/2 genOnOff([«onOff»], {«sendWhen»:»immediate»,»timeout»:10000,»disableResponse»:false,»disableRecovery»:false,»disableDefaultResponse»:true,»direction»:0,»srcEndpoint»:null,»reservedBits»:0,»manufacturerCode»:null,»transactionSequenceNumber»:null,»writeUndiv»:false}) failed (Data request failed with error: ‘No network route’ (205)))
Error 2022-05-02 19:07:29Failed to read state of ‘0x00158d00053f2a59’ after reconnect (Read 0x00158d00053f2a59/2 genOnOff([«onOff»], {«sendWhen»:»immediate»,»timeout»:10000,»disableResponse»:false,»disableRecovery»:false,»disableDefaultResponse»:true,»direction»:0,»srcEndpoint»:null,»reservedBits»:0,»manufacturerCode»:null,»transactionSequenceNumber»:null,»writeUndiv»:false}) failed (Data request failed with error: ‘No network route’ (205)))
Error 2022-05-02 19:08:11Failed to read state of ‘0x00158d00053eee28’ after reconnect (Read 0x00158d00053eee28/2 genOnOff([«onOff»], {«sendWhen»:»immediate»,»timeout»:10000,»disableResponse»:false,»disableRecovery»:false,»disableDefaultResponse»:true,»direction»:0,»srcEndpoint»:null,»reservedBits»:0,»manufacturerCode»:null,»transactionSequenceNumber»:null,»writeUndiv»:false}) failed (Data request failed with error: ‘No network route’ (205)))
Error 2022-05-02 19:11:00Failed to read state of ‘0x00158d00053eef8f’ after reconnect (Read 0x00158d00053eef8f/2 genOnOff([«onOff»], {«sendWhen»:»immediate»,»timeout»:10000,»disableResponse»:false,»disableRecovery»:false,»disableDefaultResponse»:true,»direction»:0,»srcEndpoint»:null,»reservedBits»:0,»manufacturerCode»:null,»transactionSequenceNumber»:null,»writeUndiv»:false}) failed (Data request failed with error: ‘No network route’ (205)))
Error 2022-05-02 19:11:15Failed to read state of ‘0x00158d00045f20ab’ after reconnect (Read 0x00158d00045f20ab/2 genOnOff([«onOff»], {«sendWhen»:»immediate»,»timeout»:10000,»disableResponse»:false,»disableRecovery»:false,»disableDefaultResponse»:true,»direction»:0,»srcEndpoint»:null,»reservedBits»:0,»manufacturerCode»:null,»transactionSequenceNumber»:null,»writeUndiv»:false}) failed (Data request failed with error: ‘No network route’ (205)))
Error 2022-05-02 19:11:43Failed to read state of ‘0x00158d00053f2af0’ after reconnect (Read 0x00158d00053f2af0/2 genOnOff([«onOff»], {«sendWhen»:»immediate»,»timeout»:10000,»disableResponse»:false,»disableRecovery»:false,»disableDefaultResponse»:true,»direction»:0,»srcEndpoint»:null,»reservedBits»:0,»manufacturerCode»:null,»transactionSequenceNumber»:null,»writeUndiv»:false}) failed (Data request failed with error: ‘No network route’ (205)))
Error 2022-05-02 19:12:10Failed to read state of ‘0x54ef4410001972d9’ after reconnect (Read 0x54ef4410001972d9/1 genOnOff([«onOff»], {«sendWhen»:»immediate»,»timeout»:10000,»disableResponse»:false,»disableRecovery»:false,»disableDefaultResponse»:true,»direction»:0,»srcEndpoint»:null,»reservedBits»:0,»manufacturerCode»:null,»transactionSequenceNumber»:null,»writeUndiv»:false}) failed (Data request failed with error: ‘MAC channel access failure’ (225)))
Error 2022-05-02 19:12:33Failed to read state of ‘0x54ef4410001d0b06’ after reconnect (Read 0x54ef4410001d0b06/1 genOnOff([«onOff»], {«sendWhen»:»immediate»,»timeout»:10000,»disableResponse»:false,»disableRecovery»:false,»disableDefaultResponse»:true,»direction»:0,»srcEndpoint»:null,»reservedBits»:0,»manufacturerCode»:null,»transactionSequenceNumber»:null,»writeUndiv»:false}) failed (Data request failed with error: ‘MAC channel access failure’ (225)))
Error 2022-05-02 19:12:38Failed to read state of ‘0x00158d00053f2a59’ after reconnect (Read 0x00158d00053f2a59/2 genOnOff([«onOff»], {«sendWhen»:»immediate»,»timeout»:10000,»disableResponse»:false,»disableRecovery»:false,»disableDefaultRe

Источник

I’m stumped on this one — everything appears to be correctly configured and working properly…except that HomeAssistant can’t discover any ZigBee devices. Adding the ConBee II appears to work just fine (recognized under the mapped address as below):

Screenshot of modal to add ConBee device

…but when I go to add a device, this spins until it times out after a few minutes:

screenshot of unsuccessful attempts to discover devices

This is a fresh install Raspbian, with the following docker-compose.yml (I’ve tried the commented out options, as well):

version: '3'
services:
  homeassistant:
    container_name: homeassistant
    # image: homeassistant/home-assistant:stable
    image: homeassistant/raspberrypi4-homeassistant:stable
    ports:
      - "8123:8123"
    volumes:
      - ./config:/config
      - /etc/localtime:/etc/localtime:ro
    devices:
      # - /dev/ttyACM0:/dev/ttyACM0
      - /dev/ttyACM0
    restart: unless-stopped
    # network_mode: host
    # privileged: true

This is the debug output from docker which writes immediately when I click on Add Device in the HomeAssistant configuration for ConBee:

homeassistant    | 2021-06-20 11:05:07 DEBUG (MainThread) [zigpy_deconz.zigbee.application] Sending Zigbee broadcast with tsn 1 under 2 request id, data: b'013c00'
homeassistant    | 2021-06-20 11:05:07 DEBUG (MainThread) [zigpy_deconz.api] Command Command.aps_data_request (17, 2, 0, <DeconzAddressEndpoint address_mode=1 address=65532 endpoint=None>, 0, 54, 0, b'x01<x00', 2, 0)
homeassistant    | 2021-06-20 11:05:07 DEBUG (MainThread) [zigpy_deconz.uart] Send: 0x12130018001100020001fcff00003600000300013c000200
homeassistant    | 2021-06-20 11:05:07 DEBUG (MainThread) [zigpy_deconz.uart] Frame received: 0x121300090002002202
homeassistant    | 2021-06-20 11:05:07 DEBUG (MainThread) [zigpy_deconz.api] APS data request response: [2, <DeviceState.APSDE_DATA_REQUEST_SLOTS_AVAILABLE|2: 34>, 2]
homeassistant    | 2021-06-20 11:05:07 DEBUG (MainThread) [zigpy_deconz.uart] Frame received: 0x0e14000700aa00
homeassistant    | 2021-06-20 11:05:07 DEBUG (MainThread) [zigpy_deconz.api] Device state changed response: [<DeviceState.128|APSDE_DATA_REQUEST_SLOTS_AVAILABLE|APSDE_DATA_INDICATION|2: 170>, 0]
homeassistant    | 2021-06-20 11:05:07 DEBUG (MainThread) [zigpy_deconz.api] Command Command.aps_data_indication (1, 1)
homeassistant    | 2021-06-20 11:05:07 DEBUG (MainThread) [zigpy_deconz.uart] Send: 0x1714000800010001
homeassistant    | 2021-06-20 11:05:07 DEBUG (MainThread) [zigpy_deconz.uart] Frame received: 0x17140021001a002201fcff0102000000000036000300013c0000afdd873601001e
homeassistant    | 2021-06-20 11:05:07 DEBUG (MainThread) [zigpy_deconz.api] APS data indication response: [26, <DeviceState.APSDE_DATA_REQUEST_SLOTS_AVAILABLE|2: 34>, <DeconzAddress address_mode=ADDRESS_MODE.GROUP address=0xfffc>, 1, <DeconzAddress address_mode=ADDRESS_MODE.NWK address=0x0000>, 0, 0, 54, b'x01<x00', 0, 175, 221, 135, 54, 1, 0, 30]
homeassistant    | 2021-06-20 11:05:07 DEBUG (MainThread) [zigpy.zdo] [0x0000:zdo] ZDO request ZDOCmd.Mgmt_Permit_Joining_req: [60, <Bool.false: 0>]
homeassistant    | 2021-06-20 11:05:07 DEBUG (MainThread) [zigpy_deconz.api] 'aps_data_indication' response from <DeconzAddress address_mode=ADDRESS_MODE.NWK address=0x0000>, ep: 0, profile: 0x0000, cluster_id: 0x0036, data: b'013c00'
homeassistant    | 2021-06-20 11:05:07 DEBUG (MainThread) [zigpy_deconz.uart] Frame received: 0x0e15000700a600
homeassistant    | 2021-06-20 11:05:07 DEBUG (MainThread) [zigpy_deconz.api] Device state changed response: [<DeviceState.128|APSDE_DATA_REQUEST_SLOTS_AVAILABLE|APSDE_DATA_CONFIRM|2: 166>, 0]
homeassistant    | 2021-06-20 11:05:07 DEBUG (MainThread) [zigpy_deconz.api] Command Command.aps_data_confirm (0,)
homeassistant    | 2021-06-20 11:05:07 DEBUG (MainThread) [zigpy_deconz.uart] Send: 0x04150007000000
homeassistant    | 2021-06-20 11:05:07 DEBUG (MainThread) [zigpy_deconz.uart] Frame received: 0x04150012000b00220201fcff00e100000000
homeassistant    | 2021-06-20 11:05:07 DEBUG (MainThread) [zigpy_deconz.api] APS data confirm response for request with id 2: e1
homeassistant    | 2021-06-20 11:05:07 DEBUG (MainThread) [zigpy_deconz.api] Request id: 0x02 'aps_data_confirm' for <DeconzAddressEndpoint address_mode=ADDRESS_MODE.GROUP address=0xfffc endpoint=None>, status: 0xe1
homeassistant    | 2021-06-20 11:05:07 DEBUG (MainThread) [zigpy_deconz.zigbee.application] Error while sending 2 req id broadcast: TXStatus.MAC_CHANNEL_ACCESS_FAILURE
homeassistant    | 2021-06-20 11:05:07 DEBUG (MainThread) [zigpy_deconz.api] Command Command.write_parameter (2, <NetworkParameter.permit_join: 33>, b'<')
homeassistant    | 2021-06-20 11:05:07 DEBUG (MainThread) [zigpy_deconz.uart] Send: 0x0b160009000200213c
homeassistant    | 2021-06-20 11:05:07 DEBUG (MainThread) [zigpy_deconz.uart] Frame received: 0x0b16000800010021
homeassistant    | 2021-06-20 11:05:07 DEBUG (MainThread) [zigpy_deconz.api] Write parameter permit_join: SUCCESS

Things I’ve tried:

  1. Deleting the Integration in HomeAssistant and re-adding the device
  2. RMing the docker setup and starting fresh
  3. The commented out parameters in the docker-compose file
  4. Changing the zigbee channel to 24 (via ./config/configuration.yaml
  5. Pairing multiple different device types (I’ve tried both Leviton switches and Aqara door sensors, always in discoverable mode)
  6. Connecting the ConBee to a powered USB hub to rule out any USB3 or wifi interference (although the pi is a client on a 5GHz wifi network)
  7. Googling the MAC_CHANNEL_ACCESS_FAILURE error extensively, which appears to be a red herring
Источник

Recommend Projects

  • React photo

    React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo

    Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo

    Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo

    TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo

    Django

    The Web framework for perfectionists with deadlines.

  • Laravel photo

    Laravel

    A PHP framework for web artisans

  • D3 photo

    D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Visualization

    Some thing interesting about visualization, use data art

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo

    Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo

    Microsoft

    Open source projects and samples from Microsoft.

  • Google photo

    Google

    Google ❤️ Open Source for everyone.

  • Alibaba photo

    Alibaba

    Alibaba Open Source for everyone

  • D3 photo

    D3

    Data-Driven Documents codes.

  • Tencent photo

    Tencent

    China tencent open source team.

Источник

Понравилась статья? Поделить с друзьями:
  • Data partition corrupted format the partition to continue honor как исправить
  • Data operation error перевод
  • Data load error что значит
  • Data load error retrying hive os что делать
  • Data load error retrying hive os перевод