UPDATE 31.10.: Amazon Alexa - ioBroker Skill läuft aus ?

[ap2017]

@Asgothian After Zigbee failed, after usual troubleshooting, restarting, etc., I updated Linux with "sudo apt-get update && sudo apt-get upgrade -y", which, I believe updated my Node.js to 12.8.4. Just in case, I run "npm rebuild" after. I am not sure all of this was necessary, I am totally not an expert. It is interesting that Zwave adapter works fine with ACM0 and ACM1 ports, but Zigbee stopped working with any port selected. Here my log file. Thank you for your help.
9-19-2020 Zigbee.txt

[Asgothian]

@ap2017 The node update may be the reason.
The log mentions that the port does not exist. I would suggest that you follow the steps below:

• back up your zigbee database (/opt/iobroker/iobroker-data/zigbee_0/shepherd.db)
• delete the zigbee instance
• remove the zigbee adapter
• reinstall the zigbee adapter (it seems you installed it from Github, so you should do that again)
• configure the adapter
• if your zigbee-components are missing, stop the adapter, restore the shepherd.db, then restart the adapter.

A.

[ap2017]

@Asgothian I did what you recommended. Same results "Error: Device or resource busy, cannot open /dev/ttyACM1' at Znp.<anonymous> (/opt/iobroker/node_modules/iobroker.zigbee/node_modules/zigbee-he
zigbe" and "Error: Failed to connect to the adapter (Error: Cannot request when znp has not been initialized yet)"

[Asgothian]

@ap2017 are you sure you do not have something else using that serial port ?
The message "cannot open /dev/ttyACM1" is an indicator that the port either in use or blocked by the system (not read/write for the given user)

[ap2017]

@Asgothian It looks like ACM1 is reserved for zigbee adapter.

[Asgothian]

@ap2017 No. this only means that the /dev/ttyACM1 is actually the adapter of the stick. The question is if any other process is using it.

A.

[ap2017]

@Asgothian Not sure how to check it. I only have three hardware related adapters: zWave which is on ACM0, mySensors on USB0 and zigbee on ACM1. As I mention before, if I disable zigbee, zWave runs fine on ACM1.

[ap2017]

@Asgothian Interesting that if I try to use other port like S1, getting different error message

"Error: Error while opening serialport 'Error: Error: Input/output error setting custom baud rate of 115200' at Znp.<anonymous> (/opt/iobroker/node_modules/iobroker.zigbee/node_modules/zigbe"

[ap2017]

@Asgothian Running ioBroker fixer did not help:

sudo iobroker stop
curl -sL https://iobroker.net/fix.sh | bash -
sudo iobroker start

[ap2017]

@Asgothian During npm rebuild received bunch of errors associated with serial port, see log. Could it be related to my problem?
2020-09-23T02_39_28_639Z-debug.log

[Asgothian]

@ap2017
It should not. You have an old version of the serial port library (6.2.2) still installed. The zigbee-adapter should use serial port 9.x
Can you check NPM List if it is still present ?
You might see a large number of "extraneous" packages listed.
I would suggest to run "npm prune --dry-run" to see what is removed if you prune, and - unless packages are removed you consider needed - follow it up with an "npm prune"

A.

[ap2017]

@Asgothian Pardon my ignorance, how do I check NPM list? In terms of pruning, I have no idea what do I needs. I have very rudimentary knowledge of command line controls, I am one of those users who appreciate very much object level system configuration. That is why I like ioBroker, it seems to me well though through for this purpose. As always, thank you for your time and help.

[Thomas Braun]

@ap2017

cd /opt/iobroker
npm list serialport

Should look similar to

pi@raspberrypi:/opt/iobroker $ npm list serialport
iobroker.inst@2.0.3 /opt/iobroker
└─┬ iobroker.zigbee@1.2.1
  └─┬ zigbee-herdsman@0.12.117
    └── serialport@9.0.1

[ap2017]

@Thomas-Braun said in Zigbee adapter stopped working:

npm list serialport

Here we go:

[Asgothian]

@ap2017 I apologise. I should have put quotes around the "npm list", as that was the command i wanted you to check.

As you can see, there is an extra serialport library installed, but each adapter has (should have) a usable version, so you should be able to remove the extra one.

npm prune should get rid of it.

A.

[ap2017]

@Asgothian No problem. I run the following, but still have same extraneous serial library 6..2.2 when run "npm list serialport"

cd /opt/iobroker
npm prune --dry-run
sudo reboot

[ap2017]

@Asgothian As previously, keep getting these errors:

zigbee.0 2020-09-24 10:39:10.082 error (2461) Error: Error while opening serialport 'Error: Error: Device or resource busy, cannot open /dev/ttyACM1' at Znp.<anonymous> (/opt/iobroker/node_modules/iobroker.zigbee/node_modules/zigbee-he
zigbee.0 2020-09-24 10:39:10.081 error (2461) Failed to start Zigbee
zigbee.0 2020-09-24 10:39:09.975 info (2461) Starting Zigbee...
zigbee.0 2020-09-24 10:39:09.974 info (2461) Try to reconnect. 1 attempts left
zigbee.0 2020-09-24 10:38:59.972 error (2461) Error: Failed to connect to the adapter (Error: Cannot request when znp has not been initialized yet) at ZStackAdapter.<anonymous> (/opt/iobroker/node_modules/iobroker.zigbee/node_modules/z
zigbee.0 2020-09-24 10:38:59.972 error (2461) Failed to start Zigbee

[Asgothian]

@ap2017
Of course.. the "npm prune --dry-run" only lists what it would do. This is to ensure that it doesn't get rid of something you want to keep
once you checked the list, you can do "npm prune" (without the dry run)

a Reboot is not needed..

A.

[ap2017]

@Asgothian The unwanted serial driver 6.2.2 disappeared after pruning, but it did not help to resolve the main issue, see errors below. I rebooted controller after pruning, just in case.

[Asgothian]

@ap2017
Unfortunately, that is what i expected. Now you should no longer get any errors on an npm rebuild, but i have the feeling that is not the error. I am starting to think that the firmware on the Zigbee Board / Stick is not responding correctly.

As long as there is a message that the zigbee library cannot be initialized, the issue is most likely hardware related.

A.