Page 2 of 2

Re: Aeon Labs Z-Stick trouble

Posted: Fri Jul 18, 2014 9:07 pm
by mhn
I'm on HS2 too. :-|

Re: Aeon Labs Z-Stick trouble

Posted: Fri Nov 21, 2014 11:45 pm
by Edwin2008
Weird

Re: Aeon Labs Z-Stick trouble

Posted: Mon Dec 01, 2014 9:39 am
by uAlex73
In the open-zwave group somebody communicated with Aeon Labs, and they really gave a bogus/stupid reply:

Code: Select all

I have just gotten some more information from the engineers that I have been talking to, this is an issue that has happened before. The Z-Stick will lock up after processing a large volume of concurrent messages if the interval time of receiving messages is less than 1 minute. 
This will not happen if the interval time of receiving messages is more than 1 minute.
Seems Aeon Labs isn't interested on solving it (they cashed already :-(), but complaining via the following contact form can maybe help:
http://aeotec.com/contact

Re: Aeon Labs Z-Stick trouble

Posted: Tue Dec 02, 2014 10:51 pm
by raymonvdm
I also had the Aeon Labs issue and there i replaced the stick with a Zwave.ME Stick

However sometimes the Z-Wave network seems slow. I think it has something to do with the FTDI drivers i`m currently using since the are upgraded when installing the stick. I` m currently running version 2.8.30.0 and i would like to know which version other people are using


Update: I updated the driver to version 2.12.00 but it makes nog difference so i monitored the log more closely and found the following loglines

Code: Select all


2-12-2014 23:38:11 ~!~Event~!~Event Trigger "Maak_Woonkamer_Gezellig OFF"
2-12-2014 23:38:11 ~!~Device Control~!~Device: Beganegrond Woonkamer Keukenkastjes (A3) OFF
2-12-2014 23:38:11 ~!~Device Control~!~Device: Beganegrond Woonkamer Vloerlamp (Q42+41+33+39+40) OFF
2-12-2014 23:38:11 ~!~Device Control~!~Device: Beganegrond Woonkamer Woonkamer (Q38) Dim 60%
2-12-2014 23:38:11 ~!~Event~!~Event Trigger "Maak Android Slaap"
2-12-2014 23:38:12 ~!~Event~!~Waiting 0 minute(s) 45 second(s) 0 millisecond(s)
2-12-2014 23:38:12 ~!~Event~!~Waiting 0 minute(s) 45 second(s) 0 millisecond(s)
2-12-2014 23:38:24 ~!~Warning~!~Aborting Z-Wave send, taking too long to send command to node 1 waited 12 seconds
2-12-2014 23:38:28 ~!~ERROR~!~Timeout waiting for send abort to complete
2-12-2014 23:38:28 ~!~Warning~!~Failed sending Z-Wave Multicast command to one or more node(s): 13,12,11
2-12-2014 23:38:40 ~!~Warning~!~Aborting Z-Wave send, taking too long to send command to node 1 waited 12 seconds
2-12-2014 23:38:44 ~!~ERROR~!~Timeout waiting for send abort to complete
2-12-2014 23:38:44 ~!~Warning~!~Failed sending Z-Wave Multicast command to one or more node(s): 7,10

But why is it sending multicast commands ?