Aeotec Z-Stick Gen 5 Z-Wave disconnects/goes to sleep

[Geir]

Hi. I'm trying to get my first z-wave setup to work, and have bought a  Z-Stick Gen 5 adapter, and try to use it in fhem.

When I plug the usb stick into the computer, it is active for a short while, before it is listet with a state of "disconnected". From the logs:

2018.11.10 22:53:21 3: Setting ZWDongle_0 serial parameters to 115200,8,N,1
2018.11.10 22:53:23 2: ZWDongle_ProcessSendStack: no ACK, resending message 0105004a810130
2018.11.10 22:53:24 2: ZWDongle_ProcessSendStack: no ACK, resending message 0105004ac10273
2018.11.10 22:53:25 2: ZWDongle_ProcessSendStack: no ACK, resending message 0105004ac10372
2018.11.10 22:53:26 2: ZWDongle_ProcessSendStack: no ACK, resending message 01030007fb
2018.11.10 22:53:26 1: /dev/ttyACM0 reappeared (ZWDongle_0)
2018.11.10 22:57:37 1: /dev/ttyACM0 disconnected, waiting to reappear (ZWDongle_0)

Is there a way to configure this usb stick to be always on ? any settings in fhem i should use ? Please advice

[MadMax-FHEM]

Do you have more than one usb device?

Post the list of your device:

Code Auswählen Erweitern

list ZWDongle_0

and please use code-Tags for posting ('#' in the icon bar).

What does

Code Auswählen Erweitern

ls -la /dev/serial/by-id/

show?

I defined mine using serial/by-id

Did you deactivate the initial usb-check!?

Bye, Joachim

[rudolfkoenig]

This symptom is typical on the RPi if the power supply is not powerful enough.

[Geir]

Thanks for the replies. The computer is not an RasperryPi, but a small computer running regular ubuntu.

There is only one USB device connected to the computer.

Since this is ubuntu, there is no /dev/serial/ path.

Output from [/size]list ZWDongle_0 is

Code Auswählen Erweitern

Internals:
   CallbackNr 5
   Clients    :ZWave:
   DEF        /dev/ttyACM0@115200
   DeviceName /dev/ttyACM0@115200
   MaxSendRetries 3
   NAME       ZWDongle_0
   NR         15
   PARTIAL   
   ReadTime   1541886921.8617
   STATE      disconnected
   SendRetries 0
   SendTime   1541886921.76319
   TYPE       ZWDongle
   WaitForAck 0
   homeId     dbab3a74
   nodeIdHex  01
   nrNAck     0
   MatchList:
     1:ZWave    .*
   READINGS:
     2018-11-10 22:53:26   caps            Vers:1 Rev:1 ManufID:0086 ProductType:0001 ProductID:005a SERIAL_API_GET_INIT_DATA SERIAL_API_APPL_NODE_INFORMATION APPLICATION_COMMAND_HANDLER ZW_GET_CONTROLLER_CAPABILITIES SERIAL_API_SET_TIMEOUTS SERIAL_API_GET_CAPABILITIES SERIAL_API_SOFT_RESET UNKNOWN_09 ZW_SET_R_F_RECEIVE_MODE ZW_SET_SLEEP_MODE ZW_SEND_NODE_INFORMATION ZW_SEND_DATA ZW_SEND_DATA_MULTI ZW_GET_VERSION ZW_SEND_DATA_ABORT ZW_R_F_POWER_LEVEL_SET ZW_SEND_DATA_META ZW_GET_RANDOM MEMORY_GET_ID MEMORY_GET_BYTE MEMORY_PUT_BYTE MEMORY_GET_BUFFER MEMORY_PUT_BUFFER FLASH_AUTO_PROG_SET NVM_GET_ID NVM_EXT_READ_LONG_BUFFER NVM_EXT_WRITE_LONG_BUFFER NVM_EXT_READ_LONG_BYTE NVM_EXT_WRITE_LONG_BYTE ZW_GET_NODE_PROTOCOL_INFO ZW_SET_DEFAULT ZW_REPLICATION_COMMAND_COMPLETE ZW_REPLICATION_SEND_DATA ZW_ASSIGN_RETURN_ROUTE ZW_DELETE_RETURN_ROUTE ZW_REQUEST_NODE_NEIGHBOR_UPDATE ZW_APPLICATION_UPDATE ZW_ADD_NODE_TO_NETWORK ZW_REMOVE_NODE_FROM_NETWORK ZW_CREATE_NEW_PRIMARY ZW_CONTROLLER_CHANGE ZW_SET_LEARN_MODE ZW_ASSIGN_SUC_RETURN_ROUTE ZW_REQUEST_NETWORK_UPDATE ZW_SET_SUC_NODE_ID ZW_DELETE_SUC_RETURN_ROUTE ZW_GET_SUC_NODE_ID ZW_SEND_SUC_ID ZW_EXPLORE_REQUEST_INCLUSION ZW_REQUEST_NODE_INFO ZW_REMOVE_FAILED_NODE_ID ZW_IS_FAILED_NODE ZW_REPLACE_FAILED_NODE UNKNOWN_66 UNKNOWN_67 GET_ROUTING_TABLE_LINE LOCK_ROUTE_RESPONSE ZW_GET_PRIORITY_ROUTE ZW_SET_PRIORITY_ROUTE UNKNOWN_98 ZW_SET_WUT_TIMEOUT ZW_WATCHDOG_ENABLE ZW_WATCHDOG_DISABLE ZW_WATCHDOG_CHECK ZW_SET_EXT_INT_LEVEL ZW_RF_POWERLEVEL_GET ZW_TYPE_LIBRARY ZW_SEND_TEST_FRAME ZW_GET_PROTOCOL_STATUS WATCHDOG_START WATCHDOG_STOP ZW_SET_ROUTING_MAX UNKNOWN_ee UNKNOWN_ef
     2018-11-10 22:53:26   ctrlCaps       
     2018-11-10 22:53:26   homeId          HomeId:dbab3a74 CtrlNodeIdHex:01
     2018-11-10 22:55:21   nodeList        ZWDongle_0 UNKNOWN_3
     2018-11-10 22:53:26   random          0dfd09bafedcd80271cb751af2e26de9758d294ce76108db9d2afe88446e348b
     2018-11-10 22:57:37   state           disconnected
     2018-11-10 22:53:26   sucNodeId       no
   SendStack:
     01030002fe
     0105004a810435
     0105004a810534
   addCL:
     Authenticated 0
     BUF       
     LASTACCESS 1541997623
     NAME       WEB_192.168.1.16_55304
     NR         159
     PEER       192.168.1.16
     PORT       55304
     SNAME      WEB
     SSL       
     STATE      Connected
     TEMPORARY  1
     TYPE       FHEMWEB
     READINGS:
       2018-11-12 05:39:11   state           Connected
Attributes:
   homeId     dbab3a74
   neighborListPos 52.234375,20
   room       stue


[jeti]

Hi I am having the same issue... any progress yet?

[rudolfkoenig]

Not really.
I noticed in the meantime, that my old ZWave-Controller goes offline, if the USB-Hub is doing some (unrelated) serious work. Do not have any remedy for this either, looks like a hardware issue for me.

[jeti]

  ok, ist there an comparable Z-Wave USB Dongle that actually works fine?

[MadMax-FHEM]

ok, ist there an comparable Z-Wave USB Dongle that actually works fine?

The type mentioned here works fine on my PI...

The same for the USB ZWave.me Stick (but that is what I have read so far not as good / but again: no problem with that).

Bye, Joachim

[jeti]

as I was not really sure if this is a hardware issue or Software issue here are my specks:
Rock64 with ZWave.me Stick
as a Workaround I have:

Code Auswählen Erweitern


define AT_zwave at +05:00:00 set ZWAVE_Dongle reopen

which is by far not nice but, makes it work...
So the Issue really sounds like compatibility issue to me, as some configurations are fine and some not... I guess I will try another dongle...
thanks for the fast response!

[jeti]

ok, I tried the steup with Armbian and upto now it works far more stable... I do not know the details why, but it does...

[Geir]

I have gotten my usb stick to work. I appears to have been an unstable USB connection. Once i switched USB port and wiggled it around a bit it is now stable (dont like this solution, but..).

Once the device is active it's led is cycling though different colors, and fhem reports the device as "Initialized". I'm now able to controll my swtich through FHEM

[MadMax-FHEM]

If the color switching is anoying you can turn it off...
...I did...

Bye, Joachim

[sz_wolfi]

Hi,
...just an FYI - as I've not yet seen this detail:

I have BOTH the UZB-stick and the AEOTEC

BOTH sticks plugged into a centos-7.5 box:

AEOTEC:
Bus 006 Device 003: ID 0658:0200 Sigma Designs, Inc. Aeotec Z-Stick Gen5 (ZW090)

UZB-stick:
Bus 001 Device 016: ID 0658:0200 Sigma Designs, Inc. Aeotec Z-Stick Gen5 (ZW090) - UZB

So quite funny, that the vendor/product IDs are the same for both sticks - not kidding.
Externally - they look quite different ...

But from the basic functionality - they are both the same.
I was 'forced' to do an OTA-firmware-upgrade to an AEOTEC-nano-dimmer and an AEOTEC-LED-bulb - and for this - I just connected the UZB-stick to a Windows-VM - and the AEOTEC-update-blob worked without any issues - with the UZB-Stick as the controller.

...and I see no issues with any of the two sticks.
The AEOTEC-stick 'lives' on a headless x86_64 machine, while the UZB-stick is hooked up to a wireless-router (ser2net) ... - none of them have any disconnect issues.