[SOLVED] 12.04 Aeon Z-stick (Zwave) is not detected by PnP

[davegravy]

Anyone experienced this?

I've tried unplugging and replugging the usb dongle.

dmesg sees it:

Code: [Select]

[ 1668.440102] usb 1-1.4.1: new full-speed USB device number 25 using ehci_hcd
[ 1668.552648] cp210x 1-1.4.1:1.0: cp210x converter detected
[ 1668.644276] usb 1-1.4.1: reset full-speed USB device number 25 using ehci_hcd
[ 1668.753372] usb 1-1.4.1: cp210x converter now attached to ttyUSB0

And it works fine on my 10.04 install.

I created a ticket here:http://svn.linuxmce.org/trac/ticket/2207

[davegravy]

I captured DCERouter.log after plugging in the dongle to the usb port. Here is the output which I'm not very able to make much sense of. I hope I captured a long enough period.

paste.ubuntu.com/8255104/

[phenigma]

PnpQueue::Process_Detect_Stage_Confirm_Possible_DT queue 7850 already unknown <0x8b9adb40>

^^ This line here indicates that the device is found in the Unknown Devices table.  Which means it has been told to Not be used and don't ever ask me again.  Hence why it is not adding the device.  Find the device in the webadmin -> advanced -> unknown devices list and remove it.  It should add itself the next time it is detected.

J.

[davegravy]

Massive face-palm.  How did I not think to check that... I know better.

[tompin2]

PnpQueue::Process_Detect_Stage_Confirm_Possible_DT queue 7850 already unknown <0x8b9adb40>

^^ This line here indicates that the device is found in the Unknown Devices table.  Which means it has been told to Not be used and don't ever ask me again.  Hence why it is not adding the device.  Find the device in the webadmin -> advanced -> unknown devices list and remove it.  It should add itself the next time it is detected.

J.

Hi Phenigma,

Im Having more or less the same issue but in my case there is nothing under unknown devices.  How the issue was caused.  I wanted to do a fresh start of the zwave config, because I messed up one of my motion sensors and I was unable to remove it.  I used webadmin and removed zwave device, pull the stick out, reset the stick and the minimote and plug the zstick back again but it does not get detected by PNP.  Linux is detecting it and setting as ttyusb0

157645.840518] usb 1-1.6.2: cp210x converter now attached to ttyUSB0

But nothing happens later, there is no pnpqueue on the log registered neither. 
Any hints?

TP

[tompin2]

I added Manually the zstick for testing, this is the error I get

Code: [Select]

== FRESH START ==
1 02/09/16 20:05:16 /usr/pluto/bin/Spawn_Device.sh 267 (spawning-device) device: 267 ip: localhost cmd_line: ZWave
0 02/09/16 20:05:16 267 (spawning-device) Entering 267
========== NEW LOG SECTION ==========
1 02/09/16 20:05:16 267 (spawning-device) Starting... 1
1 02/09/16 20:05:16 267 (spawning-device) Found /usr/pluto/bin/ZWave
05 02/09/16 20:05:16.758 Connection for client socket reported NEED RELOAD IP=::ffff:127.0.0.1, device 267 last error 2 <0xb6e83700>
05 02/09/16 20:05:16.758 The router must be reloaded before this device is fully functional <0xb6e83700>
05 02/09/16 20:05:16.759 void ClientSocket::Disconnect() on this socket: 0x946a610 (m_Socket: 5) <0xb6e83700>
05 02/09/16 20:05:16.811 Connection for client socket reported NEED RELOAD IP=::ffff:127.0.0.1, device 267 last error 2 <0xb6e83700>
2016-02-09 20:05:16.858 Info, Reading /etc/openzwave/options.xml for Options
2016-02-09 20:05:16.858 Info, Reading /etc/openzwave/options.xml for Options
05 02/09/16 20:06:55.412 Got a reload command from 0  <0xb5affb40>
05 02/09/16 20:06:55.664 void ClientSocket::Disconnect() on this socket: 0x946af18 (m_Socket: 6) <0xb6e83700>
05 02/09/16 20:06:55.665 Socket::ReceiveData 0x946a378 failed, bytes left -1 start: 10000 1: 0 1b: 0 2: 0 2b: 0 m_Socket: 4 Event Dev #267 <0xb6e83700>
05 02/09/16 20:06:55.665 Socket::ReceiveString2 ReceiveData failed m_Socket: -1 Event Dev #267 <0xb6e83700>
01 02/09/16 20:06:55.665 Lost connection device: 267 <0xb6e83700>
05 02/09/16 20:06:55.665 Handshake failed. Retrying in 5 seconds <0xb6e83700>
05 02/09/16 20:07:01.672 Connect() failed, Error Code 111 (Connection refused)) <0xb6e83700>
05 02/09/16 20:07:04.735 Creating child 268 <0xb6e83700>
05 02/09/16 20:07:04.735 Note: Device manager has attached a device of type 1820 that this has no custom event handler for.  It will not fire events. <0xb6e83700>
05 02/09/16 20:07:04.735 Note: Device manager has attached a device of type 1820 that this has no custom handler for.  This is normal for IR. <0xb6e83700>
05 02/09/16 20:07:04.735 Creating child 269 <0xb6e83700>
05 02/09/16 20:07:04.735 Note: Device manager has attached a device of type 1922 that this has no custom event handler for.  It will not fire events. <0xb6e83700>
05 02/09/16 20:07:04.735 Note: Device manager has attached a device of type 1922 that this has no custom handler for.  This is normal for IR. <0xb6e83700>
01 02/09/16 20:07:04.790 TranslateSerialUSB pci0000:00/0000:00:1a.0+1.6.2 result /dev/ttyUSB0 <0xb6e83700>
05 02/09/16 20:13:09.968 Got a reload command from 0  <0xb46ffb40>
== ATTEMPT FRESH START ==
1 02/09/16 20:41:31 /usr/pluto/bin/Spawn_Device.sh 267 (spawning-device) 2017 Dev: 267; Already Running list: 15,33,
== FRESH START ==
1 02/09/16 20:41:31 /usr/pluto/bin/Spawn_Device.sh 267 (spawning-device) device: 267 ip: localhost cmd_line: ZWave
0 02/09/16 20:41:31 267 (spawning-device) Entering 267
========== NEW LOG SECTION ==========
1 02/09/16 20:41:31 267 (spawning-device) Starting... 1
1 02/09/16 20:41:31 267 (spawning-device) Found /usr/pluto/bin/ZWave
05 02/09/16 20:41:31.558 Creating child 268 <0xb6e9c700>
05 02/09/16 20:41:31.559 Note: Device manager has attached a device of type 1820 that this has no custom event handler for.  It will not fire events. <0xb6e9c700>
05 02/09/16 20:41:31.559 Note: Device manager has attached a device of type 1820 that this has no custom handler for.  This is normal for IR. <0xb6e9c700>
05 02/09/16 20:41:31.559 Creating child 269 <0xb6e9c700>
05 02/09/16 20:41:31.559 Note: Device manager has attached a device of type 1922 that this has no custom event handler for.  It will not fire events. <0xb6e9c700>
05 02/09/16 20:41:31.559 Note: Device manager has attached a device of type 1922 that this has no custom handler for.  This is normal for IR. <0xb6e9c700>
01 02/09/16 20:41:31.619 TranslateSerialUSB pci0000:00/0000:00:1a.0+1.6.2 result  <0xb6e9c700>
2016-02-09 20:41:31.620 Info, Reading /etc/openzwave/options.xml for Options
2016-02-09 20:41:31.620 Info, Reading /etc/openzwave/options.xml for Options
05 02/09/16 21:07:11.236 Got a reload command from 0  <0xb5affb40>
05 02/09/16 21:07:11.488 void ClientSocket::Disconnect() on this socket: 0x9699ef8 (m_Socket: 6) <0xb6e9c700>
05 02/09/16 21:07:11.489 Socket::ReceiveData 0x969f2c0 failed, bytes left 0 start: 30000 1: 0 1b: 0 2: 0 2b: 0 m_Socket: 4 Event Dev #267 <0xb6e9c700>
05 02/09/16 21:07:11.489 Socket::ReceiveString2 ReceiveData failed m_Socket: -1 Event Dev #267 <0xb6e9c700>
01 02/09/16 21:07:11.489 Lost connection device: 267 <0xb6e9c700>
05 02/09/16 21:07:11.489 Handshake failed. Retrying in 5 seconds <0xb6e9c700>
05 02/09/16 21:07:17.495 Connect() failed, Error Code 111 (Connection refused)) <0xb6e9c700>
05 02/09/16 21:07:18.496 Connect() failed, Error Code 111 (Connection refused)) <0xb6e9c700>
05 02/09/16 21:07:21.560 Creating child 268 <0xb6e9c700>
05 02/09/16 21:07:21.560 Note: Device manager has attached a device of type 1820 that this has no custom event handler for.  It will not fire events. <0xb6e9c700>
05 02/09/16 21:07:21.560 Note: Device manager has attached a device of type 1820 that this has no custom handler for.  This is normal for IR. <0xb6e9c700>
05 02/09/16 21:07:21.560 Creating child 269 <0xb6e9c700>
05 02/09/16 21:07:21.560 Note: Device manager has attached a device of type 1922 that this has no custom event handler for.  It will not fire events. <0xb6e9c700>
05 02/09/16 21:07:21.560 Note: Device manager has attached a device of type 1922 that this has no custom handler for.  This is normal for IR. <0xb6e9c700>
01 02/09/16 21:07:21.613 TranslateSerialUSB pci0000:00/0000:00:1a.0+1.6.2 result  <0xb6e9c700>

What is this connection refused?

Regards,

TP

[phenigma]

It looks like your serial ports are not translating properly to actual /dev/tty devices all the time.  This looks to me like the device is dropping off the usb bus.  Sometimes the translate gets a result and other times not.  The only reason that would happen is if the device is not present anymore.  You might turn on LV_STATUS and LV_DEBUG loglevels and tail the HAL log to see if the device is disconnecting.

J.

[tompin2]

It looks like your serial ports are not translating properly to actual /dev/tty devices all the time.  This looks to me like the device is dropping off the usb bus.  Sometimes the translate gets a result and other times not.  The only reason that would happen is if the device is not present anymore.  You might turn on LV_STATUS and LV_DEBUG loglevels and tail the HAL log to see if the device is disconnecting.

J.

Hi Phenigma,
I got tired of trying to find where the issue was and  migrated to 14.04, and all problems gone!. Furthermore, I replaced the z-stick s2 with a gen5 and Incredible positive results!.  Fast response zwave network, very stable so far with 19 devices.  Im not even running the stick on a dedicated usb powered switch!! No retries nor failed packages on any of the devices.  I hope this helps others.

[phenigma]

Very good to know.  Thanks for the feedback!

J.