I had a perfectly good zigbee2mqtt config working prior 0.115. Now it says “missing option availability_blacklist in advanced”. But it is there, indentation is correct, nothing changed. Rebooting host didn’t help. Zigbee2mqtt addon 1.14.4.1. What to do? Thanks!
Change it to availability_blocklist (with an O not an A), you also need to include availability_passlist (which used to be white list, and also used to be optional, but is now mandatory).
You will likely also find that there is another couple of settings that had white/black in them that also need changing to pass/block.
Hope this helps.
1 Like
Hey there!
I had the same issue, I solved it by seeing this ERRROR AFTER UPDATING -- Failed to start addon - configruation validation faled! Missing option availability_passlist in advanced. · Issue #4391 · Koenkk/zigbee2mqtt · GitHub
Basically like a user responded there:
I restored the default settings. Then rewrote the username, password, channel and network key from previous settings. Now works without any problems
It’s only after pressing the restore default settings button AND then manually adding the parts mentioned above that fixed it for me
I had the same issue.
I ended by copying my current incorret configuration, reseting it to the default configuration correctly formated, and then refill my 4 or 5 customized parameters.
Works perfectly now. 
You guys fixed it! Thanks!
this is not working for me.
[s6-init] making user provided files available at /var/run/s6/etc…exited 0.
[s6-init] ensuring user provided files have correct perms…exited 0.
[fix-attrs.d] applying ownership & permissions fixes…
[fix-attrs.d] done.
[cont-init.d] executing container initialization scripts…
[cont-init.d] done.
[services.d] starting services
[services.d] done.
./run.sh: line 17: [Info] Configuration backup found in /share/zigbee2mqtt/.configuration.yaml.bk. Skipping config backup.: No such file or directory
[Info] Socat is DISABLED and not started
2020-09-18T22:00:03: PM2 log: Launching in no daemon mode
2020-09-18T22:00:03: PM2 log: App [npm:0] starting in -fork mode-
2020-09-18T22:00:03: PM2 log: App [npm:0] online
[email protected] start /zigbee2mqtt-1.14.4
node index.js
Zigbee2MQTT:info 2020-09-18 22:00:05: Logging to console and directory: ‘/share/zigbee2mqtt/log/2020-09-18.22-00-05’ filename: log.txt
Zigbee2MQTT:info 2020-09-18 22:00:05: Starting Zigbee2MQTT version 1.14.4 (commit #unknown)
Zigbee2MQTT:info 2020-09-18 22:00:05: Starting zigbee-herdsman…
Zigbee2MQTT:error 2020-09-18 22:00:06: Error while starting zigbee-herdsman
Zigbee2MQTT:error 2020-09-18 22:00:06: Failed to start zigbee
Zigbee2MQTT:error 2020-09-18 22:00:06: Exiting…
Zigbee2MQTT:error 2020-09-18 22:00:06: Error: Error while opening serialport ‘Error: Error: No such file or directory, cannot open /dev/ttyACM0’
at Znp. (/zigbee2mqtt-1.14.4/node_modules/zigbee-herdsman/dist/adapter/z-stack/znp/znp.js:136:32)
at Generator.next ()
at /zigbee2mqtt-1.14.4/node_modules/zigbee-herdsman/dist/adapter/z-stack/znp/znp.js:27:71
at new Promise ()
at __awaiter (/zigbee2mqtt-1.14.4/node_modules/zigbee-herdsman/dist/adapter/z-stack/znp/znp.js:23:12)
at SerialPort. (/zigbee2mqtt-1.14.4/node_modules/zigbee-herdsman/dist/adapter/z-stack/znp/znp.js:134:49)
at SerialPort._error (/zigbee2mqtt-1.14.4/node_modules/zigbee-herdsman/node_modules/@serialport/stream/lib/index.js:198:14)
at /zigbee2mqtt-1.14.4/node_modules/zigbee-herdsman/node_modules/@serialport/stream/lib/index.js:242:12
npm ERR!
code ELIFECYCLE
npm ERR! errno 1
npm
ERR! [email protected] start:node index.js
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the [email protected] 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/2020-09-18T20_00_06_126Z-debug.log
Yours is because zigbee2mqtt can’t find your zigbee dongle, as clearly documented in the error message you posted.
that’s right, my device (an intel NUC) does recognize the dongle.
I reinstalled the addon and now it works.
1 Like
Now the addon exposes correctly a changelog. Should contain (hopefully) breaking changes.
Make sure to watch out also for the new integrated frontend in the future releases (available in edge)