Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Stuck in status "Starting Z-Wave Driver..." #77

Closed
elvee77 opened this issue Jul 9, 2021 · 9 comments
Closed

Stuck in status "Starting Z-Wave Driver..." #77

elvee77 opened this issue Jul 9, 2021 · 9 comments
Assignees
Labels
help-wanted Extra attention is needed waiting-for-info Waiting for further info/outcome

Comments

@elvee77
Copy link

elvee77 commented Jul 9, 2021

Plugin Version
latest (downloaded today)

Platform
RPI

I have the Aeotec Z-Wave Plus Z-Stick gen5 in my Pi and the zwave.js node its serial port is set to /dev/ttyAMA0
The only odd thing is that the status of the node is stuck on "Starting Z-Wave Driver...".

Is this a common isuse? Of not, I could just try a fresh image on my Pi and see if the issue persits?

@elvee77 elvee77 added the help-wanted Extra attention is needed label Jul 9, 2021
@crxporter
Copy link
Collaborator

crxporter commented Jul 9, 2021

Have you tried /dev/ttyACM0 ? That's where my usb stick shows up on raspberry pi.

I usually get the starting status for 10-15 seconds at boot.

@marcus-j-davies
Copy link
Member

marcus-j-davies commented Jul 9, 2021

As @crxporter pointed out.

/dev/ttyAMA0 Is not right - it should be /dev/ttyACM0 for Aeotec at least.
ttyAMA0 is either bluetooth or the GPIO TX/RX (depending on Hardware)

@elvee77
Copy link
Author

elvee77 commented Jul 10, 2021

Ok, found this as a good possible reason on why the usb stick is not showing: raspberrypi/linux#3027
Apparently the Aeotec stick is not working on RPi4 and the workaround is using a USB-Hub. (Some USB2.0 vs 3.0 handshaking issue). I will buy a cheap hub and then check in again to confirm this was the issue!

@marcus-j-davies
Copy link
Member

That is exactly what I do.

The Aeotec USB dongle has issues on Pi4 (I use a pound/dollar land type USB 2.0 hub), and it works great.
Please let us know if this works - and you are able to get off the ground with it and start using this node. 👍

@marcus-j-davies marcus-j-davies added the waiting-for-info Waiting for further info/outcome label Jul 10, 2021
@marcus-j-davies
Copy link
Member

@elvee77,

Any update with your set up?
I like to keep things fresh in my mind with help requests, hence the ping.

@elvee77
Copy link
Author

elvee77 commented Jul 14, 2021

It is like magic!! Stick is detected and using the custom Node-Red menu (that is very nice by the way!) I was already able to reset the stick.

Tomorrow I am going to start playing with it.

I have 50+ Fibaro devices in my house, but the HC2 freezes from time to time. Even when I do most of the automation using Node-Red and the Fibaro API, it still freezes. So very happy to remove this buggy component in the future! This project is a very nice surprise! Thank you guys for the effort!!

@elvee77 elvee77 closed this as completed Jul 14, 2021
@marcus-j-davies
Copy link
Member

That's great to hear.
Please do reach out for any help required.

welcome to node-red-contrib-zwave-js

@Lucas68-000
Copy link

Lucas68-000 commented Mar 3, 2024

Hello everyone y obtain the same errors on a raspberry pi 4 the node red is stucks at "Starting driver nodejs" and i have a dongle 7 i have try to connect the dongle on the usb 2 and or usb 3 and i have the same errors

---------------------------------------------------------------------
Your flow credentials file is encrypted using a system-generated key.

If the system-generated key is lost for any reason, your credentials
file will not be recoverable, you will have to delete it and re-enter
your credentials.

You should set your own key using the 'credentialSecret' option in
your settings file. Node-RED will then re-encrypt your credentials
file using your chosen key the next time you deploy a change
--------------------------------------------------------------------
03/03/2024 13:18:27
msg : string[129]
[serialconfig:ccce6b9ce5924ec6] serial port /dev/ttyPKW3 error: Error: Error: No such file or directory, cannot open /dev/ttyPKW3"

can some people can help me? or have the same problems

@marcus-j-davies
Copy link
Member

I am afraid this doesn't appear to be anything related to this module

[serialconfig] is not a node we develop, but a node by Node RED them self.
you need to take this up with Node RED.

But if it's any consolation (and the fact you get stuck at connecting...) suggests Node RED cant see your serial port.
this usually means you are running Node RED as a container (for example HA) - you will need to take this up with said community if that is case

@zwave-js zwave-js locked and limited conversation to collaborators Mar 3, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
help-wanted Extra attention is needed waiting-for-info Waiting for further info/outcome
Projects
None yet
Development

No branches or pull requests

4 participants