That did not work either
Get you. I actually only work in the yaml. Learned it that way and tend to find it easier.
Hi @wrcvr4
Can you verify the linux privileges for the ttyACM0 file? Cause it is there but question is if accessible by zigbeee2mqtt user
Plus for being on secure side for the serial port naming over restarts and potential port change try to look at this:
Thanks @TriStone
So I should mention I’m running hassio on ubuntu as a VM on my qnap
The CC2531 is passed through to the VM (Has worked for a long time)
Ubuntu can see it when its passed through
Permission on the ttyACM0 file (ubuntu)
crw-rw---- 1 root dialout 166, 0 Apr 28 14:41 ttyACM0
I had access issues in past when running HA in Debian in LXC container (a bit differrent situation, I know 
) with exactly the same privilege you have.
Which should work but did not.
So I started to use the UDEV rules not only to assign strict device path in Linux but also to set privileges to 777 (not optimal, but for single purpose device not a big security risk) and this way the privileges survives.
Try just temporary set the privileges to full access for all - chmod 0x777 ttyACM0 - and start HA.
Thanks
No change
I did read somewhere people reflashed the cc2531 and it fixed the issue for them
Should I flash 3.0 or 1.2 ? I do have a zigbee 3 downlight
zigbee2mqtt:error 2020-04-28 17:23:18: Error while starting zigbee-herdsman
zigbee2mqtt:error 2020-04-28 17:23:18: Failed to start zigbee
zigbee2mqtt:error 2020-04-28 17:23:18: Exiting...
zigbee2mqtt:error 2020-04-28 17:23:18: Error: Failed to connect to the adapter (Error: SRSP - SYS - ping after 6000ms)
at ZStackAdapter.<anonymous> (/zigbee2mqtt-1.12.0/node_modules/zigbee-herdsman/dist/adapter/z-stack/adapter/zStackAdapter.js:71:23)
at Generator.throw (<anonymous>)
at rejected (/zigbee2mqtt-1.12.0/node_modules/zigbee-herdsman/dist/adapter/z-stack/adapter/zStackAdapter.js:6:65)
Can you put Zigbee2mqtt to debug?
In config:
advanced:
log_level: debug
I had it in debug before, but was reverted when I restored a snapshot trying to fix it
> node index.js
zigbee2mqtt:info 2020-04-28 18:04:21: Logging to console and directory: '/share/zigbee2mqtt/log/2020-04-28.18-04-21' filename: log.txt
zigbee2mqtt:debug 2020-04-28 18:04:21: Removing old log directory '/share/zigbee2mqtt/log/2020-04-28.18-00-49'
zigbee2mqtt:debug 2020-04-28 18:04:23: Loaded state from file /share/zigbee2mqtt/state.json
zigbee2mqtt:info 2020-04-28 18:04:24: Starting zigbee2mqtt version 1.12.0 (commit #unknown)
zigbee2mqtt:info 2020-04-28 18:04:24: Starting zigbee-herdsman...
zigbee2mqtt:debug 2020-04-28 18:04:24: Using zigbee-herdsman with settings: '{"network":{"panID":6754,"extendedPanID":[221,221,221,221,221,221,221,221],"channelList":[11],"networkKey":"HIDDEN"},"databasePath":"/share/zigbee2mqtt/database.db","databaseBackupPath":"/share/zigbee2mqtt/database.db.backup","backupPath":"/share/zigbee2mqtt/coordinator_backup.json","serialPort":{"baudRate":115200,"rtscts":true,"path":"/dev/ttyACM0"}}'
zigbee2mqtt:error 2020-04-28 18:04:32: Error while starting zigbee-herdsman
zigbee2mqtt:error 2020-04-28 18:04:32: Failed to start zigbee
zigbee2mqtt:error 2020-04-28 18:04:32: Exiting...
zigbee2mqtt:error 2020-04-28 18:04:32: Error: Failed to connect to the adapter (Error: SRSP - SYS - ping after 6000ms)
at ZStackAdapter.<anonymous> (/zigbee2mqtt-1.12.0/node_modules/zigbee-herdsman/dist/adapter/z-stack/adapter/zStackAdapter.js:71:23)
at Generator.throw (<anonymous>)
at rejected (/zigbee2mqtt-1.12.0/node_modules/zigbee-herdsman/dist/adapter/z-stack/adapter/zStackAdapter.js:6:65)
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-04-28T08_04_32_945Z-debug.log
2020-04-28T18:04:34: PM2 log: App [npm:0] exited with code [1] via signal [SIGINT]
2020-04-28T18:04:34: PM2 log: App [npm:0] starting in -fork mode-
2020-04-28T18:04:34: PM2 log: App [npm:0] online
> [email protected] start /zigbee2mqtt-1.12.0
> node index.js
Nothing new 
There are two topics mentioning this at Koenkk’s GitHub:
In one the re-flash is suggested, other one is quite interesting - pressing reset button after restart might help.
And maybe upgrading to 1.12.2 might help too.
I was running this version which started the issue, before restoring a snapshot
Tried the reset button the other day, no change
Will look at digging out the flashing hardware tomorrow
Do I go 1.2 or 3.0 fw ?
I would suggest not to do too many changes at once. So if you have now the FW 1.2, I would stick to that even now.
Today I got the case @TriStone ! Tomorrow I get the CC2652R, 8 days deliver …
Any tips for programming ?
Cheers!
There is a new method for buttons, maybe this is the problem? Buttons no longer have the click and action sensors. If you use the Automation wizard in Home Assistant you can easily use the new method which are Device triggers.
But if you want the old way maybe this option in configuration.yaml will work for you:
homeassistant_legacy_triggers: true
Good point. I did try playing with that setting, but i actually tried disabling it to make things work with old automations. Then i commented the line and assumed it would default to “true”. Probably should have set it explicitly. What’s weird is that i did see ‘_click’ topics being updated in the logs, just hass didn’t see them at all.
I ended up wiping that build for now as it was giving me more trouble than good and moved the remaining devices back to their original xiaomi/ikea hubs.After doing some more research i figured that cc2530 won’t handle my network anyway (i have about 20 xiaomi devices and another 20 ikea lights and a few more odd ones), and ESP8266 probably wasn’t the best in my case as 2.4Ghz is quite noisy where i am. Still keen to give z2m another shot but probably with a different coordinator, like CC2652R or the other powerful one when i have a chance as keeping things on four different hubs is kind of silly. Just not sure how stable those new boards are yet.
This evening. Everything went smoothly.
Same here. All good after the upgrade.
Thank you.
I just updated without any problem 