- #Aeon labs z stick homeseer does not recognize serial#
- #Aeon labs z stick homeseer does not recognize driver#
- #Aeon labs z stick homeseer does not recognize software#
- #Aeon labs z stick homeseer does not recognize Pc#
- #Aeon labs z stick homeseer does not recognize windows#
I had to unplug the z-stick AND press the reset button. Tried powered hub, replacing the z-stick. The guy) is to send no more than one message per minute to the controller. Their suggestion (as best I could understand I’ve corresponded with Aeon Labs about the issue, but they haven’t been at all helpful. Wait a day or so to confirm that not only isn’t the Z-Stick receiving frames from your PC, it won’t send any to you either (like when a node’s valueĬhanges and would ordinarily result in a message through the controller to the PC). Try (writing) again as many times as you like, you won’t get an ACK back.ĭ. Write to the Z-Stick (when it’s ready to lock up).Ĭ. I lose 20-30 seconds of data, but…Ģ) It isn’t something that gets logged (as far as I know)…from an OZW perspective it’s pretty straightforward:Ī.
#Aeon labs z stick homeseer does not recognize Pc#
Receipt of this notification, my controlling application reboots the PC and automatically restarts my application. One small change I’ve added is a notification when the controller becomes unresponsive.
I’m about to release a prototype of a “next-gen” OZW (or at least an alternate gen).
#Aeon labs z stick homeseer does not recognize windows#
The only thing I’ve found that does (and I’ve spent a lot of time in Windows and Linux programmaticallyĭisconnecting the COM port, trying to power it down (Linux), etc.) is a reboot.
#Aeon labs z stick homeseer does not recognize serial#
Send me a link to the capture file (It would be too big to email I believe) and I can have a quick look.Ī quick google search also revealed lots of hits on "cp210x hang", but seem to be related to opening the serial port rather than hanging later (but all post 3.2 kernels)ġ) A powered USB hub didn’t do the trick for me. Start the capture before starting OZW, and stop and save it after it "hangs".
This could at least "indicate" where the stick hangs (in the OS, in the Stick etc) If you do experience this issue, and are moderatly "techy", then I'd load up the usbmon module on linux, and start up wireshark to do a USB capture of the traffic to the stick.
#Aeon labs z stick homeseer does not recognize driver#
so its hard to diagnose and figure out if its OZW triggering something, a Operating System issue (USB goes funky) or a Z-Stick Firmware bug.įor my Devices, they are running on CentOS 6.4 and the kernel version is 2.6.32 - Looking over the driver logs for the cp210x (the Linux Driver that talks to the Z-Stick) it seems several patches were applied around kernel 3.2.Ĭan you confirm what version kernel you are using? I've not seen this issue at all (and I'm maintaining a installation with over 50 Z-Sticks). It seems as if the Z-Stick 2 is a popular controller for OZW users. It can work for tens of thousands of transactions (or just a few), but the Z-Stick eventually becomes unresponsive.Īnyway, I'll keep everyone informed as to progress on this issue. I use several concurrent transactions (up to two additional messages started before a requested "report" is received from the network) with essentially no delays between transactions. Admittedly, I'm pushing the controller much more aggressively than the current OZW library. If the average failure is after 100,000 transactions, it would take almost 70 days (at 1 transaction per minute) to observe the issue.
Just slowing down the rate at which transactions are started on the controller might just extend the time required to observe a failure. If they won't/can't fix the firmware, I'm hoping that they'll at least diagnose the issue carefully enough that a reasonable workaround can be devised. I suspect that it's a firmware bug (like some buffer overflows).
#Aeon labs z stick homeseer does not recognize software#
While I'm glad they've acknowledged the issue, I'm not sure what they mean by "the interval time of receiving messages is less than 1 minute." Every Z-Wave software of which I'm aware sends substantially more than one message per minute, so I'm hoping that's not what they meant! I've emailed back to ask them for more clarification and to offer some help (in the form of a program that can pretty consistently "break" the Z-Stick by making it unresponsive) if they'll further diagnose the issue. This will not happen if the interval time of receiving messages is more than 1 minute.
0 kommentar(er)
