Stuck in status "Starting z-wave driver"

[vegartb]

I have bought the z-pi 7 from Aeotech. I Have followed their instructions and disabled the bluetooth. Then the serialport should be ttyAMA0. When I Select this serialport in zwave-js the controller node don`t work. I can not find the solution. Does anyone have a tip?? :-)

[marcus-j-davies]

Hi @vegartb
what serial ports do you see listed in the drop down?

EDIT
Not to worry I can see them listed 😅

Have you followed this fully?
https://aeotec.freshdesk.com/support/solutions/articles/6000230551-z-pi-7-user-guide-

There should be no reason it will not be detected by zwave js

is anything appearing in the debug console of Node RED
if after the reboot its not responding, I would think that the Bluetooth stack is still ocupying ttyAMA0

[marcus-j-davies]

Also try adding pi to this group also

sudo usermod -a -G tty pi

so all together

sudo usermod -a -G dialout pi
sudo usermod -a -G tty pi

[vegartb]

whoami:

I did both the usermod, but still the same permission denied... :-P

[marcus-j-davies]

ok do this.
cat /dev/ttyAMA0

do you get access denied?

and you restarted after adding to both groups?

[vegartb]

sudo reboot. yepp.
This is after boot:

...I also tried usermod as root user (sudo -s)...
No access.

[marcus-j-davies]

Ok,

What does this return.

ls -l /dev/ttyAMA0

[vegartb]

[marcus-j-davies]

Ok,

quick test

run this -> id, to make sure the pi user is apart of tty

if so run this.
sudo chmod 660 /dev/ttyAMA0 (don't restart) but instead restart node red.

This adds read/write to this device for the group tty

For what its worth, all that is happening here, is the device /dev/ttyAMA0 cannot be accessed by the pi user (that node red is running under)

[vegartb]

The chmod 660 was not allowed as pi user:

When I run the command as root the error msg. change in node-red....

[vegartb]

ok.... this is not easy to understand... You where right about the conflikt on the port....
But it did not resolve befor I turned off serial console:

Sorry fore all the hasl!! I will now try to test the rest of the nodes :-) Thanks for all help!! I am still not sure about what did the trick... should probably have turned off everything first? I could reinstall everything and try once more... :-)

[marcus-j-davies]

No need to apologies.

Aeotec need to update their guide 😒
glad your up and running