Error starting up the add-on after recent 1.5.1 update

[saicrazyfire]

zigbee2mqtt add-on version (if edge, please report commit hash): 1.5.1

Operating environment (HassOS, Virtual Machine, Device/platform running Hass.io):

Running HassIO v0.95.4 on a Ubuntu 18.04.2 LTS VM.

Description of problem:

Error starting up the addon with error TypeError: net.precfgkey should be an array with 16 uint8 integers. This configuration used to work before the update to 1.5.1. The json data below was also tweaked to support the new format (with nested objects instead of one flat json).

Note - I have not added devices yet (since I've recreated my VM recently and haven't gotten around to doing so).

Your entire configuration from the frontend (with sensitive fields redacted):

{
  "data_path": "/share/zigbee2mqtt",
  "devices": "[]",
  "groups": "groups.yaml",
  "homeassistant": true,
  "permit_join": false,
  "mqtt": {
    "base_topic": "zigbee2mqtt",
    "server": "mqtt://127.0.0.1:1883",
    "user": "~REDACTED~",
    "password": "~REDACTED~"
  },
  "serial": {
    "port": "/dev/ttyACM0"
  },
  "advanced": {
    "pan_id": "~REDACTED MAYBE?~",
    "channel": 11,
    "network_key": []
  }
}

Your logs from Hass.io

./run.sh: line 13: [Info] Configuration backup found in /share/zigbee2mqtt/.configuration.yaml.bk. Skipping config backup.: No such file or directory
2019-07-20T18:35:43: PM2 log: Launching in no daemon mode
2019-07-20T18:35:43: PM2 log: App [npm:0] starting in -fork mode-
2019-07-20T18:35:43: PM2 log: App [npm:0] online
> zigbee2mqtt@1.5.1 start /zigbee2mqtt-1.5.1
> node index.js
  zigbee2mqtt:info 7/20/2019, 6:35:44 PM Logging to directory: '/share/zigbee2mqtt/log/2019-07-20.18-35-44'
  zigbee2mqtt:info 7/20/2019, 6:35:45 PM Starting zigbee2mqtt version 1.5.1 (commit #unknown)
  zigbee2mqtt:info 7/20/2019, 6:35:45 PM Starting zigbee-shepherd
/zigbee2mqtt-1.5.1/node_modules/zigbee-herdsman/dist/lib/components/controller.js:429
                    throw new TypeError('net.precfgkey should be an array with 16 uint8 integers.');
                    ^
TypeError: net.precfgkey should be an array with 16 uint8 integers.
    at /zigbee2mqtt-1.5.1/node_modules/zigbee-herdsman/dist/lib/components/controller.js:429:27
    at Object._.forOwn (/zigbee2mqtt-1.5.1/node_modules/zigbee-herdsman/node_modules/busyman/index.js:242:27)
    at Object._.forEach (/zigbee2mqtt-1.5.1/node_modules/zigbee-herdsman/node_modules/busyman/index.js:415:18)
    at Controller.setNvParams (/zigbee2mqtt-1.5.1/node_modules/zigbee-herdsman/dist/lib/components/controller.js:414:7)
    at new ZShepherd (/zigbee2mqtt-1.5.1/node_modules/zigbee-herdsman/dist/lib/shepherd.js:28:21)
    at Zigbee.start (/zigbee2mqtt-1.5.1/lib/zigbee.js:57:25)
    at startupLogVersion (/zigbee2mqtt-1.5.1/lib/controller.js:167:25)
    at utils.getZigbee2mqttVersion (/zigbee2mqtt-1.5.1/lib/controller.js:193:13)
    at git.getLastCommit (/zigbee2mqtt-1.5.1/lib/util/utils.js:102:9)
    at /zigbee2mqtt-1.5.1/node_modules/git-last-commit/source/index.js:44:5
npm
 ERR! code ELIFECYCLE
npm ERR! errno
 1
npm
 ERR! zigbee2mqtt@1.5.1 start: `node index.js`
npm ERR! Exit status 1
npm ERR! 
npm ERR! Failed at the zigbee2mqtt@1.5.1 start script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm ERR! A complete log of this run can be found in:
npm ERR!     /root/.npm/_logs/2019-07-20T22_35_45_028Z-debug.log
2019-07-20T18:35:49: PM2 log: App [npm:0] exited with code [1] via signal [SIGINT]
2019-07-20T18:35:49: PM2 log: App [npm:0] starting in -fork mode-
2019-07-20T18:35:49: PM2 log: App [npm:0] online
> zigbee2mqtt@1.5.1 start /zigbee2mqtt-1.5.1
> node index.js
  zigbee2mqtt:info 7/20/2019, 6:35:50 PM Logging to directory: '/share/zigbee2mqtt/log/2019-07-20.18-35-49'
  zigbee2mqtt:info 7/20/2019, 6:35:50 PM Starting zigbee2mqtt version 1.5.1 (commit #unknown)
  zigbee2mqtt:info 7/20/2019, 6:35:50 PM Starting zigbee-shepherd
/zigbee2mqtt-1.5.1/node_modules/zigbee-herdsman/dist/lib/components/controller.js:429
                    throw new TypeError('net.precfgkey should be an array with 16 uint8 integers.');
                    ^
TypeError: net.precfgkey should be an array with 16 uint8 integers.
    at /zigbee2mqtt-1.5.1/node_modules/zigbee-herdsman/dist/lib/components/controller.js:429:27
    at Object._.forOwn (/zigbee2mqtt-1.5.1/node_modules/zigbee-herdsman/node_modules/busyman/index.js:242:27)
    at Object._.forEach (/zigbee2mqtt-1.5.1/node_modules/zigbee-herdsman/node_modules/busyman/index.js:415:18)
    at Controller.setNvParams (/zigbee2mqtt-1.5.1/node_modules/zigbee-herdsman/dist/lib/components/controller.js:414:7)
    at new ZShepherd (/zigbee2mqtt-1.5.1/node_modules/zigbee-herdsman/dist/lib/shepherd.js:28:21)
    at Zigbee.start (/zigbee2mqtt-1.5.1/lib/zigbee.js:57:25)
    at startupLogVersion (/zigbee2mqtt-1.5.1/lib/controller.js:167:25)
    at utils.getZigbee2mqttVersion (/zigbee2mqtt-1.5.1/lib/controller.js:193:13)
    at git.getLastCommit (/zigbee2mqtt-1.5.1/lib/util/utils.js:102:9)
    at /zigbee2mqtt-1.5.1/node_modules/git-last-commit/source/index.js:44:5
npm
 ERR! code ELIFECYCLE
npm ERR! 
errno 1
npm 
ERR! zigbee2mqtt@1.5.1 start: `node index.js`
npm ERR! Exit status 1
npm ERR! 
npm ERR! Failed at the zigbee2mqtt@1.5.1 start script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

It's difficult to get the logs from /share/zigbee2mqtt/log/2019-07-20.18-35-44 since they keep getting deleted while the add-on is enabled, and file is empty when the add-on is disabled.

[PrivatHomeServer]

I'm just setting up zigbee2mqtt.

Have more or less exactly the same problem and try to solve it now.

Hass.io on a VM: 96.2

zigbee2mqtt:info 7/21/2019, 12:52:55 AM Starting zigbee-shepherd /zigbee2mqtt-1.5.1/node_modules/zigbee-herdsman/dist/lib/components/controller.js:429 throw new TypeError('net.precfgkey should be an array with 16 uint8 integers.'); ^ TypeError: net.precfgkey should be an array with 16 uint8 integers. at /zigbee2mqtt-1.5.1/nodemodules/zigbee-herdsman/dist/lib/components/controller.js:429:27 at Object..forOwn (/zigbee2mqtt-1.5.1/node_modules/zigbee-herdsman/nodemodules/busyman/index.js:242:27) at Object..forEach (/zigbee2mqtt-1.5.1/node_modules/zigbee-herdsman/node_modules/busyman/index.js:415:18) at Controller.setNvParams (/zigbee2mqtt-1.5.1/node_modules/zigbee-herdsman/dist/lib/components/controller.js:414:7) at new ZShepherd (/zigbee2mqtt-1.5.1/node_modules/zigbee-herdsman/dist/lib/shepherd.js:28:21) at Zigbee.start (/zigbee2mqtt-1.5.1/lib/zigbee.js:57:25) at startupLogVersion (/zigbee2mqtt-1.5.1/lib/controller.js:167:25) at utils.getZigbee2mqttVersion (/zigbee2mqtt-1.5.1/lib/controller.js:193:13) at git.getLastCommit (/zigbee2mqtt-1.5.1/lib/util/utils.js:102:9) at /zigbee2mqtt-1.5.1/node_modules/git-last-commit/source/index.js:44:5 npm ERR! code ELIFECYCLE npm ERR! errno 1 npm ERR! zigbee2mqtt@1.5.1 start: node index.js npm ERR! Exit status 1 npm ERR! npm ERR! Failed at the zigbee2mqtt@1.5.1 start script. npm ERR! This is probably not a problem with npm. There is likely additional logging output above. npm ERR! A complete log of this run can be found in: npm ERR! /root/.npm/_logs/2019-07-20T22_52_55_727Z-debug.log 2019-07-21T00:52:59: PM2 log: App [npm:0] exited with code [1] via signal [SIGINT] 2019-07-21T00:52:59: PM2 log: App [npm:0] starting in -fork mode- 2019-07-21T00:52:59: PM2 log: App [npm:0] online zigbee2mqtt@1.5.1 start /zigbee2mqtt-1.5.1 node index.js zigbee2mqtt:info

[holazit]

I have the same issue

`

zigbee2mqtt@1.5.1 start /zigbee2mqtt-1.5.1 node index.js zigbee2mqtt:info 7/21/2019, 1:33:44 AM Logging to directory: '/share/zigbee2mqtt/log/2019-07-21.01-33-43' zigbee2mqtt:info 7/21/2019, 1:33:44 AM Starting zigbee2mqtt version 1.5.1 (commit #unknown) zigbee2mqtt:info 7/21/2019, 1:33:44 AM Starting zigbee-shepherd /zigbee2mqtt-1.5.1/node_modules/zigbee-herdsman/dist/lib/components/controller.js:429 throw new TypeError('net.precfgkey should be an array with 16 uint8 integers.'); ^ TypeError: net.precfgkey should be an array with 16 uint8 integers. at /zigbee2mqtt-1.5.1/nodemodules/zigbee-herdsman/dist/lib/components/controller.js:429:27 at Object..forOwn (/zigbee2mqtt-1.5.1/node_modules/zigbee-herdsman/nodemodules/busyman/index.js:242:27) at Object..forEach (/zigbee2mqtt-1.5.1/node_modules/zigbee-herdsman/node_modules/busyman/index.js:415:18) at Controller.setNvParams (/zigbee2mqtt-1.5.1/node_modules/zigbee-herdsman/dist/lib/components/controller.js:414:7) at new ZShepherd (/zigbee2mqtt-1.5.1/node_modules/zigbee-herdsman/dist/lib/shepherd.js:28:21) at Zigbee.start (/zigbee2mqtt-1.5.1/lib/zigbee.js:57:25) at startupLogVersion (/zigbee2mqtt-1.5.1/lib/controller.js:167:25) at utils.getZigbee2mqttVersion (/zigbee2mqtt-1.5.1/lib/controller.js:193:13) at git.getLastCommit (/zigbee2mqtt-1.5.1/lib/util/utils.js:102:9) at /zigbee2mqtt-1.5.1/node_modules/git-last-commit/source/index.js:44:5 npm ERR! code ELIFECYCLE npm ERR! errno 1 npm ERR! zigbee2mqtt@1.5.1 start: node index.js npm ERR! Exit status 1 npm ERR! npm ERR! Failed at the zigbee2mqtt@1.5.1 start script. npm ERR! This is probably not a problem with npm. There is likely additional logging output above. npm ERR! A complete log of this run can be found in: npm ERR! /root/.npm/_logs/2019-07-20T23_33_44_835Z-debug.log 2019-07-21T01:33:45: PM2 log: App [npm:0] exited with code [1] via signal [SIGINT] 2019-07-21T01:33:45: PM2 log: App [npm:0] starting in -fork mode- 2019-07-21T01:33:45: PM2 log: App [npm:0] online `

[PlayedIn]

Same issue. Log below. Tried to roll back to an earlier version from a snapshot but still getting the same errors:

> node index.js
  zigbee2mqtt:info 7/20/2019, 8:33:49 PM Logging to directory: '/share/zigbee2mqtt/log/2019-07-20.20-33-48'
  zigbee2mqtt:info 7/20/2019, 8:33:49 PM Starting zigbee2mqtt version 1.5.1 (commit #unknown)
  zigbee2mqtt:info 7/20/2019, 8:33:50 PM Starting zigbee-shepherd
/zigbee2mqtt-1.5.1/node_modules/zigbee-herdsman/dist/lib/components/controller.js:429
                    throw new TypeError('net.precfgkey should be an array with 16 uint8 integers.');
                    ^
TypeError: net.precfgkey should be an array with 16 uint8 integers.
    at /zigbee2mqtt-1.5.1/node_modules/zigbee-herdsman/dist/lib/components/controller.js:429:27
    at Object._.forOwn (/zigbee2mqtt-1.5.1/node_modules/zigbee-herdsman/node_modules/busyman/index.js:242:27)
    at Object._.forEach (/zigbee2mqtt-1.5.1/node_modules/zigbee-herdsman/node_modules/busyman/index.js:415:18)
    at Controller.setNvParams (/zigbee2mqtt-1.5.1/node_modules/zigbee-herdsman/dist/lib/components/controller.js:414:7)
    at new ZShepherd (/zigbee2mqtt-1.5.1/node_modules/zigbee-herdsman/dist/lib/shepherd.js:28:21)
    at Zigbee.start (/zigbee2mqtt-1.5.1/lib/zigbee.js:57:25)
    at startupLogVersion (/zigbee2mqtt-1.5.1/lib/controller.js:167:25)
    at utils.getZigbee2mqttVersion (/zigbee2mqtt-1.5.1/lib/controller.js:193:13)
    at git.getLastCommit (/zigbee2mqtt-1.5.1/lib/util/utils.js:102:9)
    at /zigbee2mqtt-1.5.1/node_modules/git-last-commit/source/index.js:44:5
npm
 ERR! code ELIFECYCLE
npm ERR! errno 1
npm
 ERR! zigbee2mqtt@1.5.1 start: `node index.js`
npm ERR! Exit status 1
npm ERR! 
npm ERR! Failed at the zigbee2mqtt@1.5.1 start script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm ERR! A complete log of this run can be found in:
npm ERR!     /root/.npm/_logs/2019-07-21T00_33_50_079Z-debug.log
2019-07-20T20:33:54: PM2 log: App [npm:0] exited with code [1] via signal [SIGINT]
2019-07-20T20:33:54: PM2 log: App [npm:0] starting in -fork mode-
2019-07-20T20:33:54: PM2 log: App [npm:0] online
> zigbee2mqtt@1.5.1 start /zigbee2mqtt-1.5.1

[talondnb]

Same issue here.

[talondnb]

I've discovered the reason; 1.5.1 looks to be insistent on using a network_key.

Follow here to generate a key and apply the setting:

http://www.zigbee2mqtt.io/how_tos/how_to_secure_network.html

edit: re-pairing devices looks to be necessary

[brent0np]

I also have the above error

[minsuke]

I also have same errors pair again all things?

[talondnb]

The fix is to add a network_key and re-pair all devices.

[PlayedIn]

Can any random 16 numbers between 1-254 be used? I've added a network_key but zigbee2shepherd still will not start.

zigbee2mqtt:error 7/20/2019, 11:40:47 PM Failed to start
    {"message":"request timeout","stack":"Error: request timeout\n    at CcZnp.<anonymous> (/zigbee2mqtt-1.5.1/node_modules/zigbee-herdsman/dist/cc-znp/index.js:208:22)\n    at Object.onceWrapper (events.js:286:20)\n    at CcZnp.emit (events.js:198:13)\n    at Timeout.<anonymous> (/zigbee2mqtt-1.5.1/node_modules/zigbee-herdsman/dist/cc-znp/index.js:192:18)\n    at ontimeout (timers.js:436:11)\n    at tryOnTimeout (timers.js:300:5)\n    at listOnTimeout (timers.js:263:5)\n    at Timer.processTimers (timers.js:223:10)"}
  zigbee2mqtt:error 7/20/2019, 11:40:47 PM Exiting...

[talondnb]

Please follow this link:

http://www.zigbee2mqtt.io/how_tos/how_to_secure_network.html

[PlayedIn]

I did with the exception of generating a key. That is why I am asking if a random key can be used or if one has to be generated using the below which isn't easy on hassio.

dd if=/dev/urandom bs=1 count=16 2>/dev/null | od -A n -t x1 | awk '{printf "["} {for(i = 1; i< NF; i++) {printf "0x%s, ", $i}} {printf "0x%s]\n", $NF}'

[talondnb]

As long as you use 16 numbers between 0-255, you should be good. Yes it can be random.

[minsuke]

Please follow this link:

http://www.zigbee2mqtt.io/how_tos/how_to_secure_network.html

I recovered thx for your guide

[ReindDooyeweerd]

@danielwelch Maybe an smart idea to state this also in the component... as stated by messages above people need to repair all their devices, not a fun thing to do when you have a lot of them so i think it's an good idea to warn people about it.

[krishuang92]

I use Hass.io and add-on. I have the same issue and I look into the configuration document. It indicates that network_key is optional but when I remove the network_key:[], I can't save the config.

[XanderTenBoden]

It took me 3 hours to get most of my stuff running again this morning as I had to re-connect every ducking lamp in the house. This was not cool!

@krishuang92 you have to add 16 decimal numbers within the array to get it working. Something like: network_key:[1,2,3,4,5,6,7,8,9,10,11,12,13,14,15,16]

[tigroz]

Do someone knows if the network key can be disabled? I don’t need it and I don’t wanna pair again all my devices

[dzungpv]

Do someone knows if the network key can be disabled? I don’t need it and I don’t wanna pair again all my devices

You use default one here: https://github.com/Koenkk/zigbee2mqtt/blob/ac3b924065c6f2b9dd7433a6f193d1924b34bb7d/lib/util/settings.js#L88

[dhzl84]

This is an adapted command to generate 16 random unsigned decimal numbers since the addon doesn't accept hex values: dd if=/dev/urandom bs=1 count=16 2>/dev/null | od -A n -t u1 | awk '{printf "["} {for(i = 1; i< NF; i++) {printf "%s, ", $i}} {printf "%s]\n", $NF}'

[26tajeen]

@dzungpv are you saying if users affected by this problem just insert network_key: [1, 3, 5, 7, 9, 11, 13, 15, 0, 2, 4, 6, 8, 10, 12, 13], then things will start working again? Cheers

[tigroz]

@dzungpv tanks! I confirm that using default network key it starts working again !

[dzungpv]

@lancelon you download file .configuration.yaml.bk (configuration.yaml)to your computer, update to 1.5.1, after update just stop it, press "RESET TO DEFAULT" to get right config, after that just replace you information from old config file like mqtt info, port, channel and use the key above, press START, it will work just like before

[ivanskj]

instructions from @dzungpv works, thanks! I copied the configuration info, "Reset to default", and retyped the settings from the old config. Used the default network_key: [1, 3, 5, 7, 9, 11, 13, 15, 0, 2, 4, 6, 8, 10, 12, 13].

No need to repair devices on my setup.

[iFloris]

After also following @dzungpv and @ivanskj my Zigbee network also started working again through z2mqtt. Like @ivanskj I reset the configuration and just filled my user and password as well as the default network key. Everything worked as before right away. There has been a warning that there would be a breaking change for many weeks now, so it is not exactly a surprise that something like this was going to happen 😄 I am just grateful that others already found the simplest way to get things working again! 👍

[cdybdahl]

Using default network key worked for some (Xioami) devices for me. Thanks for saving me hours of re-pairing!

Seems that my Hue bulbs didn't get the memo, however. Anyone else? Guess I'll have to reset those...

EDIT: never mind, just had to toggle power to the bulbs and they started responding again.

[danielwelch]

Thanks for the understanding everyone. Sorry to those that had to repair all of their devices. The purpose of the back up feature was to hopefully avoid this. I'm not sure why those who had a blank network key were suddenly required to enter it (or why the default network key became explicitly required), maybe a change within zigbee2mqtt config handling with the update.

[danielwelch]

I've also updated the top warning in the README with a reference to the backup. Should've done that from the start.

[ebudalen]

Hi, can't get it to work with the standard network key. Config:

{
  "data_path": "/share/zigbee2mqtt",
  "devices": "devices.yaml",
  "groups": "groups.yaml",
  "homeassistant": true,
  "permit_join": false,
  "mqtt": {
    "base_topic": "zigbee2mqtt",
    "server": "mqtt://homeassistant:1883",
    "user": "******",
    "password": "*****"
  },
  "serial": {
    "port": "/dev/ttyACM1"
  },
  "advanced": {
    "pan_id": 6754,
    "channel": 11,
    "network_key": [
      1,
      3,
      5,
      7,
      9,
      11,
      13,
      15,
      0,
      2,
      4,
      6,
      8,
      10,
      12,
      13
    ]
  }
}

The logs:

./run.sh: line 13: [Info] Configuration backup found in /share/zigbee2mqtt/.configuration.yaml.bk. Skipping config backup.: No such file or directory
2019-07-21T19:38:07: PM2 log: Launching in no daemon mode
2019-07-21T19:38:07: PM2 log: App [npm:0] starting in -fork mode-
2019-07-21T19:38:07: PM2 log: App [npm:0] online
> zigbee2mqtt@1.5.1 start /zigbee2mqtt-1.5.1
> node index.js
  zigbee2mqtt:info 7/21/2019, 7:38:08 PM Logging to directory: '/share/zigbee2mqtt/log/2019-07-21.19-38-08'
  zigbee2mqtt:info 7/21/2019, 7:38:08 PM Starting zigbee2mqtt version 1.5.1 (commit #unknown)
  zigbee2mqtt:info 7/21/2019, 7:38:08 PM Starting zigbee-shepherd
  zigbee2mqtt:info 7/21/2019, 7:38:15 PM zigbee-shepherd started
  zigbee2mqtt:info 7/21/2019, 7:38:15 PM Coordinator firmware version: '20190223'
  zigbee2mqtt:info 7/21/2019, 7:38:15 PM Currently 9 devices are joined:
  zigbee2mqtt:info 7/21/2019, 7:38:15 PM unknown (0x00178801021036c7): 9290012607 - Philips Hue motion sensor (EndDevice)
  zigbee2mqtt:info 7/21/2019, 7:38:15 PM unknown (0x000b57fffe25384d): LED1623G12 - IKEA TRADFRI LED bulb E27 1000 lumen, dimmable, opal white (Router)
  zigbee2mqtt:info 7/21/2019, 7:38:15 PM unknown (0x90fd9ffffee7cea1): E1524 - IKEA TRADFRI remote control (EndDevice)
  zigbee2mqtt:info 7/21/2019, 7:38:15 PM unknown (0x000b57fffe90990c): ICTC-G-1 - IKEA TRADFRI wireless dimmer (EndDevice)
  zigbee2mqtt:info 7/21/2019, 7:38:15 PM unknown (0x00178801021038c2): 9290012607 - Philips Hue motion sensor (EndDevice)
  zigbee2mqtt:info 7/21/2019, 7:38:15 PM unknown (0x0017880104f79b79): 324131092621 - Philips Hue dimmer switch (EndDevice)
  zigbee2mqtt:info 7/21/2019, 7:38:15 PM unknown (0x000b57fffe2eeb99): E1525 - IKEA TRADFRI motion sensor (EndDevice)
  zigbee2mqtt:info 7/21/2019, 7:38:15 PM unknown (0x000b57fffe3210f7): LED1623G12 - IKEA TRADFRI LED bulb E27 1000 lumen, dimmable, opal white (Router)
  zigbee2mqtt:info 7/21/2019, 7:38:15 PM unknown (0x000b57fffe3239c4): E1525 - IKEA TRADFRI motion sensor (EndDevice)
  zigbee2mqtt:info 7/21/2019, 7:38:15 PM Zigbee: disabling joining new devices.
  zigbee2mqtt:info 7/21/2019, 7:38:15 PM Connecting to MQTT server at mqtt://homeassistant:1883
  zigbee2mqtt:info 7/21/2019, 7:38:15 PM zigbee-shepherd ready
  zigbee2mqtt:info 7/21/2019, 7:38:16 PM Connected to MQTT server
  zigbee2mqtt:info 7/21/2019, 7:38:16 PM MQTT publish: topic 'zigbee2mqtt/bridge/state', payload 'online'
  zigbee2mqtt:info 7/21/2019, 7:38:16 PM MQTT publish: topic 'zigbee2mqtt/0x00178801021036c7', payload '{"battery":100,"linkquality":47,"temperature":22.24,"illuminance":10876,"occupancy":false}'
  zigbee2mqtt:info 7/21/2019, 7:38:16 PM MQTT publish: topic 'zigbee2mqtt/0x000b57fffe25384d', payload '{"state":"OFF","linkquality":60,"brightness":79}'
  zigbee2mqtt:info 7/21/2019, 7:38:16 PM MQTT publish: topic 'zigbee2mqtt/0x90fd9ffffee7cea1', payload '{"linkquality":42,"battery":47}'
  zigbee2mqtt:info 7/21/2019, 7:38:16 PM MQTT publish: topic 'zigbee2mqtt/0x000b57fffe90990c', payload '{"battery":16,"linkquality":55,"brightness":255}'
  zigbee2mqtt:info 7/21/2019, 7:38:16 PM MQTT publish: topic 'zigbee2mqtt/0x00178801021038c2', payload '{"battery":84.5,"linkquality":21,"occupancy":false,"temperature":20.58,"illuminance":23849}'

None of my zigbee devices are responding when I check them in integrations.

Anyone see what's wrong?

Should it be devices.yaml or decices.yaml? Can't see that file in share/zigbee2mqtt folder.

EDIT: Got it working without re-pairing.

[krishuang92]

It took me 3 hours to get most of my stuff running again this morning as I had to re-connect every ducking lamp in the house. This was not cool!

@krishuang92 you have to add 16 decimal numbers within the array to get it working. Something like: network_key:[1,2,3,4,5,6,7,8,9,10,11,12,13,14,15,16] Though I managed to use the default network key to start it, devices didn't come back. I already repair them but one Aqara Remote Switch (Single RockerRocker) just won't pair again. I'll try that later.

Anyway, thanks for the discussions and help.

[ReindDooyeweerd]

Thanks for the understanding everyone. Sorry to those that had to repair all of their devices. The purpose of the back up feature was to hopefully avoid this. I'm not sure why those who had a blank network key were suddenly required to enter it (or why the default network key became explicitly required), maybe a change within zigbee2mqtt config handling with the update.

I had to pair 35+ devices again (i was already re-pairing everything when the "default network key solution" came up)but that's always a risk you have to keep in mind when u use a piece of software like this so i would say, no need to feel sorry!

After a few hours work everything works flawlessly again. And better then before, better networkmap, smoother and everything seems to be stable.

[FarukGN]

@lancelon, .configuration.yaml.bk (configuration.yaml) dosyasını bilgisayarınıza indirin, 1.5.1'e güncelleyin, güncellemenin hemen ardından durduktan sonra, doğru yapılandırmayı elde etmek için "RESET TO DEFAULT" düğmesine basın. mqtt info, port, channel gibi eski config dosyaları ve yukarıdaki anahtarı kullanın, BAŞLAT'a basın, daha önce olduğu gibi çalışacaktır.

I did exactly what you said. no problem left.I've never touched a device and it works fine..thank you so much

[bartn]

Adding to the discussion; as I had some custom friendly names in my device config, I needed to also restore these in the new devices.yaml. Now HA is able to also find back these devices.

[gecata93]

Hi, can't get it to work with the standard network key. Config:

{
  "data_path": "/share/zigbee2mqtt",
  "devices": "devices.yaml",
  "groups": "groups.yaml",
  "homeassistant": true,
  "permit_join": false,
  "mqtt": {
    "base_topic": "zigbee2mqtt",
    "server": "mqtt://homeassistant:1883",
    "user": "******",
    "password": "*****"
  },
  "serial": {
    "port": "/dev/ttyACM1"
  },
  "advanced": {
    "pan_id": 6754,
    "channel": 11,
    "network_key": [
      1,
      3,
      5,
      7,
      9,
      11,
      13,
      15,
      0,
      2,
      4,
      6,
      8,
      10,
      12,
      13
    ]
  }
}

The logs:

./run.sh: line 13: [Info] Configuration backup found in /share/zigbee2mqtt/.configuration.yaml.bk. Skipping config backup.: No such file or directory
2019-07-21T19:38:07: PM2 log: Launching in no daemon mode
2019-07-21T19:38:07: PM2 log: App [npm:0] starting in -fork mode-
2019-07-21T19:38:07: PM2 log: App [npm:0] online
> zigbee2mqtt@1.5.1 start /zigbee2mqtt-1.5.1
> node index.js
  zigbee2mqtt:info 7/21/2019, 7:38:08 PM Logging to directory: '/share/zigbee2mqtt/log/2019-07-21.19-38-08'
  zigbee2mqtt:info 7/21/2019, 7:38:08 PM Starting zigbee2mqtt version 1.5.1 (commit #unknown)
  zigbee2mqtt:info 7/21/2019, 7:38:08 PM Starting zigbee-shepherd
  zigbee2mqtt:info 7/21/2019, 7:38:15 PM zigbee-shepherd started
  zigbee2mqtt:info 7/21/2019, 7:38:15 PM Coordinator firmware version: '20190223'
  zigbee2mqtt:info 7/21/2019, 7:38:15 PM Currently 9 devices are joined:
  zigbee2mqtt:info 7/21/2019, 7:38:15 PM unknown (0x00178801021036c7): 9290012607 - Philips Hue motion sensor (EndDevice)
  zigbee2mqtt:info 7/21/2019, 7:38:15 PM unknown (0x000b57fffe25384d): LED1623G12 - IKEA TRADFRI LED bulb E27 1000 lumen, dimmable, opal white (Router)
  zigbee2mqtt:info 7/21/2019, 7:38:15 PM unknown (0x90fd9ffffee7cea1): E1524 - IKEA TRADFRI remote control (EndDevice)
  zigbee2mqtt:info 7/21/2019, 7:38:15 PM unknown (0x000b57fffe90990c): ICTC-G-1 - IKEA TRADFRI wireless dimmer (EndDevice)
  zigbee2mqtt:info 7/21/2019, 7:38:15 PM unknown (0x00178801021038c2): 9290012607 - Philips Hue motion sensor (EndDevice)
  zigbee2mqtt:info 7/21/2019, 7:38:15 PM unknown (0x0017880104f79b79): 324131092621 - Philips Hue dimmer switch (EndDevice)
  zigbee2mqtt:info 7/21/2019, 7:38:15 PM unknown (0x000b57fffe2eeb99): E1525 - IKEA TRADFRI motion sensor (EndDevice)
  zigbee2mqtt:info 7/21/2019, 7:38:15 PM unknown (0x000b57fffe3210f7): LED1623G12 - IKEA TRADFRI LED bulb E27 1000 lumen, dimmable, opal white (Router)
  zigbee2mqtt:info 7/21/2019, 7:38:15 PM unknown (0x000b57fffe3239c4): E1525 - IKEA TRADFRI motion sensor (EndDevice)
  zigbee2mqtt:info 7/21/2019, 7:38:15 PM Zigbee: disabling joining new devices.
  zigbee2mqtt:info 7/21/2019, 7:38:15 PM Connecting to MQTT server at mqtt://homeassistant:1883
  zigbee2mqtt:info 7/21/2019, 7:38:15 PM zigbee-shepherd ready
  zigbee2mqtt:info 7/21/2019, 7:38:16 PM Connected to MQTT server
  zigbee2mqtt:info 7/21/2019, 7:38:16 PM MQTT publish: topic 'zigbee2mqtt/bridge/state', payload 'online'
  zigbee2mqtt:info 7/21/2019, 7:38:16 PM MQTT publish: topic 'zigbee2mqtt/0x00178801021036c7', payload '{"battery":100,"linkquality":47,"temperature":22.24,"illuminance":10876,"occupancy":false}'
  zigbee2mqtt:info 7/21/2019, 7:38:16 PM MQTT publish: topic 'zigbee2mqtt/0x000b57fffe25384d', payload '{"state":"OFF","linkquality":60,"brightness":79}'
  zigbee2mqtt:info 7/21/2019, 7:38:16 PM MQTT publish: topic 'zigbee2mqtt/0x90fd9ffffee7cea1', payload '{"linkquality":42,"battery":47}'
  zigbee2mqtt:info 7/21/2019, 7:38:16 PM MQTT publish: topic 'zigbee2mqtt/0x000b57fffe90990c', payload '{"battery":16,"linkquality":55,"brightness":255}'
  zigbee2mqtt:info 7/21/2019, 7:38:16 PM MQTT publish: topic 'zigbee2mqtt/0x00178801021038c2', payload '{"battery":84.5,"linkquality":21,"occupancy":false,"temperature":20.58,"illuminance":23849}'

None of my zigbee devices are responding when I check them in integrations.

Anyone see what's wrong?

Should it be devices.yaml or decices.yaml? Can't see that file in share/zigbee2mqtt folder.

EDIT: Got it working without re-pairing.

Can you share what did you do? I have the same problem as yours and i stuck...

[GJ2019]

Hi, can't get it to work with the standard network key. Config:

{
  "data_path": "/share/zigbee2mqtt",
  "devices": "devices.yaml",
  "groups": "groups.yaml",
  "homeassistant": true,
  "permit_join": false,
  "mqtt": {
    "base_topic": "zigbee2mqtt",
    "server": "mqtt://homeassistant:1883",
    "user": "******",
    "password": "*****"
  },
  "serial": {
    "port": "/dev/ttyACM1"
  },
  "advanced": {
    "pan_id": 6754,
    "channel": 11,
    "network_key": [
      1,
      3,
      5,
      7,
      9,
      11,
      13,
      15,
      0,
      2,
      4,
      6,
      8,
      10,
      12,
      13
    ]
  }
}

The logs:

./run.sh: line 13: [Info] Configuration backup found in /share/zigbee2mqtt/.configuration.yaml.bk. Skipping config backup.: No such file or directory
2019-07-21T19:38:07: PM2 log: Launching in no daemon mode
2019-07-21T19:38:07: PM2 log: App [npm:0] starting in -fork mode-
2019-07-21T19:38:07: PM2 log: App [npm:0] online
> zigbee2mqtt@1.5.1 start /zigbee2mqtt-1.5.1
> node index.js
  zigbee2mqtt:info 7/21/2019, 7:38:08 PM Logging to directory: '/share/zigbee2mqtt/log/2019-07-21.19-38-08'
  zigbee2mqtt:info 7/21/2019, 7:38:08 PM Starting zigbee2mqtt version 1.5.1 (commit #unknown)
  zigbee2mqtt:info 7/21/2019, 7:38:08 PM Starting zigbee-shepherd
  zigbee2mqtt:info 7/21/2019, 7:38:15 PM zigbee-shepherd started
  zigbee2mqtt:info 7/21/2019, 7:38:15 PM Coordinator firmware version: '20190223'
  zigbee2mqtt:info 7/21/2019, 7:38:15 PM Currently 9 devices are joined:
  zigbee2mqtt:info 7/21/2019, 7:38:15 PM unknown (0x00178801021036c7): 9290012607 - Philips Hue motion sensor (EndDevice)
  zigbee2mqtt:info 7/21/2019, 7:38:15 PM unknown (0x000b57fffe25384d): LED1623G12 - IKEA TRADFRI LED bulb E27 1000 lumen, dimmable, opal white (Router)
  zigbee2mqtt:info 7/21/2019, 7:38:15 PM unknown (0x90fd9ffffee7cea1): E1524 - IKEA TRADFRI remote control (EndDevice)
  zigbee2mqtt:info 7/21/2019, 7:38:15 PM unknown (0x000b57fffe90990c): ICTC-G-1 - IKEA TRADFRI wireless dimmer (EndDevice)
  zigbee2mqtt:info 7/21/2019, 7:38:15 PM unknown (0x00178801021038c2): 9290012607 - Philips Hue motion sensor (EndDevice)
  zigbee2mqtt:info 7/21/2019, 7:38:15 PM unknown (0x0017880104f79b79): 324131092621 - Philips Hue dimmer switch (EndDevice)
  zigbee2mqtt:info 7/21/2019, 7:38:15 PM unknown (0x000b57fffe2eeb99): E1525 - IKEA TRADFRI motion sensor (EndDevice)
  zigbee2mqtt:info 7/21/2019, 7:38:15 PM unknown (0x000b57fffe3210f7): LED1623G12 - IKEA TRADFRI LED bulb E27 1000 lumen, dimmable, opal white (Router)
  zigbee2mqtt:info 7/21/2019, 7:38:15 PM unknown (0x000b57fffe3239c4): E1525 - IKEA TRADFRI motion sensor (EndDevice)
  zigbee2mqtt:info 7/21/2019, 7:38:15 PM Zigbee: disabling joining new devices.
  zigbee2mqtt:info 7/21/2019, 7:38:15 PM Connecting to MQTT server at mqtt://homeassistant:1883
  zigbee2mqtt:info 7/21/2019, 7:38:15 PM zigbee-shepherd ready
  zigbee2mqtt:info 7/21/2019, 7:38:16 PM Connected to MQTT server
  zigbee2mqtt:info 7/21/2019, 7:38:16 PM MQTT publish: topic 'zigbee2mqtt/bridge/state', payload 'online'
  zigbee2mqtt:info 7/21/2019, 7:38:16 PM MQTT publish: topic 'zigbee2mqtt/0x00178801021036c7', payload '{"battery":100,"linkquality":47,"temperature":22.24,"illuminance":10876,"occupancy":false}'
  zigbee2mqtt:info 7/21/2019, 7:38:16 PM MQTT publish: topic 'zigbee2mqtt/0x000b57fffe25384d', payload '{"state":"OFF","linkquality":60,"brightness":79}'
  zigbee2mqtt:info 7/21/2019, 7:38:16 PM MQTT publish: topic 'zigbee2mqtt/0x90fd9ffffee7cea1', payload '{"linkquality":42,"battery":47}'
  zigbee2mqtt:info 7/21/2019, 7:38:16 PM MQTT publish: topic 'zigbee2mqtt/0x000b57fffe90990c', payload '{"battery":16,"linkquality":55,"brightness":255}'
  zigbee2mqtt:info 7/21/2019, 7:38:16 PM MQTT publish: topic 'zigbee2mqtt/0x00178801021038c2', payload '{"battery":84.5,"linkquality":21,"occupancy":false,"temperature":20.58,"illuminance":23849}'

None of my zigbee devices are responding when I check them in integrations. Anyone see what's wrong? Should it be devices.yaml or decices.yaml? Can't see that file in share/zigbee2mqtt folder. EDIT: Got it working without re-pairing.

Can you share what did you do? I have the same problem as yours and i stuck...

Same here! I have set everything back to defaults, typed over the settings from the old configuration, and added the default network key. After restarting the Add-on the devices ( Xiaomi Sensors ) where available in HA again, but i don't get any status from any device. I am really hoping for a solution to , since i don't want to get all my sensors back in front of my Raspberry PI... BTW; i neither don't see any devices.yaml file in my folders

[gecata93]

@GJ2019 probably we have to create devices.yaml, but i dont have example configuration. In previous version 1.4.0 devices where automatically added to the array of devices i just changed the friendly_name and it was all good. Now i'm not sure in the new version file is called devices.yaml but what file structure should we use json or yaml?! And is it mandatory to have such file at all? I tried make configuration based on this, but with no luck: https://www.zigbee2mqtt.io/configuration/device_specific_configuration.html

[ebudalen]

I removed the port number in mqtt server settings in the add-on, and rebooted my intel nuc, then everything worked. Try that.

[GJ2019]

Believe it or not... but 1.5.1.1 had just been released ? Does it fix those issues ?

[GJ2019]

@zepixer: Did you removed the port number on the mqtt link ? In the config from the Zigbee2mqtt add-on?

[ebudalen]

@GJ2019 yes, that's correct.

[GJ2019]

@zepixer : Nope...no result. Still see the devices , but status doesn’t change. For example a Xiaomi door sensor tells me that a door is open which is definitely closed. Temperature on the temperature sensors doesn’t change.

[ebudalen]

@GJ2019 ok, if you also rebooted your host computer, I don't know what you can do. I have not tried v. 1.5.1.1 yet.

Maybe you can post your sensored add-on config?

[GJ2019]

@GJ2019 ok, if you also rebooted your host computer, I don't know what you can do. I have not tried v. 1.5.1.1 yet.

Maybe you can post your sensored add-on config?

Sure i can !

The config : { "data_path": "/share/zigbee2mqtt", "devices": "devices.yaml", "groups": "groups.yaml", "homeassistant": true, "permit_join": false, "mqtt": { "base_topic": "zigbee2mqtt", "server": "mqtt://192.168.178.20:1883", "user": "myusername", "password": "mypassword" }, "serial": { "port": "/dev/ttyACM0", "disable_led": true }, "advanced": { "pan_id": 6754, "channel": 11, "network_key": [ 1, 3, 5, 7, 9, 11, 13, 15, 0, 2, 4, 6, 8, 11, 12, 13 ] } }

The latest log from /share/zigbee2mqtt/log: 7/23/2019, 8:49:25 AM - info: Logging to directory: '/share/zigbee2mqtt/log/2019-07-23.08-49-22' 7/23/2019, 8:49:25 AM - info: Starting zigbee2mqtt version 1.5.1 (commit #unknown) 7/23/2019, 8:49:25 AM - info: Starting zigbee-shepherd 7/23/2019, 8:49:27 AM - info: zigbee-shepherd started 7/23/2019, 8:49:27 AM - info: Coordinator firmware version: '20190425' 7/23/2019, 8:49:27 AM - info: Currently 9 devices are joined: 7/23/2019, 8:49:27 AM - info: unknown (0x00158d000233bdxx): SJCGQ11LM - Xiaomi Aqara water leak sensor (EndDevice) 7/23/2019, 8:49:27 AM - info: unknown (0x00158d0002f2ecxx): WSDCGQ11LM - Xiaomi Aqara temperature, humidity and pressure sensor (EndDevice) 7/23/2019, 8:49:27 AM - info: unknown (0x00158d00031356xx): DJT11LM - Xiaomi Aqara vibration sensor (EndDevice) 7/23/2019, 8:49:27 AM - info: unknown (0x00158d00033ab6xx): MCCGQ11LM - Xiaomi Aqara door & window contact sensor (EndDevice) 7/23/2019, 8:49:27 AM - info: unknown (0x00158d00033dddxx): WSDCGQ11LM - Xiaomi Aqara temperature, humidity and pressure sensor (EndDevice) 7/23/2019, 8:49:27 AM - info: unknown (0x00158d0002f2ddxx): WSDCGQ11LM - Xiaomi Aqara temperature, humidity and pressure sensor (EndDevice) 7/23/2019, 8:49:27 AM - info: unknown (0x00158d0002703xxx): SJCGQ11LM - Xiaomi Aqara water leak sensor (EndDevice) 7/23/2019, 8:49:27 AM - info: unknown (0x00158d000321dxxx): MCCGQ11LM - Xiaomi Aqara door & window contact sensor (EndDevice) 7/23/2019, 8:49:27 AM - info: unknown (0x00158d0003946xxx): MCCGQ11LM - Xiaomi Aqara door & window contact sensor (EndDevice) 7/23/2019, 8:49:27 AM - info: Zigbee: disabling joining new devices. 7/23/2019, 8:49:27 AM - info: Connecting to MQTT server at mqtt://192.168.178.20:1883 7/23/2019, 8:49:28 AM - info: zigbee-shepherd ready 7/23/2019, 8:49:28 AM - info: Connected to MQTT server 7/23/2019, 8:49:28 AM - info: MQTT publish: topic 'zigbee2mqtt/bridge/state', payload 'online' 7/23/2019, 8:49:28 AM - info: MQTT publish: topic 'zigbee2mqtt/0x00158d000233bxxx', payload '{"battery":100,"voltage":3015,"linkquality":23,"water_leak":false}' 7/23/2019, 8:49:28 AM - info: MQTT publish: topic 'zigbee2mqtt/0x00158d0002f2exxx', payload '{"temperature":25.12,"linkquality":60,"humidity":65.42,"pressure":1019,"battery":86,"voltage":2975}' 7/23/2019, 8:49:28 AM - info: MQTT publish: topic 'zigbee2mqtt/0x00158d0003135xxx', payload '{"angle":7,"linkquality":0,"angle_x":-1,"angle_y":80,"angle_z":10,"angle_x_absolute":91,"angle_y_absolute":10,"battery":100,"voltage":3015}' 7/23/2019, 8:49:28 AM - info: MQTT publish: topic 'zigbee2mqtt/0x00158d00033abxxx', payload '{"contact":false,"linkquality":36,"battery":100,"voltage":3045}' 7/23/2019, 8:49:28 AM - info: MQTT publish: topic 'zigbee2mqtt/0x00158d00033ddxxx', payload '{"temperature":24.36,"linkquality":0,"humidity":52.54,"pressure":1020,"battery":91,"voltage":2985}' 7/23/2019, 8:49:28 AM - info: MQTT publish: topic 'zigbee2mqtt/0x00158d0002f2dxxx', payload '{"temperature":25.64,"linkquality":44,"humidity":60.62,"pressure":1020,"battery":97,"voltage":2995}' 7/23/2019, 8:49:28 AM - info: MQTT publish: topic 'zigbee2mqtt/0x00158d0002703xxx', payload '{"water_leak":false,"linkquality":31,"battery":100,"voltage":3025}' 7/23/2019, 8:49:28 AM - info: MQTT publish: topic 'zigbee2mqtt/0x00158d000321dxxx', payload '{"contact":true,"linkquality":44,"battery":100,"voltage":3055}' 7/23/2019, 8:49:28 AM - info: MQTT publish: topic 'zigbee2mqtt/0x00158d0003946xxx', payload '{"battery":100,"voltage":3105,"contact":true,"linkquality":60}' 7/23/2019, 8:49:28 AM - info: MQTT publish: topic 'zigbee2mqtt/bridge/config', payload '{"version":"1.5.1","commit":"unknown","coordinator":20190425,"log_level":"info","permit_join":false}'

Here you see the example of the problem i have... Guess when i installed the Add-on update ;-) BTW: The last update time was when i rebooted HA.

[ebudalen]

I don't know whats causing this, can only ask you to try the same things I have done. First, delete the disable led config, save and restart mqtt add on. If not, try unplugging and plug back in your coordinator, then restart add-on. Lastly try using "mqtt://homeassistant" as server name, instead of ip adress and port number.

[GJ2019]

Thanks for the support... but nope, no result. Even did a restart of the whole PI, but no updates are pushed from the sensors to HA. Afraid i have to re-pair all of my devices :-( Have also tried 1.5.1.1, but that won’t even start

[ghost]

Similar problems here. After updating to 1.5.1.1 and fixing config, the log ends with:

zigbee2mqtt:error 7/23/2019, 7:46:03 AM Failed to mount the cieApp

And nothing after that.

[Pjanssen]

For me starting the addon worked again after adding availability_blacklist to the options:

{
  ....
  "advanced": {
    ....
    "availability_blacklist": []
  },
  ....
}

[Stephan296]

For me works to change: "disable_led": "bool?" to "disable_led": true

You could also use false instead of true.

Check also the name of your devices.yaml, in my case it was named [] instead of devices.yaml

[gewoonik]

the next thing to do is get rid of the if the network_key starts with the number 0 remove 0 change - 080 to 80

after that also the "disable_led": "bool?" Change to "disable_led": false

configuration.yaml file advanced: network_key: -8 -024 -080 -106 -217 -015 -045 -244 -27 -188 -77 -205 -27 -35 -187 -178

###################### config.json file ###################### { "data_path": "/share/zigbee2mqtt", "devices": "devices.yaml", "groups": "groups.yaml", "homeassistant": true, "permit_join": false, "mqtt": { "base_topic": "zigbee2mqtt", "server": "mqtt://192.168.2.50", "user": "username", "password": "password" }, "serial": { "port": "/dev/ttyACM0", "disable_led": false }, "advanced": { "network_key": [ 8, 24, 80, 106, 217, 15, 45, 244, 27, 188, 77, 205, 27, 35, 187, 178 ], "availability_blacklist": [] }, "ban": [], "whitelist": [], "queue": {} }

[ivanskj]

I can confirm that solutions provided by @Pjanssen and @gewoonik works for me on v.1.5.1.1. Thanks! :)

[GuGu927]

@GJ2019 I have same issues with my xiaomi sensors. I refalsh coordinator firmware, I re pair devices, it not works. you solve problem?